APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.3 [Release 10.1 to 11.2]
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 11.2.0.4 [Release 11.2]
Information in this document applies to any platform.
***Checked for relevance on 10-Dec-2015***

GOAL

How to remove a Data Guard Configuration from the Primary Database after Standby Database is no longer present or activated to work as new/separate Primary (including the Steps for the Data Guard Broker).

In case you may want or need more about your current topic - please also access the Data Guard Community of Customers and Oracle Specialists directly via:
https://communities.oracle.com/portal/server.pt/community/high_availability_data_guard/302

SOLUTION

1. Put Primary Database in Maximum Performance Mode

On the Primary database, put the Database in Maximum Performance Mode (if not already):

or if using the Data Guard Broker:

2. Remove Data Guard Broker Configuration

If you are using the Data Guard Broker, remove the Data Guard Broker Configuration:

3. Unset Data Guard-specific Initialization Parameters

Unset/Remove following Initialization Parameters from the (S)PFILE of the Primary Database:

4. Drop Standby Redologs from the Primary Database

Use following Query to check for Standby Redolog Groups:

Use following Command to Drop the Standby Redo logs:

Drop all Standby Redolog Groups using above Command.

5. Drop the Data Guard Broker Configuration Files if used.

DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 Parameters define the Name and Location of the Data Guard Broker Configuration Files.