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.

---