NNO-00300: no listen addresses specified, at least one is required

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-00272: line string; invalid DIT or DN

NNO-00272: line string; invalid DIT or DN

Cause: There is a syntax error in the DIT or DN provided in the region description.

Action: Correct the error and restart the server.

NNO-00271: warning: names.ora region is version string, network definition is version string

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-00270: ORACLE error string

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-00269: configuration database is version string, server requires at least version string

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-00268: warning: configuration database is not used, using checkpoint data instead

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-00267: warning: configuration database contains no data for server string

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-00266: cannot find document string in configuration database

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-00265: warning: cannot load data from checkpoint file

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-00264: configuration database query returned no data

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-00263: error from configuration database

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-00262: warning: cannot write checkpoint file string

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 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-00261: cannot construct configuration checkpoint file name

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-00260: loading configuration data from checkpoint file string

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

NNO-00259: configuration tables have not been installed or are inaccessible

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-00258: cannot load configuration from configuration database

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-00257: warning: cannot get serial number from region store

NNO-00257: warning: cannot get serial number from region store

Cause: The server encountered an error while trying to get the configuration database s serial number. The error occurs almost always because 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-00256: using administrative region string

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

NNO-00255: cannot initialize ROS

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-00254: warning: parameter string value must be between number and number, set to number seconds

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