Exam 1z0-083 topic 1 question 104 discussion

CE correct In a full resynchronization, RMAN updates all changed records, including those for the database schema. RMAN performs a full resynchronization after structural changes to database (adding or dropping database files, creating new incarnation, and so on) or after changes to the RMAN persistent configuration. When a database is registered with a recovery catalog for the first time a full catalog synchronization is performed https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/managing-recovery-catalog.html#GUID-6B077FE7-8E10-4603-8FDB-CAE3357E85C9 https://www.oracledistilled.com/oracle-database/backup-and-recovery/registering-a-database-with-a-recovery-catalog/#:~:text=Using%20RMAN%2C%20connect%20to%20both,register)%20and%20the%20recovery%20catalog.&text=Next%20issue%20the%20REGISTER%20DATABASE%20command%20to%20register%20the%20database.&text=When%20a%20database%20is%20registered,is%20performed%20(%20RESYNC%20CATALOG%20).

C. I AM confuse. say "As with archive operations, the recovery catalog is not updated automatically when the physical schema changes." but tablespace is in the logical level,

Answer is DE Ref : https://www.devdoc.net/database/OracleDoc_19c_index/content/rcmrf/RESYNC-CATALOG.html#GUID-DF91BD12-A00D-49CC-99C5-E8EDD0094CCE So, As with log archiving, the recovery catalog is not updated automatically when the physical schema changes DE correct.

C & E 13.8.2.1 About Resynchronization of the Recovery Catalog Resynchronization of the recovery catalog ensures that the metadata that RMAN obtains from the control file stays current. Resynchronizations can be full or partial. In a partial resynchronization, RMAN reads the current control file of the target database to update changed metadata about new backups, new archived redo logs, and so on. RMAN does not resynchronize metadata about the database physical schema. In a full resynchronization, RMAN updates all changed records, including those for the database schema. RMAN performs a full resynchronization after structural changes to database (adding or dropping database files, creating new incarnation, and so on) or after changes to the RMAN persistent configuration. --- https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/managing-recovery-catalog.html#GUID-C4EC7335-316B-45D6-A021-2A2B2030439F

DE. C is incorrect. How did i test it? 1-Check what the catalog knows about the target tablespaces. You can see this in the catalog view: RC_TABLESPACES select ts#, name, creation_time from rc_tablespace; 2-Create tablepsace on target, name it whatever you want. 3-Check the catalog view again (step 1). You will not see the new tablespace you just created on target, meaning it did not do an automatic resync. 4- Resync manually on RMAN : RESYNC CATALOG 5- Check again the catalog's view RC_TABLESPACES: You will now see that the new tablespace information on the catalog's view, meaning you had to manually resync the catalogo to update it after a tablepsace creation. ------ D is correct. Tested it the same way, but this time using the catalog's view: RC_BACKUP_CONTROLFILE select bcf_key from RC_BACKUP_CONTROLFILE; --displays unique ids of controlfile backups as backupsets on the catalog. And in RMAN: backup as backupset current control file You will notice that the catalog is updated automatically when you backup the current control file.

CE because question is talking about FULL sync not PARTIAL.

D,E correct. C is incorrect: RMAN> show controlfile autobackup; RMAN configuration parameters for database with db_unique_name CDB1 are: CONFIGURE CONTROLFILE AUTOBACKUP ON; # default RMAN> sql pdb1 'create tablespace t4'; sql statement: create tablespace t4 RMAN>

Agree with egore0496, when a tablespace is added to a registered target, the catalog is NOT automatically resynced

CE ... I think D is wrong, it is a tricky answer "when a backup of the current control file is created" but full synchronize is done after the backup was created.

NOT C DE https://web.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14191/rcmcatdb003.htm RMAN> register database; database registered in recovery catalog starting full resync of recovery catalog full resync complete RMAN> backup current controlfile; Starting backup at 26.01.2022 18:24:45 starting full resync of recovery catalog full resync complete allocated channel: ORA_DISK_1

I think D, E for 'automatic full resynchronization'. https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/managing-recovery-catalog.html#GUID-87642B50-AF67-482E-A93D-291B8D2EED92 Most 'RMAN commands' perform a resynchronization automatically when the target control file is mounted and the catalog is available. RMAN> backup current controlfile; Starting backup at 08-JAN-22 12:14:16 starting full resync of recovery catalog full resync complete allocated channel: ORA_DISK_1 https://docs.oracle.com/en/database/oracle/oracle-database/19/rcmrf/RESYNC-CATALOG.html#GUID-DF91BD12-A00D-49CC-99C5-E8EDD0094CCE Typically, you run RESYNC CATALOG in the following situations: You made changes to the physical structure of the target database such as adding or dropping a tablespace. As with log archiving, the recovery catalog is NOT updated automatically when the physical schema changes.

Agree, C and E