Oracle Error Messages: 12/02/11

NNO-00606: disabling modification requests

NNO-00606: disabling modification requests

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

Action: none

NNO-00605: enabling modification requests

NNO-00605: enabling modification requests

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

Action: none

NNO-00604: disabling all request processing

NNO-00604: disabling all request processing

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

Action: none

NNO-00603: enabling all request processing

NNO-00603: enabling all request processing

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

Action: none

NNO-00602: warning: forwarder number has invalid address, forwarder ignored

NNO-00602: warning: forwarder number has invalid address, forwarder ignored

Cause: One of the forwarders in the default forwarder list has an invalid address. The forwarder definition is ignored and the server continues running.

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

NNO-00601: warning: no forwarders, DEFAULT-FORWARDERS-ONLY mode ignored

NNO-00601: warning: no forwarders, DEFAULT-FORWARDERS-ONLY mode ignored

Cause: the server s configuration enables DEFAULT-FORWARDERS-ONLY mode but the configuration contains no default forwarders. The server ignores the request and continues running.

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

type- probably SQL, possibly LDAP or LDIF NNO-00600: warning: forwarder count number exceeds maximum of number, first number will be loaded

type- probably SQL, possibly LDAP or LDIF NNO-00600: warning: forwarder count number exceeds maximum of number, first number will be loaded

Cause: the server s configuration contains too many default forwarders. The server loads a specified maximum number of forwarders, ignores the rest, and continues running.

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

type- probably SQL, possibly LDAP or LDIF NNO-00334: region load failure: ROS admin_region type number unsupported

type- probably SQL, possibly LDAP or LDIF NNO-00334: region load failure: ROS admin_region type number unsupported

Cause: the value set in names.admin_region is an obsolete ROS type

Action: No action is necessary; administrators should set the value to the correct

NNO-00333: warning: ROS admin_region types obsolete; using SQL

NNO-00333: warning: ROS admin_region types obsolete; using SQL

Cause: the value set in names.admin_region is an obsolete ROS type

Action: No action is necessary; administrators should set the value to the correct

NNO-00332: warning: region store serial number reduced from number to number

NNO-00332: warning: region store serial number reduced from number to number

Cause: An informational message written to the log file when the server finds the region database has its serial number set lower than it was when the server previously loaded the region data. This is an unnatural condition- every update to the region should increment the serial number so a reduction of the serial number might reflect tampering or accidental manual alteration this and possibly other region tables.

Action: Administrators should find out how or why the serial number decreased.

NNO-00331: error saving new value string of string to the save config table.

NNO-00331: error saving new value string of string to the save config table.

Cause: An informational message written to the log file when the a set operation is performed and the change cannot be saved in the save config ptable, but should be.

Action: none

NNO-00330: server saved the config file string .

NNO-00330: server saved the config file string .

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

Action: none

NNO-00329: server will save the config file in number seconds

NNO-00329: server will save the config file in number seconds

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

Action: none

NNO-00328: server has reset statistic counters to zero

NNO-00328: server has reset statistic counters to zero

Cause: An informational message written to the log file when the server resets its statistic counters to zero in response to a request from the Oracle Names control program.

Action: none

NNO-00327: server statistic counter dump ends

NNO-00327: server statistic counter dump ends

Cause: An informational message written to the log file at the end of a statistic dump. The message is preceded by a set of server statistics.

Action: none

NNO-00326: server statistic counter dump follows

NNO-00326: server statistic counter dump follows

Cause: An informational message written to the log file at the beginning of a statistic dump. The message is followed by a set of server statistics, and ends with another informational message indicating the dump has finished.

Action: none

NNO-00323: overriding next statistic counter dump, dumping in number seconds

NNO-00323: overriding next statistic counter dump, dumping in number seconds

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

Action: none

NNO-00322: statistic counter dump interval changed to number seconds

NNO-00322: statistic counter dump interval changed to number seconds

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

Action: none

NNO-00321: statistic counter dump disabled

NNO-00321: statistic counter dump disabled

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

