nerdexam
Oracle

1Z0-052 · Question #235

It is a holiday and no transactions are being performed on the database. You took a consistent backup of your database without using Recovery Manager (RMAN). How would you make use of this…

The correct answer is A. cannot be used in RMAN. A consistent Oracle backup taken using OS-level user-managed methods without RMAN cannot be used by RMAN because it exists entirely outside RMAN's repository and proprietary backup format.

Performing Backup and Recovery

Question

It is a holiday and no transactions are being performed on the database. You took a consistent backup of your database without using Recovery Manager (RMAN). How would you make use of this consistent backup in RMAN?

Options

  • Acannot be used in RMAN
  • Bby starting up the database again
  • Cby using the CATALOG command of RMAN
  • Dby using the RECOVER CATALOG command in RMAN
  • Eby re-creating the target control file to rebuild the RMAN repository

How the community answered

(39 responses)
  • A
    56% (22)
  • B
    13% (5)
  • C
    8% (3)
  • D
    3% (1)
  • E
    21% (8)

Why each option

A consistent Oracle backup taken using OS-level user-managed methods without RMAN cannot be used by RMAN because it exists entirely outside RMAN's repository and proprietary backup format.

Acannot be used in RMANCorrect

RMAN operates exclusively with backups it has created (backup sets or image copies) that are tracked in its repository or recovery catalog. A user-managed consistent cold backup consists of raw OS-level file copies that are not in RMAN's backup set format and are not registered in RMAN's repository, making them incompatible with RMAN restore and recovery operations.

Bby starting up the database again

Starting the database again is a standard database operation and has no bearing on whether RMAN can recognize or incorporate a user-managed backup taken outside of RMAN.

Cby using the CATALOG command of RMAN

The RMAN CATALOG command is used to register RMAN-created backup pieces or image copies that are missing from the catalog, not to import arbitrary OS-level cold backup files created entirely outside of RMAN.

Dby using the RECOVER CATALOG command in RMAN

RECOVER CATALOG is an RMAN command used to synchronize a separate recovery catalog database with the target control file, not to import or register external user-managed backup files.

Eby re-creating the target control file to rebuild the RMAN repository

Re-creating the control file rebuilds the database's control file metadata structure but does not enable RMAN to use a backup it did not create and has no record of in its repository.

Concept tested: RMAN compatibility limitations with user-managed Oracle backups

Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/user-managed-database-backups.html

Topics

#RMAN catalog#user-managed backup#consistent backup#backup interoperability

Community Discussion

No community discussion yet for this question.

Full 1Z0-052 Practice