My Oracle Support Banner

Resolving ORA-00752 or ORA-600 [3020] During Standby Recovery (Doc ID 1265884.1)

Last updated on JANUARY 22, 2024

Applies to:

Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 19.3.0.0.0 [Release 12.1 to 19]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express 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)

Changes

 

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!


In this Document
Symptoms
Changes
Cause
Solution
 Determining Root Cause
 PRIMARY DATABASE LOST WRITES: ORA-00752 or ORA-00600 [3020] without KCOX FUTURE message
 Primary Lost Write Option 1: Determine if affected objects can be recreated and recovery allowed to continue:
 STANDBY DATABASE LOST WRITES: ORA-753 or ORA-00600 [3020] with KCOX FUTURE message
 Standby Lost Write Repair Option 1
 Stop Managed Recovery
 Stop Standby Database and Start Mounted Mode 
 Restore Datafile from Primary Database Service
  Restart the Standby Database
 Enable Managed Recovery 
 Standby Lost Write Repair Option 2
 Protecting Against Lost Writes
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.