Action: none

NNO-00320: missing server name parameter

NNO-00320: missing server name parameter

Cause: the server could not find a names.server_name parameter. The name is specified in the server s names.ora configuration file.

Action: Make sure that the names.server_name parameter in names.ora is correct. The names.ora file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Worldwide Customer Support.

NNO-00318: overriding next statistic counter reset, resetting in number seconds

NNO-00318: overriding next statistic counter reset, resetting in number seconds

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

Action: none

NNO-00317: statistic counter reset interval changed to number seconds

NNO-00317: statistic counter reset interval changed to number seconds

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

Action: none

NNO-00316: statistic counter reset disabled

NNO-00316: statistic counter reset disabled

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

Action: none

NNL-00015: type string has string syntax, which has no textual representation

NNL-00015: type string has string syntax, which has no textual representation

Cause: Not all data type syntaxes can be represented as text. This message indicates that the user issued a name server request for a type with an non-textual representation.

Action: Re-issue the operation with a data type that has a syntax with a textual representation.

NNL-00014: unknown data type string

NNL-00014: unknown data type string

Cause: The user issued a name server request which contained an unknown data type.

Action: It is possible that the server had no information on the type, but automatically fetched it in response to the failing request. Re-issue the failing request; if the server has in the meantime fetched the appropriate data type information, the error will go away. If the error persists, the data type is probably invalid.

NNL-00013: not performed, permission denied for supplied password

NNL-00013: not performed, permission denied for supplied password

Cause: The user issued a request to an Oracle Names server, and the password supplied with the request was incorrect.

Action: Check to see that the password sent by the control program to the server is correct for that server. You can set a new password with the SET PASSWORD control program command.

NNL-00012: invalid string value string

NNL-00012: invalid string value string

Cause: The first argument is a data type, the second is a value. The user supplied an invalid data value of the specified type.

Action: Re-issue the failing operation with correct data.

NNL-00011: no server with name string exists

NNL-00011: no server with name string exists

Cause: The user issued a SET SERVER request and the current managed Oracle Names server was unable to translate that name into an address. Alternatively, the user issued a control program request to a specific server, and that server s name could not be translated into an address. Both problems are almost always caused by mis-typing the server name.

Action: Re-issue the request with a valid server name.

NNL-00010: error getting address for server string

NNL-00010: error getting address for server string

Cause: s for the failure. 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. If the user has changed managed servers with the SET SERVER command, the new server must be running, and must be able to resolve the address or forward the request to another server which can resolve the address. Alternatively, a TNSNAMES.ORA file with valid name server names and addresses must exist in the correct system-specific location.

Action: For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNL-00009: encryption of server password failed

NNL-00009: encryption of server password failed

Cause: The control program attempted and failed to encrypt a server password, supplied either through the SET PASSWORD command or the namesctl.server_ password configuration parameter.

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

NNL-00008: request not understood by server

NNL-00008: request not understood by server

Cause: The control program issued a request to an Oracle Names server and the server did not understand the request.

Action: If the server and the control program have different versions, they may be unable to communicate. Check your documentation for version compatibility constraints. If the server and control program are compatible, turn on tracing for further details, and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNL-00007: server responded with an error

NNL-00007: server responded with an error

Cause: The control program issued a request to an Oracle Names server and the server responded with an error.

Action: For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNL-00006: timeout, server is not responding

NNL-00006: timeout, server is not responding

Cause: The control program issued a request to an Oracle Names server and no response arrived in a timely fashion. The network connection between the control program and the server may be faulty, the server may be very heavily loaded, or there may be substantial network delays between the control program and the server. The latter is especially true for WAN links.

Action: Reissue the command; if it continues to fail, check to see that the server being managed is running correctly and that the network connection between the server and the control program is working correctly.

NNL-00005: no server has been set. Use the SET SERVER command first

NNL-00005: no server has been set. Use the SET SERVER command first

Cause: The user attempted to issue a command which requires that a default managed Oracle Names server be set first.

