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

## 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: None

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

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