NNL-00018: warning: could not contact default name server
- 1 Answers
- 2994 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-24123: feature string is not yet implemented
ORA-00119: invalid specification for system parameter string
DRG-11118: object string does not exist
ORA-40104: invalid training data for model build
ORA-14624: DEFAULT subpartition must be last subpartition specified
PLS-00356: 'string' must name a table to which the user has access
DRG-50200: Third-party filter internal error
TNS-00296: Stoppable : string
ORA-19633: controlfile record string is out of sync with recovery catalog
ORA-32021: parameter value longer than string characters
ORA-02038: define is not allowed for array type
ORA-36290: (EIFMAKEF14) You cannot export object workspace object, because EIFVERSION is set to number. That version does not support dimensions of type NUMBER.
Oracle Errors 
