1Z0-062 · Question #60
Which three statements are true about using flashback database in a multitenant container database (CDB)?
The correct answer is A. The root container can be flashed back without flashing back the pluggable databases (PDBs). B. To enable flashback database, the CDB must be mounted. D. The DB_FLASHBACK RETENTION_TARGET parameter must be set to enable flashback of the. Flashback database in a CDB requires the database to be mounted for enablement, DB_FLASHBACK_RETENTION_TARGET must be configured, and the root can be independently flashed back in supported configurations.
Question
Which three statements are true about using flashback database in a multitenant container database (CDB)?
Options
- AThe root container can be flashed back without flashing back the pluggable databases (PDBs).
- BTo enable flashback database, the CDB must be mounted.
- CIndividual PDBs can be flashed back without flashing back the entire CDB.
- DThe DB_FLASHBACK RETENTION_TARGET parameter must be set to enable flashback of the
- EA CDB can be flashed back specifying the desired target point in time or an SCN, but not a
How the community answered
(58 responses)- A71% (41)
- C12% (7)
- E17% (10)
Why each option
Flashback database in a CDB requires the database to be mounted for enablement, DB_FLASHBACK_RETENTION_TARGET must be configured, and the root can be independently flashed back in supported configurations.
In a multitenant CDB, the root container can be flashed back independently of PDBs; after flashing back the CDB, individual PDBs that should not be reverted can be recovered forward using RMAN, allowing selective point-in-time management per container.
Flashback database is enabled by issuing ALTER DATABASE FLASHBACK ON while the CDB is in the MOUNT state; the database cannot be open when this command is executed, making the mounted state a prerequisite.
In the shared undo mode available through Oracle 12.1, individual PDB flashback is not supported independently - a flashback operation affects the entire CDB including all PDBs, making this statement false in that context.
DB_FLASHBACK_RETENTION_TARGET specifies the desired retention period in minutes for flashback logs in the fast recovery area; setting this parameter is required so Oracle retains sufficient flashback log data to support the desired recovery window.
This choice is truncated but implies that restore points cannot be used as a flashback target, which is incorrect - Oracle supports flashing back a CDB to a named restore point, an SCN, or a specific point in time.
Concept tested: Flashback database enablement and behavior in multitenant CDB
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/using-oracle-flashback-database-restore-points.html
Topics
Community Discussion
No community discussion yet for this question.