NNO-00616: enabling DEFAULT-FORWARDERS-ONLY mode

NNO-00616: enabling DEFAULT-FORWARDERS-ONLY mode

Cause: An informational message written to the log file when the server enables DEFAULT-FORWARDERS-ONLY mode in response to a request from the Oracle Names control program.

Action: none

NNO-00615: disabling DEFAULT-FORWARDERS-ONLY mode

NNO-00615: disabling DEFAULT-FORWARDERS-ONLY mode

Cause: An informational message written to the log file when the server disables DEFAULT-FORWARDERS-ONLY mode in response to a request from the Oracle Names control program.

Action: none

NNO-00614: enabling FORWARDING-DESIRED on system queries

NNO-00614: enabling FORWARDING-DESIRED on system queries

Cause: An informational message written to the log file when the server enables the FORWARDING-DESIRED attribute on queries that it generates. The message comes in response to a request from the Oracle Names control program.

Action: none

NNO-00613: disabling FORWARDING-DESIRED on system queries

NNO-00613: disabling FORWARDING-DESIRED on system queries

Cause: An informational message written to the log file when the server disables the FORWARDING-DESIRED attribute on queries that it generates. The message comes in response to a request from the Oracle Names control program.

Action: none

NNO-00612: enabling request forwarding

NNO-00612: enabling request forwarding

Cause: An informational message written to the log file when the server enables request forwarding in response to a request from the Oracle Names control program.

Action: none

NNO-00611: disabling request forwarding

NNO-00611: disabling request forwarding

Cause: An informational message written to the log file when the server disables request forwarding in response to a request from the Oracle Names control program.

Action: none

NNO-00609: warning: forwarder number address length number exceeds maximum of number, ignored

NNO-00609: warning: forwarder number address length number exceeds maximum of number, ignored

Cause: the server s configuration contains a forwarder address whose length exceeds an internal limit.

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

NNO-00608: received corrupted message

NNO-00608: received corrupted message

Cause: The server received a corrupted request. The request is ignored.

Action: corrupted requests are usually caused by transient network problems. If many corrupted messages are received, turn on tracing for further information. If the errors persist, contact Worldwide Customer Support.

NNL-00205: Reload check occurs in string

NNL-00205: Reload check occurs in string

Cause: Control program general message.

Action: None.

NNL-00204: Cancelled shutdown

NNL-00204: Cancelled shutdown

Cause: Control program general message.

Action: None.

NNL-00203: Scheduled shutdown to occur in string

NNL-00203: Scheduled shutdown to occur in string

Cause: Control program general message.

Action: None.

NNL-00202: No shutdown currently scheduled

NNL-00202: No shutdown currently scheduled

Cause: Control program general message.

Action: None.

NNL-00201: Shutdown occurs in string

NNL-00201: Shutdown occurs in string

Cause: Control program general message.

Action: None.

NNL-00049: Output in string cannot be renamed to string

NNL-00049: Output in string cannot be renamed to string

Cause: The given file cannot be created.

Action: Insure that the file specified can be created before running the command. Or use the temporary file itself.

NNL-00048: Error opening file: string

NNL-00048: Error opening file: string

Cause: Named file cannot be opened.

Action: Provide for access to file.

NNL-00047: LDAP modify returned error: 0xnumber, string

NNL-00047: LDAP modify returned error: 0xnumber, string

Cause: LDAP failed with the return code shown.

Action: Refer to LDAP documentation for the meaning of the error.

NNL-00046: Name string exceeds DN template depth

NNL-00046: Name string exceeds DN template depth

Cause: There are more domains in the name than are specified in the DN template.

Action: Add fields to the template or migrate subdomains with separate dump operations.

NNL-00045: No host given for LDAP server

NNL-00045: No host given for LDAP server

Cause: LDAP open will dump core without a host.

Action: Provide appropriate host with -h option.

NNL-00044: Unsupported data type string not mapped

NNL-00044: Unsupported data type string not mapped

Cause: ONames data type could not be mapped to LDAP attributes

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

NNL-00043: LDAP open failure

NNL-00043: LDAP open failure

Cause: LDAP server could not be contacted.

Action: Correct connect info or server unavailability.

NNL-00042: LDAP bind failure: number, string

NNL-00042: LDAP bind failure: number, string

Cause: Call to ldap_bind failed with return set to given number.

Action: Correct user or pwd parameters or definitions.

NNL-00041: Object string not in domain string

NNL-00041: Object string not in domain string

Cause: Object has no relevant RRs to be mapped to LDAP objects.

Action: None.

NNL-00040: Distinguished Name exceeds buffer length: string

NNL-00040: Distinguished Name exceeds buffer length: string

Cause: Distinguished Name derived from Domain Name is too long.

Action: Either move the object to a domain whose name is shorter or manually update the LDAP object.

NNL-00039: no RRs

NNL-00039: no RRs

Cause: Object has no relevant RRs to be mapped to LDAP objects.

Action: None.

NNL-00038: Distinguished Name syntax error

