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.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading

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 Oracle Support Services.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading

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 Oracle Support Services.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading

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. This is an internal error, not normally visible to the user.

Action: Contact Oracle Support Services.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading

NNL-00010 error getting address for server “string”

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 Oracle Support Services.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading

NNL-00011 no server with name “string” 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 incorrectly typing the server name.

Action: Re-issue the request with a valid server name.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading