1Z0-083 · Question #189
Identify three reasons for using a recovery catalog with Recovery Manager (RMAN).
The correct answer is A. to allow database duplication without a connection to the target instance. B. to store backup metadata that would cause the controlfile to become too large. D. to report on the database schema at an earlier point in time. Using an RMAN recovery catalog is correct for options A, B, and D because the catalog is a separate Oracle schema that stores extended backup metadata, historical database structural information, and enables flexible duplication scenarios. A is correct because with…
Question
Identify three reasons for using a recovery catalog with Recovery Manager (RMAN).
Options
- Ato allow database duplication without a connection to the target instance.
- Bto store backup metadata that would cause the controlfile to become too large.
- Cto store backups that would cause the controlfile to become too large.
- Dto report on the database schema at an earlier point in time.
- Eto allow database duplication without a connection to the auxiliary instance.
How the community answered
(63 responses)- A76% (48)
- C16% (10)
- E8% (5)
Explanation
Using an RMAN recovery catalog is correct for options A, B, and D because the catalog is a separate Oracle schema that stores extended backup metadata, historical database structural information, and enables flexible duplication scenarios. A is correct because with catalog-stored metadata, RMAN can duplicate a database using the catalog as the source of backup information, removing the requirement to connect to the (potentially unavailable) target database. B is correct because the controlfile has a fixed, limited capacity for RMAN metadata - a recovery catalog offloads that metadata to a dedicated schema, preventing controlfile bloat for long-running or heavily-backed-up databases. D is correct because the catalog tracks historical schema changes (tablespace history, datafile additions/drops, incarnations), enabling REPORT and LIST commands to describe the database structure as it existed at a prior point in time.
C is wrong because the catalog stores metadata about backups (location, timestamps, piece names), not the actual backup data itself - backup sets and image copies live on disk or tape, never inside the catalog. E is wrong because the auxiliary instance is the destination of a duplication and must always be connected - it's the target (source) connection that the catalog can replace.
Memory tip: Think of the catalog as a "smart librarian" - it remembers where things are (metadata → B), what things looked like before (history → D), and lets you check out books even if the original store is closed (no target needed → A). The librarian stores records, not the books themselves (eliminating C), and you still have to hand the books to the person receiving them (auxiliary must connect → eliminating E).
Topics
Community Discussion
No community discussion yet for this question.