/ Copyright (c) 1991, 1996, 1997, 1998 by the Oracle Corporation.  All rights reserved.
/
/ $Header: nnous.msg 05-mar-97.20:18:12 vjoshi Exp $
/
/ NAME     
/   nnous.msg
/
/ FUNCTION 
/   ONRS server US error message file
/
/ NOTES
/       Message text should be limited to a maximum of 76 characters.
/	Messages containing embedded % directives should not overrun
/	the 76 character limit unless they signal unusual errors
/	which do not occur as part of user applications.  For example,
/	startup errors and system-dependent errors can probably get
/	away with longer message text.
/
/ OWNER
/   markl
/
/ MODIFIED
/    eminer     11/06/98 - drop references to impossible OCI errors
/    vjoshi     03/05/97 - save_config changes.
/    eminer     12/18/96 - fill out the OCI related messages
/    rkasamse   09/10/96 - Add OCI error messages
/
/   $Log:  $
/    Revision 1.30  1995/05/31  16:46:43  eminer
/    add a message for group checkpoint failure
/
/    Revision 1.29  1994/08/30  21:25:44  eminer
/    shorten messages longer than 76 chars
/    ./
/
/    Revision 1.28  1994/08/30  20:58:04  eminer
/    correct spelling errors, bug 217250
/
/    Revision 1.27  1994/04/14  01:15:54  eminer
/    Revise message 269; config database no longer needs an exact match,
/     and add mesg 271 for logging names.ora/ROS-doc mismatch.
/
/    Revision 1.26  1994/02/07  02:49:05  eminer
/    Change all occurences of "SQL*Net configuiartion tool" to
/     "Oracle Network Manager".
/
/    Revision 1.25  1994/02/07  01:41:24  eminer
/    Change all occurences of 'your customer support representative" to
/     "Worldwide Customer Support"
/
/
00000, 00000, "normal, successful completion"
/
/						Translate:
/						==========
/ Loader errors 50 - 149			yes
/
00050, 00000, "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.
/
00051, 00000, "domain count %d exceeds maximum of %d, first %d 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.
/
00052, 00000, "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.
/
00053, 00000, "duplicate domain description for domain \"%s\""
// *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.
/
00054, 00000, "invalid domain name \"%s\""
// *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.
/
00055, 00000, "invalid domain minimum TTL \"%s\""
// *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.
/
00056, 00000, "warning: domain minimum TTL must be between %lu and %lu, set to %lu 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.
/
00057, 00000, "loading and verifying topology data"
// *Cause: An informational message written to the log file during normal
// server startup.
// *Action: none
/
00058, 00000, "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.
/
00059, 00000, "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.
/
00060, 00000, "loading server topology from checkpoint file \"%s\""
// *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
/
00061, 00000, "loading data for domain \"%s\""
// *Cause: An informational message written to the log file during normal
// server startup.
// *Action: none
/
00062, 00000, "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.
/
00063, 00000, "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.
/
00064, 00000, "loading domain data from checkpoint file \"%s\""
// *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
/
00065, 00000, "loading cached data from checkpoint file \"%s\""
// *Cause: An informational message written to the log file during normal
// server startup.
// *Action: none
/
00066, 00000, "server will perform reload check of administrative region in %lu 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
/
00067, 00000, "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
/
00068, 00000, "warning: administrative region check failed, next check in %lu 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.
/
00069, 00000, "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.
/
00070, 00000, "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
/
/ Domain configuration errors
/
00080, 00000, "domain \"%s\" 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.
/
00081, 00000, "domain \"%s\" 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.
/
00082, 00000, "domain \"%s\" is missing my name \"%s\" 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.
/
00083, 00000, "domain \"%s\" server \"%s\" 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.
/
00084, 00000, "domain \"%s\" 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.
/
/
/ Other loader errors and messages
/
00104, 00000, "line %s: 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.
/
00105, 00000, "line %s: invalid name \"%s\", 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.
/
00106, 00000, "line %s: invalid TTL \"%s\", 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.
/
00107, 00000, "line %s: 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: none
/
00108, 00000, "line %lu: TTL of %lu seconds below domain minimum %lu, 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.
/
00109, 00000, "line %s: invalid data type name \"%s\", 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.
/
00110, 00000, "line %s: unknown data type \"%s\", 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.
/
00111, 00000, "line %s: data type \"%s\" has syntax \"%s\", should be \"%s\", 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.
/
00112, 00000, "line %s: ignored duplicate data of type \"%s\""
// *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.
/
00113, 00000, "line %s: 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.
/
00114, 00000, "line %s: 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.
/
00115, 00000, "line %s: single-value data type \"%s\", 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.
/
00116, 00000, "line %s: data type \"%s\" 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.
/
00117, 00000, "line %s: 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.
/
00118, 00000, "line %s: data length %s exceeds maximum of %s, 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.
/
00119, 00000, "line %s: server not authoritative for name \"%s\", 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.
/
00120, 00000, "line %s: topology name \"%s\" 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.
/
/
/						Translate:
/						==========
/ Hint errors, 150 - 199			yes
/
00150, 00000, "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.
/
00151, 00000, "warning: ignoring hint for domain \"%s\", 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.
/
00152, 00000, "warning: hint count %d exceeds maximum of %d, first %d 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.
/
00153, 00000, "warning: hint domain %d has invalid name \"%s\", hint domain ignored"
// *Cause: The server's configuration contains a hont 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.
/
00154, 00000, "warning: hint %d has invalid server name \"%s\", 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.
/
00155, 00000, "warning: hint %d 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.
/
00156, 00000, "warning: hint %d address length %d exceeds maximum of %d, 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.
/
00157, 00000, "warning: hint %d 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.
/
00158, 00000, "warning: hint domain count %d exceeds maximum of %d, first %d 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.
/
00159, 00000, "warning: ignoring duplicate hint domain %d name \"%s\""
// *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.
/
00160, 00000, "warning: ignoring duplicate hint server \"%s\""
// *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.
/
/						                Translate:
/					                	==========
/ configuration database and admin region errors 250 - 299	yes
/
00250, 00000, "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.
/
00251, 00000, "missing administrative region parameter %s"
// *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.
/
00252, 00000, "invalid administrative region parameter %s value \"%s\""
// *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.
/
00253, 00000, "administrative region parameter %s length %s exceeds maximum of %s"
// *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.
/
00254, 00000, "warning: parameter %s value must be between %lu and %lu, set to %lu 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.
/
00255, 00000, "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.
/
00256, 00000, "using administrative region \"%s\""
// *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
/
00257, 00000, "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.
/
00258, 00000, "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.
/
00259, 00000, "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
/
00260, 00000, "loading configuration data from checkpoint file \"%s\""
// *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
/
00261, 00000, "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.
/
00262, 00000, "warning: cannot write checkpoint file \"%s\""
// *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.
/
00263, 00000, "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.
/
00264, 00000, "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.
/
00265, 00000, "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.
/
00266, 00000, "cannot find document \"%s\" 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.
/
00267, 00000, "warning: configuration database contains no data for server \"%s\""
// *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.
/
00268, 00000, "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
/
00269, 00000, "configuration database is version %s, server requires at least version %s"
// *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.
/
00270, 00000, "ORACLE error %s"
// *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.
/
00271, 00000, "warning: names.ora region is version %s, network definition is version %s"
// *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.
/
/						Translate:
/						==========
/ Server errors 300 - 349			yes
/
00300, 00000, "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.
/
00301, 00000, "server will shut down in %lu seconds"
// *Cause: An informational message written to the log file when the server
// receives a shutdown request from the Oracle Names control program.
// *Action: none
/
00302, 00000, "server stopped"
// *Cause: An informational message written to the log file when the server
// shuts down.
// *Action: none
/
00303, 00000, "server \"%s\" started with process ID %lu"
// *Cause: An informational message written to the log file when the server
// successfully starts up.
// *Action: none
/
00304, 00000, "listen address %s length %s exceeds maximum of %s"
// *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.
/
00305, 00000, "trace level changed from %u to %u"
// *Cause: An informational message written to the log file when the server
// changes its trace level in response to a request from the Oracle Names 
// control program.
// *Action: none
/
00306, 00000, "server shutdown countdown aborted"
// *Cause: An informational message written to the log file whenever
// the Oracle Names control program halts a shutdown request previously sent
// to the server
// *Action: none
/
00307, 00000, "invalid server name \"%s\""
// *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.
/
00308, 00000, "server will restart in %lu seconds"
// *Cause: An informational message written to the log file when the server
// receives a restart request from the Oracle Names control program.
// *Action: none
/
00309, 00000, "server restarting"
// *Cause: An informational message written to the log file when the server
// restarts.
// *Action: none
/
00310, 00000, "server restart countdown aborted"
// *Cause: An informational message written to the log file whenever
// the Oracle Names control program halts a restart request previously sent
// to the server
// *Action: none
/
00311, 00000, "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.
/
00312, 00000, "listen address %s 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.
/
00313, 00000, "server password length %s exceeds maximum of %s"
// *Cause: the server's password length exceeds an internal limit.
// *Action: An internal error not normally visible to the user.  Contact
// Worldwide Customer Support.
/
00314, 00000, "error changing trace level from %u to %u, 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.
/
00315, 00000, "server is listening on address %s"
// *Cause: An informational message written to the log file during server
// startup.
// *Action: none
/
00316, 00000, "statistic counter reset disabled"
// *Cause: An informational message written to the log file when the server
// disables statistic counter resetting in response to a request from the
// Oracle Names control
// program.
// *Action: none
/
00317, 00000, "statistic counter reset interval changed to %lu seconds"
// *Cause: An informational message written to the log file when the server
// changes its statistic counter reset interval in response to a request from
// the Oracle Names control program.
// *Action: none
/
00318, 00000, "overriding next statistic counter reset, resetting in %lu seconds"
// *Cause: An informational message written to the log file when the server
// resets its statistic counters in response to a request from the Oracle Names
// control program.
// *Action: none
/
00320, 00000, "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.
/
00321, 00000, "statistic counter dump disabled"
// *Cause: An informational message written to the log file when the server
// disables statistics dumping in response to a request from the Oracle
// Names control program.
// *Action: none
/
00322, 00000, "statistic counter dump interval changed to %lu seconds"
// *Cause: An informational message written to the log file when the server
// changes its statistic dump interval in response to a request from the Oracle
// Names control program.
// *Action: none
/
00323, 00000, "overriding next statistic counter dump, dumping in %lu seconds"
// *Cause: An informational message written to the log file when the server
// dumps its statistic counters in response to a request from the Oracle Names
// control program.
// *Action: none
/
00326, 00000, "server statistic counter dump follows"
// *Cause: An informational message written to the log file at the beginning
// of a statistic dump.  The message is followed by a set of server statistics,
// and ends with another informational message indicating the dump has 
// finished.
// *Action: none
/
00327, 00000, "server statistic counter dump ends"
// *Cause: An informational message written to the log file at the end
// of a statistic dump.  The message is preceded by a set of server statistics.
// *Action: none
/
00328, 00000, "server has reset statistic counters to zero"
// *Cause: An informational message written to the log file when the server
// resets its statistic counters to zero in response to a request from the
// Oracle Names control program.
// *Action: none
/
00329, 00000, "server will save the config file in %lu seconds"
// *Cause: An informational message written to the log file when the server
// saves the config to config file in response to a request from the 
// Oracle Names control program.
// *Action: none
/
00330, 00000, "server saved the config file \"%s\"."
// *Cause: An informational message written to the log file when the server
// saves the config to config file in response to a request from the 
// Oracle Names control program.
// *Action: none
/
00331, 00000, "error saving new value %s of %s to the save config table."
// *Cause: An informational message written to the log file when the a set 
// operation is performed and the change cannot be saved in the save config
// ptable, but should be.
// *Action: none
/						Translate:
/						==========
/ Message Processor Errors 600 - 699		yes
/
00600, 00000, "warning: forwarder count %d exceeds maximum of %d, first %d 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.
/
00601, 00000, "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.
/
00602, 00000, "warning: forwarder %d 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.
/
00603, 00000, "enabling all request processing"
// *Cause: An informational message written to the log file when the server
// enables request processing in response to a request from the Oracle Names
// control program.
// *Action: none
/
00604, 00000, "disabling all request processing"
// *Cause: An informational message written to the log file when the server
// disables request processing in response to a request from the Oracle Names
// control program.
// *Action: none
/
00605, 00000, "enabling modification requests"
// *Cause: An informational message written to the log file when the server
// enables modification-request processing in response to a request from the
// Oracle Names control program.
// *Action: none
/
00606, 00000, "disabling modification requests"
// *Cause: An informational message written to the log file when the server
// disables modification-request processing in response to a request from the
// Oracle Names control program.
// *Action: none
/
00607, 00000, "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: none
/
00608, 00000, "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.
/
00609, 00000, "warning: forwarder %d address length %d exceeds maximum of %d, 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.
/
00610, 00000, "detected possible alias loop involving name \"%s\""
// *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.
/
00611, 00000, "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: none
/
00612, 00000, "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: none
/
00613, 00000, "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: none
/
00614, 00000, "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: none
/
00615, 00000, "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: none
/
00616, 00000, "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: none
/
00617, 00000, "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: none
/
00618, 00000, "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: none
/
00622, 00000, "warning: too many auto-refresh failures for name \"%s\", 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.
/
00623, 00000, "setting auto-refresh retry interval to %lu 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: none
/
00624, 00000, "setting auto-refresh expiration period to %lu 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: none
/
00625, 00000, "overriding auto-refresh of name \"%s\", type \"%s\", refresh in %lu 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: none
/
00626, 00000, "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
/
00627, 00000, "cancelling auto-refresh of name \"%s\", type \"%s\""
// *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: none
/
00628, 00000, "setting maximum reforwards per query to %lu"
// *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: none
/
00629, 00000, "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.
/
00630, 00000, "setting request-processing delay to %lu 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: none
/
00631, 00000, "warning: forwarder %d has invalid name \"%s\", 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.
/
00632, 00000, "warning: forwarder %d 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.
/
00633, 00000, "detected fatal delegation loop involving server \"%s\""
// *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.
/
00634, 00000, "received authoritative name \"%s\" 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.
/
00635, 00000, "warning: ignoring duplicate forwarder \"%s\""
// *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.
/
/						Translate:
/						==========
/ Cache Errors 700 - 799			yes
/
00700, 00000, "warning: cannot checkpoint the cache, trying again in %lu 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.
/
00701, 00000, "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.
/
00702, 00000, "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: none
/
00703, 00000, "checkpoint interval changed to %lu 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: none
/
00705, 00000, "warning: cannot open checkpoint file \"%s\", 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.
/
00706, 00000, "overriding next cache checkpoint, checking in %lu 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: none
/
00707, 00000, "server's cache will be flushed in %lu 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: none
/
00708, 00000, "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: none
/
00709, 00000, "failed delete of cache checkpoint file \"%s\", 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.
/
00710, 00000, "server's cache will be dumped to the trace file in %lu 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: none
/
00711, 00000, "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: none
/
00712, 00000, "warning: group %s 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.
/
/
//OCI Errors :  800 - 899
/
00800, 00000, "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.
/
00801, 00000, "Error: OCI_SUCCESS_WITH_INFO"
// *Cause: Diagnostic information was returned from OCI during region
// database access.
// *Action: none
/
00802, 00000, "Error: OCI_NEED_DATA"
// *Cause: The server did not provide sufficient data to the OCI interface
// while accesing the region database.
// *Action: An internal error not normally visible to the user.  Contact
// Worldwide Customer Support.
/
00803, 00000, "Error: OCI_INVALID_HANDLE"
// *Cause: The server called OCI with an invalid handle whilc accessing the
// region database.
// *Action: An internal error not normally visible to the user.  Contact
// Worldwide Customer Support.
/
00804, 00000, "Error: OCI_STILL_EXECUTE"
// *Cause: An OCI operation between the server and the database is still in
// progress.
// *Action: none
/
00805, 00000, "Error: OCI_CONTINUE"
// *Cause: Not possible.
// *Action: none
/
00806, 00000, "Error: OCI_ERROR \"%s\""
// *Cause: An OCI occurred 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 Worldwide Customer Support.
/
00807, 00000, "Error: OCI_NO_DATA "
// *Cause: Not possible.
// *Action: none
/
