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-22334: cannot reset type "string"."string". Dependent tables must be upgraded to latest version
ORA-27300: OS system dependent operation:string failed with status: string
ORA-32832: failure string trying to acquire administration lock
PLS-00989: Cursor Variable in record, object, or collection is not supported by this release
ORA-30025: DROP segment 'string' (in undo tablespace) not allowed
ORA-19503: cannot obtain information on device, name="string", type="string", parms="string"
ORA-31621: error creating master process
ORA-24802: user defined lob read callback error
ORA-07287: sksagdi: unsupported device for log archiving.
ORA-02381: cannot drop PUBLIC_DEFAULT profile
ORA-01373: insufficient memory for staging persistent LogMiner session
TNS-01185: Registration attempted from a remote node