ORA-12560: TROUBLESHOOTING -------------------------- ORA-12560:
TNS:protocol adapter error Cause: A generic protocol adapter error
occurred. Action: Check addresses used for proper protocol
specification. Before reporting this error, look at the error
stack and check for lower level transport errors. For further details,
turn on tracing and re-execute the operation. Turn off tracing when
the operation is complete. This is a high level error
reporting that an error occurred in the transport layer. Since the
12560 is the end result of another problem and not necessarily the
cause look at the accompanying errors in the error stack. To get an
error stack, a SQL*Net trace should be obtained. Note 39774.1
describes how to set up SQL*Net tracing. Once you have the trace, you
should be able to locate the other errors accompanying the 12560. Note
39662.1 shows the SQL*Net components that take part during a
connection. Example of stack trace where a ORA-12560 appeared:
-<ERROR>- nsres: id=0, op=13, ns=12545, ns2=12560; nt[0]=515,
nt[1]=0,nt[2]=0 Call failed... Exiting NRICALL with following
termination result -1 -<ERROR>- error from nricall -<ERROR>- nr
err code: 12206 -<ERROR>- ns main err code: 12545 -<ERROR>- ns (2)
err code: 12560 -<ERROR>- nt main err code: 515 -<ERROR>- nt (2)
err code: 0 -<ERROR>- nt OS err code: 0 -<ERROR>- Couldn't
connect, returning 12545 These lines show all of the errors that have
been compiled up to the session layer within SQL*Net. 'ns' and 'ns2'
are the primary and secondary error codes for the session layer.
'nt[]' is the error code given back by SQL*Net�s transport
layer. Keep in mind that it is not the error code given by the
specific transport protocol below SQL*Net. The nt[0], nt[1] and nt[2]
are the primary, secondary, and tertiary error codes for the NT
layer. The NT error codes are not available through the Oracle UNIX
'oerr' tool, but are available in the Oracle Network Products
Troubleshooting Guide error documentation. ORA-12560 ON WINDOWS NT:
Oracle errors are not visible if you try to start up the services
(listener or Instance) via the Control Panel. Start the listener or
start the database from the DOS command line to get more detailed
information. The Event Viewer (found in Windows NT's Administrative
Tools) is another place to check for errors. Note 118999.1
ORA-12560 STARTING LISTENER ON NT - TROUBLESHOOTING Note 119003.1
ORA-12560 STARTING SVRMGR OR SQLPLUS ON NT - TROUBLESHOOTING Note
1072920.6 ORA-12560 STARTING NAMES - NEW INSTALL ORA-12560 ON UNIX
Note:119007.1 ORA-12560 ADMINISTERING THE LISTENER ON UNIX -
TROUBLESHOOTING Note:119008.1 ORA-12560 CONNECTING TO THE SERVER ON
UNIX - TROUBLESHOOTING ORA-12560 GENERIC ISSUES: Note 114516.1
Resolving the TNS-12541 error: TNS No Listener Note 1005739.6
TNS-12542 TNS-12560 TNS-00512 STARTING LISTENER USING SQL*NET RELATED
DOCUMENTS ----------------- Note:39774.1 LOG & TRACE Facilities on
NET v2. Note:39662.1 Network Products and Error Stack Components
Oracle 8i Network Adminstrators Guide, Ch. 11 "Establishing a
Connection and Testing the Network" Ch. 12 "Troubleshooting"
Oracle 9i Net Services/Admin Guide, Ch. 16 "Establishing a
Connection and Testing the Network" Ch. 17 "Troubleshooting Oracle
Net Services"
.
Received on Tue Feb 25 2003 - 15:13:52 CST
