27
Oracle Names Server Messages (NNO)

NNO-00000 normal, successful completion: Cause: An operation has completed normally, having met no exceptions.; Action: No action required.
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.
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. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00052 invalid domain description list: Cause: The server's configuration contains an invalid domain description list. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00053 duplicate domain description for domain "string": Cause: The server's configuration contains duplicate domain descriptions in the domain description list. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00054 invalid domain name "string": Cause: The server's configuration contains a domain description with an invalid name. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00055 invalid domain minimum TTL "string": Cause: The server's configuration contains a domain description with an invalid minimum TTL. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
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. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00057 loading and verifying topology data: Cause: An informational message written to the log file during normal server startup.; Action: No action required.
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-00059 cannot construct topology checkpoint file name: Cause: The server could not construct a system-dependent file name. This is an internal error, not normally visible to the user.; Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Customer Support.
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: No action required.
NNO-00061 loading data for domain "string": Cause: An informational message written to the log file during normal server startup.; Action: No action required.
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-00063 cannot construct domain checkpoint file name: Cause: The server could not construct a system-dependent file name. This is an internal error, not normally visible to the user.; Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Customer Support.
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: No action required.
NNO-00065 loading cached data from checkpoint file "string": Cause: An informational message written to the log file during normal server startup.; Action: No action required.
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: No action required.
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: No action required.
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-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-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: No action required.
NNO-00080 domain "string" cannot be delegated because its parent is already delegated: Cause: An internal delegation error has occurred. Delegation is controlled by the Oracle Network Manager, which enforces correct delegation rules. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00081 domain "string" has no name servers: Cause: An internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00082 domain "string" is missing my name "string" as a name server: Cause: An internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00083 domain "string" server "string" has no addresses: Cause: An internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00084 domain "string" is not in the authoritative domain list: Cause: An internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00104 line string: syntax error, data ignored: Cause: The server found a syntax error its domain data. This message will also appear if the server's internal checkpoint files become corrupted. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00105 line string: invalid name "string", data ignored: Cause: The server found an invalid global name in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00106 line string: invalid TTL "string", data ignored: Cause: The server found an invalid TTL in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00107 line string: ignoring stale checkpoint data: Cause: An informational message which appears during server startup when the server detects out-of-date cached data in its cache checkpoint file. The message is part of normal server startup.; Action: No action required.
NNO-00108 line number: TTL of number seconds below domain minimum number, using minimum: Cause: The server found an invalid TTL value in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00109 line string: invalid data type name "string", data ignored: Cause: The server found an invalid data type name in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00110 line string: unknown data type "string", data ignored: Cause: The server found an unknown data type in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00111 line string: data type "string" has syntax "string", should be "string", data ignored: Cause: The server found an invalid data type syntax in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00112 line string: ignored duplicate data of type "string": Cause: The server found a duplicate record in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00113 line string: alias data already exists, all other data ignored: Cause: The server found a alias and non-alias data with the same global name in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00114 line string: other data exists, alias data ignored: Cause: The server found a alias and non-alias data with the same global name in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00115 line string: single-value data type "string", other instances ignored: Cause: The server found more than one record with the same name and type, when the type allows only a single record with a particular name. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00116 line string: data type "string" not allowed here, data ignored: Cause: The server found a record with an invalid data type in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00117 line string: missing data type, data ignored: Cause: The server found a record with a missing data type in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00118 line string: data length string exceeds maximum of string, data ignored: Cause: The server found a record whose length exceeds an internal limit. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00119 line string: server not authoritative for name "string", data ignored: Cause: The server found a global name in its domain data for which it is not authoritative. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00120 line string: topology name "string" not allowed here: Cause: The server found an invalid record in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00150 warning: invalid hint list, no hints loaded: Cause: The server's configuration contains an invalid hint description list. The server will continue to run, but will not load any hints. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00151 warning: ignoring hint for domain "string", server is authoritative: Cause: The server's configuration contained a hint for a domain in the server's administrative region. The hint is ignored and the server continues to run. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00152 warning: hint count number exceeds maximum of number, first number will be loaded: Cause: There are too many hints in the server's hint list. The server will load a specified maximum number of hints, ignore the rest, and continue running. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00153 warning: hint domain number has invalid name "string", hint domain ignored: Cause: The server's configuration contains a hint domain with an invalid name. The domain is ignored and the server continues to run. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00154 warning: hint number has invalid server name "string", hint ignored: Cause: The server's configuration contains a hint with an invalid server name. The hint is ignored and the server continues to run. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00155 warning: hint number has missing address, hint ignored: Cause: The server's configuration contains a hint with no server address. The hint is ignored and the server continues to run. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00156 warning: hint number address length number exceeds maximum of number, hint ignored: Cause: The server's configuration contains a hint whose address length exceeds an internal limit. The hint is ignored and the server continues to run. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00157 warning: hint number has invalid address, hint ignored: Cause: The server's configuration contains a hint with an invalid address. The hint is ignored and the server continues to run. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00158 warning: hint domain count number exceeds maximum of number, first number will be loaded: Cause: The server's hint domain list is too long. The server will load a specified maximum number of hint domains, ignore the rest, and continue running. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00159 warning: ignoring duplicate hint domain number name "string": Cause: The server's hint domain list contains a duplicate domain. The duplicate is ignored and the server continues running. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00160 warning: ignoring duplicate hint server "string": Cause: The server's hint server list contains a duplicate server. The duplicate is ignored and the server continues running. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00250 invalid administrative region description: Cause: The server encountered an invalid administrative region description during startup. This error will prevent the server from starting. The administrative region description is stored in the server's NAMES.ORA configuration file.; Action: Make sure that the NAMES.ADMIN_REGION 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 Oracle Customer Support.
NNO-00251 missing administrative region parameter string: Cause: The server's administrative region description is missing a required parameter. This error will prevent the server from starting. The administrative region description is stored in the server's NAMES.ORA configuration file.; Action: Make sure that the NAMES.ADMIN_REGION 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 Oracle Customer Support.
NNO-00252 invalid administrative region parameter string value "string": Cause: The server encountered an invalid administrative region parameter. This error will prevent the server from starting. The administrative region description is stored in the server's NAMES.ORA configuration file.; Action: Make sure that the NAMES.ADMIN_REGION 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 Oracle Customer Support.
NNO-00253 administrative region parameter string length string exceeds maximum of string: Cause: The server encountered an administrative region parameter whose length exceeds an internal limit. This error will prevent the server from starting. The administrative region description is stored in the server's NAMES.ORA configuration file.; Action: Make sure that the NAMES.ADMIN_REGION 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 Oracle Customer Support.
NNO-00254 warning: parameter string value must be between number and number, set to number seconds: Cause: The server encountered an administrative region parameter with an invalid value. The value is set to a default suitable for most applications, and the server continues running. The administrative region description is stored in the server's NAMES.ORA configuration file.; Action: Make sure that the NAMES.ADMIN_REGION 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 Oracle Customer Support.
NNO-00255 cannot initialize ROS: Cause: The server was unable to initialize ROS during startup. The error prevents the server from running. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00256 using administrative region "string": Cause: An informational message which appears during server startup, and notes the name of the administrative region for future diagnostic use by administrators. The message is part of normal server startup.; Action: No action required.
NNO-00257 warning: cannot get serial number from configuration database: Cause: The server encountered an error while trying to get the configuration database's serial number. The error occurs almost always because the server configuration has not been exported from the NETADMIN program. The error can also occur any time the server is unable to access the configuration database. If the error occurs during server startup, the server will shut down. If the error occurs during server operation (the server checks the serial number periodically to see if it should reload itself), then the server assumes a transient failure has occurred and repeats the operation a short while later. If the repetitions continue to fail for three days, the server will log another error and stop issuing the serial number load operation.; Action: First make sure that the NETADMIN program has exported a server configuration for this name server. Next, 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. If the error occurs during server startup, you can force startup anyway, with checkpoint data, by starting the server with the NAMES.NO_REGION_DATABASE parameter set to TRUE. If no checkpoint data is available, the server will shut down.
NNO-00258 cannot load configuration from configuration database: Cause: An error was encountered while trying to load the server's configuration 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-00259 configuration tables have not been installed or are inaccessible: Cause: The configuration database has not been properly installed.; Action: Make sure the Oracle Network Manager and its database have been properly installed
NNO-00260 loading configuration 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 configuration checkpoint file, by setting the NAMES.NO_REGION_DATABASE parameter to TRUE.; Action: No action required.
NNO-00261 cannot construct configuration checkpoint file name: Cause: The server could not construct a system-dependent file name. This is an internal error, not normally visible to the user.; Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Customer Support.
NNO-00262 warning: cannot write checkpoint file "string": Cause: The server was unable to write the named checkpoint file. This problem is typically due to the file system's protection settings. The error is not fatal; it means the server will not create any checkpoint data. Note, however, that if the configuration database is ever unavailable during a future server startup, the lack of checkpoint data means you will be unable to force a startup from checkpoint data with the NAMES.NO_REGION_DATABASE parameter.; Action: Check to see that the server has permission to write the file named in the error message.
NNO-00263 error from configuration database: Cause: The server encountered an error while accessing the configuration database. The error can occur when the database is unavailable, or SQL*Net connectivity to the database is interrupted.; 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-00264 configuration database query returned no data: Cause: The server attempted to fetch data from the configuration database and no data was found.; Action: The error generally appears underneath a more specific error which will tell you the exact nature of the problem.
NNO-00265 warning: cannot load data from checkpoint file: Cause: The server was started using checkpoint data, and was unable to read that data. The remaining errors below this one on the error stack provide more specific information about the problem.; Action: Check to see that the named file exists and that the server has permission to read it.
NNO-00266 cannot find document "string" in configuration database: Cause: The server encountered an error while trying to get its configuration ID from the configuration database. The error can occur any time the server is unable to access the configuration database. 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-00267 warning: configuration database contains no data for server "string": Cause: The server successfully contacted the configuration database, but was unable to find any configuration information associated with the server's name. The name is specified in the server's NAMES.ORA configuration file. The error occurs almost always because the server configuration has not been exported from the NETADMIN program.; Action: Make sure that the NETADMIN program has exported a server configuration for this name server.
NNO-00268 warning: configuration database is not used, using checkpoint data instead: Cause: An informational message indicating that the server has been started with the NAMES.NO_REGION_DATABASE parameter set to TRUE, and that it will use checkpoint data rather than attempting to contact the configuration database.; Action: No action required.
NNO-00269 configuration database is version string, server requires at least version string: Cause: The server cannot use the specified configuration database because it is of an incorrect version.; Action: Run the document conversion utility supplied with the Network Manager and re-export your network. The conversion utility will upgrade old documents to a version which can be understood by the name server.
NNO-00270 ORACLE error string: Cause: An ORACLE error was encountered while accessing the configuration database. The error can occur when the database is unavailable, or SQL*Net connectivity to the database is interrupted.; 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-00271 warning: names.ora region is version string, network definition is version string: Cause: The region description in NAMES.ORA is out of synch with the network definition.; Action: No action is required unless the name server cannot run with the network definition. To be safe NAMES.ORA should be updated with one which is consistent with the network definition.
NNO-00300 no listen addresses specified, at least one is required: Cause: The server's configuration is missing addresses on which to listen. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00301 server will shut down in number seconds: Cause: An informational message written to the log file when the server receives a shutdown request from the Oracle Names control program.; Action: No action required.
NNO-00302 server stopped: Cause: An informational message written to the log file when the server shuts down.; Action: No action required.
NNO-00303 server "string" started with process ID number: Cause: An informational message written to the log file when the server successfully starts up.; Action: No action required.
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. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
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: No action required.
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: No action required.
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 Oracle Customer Support.
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: No action required.
NNO-00309 server restarting: Cause: An informational message written to the log file when the server restarts.; Action: No action required.
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: No action required.
NNO-00311 invalid listen address list: Cause: The server's configuration contains an invalid listen address list. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00312 listen address string is invalid: Cause: The server's configuration contains an invalid listen address. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00313 server password length string exceeds maximum of string: Cause: The server's password length exceeds an internal limit. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
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. This is an internal error, not normally visible to the user.; Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Customer Support.
NNO-00315 server is listening on address string: Cause: An informational message written to the log file during server startup.; Action: No action required.
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: No action required.
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: No action required.
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: No action required.
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 Oracle Customer Support.
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: No action required.
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: No action required.
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: No action required.
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: No action required.
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: No action required.
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: No action required.
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 configuration to the configuration file in response to a request from the Oracle Names control program.; Action: No action required.
NNO-00330 server saved the config file "string".: Cause: An informational message written to the log file when the server saves the configuration to a configuration file in response to a request from the Oracle Names control program.; Action: No action required.
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 configuration table, but should be.; Action: No action required.
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. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
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. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
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. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
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: No action required.
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: No action required.
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: No action required.
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: No action required.
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: No action required.
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 Oracle Customer Support.
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. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00610 detected possible alias loop involving name "string": Cause: The server detected an alias loop involving the specified name. An alias loop occurs when an alias "X" points to another alias "Y", which points back to "X" rather than to an address or other name server data. The loop can contain more hops but the basic idea remains the same. Loops occur when administrators incorrectly enter network data, particularly when an alias in one administrative region points to data in another administrative region.; Action: Use the Oracle Names control program to query for the specified name. The control program will describe the alias path, and you can use that information to find which names are incorrect and what administrative regions the incorrect data belongs to.
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: No action required.
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: No action required.
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: No action required.
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: No action required.
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: No action required.
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: No action required.
NNO-00617 enabling AUTHORITY-REQUIRED on system queries: Cause: An informational message written to the log file when the server enables the AUTHORITY-REQUIRED attribute on queries that it generates. The message comes in response to a request from the Oracle Names control program.; Action: No action required.
NNO-00618 disabling AUTHORITY-REQUIRED on system queries: Cause: An informational message written to the log file when the server disables the AUTHORITY-REQUIRED attribute on queries that it generates. The message comes in response to a request from the Oracle Names control program.; Action: No action required.
NNO-00622 warning: too many auto-refresh failures for name "string", query expired: Cause: If an auto-refresh query is issued and continuously returns an error for three days, the query is removed from the auto-refresh queue and a warning logged. The query can be restarted from the Oracle Names control program.; Action: this message will be preceded by numerous warnings that the query in question is failing. Use the Oracle Names control program to describe the failing query. Make sure the server being queried is running and that there is network connectivity between the querying server and the server being queried.
NNO-00623 setting auto-refresh retry interval to number seconds: Cause: An informational message written to the log file when the server changes its auto-refresh retry interval in response to a request from the Oracle Names control program.; Action: No action required.
NNO-00624 setting auto-refresh expiration period to number seconds: Cause: An informational message written to the log file when the server changes its auto-refresh expiration period in response to a request from the Oracle Names control program.; Action: No action required.
NNO-00625 overriding auto-refresh of name "string", type "string", refresh in number seconds: Cause: An informational message written to the log file when the server changes the time when an auto-refresh query is next issued. The message comes in response to a request from the Oracle Names control program.; Action: No action required.
NNO-00626 cannot enable DEFAULT-FORWARDERS-ONLY mode, no default forwarders exist: Cause: The Oracle Names control program issued a request to enable DEFAULT-FORWARDERS-ONLY mode, and the request was ignored because the server has no default forwarders.; Action: No action required.
NNO-00627 cancelling auto-refresh of name "string", type "string": Cause: An informational message written to the log file when the server removes a query from the auto-refresh queue in response to a request from the Oracle Names control program.; Action: No action required.
NNO-00628 setting maximum reforwards per query to number: Cause: An informational message written to the log file when the server changes its maximum-reforward count in response to a request from the Oracle Names control program.; Action: No action required.
NNO-00629 warning: invalid forwarder list, no default forwarders loaded: Cause: The server's configuration contains an invalid forwarder description list. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00630 setting request-processing delay to number seconds: Cause: An informational message written to the log file when the server sets an artificial request-processing delay in response to a request from the Oracle Names control program.; Action: No action required.
NNO-00631 warning: forwarder number has invalid name "string", forwarder ignored: Cause: The server's configuration contains a forwarder description with an invalid server name. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
NNO-00632 warning: forwarder number has missing address, forwarder ignored: Cause: The server's configuration contains a forwarder description with a missing address. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
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. This is an internal error, not normally visible to the user.; Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Customer Support.
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. This is an internal error, not normally visible to the user.; Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Customer Support.
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. This is an internal error, not normally visible to the user.; Action: Contact Oracle Customer Support.
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-00701 warning: cannot construct checkpoint file name, checkpointing disabled: Cause: The server could not construct a system-dependent file name. This is an internal error, not normally visible to the user.; Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Customer Support.
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: No action required.
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: No action required.
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 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-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: No action required.
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: No action required.
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: No action required.
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. Accompanying 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 re-create 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-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: No action required.
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: No action required.
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-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-00801 Error: OCI_SUCCESS_WITH_INFO: Cause: Diagnostic information was returned from OCI during region database access.; Action: No action required.
NNO-00802 Error: OCI_NEED_DATA: Cause: The server did not provide sufficient data to the OCI interface while accessing the region database. This is an internal error.; Action: Contact Oracle Customer Support.
NNO-00803 Error: OCI_INVALID_HANDLE: Cause: The server called OCI with an invalid handle whilc accessing the region database. This is an internal error.; Action: Contact Oracle Customer Support.
NNO-00804 Error: OCI_STILL_EXECUTE: Cause: An OCI operation between the server and the database is still in progress.; Action: No action required.
NNO-00805 Error: OCI_CONTINUE: Cause: This message should not be displayed.; Action: No action required.
NNO-00806 Error: OCI_ERROR "string": Cause: An OCI occurred while 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 Oracle Customer Support.
NNO-00807 Error: OCI_NO_DATA: Cause: This message should not be displayed.; Action: No action required.

27Oracle Names Server Messages (NNO)

27
Oracle Names Server Messages (NNO)