Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 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-01012: Database is in NOARCHIVELOG mode

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.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index