Resolving ORA-00752 or ORA-600 [3020] During Standby Recovery
(Doc ID 1265884.1)
Last updated on DECEMBER 17, 2024
Applies to:
Oracle Database Exadata Express Cloud Service - Version N/A and later Oracle Cloud Infrastructure - Database Service - Version N/A and later Oracle Database Backup Service - Version N/A and later Oracle Database Cloud Exadata Service - Version N/A and later Oracle Database Cloud Service - Version N/A and later Information in this document applies to any platform.
Symptoms
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.
To detect lost write and corruptions, Oracle recommends setting DB_LOST_WRITE_PROTECT=TYPICAL for your primary and standby database systems. For comprehensive data protection guidance, refer to Best Practices for Corruption Detection, Prevention, and Automatic Repair - in a Data Guard Configuration (Doc ID 1302539.1) For best practices for addressing database logical corruptions, refer to Resolving Logical Block Corruption Errors in a Physical Standby Database (Doc ID 2821699.1)
Cause
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
