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 |
ORA-27125: unable to create shared memory segment
NZE-29007: Bad Clear Key Length when using SSL 2.0
IMP-00005: all allowable logon attempts failed
ORA-26535: %ud byte row cache insufficient for table with rowsize=number
TNS-01185: Registration attempted from a remote node
ORA-38423: Attribute set created from an ADT may not be extended.
ORA-12653: Authentication control function failed
PLS-00641: INTO clause not allowed for this SELECT statement
ORA-24375: Cannot use V6 syntax when talking to a V8 server
ORA-32400: cannot use object id columns from materialized view log on "string"."string"
RMAN-05004: target database log mode is NOARCHIVELOG
PCC-02315: cannot evaluate expression as constant