Recover_DB_in_NOARCHIVELOG

6.1 Recovering a Database  in NOARCHIVELOG mode
6.1.1 Backup db  using RMAN and create the recovery case

SQL> startup mount
SQL> alter database NOARCHIVELOG;
RMAN> backup database  tag ‘DB1DUP_NOARCHIVELOG’ ;
% asmcmd  rm   ‘BIG_DATA/db1dup/datafile/*’;

6.1.2 Potential Error

SQL> alter database open
ERROR at line 1:
ORA-01157: cannot identify/lock data file 1 – see DBWR trace file
ORA-01110: data file 1: ‘+BIG_DATA/db1dup/datafile/system.263.807297175’

6.1.3 Recover database in NOARCHIVELOG mode
6.1.3.1 List our backup set

%  rman target=/
RMAN> list backup tag DB1DUP_NOARCHIVELOG;

Full list of all backupsets !

6.1.3.2 Restore and Recover database

RMAN> restore database
–> Check recovery
RMAN> recover database noredo preview
starting media recovery
media recovery complete, elapsed time: 00:00:24
Finished recover at 13-FEB-13 16:47:21
–> Run  recovery
RMAN> recover database noredo
Finished recover at 13-FEB-13 16:48:37
–> Open database
RMAN>  sql ‘alter database open’

Full output from used Recovery commands !

6.1.4 Lessons learned in this session

• Always do a clean shutdown before backing up your database !
• We get 2 backup sets as we have configured 2 disk channels by running:  
  CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
• Recover your database with NOREDO keyword as we don’t have to apply any Redo
• RMAN doesn’t backup any temp files
• Use the preview command to check whether recover goes through:
  Recover database noredo preview: