You use RMAN with a recovery catalog to back up your database. The backups and the
archived redo log files are backed up to media daily. Because of a media failure, the entire
database along with the recovery catalog database is lost. Examine the steps required to
recover the database: 1.Restore an autobackup of the server parameter file. 2.Restore the
control file. 3. Start up the database instance in nomount state. 4.Mount the database.
5.Restore the data files. 6.Open the database with the resetlogs option. 7.Recover the data
files. 8.Set D3ID for the database. Identify the required steps in the correct order.
A.
8, 3, 2, 4, 5, 7, 6
B.
8, 1, 3, 2, 4, 5, 6
C.
8, 1, 3, 2, 4, 5, 7, 6
D.
1, 8, 3, 2, 4, 5, 7, 6
E.
1, 3, 2, 4, 8, 5, 6, 7
C
How can you restore the autobackup spfile when the DB is in nomount mount .you will be alerted as below ,so the answer is A.
[oracle@rac1 ~]$ rman
Recovery Manager: Release 12.1.0.2.0 – Production on Wed Mar 16 04:08:41 2016
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
RMAN> connect target sys/dbAdm1ns123
connected to target database (not started)
RMAN> set dbid 4104776697;
executing command: SET DBID
RMAN> restore spfile FROM ‘/shared/backup/cdb12c/cont_CDB12C_c-4104776697-20160316-04.cont’;
Starting restore at 16-MAR-16
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/16/2016 04:08:54
RMAN-12010: automatic channel allocation initialization failed
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3640
Additional information: 285160267