NNO-00074: downloading region from server string

NNO-00074: downloading region from server string

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

Action: none

NNO-00073: loading server config from region database

NNO-00073: loading server config from region database

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

Action: none

NNO-00072: loading from region database

NNO-00072: loading from region database

Cause: normal

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

NNO-00071: cannot construct cache checkpoint file name

NNO-00071: cannot construct cache checkpoint file name

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

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

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

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

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

Action: none

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

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

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

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

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

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

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

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

NNO-00067: server reload check countdown aborted

NNO-00067: server reload check countdown aborted

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

Action: none

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

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

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

Action: none

NNO-00065: loading cached data from checkpoint file string

NNO-00065: loading cached data from checkpoint file string

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

Action: none

NNO-00064: loading domain data from checkpoint file string

NNO-00064: loading domain data from checkpoint file string

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

Action: none

NNO-00063: cannot construct domain checkpoint file name

NNO-00063: cannot construct domain checkpoint file name

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

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

NNO-00062: cannot load domain data from configuration database

NNO-00062: cannot load domain data from configuration database

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

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

NNO-00061: loading data for domain string

NNO-00061: loading data for domain string

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

Action: none

NNO-00060: loading server topology from checkpoint file string

NNO-00060: loading server topology from checkpoint file string

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

Action: none

NNO-00059: cannot construct topology checkpoint file name

NNO-00059: cannot construct topology checkpoint file name

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

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

NNO-00058: cannot load topology data from configuration database

NNO-00058: cannot load topology data from configuration database

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

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

NNO-00057: loading and verifying topology data

NNO-00057: loading and verifying topology data

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

Action: none

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

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

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

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

NNO-00055: invalid domain minimum TTL string

NNO-00055: invalid domain minimum TTL string

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

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