Re: Configure standby EBS 12.1.3 apps server to work with primary database in place

Posted by Mohammed Misbahuddin on Dec 16, 2019; 2:23pm
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/Configure-standby-EBS-12-1-3-apps-server-to-work-with-primary-database-in-place-tp7921p7925.html

Hi,
Thanks a lot for the prompt response....Yes, we kept the directory structure same on the second apps tier.....we have solaris 11 on m4000 server as our secondary apps server....so if we keep the hostname same as primary and start the services...will it work?...the IP address will be still different....

Our plan is to have a different hostname of the 2nd apps server...when the primary apps goes down....we will create application context and run autoconfig...and start the services......the users will be give a different shortcut to connect ..like APPSDR with the new URL …….

http://apps1.com.sa:8006  this will be our primary apps server EBS url….

http://appsdr1.com:8006 this will be our secondary apps server URL....

We want to follow the below step from the business continuity doc:

Step 3 Configuration of application tiers after standby database is enabled

Perform file-based configurations on standby application tiers

After the application tier software copies are complete, the file system configurations need to be updated to reflect the new environment. To do this on the application tiers, log onto each standby application tier system as the APPLMGR user and execute the following commands. Since your environment scripts are not yet set up, you will need to manually resolve the reference to and .
If the directory structure on standby is different than the primary then you need to run "perl adcfgclone.pl atTechStack" instead of adclonectx.
$ cd /clone/bin
$ perl adclonectx.pl /appl/admin/.xml


When the script is finished and the context file is created, execute the following commands, again resolving the reference to

$ cd APPL_TOP/ad/12.0.0/bin
$ perl adconfig.pl contextfile=$INST_TOP/appl/admin/.xml run=INSTE8
Answer the questions when prompted. This creates your environment files on the application tier. It tries to connect to the database, so some portions will fail, but the environment scripts should be created successfully. /LI>
Optionally, set up rsync for log and out files. If you wish to synchronize your concurrent manager log and out files from primary to the standby, first create directories matching matching to the APPLCSF environment variables in the appropriate place on the standby application tier server(s). For example:

$ mkdir -p /log
$ mkdir -p /out
Repeat this on the primary server, creating directories matching the standby context name, so as to be ready for a switchover operation. For UNIX systems, on the primary application tier(s), set up an rsync job in cron, to run every few minutes. This example synchronizes the log directory.
$ rsync av < APPLCSF>/log : /log --rsync-path=/usr/local/bin/rsync

----------------------------------------------------------------------------------------------
The only difference will be in our case we will not have standby db enabled....we will do the above steps connecting the primary db

Do you think the above idea is feasible ...will it work?