Your database is running in archivelog mode and a nightly backup of the database, along
with an autobackup of the control file, is taken by using RMAN. Because of a media failure,
the SPFILE and the control files are lost.
Examine the steps to restore the SPFILE and the control file to mount the database:
1. Set D3ID of the target database in RMAN.
2.Start the database instance by using the startup force nomount command in RMAN.
3.Restore the control files from the backup.
4.Mount the database.
5.Restore the SPFILE from the autobackup.
6.Create a PFILE from the recovered SPFILE.
7.Restart the instance in nomount state.
Identify the required steps in the correct order.
A.
1, 2, 5, 3, 6, 4
B.
1, 2, 3, 5, 6, 4
C.
2, 1, 5, 7, 3, 4
D.
2, 1, 5, 6, 7, 4, 3
D really ? How can you mount the database without having the controlfiles first ??
someone please…
C seems like a better answer. You shouldn’t need step 6 in answer D if you have restored your spfile. There is no need to have a pfile if you have a restored and functioning spfile. In fact, step 6 in any answer presented seems extraneous.
I would go with C.
C
Seenagape PLEASE update the questions with the correct answers!!
A
http://docs.oracle.com/cd/B19306_01/backup.102/b14192/recov004.htm#CFAGFDJC
To restore the server parameter file:
If the database is up at the time of the loss of the SPFILE, connect to the target database. For example, run:
% rman TARGET /
If the database is not up when the SPFILE is lost, and you are not using a recovery catalog, then you must set the DBID of the target database. See “Determining your DBID” for details on determining your DBID.
Shut down the instance and restart it without mounting. When the SPFILE is not available, RMAN starts the instance with a dummy parameter file. For example:
RMAN> STARTUP FORCE NOMOUNT;
Restore the server parameter file
A appears to be correct.
https://docs.oracle.com/database/121/BRADV/rcmadvre.htm#BRADV85339
Well done Steve.
How can it be correct ?
If you lose the server parameter file, then RMAN can restore it to its default location or to a location of your choice. Unlike the loss of the control file, the loss of the server parameter file does not cause the instance to immediately stop. The instance may continue operating, although you must shut it down and restart it after restoring the server parameter file.
All the options seems off.
Can it be A?
After starting the database in force nomount, then restore spfile. You need to restart the database in nomount state and then restore the controlfile then mount the database.
If the question specified that no catalog was in use, then option A is probably better because you need to set the DBID.
Step 6 is not needed.
I am sticking to option C because it is the closet possible answer.
Regarding A, everything is fine but creating pfile from spfile? Thats a totally unnecessary step and for that reason I stick to Option C which wouldnt fail at any of the steps. You can startup nomount with dummy spfile, then restart again in nomount once spfile is restored, restore controlfiles and mount.
I think the answer is C because 7.Restart the instance in nomount state. needs to be done so that the restored SPFILE is read by the instance before its mounted
I agree with C as well since you have to have the database in NOMOUNT before you can even set the DBID which means A is not an option. From Oracle Docs:
If you want to restore the control file from autobackup, the database must be in a NOMOUNT state. You must first set the DBID for your database, and then use the RESTORE CONTROLFILE FROM AUTOBACKUP command:
RMAN> SET DBID 320066378;
RMAN> RUN {
SET CONTROLFILE AUTOBACKUP FORMAT
FOR DEVICE TYPE DISK TO ‘autobackup_format’;
RESTORE CONTROLFILE FROM AUTOBACKUP;
}
Actually I’m seeing that Oracle Docs example sets the DBID BEFORE the instance starts for restoring SPFiles, but for restoring controlfiles the instance is in NOMOUNT mode and then you set the DBID. This is a tricky question. A or C for sure…I’m almost leaning toward C now due to this example in Oracle Docs:
Restoring the Server Parameter File: Example
This example restores a lost server parameter file:
CONNECT TARGET / CATALOG rman/rman@catdb
SET DBID 676549873; # set dbid so rman knows the database name
STARTUP FORCE NOMOUNT # rman starts database with a dummy server parameter file
RESTORE SPFILE;
STARTUP FORCE; # needed so that RMAN restarts database with restored server parameter file
Not A : After spfile is restore, instance must be restart in nomount before able to restore control files
Answer is C
I always use steps like in C in practice, when we need to test cases where all files including SPFILE are lost.
So it should be C.
C is correct.
C is the best choice but not enough. After restore spfile we need to restart instance for it to using the newly restored spfile.
C