NNL-00020: warning: no TNSNAMES.ORA file and no preferred
name servers in SQLNET.ORA
- 1 Answers
- 2623 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-08451: invalid specification of DB in picture mask
ORA-32312: cannot refresh a secondary materialized view "string"."string"
PCC-00026: Invalid host variable "string" at line number in file string
ORA-16066: remote archival disabled
SQL*Loader-00481: HIDDEN may not be used with non-scalar fields.
PCC-02439: FOR clause not allowed in this COLLECTION statement
RMAN-11000: message number number not found in recovery manager message file
ORA-07303: ksmcsg: illegal database buffer size.
ORA-00237: snapshot operation disallowed: controlfile newly created
ORA-31655: no data or metadata objects selected for job
ORA-29314: tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
ORA-38478: creation of system trigger EXPFIL_DROPOBJ_MAINT failed
Oracle Errors 
