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 |
NNO-00616: enabling DEFAULT-FORWARDERS-ONLY mode
DRG-12501: null stoplist is not allowed
PCC-00113: Value of DBMS option invalid with given value of MODE option
ORA-24272: initialization value must be either F or T
LSX-00286: duplicate key "~S" for {"~S"}"~S"
ORA-13014: a topology identifier outside the range of 1 to 8 was specified
ORA-00226: operation disallowed while alternate controlfile open
RMAN-20009: database incarnation already registered
EXP-00038: Bad Hash cluster id in clu$
NID-00312: Connected to server version string
NZE-29109: Cannot create private key object.
ORA-02163: invalid value for FREELIST GROUPS