Dec 5, 2013

when standby DB not in synch due to ORA-00333/00334/27069 ( Incomplete read from log member )- solution

-- Troubleshoot standby  ORA-00333/00334/27069 issue

-- When archive logs are not applying ( scenario based)
-- Applied in Oracle 11gR2 ( applicable to Oracle 10g onwards)
-- observed standby DB some times out of synch due to following error

Error Message: ( from alert log)

Errors in file /u03/app/oracle/diag/rdbms/PROD/PROD/trace/PROD_pr00_10867.trc:
ORA-00333: redo log read error block 30720 count 2048
ORA-00334: archived log: '/u03/ARCBKP/1_918_829075801.dbf'
ORA-27069: attempt to do I/O beyond the range of the file
Additional information: 30720
Additional information: 2048
Additional information: 32320
Incomplete read from log member '/u03/ARCBKP/1_918_829075801.dbf'. Trying next member.
Errors with log /u03/ARCBKP/1_918_829075801.dbf
MRP0: Detected read corruption! Retry recovery once log is re-fetched...


Don't disturb recovery mode. If down, then bring the DB into recovery managed mode again. Register the archive log(s) which is/are not recovered.

SQL> alter database register logfile '/u03/ARCBKP/1_918_829075801.dbf';

Sure recover will be started.
Sure archive logs will start applying if cataloged already.

No comments:

Post a Comment

Translate >>