Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## Oracle Names Server Error Messages: NNO-00050 to NNO-00712

##### 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 num exceeds maximum of num, first num will be loaded

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

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

##### NNO-00052: invalid domain description list

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

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

##### NNO-00053: duplicate domain description for domain str

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

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

##### NNO-00054: invalid domain name str

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

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

##### NNO-00055: invalid domain minimum TTL str

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

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

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

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

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

##### NNO-00057: loading and verifying topology data

Cause: An informational message written to the log file during normal server start-up.

Action: none

##### 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.

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-00060: loading server topology from checkpoint file str

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

Action: none

##### NNO-00061: loading data for domain str

Cause: An informational message written to the log file during normal server start-up.

Action: none

##### 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.

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-00068: warning: administrative region check failed, next check in num 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: none

##### NNO-00080: domain str 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.

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

##### NNO-00081: domain str has no name servers

Cause: an internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly.

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

##### NNO-00082: domain str is missing my name str as a name server

Cause: an internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly.

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

##### NNO-00083: domain str server str has no addresses

Cause: an internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly.

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

##### NNO-00084: domain str 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.

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

##### NNO-00104: line str: 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.

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

##### NNO-00105: line str: invalid name str, 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.

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

##### NNO-00106: line str: invalid TTL str, 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.

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

##### NNO-00107: line str: ignoring stale checkpoint data

Cause: an informational message which appears during server start-up when the server detects out-of-date cached data in its cache checkpoint file. The message is part of normal server startup.

Action: none

##### NNO-00108: line num: TTL of num seconds below domain minimum num, 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.

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

##### NNO-00109: line str: invalid data type name str, 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.

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

##### NNO-00110: line str: unknown data type str, 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.

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

##### NNO-00111: line str: data type str has syntax str, should be str, 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.

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

##### NNO-00112: line str: ignored duplicate data of type str

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.

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

##### NNO-00113: line str: 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.

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

##### NNO-00114: line str: 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.

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

##### NNO-00115: line str: single-value data type str, 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.

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

##### NNO-00116: line str: data type str 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.

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

##### NNO-00117: line str: 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.

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

##### NNO-00118: line str: data length str exceeds maximum of str, 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.

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

##### NNO-00119: line str: server not authoritative for name str, 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.

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

##### NNO-00120: line str: topology name str 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.

Action: An internal error not normally visible to the user. Contact Worldwide 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.

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

##### NNO-00151: warning: ignoring hint for domain str, 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.

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

##### NNO-00152: warning: hint count num exceeds maximum of num, first num 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.

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

##### NNO-00153: warning: hint domain num has invalid name str, 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.

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

##### NNO-00154: warning: hint num has invalid server name str, 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.

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

##### NNO-00155: warning: hint num 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.

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

##### NNO-00156: warning: hint num address length num exceeds maximum of num, 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.

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

##### NNO-00157: warning: hint num 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.

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

##### NNO-00158: warning: hint domain count num exceeds maximum of num, first num 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.

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

##### NNO-00159: warning: ignoring duplicate hint domain num name str

Cause: The server's hint domain list contains a duplicate domain. The duplicate is ignored and the server continues running.

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

##### NNO-00160: warning: ignoring duplicate hint server str

Cause: The server's hint server 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-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 Worldwide Customer Support.

##### NNO-00251: missing administrative region parameter str

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 Worldwide Customer Support.

##### NNO-00252: invalid administrative region parameter str value str

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 Worldwide Customer Support.

##### NNO-00253: administrative region parameter str length str exceeds maximum of str

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 Worldwide Customer Support.

##### NNO-00254: warning: parameter str value must be between num and num, set to num 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 Worldwide Customer Support.

##### NNO-00255: cannot initialize ROS

Cause: The server was unable to initialize ROS during startup. The error prevents the server from running.

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

##### NNO-00256: using administrative region str

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: none

##### 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 str

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: none

##### NNO-00261: cannot construct configuration checkpoint file name

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

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

##### NNO-00262: warning: cannot write checkpoint file str

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 simply 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 str 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 str

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: none

##### NNO-00269: configuration database is version str, server requires at least version str

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 str

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 str, network definition is version str

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.

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

##### NNO-00304: listen address str length str exceeds maximum of str

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.

##### NNO-00307: invalid server name str

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-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-00312: listen address str 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-00313: server password length str exceeds maximum of str

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-00314: error changing trace level from num to num, 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-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-00600: warning: forwarder count num exceeds maximum of num, first num 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.

##### 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.

##### NNO-00602: warning: forwarder num 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-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.

##### NNO-00609: warning: forwarder num address length num exceeds maximum of num, 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-00610: detected possible alias loop involving name str

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 mis-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-00622: warning: too many auto-refresh failures for name str, 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-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: None.

##### NNO-00629: warning: invalid forwarder list, no default forwarders loaded

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

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

##### NNO-00631: warning: forwarder num has invalid name str, forwarder ignored

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

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

##### NNO-00632: warning: forwarder num has missing address, forwarder ignored

Cause: The server's configuration contains a forwarder description with a missing address.

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

##### NNO-00633: detected fatal delegation loop involving server str

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-00634: received authoritative name str 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-00635: warning: ignoring duplicate forwarder str

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

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-00705: warning: cannot open checkpoint file str, 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-00709: failed delete of cache checkpoint file str, 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-00712: warning: group str 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.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index