/ Copyright (c) 1991, 1996, 1997 by the Oracle Corporation.  All rights reserved.
/
/ $Header: nncus.msg 04-oct-96.11:01:10 rkasamse Exp $
/
/ NAME     
/   nncus.msg
/
/ FUNCTION 
/   Network Naming Client 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.
/
/	NOTE THE FORMATTING characters in this SNMP portion of this file.
/	Spacing is important; many of these messages appear as part of 
/	tabular displays.
/
/ OWNER
/   markl
/
/ MODIFIED
/    eminer     03/18/97 - cleanup, as per Sandy's review
/    rkasamse   10/04/96 - add error message for error code -- 431
/    rkasamse   09/24/96 - add message for the error -- database not accessible
/
/   $Log:  $
/    Revision 1.11  1994/02/07  01:41:24  eminer
/    Change all occurences of 'your customer support representative" to
/     "Worldwide Customer Support"
/
/    Revision 1.10  1993/08/12  21:17:50  markl
/    Add translate yes/no information for NLS translation
/
/    Revision 1.9  1993/07/21  19:28:42  markl
/    Remove old warning messages for invalid boolean and numeric parameters
/
/    Revision 1.8  1993/06/08  01:10:24  markl
/    Cosmetic changes for V1.0.1.0.1
/
/    Revision 1.7  1993/05/24  17:16:56  markl
/    Add messages for stream max-open-connections out of bounds and
/    message-pool-start-size out of bounds
/
/    Revision 1.6  1993/04/06  00:40:17  markl
/    Better text for error 409
/
/
00000, 00000, "normal, successful completion"
/
/						Translate:
/						==========
/ Data stream and network errors 1 - 49		yes
/
00001, 00000, "maximum number of connections already open"
// *Cause: All available name service connections are handling requests.
// *Action: If the problem occurs when running a name server, increase the
// values of names.max_open_connections.  If the problem occurs in a client
// program, turn on tracing and re-execute the failing operation.  If the
// error persists, contact Worldwide Customer Support.
/
00002, 00000, "error listening on stream %s"
// *Cause: The name server was asked to listen on the specified address, and
// failed, probably because the address is malformed, or because it uses a 
// SQL*Net protocol adaptor which has not been installed.
// *Action: Make sure the address is properly formed, and that it uses a
// protocol adaptor which has been installed on your system.
/
00003, 00000, "error opening stream %s"
// *Cause: A name server or client program attempted to open a connection to
// another server and failed, either because the server is down, or because
// the network path to that server is not working.  This error is usually
// displayed underneath an error which describes the problem in more detail.
// *Action: Make sure that the server being connected to is listening on the
// address used, and that there is network connectivity between the two
// end-points.
/
00004, 00000, "connection is broken"
// *Cause: The connection from a name server or client program to another
// server has been broken, either because that server has shut down, or because
// the network path to the server has stopped working.  This error is usually
// displayed underneath an error which describes the problem in more detail.
// *Action: Make sure that the server being connected to is running and
// listening on the address used, and that there is network connectivity 
// between the two end-points.
/
00005, 00000, "cannot initialization stream subsystem"
// *Cause: The name service stream subsystem could not be started, probably
// because of a missing TNS error message file.
// *Action: Check that SQL*Net has been installed properly and that all message
// files are in their proper locations.
/
/						Translate:
/						==========
/ Message transmission errors 50 - 100		yes
/
00050, 00000, "message format error"
// *Cause: A corrupted name server message was received by a name server or 
// the name server program interface.
// *Action: Not normally visible to the user.  For further details, turn on
// tracing and re-execute the failing operation.  If the error persists, 
// contact Worldwide Customer Support.
/
00051, 00000, "message content error"
// *Cause: A corrupted name server message was received by a name server or 
// the name server program interface.
// *Action: Not normally visible to the user.  For further details, turn on
// tracing and re-execute the failing operation.  If the error persists, 
// contact Worldwide Customer Support.
/
00052, 00000, "client and server protocol versions are incompatible"
// *Cause: A name server message with an incompatible protocol version was
// received by a name server or the name server program interface.  This 
// problem will occur when there are clients and servers with widely varying
// protocol versions that are trying to communicate.
// *Action: upgrade older client and server software so it is compatible with
// newer software.
/
00053, 00000, "ASN.1 error encountered while sending or receiving message"
// *Cause: The name server or the name server program interface attempted to
// send or receive a message and failed because of an ASN.1 error.
// *Action: Not normally visible to the user.  For further details, turn on
// tracing and re-execute the failing operation.  If the error persists, 
// contact Worldwide Customer Support.
/
/						   Translate:
/					 	   ==========
/ Name server program interface errors 400 - 499   yes
/
00400, 00000, "memory exhausted"
// *Cause: The program interface has run out of memory.
// *Action: Add more memory or run fewer processes.
/
00401, 00000, "program interface initialization failed"
// *Cause: The name server program interface could not be initialised,
// probably because of a missing TNS or name server error message file.
// *Action: Check that SQL*Net has been installed properly and that all message
// files are in their proper locations.
/
00402, 00000, "program interface de-initialization failed"
// *Cause: An internal error occurred while the name server program
// interface was being de-initialised by an internal function.
// *Action: Not normally visible to the user.  For further details, turn on
// tracing and re-execute the failing operation.  If the error persists, 
// contact Worldwide Customer Support.
/
00403, 00000, "program interface has not been initialised"
// *Cause: An internal function has attempted to de-initialise the name service
// program interface when it has not yet been initialised.
// *Action: Not normally visible to the user.  For further details, turn on
// tracing and re-execute the failing operation.  If the error persists, 
// contact Worldwide Customer Support.
/
00404, 00000, "supplied buffer of size %s is smaller than minimum size %s"
// *Cause: A caller supplied the name server program interface with a memory
// buffer too small for the interface's requirements.  This error is usually
// displayed underneath an error which describes the problem in more detail.
// *Action: Not normally visible to the user.  For further details, turn on
// tracing and re-execute the failing operation.  If the error persists, 
// contact Worldwide Customer Support.
/
00405, 00000, "network failure"
// *Cause: The network connection between the client program and the name
// server has failed, either because the server has shut down, or because
// the network path to the server has stopped working.  This error is usually
// displayed underneath an error which describes the problem in more detail.
// *Action: Contact your name server administrator to make sure that the
// server being connected to is running and listening on the address used, 
// and that there is network connectivity between the two end-points.
/
00406, 00000, "name \"%s\" does not exist"
// *Cause: The user asked for information associated with a global name that
// does not exist.
// *Action: Re-try the failing operation with a global name that exists.
/
00407, 00000, "alias loop in name request"
// *Cause: The name service detected an "alias loop" when trying to retrieve
// information associated with a global name.  An alias loop occurs when 
// an alias name X points to another alias name Y, which in turn points back
// to X, rather than eventually to a global name which contains data.
// *Action: Contact your name server administrator to have the alias loop
// investigated and fixed.
/
00408, 00000, "name \"%s\" exists but desired data does not"
// *Cause: The user asked for information associated with a global name.  The
// name in question exists, but does not contain the desired type of 
// information.
// *Action: Re-try the failing operation with a type which the desired name
// does contain.
/
00409, 00000, "temporary name service failure"
// *Cause: There are no name servers available to handle a client request,
// or a name server was temporarily unable to handle a client request.
// This situation is almost always temporary, and occurs when the program
// interface has issued a name server request and not received a timely
// response from any of its preferred servers.  Such delays can occur due to
// transient network or name server outages or heavy load.
// *Action: Re-try the failing operation.  If the error persists, make sure
// there is network connectivity between the client and its preferred name
// servers, and contact your name server administrator to make sure that those
// name servers are running.
/
00410, 00000, "invalid preferred server address list"
// *Cause: The names.preferred_servers parameter in sqlnet.ora is malformed.
// *Action: Make sure the address list is properly formatted.
/
00411, 00000, "invalid default domain name \"%s\""
// *Cause: The names.default_domain parameter in sqlnet.ora is invalid.
// *Action: Make sure the parameter value is a valid global name.  See your
// documentation for the characters which may be used in a global name.
/
00412, 00000, "invalid name \"%s\""
// *Cause: The name server program interface was given an invalid global name 
// to process.
// *Action: Supply a valid domain name.  If the error is caused by an internal
// function, contact Worldwide Customer Support.
/
00413, 00000, "general failure"
// *Cause: A name server program interface error occured which did not fall
// under the heading of any other more specific error condition.  The error
// will usually be followed by more specific lower-level information.
// *Action: Not normally visible to the user.  For further details, turn on
// tracing and re-execute the failing operation.  If the error persists, 
// contact Worldwide Customer Support.
/
00414, 00000, "invalid name-value binding string \"%s\""
// *Cause: A caller provided the name server program interface with an invalid
// name-value binding string value.
// *Action: Not normally visible to the user, except when using the name server
// control program.  If the error occurs when using the control program, 
// retry the failing operation with a valid name-value binding string 
// argument.  Otherwise, turn on tracing and re-execute the failing operation.
// If the error persists, contact Worldwide Customer Support.
/
00415, 00000, "section identifier %s is invalid, must be between %s and %s"
// *Cause: An internal function has called the name server program interface
// with illegal arguments.
// *Action: Not normally visible to the user.  For further details, turn on
// tracing and re-execute the failing operation.  If the error persists, 
// contact Worldwide Customer Support.
/
00416, 00000, "user callback function returned error number %s"
// *Cause: An internal function has called the name server program interface
// with illegal arguments.
// *Action: Not normally visible to the user.  For further details, turn on
// tracing and re-execute the failing operation.  If the error persists, 
// contact Worldwide Customer Support.
/
00417, 00000, "name \"%s\" already exists"
// *Cause: A caller has attempted to create a new global name, and that name
// already exists.
// *Action: Not normally visible to the user, except when using the name server
// control program.  If the error occurs when using the control program, 
// retry the failing operation with a name that does not already exist.  
// Otherwise, turn on tracing and re-execute the failing operation.  If the
// error persists, contact Worldwide Customer Support.
/
00418, 00000, "name \"%s\" cannot be modified because it has children"
// *Cause: A caller has attempted to delete or rename a global name, and that
// name cannot be modified because it has child names underneath it in the name
// space.
// *Action: Not normally visible to the user, except when using the name server
// control program.  If the error occurs when using the control program, 
// retry the failing operation with a name that is a leaf node.
// Otherwise, turn on tracing and re-execute the failing operation.  If the
// error persists, contact Worldwide Customer Support.
/
00419, 00000, "authoritative server is unreachable"
// *Cause: A name server request cannot be processed because the server which
// received the operation does not own the name specified in the request and
// cannot locate the server which does own the name.  The error is almost
// always transient, and occurs either because the path between the server 
// receiving the request and the request's final destination has been 
// interrupted, or because the final destination is down.
// *Action: Not normally visible to the user, except when using the name server
// control program.  Because the error is typically a transient one, retrying
// the failing operation will usually work.  If the failure persists, the
// name server which is allowed to process the failing operation is probably
// shut down or unreachable.  Contact your name server administrator to make
// sure that your site's name servers are running, and are properly configured.
/
00420, 00000, "operation not allowed"
// *Cause: A name server request cannot be processed because the server which
// received the operation is not allowed to process it.  The problem typically
// occurs when an administrator has disabled request processing at a particular
// server for some reason.
// *Action: Contact your name server administrator to determine why server
// request processing has been disabled.
/
00421, 00000, "invalid modification directive %s, must be between %s and %s"
// *Cause: An internal function has called the name server program interface
// with illegal arguments.
// *Action: Not normally visible to the user.  For further details, turn on
// tracing and re-execute the failing operation.  If the error persists, 
// contact Worldwide Customer Support.
/
00422, 00000, "invalid data type name \"%s\""
// *Cause: A caller has provided an invalid data type name to the name server
// program interface.
// *Action: Not normally visible to the user, except when using the name server
// control program.  If the error occurs when using the control program, 
// retry the failing operation with a valid type name.  Otherwise, turn on
// tracing and re-execute the failing operation.  If the error persists, 
// contact Worldwide Customer Support.
/
00423, 00000, "invalid data item syntax code %s"
// *Cause: A caller has provided an invalid data type code to the name server
// program interface.
// *Action: Not normally visible to the user, except when using the name server
// control program.  If the error occurs when using the control program, 
// retry the failing operation with a valid type name.  Otherwise, turn on
// tracing and re-execute the failing operation.  If the error persists, 
// contact Worldwide Customer Support.
/
00424, 00000, "invalid address \"%s\""
// *Cause: A caller provided the name server program interface with an invalid
// address value.
// *Action: Not normally visible to the user, except when using the name server
// control program.  If the error occurs when using the control program, 
// retry the failing operation with a valid address argument.  Otherwise,
// turn on tracing and re-execute the failing operation.  If the error
// persists, contact Worldwide Customer Support.
/
00425, 00000, "meta-data violation"
// *Cause: A caller issued a name server modification request and that request
// cannot be processed because it would violate data type meta-data 
// constraints.
// *Action: Not normally visible to the user, except when using the name server
// control program.  If the error occurs when using the control program, 
// examine the meta-data constraints for the data type being operated upon
// and don't violate them.  Examples of typical constraint violations are
// attempts to add a new data item to a name which already contains alias 
// information, or attempts to add alias information to a name which already
// contains other data, or attempts to replace a data item with another item
// that has the wrong syntax.  If the error occurs outside the control program,
// turn on tracing and re-execute the failing operation.  If the error
// persists, contact Worldwide Customer Support.
/
00426, 00000, "no such data type"
// *Cause: A caller attempted to create a data item, and could not because
// the data item's type does not exist.
// *Action: Not normally visible to the user, except when using the name server
// control program.  If the error occurs when using the control program, 
// retry the operation with an existent data type.  Otherwise, turn on tracing
// and re-execute the failing operation.  If the error persists, contact
// Worldwide Customer Support.
/
00427, 00000, "server does not support this version of the protocol"
// *Cause: A name server message with an incompatible protocol version was
// received by a name server or the name server program interface.  This 
// problem will occur when there are clients and servers with widely varying
// protocol versions that are trying to communicate.
// *Action: upgrade older client and server software so it is compatible with
// newer software.
/
00428, 00000, "invalid meta-data data item"
// *Cause: A caller provided the name server program interface with an invalid
// meta-data data item.
// *Action: Not normally visible to the user, except when using the name server
// control program.  If the error occurs when using the control program, 
// retry the failing operation with a valid meta-data argument.  Otherwise,
// turn on tracing and re-execute the failing operation.  If the error
// persists, contact Worldwide Customer Support.
/
00429, 00000, "invalid octet string literal \"%s\""
// *Cause: A caller provided the name server program interface with an invalid
// octet string string value.
// *Action: Not normally visible to the user, except when using the name server
// control program.  If the error occurs when using the control program, 
// retry the failing operation with a valid octet string argument.  Otherwise,
// turn on tracing and re-execute the failing operation.  If the error
// persists, contact Worldwide Customer Support.
/
00430, 00000, "Database not accessible"
// *Cause: When a database is used for consistency between different 
// nameservers, any modify operation should not only modify the cache but also
// the database.  And if the database is not accessible, this error occurs.
// *Action: Not normally visible to the user, except when using the name server
// control program.  If the error occurs when using the control program, 
// make sure database is available and then re-execute the operation. If error
// persists, contact Worldwide Customer Support.
/
00431, 00000, "NS address does not match any of the current addresses"
// *Cause:  When delegating a domain, the address of the  Nameserver
// is provided by the client.  If the nameserver already exists, then
// it already  has address(es) associated with it.  So, the address supplied
// by the client must match one of them.  Otherwise, this error occurs.
// *Action:  Not normally visible to the user, except when using name server
// control program.   If the error occurs when using the control program,
// either provide an one of the existing addresses of the name server or
// delegate the domain to a new nameserver.
/
/ Miscellaneous common name service library errors 500 - 519
/
00500, 00000, "warning: \"%s\" parameter value is illegal, setting to %s"
// *Cause: The named parameter value is invalid.
// *Action: Make sure the parameter value is formatted correctly.  Valid
// choices for boolean parameter values are TRUE, FALSE, YES, NO, ON, and OFF.
/
00501, 00000, "warning: \"%s\" parameter value must be between %lu and %lu, setting to %lu"
// *Cause: The named parameter value is invalid or outside legal boundary
// values.
// *Action: Make sure the parameter value is a number, and falls between
// valid minimum and maximum values, as specified in the error text.
/
/ Miscellaneous national text   700 - 749
/
/ The following text is substituted into various server and controller messages
/ as needed.
/ 
00700, 00000, "day"
00701, 00000, "days"
00702, 00000, "hour"
00703, 00000, "hours"
00704, 00000, "minute"
00705, 00000, "minutes"
00706, 00000, "second"
00707, 00000, "seconds"
00708, 00000, "yes"
00709, 00000, "no"
00710, 00000, "not set"
00711, 00000, "on"
00712, 00000, "off"
00713, 00000, "now"
