OACORE Services Starting in ADMIN Mode

OACORE Services Starting in ADMIN Mode

Problem Description:

The OACORE server log file showed the following error:

Failed to load webapp: /OA_HTML because of DeploymentException: java.lang.NullPointerException
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:397)

Due to this, OACORE remained stuck in ADMIN mode and the application was inaccessible via the web.

Root Cause:

This typically happens when:

✔️ JSP dependencies are broken or outdated.
✔️ OA Framework components were not properly compiled or deployed.
✔️ Missing or invalid compiled JSP files.

Fix (Step by Step):

1. Check EBS Dependencies

Run the Oracle-provided script to check all OA Framework and OACORE dependencies:

$FND_TOP/bin/txkrun.pl -script=ChkEBSDependecies -server=ALL_SERVERS

✔️ This will validate critical EBS component setups.

2. Compile JSP Files

Navigate to the patch directory and recompile all JSPs:

cd $FND_TOP/patch/115/bin
ojspCompile.pl --compile --flush

✔️ The --flush option clears old compiled JSPs before rebuilding.

3. Stop OACORE Managed Server

admanagedsrvctl.sh stop oacore_server1

4. Start OACORE Managed Server

admanagedsrvctl.sh start oacore_server1

✔️ After this, OACORE should start in RUNNING mode without errors.