Error finding "chmod" prevents JAM Agent initializing and registering with JAM Server Console when running in OPMN managed OC4J

(Doc ID 470796.1)

Last updated on APRIL 22, 2013

Applies to:

Enterprise Manager Base Platform - Version to [Release 10.2]
Information in this document applies to any platform.
This problem can occur on any platform.
***Checked for relevance on 22-Apr-2013***


You have completed the following tasks for the use of AD4J on a UNIX system:

However, the JAM Server Console does not automatically detect the JVM where the agent is deployed and does not list it under the console's Setup => JVMs screen, under the section "Show Registered JVMs".

In the relevant stdout log for the OC4J instance (located under $ORACLE_HOME/opmn/logs) you see errors similar to the following:

07/12/11 15:32:49 JAM Agent: jaminit.init()
07/12/11 15:32:49 JAM Agent: jaminit.init() Instantiating jamagent
07/12/11 15:32:49 JAM Agent loadNative() Unable to write to [/tmp/] chmod: not found
07/12/11 15:32:49 jamagent : Native load failed. Caused by the following exception
07/12/11 15:32:49 java.lang.UnsatisfiedLinkError: no jamagent in java.library.path
07/12/11 15:32:49 at java.lang.ClassLoader.loadLibrary(
07/12/11 15:32:49  at java.lang.Runtime.loadLibrary0(
07/12/11 15:32:49  at java.lang.System.loadLibrary(
07/12/11 15:32:49  at jamagent.jamagent.loadNativeDefault(
07/12/11 15:32:49  at jamagent.jamagent.<init>(
07/12/11 15:32:49  at jamagent.jaminit.init(


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