The tablespace cannot be duplicated or restored to any point in time after the duplication.
The tablespace cannot be duplicated or restored to the point in time before the duplication.
The entire database cannot be restored after a TSPITR, so a backup is required.
You cannot bring the tablespace online until its been backed up.
There is no requirement to do so, as RMAN will back up the tablespace after the TSPITR.
第1题:
You have a database with the following tablespaces: SYSTEM, SYSAUX, UNDO, USERS, TEMP. You want to"roll back" the data in the USERS tablespace to the way it looked yesterday. Which tablespaces do you need to perform a point-in-time restore operation on in order to complete this task?()
第2题:
What RMAN command is used to execute a tablespace point-in-time recovery?()
第3题:
Which of the following restrictions are not true with respect to tablespace point-in-time recovery?()
第4题:
Why should you back up a duplicated tablespace after a TSPITR is complete?()
第5题:
You lost the PRODSTD tablespace, which was read/write. The tablespace was read-only when the last backup was performed. How would you recover the tablespace?()
第6题:
flash back the database
perform point-in-time recovery
perform a full database recovery
drop and re-create the tablespace
use Recovery Manager (RMAN) to recover the database
第7题:
You cannot perform the TSPITR with the constraints enabled.
You must perform the TSPITR recovery of both tablespaces for it to be successful.
You can perform TSPITR only on the USERS tablespace.
RMAN will determine if the INDEX_TBS tablespace must also be duplicated and will duplicate it automatically.
The TSPITR will only be successful if the constraint is enabled.
第8题:
The database is in ARCHIVELOG mode.
There is not a current backup of the database available.
The USERS tablespace has dependent objects in other tablespaces and can not be a part of a TSPITR alone.
The USERS tablespace is not eligible for TSPITR because it has invalid objects.
The recover tablespace command is incorrect and generates the error.
第9题:
recover
duplicate
restore
copy
None of the above
第10题:
restore the tablespace from the backup; there is no need to apply the redo information
restore the full database to recover the data up to the point when you performed the backup
restore the tablespace from the backup and then perform a recovery using the backup control file
restore the tablespace from the backup and then recover the tablespace; all the redo information from the point when the tablespace was made read/write is applied
第11题:
The SYSTEM tablespace.
The UNDO tablespace.
All tablespaces with tables.
All tablespaces with indexes.
No tablespaces are automatically restored.
第12题:
alter tablespace MY_DATA begin backup
alter tablespace MY_DATA start backup
alter tablespace MY_DATA backup begin
alter MY_DATA begin backup
You cannot back up individual tablespaces
第13题:
Your Supportcenter.cn database is in ARCHIVELOG mode. The data file that belongs to the SYSTEM tablespace has become corrupted. Up to what point can you recover the database?()
第14题:
Which command is used to begin a tablespace point-in-time recovery?()
第15题:
You lost the index tablespace in your database. You are not able to use tablespace point-in-time recovery on the index tablespace. What could be the reason for this?()
第16题:
Youre performing tablespace point-in-time recovery on a tablespace called USERS. If an object in that tablespace has a foreign key constraint owned by another object in the INDEX_TBS which statement is true?()
第17题:
You want to put a specific tablespace called MY_DATA in hot backup mode so you can back it up. What command would you use?()
第18题:
The index tablespace contains bitmap indexes.
The index tablespace contains more than one data file.
The index tablespace supports only complete recovery.
The index tablespace is not a dictionary-managed tablespace.
There is a dependency relationship between a table and its indexes.
第19题:
Perform Export before TSPITR and Import after TSPITR
Move objects to another schema that has the same tablespace assigned
Perform Incomplete Recovery before TSPITR with the Log Sequence Number (LSN)
Perform Incomplete Recovery before TSPITR with the System Change Number (SCN)
第20题:
The target database must be in NOARCHIVELOG mode.
No backup is required of the database before you perform a TSPITR.
You must have all archived redo logs generated since the last backup up to the point to which you want to restore the transport set.
If you rename a tablespace, you can not perform a TSPITR to any point in time before that rename operation occurred.
If you have tables in tablespace_1 that have associated constraints in tablespace_2,then you must transport both tablespaces.
第21题:
recover tablespace users until time ,,10/06/2008:22:42:00 auxiliary ,,c/oracle/auxiliary
recover tablespace users time ,,10/06/2008:22:42:00 auxiliary destination ,,c:/oracle/auxiliary; time ,, 10/06/2008:22:42:00 auxiliary destination ,,c/oracle/auxiliary
recover tablespace users to point-in.
recover tablespace users except time ,,10/06/2008:22:42:00 auxiliary destination ,,c:/oracle/auxiliary
recover tablespace users until time ,,10/06/2008:22:42:00 auxiliary destination ,,c:/oracle/auxiliary
第22题:
Until last commit
Until the time you perform recovery
Until the time the date file got corrupted
Until the point where the last transaction begun
You cannot recover the SYSTEMtablespaceand must re-create the database.
第23题:
Perform Export before TSPITR and Import after TSPITR
Move objects to another schema that has the same tablespace assigned
Perform Incomplete Recovery before TSPITR with the Log Sequence Number (LSN)
Perform Incomplete Recovery before TSPITR with the System Change Number (SCN)