NMS-01000 to NMS-01099: Agent Error Messages

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-01000 to NMS-01099: Agent Error Messages

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-01000 to NMS-01099: Agent Error Messages

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: Either the user-defined program does not exist or the agent cannot execute it. Your Console and Agent may also be out of sync.

Action: Make sure that the agent can invoke either svrmgr1 or sqldba. Try dropping the particular node from the Console Navigator Pane to re-discover and re-submit the job.

NMS-01011: Invalid data format.

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

Action: Correct the date format.

NMS-01012: Database is in NOARCHIVELOG mode. As a result, this event will not be executed.

Cause: The database is in NOARCHIVELOG mode.

Action: Alter the database archive log mode to on.

NMS-01013: sqlplus does not exist

Cause: The sqlplus executable does not exist.

Action: Make sure either svrmgrl or sqldba can be invoked by the agent.

NMS-01014: Tablespace does not exist or has no free extents.

Cause: No free extends were found for the specified tablespace.

Action: Check the sql statement, and if necessary correct the event or job parameters.

NMS-01015: SELECT unexpectedly returned no rows.

Cause: The SQL statement returned no rows.

Action: Check the SQL statement.

NMS-01016: DML_LOCKS is set to 0. As a result, this event will not be executed.

Cause: DML_LOCKS equals 0.

Action: Check the SQL statement.

NMS-01000 to NMS-01099: Agent Error Messages

NMS-01017: Automatic archiving has been disabled. As a result, this event will not be executed.

Cause: LOG_ARCHIVE_START equals FALSE.

Action: Check the SQL statement.

NMS-01018: VIEW SYS.DBA_BLOCKERS does not exist. Please verify smptsixx.sql has been run.

Cause: VIEW SYS.DBA_BLOCKERS does not exist.

Action: Verify $ORACLE_HOME\sysman\admin\smptsixx.sql has been run.

NMS-01019: The partitions for index %s.%s could not be found.

Cause: The index partitions associated with a particular indexed partition could not be found.

Action: Check the SQL statement.

NMS-01020: Tablespace does not exist or at least one of its datafiles has been defined with autoextend enabled.

Cause: Tablespace does not exist or at least one of its datafiles has been defined with autoextend enabled.