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

Posted by ErmanArslansOracleBlog on Dec 17, 2019; 1:01pm
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-tp7921p7929.html

if you execute "exec fnd_conc_clone.setup_clean; ", then you will need to run autoconfig on database tier as well!

So ensure what you are doing. Test it carefully.
You may try going with executing  "exec fnd_conc_clone.setup_clean; ".. Test it and verify it.
or , include db tier autoconfig to your action list as well..

Again, dont run these command while your primary env is up and running.. This kinds of a customized action plan is only applicable for your customized failover scenario (during a custom failover that you described.)

And why  -> "without passing the context file name and start the services..."?

Just implement the synthesis of the apps tier specific actions that are documented in  1277556.1 and 751328.1. I mean a union set of the the apps tier specific actions that are documented in  1277556.1 and 751328.1 .. Ofcourse in the correct order..

In your secondary app env (to make it be the primary app env, with the original primary db)->

*Deregister the current Applications server "perl $AD_TOP/bin/adgentns.pl ......remove" --> for your apps host
*Remove "Run FND_NET_SERVICES.remove_server('<SID>', '<hostname>');" --> for your apps host
*Create a new apps tier Context file
*Shutdown the Application Tier Services (already shutdown in your case)
*Change the server machine hostname. (already different in your case)
*Run autuconfig on apps tier
*Start the Applicataion Tier Services