ORA-00333 ORA-27069 Incomplete read from log member | MRP0: Detected read corruption! Retry recovery once log is re-fetched | Allowing overwrite of partial archivelog (Doc ID 2207349.1)

Last updated on DECEMBER 04, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.

Symptoms

Standby was lagging behind and the below error seen in the standby alert log.

Error Description:

Sat Nov 05 09:43:12 2016
Archived Log entry 66103 added for thread 1 sequence 235331 ID 0xffffffff8725ea88 dest 1: =================> Log sequence 235331 added to dest_1
.......
Sat Nov 05 19:54:19 2016
Media Recovery Log /fcrmarch/archive_FCRM/FCRM10DB_1_235330_804249727.arc
Media Recovery Log /fcrmarch/archive_FCRM/FCRM10DB_1_235331_804249727.arc     ===================> MRP was trying to apply log 235331
Errors in file /oradumps/FCRM10DB/diag/diag/rdbms/fcrm10db_dr/FCRM10DB/trace/FCRM10DB_pr00_43647406.trc:
ORA-00333: redo log read error block 153600 count 2048                                                       ==========> Read error because cron job was deleting logs while trying to apply.
ORA-00334: archived log: '/fcrmarch/archive_FCRM/FCRM10DB_1_235331_804249727.arc'
ORA-27069: attempt to do I/O beyond the range of the file               ===========================> Expected error.
........
Incomplete read from log member '/fcrmarch/archive_FCRM/FCRM10DB_1_235331_804249727.arc'. Trying next member. =======> Incomplete read by MRP
Errors with log /fcrmarch/archive_FCRM/FCRM10DB_1_235331_804249727.arc
MRP0: Detected read corruption! Retry recovery once log is re-fetched...         =======> Error as expected, MRP will retry the recovery once log is re-fetched by FAL server.
Errors in file /oradumps/FCRM10DB/diag/diag/rdbms/fcrm10db_dr/FCRM10DB/trace/FCRM10DB_pr00_43647406.trc:
ORA-00333: redo log read error block 153600 count 2048
Recovery interrupted!
Sat Nov 05 19:54:31 2016
Recovered data files to a consistent state at change 11092573391510
.......
RFS[4]: Allowing overwrite of partial archivelog for thread 1 sequence 235331    =========> FAL was attempted and the log is re-fetched.
RFS[4]: Opened log for thread 1 sequence 235331 dbid -2143810049 branch 804249727
Sat Nov 05 19:54:51 2016
started logmerger process
Sat Nov 05 19:54:51 2016
.............
Sat Nov 05 20:06:34 2016
Media Recovery Log /fcrmarch/archive_FCRM/FCRM10DB_1_235331_804249727.arc    ==========> This time MRP applied this log successfully.

 

** So this process of (looping) deleting the logs by cron, then re-fetching by FAL and then re-applying was the root cause for apply lag in the standby.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms