Oracle Enterprise Manager Messages Manual

Library

Product

Contents

Index

Agent Messages

NMS-00000 to NMS-00050: Agent Configuration and Startup
NMS-00051 to NMS-00075: Agent Logging Messages
NMS-00200 to NMS-00250: Database Subagent
NMS-00250 to NMS-00275: Subagent Logging Messages
NMS-00301 to NMS-00350: Agent Operation Messages
NMS-00351 to NMS-00360: Encryption of Agent Files
NMS-00361 to NMS-00370: Unsolicited Event Executable
NMS-00600 to NMS-00799: Jobs and Events
NMS-00900 to NMS-00999: Agent Logging Messages
NMS-01000 to NMS-01099: Agent Error Messages
NMS-01200 to NMS-01999: Internal Agent Error Messages
NMS-05000 to NMS-05999 Agent Errors of the Console

NMS-00000 to NMS-00050: Agent Configuration and Startup

NMS-00051 to NMS-00075: Agent Logging Messages

These messages do not indicate an error.

NMS-00051 Name connected successfully to master agent.

Cause The subagent successfully connected to the master agent.

Action None.

NMS-00052 Disconnected successfully from master agent.

Cause The subagent successfully logged off from the master agent. This would normally be a part of the shutdown process.

Action None.

NMS-00055 Optional parameter parameter was not found in snmp.ora; using default.

Cause The snmp.ora file did not contain the indicated parameter, which was optional. The service instead used its default value for that parameter.

Action If a value other than the default is desired, edit or create the snmp.ora file and try again.

NMS-00200 to NMS-00250: Database Subagent

NMS-00202 Failure to connect to the database.

Cause The database subagent was unable to connect to the database. The detailed error message follows.

Action Consult Oracle7 Server Messages for the detailed error message.

NMS-00203 Error error_number disconnecting from the database: name.

Cause The database subagent was unable to connect to the database, and received the specified error number and text message. The detailed error message follows.

Action Consult Oracle7 Server Messages for the detailed error message.

NMS-00204 Failure to listen on address TNS_address.

Cause The database subagent was unable to listen on the specified TNS address, possibly because another instance of the database agent has already claimed the address. If more information is available, it will appear under this error.

Action If another instance of the database agent is already running, either allow it to continue running or bring it down and try again.

NMS-00205 Failure to connect to database name with username/password string.

Action If another instance of the database agent is already running, either allow it to continue running or bring it down and try again.

NMS-00206 Failure to retrieve character set information from database name.

Cause The character set information is not available.

Action Check if nls_database_parameters table exists.

NMS-00250 to NMS-00275: Subagent Logging Messages

These messages provide information only, they do not indicate an error.

NMS-00250 Database subagent started.

Cause The database subagent started successfully.

Action None.

NMS-00251 Database subagent beginning shutdown process.

Cause The database subagent has received the shutdown command and is processing it.

Action None.

NMS-00252 Database subagent shutting down now.

Cause The shutdown process has completed. This should be the last message output.

Action None.

NMS-00253 Connected successfully to database name.

Cause The subagent successfully logged on to the specified database. This message may also appear if the database goes down and comes back up.

Action None.

NMS-00254 Disconnected successfully from database name.

Cause The subagent successfully logged off from the specified database. This would normally be a part of the shutdown process.

Action None.

NMS-00255 Database name became unreachable; trap sent.

Cause The specified database became inaccessible, and the subagent then sent an SNMP trap. This may not indicate a problem, since the database may have been shut down deliberately (the subagent is unable to distinguish the cause of the inaccessibility). The destination(s) of the trap are normally set as part of master agent configuration.

Action If the shutdown was not deliberate, consult Oracle7 Server Messages. If traps are not being received at your management station(s), consult the platform SNMP documentation and ensure that the management station's address is configured properly for the master agent.

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.

Action 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.

NMS-00351 to NMS-00360: Encryption of Agent Files

NMS-00351 Encryption key supplied is not the one used to encrypt file.

Cause If a key was given at startup, it does not match the key that was last used. If no key was given at startup, then the file was encrypted with a non-default key, and that key must be supplied. There is no way for Oracle to recover the key because it is not hidden anywhere.

Action If the user cannot remember it, then the files should be saved in case the key is remembered later.

NMS-00352 Password file not found or not readable.

Cause This message appears on startup if a "password_file=" argument was typed on the command line, but the indicated file was not found, could not be read, or did not contain a line of text. (For security reasons, the name of the password file is not echoed.)

Action Enter the correct file name and ensure that it has at least one text line of at least 6 characters.

NMS-00355 Password must be at least 6 characters.

Cause The user has typed in a key that is too short. See message 00352.

Action Enter between 6 and 8 characters.

NMS-00361 to NMS-00370: Unsolicited Event Executable

NMS-00361 oemevent invoked with insufficient arguments.

Cause oemevent was called with too few arguments.

Action oemevent should be invoked as follows:

oemevent eventname object severity message [result...]

where:

eventname is a legal Oracle Enterprise Manager event name;

object is the name of the service or resource to which the event applies;

severity is one of the following-----alert, warning, or clear;

message is the text of the error message to be conveyed to the Oracle Enterprise Manager console;

result is zero or more strings to be returned as the results of the event.

NMS-00362 Event name not valid.

Cause The first argument passed to oemevent is not a valid Oracle Enterprise Manager event name.

Action Invoke oemevent with a legal Oracle Enterprise Manager event name.

NMS-00363 Severity level is not valid.

Cause The third argument passed to oemevent is not a valid Oracle Enterprise Manager event severity level (either alert, warning, or clear).

Action Invoke oemevent with a legal Oracle Enterprise Manager severity level.

NMS-00364 oemevent failed to contact agent.

Cause oemevent was unable to establish a connection with the agent Comm process.

Action Make sure that the agent Comm process is running, that it is accepting connections, and that the agent address in the snmp.ora file is correct.

NMS-00365 ReportEvent RPC to agent failed.

Cause oemevent was unable to send the ReportEvent RPC to the agent Comm process.

Action Make sure that the agent is up. Try running oemevent again.

NMS-00600 to NMS-00799: Jobs and Events

These messages can be sent back to the console when users run jobs or register events.

NMS-00600 Insufficient or incorrect arguments.

Cause A predefined event or job was invoked with fewer arguments than required, or with the wrong types of arguments.

Action Check the documentation and try again. If the problem continues, ensure that the installed versions of the agent and the console match.

NMS-00900 to NMS-00999: Agent Logging Messages

These messages appear only in the agent log file and do not necessarily indicate an error.

NMS-00900 Registered event event_name for user_name on service_name; id=event_id.

Cause The agent has registered the specified event for the user of the service; the internal ID number of the event, user and service is shown in the message.

Action None.

NMS-00901 Event event_name duplicates existing registration; rejected.

Cause The Registration was rejected because it was identical to an existing registration.

Action None.

NMS-00902 Cancelling event registration, id event_id.

Cause The agent is about to cancel an event registration.

Action None.

NMS-00903 Delivered an occurrence of event event_id to user_name.

Cause The agent delivered a report of an event occurring, which was registered by the specified user.

Action None.

NMS-00904 Job job_number has expired.

Cause The schedule of the specified job number has expired.

Action None.

NMS-00905 Executing job job_number.

Cause The specified job number is being executed by the agent.

Action None.

NMS-00906 Cancelling job job_number.

Cause The specified job is being cancelled at the request of the console.

Action None.

NMS-00907 Running fixup job job_number for event event_id.

Cause The specified fixup job is being run, since its event occurred.

Action

NMS-00908 Shutting down normally.

Cause A dbsnmp_stop command was received from lsnrctl.

Action None.

NMS-00909 Restarting Comm process.

Cause The Worker process has detected no response from the Comm process for the timeout period, and has restarted it. This may or may indicate an error. If it happens repeatedly, it may indicate communication problems with the console.

Action Inspect trace file for the Comm process, if tracing is on. If not, and this appears repeatedly, stop the agent, turn on tracing, and restart it.

NMS-00910 Scheduled job job_number for user_name with schedule schedule_number; id=internal_id.

Cause A request to schedule the specified job was received from the console and the job was scheduled; the internal ID number is shown in the message.

Action None.

NMS-00911 Cancelling job job_number for user user_name.

Cause The specified job number was cancelled by the console.

Action None.

NMS-00912 Delivered status for job job_number to user user_name.

Cause The status of a completed job was delivered to the console.

Action None.

NMS-00913 Registered user user_name with address address, language name; id=user_id.

Cause The user was registered with the specified parameters. The internal ID of the user is also shown in the message.

Action None.

NMS-00914 Job job_number succeeded.

Cause The specified job number has been run and reported success.

Action None.

NMS-00915 Job job_number failed, error code=error_code.

Cause The specified job ID failed with the error code given. Complete output is returned to the console.

Action None.

NMS-00916 File transfer request for user_name from address.

