OCP 1Z0 053 161

161.You are using a recovery catalog to maintain Recovery Manager (RMAN) backup information for your 
production database. You have registered your production database and are performing regular backups. 
Because of a new requirement you have added a few new tablespaces to your production database and 
you want them to be included in backups. Identify two options for completing this task. (Choose two.) 
A. Reregistering the target database in recovery catalog 
B. Transporting the new tablespaces to the recovery catalog database 
C. Syncronizing the recovery catalog with the target database control file 
D. Performing a fresh backup of the target database to include the new data files in the catalog database 
Answer: CD

增加表空间后需要同步metadata，并重新备份

file:///G:/book/Oracle/E11882_01/backup.112/e10643/rcmsynta2009.htm#i999772

RESYNC CATALOG

Purpose

Use the RESYNC CATALOG command to perform a full resynchronization of metadata in a recovery catalog schema with metadata in a target database control file. You can also use the FROM CONTROLFILECOPY clause to resynchronize the current control file with the RMAN metadata in a control file copy.

Typically, you run RESYNC CATALOG in the following situations:

• The recovery catalog was unavailable when you executed RMAN commands that automatically perform a resynchronization.

• The target database is running in ARCHIVELOG mode, because the recovery catalog is not updated automatically when an online redo log switch occurs or when a redo log is archived.

• You made changes to the physical structure of the target database such asadding or dropping a tablespace. As with log archiving, the recovery catalog is not updated automatically when the physical schema changes.

• RMAN is connected as TARGET to a standby database. You want to update the recovery catalog with metadata about RMAN operations performed on this database.

• RMAN is connected as TARGET to a standby database. You want to update the recovery catalog with metadata about a physical change on the primary database (see Example 3-29).