Action: Use the SET SERVER command to set your default server, then reissue the command. Alternatively, if the command allows, re-issue it with a specific server name so the control program does not need to use the default.

NNL-00004: invalid command argument string

NNL-00004: invalid command argument string

Cause: The user entered an invalid command argument.

Action: Supply a valid argument.

NNL-00003: memory exhausted

NNL-00003: memory exhausted

Cause: The program has run out of memory

Action: Check the amount of available memory on your machine to ensure that there is enough memory to run this executable. If necessary, free up memory by running fewer programs, then try again.

NNL-00002: request argument string is not allowed with this operation

NNL-00002: request argument string is not allowed with this operation

Cause: The user entered a request command argument which is not valid with the particular request command.

Action: Supply a valid argument.

NNL-00001: request argument string is invalid

NNL-00001: request argument string is invalid

Cause: The user entered an invalid request command argument.

Action: Supply a valid argument.

NNO-00854: error unbinding LDAP: error = number

NNO-00854: error unbinding LDAP: error = number

Cause: the server failed to connect to the LDAP directory.

Action: Find the cause of the error and correct it and restart the server.

NNO-00853: failed to get LDAP attribute or value: error = number

NNO-00853: failed to get LDAP attribute or value: error = number

Cause: the server failed to connect to the LDAP directory.

Action: Find the cause of the error and correct it and restart the server.

NNO-00852: failed to get LDAP entry: error = number

NNO-00852: failed to get LDAP entry: error = number

Cause: the server could not retrieve query entries from the LDAP API.

Action: Find the cause of the error and correct it and restart the server.

NNO-00851: LDAP open or bind failed: error = number

NNO-00851: LDAP open or bind failed: error = number

Cause: the server failed to connect to the LDAP directory.

Action: Find the cause of the error and correct it and restart the server.

NNO-00850: Error: LDAP query returns string

NNO-00850: Error: LDAP query returns string

Cause: The LDAP API returned an error. 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-00809: Unknown OCI error: number

NNO-00809: Unknown OCI error: number

Cause: Not possible.

Action: none

NNO-00808: Error connecting to region database

NNO-00808: Error connecting to region database

Cause: Not possible.

Action: none

NNO-00315: server is listening on address string

NNO-00315: server is listening on address string

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

Action: none

NNO-00314: error changing trace level from number to number, level change ignored

NNO-00314: error changing trace level from number to number, level change ignored

Cause: the server encountered an error while changing its trace level in response to a request from the Oracle Names control program.

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-00313: server password length string exceeds maximum of string

NNO-00313: server password length string exceeds maximum of string

Cause: the server s password length exceeds an internal limit.

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

NNO-00312: listen address string is invalid

NNO-00312: listen address string is invalid

Cause: the server s configuration contains an invalid listen address.

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

NNO-00311: invalid listen address list

NNO-00311: invalid listen address list

Cause: the server s configuration contains an invalid listen address list.

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

NNO-00310: server restart countdown aborted

NNO-00310: server restart countdown aborted

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

Action: none

NNO-00309: server restarting

NNO-00309: server restarting

Cause: An informational message written to the log file when the server restarts.

Action: none

NNO-00308: server will restart in number seconds

NNO-00308: server will restart in number seconds

Cause: An informational message written to the log file when the server receives a restart request from the Oracle Names control program.

Action: none

NNO-00307: invalid server name string

NNO-00307: invalid server name string

Cause: the server s name is invalid. The name is specified in the server s names.ora configuration file.

Action: Make sure that the names.server_name parameter in names.ora is correct. The names.ora file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Worldwide Customer Support.

NNO-00306: server shutdown countdown aborted

NNO-00306: server shutdown countdown aborted

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

Action: none

NNO-00305: trace level changed from number to number

NNO-00305: trace level changed from number to number

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

Action: none

NNO-00304: listen address string length string exceeds maximum of string

NNO-00304: listen address string length string exceeds maximum of string

Cause: the length of one of the server s listen addresses exceeds an internal limit.

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