NNL-00020: warning: no TNSNAMES.ORA file and no preferred
name servers in SQLNET.ORA
Answer / guest
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.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
PLS-00370: OTHERS handler must be last among the exception handlers of a block
ORA-25200: invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
ORA-26021: index string.string partition string loaded successfully with string keys
PLS-00703: multiple instances of named argument in list
SQL*Loader-02026: the load was aborted because SQL Loader cannot continue.
ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
PCC-02014: Syntax error at line number, column number, file string:
PCC-00108: This statement is not supported by ANSI
TNS-12646: Invalid value specified for boolean parameter
NNL-00551: Displays cache statistics
NZE-29029: SSL handshake already completed
ORA-00486: ASMB process terminated with error