NNO-00074: downloading region from server string

NNO-00074: downloading region from server string

Cause: An informational message written to the log file during normal server startup.

Action: none

NNO-00073: loading server config from region database

NNO-00073: loading server config from region database

Cause: An informational message written to the log file during normal server startup.

Action: none

NNO-00072: loading from region database

NNO-00072: loading from region database

Cause: normal

Action: An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support.

NNO-00071: cannot construct cache checkpoint file name

NNO-00071: cannot construct cache checkpoint file name

Cause: the server could not construct a system-dependent file name.

Action: An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support.

NNO-00070: administrative region has changed, reloading domain data

NNO-00070: administrative region has changed, reloading domain data

Cause: An informational message written to the log file whenever the server s configuration has changed, and the server is reloading the new configuration from the configuration database.

Action: none

NNO-00069: warning: too many administrative region check failures, checking disabled

NNO-00069: warning: too many administrative region check failures, checking disabled

Cause: a warning issued whenever the server has continuously failed for three days in its attempts to connect to the configuration database. The server disables reload checking. Reload checking can later be re-enabled from the Oracle Network Manager or the Oracle Names control program.

Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the names.no_region_database parameter set to TRUE. If no checkpoint data is available, the server will shut down.

NNO-00068: warning: administrative region check failed, next check in number seconds

NNO-00068: warning: administrative region check failed, next check in number seconds

Cause: this warning is issued whenever the server fails to connect to the configuration database to see if any configuration data has changed. The server will automatically begin reissuing reload checks more frequently, and will eventually give up if connections fail continuously for three days.

Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database.

NNO-00067: server reload check countdown aborted

NNO-00067: server reload check countdown aborted

Cause: An informational message written to the log file whenever the Oracle Names control program halts a reload request previously sent to the server

Action: none

NNO-00066: server will perform reload check of administrative region in number seconds

NNO-00066: server will perform reload check of administrative region in number seconds

Cause: An informational message written to the log file whenever the Oracle Network Manager or the Oracle Names control program send a reload request to the server.

Action: none

NNO-00065: loading cached data from checkpoint file string

NNO-00065: loading cached data from checkpoint file string

Cause: An informational message written to the log file during normal server startup.

Action: none

NNO-00064: loading domain data from checkpoint file string

NNO-00064: loading domain data from checkpoint file string

Cause: An informational message written to the log file when the server has been forced to load from its most recent domain checkpoint file, by setting the names.no_region_database parameter to TRUE.

Action: none

NNO-00063: cannot construct domain checkpoint file name

NNO-00063: cannot construct domain checkpoint file name

Cause: the server could not construct a system-dependent file name.

Action: An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support.

NNO-00062: cannot load domain data from configuration database

NNO-00062: cannot load domain data from configuration database

Cause: An error was encountered while trying to load the server s domain data from the configuration database. If more information is available, it will appear under this error. This error will cause the server to shut down.

Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the names.no_region_database parameter set to TRUE. If no checkpoint data is available, the server will shut down.

NNO-00061: loading data for domain string

NNO-00061: loading data for domain string

Cause: An informational message written to the log file during normal server startup.

Action: none

NNO-00060: loading server topology from checkpoint file string

NNO-00060: loading server topology from checkpoint file string

Cause: An informational message written to the log file when the server has been forced to load from its most recent topology checkpoint file, by setting the names.no_region_database parameter to TRUE.

Action: none

NNO-00059: cannot construct topology checkpoint file name

NNO-00059: cannot construct topology checkpoint file name

Cause: the server could not construct a system-dependent file name.

Action: An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support.

NNO-00058: cannot load topology data from configuration database

NNO-00058: cannot load topology data from configuration database

Cause: An error was encountered while trying to load the server s topology data from the configuration database. If more information is available, it will appear under this error. This error will cause the server to shut down.

Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the names.no_region_database parameter set to TRUE. If no checkpoint data is available, the server will shut down.

NNO-00057: loading and verifying topology data

NNO-00057: loading and verifying topology data

Cause: An informational message written to the log file during normal server startup.

Action: none

NNO-00056: warning: domain minimum TTL must be between number and number, set to number seconds

