Resolving ORA-752 or ORA-600  During Standby Recovery
(Doc ID 1265884.1)
Last updated on SEPTEMBER 25, 2018
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 22.214.171.124 [Release 10.2 to 11.2] Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 12.1] Information in this document applies to any platform.
Standby Redo Apply can terminate due to a failure of redo-data consistency checks, a problem called stuck recovery. Stuck recovery can occur when an underlying operating system or storage system loses a write issued by the Primary or Standby database during normal operation. Because there is an inconsistency between the information stored in the redo and the information stored in a database block being recovered, the database signals an internal error when applying the redo.
ORA-00600: internal error code, arguments: , , , ,, , ,  ORA-10567: Redo is inconsistent with data block (file# 1, block# 419819) ORA-10564: tablespace USER1 ORA-01110: data file ’/oracle/datafiles/user1.dbf’
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!