NNL-00018: warning: could not contact default name server
- 1 Answers
- 2955 Views
- I also Faced
- E-Mail Answers
Answer / guest
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.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
ORA-07550: sftopn: $CONNECT failure
NCR-03019: NCRO: Unable to initialize thread support
ORA-12416: policy string not found
ORA-01605: missing numbers in clause "string" of string
ORA-13184: failed to initialize tessellation package
DRG-10707: a value is required for attribute string of preference string
TNS-12550: TNS:syntax error
ORA-15072: command requires at least string failure groups, specified only string
ORA-13430: the GeoRaster object has null attribute(s)
NZE-29192: Validation mechanism not set in OID
NNF-02002: NIS value does not conform to adapter schema: string
Oracle Errors 
