Oracle Network Products Troubleshooting Guide

Oracle Names Client and Client/Server (NNC-00001 to 00501)

NNC-00001 maximum number of connections already open

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 Worldwide Customer Support.
NNC-00002 error listening on stream num

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.
NNC-00003 error opening stream num

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.
NNC-00004 connection is broken

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.
NNC-00005 cannot initialization stream subsystem

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.
NNC-00050 message format error

Cause: A corrupted name server message was received by a name server or the name server program interface.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NNC-00051 message content error

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.
NNC-00053 ASN.1 error encountered while sending or receiving message

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.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NNC-00400 memory exhausted

Cause: The program interface has run out of memory.

Action: Add more memory or run fewer processes.
NNC-00401 program interface initialization failed

Cause: The name server program interface could not be initialised, 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.
NNC-00402 program interface de-initialization failed

Cause: An internal error occurred while the name server program interface was being de-initialised by an internal function.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NNC-00403 program interface has not been initialised

Cause: Cause: An internal function has attempted to de-initialise the name service program interface when it has not yet been initialised.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NNC-00404 supplied buffer of size num is smaller than minimum size num

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.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NNC-00405 network failure

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.
NNC-00406 name name does not exist

Cause: The user asked for information associated with a global name that does not exist.

Action: Re-try the failing operation with a global name that exists.
NNC-00407 alias loop in name request

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.
NNC-00408 name name exists but desired data does not

Cause: The user asked for information associated with a global name. The name in question exists, but does not contain the desired type of information.

Action: Re-try the failing operation with a type which the desired name does contain.
NNC-00409 temporary name service failure

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: Re-try 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.
NNC-00410 invalid preferred server address list

Cause: The names.preferred_servers parameter in sqlnet.ora is malformed.

Action: Make sure the address list is properly formatted.
NNC-00411 invalid default domain name name

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.
NNC-00412 invalid name 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 Worldwide Customer Support.
NNC-00413 general failure

Cause: A name server program interface error occured 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.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NNC-00414 invalid name-value binding string name

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 Worldwide Customer Support.
NNC-00415 section identifier num is invalid, must be between num and num

Cause: An internal function has called the name server program interface with illegal arguments.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NNC-00416 user callback function returned error number num

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 Worldwide Customer Support.
NNC-00418 name name cannot be modified because it has children

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 Worldwide Customer Support.
NNC-00419 authoritative server is unreachable

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.
NNC-00420 operation not allowed

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.
NNC-00421 invalid modification directive name, must be between num and num

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 Worldwide Customer Support.
NNC-00423 invalid data item syntax code num

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 Worldwide Customer Support.
NNC-00424 invalid address name

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 Worldwide Customer Support.
NNC-00425 meta-data violation

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 Worldwide Customer Support.
NNC-00426 no such data type

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 Worldwide Customer Support.
NNC-00427 server does not support this version of the protocol

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 Worldwide Customer Support.
NNC-00429 invalid octet string literal num

Cause: A caller provided the name server program interface with an invalid octet string 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 Worldwide Customer Support.
NNC-00500 warning: name parameter value is illegal, setting to name

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.
NNC-00501 warning: name parameter value must be between num and num, setting to num

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.