Release 9.2.0
Part Number A96671-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle Enterprise Manager Messages Manual Release 9.2.0 Part Number A96671-01 |
|
Cause: The agent was unable to access the job data from the job queue file.
Action: Contact Oracle Support Services.
Cause: The agent was unable to access one of the following files: job queue, job status, job output, job input parameter file, or job script file.
Action: Make sure the Agent has been properly installed. Refer to the Oracle Intelligent Agent User's Guide for information on how to verify the agent installation. Verify none of the agent files have been edited nor additional directories created under $ORACLE_HOME/network/agent.
Cause: The agent was unable to allocate the required memory to accomplish the job.
Action: Contact Oracle Support Services.
Cause: The agent was unable to locate the specified job id. This can happen if the Oracle Management Server repository is out of sync with the agent's queue files.
Action: Contact Oracle Support Services.
Cause: The agent was unable to locate the script required to run the job. This can happen if the submitted job refers to a tcl script residing on the agent machine and the script is not available.
Action: Verify that the agent on the target machine is installed correctly.
Cause: Script parameters of the job are missing.
Action: Submit the job with all required parameters.
Cause: The total length of the job task parameters is too long.
Action: Correct the parameters to satisfy the following constraints:
Cause: Scheduling of job failed either because the time the job was scheduled for has already past or there was an error parsing the job schedule string.
Action: Check the parameters in the job schedule page.
Cause: The number of input files for the job is greater than 5.
Action: Submit the job with the number of input files greater than or equal to 5.
Cause: The agent was unable to locate the repository for the specified job ID. This can happen if the Oracle Management Server repository is out of sync with the agent's queue files.
Action: Contact Oracle Support Services.
Cause: The running job cannot be deleted.
Action: Delete the job after it completes its execution.
Cause: The operating system user credentials set for the target node were incorrect. The agent validates/uses this information to run a job.
Action: In the administrator preferences preferred credentials page, set the correct operating system user credentials for the target node. For more detailed information, see theOracle Enterprise Manager Configuration Guide.
Cause: The agent failed to create an operating system process for running the job.
Action: In the administrator preferences preferred credentials page, set the correct operating system user credentials for the target node. Check the number of processes running on the agent's machine. The operating system may restrict the number of processes.
Cause: The agent was restarted while the job process was running.
Action: Submit the job again.
Cause: The job output could not be written because of file errors.
Action: On the agent machine, check space availability, the permissions on the directory, and the system resources.
Cause: Internal error
Action: Contact Oracle Support Services.
Cause: The job process could not be started after trying several times because of system resource shortage.
Action: Reduce the system work load by reducing the number of jobs.
Cause: An attempt to establish a secure communication channel between the Oracle Management Server and the agent failed.
Action: Check if the Oracle Management Server and agent are up and running and check the network connections.
Cause: Decryption failure
Action: Try performing the action again, and if a problem persists, contact Oracle Support Services.
Cause: The agent was unable to access the event data from the event registration queue file.
Action: Contact Oracle Support Services.
Cause: The agent was unable to access the registration queue file or the event status file.
Action: Contact Oracle Support Services.
Cause: The agent was unable to allocate the required memory during registration or event notification reporting.
Action: Contact Oracle Support Services.
Cause: The agent encountered a tcl script error while evaluating the event tcl script during registration and subsequent scheduled evaluations.
Action: Confirm that the event test parameters are set properly and that the agent is installed properly.
Cause: Either an event containing two identical event tests with the same parameter values is registered, or the Oracle Management Server repository is out of sync with the agent's queue files.
Action: Re-register the event with a different set of parameters.
Cause: The agent was unable to locate the specified event ID. The Oracle Management Server repository might be out of sync with the agent's queue files.
Action: Contact Oracle Support Services.
Cause: The agent was unable to locate the event's script. The event tcl script residing on the agent machine may accidentally have been deleted.
Action: Re-install the Intelligent Agent to ensure all event files are provided on the system. If this fails, contact Oracle Support Services.
Cause: The named parameter which identifies the event is missing.
Action: Register the event supplying the value of the named parameter.
Cause: The maximum string length was exceeded.
Action: Correct the parameters to satisfy the following constraints:
Cause: The Oracle Management Server repository is out of sync with the agent's queue files.
Action: Contact Oracle Support Services.
Cause: Two events containing the same event test were registered with the same parameter values and frequency, and with the fixit flag on. The events were either registered by the same user or by two different users.
Action: Modify the parameter values slightly to ensure the uniqueness of the job.
Cause: The job and event queue files are in an inconsistent state, which may have been caused by an abnormal shutdown of the agent.
Action: Contact Oracle Support Services.
Cause: The frequency parameter of the event is < 30 seconds.
Action: Make sure frequency parameter value is > 30 seconds.
Cause: Either the RPC connection between the gateway and the agent is bad, or the agent might be down.
Action: Restart the agent.
Cause: An attempt to establish a secure communication channel between the Oracle Management Server and the agent failed.
Action: Check if the Oracle Management Server and agent are up and running, and check the network connections.
Cause: Decryption failure
Action: Try performing the action again and if the problem persists, contact Oracle Support Services.
Cause: Agent Gateway failed to get TCP/IP host name of its machine.
Action: Check your TCP/IP configuration and contact Oracle Support Services.
Cause: Some abnormal conditions can cause this error.
Action: Contact Oracle Support Services. You will most likely need to provide a trace file for the Oracle Management Server. Refer to the Oracle Enterprise Manager Configuration Guide for information on tracing the Management Server.
Cause: There may be network congestion or problems with the hardware/software on the node.
Action: Check the node and make sure it is still operational. Check the network connection by pinging the node. For network problems, contact your network adminstrator.
Cause: The Oracle Management Server repository is out of sync with agent's queue files.
Action: Contact Oracle Support Services.
Cause: The task dependency structure of the job or event being submitted is invalid. The job or event could be corrupt.
Action: Delete the job or event and recreate it. If the problem persists, contact Oracle Support Services.
Cause: The task dependency structure of the job or event being submitted is invalid. The job or event could be corrupt.
Action: Delete the job or event and recreate it. If the problem persists, contact Oracle Support Services.
Cause: The job's schedule parameter is incorrect.
Action: Check the parameters on the job schedule page.
Cause: The job's schedule parameter is incorrect.
Action: Submit the job with correct schedule string.
Cause: The submitted job might not have had any output or might have crashed while running.
Action: If the job did have output, check the job script and ensure it is correct, then resubmit the job. Otherwise, contact Oracle Support Services.
Cause: The user who started the Oracle Management Server might not have write permissions to the Oracle Enterprise Manager temporary directory. The gateway uses a temporary directory during the discovery process.
Action: Give write permissions to the Oracle Enterprise Manager temporary directory to the user who started the Oracle Management Server. The temporary directory is located at $ORACLE_HOME/sysman/temp.
Cause: A broadcast job with a non-null value for the Recipient parameter was submitted against an agent. The agent does not support the Recipient field.
Action: Submit the job against the agent with no value filled in the Recipient field.
Cause: The Oracle Management Server's connection to the repository was lost.
Action: Check the health of the repository where Oracle Management Server's schema is stored. If the problem persists, contact Oracle Support Services.
Cause: A non-existent task name was used internally by the Oracle Management Server/Agent Gateway to identify job tasks and event tests. Either the task name is null, or it does not figure in the list of valid tasks maintained in the registry. This error signifies a problem in the Oracle Management Server, the Agent Gateway, or the installation.
Action: Ensure the proper installation of Oracle Enterprise Manager. If problems persist, contact Oracle Support Services.
Cause: Task does not implement the required interface.
Action: Contact Oracle Support Services.
Cause: A valid listener name could not be formed for the submitted listener job/event.
Action: Contact Oracle Support Services.
Cause: Errors occurred while locking Oracle Management Server repository tables.
Action: Check the health of the repository where the Oracle Management Server's schema is stored. If the problem persists, contact Oracle Support Services.
Cause: Unable to access the Oracle Management Server repository.
Action: Check the health of repository where the Oracle Management Server's schema is stored. If the problem persists, contact Oracle Support Services.
Cause: The event submitted contains two event tests that are duplicates.
Action: Edit the event to remove the duplicate event tests.
Cause: A similar event test has already been submitted against the same target.
Action: Deregister the previously registered event before registering a new one.
Cause: An event test with the same arguments has already been submitted against this target.
Action: Deregister the previously registered event before registering a new one.
Cause: The Oracle Management Server was unable to allocate the required memory to collect the job output. This is caused when the output of the returned job is large.
Action: Free up more memory on the node running the Management Server.
Cause: The job output was truncated because the required amount of memory could not be allocated. This occurs when the job's output is large.
Action: If the problem persists, consider reducing the maximum job output size parameter.
Cause: The Oracle Management Server repository is out of sync with the agent's queue files. This could be caused in one of the following ways:
Situation 1: A new agent was installed into a new Oracle home but the "*.q" files were not copied over from the old Oracle home.
Action: Bring the agent down, copy over the new "*.q" files, and bring the agent back up. Refresh the node from within the Oracle Enterprise Manager console.
Situation 2: The agent queue files were accidentally deleted by the user.
Action: Bring the agent down. Remove the node from the Oracle Enterprise Manager console navigator. This will prompt you to remove existing jobs/events. Once jobs and events have been removed, collapse and expand the console navigator to refresh the tree and see that the node is removed.
Situation 3: Two or more agents are one the same node. At some point, jobs and events were submitted against one agent. That agent was brought down and another agent was brought up. Jobs and events were then submitted against the second agent.
Action: Bring up the correct agent and refresh the node from the Oracle Enterprise Manager console navigator.
Situation 4: Communication from the Management Server to the Agent is hung because of network problems or because the agent's machine has crashed.
Action: Perform a tcp/ip ping of the agent machine. Then, check network connectivity by doing a ping from the Management Server machine to the Agent machine. If that succeeds, verify the agent is running by entering these Oracle Net tnsping commands:
tnsping (address=(protocol=tcp)(host=agent-hostname)(port=1748)) tnsping (address=(protocol=tcp)(host=agent-hostname)(port=1754))
If it fails with the ORA-12541 error, it means the agent is not running and needs to be started.
Cause: The user who started the Oracle Management Server might not have write permissions to the Oracle Enterprise Manager temporary directory. The gateway uses a temporary directory during the discovery process.
Action: Give write permissions to the Oracle Enterprise Manager temporary directory to the user who started the Oracle Management Server. The temporary directory is located at $ORACLE_HOME/sysman/temp.
Cause: There is a problem in communication between the Agent and the Oracle Management Server. This error may occur during job submission, event registration or node refresh. This error usually occurs if there is a firewall separating the Agent and the Management Server and the appropriate ports are not open.
Action: If a firewall separates the Management Server and the Agent, the following security rules need to be configured for the firewall:
Cause: There are problems contacting the node itself.
Action: Check the node and make sure it is up and running. Check the physical network connections to the node. Try doing a "ping" and make sure the node is responding. If there are network problems, contact your network adminstrator.
Cause: The node is accessible, but the agent is not running.
Action: Start the agent. If you are running on a Microsoft Windows NT client, start the agent service from the Control Panel Services dialog. If you are running on a UNIX-based client, use the command: lsnrctl dbsnmp_start.
Cause: The agent is not able to respond in a timely manner. This is most likely due to internal communication problems with the agent.
Action: Restart the agent. If this error occurs repeatedly, turn on agent tracing and contact Oracle Support Services.
Cause: There are problems accessing .q files on the agent node.
Action: Check the $ORACLE_HOME/network/agent directory, where $ORACLE_HOME is the directory where the agent is installed. Make sure there is disk space available and permissions are set such that the agent executable (dbsnmp) has read/write permissions on that directory and its files.
Cause: This is an internal error.
Action: Make sure the Agent has been properly installed. Refer to the Oracle Intelligent Agent User's Guide for information on how to verify the agent installation. Verify none of the agent files have been edited nor additional directories created under $ORACLE_HOME/network/agent.
Cause: This is usually a transient type of error.
Action: Check the network connection between the Oracle Management Server and the agent node.
Cause: This occurs when there is communication between an Oracle Management Server and an Agent of a later version. The latest version of Agents supported by a Management Server is the version that ships with the Management Server.
Action: Make sure you use an Agent that is compatible with the Management Server. Refer to the Oracle Enterprise Manager Configuration Guide for information on compatible versions.
Cause: This may occur if jobs or events are submitted against a target that is no longer recognized by the Agent. This happens if a previously discovered target is deleted or if there are configuration problems on the Agent host.
Action: If the target has really been removed, its information also needs to be removed from the Enterprise Manager console. First delete any existing jobs and events against that target. Then delete the target from the console navigator tree.
Cause: Registration of the event test is not supported against this agent version.
Action: Upgrade agent to the version that is supported or higher.
Cause: This may happen during a node refresh. The error occurs because the Oracle Management Server out of sync with the agent's queue files. This could be caused in one of the following ways:
Situation 1: A new agent was installed into a new Oracle home but the "*.q" files were not copied over from the old Oracle home.
Action: Bring the agent down, copy over the new "*.q" files, and bring the agent back up. Refresh the node from within the Oracle Enterprise Manager console.
Situation 2: The agent queue files were accidentally deleted by the user.
Action: Bring the agent down. Remove the node from the Oracle Enterprise Manager console navigator. This will prompt you to remove existing jobs/events. Once jobs and events have been removed, collapse and expand the console navigator to refresh the tree and see that the node is removed.
Situation 3: Two or more agents are one the same node. At some point, jobs and events were submitted against one agent. That agent was brought down and another agent was brought up. Jobs and events were then submitted against the second agent.
Action: Bring up the correct agent and refresh the node from the Oracle Enterprise Manager console navigator.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
