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-00050: serious errors in configuration data, server cannot run
ORA-27483: "string.string" has an invalid END_DATE
ORA-09840: soacon: Name translation failure.
ORA-29361: value string is outside valid range of 0 to 100
RMAN-06108: changed datafile copy unvailable
ORA-12024: materialized view log on "string"."string" does not have primary key columns
ORA-30489: Cannot have more than one rollup/cube expression list
AUD-00706: unsupported or corrupted input format
RMAN-06211: ==========================
RMAN-08534: channel string: controlfile restore from autobackup complete
DRG-12307: column string is NULL and cannot be indexed
NZE-29229: the magic number found in the header does not match expected