OCP-1Z0-053-V12.02-365题

 

365.Which of the following restrictions are not true with respect to tablespace point-in-time recovery?

(Choose all that apply.)

A. The target database must be in NOARCHIVELOG mode.

B. No backup is required of the database before you perform a TSPITR.

C. 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.

D. If you rename a tablespace, you can not perform a TSPITR to any point in time before that rename

operation occurred.

E. If you have tables in tablespace_1 that have associated constraints in tablespace_2, then you must

transport both tablespaces.

Answer: AB

答案解析：

官方参考：http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmtspit.htm#BRADV161

TSPITR Restrictions, Special Cases, and Limitations

Some database problems cannot be resolved with TSPITR. The following list explains when you cannot perform TSPITR:

• If there are no archived redo logs or if the database runs in NOARCHIVELOG mode.

• If TSPITR is used to recover a renamed tablespace to a point in time before it was renamed, you must use the previous name of the tablespace to perform the recovery operation.

  In this case when TSPITR completes, the target database contains two copies of the same tablespace, the original tablespace with the new name and the TSPITR tablespace with the old name. If this is not your goal, then you can drop the new tablespace with the new name.

• If constraints for the tables in tablespace tbs1 are contained in tablespace tbs2, then you cannot recover tbs1 without also recovering tbs2.

• You cannot use TSPITR to recover the current default tablespace.

• You cannot use TSPITR to recover tablespaces containing any of the following objects:

  • Objects with underlying objects (such as materialized views) or contained objects (such as partitioned tables) unless all of the underlying or contained objects are in the recovery set

  • Undo or rollback segments

  • Oracle8-compatible advanced queues with multiple recipients

  • Objects owned by the user SYS. Examples of these types of objects are: PL/SQL, Java classes, callout programs, views, synonyms, users, privileges, dimensions, directories, and sequences.