Oracle Names Control Utility (NNL-00001 to 01073)

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.