You take regular backups of one of your production databases by using RMAN with a recovery catalog. You have added two new tablespaces to this database which must be included in future backups…

Question

Options

• AThe target database control file is synchronized from the recovery catalog with a partial resync
• BThe recovery catalog is synchronized from the target database control file with a full resync at
• CThe target database control file is synchronized from the recovery catalog with a full resync at
• DThe recovery catalog is synchronized from the target database control file with a partial resync

• A
  13% (3)
• B
  74% (17)
• C
  4% (1)
• D
  9% (2)

Explanation

When new tablespaces are added, the target database's control file is the authoritative source of truth about the database structure. RMAN must push that structural information into the recovery catalog - not the other way around - which is why B is correct: the recovery catalog is synchronized from the control file, and because a structural change (new datafiles) occurred, a full resync is required to capture the complete updated schema metadata.

Option A is wrong on both counts: the direction is reversed (the catalog cannot be the source for new datafile information it doesn't yet have), and "partial" resync only updates backup/restore job records, not structural changes. Option C shares the same fatal flaw as A - the direction is inverted; the control file is always the source, the catalog is always the destination. Option D gets the direction right but uses "partial resync," which is insufficient - partial resyncs handle incremental metadata updates (like completed backup records), while structural changes like new tablespaces always require a full resync to register new datafile entries.

Memory tip: Think of it as a one-way street - data flows from the control file to the catalog, never in reverse. And remember "structural change = full resync" (F for Full, F for File/tablespace added).

No community discussion yet for this question.