Oracle Names Error Messages
This chapter describes the messages generated by:
- the Oracle Names client, and those common to both client and server
- the Oracle Names Control Utility
- the Oracle Names server's Network Management Protocol, which is the part of the Names server that handles SNMP queries. Most of these are internal errors not normally visible to the user.
- Oracle Names server Network Presentation Layer. Most of these are internal errors not normally visible to the user.
Oracle Names Server (NNO-00050 to 00711)
NNO-00050 serious errors in configuration data, server cannot run
| Cause: | The server's configuration data has a problem of some sort which prevents the server from starting. | |
| Action: | Previous error messages in the log file will specify the exact problems leading to the shutdown. The problem most frequently occurs when the network is broken up into multiple administrative regions and the delegation points are incorrect. Read the Oracle Names documentation sections on region delegation and ensure that their directions are being followed correctly. | |
NNO-00051 domain count num exceeds maximum of num, first num will be loaded
| Cause: | The server's configuration contains more domains than the server can support. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00052 invalid domain description list
| Cause: | The server's configuration contains an invalid domain description list. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00053 duplicate domain description for domain domain_name
| Cause: | The server's configuration contains duplicate domain descriptions in the domain description list. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00054 invalid domain name domain_name
| Cause: | The server's configuration contains a domain description with an invalid name. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00055 invalid domain minimum TTL num
| Cause: | The server's configuration contains a domain description with an invalid minimum TTL. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00056 warning: domain minimum TTL must be between num and num, set to num seconds
| Cause: | The server's configuration contains a domain description with an invalid minimum TTL. This error is not fatal; the server will automatically set the TTL to a default value which is suitable for most uses. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00058 warning: cannot load topology data from configuration database
| Cause: | An error was encountered while trying to load the server's topology data from the configuration database. If more information is available, it will appear under this error. This error will cause the server to shut down. | |
| Action: | Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the names.no_region_database parameter set to TRUE. If no checkpoint data is available, the server will shut down. | |
NNO-00059 cannot construct topology checkpoint file name
| Cause: | The server could not construct a system-dependent file name. | |
| Action: | An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support. | |
NNO-00060 loading server topology from checkpoint file checkpoint_file
| Cause: | An informational message written to the log file when the server cannot load from the ROS data store and is instead reading from its most recent topology checkpoint file. | |
| Action: | While the message is informational in nature, it indicates that the server was unable to contact its ROS data store, which is not normal. If the ROS data store is a file, make sure that file is accessible to the server. The file's name is set in the Oracle Network Manager. If the ROS data store is an RDBMS, make sure that the RDBMS 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 RDBMS. | |
NNO-00062 cannot load domain data from configuration database
| Cause: | An error was encountered while trying to load the server's domain data from the configuration database. If more information is available, it will appear under this error. This error will cause the server to shut down. | |
| Action: | Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the names.no_region_database parameter set to TRUE. If no checkpoint data is available, the server will shut down. | |
NNO-00063 cannot construct domain checkpoint file name
| Cause: | The server could not construct a system-dependent file name. | |
| Action: | An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support. | |
NNO-00064 loading domain data from checkpoint file checkpoint_file
| Cause: | An informational message written to the log file when the server cannot load from the ROS data store and is instead reading from its most recent domain checkpoint file. | |
| Action: | While the message is informational in nature, it indicates that the server was unable to contact its ROS data store, which is not normal. If the ROS data store is a file, make sure that file is accessible to the server. The file's name is set in the Oracle Network Manager. If the ROS data store is an RDBMS, make sure that the RDBMS 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 RDBMS. | |
NNO-00068 warning: administrative region reload check failed, next check in num seconds
| Cause: | This warning is issued whenever the server fails to connect to the ROS data store and 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: | If the ROS data store is a file, make sure that file is accessible to the server. The file's name is set in the Oracle Network Manager. If the ROS data store is an RDBMS, make sure that the RDBMS 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 RDBMS. | |
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 ROS data store. The server disables reload checking. Reload checking can later be re-enabled from the Oracle Network Manager or the Oracle Names control program. | |
| Action: | If the ROS data store is a file, make sure that file is accessible to the server. The file's name is set in the Oracle Network Manager. If the ROS data store is an RDBMS, make sure that the RDBMS 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 RDBMS. | |
NNO-00080 domain domain_name cannot be delegated because its parent is already delegated
| Cause: | An internal delegation error has occurred. Delegation is controlled by the Oracle Network Manager, which enforces correct delegation rules. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00081 domain domain_name has no name servers
| Cause: | An internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00082 domain name is missing my name name as a name server
| Cause: | An internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00083 domain name server name has no addresses
| Cause: | An internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00084 domain name is not in the authoritative domain list
| Cause: | An internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00104 line num syntax error, data ignored
| Cause: | The server found a syntax error its domain data. This message will also appear if the server's internal checkpoint files become corrupted. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00105 line num invalid name name, data ignored
| Cause: | The server found an invalid global name in its domain data. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support | |
NNO-00106 line num invalid TTL num, data ignored
| Cause: | The server found an invalid TTL in its domain data. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00107 line num 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. | |
NNO-00108 line num TTL of num seconds below domain minimum num using minimum
| Cause: | The server found an invalid TTL value in its domain data. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00109 line invalid data type name name, data ignored
| Cause: | The server found an invalid data type name in its domain data. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00110 line num unknown data type name, data ignored
| Cause: | The server found an unknown data type in its domain data. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00111 line num data type name has syntax name, should be name, data ignored
| Cause: | The server found an invalid data type syntax in its domain data. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00112 line num ignored duplicate data of type name
| Cause: | The server found a duplicate record in its domain data. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00113 line num alias data already exists, all other data ignored
| Cause: | The server found a alias and non-alias data with the same global name in its domain data. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00114 line num other data exists, alias data ignored
| Cause: | The server found a alias and non-alias data with the same global name in its domain data. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00115 line num single-value data type name, other instances ignored
| Cause: | The server found more than one record with the same name and type, when the type allows only a single record with a particular name. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00116 line num data type name 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. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00117 line num missing data type, data ignored
| Cause: | The server found a record with a missing data type in its domain data. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00118 line line_num data length num exceeds maximum of num, data ignored
| Cause: | The server found a record whose length exceeds an internal limit. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00119 line line_num server not authoritative for name num, data ignored
| Cause: | The server found a global name in its domain data for which it is not authoritative. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00120 line line_num topology name record_name not allowed here
| Cause: | The server found an invalid record in its domain data. The record in question is not loaded, but the server continues to load data. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00150 warning: invalid hint list, no hints loaded
| Cause: | The server's configuration contains an invalid hint description list. The server will continue to run, but will not load any hints. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00151 warning: ignoring hint for domain name, server is authoritative
| Cause: | The server's configuration contained a hint for a domain in the server's administrative region. The hint is ignored and the server continues to run. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00152 warning: hint count num exceeds maximum of num, first num will be loaded
| Cause: | There are too many hints in the server's hint list. The server will load a specified maximum number of hints, ignore the rest, and continue running. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00153 warning: hint domain name has invalid name name, hint domain ignored
| Cause: | The server's configuration contains a hint domain with an invalid name. The domain is ignored and the server continues to run. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00154 warning: hint name has invalid server name name, hint ignored
| Cause: | The server's configuration contains a hint with an invalid server name. The hint is ignored and the server continues to run. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00155 warning: hint name has missing address, hint ignored
| Cause: | The server's configuration contains a hint with no server address. The hint is ignored and the server continues to run. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00156 warning: hint name address length num exceeds maximum of num, hint ignored
| Cause: | The server's configuration contains a hint whose address length exceeds an internal limit. The hint is ignored and the server continues to run. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00157 warning: hint name has invalid address, hint ignored
| Cause: | The server's configuration contains a hint with an invalid address. The hint is ignored and the server continues to run. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00158 warning: hint domain count num exceeds maximum of num first num will be loaded
| Cause: | The server's hint domain list is too long. The server will load a specified maximum number of hint domains, ignore the rest, and continue running. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00159 warning: ignoring duplicate hint domain name name name
| Cause: | The server's hint domain list contains a duplicate domain. The duplicate is ignored and the server continues running. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00160 warning: ignoring duplicate hint server
| Cause: | The server's hint server list contains a duplicate server. The duplicate is ignored and the server continues running. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00250 invalid administrative region description
| Cause: | The server encountered an invalid administrative region description during startup. This error will prevent the server from starting. The administrative region description is stored in the server's names.ora configuration file. | |
| Action: | Make sure that the names.admin_region parameter in names.ora is correct. The names.ora file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Worldwide Customer Support. | |
NNO-00251 missing administrative region parameter name
| Cause: | The server's administrative region description is missing a required parameter. This error will prevent the server from starting. The administrative region description is stored in the server's names.ora configuration file. | |
| Action: | Make sure that the names.admin_region parameter in names.ora is correct. The names.ora file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Worldwide Customer Support. | |
NNO-00252 invalid administrative region parameter name value name
| Cause: | The server encountered an invalid administrative region parameter. This error will prevent the server from starting. The administrative region description is stored in the server's names.ora configuration file. | |
| Action: | Make sure that the names.admin_region parameter in names.ora is correct. The names.ora file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Worldwide Customer Support. | |
NNO-00253 administrative region parameter name length num exceeds maximum of name
| Cause: | The server encountered an administrative region parameter whose length exceeds an internal limit. This error will prevent the server from starting. The administrative region description is stored in the server's names.ora configuration file. | |
| Action: | Make sure that the names.admin_region parameter in names.ora is correct. The names.ora file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Worldwide Customer Support. | |
NNO-00254 warning: parameter num value must be between num and num, set to num seconds
| Cause: | The server encountered an administrative region parameter with an invalid value. The value is set to a default suitable for most applications, and the server continues running. The administrative region description is stored in the server's names.ora configuration file. | |
| Action: | Make sure that the names.admin_region parameter in names.ora is correct. The names.ora file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Worldwide Customer Support. | |
NNO-00255 cannot initialize ROS
| Cause: | The server was unable to initialize ROS during startup. The error prevents the server from running. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00257 warning: cannot get serial number from configuration database
| Cause: | The server encountered an error while trying to get the configuration database's serial number. The error occurs almost always because the server configuration has not been exported from the Oracle Network Manager. 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 Oracle Network Manager has exported a server configuration for this name server. Next, make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. If the error occurs during server startup, you can force startup anyway, with checkpoint data, by starting the server with the names.no_region_database parameter set to TRUE. If no checkpoint data is available, the server will shut down. | |
NNO-00258 cannot load configuration from configuration database
| Cause: | An error was encountered while trying to load the server's configuration from the configuration database. If more information is available, it will appear under this error. This error will cause the server to shut down. | |
| Action: | Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the names.no_region_database parameter set to TRUE. If no checkpoint data is available, the server will shut down. | |
NNO-00259 configuration tables have not been installed or are inaccessible
| Cause: | The configuration database has not been properly installed. | |
| Action: | Make sure the Oracle Network Manager and its database have been properly installed. | |
NNO-00260 loading configuration data from checkpoint file checkpoint_file
| Cause: | An informational message written to the log file when the server cannot load from the ROS data store and is instead reading from its most recent configuration checkpoint file. | |
| Action: | While the message is informational in nature, it indicates that the server was unable to contact its ROS data store, which is not normal. If the ROS data store is a file, make sure that file is accessible to the server. The file's name is set in the Oracle Network Manager. If the ROS data store is an RDBMS, make sure that the RDBMS 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 RDBMS. | |
NNO-00261 cannot construct configuration checkpoint file name
| Cause: | The server could not construct a system-dependent file name. | |
| Action: | An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support. | |
NNO-00262 warning: cannot write checkpoint file checkpoint_file
| 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, and that ROS data store access failures during subsequent startups may prevent the server from running, because the server will have no checkpoint data on which to fall back. | |
| Action: | Check to see that the server has permission to write the file named in the error message. | |
NNO-00263 error from configuration database
| Cause: | The server encountered an error while accessing the configuration database. The error can occur when the database is unavailable, or SQL*Net connectivity to the database is interrupted. | |
| Action: | Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the names.no_region_database parameter set to TRUE. If no checkpoint data is available, the server will shut down. | |
NNO-00264 configuration database query returned no data
| Cause: | The server attempted to fetch data from the configuration database and no data was found. | |
| Action: | The error generally appears underneath a more specific error which will tell you the exact nature of the problem. | |
NNO-00265 warning: cannot load data from checkpoint file
| Cause: | The server was started using checkpoint data, and was unable to read that data. The remaining errors below this one on the error stack provide more specific information about the problem. | |
| Action: | Check to see that the named file exists and that the server has permission to read it. | |
NNO-00266 cannot find document document in configuration database
| Cause: | The server encountered an error while trying to get its configuration ID from the configuration database. The error can occur any time the server is unable to access the configuration database. This error will cause the server to shut down. | |
| Action: | Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the names.no_region_database parameter set to TRUE. If no checkpoint data is available, the server will shut down. | |
NNO-00267 warning: configuration database contains no data for server server_name
| 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 Oracle Network Manager. | |
| Action: | Make sure that the Oracle Network Manager has exported a server configuration for this names server. | |
NNO-00268 warning: configuration database is not used, using checkpoint data instead
| Cause: | An informational message indicating that the server has been started with the names.no_region_database parameter set to TRUE, and that it will use checkpoint data rather than attempting to contact the configuration database. | |
NNO-00269 configuration database is version version, server requires version version
| 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 Oracle Network Manager and re-export your network. The conversion utility will upgrade old documents to a version which can be understood by the Names server. | |
NNO-00270 ORACLE error error
| 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-00300 no listen addresses specified, at least one is required
| Cause: | The server's configuration is missing addresses on which to listen. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00304 listen address address length length exceeds maximum of num
| Cause: | The length of one of the server's listen addresses exceeds an internal limit. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00307 invalid server name server
| Cause: | The server's name is invalid. The name is specified in the server's names.ora configuration file. | |
| Action: | Make sure that the names.server_name parameter in names.ora is correct. The names.ora file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Worldwide Customer Support. | |
NNO-00311 invalid listen address list
| Cause: | The server's configuration contains an invalid listen address list. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00312 listen address address is invalid
| Cause: | The server's configuration contains an invalid listen address. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00313 server password length num exceeds maximum of num
| Cause: | The server's password length exceeds an internal limit. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00314 error changing trace level from num to num, level change ignored
| Cause: | The server encountered an error while changing its trace level in response to a request from the Oracle Names control program. | |
| Action: | An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support. | |
NNO-00320 missing server name parameter
| Cause: | The server could not find a names.server_name parameter. The name is specified in the server's names.ora configuration file. | |
| Action: | Make sure that the names.server_name parameter in names.ora is correct. The names.ora file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Worldwide Customer Support. | |
NNO-00600 warning: forwarder count num exceeds maximum of num, first num will be loaded
| Cause: | The server's configuration contains too many default forwarders. The server loads a specified maximum number of forwarders, ignores the rest, and continues running. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00601 warning: no forwarders, DEFAULT-FORWARDERS-ONLY mode ignored
| Cause: | The server's configuration enables DEFAULT-FORWARDERS-ONLY mode but the configuration contains no default forwarders. The server ignores the request and continues running. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00602 warning: forwarder name has invalid address, forwarder ignored
| Cause: | One of the forwarders in the default forwarder list has an invalid address. The forwarder definition is ignored and the server continues running. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00608 received corrupted message
| Cause: | The server received a corrupted request. The request is ignored. | |
| Action: | Corrupted requests are usually caused by transient network problems. If many corrupted messages are received, turn on tracing for further information. If the errors persist, contact Worldwide Customer Support. | |
NNO-00609 warning: forwarder name address length num, exceeds maximum of num, ignored
| Cause: | The server's configuration contains a forwarder address whose length exceeds an internal limit. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00610 detected possible alias loop involving name name
| Cause: | The server detected an alias loop involving the specified name. An alias loop occurs when an alias "X" points to another alias "Y", which points back to "X" rather than to an address or other name server data. The loop can contain more hops but the basic idea remains the same. Loops occur when administrators mis-enter network data, particularly when an alias in one administrative region points to data in another administrative region. | |
| Action: | Use the Oracle Names control program to query for the specified name. The control program will describe the alias path, and you can use that information to find which names are incorrect and what administrative regions the incorrect data belongs to. | |
NNO-00632 warning: forwarder name has missing address, forwarder ignored
| Cause: | The server's configuration contains a forwarder description with a missing address. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00633 detected fatal delegation loop involving server name
| Cause: | The server detected a fatal delegation loop while forwarding a request. A loop occurs when the server's topology data indicates that it should forward a request to itself. The server immediately shuts down in response to this error. | |
| Action: | An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support. | |
NNO-00634 received authoritative name name when we are its authority
| Cause: | A server "X" received authoritative data from another server "Y" when server "X" is also authoritative for the data. Such situations should never arise because if server "X" is authoritative for the requested data, it should never forward the request to another server. | |
| Action: | An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support. | |
NNO-00635 warning: ignoring duplicate forwarder name
| Cause: | The server's default forwarder list contains a duplicate server. The duplicate is ignored and the server continues running. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNO-00700 warning: cannot checkpoint the cache, trying again in num seconds
| Cause: | The server was unable to perform its normal periodic cache checkpointing, typically because the cache checkpoint file could not be written. The cache checkpoint file name appears as an informational message during server startup. | |
| Action: | Check to see that the server has permission to write the cache checkpoint file, and that there is sufficient disk space for the file to be written. | |
NNO-00701 warning: cannot construct checkpoint file name, checkpointing disabled
| Cause: | The server could not construct a system-dependent file name. | |
| Action: | An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Worldwide Customer Support. | |
NNO-00705 warning: cannot open checkpoint file name, checkpointing disabled
| Cause: | The server was unable to open the named checkpoint file for writing. This problem is typically due to the file system's protection settings. The error is not fatal; it simply means the server will not checkpoint its cache. | |
| Action: | Check to see that the server has permission to write the file named in the error message. | |
NNO-00709 failed delete of cache checkpoint file checkpoint_file, 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. | |
Oracle Names Client and Client/Server (NNC-00001 to 00501)
NNC-00001 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. | |
NNC-00002 error listening on stream num
| 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. | |
NNC-00003 error opening stream num
| 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. | |
NNC-00004 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. | |
NNC-00005 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. | |
NNC-00050 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. | |
NNC-00051 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. | |
NNC-00052 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. | |
NNC-00053 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. | |
NNC-00400 memory exhausted
| Cause: | The program interface has run out of memory. | |
| Action: | Add more memory or run fewer processes. | |
NNC-00401 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. | |
NNC-00402 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. | |
NNC-00403 program interface has not been initialised
| Cause: | 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. | |
NNC-00404 supplied buffer of size num is smaller than minimum size num
| 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. | |
NNC-00405 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. | |
NNC-00406 name name 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. | |
NNC-00407 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. | |
NNC-00408 name name 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. | |
NNC-00409 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. | |
NNC-00410 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. | |
NNC-00411 invalid default domain name name
| 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. | |
NNC-00412 invalid name name
| 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. | |
NNC-00413 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. | |
NNC-00414 invalid name-value binding string name
| 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. | |
NNC-00415 section identifier num is invalid, must be between num and num
| 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. | |
NNC-00416 user callback function returned error number num
| 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. | |
NNC-00417 name name 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. | |
NNC-00418 name name 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. | |
NNC-00419 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. | |
NNC-00420 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. | |
NNC-00421 invalid modification directive name, must be between num and num
| 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. | |
NNC-00422 invalid data type name name
| 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. | |
NNC-00423 invalid data item syntax code num
| 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. | |
NNC-00424 invalid address name
| 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. | |
NNC-00425 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. | |
NNC-00426 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. | |
NNC-00427 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. | |
NNC-00428 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. | |
NNC-00429 invalid octet string literal num
| 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. | |
NNC-00500 warning: name parameter value is illegal, setting to name
| 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. | |
NNC-00501 warning: name parameter value must be between num and num, setting to num
| 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. | |
Oracle Names Control Utility (NNL-00001 to 01073)
NNL-00001 request argument name is invalid
| Cause: | The user entered an invalid request command argument. | |
| Action: | Supply a valid argument. | |
NNL-00002 request argument name is not allowed with this operation
| Cause: | The user entered a request command argument which is not valid with the particular request command. | |
| Action: | Supply a valid argument. | |
NNL-00003 memory exhausted
| Cause: | The program has run out of memory | |
| Action: | Check the amount of available memory on your machine to ensure that there is enough memory to run this executable. If necessary, free up memory by running fewer programs, then try again. | |
NNL-00004 invalid command argument name
| Cause: | The user entered an invalid command argument. | |
| Action: | Supply a valid argument. | |
NNL-00005 no server has been set. Use the SET SERVER command first
| Cause: | The user attempted to issue a command which requires that a default managed Oracle Names server be set first. | |
| Action: | Use the SET SERVER command to set your default server, then reissue the command. Alternatively, if the command allows, re-issue it with a specific server name so the control program does not need to use the default. | |
NNL-00006 timeout, server is not responding
| Cause: | The control program issued a request to an Oracle Names server and no response arrived in a timely fashion. The network connection between the control program and the server may be faulty, the server may be very heavily loaded, or there may be substantial network delays between the control program and the server. The latter is especially true for WAN links. | |
| Action: | Reissue the command; if it continues to fail, check to see that the server being managed is running correctly and that the network connection between the server and the control program is working correctly. | |
NNL-00007 server responded with an error
| Cause: | The control program issued a request to an Oracle Names server and the server responded with an error. | |
| Action: | For further details, turn on tracing and re-execute the failing operation. If the error persists, contact your customer service representative. | |
NNL-00008 request not understood by server
| Cause: | The control program issued a request to an Oracle Names server and the server did not understand the request. | |
| Action: | If the server and the control program have different versions, they may be unable to communicate. Check your documentation for version compatibility constraints. If the server and control program are compatible, turn on tracing for further details, and re-execute the failing operation. If the error persists, contact Worldwide Customer Support. | |
NNL-00009 encryption of server password failed
| Cause: | The control program attempted and failed to encrypt a server password, supplied either through the SET PASSWORD command or the namesctl.server_password configuration parameter. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNL-00010 error getting address for server name
| Cause: | The control program attempted to translate a server name to its corresponding address, and failed. There are a large number of possible causes for the failure. The control program's SQLNET.ORA file must exist in the correct system-specific location, and must be readable by the control program. The file must contain a names.preferred_servers entry with valid name server addresses. If the user has changed managed servers with the SET SERVER command, the new server must be running, and must be able to resolve the address or forward the request to another server which can resolve the address. Alternatively, a TNSNAMES.ORA file with valid name server names and addresses must exist in the correct system-specific location. | |
| Action: | For further details, turn on tracing and re-execute the failing operation. If the error persists, contact your customer service representative. | |
NNL-00011 no server with name name exists
| Cause: | The user issued a SET SERVER request and the current managed Oracle Names server was unable to translate that name into an address. Alternatively, the user issued a control program request to a specific server, and that server's name could not be translated into an address. Both problems are almost always caused by mis-typing the server name. | |
| Action: | Re-issue the request with a valid server name. | |
NNL-00012 invalid name value name
| Cause: | The first argument is a data type, the second is a value. The user supplied an invalid data value of the specified type. | |
| Action: | Re-issue the failing operation with correct data. | |
NNL-00013 not performed, permission denied for supplied password
| Cause: | The user issued a request to an Oracle Names server, and the password supplied with the request was incorrect. | |
| Action: | Check to see that the password sent by the control program to the server is correct for that server. You can set a new password with the SET PASSWORD control program command. | |
NNL-00014 unknown data type name
| Cause: | The user issued a name server request which contained an unknown data type. | |
| Action: | It is possible that the server had no information on the type, but automatically fetched it in response to the failing request. Re-issue the failing request; if the server has in the meantime fetched the appropriate data type information, the error will go away. If the error persists, the data type is probably invalid. | |
NNL-00015 type data_type has name syntax, which has no textual representation
| Cause: | Not all data type syntaxes can be represented as text. This message indicates that the user issued a name server request for a type with an non-textual representation. | |
| Action: | Re-issue the operation with a data type that has a syntax with a textual representation. | |
NNL-00016 cannot start server, error getting program directory's name
| Cause: | The user issued a STARTUP request, but the control program was unable to start the server because it was unable to find the name of the directory where the server executable resides. | |
| Action: | An internal error not normally visible to the user. Contact Worldwide Customer Support. | |
NNL-00017 cannot start server, program program_name does not exist
| Cause: | The user issued a STARTUP request, but the control program was unable to start the server because it was unable to find the server executable. | |
| Action: | Make sure that a copy of the server executable exists in your system's oracle executable directory. | |
NNL-00018 warning: could not contact default name server
| Cause: | The control program was unable to contact its default name server during startup. There are a number of possible causes for this error. The control program's SQLNET.ORA file must exist in the correct system-specific location, and must be readable by the control program. The file must contain a names.preferred_servers entry with valid name server addresses. The first server in the preferred-server list must be running, and there must be network connectivity between the control program and that server. | |
| Action: | Check to see that all of the above are true. If the control program is still unable to contact its default server, turn on tracing and restart the control program. If the error persists, contact Worldwide Customer Support. | |
NNL-00019 warning: server either changed or ignored your request
| Cause: | The user issued a request to an Oracle Names server and that request was altered in some way. Typically the user specified an invalid argument of some sort, and the server either ignored the request, or replaced the invalid argument with a reasonable default. | |
| Action: | Use the control program to check the current state of the value that you attempted to change. The server's log file may also contain information about the exact cause of the problem. Re-issue the operation with correct arguments. | |
NNL-00020 warning: no TNSNAMES.ORA file and no preferred name servers in SQLNET.ORA
| Cause: | The control program was unable to find a TNSNAMES.ORA file and was unable to find a default name server in SQLNET.ORA. The control program will operate in this state, but will be unable to resolve any names until a default server has been set, and that server must be set using its raw TNS address. | |
| Action: | The control program's SQLNET.ORA file must exist in the correct system-specific location, and must be readable by the control program. The file must contain a names.preferred_servers entry with valid name server addresses. The first server in the preferred-server list must be running, and there must be network connectivity between the control program and that server. Alternatively, a TNSNAMES.ORA file with valid name server information must exist in the correct system-specific location. | |
NNL-00022 error changing trace level from num to num level change ignored
| Cause: | The user attempted to change the control program's local trace level, and the program encountered an error while changing the level. Usually the problem is that tracing was enabled for the first time (by changing the trace level from OFF to something else) and the trace file is not writeable by the control program. | |
| Action: | Check to see that the trace file is writeable. Your documentation will tell you the name of the trace file. | |
NNL-00023 SET command is missing an argument
| Cause: | The user attempted to issue a SET command with no argument. | |
| Action: | Supply a valid argument to the SET command. | |
NNL-00024 warning: no preferred name servers in SQLNET.ORA
| Cause: | The control program was unable to find any preferred name servers in SQLNET.ORA, and will therefore not connect to a default server. | |
| Action: | Make sure that the SQLNET.ORA file contains a valid names.preferred_servers entry. | |
Oracle Names Server Network Management Protocol (NMP-00001 to 00011)
NMP-00001 value too big
| Cause: | The SNMP program interface received a value too large for it to process. This error is usually displayed underneath an error which describes in more detail the value which caused the problem. | |
| 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 | |
NMP-00002 no such SNMP variable name
| Cause: | An SNMP request was not processed because one or more of the variable names in the request does not exist. This error is not normally visible to the user except in a trace file, where it is usually part of a "soft" error condition which is normal. | |
| Action: | The error may indicate that a managed server does not support an operation requested by its control program, perhaps because of version incompatibility. For further details, turn on tracing and re-execute the failing operation. If the error persists, and does not occur as part of a "soft" error condition as noted in the trace file, contact Worldwide Customer Support. | |
NMP-00003 bad SNMP variable value
| Cause: | The SNMP program interface received a variable value which has an unsupported data type. This error may occur if a standard SNMP network monitor is sending requests to an Oracle service through an SNMP-to-TNS gateway, and that service cannot understand the requests. | |
| Action: | Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, and occurs when an Oracle control program sends requests to an Oracle service, contact Worldwide Customer Support. | |
NMP-00004 SNMP variable is read only
| Cause: | The user attempted to change a variable value at a remote server, and that variable is read-only. This error is usually displayed underneath an error which describes the problem in more detail. | |
| Action: | Read-only variables may never be modified. | |
NMP-00005 general SNMP error
| Cause: | An SNMP error occured which did not fall under the heading of any other more specific error condition. This error may occur if a standard SNMP network monitor is sending requests to an Oracle service through an SNMP-to-TNS gateway, and that service cannot understand the requests. | |
| Action: | Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, and occurs when an Oracle control program sends requests to an Oracle service, contact Worldwide Customer Support. | |
NMP-00005 general SNMP error
| Cause: | An SNMP error occured which did not fall under the heading of any other more specific error condition. This error may occur if a standard SNMP network monitor is sending requests to an Oracle service through an SNMP-to-TNS gateway, and that service cannot understand the requests. | |
| Action: | Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, and occurs when an Oracle control program sends requests to an Oracle service, contact Worldwide Customer Support. | |
NMP-00006 uninitialized SNMP context
| Cause: | An internal function attempted to use an uninitialize SNMP handle. | |
| 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. | |
NMP-00007 I/O failure
| Cause: | The SNMP program interface attempted to send or receive an SNMP request and was unable to do so because of a network failure of some sort. This error is usually displayed underneath an error which describes the problem in more detail. The problem typically occurs when a control program is attempting to communicate with a service and either that service has unexpectedly terminated or the network path between the control program. | |
| 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. | |
NMP-00008 SNMP message has incorrect version, version 0 is required
| Cause: | The SNMP program interface received a protocol request with an illegal version number. This error may occur if a standard SNMP network monitor is sending malformed requests to an Oracle service through an SNMP-to-TNS gateway. | |
| Action: | Ensure that the management platform in question is sending SNMP requests with the correct version number. If the error persists, and occurs when an Oracle control program sends requests to an Oracle service, contact Worldwide Customer Support. | |
NMP-00009 SNMP initialization failure
| Cause: | The SNMP program interface could not be initialized, either because its error message file could not be found, or because there is a malformed snmp.communities parameter value in the parameter table. | |
| Action: | Check that SQL*Net has been installed properly and that all message files are in their proper locations. Turn on tracing and look for parameter table load errors. | |
NMP-00010 memory exhausted
| Cause: | The program interface has run out of memory. | |
| Action: | Add more memory or run fewer processes. | |
NMP-00011 internal SNMP program interface error
| Cause: | An internal error occurred inside the SNMP program interface. This error is usually displayed underneath an error which describes the problem in more detail. | |
| Action: | Not nomally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support. | |
Oracle Names Server Network Presentation Layer (NPL-00100 to 00420)
NPL-00100 cannot initialize ASN.1 context
| Cause: | The ASN.1 program interface could not be initialized, probably because its error message file could not be found. | |
| Action: | Check that SQL*Net has been installed properly and that all message files are in their proper locations. | |
NPL-00101 uninitialized ASN.1 context
| Cause: | The ASN.1 program interface received an uninitialized ASN.1 handle. | |
| 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. | |
NPL-00102 missing stream functions in ASN.1 context initialization
| Cause: | An internal function improperly attempted to initialize an ASN.1 handle. | |
| 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 | |
NPL-00103 unusable ASN.1 context
| Cause: | The ASN.1 program interface received an unusable ASN.1 handle. | |
| 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. | |
NPL-00300 maximum ASN.1 element nesting depth num exceeded on read
| Cause: | An ASN.1 construct is too complex for the program interface to read. | |
| 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. | |
NPL-00301 maximum ASN.1 element nesting depth num exceeded on write
| Cause: | An ASN.1 construct is too complex for the program interface to write. | |
| 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. | |
NPL-00302 ASN.1 type tag is greater than maximum of 16383
| Cause: | An internal function attempted to create an illegal ASN.1 construct. | |
| 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. | |
NPL-00303 uninitialized ASN.1 class attribute
| Cause: | An internal function attempted to create an illegal ASN.1 construct. | |
| 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. | |
NPL-00304 uninitialized ASN.1 tag attribute
| Cause: | An internal function attempted to create an illegal ASN.1 construct. | |
| 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. | |
NPL-00305 unsupported ASN.1 \"UNIV\" type name
| Cause: | An internal function attempted to create an illegal ASN.1 construct. | |
| 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. | |
NPL-00307 ASN.1 sequence has already been ended on write
| Cause: | An internal function attempted to end an ASN.1 construct prematurely. | |
| 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. | |
NPL-00308 requested ASN.1 class name does not match received class name
| Cause: | An internal function requested an ASN.1 construct different from that received by the ASN.1 protocol engine. | |
| 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. | |
NPL-00309 requested ASN.1 type tag name does not match received type tag name
| Cause: | An internal function requested an ASN.1 construct different from that received by the ASN.1 protocol engine. | |
| 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. | |
NPL-00310 ASN.1 sequence has already been ended on read
| Cause: | An internal function attempted to finish reading an ASN.1 construct which has already been completely read. | |
| 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. | |
NPL-00311 cannot end constructed ASN.1 encoding, num encoding octets unread
| Cause: | An internal function attempted to finish reading an ASN.1 construct prematurely. | |
| 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. | |
NPL-00312 attempt to put ASN.1 \"UNIV\" type with illegal tag num
| Cause: | An internal function attempted to finish reading an ASN.1 construct prematurely. | |
| 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. | |
NPL-00313 requested form name does not match actual form name
| Cause: | An internal function received an ASN.1 construct different from that expected. | |
| 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. | |
NPL-00410 incoming ASN.1 value too large (num octets) to store locally
| Cause: | The ASN.1 protocol engine was unable to translate an ASN.1 construct to its host representation because the construct was too big. | |
| 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. | |
NPL-00411 incoming ASN.1 NULL encoding has nonzero length of num
| Cause: | The ASN.1 protocol engine received a corrupted ASN.1 construct. | |
| 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. | |
NPL-00412 incoming ASN.1 BOOLEAN encoding has incorrect length of num
| Cause: | The ASN.1 protocol engine received a corrupted ASN.1 construct. | |
| 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. | |
NPL-00413 incoming ASN.1 encoding has length num, maximum allowed is num
| Cause: | The ASN.1 protocol engine received an ASN.1 construct too large for it to process. | |
| 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. | |
NPL-00414 incoming ASN.1 type tag is greater than maximum of 16383
| Cause: | The ASN.1 protocol engine received an illegal ASN.1 construct. | |
| 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. | |
NPL-00415 received unsupported ASN.1 INDEFINITE-LENGTH encoding
| Cause: | The ASN.1 protocol engine received an ASN.1 encoding which it could not process because its implementation does not support it. | |
| 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. | |
NPL-00416 received illegal ASN.1 encoding length of num
| Cause: | The ASN.1 protocol engine received a corrupted ASN.1 construct. | |
| 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. | |
NPL-00417 received ASN.1 length octet count greater than maximum of num
| Cause: | The ASN.1 protocol engine received an ASN.1 encoding which it could not process because its implementation does not support it. | |
| 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. | |
NPL-00418 received malformed ASN.1 object identifier
| Cause: | The ASN.1 protocol engine received a corrupted ASN.1 construct. | |
| 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. | |
NPL-00419 received ASN.1 object identifier with sub-identifier that is too large
| Cause: | The ASN.1 protocol engine received an ASN.1 encoding which it could not process because its implementation does not support it. | |
| 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. | |
NPL-00420 received ASN.1 object identifier with more than 256 sub-identifiers
| Cause: | The ASN.1 protocol engine received an ASN.1 encoding which it could not process because its implementation does not support it. | |
| 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. | |
