Pages

Wednesday, July 3, 2019

RECOVERY SCENARIO: Complete loss of all database files including SPFILE using RMAN

RECOVERY SCENARIO: Complete loss of all database files including SPFILE using RMAN 

Database Details
------------------

Database Name=OPSDBA
Machine Name=ITLINUXDEVBLADE07
DBID=1499754868 (select dbid from v$database)

SIMULATING CRASH
------------------------

opsdba:/u01/ORACLE/opsdba>ls -l
total 1948980
drwxr-x---    2 oracle  dba          4096 Feb 12 13:35 arch
-rw-r-----    1 oracle   dba       7389184 Feb 12 13:57 control01.ctl
-rw-r-----    1 oracle   dba       7389184 Feb 12 13:57 control02.ctl
-rw-r-----    1 oracle   dba       7389184 Feb 12 13:57 control03.ctl
-rw-r-----    1 oracle   dba      104865792 Feb 12 13:57 drtbs1.dbf
-rw-r-----    1 oracle   dba      104865792 Feb 12 13:57 drtbs2.dbf
drwxr-xr-x    2 oracle  dba          4096 Feb 12 13:55 recovery
-rw-r-----    1 oracle   dba      52429312 Feb 12 13:34 redo01.log
-rw-r-----    1 oracle   dba      52429312 Feb 12 13:35 redo02.log
-rw-r-----    1 oracle   dba      52429312 Feb 12 13:57 redo03.log
-rw-r-----    1 oracle   dba      367009792 Feb 12 13:57 sysaux01.dbf
-rw-r-----    1 oracle   dba      513810432 Feb 12 13:57 system01.dbf
-rw-r-----    1 oracle   dba      20979712 Jan 30 12:32 temp01.dbf
-rw-r-----    1 oracle   dba       5251072 Feb 12 13:57 undonew.dbf
-rw-r-----    1 oracle   dba      634396672 Feb 12 13:57 undotbs01.dbf
-rw-r-----    1 oracle   dba      31465472 Feb 12 13:57 users01.dbf
-rw-r-----    1 oracle   dba      10493952 Feb 12 13:57 users02.dbf
-rw-r-----    1 oracle   dba      10493952 Feb 12 13:57 users03.dbf
-rw-r-----    1 oracle   dba      10493952 Feb 12 13:57 users04.dbf
-rw-r-----    1 oracle   dba      10493952 Feb 12 13:57 users05.dbf
-rw-r-----    1 oracle   dba       5251072 Feb 12 13:57 users06.dbf
-rw-r-----    1 oracle   dba       5251072 Feb 12 13:57 users07.dbf
opsdba:/u01/ORACLE/opsdba>rm *.dbf
                                                                                                                                *FILES REMOVED
opsdba:/u01/ORACLE/opsdba>ls -l *.dbf
ls: *.dbf: No such file or directory

opsdba:/opt/oracle/product10gpr2/dbs>mv spfileopsdba.ora spfileopsdba.org
opsdba:/opt/oracle/product10gpr2/dbs>ls -lt spfile*   *SPFILE REMOVED
-rw-r-----    1 oracle   dba          2560 Feb 12 13:06 spfileopsdba.org
-rw-r-----    1 oracle   dba          2560 Jan 23 11:32 spfilerman10d.ora
-rw-r-----    1 oracle   dba          4608 Dec 18 09:28 spfileerpmig.ora
-rw-r-----    1 oracle   dba          3584 Nov 21 08:22 spfileprimary.ora
-rw-r-----    1 oracle   dba          3584 Oct 22 14:32 spfilebozo.ora
-rw-r-----    1 oracle   dba          4608 Oct  8 15:24 spfilestreams2.ora
-rw-r-----    1 oracle   dba          2560 Oct  1 11:46 spfilevaultdb.ora

THE FOLLOWING STEPS WILL OUTLINE THE RECOVERY PROCESS:

Step 1:   RECOVERY OF SPFILE

Create spfile.rcv as:
set dbid= 1499754868
run {
startup nomount force  ;
 };

opsdba:/u01/ORACLE/opsdba/recovery>rman target / catalog rman10/rman10@rman10p cmdfile=spfile.rcv

Recovery Manager: Release 10.2.0.2.0 - Production on Mon Feb 12 14:02:26 2007

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

connected to target database (not started)
connected to recovery catalog database

RMAN>
executing command: SET DBID
database name is "OPSDBA" and DBID is 1499754868

Oracle instance started

Total System Global Area     264241152 bytes

Fixed Size                     2070416 bytes
Variable Size                113248368 bytes
Database Buffers             142606336 bytes
Redo Buffers                   6316032 bytes

Recovery Manager complete.
opsdba:/u01/ORACLE/opsdba/recovery>

Now restore the spfile

set dbid=1499754868
run {
allocate channel ch1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opsdbad.opt)';
restore spfile ;
release channel ch1 ;
}

Step 2:   RESTORE OF CONTROLFILES

Same Steps as spfile with the restore command changed. So the new script is

set dbid=1499754868
run {
allocate channel ch1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opsdbad.opt)';
restore controlfile ;
release channel ch1 ;
}

Step 3:   RESTORE OF DATABASE

Since you have the controlfiles now mount the database

SQL> conn sys as sysdba
Enter password:
Connected.
SQL> alter database mount;

Database altered.

Now get the log sequence number of the database from the catalog database:

select sequence# from rc_backup_redolog where db_name=’OPSDBA’;

RMAN> run {
2> allocate channel ch1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opsdbad.opt)';
3> restore database ;
4> recover database until logseq=6;                                -- GOT FROM THE ABOVE QUERY
5> release channel ch1 ;
6> }
7>
allocated channel: ch1
channel ch1: sid=156 devtype=SBT_TAPE
channel ch1: Data Protection for Oracle: version 5.2.4.0

Starting restore at 12-FEB-07

channel ch1: starting datafile backupset restore
channel ch1: specifying datafile(s) to restore from backup set

Step 4:   alter database open resetlogs;


No comments:

Post a Comment