RMAN Recovery Scenarios

Comments
-
Hi Santosh, firstly great article!
On the block recovery an easier way perhaps is to use the blockrecover corruption list
i.e.:
SQL> select * from v$database_block_corruption;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
---------- ---------- ---------- ------------------ ---------
5 12 1 0 CORRUPT
5 3068 2 0 CORRUPTRMAN> run
2> {
3> blockrecover corruption list;
4> }....
Post recovery looking at the view corruption still shows?SQL> select * from v$database_block_corruption;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
---------- ---------- ---------- ------------------ ---------
5 12 1 0 CORRUPT
5 3068 2 0 CORRUPTSo try backup validate…..
RMAN> BACKUP VALIDATE DATABASE;
SQL> select * from v$recover_file;no rows selected
SQL> select * from v$database_block_corruption;
no rows selected
Verfiy file is ok
DBVERIFY - Verification starting : FILE = /u02/oradata/crashdb/example01.dbf
DBVERIFY - Verification completeTotal Pages Examined : 19200
Total Pages Processed (Data) : 8838
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 1279
Total Pages Failing (Index): 0
Total Pages Processed (Other): 7368
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 1715
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
Highest block SCN : 763674 (0.763674)0