My Oracle Support Banner

ORA-3113 Starting Primary Database after removing Data Guard Configuration (Doc ID 260819.1)

Last updated on OCTOBER 15, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 9.0.1.0 to 11.2.0.2 [Release 9.0.1 to 11.2]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - 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

After removing all Data Guard related parameters from the init.ora or spfile.ora, attempting to start the database as a non-Data Guard Database fails.

The database will mount correctly, but opening results in an ORA-3113.


Alert.log shows an error similar to the following:
~~~

Thu Aug 9 10:53:55 2001
LGWR: Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR
LGWR: Minimum of 1 synchronous standby database required
Thu Aug 9 10:53:55 2001
Errors in file /<path>/<oracle_sid>_lgwr_4024.trc:
ORA-16072: a minimum of one standby database destination is required
LGWR: terminating instance due to error 16072
Instance terminated by LGWR, pid = 4024



The trace file associated with the alert.log error looks similar to this:
~~~

*** SESSION ID:(3.1) 2004-01-07 11:47:21.321
Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR
Standby database verification failed:16072
error 16072 detected in background process
ORA-16072: a minimum of one standby database destination is required


Changes

Data Guard Protection Mode is still set set to 'Maximum Availability' or even 'Maximum Protection', but the Standby Database has been removed

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!


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