NNO-00056: warning: domain minimum TTL must be between number and number, set to number seconds

Cause: The server s configuration contains a domain description with an invalid minimum TTL. This error is not fatal; the server will automatically set the TTL to a default value which is suitable for most uses.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.

NNO-00055: invalid domain minimum TTL string

NNO-00055: invalid domain minimum TTL string

Cause: The server s configuration contains a domain description with an invalid minimum TTL.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.

NNO-00054: invalid domain name string

NNO-00054: invalid domain name string

Cause: The server s configuration contains a domain description with an invalid name.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.

NNO-00053: duplicate domain description for domain string

NNO-00053: duplicate domain description for domain string

Cause: The server s configuration contains duplicate domain descriptions in the domain description list.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.

NNO-00052: invalid domain description list

NNO-00052: invalid domain description list

Cause: The server s configuration contains an invalid domain description list.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.

NNO-00051: domain count number exceeds maximum of number, first number will be loaded

NNO-00051: domain count number exceeds maximum of number, first number will be loaded

Cause: The server s configuration contains more domains than the server can support.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.

NNO-00050: serious errors in configuration data, server cannot run

NNO-00050: serious errors in configuration data, server cannot run

Cause: The server s configuration data has a problem of some sort which prevents the server from starting.

Action: Previous error messages in the log file will specify the exact problems leading to the shutdown. The problem most frequently occurs when the network is broken up into multiple administrative regions and the delegation points are incorrect. Read the Oracle Names documentation sections on region delegation and ensure that their directions are being followed correctly.

NNC-00501: warning: string parameter value must be between number and number, setting to number

NNC-00501: warning: string parameter value must be between number and number, setting to number

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.

NNC-00500: warning: string parameter value is illegal, setting to string

NNC-00500: warning: string parameter value is illegal, setting to string

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-00431: NS address does not match any of the current addresses

NNC-00431: NS address does not match any of the current addresses

Cause: When delegating a domain, the address of the Nameserver is provided by the client. If the nameserver 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 nameserver.

NNC-00430: Database not accessible

NNC-00430: Database not accessible

Cause: When a database is used for consistency between different nameservers, 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 Worldwide Customer Support.

NNC-00429: invalid octet string literal string

NNC-00429: invalid octet string literal string

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-00427: server does not support this version of the protocol

NNC-00427: server does not support this version of the protocol

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-00426: no such data type

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-00425: meta-data violation

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

NNC-00424: invalid address string

NNC-00424: invalid address string

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-00423: invalid data item syntax code string

NNC-00423: invalid data item syntax code string

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-00422: invalid data type name string

NNC-00422: invalid data type name string

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-00421: invalid modification directive string, must be between string and string

NNC-00421: invalid modification directive string, must be between string and string

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

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-00419: authoritative server is unreachable

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-00418: name string cannot be modified because it has children

NNC-00418: name string 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-00417: name string already exists

NNC-00417: name string already exists

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-00416: user callback function returned error number string

NNC-00416: user callback function returned error number string

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-00415: section identifier string is invalid, must be between string and string

NNC-00415: section identifier string is invalid, must be between string and string

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-00413: general failure

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-00412: invalid name string

NNC-00412: invalid name string

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-00411: invalid default domain name string

NNC-00411: invalid default domain name string

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-00410: invalid preferred server address list

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-00409: temporary name service failure

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

NNC-00408: name string 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-00407: alias loop in name request

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-00406: name string does not exist

NNC-00406: name string 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-00405: network failure

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-00404: supplied buffer of size string is smaller than minimum size string

NNC-00404: supplied buffer of size string is smaller than minimum size string

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-00403: program interface has not been initialised

NNC-00403: program interface has not been initialised

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-00402: program interface de-initialization failed

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-00401: program interface initialization failed

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-00400: memory exhausted

NNC-00400: memory exhausted

Cause: The program interface has run out of memory.

Action: Add more memory or run fewer processes.

NNC-00053: ASN.1 error encountered while sending or receiving message

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-00052: client and server protocol versions are incompatible

NNC-00052: client and server protocol versions are incompatible

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-00051: message content error

NNC-00051: message content 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.