Cause The specified file was fetched from the specified address.

Action None.

NMS-01000 to NMS-01099: Agent Error Messages

These error messages can appear on the console; they may or may not indicate a software problem. In certain cases, user actions can clear the problem.

NMS-01001 Event file filename does not exist.

Cause The specified event could not be registered because the .tcl file that implements it does not exist on the agent.

Action Check the installation of the agent, and if necessary reinstall the correct version.

NMS-01002 Invalid service name.

Cause On an event registration, a database or service name was specified which the agent does not monitor.

Action Check configuration files on the console, and the snmp.ora file on the agent.

NMS-01003 Failed to lookup user data.

Cause For an event, a user was specified who has not been registered with the agent. Possibly the user registration file has been inadvertently deleted.

Action Logging off from the console and logging back in may fix the problem.

NMS-01004 Invalid user language.

Cause For an event registration, the language string which was registered for the user was invalid. The language comes from the NLS_LANG environment variable on the console machine.

Action Check the setting of the NLS_LANG environment variable. If necessary, correct it, log off from the console, and log back on.

NMS-01005 Event script filename evaluation failed.

Cause The Tcl script for the specified event failed to evaluate. The specific error found by Tcl is returned to the console. It may be that incorrect arguments were provided to the event, or the catsnmp.sql script that allows the agent permission to execute the predefined events has not been run.

Action Check the results returned to the console. Correct the Tcl script if necessary.

NMS-01006 Job file filename does not exist.

Cause The specified job could not be registered because the .tcl file that implements it does not exist on the agent.

Action Check the installation of the agent, and if necessary install the correct version.

NMS-01007 Segment does not exist.

Cause The specified segment could not be found in the database.

Action Make sure the SQL statement is correct, especially the job or event parameters.

NMS-01008 Parameter does not exist.

Cause The specified parameter could not be found in the V$SYSSTAT table.

Action Make sure the SQL statement is correct, especially the job or event parameters.

NMS-01009 Failed to execute the user defined program.

Cause The specified user-defined program could not be executed on the agent.

Action Make sure the user defined program exists and that the agent can execute it.

NMS-01010 svrmgr1 or sqldba does not exist.

Cause Make sure the user-defined program exists and that the agent can execute it.

Action Make sure that the agent can invoke either svrmgr1 or sqldba.

NMS-01011 Invalid data format.

Cause The date format is not in mm/dd/yy format.

Action Correct the date format.

NMS-01200 to NMS-01999: Internal Agent Error Messages

NMS-01200 NMS-Failed to locate user user_name. Deleting an occurrence of event event_id.

Cause Files are out of sync.

Action Shut down the agent, delete the .q files, and then restart the agent.

NMS-01201 Could not create Tcl interpreter.

Cause On an event registration, the agent was unable to create the Tcl interpreter to process the event.

Action Report to Worldwide Customer Support.

NMS-05000 to NMS-05999 Agent Errors of the Console

NMS-05000 Unable to Start Hot Backup.

Cause Call to a SQL statement failed.

Action To be determined.

NMS-05002 An offline backup is in progress.

Cause An offline backup is in progress.

Action To be determined.

NMS-05003 Tablespace is offline.

Cause Tablespace is offline.

Action To be determined.

NMS-05004 Unable to End Hot Backup.

Cause Call to a SQL statement failed.

Action To be determined.

NMS-05005 Unable to Start Cold Backup.

Cause Call to a SQL statement failed.

Action To be determined.

NMS-05006 Offline backup about to take place.

Cause Offline backup about to take place.

Action To be determined.

NMS-05007 Unable to End Cold Backup.

Cause Call to a SQL statement failed.

Action To be determined.

NMS-05008 Database not started.

Cause Database not started.

Action To be determined.

NMS-05009 Logon Failed.

Cause Unable to logon.

Action To be determined.

NMS-05010 Database is running - please shutdown.

Cause Database is running and needs to be shutdown.

Action To be determined.

NMS-05011 Database is not running - please start it.

Cause Database is not running and needs to be started.

Action To be determined.

Prev Next

Library

Product

Contents

Index

Agent Messages

NMS-00001 Warning: service unable to connect to SNMP master agent.

NMS-00202 Failure to connect to the database.

NMS-00302 Failed to initialize user queue.

NMS-00351 Encryption key supplied is not the one used to encrypt file.

NMS-00361 oemevent invoked with insufficient arguments.

NMS-01200 NMS-Failed to locate user user_name. Deleting an occurrence of event event_id.

NMS-05000 Unable to Start Hot Backup.