1Z0-060 · Question #146
Your multitenant container (CDB) containing three pluggable databases (PDBs) is running in ARCHIVELOG mode. You find that the SYSAUX tablespace is corrupted in the root container. The steps to…
The correct answer is A. 6, 5, 4, 7. RMAN> ALTER TABLESPACE sysaux OFFLINE IMMEDIATE; RMAN> RESTORE TABLESPACE sysaux; RMAN> RECOVER TABLESPACE sysaux; RMAN> ALTER TABLESPACE sysaux ONLINE; While evaluating the 12c beta3 I was not able to do the recover while testing "all pdb files lost". Cannot close the pdb as…
Question
Options
- A6, 5, 4, 7
- B10, 1, 2, 5, 8
- C10, 1, 2, 5, 4, 9, 8
- D10, 1, 5, 8, 10
How the community answered
(24 responses)- A58% (14)
- B8% (2)
- C21% (5)
- D13% (3)
Explanation
RMAN> ALTER TABLESPACE sysaux OFFLINE IMMEDIATE; RMAN> RESTORE TABLESPACE sysaux; RMAN> RECOVER TABLESPACE sysaux; RMAN> ALTER TABLESPACE sysaux ONLINE; While evaluating the 12c beta3 I was not able to do the recover while testing "all pdb files lost". Cannot close the pdb as the system datafile was missing... So only option to recover was: Shutdown cdb (10) startup mount; (1) restore pluggable database recover pluggable database alter database open; alter pluggable database name open; Oracle support says: You should be able to close the pdb and restore/recover the system tablespace of PDB. * Inconsistent backups are usually created by taking online database backups. You can also make an inconsistent backup by backing up data files while a database is closed, either: / Immediately after the crash of an Oracle instance (or, in an Oracle RAC configuration, all / After shutting down the database using SHUTDOWN ABORT Inconsistent backups are only useful if the database is in ARCHIVELOG mode and all archived redo logs created since the backup are available. *Open the database with theRESETLOGSoption after finishing recovery: SQL> ALTER DATABASE OPEN RESETLOGS;
Topics
Community Discussion
No community discussion yet for this question.