OC4J Startup Encountering Error "execve()" When Using JavaVM Startup Flag -D64
Last updated on OCTOBER 13, 2017
Applies to:Oracle Containers for J2EE - Version 184.108.40.206.0 to 10.1.3.5.0 [Release AS10g to AS10gR3]
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on SPARC (64-bit)
***Checked for relevance on 22-Feb-2013***
Sun Solaris SPARC (64-bit)Sun Solaris SPARC (32-bit)
Solaris Operating System (SPARC 64-bit)Solaris Operating System (SPARC 32-bit)
You are using the OC4J component of an Application Server release and have added "-d64" as a JVM command line flag via the "java-options" data element in the "start-parameters" for an OC4J instance. Your configuration file opmn.xml looks like:
id="java-options" value="-server -d64 -Djava.security.policy=$ORACLE_HOME/j2ee/OC4J_A1/config/java2.policy"
After modifying opmn.xml with the above, you have to ensure that the running OPMN process is updated with the new configuration. When running the command opmnctl reload to do so you find the OC4J instance you have configured no longer starts up successfully. The error reported is:
execve(): No such file or directory
Error trying to exec /u01/app/oracle/product/as10g/jdk/bin/sparcv9/java.
Check if file exists and permissions are set correctly.
Failed to start a 64-bit JVM process from a 32-bit JVM.
Verify all necessary J2SE components have been installed.
(Solaris SPARC 64-bit components must be installed after 32-bit components.)
It can be necessary to increase the level of logging for the OPMN. To do so follow this steps:
- For Application Server 10.1.3
The relevant OPMN log file is located at $ORACLE_HOME/opmn/logs/opmn.dbg. The logging level can be increased temporarily (until the next OPMN restart or reload) via the following dynamic approach:
$ opmnctl set target=debug comp="pm"
and the change can be validated using the "opmnctl query target=debug" command, which should return back to the command line the output "pm" as shown below:
$ opmnctl query target=debug
The logging level can be changed permanently by editing the configuration file $ORACLE_HOME/opmn/conf/opmn.xml and adding "pm" into the COMP attribute of the <debug> tag toward the top of that file:
<debug path="$ORACLE_HOME/opmn/logs/opmn.dbg" comp="pm" rotation-size="1500000" />
- For Application Server 9.0.4 and 10.1.2
The relevant OPMN log file is located at $ORACLE_HOME/opmn/logs/ipm.log. It is not possible to change the log level dynamically. It has to be changed by editing the configuration file $ORACLE_HOME/opmn/conf/opmn.xml, locating the <log-file> directive and increasing the "level" attribute from it's default of "4" to "9":
<log-file path="$ORACLE_HOME/opmn/logs/ons.log" level="9" rotation-size="1500000"/>
and then having issued "opmnctl reload" for OPMN to pickup the newly modified configuration.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms