steps that need to perform during any application upgrade activities for disabling data guard

Below mentioned are the steps that need to perform during any application upgrade activities for disabling data guard and archive log mode at same time.

We need to execute all below steps on primary server only.

Take backup of primary archive log files with backup script threshold set to Zero.

Take backup of spfile/pfile, sqlnet.ora, listener.ora and tnsnames.ora files.

Take backup of /oracle/DB1/112_64/dbs/dr1DB1_ P.dat and /oracle/DB1/112_64/dbs/dr2DB1_ P.dat  files.  (DG broker config files backup.)

Put the DB in mount mode and execute below commands to disable broker and data guard.

SHUT IMMEDIATE;

STARTUP MOUNT;

                  ## Disable Broker ##

ALTER SYSTEM SET DG_BROKER_START=FALSE SCOPE=BOTH;

ALTER SYSTEM SET dg_broker_config_file1=’’  SCOPE=BOTH;

ALTER SYSTEM SET dg_broker_config_file2=’’  SCOPE=BOTH;

                 ## Disable Data Guard ##

ALTER SYSTEM SET LOG_ARCHIVE_CONFIG=’’ SCOPE=BOTH;

ALTER SYSTEM SET LOG_ARCHIVE_DEST_2=’’ SCOPE=BOTH;

ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=’DEFER’ SCOPE=BOTH;

ALTER SYSTEM SET standby_file_management=MANUAL SCOPE=BOTH;

ALTER SYSTEM SET FAL_SERVER=’’ SCOPE=BOTH;

ALTER SYTEM SET LOG_FILE_NAME_CONVERT=’’ SCOPE=BOTH; 

              ## Disable Force logging and Flash back ##

ALTER DATABASE NO FORCE LOGGING;

ALTER DATABASE FLASHBACK OFF;

             ## Disable archive log mode ##

ALTER DATABASE NOARCHIVELOG;

            ## Bounce the database ##

SHUT IMMEDIATE;

STARTUP;

CREATE PFILE FROM SPFILE;

Verify above changes are in effect and data guard is disabled.

Disable below script on primary server.

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; - RMAN configuration to change archive deletion policy without data guard. To be executed on primary.

Do not terminate DR server. 

Login to DR SERVER and then stop redo apply and bring down DB1 DR instance and listener. 

 ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;