Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| 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: All available name service connections are handling requests.
Action: If the problem occurs when running a name server, increase the values of NAMES.MAX_OPEN_CONNECTIONS. If the problem occurs in a client program, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: The name server was asked to listen on the specified address, and failed, probably because the address is malformed, or because it uses a SQL*Net protocol adaptor which has not been installed.
Action: Make sure the address is properly formed, and that it uses a protocol adaptor which has been installed on your system.
Cause: A name server or client program attempted to open a connection to another server and failed, either because the server is down, or because the network path to that server is not working. This error is usually displayed underneath an error which describes the problem in more detail.
Action: Make sure that the server being connected to is listening on the address used, and that there is network connectivity between the two end-points.
Cause: The connection from a name server or client program to another server has been broken, either because that server has shut down, or because the network path to the server has stopped working. This error is usually displayed underneath an error which describes the problem in more detail.
Action: Make sure that the server being connected to is running and listening on the address used, and that there is network connectivity between the two end-points.
Cause: The name service stream subsystem could not be started, probably because of a missing TNS error message file.
Action: Check that SQL*Net has been installed properly and that all message files are in their proper locations.
Cause: A corrupted name server message was received by a name server or the name server program interface. 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.
Cause: A corrupted name server message was received by a name server or the name server program interface. 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.
Cause: A name server message with an incompatible protocol version was received by a name server or the name server program interface. This problem will occur when there are clients and servers with widely varying protocol versions that are trying to communicate.
Action: Upgrade older client and server software so it is compatible with newer software.
Cause: The name server or the name server program interface attempted to send or receive a message and failed because of an ASN.1 error. 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.
Cause: The program interface has run out of memory.
Action: Add more memory or run fewer processes.
Cause: The name server program interface could not be initialized, probably because of a missing TNS or name server error message file.
Action: Check that SQL*Net has been installed properly and that all message files are in their proper locations.
Cause: An internal error occurred while the name server program interface was being de-initialized by an internal function. 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.
Cause: An internal function has attempted to de-initialize the name service program interface when it has not yet been initialized. 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.
Cause: A caller supplied the name server program interface with a memory buffer too small for the interface's requirements. 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.
Cause: The network connection between the client program and the name server has failed, either because the server has shut down, or because the network path to the server has stopped working. This error is usually displayed underneath an error which describes the problem in more detail.
Action: Contact your name server administrator to make sure that the server being connected to is running and listening on the address used, and that there is network connectivity between the two end-points.
Cause: A request was made for information associated with a global name that does not exist.
Action: Retry the failing operation with a global name that exists.
Cause: The name service detected an "alias loop" when trying to retrieve information associated with a global name. An alias loop occurs when an alias name X points to another alias name Y, which in turn points back to X, rather than eventually to a global name which contains data.
Action: Contact your name server administrator to have the alias loop investigated and fixed.
Cause: A request was made for information associated with a global name. The name in question exists, but does not contain the desired type of information.
Action: Retry the failing operation with a type which the desired name does contain.
Cause: There are no name servers available to handle a client request, or a name server was temporarily unable to handle a client request. This situation is almost always temporary, and occurs when the program interface has issued a name server request and not received a timely response from any of its preferred servers. Such delays can occur due to transient network or name server outages or heavy load.
Action: Retry the failing operation. If the error persists, make sure there is network connectivity between the client and its preferred name servers, and contact your name server administrator to make sure that those name servers are running.
Cause: The NAMES.PREFERRED_SERVERS parameter in SQLNET.ORA is malformed.
Action: Make sure the address list is properly formatted.
Cause: The NAMES.DEFAULT_DOMAIN parameter in SQLNET.ORA is invalid.
Action: Make sure the parameter value is a valid global name. See your documentation for the characters which may be used in a global name.
Cause: The name server program interface was given an invalid global name to process.
Action: Supply a valid domain name. If the error is caused by an internal function, contact Oracle Support Services.
Cause: A name server program interface error occurred which did not fall under the heading of any other more specific error condition. The error will usually be followed by more specific lower-level information. 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.
Cause: A caller provided the name server program interface with an invalid name-value binding string value.
Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a valid name-value binding string argument. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: An internal function has called the name server program interface with illegal arguments. 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.
Cause: An internal function has called the name server program interface with illegal arguments. 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.
Cause: A caller has attempted to create a new global name, and that name already exists.
Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a name that does not already exist. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: A caller has attempted to delete or rename a global name, and that name cannot be modified because it has child names underneath it in the name space.
Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a name that is a leaf node. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: A name server request cannot be processed because the server which received the operation does not own the name specified in the request and cannot locate the server which does own the name. The error is almost always transient, and occurs either because the path between the server receiving the request and the request's final destination has been interrupted, or because the final destination is down.
Action: Not normally visible to the user, except when using the name server control program. Because the error is typically a transient one, retrying the failing operation will usually work. If the failure persists, the name server which is allowed to process the failing operation is probably shut down or unreachable. Contact your name server administrator to make sure that your site's name servers are running, and are properly configured.
Cause: A name server request cannot be processed because the server which received the operation is not allowed to process it. The problem typically occurs when an administrator has disabled request processing at a particular server for some reason.
Action: Contact your name server administrator to determine why server request processing has been disabled.
Cause: An internal function has called the name server program interface with illegal arguments. 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.
Cause: A caller has provided an invalid data type name to the name server program interface.
Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a valid type name. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: A caller has provided an invalid data type code to the name server program interface.
Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a valid type name. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: A caller provided the name server program interface with an invalid address value.
Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a valid address argument. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: A caller issued a name server modification request and that request cannot be processed because it would violate data type meta-data constraints.
Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, examine the meta-data constraints for the data type being operated upon and don't violate them. Examples of typical constraint violations are attempts to add a new data item to a name which already contains alias information, or attempts to add alias information to a name which already contains other data, or attempts to replace a data item with another item that has the wrong syntax. If the error occurs outside the control program, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: A caller attempted to create a data item, and could not because the data item's type does not exist.
Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the operation with an existent data type. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: A name server message with an incompatible protocol version was received by a name server or the name server program interface. This problem will occur when there are clients and servers with widely varying protocol versions that are trying to communicate.
Action: Upgrade the older client and server software so it is compatible with newer software.
Cause: A caller provided the name server program interface with an invalid meta-data data item.
Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a valid meta-data argument. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: A caller provided the name server program interface with an invalid octet string value.
Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, retry the failing operation with a valid octet string argument. Otherwise, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.
Cause: When a database is used for consistency between different name servers, any modify operation should not only modify the cache but also the database. And if the database is not accessible, this error occurs.
Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, make sure database is available and then re-execute the operation. If error persists, contact Oracle Support Services.
Cause: When delegating a domain, the address of the name server is provided by the client. If the name server already exists, then it already has address(es) associated with it. So, the address supplied by the client must match one of them. Otherwise, this error occurs.
Action: Not normally visible to the user, except when using name server control program. If the error occurs when using the control program, either provide an one of the existing addresses of the name server or delegate the domain to a new name server.
Cause: The named parameter value is invalid.
Action: Make sure the parameter value is formatted correctly. Valid choices for boolean parameter values are TRUE, FALSE, YES, NO, ON, and OFF.
Cause: The named parameter value is invalid or outside legal boundary values.
Action: Make sure the parameter value is a number, and falls between valid minimum and maximum values, as specified in the error text.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