NNL-00038: Distinguished Name syntax error

Cause: Distinguished Name incorrectly specified.

Action: Supply a valid DN.

NNL-00037: Error number while sequencing through parameter table.

NNL-00037: Error number while sequencing through parameter table.

Cause: The NL Parameter system reported an error while retrieving the next name from the table.

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

NNL-00036: No records loaded

NNL-00036: No records loaded

Cause: No loadable data.

Action: None.

NNL-00035: File string or nested IFILEs not found.

NNL-00035: File string or nested IFILEs not found.

Cause: Error in loading from the tnsfile.

Action: None.

NNL-00024: warning: no preferred name servers in SQLNET.ORA

NNL-00024: warning: no preferred name servers in SQLNET.ORA

Cause: The control program was unable to find any preferred name servers in SQLNET.ORA, and will therefore not connect to a default server.

Action: Make sure that the SQLNET.ORA file contains a valid names.preferred_ servers entry.

NNL-00023: SET command is missing an argument

NNL-00023: SET command is missing an argument

Cause: The user attempted to issue a SET command with no argument.

Action: Supply a valid argument to the SET command.

NNL-00022: error changing trace level from string to string, level change ignored

NNL-00022: error changing trace level from string to string, level change ignored

Cause: The user attempted to change the control program s local trace level, and the program encountered an error while changing the level. Usually the problem is that tracing was enabled for the first time (by changing the trace level from OFF to something else) and the trace file is not writeable by the control program.

Action: Check to see that the trace file is writeable. Your documentation will tell you the name of the trace file.

NNL-00020: warning: no TNSNAMES.ORA file and no preferred name servers in SQLNET.ORA

NNL-00020: warning: no TNSNAMES.ORA file and no preferred name servers in SQLNET.ORA

Cause: The control program was unable to find a TNSNAMES.ORA file and was unable to find a default name server in SQLNET.ORA. The control program will operate in this state, but will be unable to resolve any names until a default server has been set, and that server must be set using its raw TNS address.

Action: The control program s SQLNET.ORA file must exist in the correct system-specific location, and must be readable by the control program. The file must contain a names.preferred_servers entry with valid name server addresses. The first server in the preferred-server list must be running, and there must be network connectivity between the control program and that server. Alternatively, a TNSNAMES.ORA file with valid name server information must exist in the correct system-specific location.

NNL-00019: warning: server either changed or ignored your request

NNL-00019: warning: server either changed or ignored your request

Cause: The user issued a request to an Oracle Names server and that request was altered in some way. Typically the user specified an invalid argument of some sort, and the server either ignored the request, or replaced the invalid argument with a reasonable default.

Action: Use the control program to check the current state of the value that you attempted to change. The server s log file may also contain information about the exact cause of the problem. Re-issue the operation with correct arguments.

NNL-00018: warning: could not contact default name server

NNL-00018: warning: could not contact default name server

Cause: The control program was unable to contact its default name server during startup. There are a number of possible causes for this error. The control program s SQLNET.ORA file must exist in the correct system-specific location, and must be readable by the control program. The file must contain a names.preferred_servers entry with valid name server addresses. The first server in the preferred-server list must be running, and there must be network connectivity between the control program and that server.

Action: Check to see that all of the above are true. If the control program is still unable to contact its default server, turn on tracing and restart the control program. If the error persists, contact Worldwide Customer Support.

NNL-00017: cannot start server, program string does not exist

NNL-00017: cannot start server, program string does not exist

Cause: The user issued a STARTUP request, but the control program was unable to start the server because it was unable to find the server executable.

Action: Make sure that a copy of the server executable exists in your system s oracle executable directory.

NNL-00016: cannot start server, error getting program directory s name

NNL-00016: cannot start server, error getting program directory s name

Cause: The user issued a STARTUP request, but the control program was unable to start the server because it was unable to find the name of the directory where the server executable resides.

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

NNO-00807: End of Fetch: OCI_NO_DATA

NNO-00807: End of Fetch: OCI_NO_DATA

Cause: All rows have been returned from the region table.

Action: none

NNO-00806: Error: OCI_ERROR: string

NNO-00806: Error: OCI_ERROR: string

Cause: An OCI occurred accessing the region database. More specific details will be written to the log file.

Action: Find the appropriate entry in the log file and correct the cause of the failure if possible. Otherwise contact Worldwide Customer Support.

NNO-00805: Error: OCI_CONTINUE

NNO-00805: Error: OCI_CONTINUE

Cause: Not possible.

Action: none

NNO-00804: Error: OCI_STILL_EXECUTE

NNO-00804: Error: OCI_STILL_EXECUTE

Cause: An OCI operation between the server and the database is still in progress.

Action: none

NNO-00803: Error: OCI_INVALID_HANDLE

NNO-00803: Error: OCI_INVALID_HANDLE

Cause: The server called OCI with an invalid handle whilc accessing the region database.

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

NNO-00802: Error: OCI_NEED_DATA

NNO-00802: Error: OCI_NEED_DATA

Cause: The server did not provide sufficient data to the OCI interface while accesing the region database.

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

NNO-00801: Error: OCI_SUCCESS_WITH_INFO: string

NNO-00801: Error: OCI_SUCCESS_WITH_INFO: string

Cause: Diagnostic information was returned from OCI during region database access.

Action: none

NNO-00800: Error: cannot read version from config database

NNO-00800: Error: cannot read version from config database

Cause: The query for the region database version failed. The database may be shut down, or the tables may not exist in the schema specified in names.ora.

Action: Correct any access problems accordingly.

NNO-00712: warning: group string cache checkpoint failed

NNO-00712: warning: group string cache checkpoint failed

Cause: The server was unable to perform its normal periodic cache checkpointing, typically because the cache checkpoint file could not be written. The cache checkpoint file name appears as an informational message during server startup.

Action: Check to see that the server has permission to write the cache checkpoint file, and that there is sufficient disk space for the file to be written.

NNO-00711: cache dump countdown aborted

NNO-00711: cache dump countdown aborted

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

Action: none

NNO-00710: server s cache will be dumped to the trace file in number seconds

NNO-00710: server s cache will be dumped to the trace file in number seconds

Cause: An informational message written to the log file when the server dumps its cache to the trace file in response to a request from the Oracle Names control program.

Action: none

NNO-00709: failed delete of cache checkpoint file string , cache flush may not work

NNO-00709: failed delete of cache checkpoint file string , cache flush may not work

Cause: the server attempted to flush its cache, which also deletes the cache checkpoint file. The file deletion failed, although the rest of the cache flush succeeded. Succeeding errors describe the reason for the deletion failure.

Action: This error typically occurs when two cache-flush operations are issued in succession without an intervening cache checkpoint operation (which would recreate the file). The first deletes the cache file, the second attempts to do so, but fails since the file has already been deleted. In such cases, the message is harmless and can be ignored. If, however, the error occurs because the server lacks permission to delete the file, then you must change the file system permissions so the server is allowed to delete the file.

NNO-00708: cache flush countdown aborted

NNO-00708: cache flush countdown aborted

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

Action: none

NNO-00707: server s cache will be flushed in number seconds

NNO-00707: server s cache will be flushed in number seconds

Cause: An informational message written to the log file when the server flushes its cache in response to a request from the Oracle Names control program.

Action: none

NNO-00706: overriding next cache checkpoint, checking in number seconds

NNO-00706: overriding next cache checkpoint, checking in number seconds

Cause: An informational message written to the log file when the server checkpoints its cache in response to a request from the Oracle Names control program.

Action: none

NNO-00705: warning: cannot open checkpoint file string , checkpointing disabled

NNO-00705: warning: cannot open checkpoint file string , checkpointing disabled

Cause: the server was unable to open the named checkpoint file for writing. This problem is typically due to the file system s protection settings. The error is not fatal; it simply means the server will not checkpoint its cache.

Action: Check to see that the server has permission to write the file named in the error message.

NNO-00703: checkpoint interval changed to number seconds

NNO-00703: checkpoint interval changed to number seconds

Cause: An informational message written to the log file when the server changes its cache checkpoint interval in response to a request from the Oracle Names control program.

Action: none

NNO-00702: cache checkpointing disabled

NNO-00702: cache checkpointing disabled

Cause: An informational message written to the log file when the server disables cache checkpointing in response to a request from the Oracle Names control program.

Action: none

NNO-00701: warning: cannot construct checkpoint file name, checkpointing disabled

NNO-00701: warning: cannot construct checkpoint file name, checkpointing disabled

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-00700: warning: cannot checkpoint the cache, trying again in number seconds

NNO-00700: warning: cannot checkpoint the cache, trying again in number seconds

Cause: The server was unable to perform its normal periodic cache checkpointing, typically because the cache checkpoint file could not be written. The cache checkpoint file name appears as an informational message during server startup.

Action: Check to see that the server has permission to write the cache checkpoint file, and that there is sufficient disk space for the file to be written.

NNO-00635: warning: ignoring duplicate forwarder string

NNO-00635: warning: ignoring duplicate forwarder string

Cause: The server s default forwarder list contains a duplicate server. The duplicate is ignored and the server continues running.

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

NNO-00634: received authoritative name string when we are its authority

NNO-00634: received authoritative name string when we are its authority

Cause: a server X received authoritative data from another server Y when server X is also authoritative for the data. Such situations should never arise because if server X is authoritative for the requested data, it should never forward the request to another server.

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-00633: detected fatal delegation loop involving server string

NNO-00633: detected fatal delegation loop involving server string

Cause: the server detected a fatal delegation loop while forwarding a request. A loop occurs when the server s topology data indicates that it should forward a request to itself. The server immediately shuts down in response to this error.

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-00607: server will forward to default forwarders only

NNO-00607: server will forward to default forwarders only

Cause: An informational message written to the log file when the server s configuration enables DEFAULT-FORWARDERS-ONLY mode.

Action: none