NNL-00020: warning: no TNSNAMES.ORA file and no preferred
name servers in SQLNET.ORA
- 1 Answers
- 2413 Views
- I also Faced
- E-Mail Answers
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 |
ORA-12555: TNS:permission denied
ORA-06034: NETDNT: connect failed, partner exited unexpectedly
ORA-28150: proxy not authorized to connect as client
ORA-12544: TNS:contexts have different wait/test functions
ORA-06407: NETCMN: unable to set up break handling environment
NNO-00062: cannot load domain data from configuration database
PLS-00635: method does not override
ORA-01742: comment not terminated properly
ORA-09771: osnmwrtbrkmsg: bad return code from msg_send.
ORA-27152: attempt to post process failed
TNS-12636: Packet send failed
O2I-00126: You must specify an INTYPE file with SCHEMA_NAMES=FROM_INTYPE
Oracle Errors 
