12.2 E-Business Suite Applications Technology Stack Oacore and OAFM Servers Do Not Restart And Are Stuck at State-Admin After Aborting ADOP Session And Restarting The Database / Applications Tiers

During an in progress ADOP patch session applying AD/TXK patch, users reported issues with login attempts to the E-Business Suite instance.

To resolve the login issues, the ADOP patch session was aborted and the DB / Applications were restarted.

After the restart the database started correctly, but the applications restart failed for oacore and oafm servers at state-admin with the following errors:

Current status of this issue:
Stopped all the services and rebooted the node.
performed the DB Bounce using srvctl ..
Then restarted the applications services using adstrtal.sh script from ADMIN_SCRIPTS_HOME @08:07 server time..

2 out of 4 oacore managed servers got started whereas remaining 2 oacore and oafm_server managed servers are in starting mode still.

$ tail $EBS_DOMAIN_HOME/servers/oafm_server1/logs/oafm_server1.log

 

#### <oafm_server1> <[ACTIVE] ExecuteThread: ‘1’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <> <> <0000LoIecgeC^q8_Rhp2id1PNDTk000003>
#### <oafm_server1> <[ACTIVE] ExecuteThread: ‘1’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <> <> <0000LoIecgeC^q8_Rhp2id1PNDTk000003>
#### <oafm_server1> <[ACTIVE] ExecuteThread: ‘1’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <> <> <0000LoIecgeC^q8_Rhp2id1PNDTk000003>
#### <oafm_server1> <[ACTIVE] ExecuteThread: ‘1’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <> <> <0000LoIecgeC^q8_Rhp2id1PNDTk000003>

The below exception also appears multiple times in the oacore_server1.out:

Exception in static block of jtf.cache.CacheManager. Stack trace is: java.lang.NoClassDefFoundError: Could not initialize class oracle.apps.fnd.common.PoolException

 

CAUSE

The cause has been documented as a mis-configuration  ter the following unpublished defects:

Bug 21383809 : APPS LOCAL LOGIN IS GIVING ERROR 404 AND OACORE DEPLOYMENT IN FAILED STATE

Bug 21384732 : APPS LOCAL LOGIN IS GIVING ERROR 404 AND OACORE DEPLOYMENT IN FAILED STATE

 

SOLUTION

To resolve the issue test the following steps in a development instance and then migrate accordingly:

  1. Shutdown all processes on all tiers.
  2. Run autoconfig per section ‘Using AutoConfig Tools for System Configuration’ in the following document:

https://docs.oracle.com/cd/E26401_01/doc.122/e22953/T174296T589913.htm#6237534

  1. Restart the DB / application tier processes and confirm whether users are now able to login successfully.

 

Reference : (Doc ID 2285759.1)

 

Recent Posts