Interesting ORA-00600 Bug during RMAN recovery

 

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of recover command at 07/06/2017 12:02:20

ORA-00283: recovery session canceled due to errors

RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile ‘+RECO_DAL/DWPREPRD/ARCHIVELOG/2017_07_06/thread_1_seq_85714.395.948615485’

ORA-00283: recovery session canceled due to errors

ORA-00600: internal error code, arguments: [3020], [219], [709377], [919261953], [], [], [], [], [], [], [], []

ORA-10567: Redo is inconsistent with data block (file# 219, block# 709377, file offset is 1516249088 bytes)

ORA-10564: tablespace ODS

ORA-01110: data file 219: ‘+DATA_DAL/DWPREPRD/DATAFILE/ods.501.948545309′

ORA-10560: block type ’58’

This is a known Oracle Bug where RMAN creates corrupted free blocks during recovery and causes related errors. There is no fix to this issue and work around is to use “blocks all” in RMAN backup script.

Note: For next execution, use below change in the rman backup script to take the backup:

backup as compressed backupset incremental level 0 database tag ‘edw_edwbkp’ plus archivelog tag ‘edw_edwbkp’ delete all input;

to:

backup blocks all as compressed backupset incremental level 0 database tag ‘edw_edwbkp’ plus archivelog tag ‘edw_edwbkp’ delete all input;

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s