Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: An operation has completed normally, having met no exceptions.
Action: No action required.
Cause: The SNMP program interface received a value too large for it to process. This error is usually displayed underneath an error which describes in more detail the value which caused the problem.
Action: For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: An SNMP request was not processed because the one or more of the variable names in the request does not exist. This error is not normally visible to the user except in a trace file, where it is usually part of a "soft" error condition which is normal.
Action: The error may indicate that a managed server does not support an operation requested by its control program, perhaps because of version incompatibility. For further details, turn on tracing and re-execute the failing operation. If the error persists, and does not occur as part of a "soft" error condition as noted in the trace file, contact Oracle Support Services.
Cause: The SNMP program interface received a variable value which has an unsupported data type. This error may occur if a standard SNMP network monitor is sending requests to an Oracle service through an SNMP-to-TNS gateway, and that service cannot understand the requests.
Action: For further details, turn on tracing and re-execute the failing operation. If the error persists, and occurs when an Oracle control program sends requests to an Oracle service, contact Oracle Support Services.
Cause: An attempt was made to change a variable value at a remote server, and that variable is read only. This error is usually displayed underneath an error which describes the problem in more detail.
Action: Read-only variables may never be modified.
Cause: An SNMP error occurred which did not fall under the heading of any other more specific error condition. This error may occur if a standard SNMP network monitor is sending requests to an Oracle service through an SNMP-to-TNS gateway, and that service cannot understand the requests.
Action: For further details, turn on tracing and re-execute the failing operation. If the error persists, and occurs when an Oracle control program sends requests to an Oracle service, contact Oracle Support Services.
Cause: An internal function attempted to use an uninitialized SNMP handle.
Action: For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: The SNMP program interface attempted to send or receive an SNMP request and was unable to do so because of a network failure of some sort. This error is usually displayed underneath an error which describes the problem in more detail. The problem typically occurs when a control program is attempting to communicate with a service and either that service has unexpectedly terminated or the network path between the control program and the service has been interrupted.
Action: Ensure that the management platform in question is sending SNMP requests with the correct version number. If the error persists, and occurs when an Oracle control program sends requests to an Oracle service, contact Oracle Support Services.
Cause: The SNMP program interface received a protocol request with an illegal version number. This error may occur if a standard SNMP network monitor is sending malformed requests to an Oracle service through an SNMP-to-TNS gateway.
Action: Ensure that the management platform in question is sending SNMP requests with the correct version number. If the error persists, and occurs when an Oracle control program sends requests to an Oracle service, contact Oracle Support Services.
Cause: The SNMP program interface could not be initialized, either because its error message file could not be found, or because there is a malformed SNMP.COMMUNITIES parameter value in the parameter table.
Action: Check that SQL*Net has been installed properly and that all message files are in their proper locations. Turn on tracing and look for parameter table load errors.
Cause: The program interface has run out of memory.
Action: Add more memory or run fewer processes.
Cause: An internal error occurred inside the SNMP program interface. This error is usually displayed underneath an error which describes the problem in more detail. This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
|
Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|