Increasing Number of JVMs Allocated to oacore Process Causes Login Problems
Last updated on AUGUST 08, 2016
Applies to:Oracle Applications Technology Stack - Version 12.0 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.
This issue is currently known to affect Release 12 installations running OracleAS 10.1.3.0 on any platform, and Release 12 installations running OracleAS 10.1.3.3 or 10.1.3.4 on the HP-UX (PA-RISC 64) platform only. The solution is different for each of these scenarios.
Checked for relevance on 14-DEC-2013
If you see the same behavior in any other circumstances, there is probably a different cause. In such a case, the fixes listed here are unlikely to work and should not be attempted.
You decide to increase the number of JVMs allocated to the oacore process, by amending the s_oacore_nprocs context variable to a value greater than 1. Subsequently, you observe a problem rendering the E-Business Suite login page, and are left with the browser displaying an HTTP 404 Not Found error.
This has been shown to manifest itself immediately after s_oacore_nprocs is increased from the default value of 1, AutoConfig is run, and the application tier processes are restarted.
As a workaround, you can issue the following sequence of commands to enable the login page to appear:
$ adopmnctl.sh stop
$ adopmnctl.sh start
However, the next time AutoConfig is run (with s_oacore_nprocs set to > 1), the problem will recur.
The number of JVMs allocated for the oacore process is increased from the default value of 1 by editing the s_oacore_nprocs context variable in the AutoConfig section of Oracle Applications Manager.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms