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 recover the tablespace are as follows:
1. Mount the CDB.
2. Close all the PDBs.
3. Open the database.
4. Apply the archive redo logs.
5. Restore the data file.
6. Take the SYSAUX tablespace offline.
7. Place the SYSAUX tablespace online.
8. Open all the PDBs with RESETLOGS.
9. Open the database with RESETLOGS.
10. Execute the command SHUTDOWN ABORT.
Which option identifies the correct sequence to recover the SYSAUX tablespace?
A.
6, 5, 4, 7
B.
10, 1, 2, 5, 8
C.
10, 1, 2, 5, 4, 9, 8
D.
10, 1, 5, 8, 10
Explanation:
RMAN> ALTER TABLESPACE sysaux OFFLINE IMMEDIATE;
RMAN> RESTORE TABLESPACE sysaux;
RMAN> RECOVER TABLESPACE sysaux;
RMAN> ALTER TABLESPACE sysaux ONLINE;
* Example:
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
instances)
/ 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 the RESETLOGS option after finishing recovery:
SQL> ALTER DATABASE OPEN RESETLOGS;
A