Release 2.2
Part Number A85245-01
 Library |
 Solution Area |
 Contents |
 Index |
| Oracle Enterprise Manager Messages Manual Release 2.2 Part Number A85245-01 |
|
VNI-2001: Queue facility error
Cause: The agent was unable to access the job data from the job queue file.
Action: Contact Oracle Worldwide Customer Support.
VNI-2002: File operation error
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: Contact Oracle Worldwide Customer Support.
VNI-2003: Memory manager error
Cause: The agent was unable to allocate the required memory to accomplish the job.
Action: Contact Oracle Worldwide Customer Support.
VNI-2006: Job is not found.
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 Worldwide Customer Support.
VNI-2007: tcl script is not found.
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.
VNI-2008: Mandatory input is missing.
Cause: Script parameters of the job are missing.
Action: Submit the job with all required parameters.
VNI-2009: Total job task parameters are too long.
Cause: The total length of the job task parameters is too long.
Action: Correct the parameters to satisfy the following constraints:
VNI-2010: Schedule error
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.
VNI-2011: Maximum number of input files exceeded.
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.
VNI-2012: No such user
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 Worldwide Customer Support.
VNI-2013: Outstanding tcl exists. Cannot interrupt.
Cause: The running job cannot be deleted.
Action: Delete the job after it completes its execution.
VNI-2015: Authentication error
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, please see the Oracle Enterprise Manager Configuration Guide.
VNI-2016: Failed to fork job
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.
VNI-2017: Agent restarted while job running.
Cause: The agent was restarted while the job process was running.
Action: Submit the job again.
VNI-2018: Job output lost.
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.
VNI-2019: Could not resume thread
Cause: Internal error
Action: Contact Oracle Worldwide Customer Support.
VNI-2020: System resources shortage
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.
VNI-2021: Crypt key initialization error
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.
VNI-2022: Crypt operation (encryption/decryption) error
Cause: Decryption failure
Action: Try performing the action again, and if a problem persists, contact Oracle Worldwide Customer Support.
VNI-3001: Internal Error: queue facility error
Cause: The agent was unable to access the event data from the event registration queue file.
Action: Contact Oracle Worldwide Customer Support.
VNI-3002: File operation error
Cause: The agent was unable to access the registration queue file or the event status file.
Action: Contact Oracle Worldwide Customer Support.
VNI-3003: Internal Error: memory manager
Cause: The agent was unable to allocate the required memory during registration or event notification reporting.
Action: Contact Oracle Worldwide Customer Support.
VNI-3004: Internal Error: tcl error
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.
VNI-3005: The event test has already been registered with same parameter values by an EM user against the same target.
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.
VNI-3006: Event is not found.
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 Worldwide Customer Support.
VNI-3007: tcl script is not found.
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 Worldwide Customer Support.
VNI-3008: Mandatory input is missing.
Cause: The named parameter which identifies the event is missing.
Action: Register the event supplying the value of the named parameter.
VNI-3009: Maximum string length exceeded.
Cause: The maximum string length was exceeded.
Action: Correct the parameters to satisfy the following constraints:
VNI-3011: User not found in user tables.
Cause: The Oracle Management Server repository is out of sync with the agent's queue files.
Action: Contact Oracle Worldwide Customer Support.
VNI-3012: Fixit job registration already exists.
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.
VNI-3013: Fixit requested and job not scheduled.
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 Worldwide Customer Support.
VNI-3014: Interval too short.
Cause: The frequency parameter of the event is < 30 seconds.
Action: Make sure frequency parameter value is > 30 seconds.
VNI-3015: Connection failed.
Cause: Either the RPC connection between the gateway and the agent is bad, or the agent might be down.
Action: Restart the agent.
VNI-3016: Crypt key initialization error
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.
VNI-3017: Crypt operation (encryption/decryption) error
Cause: Decryption failure
Action: Try performing the action again and if the problem persists, contact Oracle Worldwide Customer Support.
VNI-4001: Local host IP Address could not be resolved.
Cause: Agent Gateway failed to get TCP/IP host name of its machine.
Action: Check your TCP/IP configuration and contact Oracle Worldwide Customer Support.
VNI-4002: Unknown gateway exception
Cause: Some abnormal conditions can cause this error.
Action: Contact Oracle Worldwide Customer Support.
VNI-4009: Cannot contact agent on the node--agent may be down or network communication to the node has failed.
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.
VNI-4016: Fixit job id is invalid.
Cause: The Oracle Management Server repository is out of sync with agent's queue files.
Action: Contact Oracle Worldwide Customer Support.
VNI-4017: Bad vni controller instruction
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 Worldwide Customer Support.
VNI-4018: Inputs to adapter are invalid.
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 Worldwide Customer Support.
VNI-4021: Unrecognized schedule details class in token.
Cause: The job's schedule parameter is incorrect.
Action: Check the parameters on the job schedule page.
VNI-4022: Bad V1 schedule string
Cause: The job's schedule parameter is incorrect.
Action: Submit the job with correct schedule string.
VNI-4025: Task returned no output.
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 Worldwide Customer Support.
VNI-4026: Discovery failed.
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.
VNI-4027: Recipient parameter for broadcast task is not supported by this agent.
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.
VNI-4028: Error accessing gateway registry
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 Worldwide Customer Support.
VNI-4029: Invalid task name: <taskname>
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 Worldwide Customer Support.
VNI-4030: Invalid task : <taskname>
Cause: Task does not implement the required interface.
Action: Contact Oracle Worldwide Customer Support.
VNI-4031: Invalid listener name
Cause: A valid listener name could not be formed for the submitted listener job/event.
Action: Contact Oracle Worldwide Customer Support.
VNI-4032: Error while locking the agent
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 Worldwide Customer Support.
VNI-4033: Error while accessing repository
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 Worldwide Customer Support.
VNI-4034: Duplicate event tests are not allowed. <event test> is a duplicate event test.
Cause: The event submitted contains two event tests that are duplicates.
Action: Edit the event to remove the duplicate event tests.
VNI-4035: The event test has already been registered by an EM user against the same target.
Cause: A similar event test has already been submitted against the same target.
Action: Deregister the previously registered event before registering a new one.
VNI-4036: The event test has already been registered with same parameter values by an EM user against the same target.
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.
VNI-4038: Out of memory! Large job outputs could cause this.
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.
VNI-4039: Output truncated due to Out of Memory.
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.
VNI-4040: Agent state is corrupted.
Cause: The Oracle Management Server repository is out of sync with the agent's queue files. The queue files of the agent may have been corrupted or deleted. This could be caused in one of three 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. Ping the node to see if the Oracle Management Server and agent are now synchronized.
Situation 2: The "*.q" files were deleted.
Action: Remove the node from the Oracle Enterprise Manager console navigator. This will prompt you to remove existing jobs/events. Once the 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 on 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.
VNI-4041: The version of agent cannot be retrieved.
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.
VNI-4042: Secure communication with agent failed.
Cause: The Oracle Management Server is operating in secure mode and tried to communicate with an older agent.
Action: Run the Oracle Management Server in non-secure mode or upgrade the agent to a version which supports secure communication.
VNI-4044: Cannot contact agent. Node may be down, or the network may be down or slow.
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.
VNI-4045: Cannot contact agent. Agent is not running on the node.
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.
VNI-4046: Agent is not responding. Agent may be busy or in an invalid state.
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 Worldwide Customer Support.
VNI-4047: Error accessing queue files on the Agent node.
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.
VNI-4048: Agent internal error (e.g, Out of memory, Operating system error).
Cause: This is an internal error.
Action: Try restarting the agent. If the problem occurs again, turn on the agent tracing and contact Oracle Worldwide Support.
VNI-4049: Agent gateway internal error.
Cause: This is usually a transient type of error.
Action: Check the network connection between the Oracle Management Server and the agent node.
|
 Copyright © 1996-2000, Oracle Corporation. All Rights Reserved. |
|