Interested to Buy Any Domain ? << Click Here >> for more details...
NNL-00018: warning: could not contact default name server
- 1 Answers
- 3735 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 |
QSM-02030: reduced precision specified for prebuilt mv
ORA-28577: argument string of external procedure string has unsupported datatype string
ORA-01220: file based sort illegal before database is open
ORA-37021: (XSMULTI02) Object workspace object is not acquired.
PLS-00139: duplicate external NAME specification in subprogram expression
NNO-00703: checkpoint interval changed to number seconds
ORA-14521: Default tablespace string block size [string] for string string does not match existing string block size [string]
ORA-13417: null or invalid layerNumber for get functions
DRG-50902: unexpected character string
LSX-00014: empty instance document
ORA-02724: osnpbr: cannot send break message to orapop
PLS-00514: INSERT statement with REF INTO clause requires a typed table
Oracle Errors 
