DOYENSYS Knowledge Portal




We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal




Tuesday, April 4, 2017

R12.2 Handling Standby Database and Application after applying patch using ADOP

Steps to do, after applying patches through ADOP (Not Hotpatch) if you have a standby environment
Put the Standby database into Snapshot Standby mode.

Convert the Standby to a Snapshot Standby

alter system set db_recovery_file_dest_size=100g scope=both;
alter system set db_recovery_file_dest='/s01/flash_recovery_area' scope=both;
alter system set db_flashback_retention_target=1440 scope=both;


Stop redo apply on the physical standby database

alter database recover managed standby database cancel;

Turn on flashback logging:

alter database flashback on;

Convert the standby database into a snapshot standby database:

alter database convert to snapshot standby;

Shut down the snapshot standby database and startup the database (it will be opened for read/write access):

shutdown immediate;
startup

Remove the applications configuration.

$ sqlplus apps/
exec fnd_conc_clone.setup_clean;
exec ad_zd_fixer.clear_valid_nodes_info;
Commit;

Run AutoConfig on the database tier.

 $ORACLE_HOME/appsutil/scripts//adautocfg.sh

Run AutoConfig on application tiers

Apply the patches to the Standby using hotpatch mode with nodatabaseportion option

Flip the file system on the Standby application tiers to be the same as the Primary

$ perl $AD_TOP/patch/115/bin/txkADOPCutOverPhaseCtrlScript.pl -action=ctxupdate -contextfile= -patchcontextfile= -outdir=


Apply the patches using hotpatch in the order that they were applied on the Primary

adop phase=apply patches= apply_mode=hotpatch options=nodatabaseportion



Reconfigure the standby database file systems (optional)

Source the Oracle Applications environmen tand run the following command to create the file appsutil.zip in /admin/out

perl /bin/admkappsutil.pl

Copy appsutil.zip to the database servers and uncompress appsutil.zip under the 

$ cd
$ unzip -o appsutil.zip

As the ORACLE user on the standby database server, first stop the listener if it is running, then use the cloning toolkit to define the database tier topology at the standby site - Answer the questions when prompted.

$ lsnrctl stop
$ cd < RDBMS_ORACLE_HOME>/appsutil/clone/bin
$ perl adcfgclone.pl dbTechStack

The step above starts the database listener for the primary services. You need to stop and restart it for the standby services:

$ lsnrctl stop
$ lsnrctl start < standby service name>

รจ Patching on Standby environment is completed.
Revert the Physical Standby Database Back to its Original State

startup mount force;
alter database convert to physical standby;
shutdown immediate;
startup nomount;
alter database mount standby database;

alter database recover managed standby database using current logfile disconnect;


No comments: