You are on page 1of 3

CR00048494 recover corrupted blocks in tip02a database

RMAN> recover corruption list;


Starting recover at 07-AUG-14
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=5 instance=tip02a2 device type=DISK
finished standby search, restored 37 blocks
starting media recovery
media recovery complete, elapsed time: 00:00:03
Finished recover at 07-AUG-14
==========================================================
Some note::
Best Practices for Corruption Detection, Prevention, and Automatic Repair - in a
Data Guard Configuration (Doc ID 1302539.1) --- GOOD ONE TO CHECK
New Rman Blockrecover command in 11g (Recover corruption list) (Doc ID 1390759.1
)
Quick guide RMAN corrupt block recover steps (Doc ID 1428823.1)
RMAN Tips, Tricks and Pitfalls (Doc ID 1462118.1)
RMAN : Block-Level Media Recovery - Concept & Example (Doc ID 144911.1)
ORA-10588 with RECOVER DATABASE...ALLOW n CORRUPTION (Doc ID 1354344.1)
Recovering data after extensive loss or corruption of data sent to target node.
(Doc ID 1319045.1)
FAQ: Physical Corruption (Doc ID 403747.1) --- GOOD ONE TO CHECK TOOO
Use RMAN to format corrupt data block which is not part of any object (Doc ID 14
59778.1)
NOTE:336133.1 - How to Format Corrupted Block Not Part of Any Segment
NOTE:1088018.1 - Master Note for Handling Oracle Database Corruption Issues
NOTE:798844.1 - Why is RMAN not using Unused Block Compression during backup?
V$BACKUP_CORRUPTION Contains Information About Corrupt Blocks (Doc ID 209691.1)
How to Recover from ORA-01171 ORA-01122 ORA-01110 ORA-01251 (Doc ID 333620.1)
SMON: ABOUT TO RECOVER UNDO SEGMENT %s messages in alert log (Doc ID 266159.1)
NOTE:396863.1 - How to Keep All UNDO Segments from Being Offlined in Oracle 10g
- Fast Ramp-Up
Potential disk corruption when adding a node to a cluster (Doc ID 754594.1)
ABMR: How to test Automatic Block Recover Feature (Doc ID 1266059.1)

You might also like