Oracle Network Products Troubleshooting Guide | Library |
Product |
Contents |
Index |
Cause: | The specified service could not contact the SNMP master agent.The master agent supported by Oracle for this platform is not installed, or has not been started. Messages specific to this platform follow. |
Action: | Consult Oracle documentation for your platform, and then make sure that the correct SNMP master agent is installed and started. |
Cause: | The specified service was unable to allocate enough memory to hold all all the snmp.ora parameters. This may indicate that the parameters are too big, but more likely is a system error. |
Action: | Check system configuration and if possible, reduce the number of the processes running. If this does not fix the problem, report as a bug. |
Cause: | The snmp.ora file could not be opened and read by the specified service. The location of this file varies by platform, but normally it must be in the same directory as other SQL*Net paramter files. Detailed error messages may follow this one, if the problem could be traced to a specific parameter. |
Action: | Consult the documentation for your platform, then create the file in the proper location, and restart the program. |
Cause: | The specified service was unable to register its MIB or MIB row with the master agent. |
Action: | Consult the documentation for SNMP on your platform. If the messages indicate that another program already has that MIB or MIB row registered, you may want to terminate that program, then retry. |
Cause: | The snmp.ora file does not contain a filled-in snmp.visibleservices parameter, or it's empty. |
Action: | Edit or create the snmp.ora file and try again. |
Cause: | The snmp.ora file did not contain the indicated parameter, which was required. Normally this would happen because one of the services mentioned in snmp.visible services required one or more detail parameters to be supplied, such as the one indicated. |
Action: | Edit or create the snmp.ora file and try again. |
Cause: | The specified service was unable to allocate memory. |
Action: | Check system configuration and if possible, reduce the number of the processes running. If this does not fix the problem, report as a bug. |
Cause: | The database subagent was unable to connect to the database. The detailed error message, which is documented in Oracle7 Server manuals, follows. |
Action: | Consult Oracle7 Server documentation for the detailed error message. |
Cause: | The database subagent was unable to connect to the database, and received the specified error number and text message. The detailed error message, which is documented in Oracle7 Server manuals, follows. |
Action: | Consult Oracle7 Server documentation for the detailed error message. |
Cause: | The database subagent was unable to listen on the specifiedTNS 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. Otherwise, see "Actions" for the other TNS errors. |
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 dow and try again. Otherwise, see "Actions" for the other TNS errors. |
NMS-00253 Connected successfully to database Oracle_SID
Cause: | The subagent successfully logged on to the specified database. This message may also be output if the database goes down and comes back up. |
Action: | None |
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). |
Action: | Consult the Oracle7 Server documentation, if the shutdown was not deliberate. 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. |
Prev Next |
Copyright © 1996 Oracle Corporation. All Rights Reserved. |
Library |
Product |
Contents |
Index |