Friday, September 2, 2011

ORA-19566 Corruption Preventing RMAN Backup

File corruption is a regular problem DBA's come across.  It could be corruption of the redo log or controlfile that prevents the database from opening.  Or a corruption in a datafile that is affecting queries of certain data blocks or preventing RMAN from taking a backup.  These issues can easily be overcome with a good backup solution using RMAN.  If you do not have a valid backup without the offending corruption, you could have a serious problem on your hands. 

If you are just now trying to implement an RMAN backup solution and your backups are failing with

ORA-19566: exceeded limit of 0 corrupt blocks for file

... we at least have the option of skipping the corrupted blocks so the backups can complete successfully

Using SET MAXCORRUPT will allow RMAN to skip up to a specified number of corrupted blocks in a datafile without aborting the backup.

Syntax  :  set maxcorrupt for datafile <dataFileSpec> TO <integer>

Example: RMAN>  run {  set maxcorrupt for datafile 'C:\oracle\oradata\Users01.dbf' to 3;
                                          backup  database;
                                       }

This will get back on track (or started) with RMAN backups. 

Want to avoid these problems in the future?  Want to prevent them from happening in the first place?  Let an experienced Oracle DBA create and maintain a reliable RMAN backup solution for you without having to pay exorbonant rates/salary.  Feel free to contact me to inquire about my services or other questions you may have.

No comments:

Post a Comment