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 offline.
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:
* 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 databsae
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.
* Open the database with the RESETLOGS option after finishing recovery:
SQL> ALTER DATABASE OPEN RESETLOGS;
The Answer should be – A (6,5,4,7)
To recover Sysaux tablespace, you just need to take the tablespace offline, restore, apply archives, recover and make it online.
Answer should be A
A:
RMAN> ALTER TABLESPACE sysaux OFFLINE IMMEDIATE;
RMAN> RESTORE TABLESPACE sysaux;
RMAN> RECOVER TABLESPACE sysaux;
RMAN> ALTER TABLESPACE sysaux ONLINE;
A is right but step 7 does not say put it back online! It says out it offline!!!
Sorry,
A is right but step 7 does not say put it back online! It says put it offline!!!
A because it works. B,C,D is something ner nonsense. So POE (process of elimnation) is very open helpful!
have fun
I think that non of the provided answers are good.
First of all, after the corruption of the SYSAUX tablespace the Oracle instance will be terminated, so no need for putting the SYSAUX tablespace offline or issue SHUTDOWN ABORT.
After that we have to start in mount mode the Oracle instance, connect to RMAN and issue the following statements:
1. restore tablespace sysaux;
2. recover tablespace sysaux;
3. alter database open;
In conclusion, I don’t see any correct answers to this question. I also tested.
A
Demonstration:
http://blog.itpub.net/28552278/viewspace-1250092/
A because SYSAUX is not a system critical tablespace as “system” or “undo”
A
However step 7 says “Place the SYSAUX tablespace ***offline***”, it should be ‘online’. I suppose it’s a typo
A