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-09344: spsig: error signalling thread
ORA-24418: Cannot open further sessions.
ORA-32154: Anydata context not specified
NZE-28867: Integer value is too big.
NNL-00049: Output in string cannot be renamed to string
PLS-00120: inappropriate argument in OPEN statement
PCC-02206: Host variables are not permitted within a DDL statement
ORA-32130: invalid offset/index refrenced in Bytes
NNL-00204: Cancelled shutdown
ORA-01151: use media recovery to recover block, restore backup if needed
PCC-02317: illegal cast type expression
ORA-09949: Unable to get client operating system privileges