Agent Messages

NMS-00301 to NMS-00350: Agent Operation Messages

NMS-00302: Failed to initialize user queue.

Cause: The agent was unable to initialize the file which holds data about users. Following messages may provide more details.

Action: If a solution cannot be found, call Worldwide Customer Support with the circumstances and complete set of messages leading to the error.

NMS-00303: Failed to initialize event registration queue.

Cause: The agent was unable to initialize the file which holds data about event registrations. Following messages may provide more details.

Action: If a solution cannot be found, call Worldwide Customer Support with the circumstances and complete set of messages leading to the error.

NMS-00304: Failed to initialize job queue.

Cause: The agent was unable to initialize the file which holds data about jobs. Following messages may provide more details.

Action: If a solution cannot be found, call Worldwide Customer Support with the circumstances and complete set of messages leading to the error.

NMS-00305: Failed to initialize event occurrence queue.

Cause: The agent was unable to initialize the file which holds data about event occurrences. Following messages may provide more details.

Action: If a solution cannot be found, call Worldwide Customer Support with the circumstances and complete set of messages leading to the error.

NMS-00306: Failed to initialize job status queue.

Cause: The agent was unable to initialize the file which holds data about job statuses. Following messages may provide more details.

Action: If a solution cannot be found, call Worldwide Customer Support with the circumstances and complete set of messages leading to the error.

NMS-00307: Failed to initialize RPC layer.

Cause: The Remote Procedure Call layer could not be initialized. Following messages may provide more details.

Action: If a solution cannot be found, call Worldwide Customer Support with the circumstances and complete set of messages leading to the error.

NMS-00308: Failed to listen on address: another agent may be running

Cause: The agent's connection cache could not be initialized. This message usually appears when another agent is running. Only one copy can be running at a time.

Action: If another agent is running, bring it down before running the desired agent.

NMS-00309: Failed to initialize internal address.

Cause: The agent's address for internal RPC's could not be initialized. This may be because another copy of the agent is already running.

Action: If another copy of the agent is already running, kill both agents and try again.

NMS-00310: Failed to initialize auxiliary address.

Cause: The agent's address for file transfer RPC's could not be initialized. This may be because another copy of the agent is already running.

Action: If another copy of the agent is already running, kill both agents and try again.

NMS-00311: Failed to initialize language ID.

Cause: The language ID of the agent could not be initialized.

Action: Make sure the language ID environment variable is correct for the agent.

NMS-00312: Error opening file filename.

Cause: The agent was unable to open the specified file.

Action: Make sure that the directory exists, and that the agent has the required permissions to write to it.

NMS-00313: Unable to access directory name.

Cause: The agent was unable to access the specified directory, or the directory does not exist.

Action: Make sure that the directory exists, and that the agent has the required permissions to write to it.

NMS-00314: dbsnmp.spawnaddress parameter in snmp.ora missing.

Cause: The dbsnmp.spawnaddress parameter is required from 7.3.2.1 and later releases. This must be a different address from the dbsnmp.address and is used for file transfer and Oracle Software Manager.

Cause: Add the dbsnmp.spawnaddress parameter to snmp.ora.

NMS-00315: Failed to create tcl package index.

Cause: The tcl package index could not be created.

Action: Make sure all the shared libraries in the $ORACLE_HOME/network/agent/library directory are correct.

NMS-00316: Failed to initialize init.tcl.

Cause: The tcl7.5 init.tcl file could not be initialized.

Action: Make sure you have a correct version of init.tcl in $ORACLE_HOME/network/agent/tcl.