Release 1 (9.0.1)
Part Number A90154-01
 Home |
 Book List |
 Contents |
 Index |  Master Index |  Feedback |
| Oracle9i Net Services Administrator's Guide Release 1 (9.0.1) Part Number A90154-01 |
|
Oracle Net Services provide methods for understanding and resolving network problems through the use of log and trace files. These files keep track of the interaction between network components as errors occur. Evaluating this information will help you to diagnose and troubleshoot even the most complex network problems.
This chapter describes common network errors and outlines procedures for resolving them. It also describes methods for logging and tracing error information to diagnose and troubleshoot more complex network problems. This chapter contains these topics:
If an attempt to make a basic peer-to-peer (single protocol network) connection returns an ORA Error, this section may help you diagnose the cause of the problem.
Any underlying fault, noticeable or not, is reported by Oracle Net with an error number or message that is not always indicative of the actual problem. This section helps you determine which parts of Oracle Net do function properly rather than the parts that do not work. It also helps you to decide in which of the following categories the fault belongs:
Testing the various network layers progressively should in most cases uncover any problem.
Answer the following questions:
If you answered YES to any of the above questions/statements, skip this section and continue to "Client Diagnostics".
If you are unsure, or answered NO to any of the above questions, please continue.
Diagnosing Oracle Net on the server involves the following tasks:
To check that the database is up, login to the database and connect with a valid user name and password. For example:
SQLPLUS system/manager
A message appears, confirming that you are connected with the database. If you receive the following errors, ask your Database Administrator to assist you:
To perform a loopback test from the server to the database:
listener.ora, tnsnames.ora, and sqlnet.ora files exist in the $ORACLE_HOME/network/admin directory on UNIX, or the ORACLE_HOME\network\admin directory on Windows NT.
The search order for configuration files is as follows:
TNS_ADMIN environment variable
If the TNS_ADMIN environment variable is not defined as a variable on Windows NT, it may be in the registry.
/var/opt/oracle. Windows NT does not have a central directory.
$ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows operating systems
At this point, you know the serverside listener works properly, because you could verify at least one of the following statements:
To perform diagnostics on the client:
On UNIX, you can run the adapters program to verify this. Run adapters at $ORACLE_HOME/bin.
Output similar to the following appears:
Installed Oracle Net Services Tranport Protocols are: IPC TCP/IP BEQueath SSL RAW
| Protocol | Verify that you can... |
|---|---|
|
TCP/IP |
Use terminal emulation or file transfer utilities, (PING, FTP, TELNET) from the client to the server. |
|
Named Pipes |
tnsnames.ora and the sqlnet.ora files in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows operating systems.
The search order for sqlnet.ora and tnsnames.ora follows:
TNS_ADMIN environment variable
If the TNS_ADMIN environment variable is not defined as a variable on Windows NT, it may be in the registry.
/var/opt/oracle. Windows NT does not have a central directory.
$ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows operating systems
tnsnames.ora and sqlnet.ora files from the working computer onto the non-working client workstations. This eliminates the possibility of errors in the files.
http://support.oracle.com for a specific diagnostics bulletin on the error received
Due to the complexity of network communications, network errors may originate from a variety of sources, for a variety of reasons. If an error occurs, applications such as SQL*Plus, that depend on network services from Oracle Net Services, will normally generate an error message.
A list of the most common network error messages follows:
ORA-12154: TNS:could not resolve service name
Cause: Oracle Net could not locate the net service name specified in the tnsnames.ora configuration file.
Action: Perform these steps:
tnsnames.ora file exists.
tnsnames.ora file.
tnsnames.ora file, verify that the net service name specified in your connect string is mapped to a connect descriptor.
sqlnet.ora file.
sqlnet.ora file contains a NAMES.DEFAULT_DOMAIN parameter. If this parameter does not exist, you must specify the domain name in your connect string.
Cause: Oracle Net could not locate the database service name or net service name specified in the directory server.
Action: Perform these steps:
ORA-12198: TNS:could not find path to destination
ORA-12203: TNS:unable to connect to destination
Cause: The client cannot find the desired database.
Action: Perform these steps:
ADDRESS parameters in the connect descriptor.
tnsnames.ora file is stored in the correct directory.
lsnrctlLSNRCTL> STATUS [listener_name]
listener_name is the name of the listener defined in the listener.ora file. It is not necessary to identify the listener if you are using the default listener, named LISTENER.
If the output indicates the listener is not running, try starting it with the command:
LSNRCTL> START [listener_name]
ORA-12203: TNS:unable to connect to destination
Cause: ORA-12203 error is a generic error that often shields secondary errors.
Action: Check the latest sqlnet.log file for secondary ORA messages.
Cause: An invalid net service name was supplied in the connect string.
Action: Verify that the net service name supplied in the connect string exists in the tnsnames.ora file or directory server and the ADDRESS information for that net service name is valid. Ask yourself the following questions:
Cause: The tnsnames.ora file is not located in the proper directory.
Action: Make sure the tnsnames.ora file is in the proper location.
Cause: The (HOST=server_name) parameter for TCP/IP addresses is not consistent on the client and server computers.
Action: Ensure that the values for these parameter are the same on the server and client.
For TCP/IP, make sure that the HOST parameter in listener.ora on the server and in the tnsnames.ora file on the client point to the same name, or at least to names that are then translated to the same IP address by each system. This is especially important for servers with multiple IP addresses assigned to the various network interfaces on the server.
Cause: The destination system's listener is not listening.
Action: Verify that the remote system's listener is running. Enter:
lsnrctlLSNRCTL> STATUS [listener_name]
listener_name is the name of the listener defined in the listener.ora file. It is not necessary to identify the listener if you are using the default listener, named LISTENER.
If the output indicates the listener is not running, try starting it with the command:
LSNRCTL> START [listener_name]
Cause: There are underlying network transport problems.
Action: Use the utilities supplied with the underlying networking protocol to verify that the protocol itself is functional. For example, with TCP/IP, try to ping the remote system.
Cause: The incorrect Oracle protocol for the selected networking protocol is installed. A missing protocol support driver usually produces the following errors in the sqlnet.log or any client trace file:
Action: Check that you have installed the appropriate Oracle protocol. On UNIX, you can run the adapters program to verify this. Run adapters at $ORACLE_HOME/bin.
Output similar to the following displays:
Installed Oracle Net Tranport Protocols are: IPC TCP/IP BEQueath SSL RAW ...
ORA-12224: TNS:no listener
Cause: The connection request could not be completed because the listener is not running.
Action: Perform these steps:
ORA-12533: TNS:illegal ADDRESS parameters
Cause: The protocol specific parameters in the ADDRESS section of the designated connect descriptor are incorrect.
Action: Correct the protocol address.
ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor
Cause: The service name specified in the connect descriptor is incorrect, or the database service is not registered with the listener.
Action: Perform these steps:
SERVICE_NAME specified in the connect descriptor is correct.
SERVICES command to see what services are currently registered with the listener.
ORA-12520: TNS:listener could not find available handler for requested type of server
Cause: The type of service handler requested by the client is incorrect or not registered for the requested SERVICE_NAME/INSTANCE_NAME, or the database instance is not registered with the listener.
Action: If you suspect the problem is the wrong type of service handler, perform these steps:
(server=value) is set is in the connect descriptor, ensure that the value is set to the appropriate service handler type for the database, that is, dedicated for dedicated server or shared for dispatchers. You can use the Listener Control utility SERVICES command to see what service handlers are currently registered with the listener.
USE_DEDICATED_SERVER is set to ON in the sqlnet.ora file, then ensure the database is configured to use dedicated servers. If it is not, set this parameter to off.
ORA-12521: TNS:listener could not resolve INSTANCE_NAME given in connect descriptor
Cause: The INSTANCE_NAME in the connect descriptor is incorrect, or the database instance is not registered with the listener.
Action: Perform these steps:
SERVICES command to see what instances are currently registered with the listener.
ORA-12545: TNS:name lookup failure
Cause: The listener on the remote node cannot be contacted.
Action: Perform these steps:
ADDRESS in the tnsnames.ora file and the listener.ora file is correct.
lsnrctlLSNRCTL> STATUS [listener_name]
listener_name is the name of the listener defined in the listener.ora file. It is not necessary to identify the listener if you are using the default listener, named LISTENER.
If the output indicates the listener is not running, try starting it with the command:
LSNRCTL> START [listener_name]
ORA-12560: TNS:protocol adapter error
Action: The listener was unable to start a process connecting the user to the database server.
Cause: Perform these steps:
ORA-3113: TNS:End of file on communication channel
Cause: An error has occurred on the database server.
Action: Check the alert_sid.log on the server. The location of alert_sid.log is specified by the BACKGROUND_DUMP_DEST initialization parameter.
Cause: An unexpected end of file was processed on the communication channel. This may be an indication that the communications link may have gone down at least temporarily; it may indicate that the server has gone down.
Action: You may need to modify your retransmission count.
ORA-3121: No interface driver connection - function not performed
Cause: A SQL*Net version 1 prefix was erroneously used in the connect string.
Action: Do not use the following prefixes in the connect string.
Cause: Only the user name and password were specified from a client computer that had no local Oracle database installed.
Action: Specify a connect string.
Directory naming issues associated with connectivity errors such as ORA-12154, ORA-12203, or ORA-12224 for database service or net service name entries in a directory server require analysis of the data. You can analyze the data contained within a directory server with the ldifwrite command line tool.
ldifwrite enables you to convert all or part of the information residing in a directory server to LDAP Data Interchange Format (LDIF). The ldifwrite tool performs a subtree search, including all entries below the specified distinguished name (DN), including the DN itself.
The ldifwrite tool syntax is as follows:
ldifwrite -cnet_service_name/database_service-bbase_DN-fldif_file
Table 17-1 ldapwrite Arguments
The following example writes all the Oracle Net Services entries under dc=us,dc=acme,dc=com into the output1.ldi file:
ldifwrite -c ldap -b "dc=us,dc=acme,dc=com" -f output.ldif
Errors in the region load operation will be reported in the Oracle Names server log file (names.log). These errors may range from failure to contact the directory server to errors with the query for all, some, or one of the records.
Some directories, such as Oracle Internet Directory, have limits on ldapsearch operations. There are settings in the directory server that limit the number of objects returned by the search and the amount of time spent performing a search.
The size limit specifies how many objects can be returned from a search. The default limit is 1000. If this limit is exceeded, you will see the following errors in the names.log file:
NNO-00062: cannot load domain data from configuration database NNO-00850: Error: LDAP query returns 4
You can also use the ldapsearch command line tool to mimic what the Oracle Names server will do when it loads its region. The following syntax shows loading data from DN (dn:dc=acme,dc=com):
ldapsearch -p 389 -h host -b "dc=acme,dc=com"
"(objectclass=orclNetService)(objectclass=orclService)"
After returning the allowed number of object, ldapsearch returns the following error message:
ldapsearch: Sizelimit exceeded
You can modify the size limit using the following sample LDIF file output. Enter the appropriate DN. In addition, set orclsizelimit high enough to allow for the number of databases defined in the region in the directory server, with a little room for future expansion.
dn: changetype: modify replace: orclsizelimit orclsizelimit: 5000
The time limit specifies the amount of time that can be spent performing a search. The default time limit is 10 seconds. Ten seconds is sufficient to query for roughly 1,000 object, which is sufficient for most searches. If the query exceeds the time limit, you will see the following errors in the names.log file:
NNO-00062: cannot load domain data from configuration database NNO-00850: Error: LDAP query returns 105
You can modify the time limit using the following sample LDIF file output. Enter the appropriate DN.
dn: changetype: modify replace: orcltimelimit orcltimelimit: 20
The time limit is applied at both the directory server and API levels. Therefore, in addition to resetting the directory server time limit, you will also need to set the TIMEOUT sub-parameter of NAMES.ADMIN_REGION. For example:
NAMES.ADMIN_REGION= (REGION= (TIMEOUT=20) (TYPE=ldap) (HOST=dlsun1598) (PORT=389) (SUBTREE=(BASE=dc=acme,dc=com)))
Here are some tips you may find helpful when you are having difficulty diagnosing network problems:
This eliminates any internal lookup problems and make the connection slightly faster.
For example, change the
(HOST=server_name) line in the tnsnames.ora file with the internet address, for example (HOST=198.32.3.5).
Perform a loopback test on the server as described in "Testing Configuration on the Database Server". If the test passes, ftp the tnsnames.ora and sqlnet.ora files to the client.
If it is a wide area network (WAN), identify any intermediate systems that may not work correctly. If all computers are fine, the problem may be a timing issue.
Timing issues are associated with ORA-12203, ORA-12535, or ORA-12547 errors in the client log files.
CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. The default value for this parameter is 10 seconds.
SQL*Plus may work, but CASE tools may not. If you determine the problem is a data volume issue, try to transfer a large (5 MB) file with the base connectivity.
Here are some questions to ask yourself when diagnosing a problem:
If one computer works and another does not, and you are confident that the same software (Oracle and third-party products) is installed, on each computer, swap out the network cables, if they are close enough, to see if the problem moves. If it does move, it indicates that the problem has something to do with the client/server connection and is not local to the PC.
Sniffers and LAN analyzers are useful for intermittent failing connections or detecting time-outs and re-sent packets. You can also see what side of the conversation is waiting for a response.
Oracle Net Services provide detailed information about the source and context of problems as they arise. This information is generated and stored in log and trace files. The process of logging and tracing error information will help you to diagnose and resolve network problems.
All errors encountered in Oracle Net Services are appended to a log file for evaluation by a network or database administrator. The log file provides additional information for an administrator when the error message on the screen is inadequate to understand the failure. The log file, by way of the error stack, shows the state of the software at various layers.
To ensure that all errors are recorded, logging cannot be disabled on clients or Names Servers. Furthermore, only an administrator may replace or erase log files. The log file for the listener also includes Audit Trail information about every client connection request, as well as most listener control commands.
This section contains these topics:
Log files provide information contained in an error stack. An error stack refers to the information that is produced by each layer in an Oracle communications stack as the result of a network error. Figure 17-1 depicts the relationship among error stack components and Oracle Net.
The error stack components in Figure 17-1 are described in Table 17-2.
Table 17-2 Error Stack Components :As an example, suppose that a user of a client application tries to establish a connection with a database server using Oracle Net and TCP/IP, and the user enters:
sqlplus scott/tiger@hrserver.com
The following error displays:
ORA-12203: TNS:Unable to connect to destination
This message indicates that the connection to the server failed because the database could not be contacted. Although the application displays only a one-line error message, an error stack that is much more informative is recorded in the log file by the network layer.
On the client side, a sqlnet.log file (Figure 17-2) contains an error stack corresponding to the ORA-12203 error.
***********************************************************
Fatal OSN connect error 12203, connecting to: (DESCRIPTION=(CONNECT_DATA=(SID=trace)(CID=(PROGRAM=) (HOST=lala)(USER=sviavant)))(ADDRESS_LIST=(ADDRESS= (PROTOCOL=ipc)(KEY=trace))(ADDRESS=(PROTOCOL=tcp) (HOST=lala)(PORT=1521)))) VERSION INFORMATION: TNS for SunOS: Oracle Bequeath NT Protocol Adapter for SunOS: Unix Domain Socket IPC NT Protocol Adaptor for SunOS: TCP/IP NT Protocol Adapter for SunOS: Tracing to file: /home/sviavant/trace_admin.trc Tns error struct: nr err code: 12203 TNS-12203: TNS:unable to connect to destination ns main err code: 12541 TNS-12541: TNS:no listener ns secondary err code: 12560 nt main err code: 511 TNS-00511: No listener nt secondary err code: 61 nt OS err code: 0
Each Oracle Net Services component produces its own log file. Table 17-3 provides the default file names and a description of the information they contain.
Table 17-3 Oracle Net Log Files
Parameters that control logging, including the type and amount of information logged, as well as the location where the files are stored, are set in the configuration file of each network component as described in Table 17-4.
Table 17-4 Oracle Net Log Parameters
| Network Component | Configuration Files |
|---|---|
|
Client |
|
|
Database Server |
|
|
Listener |
|
|
Oracle Names Server |
|
|
Oracle Connection Manager |
|
This section contains these topics:
Table 17-5 describes the log parameters settings that can be set in the sqlnet.ora file.
Table 17-6 describes the log parameters settings that can be set in the listener.ora file.
Table 17-7 describes the log parameters settings that can be set in the names.ora file.
Table 17-8 describes the log parameters settings that can be set in the cman.ora file.
Logging parameters for the sqlnet.ora file, listener.ora files and names.ora file can be set with the Oracle Net Manager. The cman.ora file logging parameters must be set manually.
To set logging parameters:
| Log File | Set logging parameters here... |
|---|---|
|
|
|
|
|
|
|
|
Logging can be set during runtime of control utilities. Note that setting logging with a control utility will not set parameters in the *.ORA files; the setting is only valid for the session of the control utility:
SET LOG_FILE and SET LOG_DIRECTORY commands from the Listener Control utility.
SET LOG_LEVEL command from the Oracle Connection Manager control utility.
SET LOG_FILE_NAME command from the Oracle Names Control utility, or set logging settings through Oracle Net Manager.
To set tracing for an Oracle Names server with Oracle Net Manager:
To use a log file to diagnose a network error:
This section describes what is recorded in the listener log file, including:
The listener log file contains audit trail information that enables you to gather and analyze network usage statistics, as well as information indicating the following:
RELOAD, START, STOP, STATUS, or SERVICES command issued by the Listener Control utility
The Audit Trail formats text into the following fields:
Timestamp * Connect Data * [Protocol Info] * Event * [SID | Service] * Return Code
Properties of the Audit Trail are as follows:
*).
"Resolving the Most Common Error Messages for Oracle Net Services" for the most common Oracle Net errors or Oracle9i Database Error Messages for a complete listing of error messages
See Also:
Typical output to the log file upon a RELOAD request follows.
14-SEP-1999 00:29:54 * (connect_ data=(cid=(program=)(host=dlsun1013)(user=jdoe))(command=stop)(arguments=64)(ser vice=listener)(version=135290880)) * stop * 0
Typical output to the log file upon a connection request follows.
10-AUG-1999 15:28:58 * (connect_data=(service_name=sales.us.acme.com)(cid=(program=)(host=dlsun1013) (user=jdoe))) * (address=(protocol=tcp)(host=144.25.185.246)(port=41349)) * establish * sales.us.acme.com * 0
You can use Audit Trail information to view trends and user activity by first storing it in a table and then collating it into a report format. To import the data into a table, use an import utility such as SQL*Loader.
The listener records service registration events. During service registration, the instance background process PMON process provides the listener with information about the following:
The following service registration-related events are recorded in the listener.log file:
The service registration events are formatted into the following fields:
Timestamp * Event * Instance Name * Return Code
Properties of service registration fields are as follows:
*).
See Also:
The following example shows a log file with service registration events. Notice how the listener is able to receive a client request after a successful service_register event, but is unable to receive client requests after a service_died event.
------------------------------- 10-AUG-1999 15:28:43 * service_register * sales * 0 10-AUG-1999 15:28:43 * service_register * sales * 0 10-AUG-1999 15:28:58 * (connect_data=(service_name=sales.us.acme.com)(cid=(program=)(host=dlsun1013) (user=jdoe))) * (address=(protocol=tcp)(host=144.25.185.246)(port=41349)) * establish * sales.us.acme.com * 0 10-AUG-1999 15:38:44 * service_update * sales * 0 10-AUG-1999 15:38:44 * service_update * sales * 0 10-AUG-1999 15:48:45 * service_update * sales * 0 10-AUG-1999 15:48:45 * service_update * sales * 0 10-AUG-1999 15:50:57 * (connect_data=(service_name=sales.us.acme.com)(cid=(program=)(host=dlsun1013)(u ser=jdoe))) * (address=(protocol=tcp)(host=144.25.185.246)(port=41365)) * establish * sales.us.acme.com * 0 10-AUG-1999 15:51:26 * service_died * sales * 12537 10-AUG-1999 15:51:26 * service_died * sales * 12537 10-AUG-1999 15:52:06 * (connect_data=(service_name=sales.us.acme.com)(cid=(program=)(host=dlsun1013)(u ser=jdoe))) * (address=(protocol=tcp)(host=144.25.185.246)(port=41406)) * establish * sales.us.acme.com * 12514 TNS-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor --------------------------------
The listener records direct hand-off events to dispatchers. These events are formatted into the following fields:
Timestamp * Presentation * Handoff * Error Code
Properties of direct hand-off fields are as follows:
*).
"Resolving the Most Common Error Messages for Oracle Net Services" for the most common Oracle Net errors or Oracle9i Database Error Messages for a complete listing of error messages
See Also:
A direct hand-off event in the log file is shown in the following example.
21-MAY-1999 10:54:55 * oracle.aurora.net.SALESHttp2 * handoff * 0
Oracle Connection Manager generates two types of log files: one for its CMGW gateway process (cman_pid.log) and one for its CMADMIN administrative process.
Figure 17-3 and Figure 17-4 show examples of the log files.
(TIMESTAMP=30-OCT-98 18:03:10)(EVENT=10)(VERSION=8.1.6.0.0) (TIMESTAMP=30-OCT-98 18:03:10)(EVENT=36)(rule_list= (rule=(src=spcstn)(dst=x)(srv=x)(act=accept))) (TIMESTAMP=30-OCT-98 18:03:10)(EVENT=32)(PARAMETER_LIST=(MAXIMUM_ RELAYS=1024)(RELAY_STATISTICS=no)(AUTHENTICATION_LEVEL=0)(LOG_LEVEL=1)(SHOW_TNS_ INFO=no)(ANSWER_TIMEOUT=0)(MAXIMUM_CONNECT_DATA=1024)(USE_ASYNC_ CALL=yes)(TRACING=no)(TRACE_DIRECTORY=default)(MAX_FREELIST_BUFFERS=0)) (TIMESTAMP=30-OCT-98 18:03:10)(EVENT=34)(ADDRESS_LIST= (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1610)(QUEUESIZE=32))) (TIMESTAMP=30-OCT-98 18:03:12)(EVENT=38)(COMMAND=2) (TIMESTAMP=30-OCT-98 18:03:27)(EVENT=26)(RLYNO=0)(SRC=(ADDRESS=(PROTOCOL=tcp)(HOST=spcstn.us.oracle.c om)(PORT=34758)))(DST=(ADDRESS=(PROTOCOL=tcp)(HOST=144.25.187.89)(PORT=1581))) (TIMESTAMP=30-OCT-98 18:03:43)(EVENT=28)(RLYNO=0)(SINCE=30-OCT-98 18:03:27)(STATISTICS=(IN=(BYTES=0)(PACKETS=0)(DCDS=0)(OUT=(BYTES=0)(PACKETS=0)(D CDS=0)))Figure 17-4 cmadm_pid.log
(TIMESTAMP=30-OCT-98 18:03:09)(EVENT=Sent Admin Status to UI) (TIMESTAMP=30-OCT-98 18:03:10)(EVENT=CMan Registration)
The cman_pid.log on UNIX and cmanpid.log on Windows NT reports events using event code numbers. The event code reported depends upon the log level set with the LOG_LEVEL parameter in the cman.ora file or with the Oracle Connection Manager Control utility command SET LOG_LEVEL. This section explains what each of these event codes represents.
| Code | Description |
|---|---|
|
10 |
Gateway is starting up |
|
12 |
Gateway is shutting down |
|
14 |
Listening on TNS address(es) |
|
18 |
See Also: "Reasons for Event Code 18" |
|
20 |
See Also: "Reasons for Event Code 20" |
|
26 |
Relay is now open |
|
28 |
Relay is now closed |
|
30 |
Statistics report |
|
32 |
< |
|
34 |
< |
|
36 |
< |
|
38 |
Oracle Connection Manager Control utility command |
|
40 |
Oracle Connection Manager Control utility command refused because the gateway is busy |
|
42 |
Dead connection detected |
|
44 |
Relay has timed out |
|
11 |
Bad < |
|
13 |
Bad < |
|
15 |
Bad < |
|
23 |
Bad Oracle Connection Manager Control utility record |
|
25 |
Command line argument is too long |
|
27 |
Memory allocation failure |
|
29 |
TNS error |
|
31 |
TNS error while processing Oracle Connection Manager Control utility requests |
The answer can fail due to the following:
| Code | Description |
|---|---|
|
1 |
Timed out |
|
2 |
Connect data buffer is too small |
|
3 |
Refused by TNS |
|
4 |
TNS packet checksum error |
The incoming call can be refused if:
| Code | Description |
|---|---|
|
102 |
Answering in-coming call |
|
104 |
Making out-going call |
|
105 |
Accepting in-coming call |
|
106 |
Rule match report |
| Code | Description |
|---|---|
|
202 |
Call will block (no asynchronous TNS support) |
|
204 |
See Also: "Reasons for Event Code 204" |
|
206 |
Buffer contains leftover data |
The relay can be blocked due to the following:
| Code | Description |
|---|---|
|
1 |
Waiting for writer to be ready |
|
2 |
Waiting for writer to clear backlog |
|
3 |
WOULDBLOCK error on receive |
|
4 |
WOULDBLOCK or PARTIAL error on send |
|
5 |
Repeated WOULDBLOCK or PARTIAL send error |
| Code | Description |
|---|---|
|
302 |
Read this many bytes |
|
304 |
Wrote this many bytes |
|
306 |
Wrote this many bytes on retry |
Tracing produces a detailed sequence of statements that describe network events as they are executed. Tracing an operation enables you to obtain more information on the internal operations of the components of Oracle Net than is provided in a log file. This information is output to files that can be evaluated to identify the events that led to an error.
This section contains topics:
Each Oracle Net component produces its own trace file. Table 17-14 provides the default file names and a description of the information they contain.
Table 17-14 Oracle Net Trace Files
Parameters that control tracing, including the type and amount of information logged, as well as the location where the files are stored, are set in the configuration file of each network component as described in Table 17-15.
Table 17-15 Oracle Net Trace Parameters
| Trace Parameters | Configuration Files |
|---|---|
|
Client |
|
|
Server |
|
|
Listener |
|
|
Oracle Names Server |
|
|
Oracle Connection Manager processes |
|
This sections contains these topics:
Table 17-16 describes the trace parameters settings that can be set in the sqlnet.ora file.
You can also manually add the following TNSPING utility tracing parameters described in Table 17-17 to sqlnet.ora. The TNSPING utility determines whether or not a service (such as a database, an Oracle Names Server, or other TNS services) on a Oracle Net network can be successfully reached.
Table 17-18 describes the trace parameters settings that can be set in the listener.ora file.
Table 17-19 describes the trace parameters settings that can be set in the names.ora file.
Table 17-20 describes the trace parameters settings that can be set in the cman.ora file.
sqlnet.ora, listener.ora and names.ora logging parameters can be set with the Oracle Net Manager. The cman.ora tracing parameters must be set manually.
To set tracing parameters:
| Trace File | Instruction |
|---|---|
|
|
|
|
|
|
|
|
Tracing can be set during a runtime of a control utility. Note that setting tracing with a control utility will not set parameters in the *.ora files; the setting is valid only for the session of the control utility:
SET TRC_FILE, SET TRC_DIRECTORY and SET TRC_LEVEL commands from the Listener Control utility.
SET TRACE_LEVEL and SET TRACE_DIRECTORY commands from the Oracle Connection Manager Control utility.
SET TRACE_FILE_NAME and SET TRACE_LEVEL commands from the Oracle Names Control utility, or set tracing settings through Oracle Net Manager.
To set tracing for an Oracle Names server with Oracle Net Manager:
Trace files can help Oracle Support Service diagnose and troubleshoot network problems.
This section explains how to do basic analysis of trace files. The topics discussed include:
Oracle Net performs its functions by sending and receiving data packets.By specifying a trace level of support, you can view the actual contents of the Oracle Net packet in your trace file. The order of the packet types sent and received will help you to determine how your connection was established.
Each line in the trace file begins with a procedure followed by a message. Following each procedure is a line of hexadecimal data representing actual data. The actual data that flows inside the packet is sometimes viewable to the right of the hexadecimal data.
Next is a list of the Oracle Net packet keywords and descriptions of the types of packets they represent:
| Keyword | Packet Type |
|---|---|
|
|
Connect |
|
|
Accept |
|
|
Refuse |
|
|
Resend |
|
|
Data |
|
|
Control |
|
|
Marker |
For example, the following line describes a procedure called "nscon" sending a NSPTCN packet over the network:
nscon: sending NSPTCN packet
Each packet has a keyword that denotes the packet type. All packet types begin with the prefix "nsp". It is helpful to remember this when reviewing trace files for specific packet information
Figure 17-5 provides typical packet information.
nscon: entry nscon: doing connect handshake... nscon: sending NSPTCN packet nspsend: entry nspsend: plen=187, type=1 nspsend: 187 bytes to transport nspsend:packet dump nspsend:00 BB 00 00 01 00 00 00 |........| nspsend:01 33 01 2C 0C 01 08 00 |.3.,....| nspsend:7F FF 7F 08 00 00 00 01 |........| nspsend:00 99 00 22 00 00 08 00 |..."....| nspsend:01 01 28 44 45 53 43 52 |..(DESCR| nspsend:49 50 54 49 4F 4E 3D 28 |IPTION=(| nspsend:43 4F 4E 4E 45 43 54 5F |CONNECT_| nspsend:44 41 54 41 3D 28 53 49 |DATA=(SI| nspsend:44 3D 61 70 33 34 37 64 |D=ap347d| nspsend:62 31 29 28 43 49 44 3D |b1)(CID=| nspsend:28 50 52 4F 47 52 41 4D |(PROGRAM| nspsend:3D 29 28 48 4F 53 54 3D |=)(HOST=| nspsend:61 70 32 30 37 73 75 6E |ap207sun| nspsend:29 28 55 53 45 52 3D 6D |)(USER=m| nspsend:77 61 72 72 65 6E 29 29 |warren))| nspsend:29 28 41 44 44 52 45 53 |)(ADDRES| nspsend:53 5F 4C 49 53 54 3D 28 |S_LIST=(| nspsend:41 44 44 52 45 53 53 3D |ADDRESS=| nspsend:28 50 52 4F 54 4F 43 4F |(PROTOCO| nspsend:4C 3D 74 63 70 29 28 48 |L=tcp)(H| nspsend:4F 53 54 3D 61 70 33 34 |OST=ap34| nspsend:37 73 75 6E 29 28 50 4F |7sun)(PO| nspsend:52 54 3D 31 35 32 31 29 |RT=1521)| nspsend:29 29 29 00 00 00 00 00 |))).....| nspsend: normal exit nscon: exit (0)
When there is a problem an Oracle Net connection, the error code is logged in the trace file. Figure 17-6 depicts typical trace file output for a failed SQL*Plus connection to a database server.
[09-MAR-2001 13:34:07] nsprecv: entry [09-MAR-2001 13:34:07] nsbal: entry [09-MAR-2001 13:34:07] nsbgetfl: entry [09-MAR-2001 13:34:07] nsbgetfl: normal exit [09-MAR-2001 13:34:07] nsmal: entry [09-MAR-2001 13:34:07] nsmal: 44 bytes at 0x132d90 [09-MAR-2001 13:34:07] nsmal: normal exit [09-MAR-2001 13:34:07] nsbal: normal exit [09-MAR-2001 13:34:07] nsprecv: reading from transport... [09-MAR-2001 13:34:07] nttrd: entry [09-MAR-2001 13:35:09] nttrd: exit [09-MAR-2001 13:35:09] ntt2err: entry [09-MAR-2001 13:35:09] ntt2err: Read unexpected EOF ERROR on 10 [09-MAR-2001 13:35:09] ntt2err: exit [09-MAR-2001 13:35:09] nsprecv: transport read error [09-MAR-2001 13:35:09] nsprecv: error exit [09-MAR-2001 13:35:09] nserror: entry [09-MAR-2001 13:35:09] nserror: nsres: id=0, op=68, ns=12537, ns2=12560; nt[0]=507, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0 [09-MAR-2001 13:35:09] nscon: error exit [09-MAR-2001 13:35:09] nsdo: nsctxrnk=0 [09-MAR-2001 13:35:09] nsdo: error exit [09-MAR-2001 13:35:09] nscall: unexpected response [09-MAR-2001 13:35:09] nsclose: entry [09-MAR-2001 13:35:09] nstimarmed: entry [09-MAR-2001 13:35:09] nstimarmed: no timer allocated [09-MAR-2001 13:35:09] nstimarmed: normal exit [09-MAR-2001 13:35:09] nsdo: entry [09-MAR-2001 13:35:09] nsdo: cid=0, opcode=98, *bl=0, *what=0, uflgs=0x440, cflgs=0x2 [09-MAR-2001 13:35:09] nsdo: rank=64, nsctxrnk=0 [09-MAR-2001 13:35:09] nsdo: nsctx: state=1, flg=0x4201, mvd=0 [09-MAR-2001 13:35:09] nsbfr: entry [09-MAR-2001 13:35:09] nsbaddfl: entry [09-MAR-2001 13:35:09] nsbaddfl: normal exit [09-MAR-2001 13:35:09] nsbfr: normal exit [09-MAR-2001 13:35:09] nsbfr: entry [09-MAR-2001 13:35:09] nsbaddfl: entry [09-MAR-2001 13:35:09] nsbaddfl: normal exit [09-MAR-2001 13:35:09] nsbfr: normal exit [09-MAR-2001 13:35:09] nsdo: nsctxrnk=0 [09-MAR-2001 13:35:09] nsdo: normal exit [09-MAR-2001 13:35:09] nsclose: closing transport [09-MAR-2001 13:35:09] nttdisc: entry [09-MAR-2001 13:35:09] nttdisc: Closed socket 10 [09-MAR-2001 13:35:09] nttdisc: exit [09-MAR-2001 13:35:09] nsclose: global context check-out (from slot 0) complete [09-MAR-2001 13:35:09] nsnadisc: entry [09-MAR-2001 13:35:09] nadisc: entry [09-MAR-2001 13:35:09] nacomtm: entry [09-MAR-2001 13:35:09] nacompd: entry [09-MAR-2001 13:35:09] nacompd: exit [09-MAR-2001 13:35:09] nacompd: entry [09-MAR-2001 13:35:09] nacompd: exit [09-MAR-2001 13:35:09] nacomtm: exit [09-MAR-2001 13:35:09] nas_dis: entry [09-MAR-2001 13:35:09] nas_dis: exit [09-MAR-2001 13:35:09] nau_dis: entry [09-MAR-2001 13:35:09] nau_dis: exit [09-MAR-2001 13:35:09] naeetrm: entry [09-MAR-2001 13:35:09] naeetrm: exit [09-MAR-2001 13:35:09] naectrm: entry [09-MAR-2001 13:35:09] naectrm: exit [09-MAR-2001 13:35:09] nagbltrm: entry [09-MAR-2001 13:35:09] nau_gtm: entry [09-MAR-2001 13:35:09] nau_gtm: exit [09-MAR-2001 13:35:09] nagbltrm: exit [09-MAR-2001 13:35:09] nadisc: exit [09-MAR-2001 13:35:09] nsnadisc: normal exit [09-MAR-2001 13:35:09] nsbfr: entry [09-MAR-2001 13:35:09] nsbaddfl: entry [09-MAR-2001 13:35:09] nsbaddfl: normal exit [09-MAR-2001 13:35:09] nsbfr: normal exit [09-MAR-2001 13:35:09] nsmfr: entry [09-MAR-2001 13:35:09] nsmfr: 2256 bytes at 0x130508 [09-MAR-2001 13:35:09] nsmfr: normal exit [09-MAR-2001 13:35:09] nsmfr: entry [09-MAR-2001 13:35:09] nsmfr: 484 bytes at 0x1398a8 [09-MAR-2001 13:35:09] nsmfr: normal exit [09-MAR-2001 13:35:09] nsclose: normal exit [09-MAR-2001 13:35:09] nscall: connecting... [09-MAR-2001 13:35:09] nsclose: entry [09-MAR-2001 13:35:09] nsclose: normal exit [09-MAR-2001 13:35:09] nladget: entry [09-MAR-2001 13:35:09] nladget: exit [09-MAR-2001 13:35:09] nsmfr: entry [09-MAR-2001 13:35:09] nsmfr: 144 bytes at 0x132cf8 [09-MAR-2001 13:35:09] nsmfr: normal exit [09-MAR-2001 13:35:09] nsmfr: entry [09-MAR-2001 13:35:09] nsmfr: 156 bytes at 0x138e70 [09-MAR-2001 13:35:09] nsmfr: normal exit [09-MAR-2001 13:35:09] nladtrm: entry [09-MAR-2001 13:35:09] nladtrm: exit [09-MAR-2001 13:35:09] nscall: error exit [09-MAR-2001 13:35:09] nioqper: error from nscall [09-MAR-2001 13:35:09] nioqper: nr err code: 0 [09-MAR-2001 13:35:09] nioqper: ns main err code: 12537 [09-MAR-2001 13:35:09] nioqper: ns (2) err code: 12560 [09-MAR-2001 13:35:09] nioqper: nt main err code: 507 [09-MAR-2001 13:35:09] nioqper: nt (2) err code: 0 [09-MAR-2001 13:35:09] nioqper: nt OS err code: 0 [09-MAR-2001 13:35:09] niomapnserror: entry [09-MAR-2001 13:35:09] niqme: entry [09-MAR-2001 13:35:09] niqme: reporting NS-12537 error as ORA-12537 [09-MAR-2001 13:35:09] niqme: exit [09-MAR-2001 13:35:09] niomapnserror: returning error 12537 [09-MAR-2001 13:35:09] niomapnserror: exit [09-MAR-2001 13:35:09] niotns: Couldn't connect, returning 12537 [09-MAR-2001 13:35:10] niotns: exit [09-MAR-2001 13:35:10] nsbfrfl: entry [09-MAR-2001 13:35:10] nsbrfr: entry [09-MAR-2001 13:35:10] nsbrfr: nsbfs at 0x132d90, data at 0x132dc8. [09-MAR-2001 13:35:10] nsbrfr: normal exit [09-MAR-2001 13:35:10] nsbrfr: entry [09-MAR-2001 13:35:10] nsbrfr: nsbfs at 0x1248d8, data at 0x132210. [09-MAR-2001 13:35:10] nsbrfr: normal exit [09-MAR-2001 13:35:10] nsbrfr: entry [09-MAR-2001 13:35:10] nsbrfr: nsbfs at 0x12d820, data at 0x1319f0. [09-MAR-2001 13:35:10] nsbrfr: normal exit [09-MAR-2001 13:35:10] nsbfrfl: normal exit [09-MAR-2001 13:35:10] nigtrm: Count in the NI global area is now 1 [09-MAR-2001 13:35:10] nigtrm: Count in the NL global area is now 1
The most efficient way to evaluate error codes is to find the most recent nserror entry logged, as the session layer controls the connection. The most important error messages are the ones at the bottom of the file. They are the most recent errors and the source of the problem with the connection.
For information about the specific return codes, use the Oracle UNIX error tool oerr, by entering the following at any command line:
oerr tns error_number
As an example, consider the following nserror entry logged in the trace file shown in Figure 17-6:
[09-MAR-2001 13:35:09] nserror: nsres: id=0, op=68, ns=12537, ns2=12560; nt[0]=507, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
Using oserr, you can find out more information about return codes 12537 and 507. (Bold denotes user input.)
oerr tns 12537 12537, 00000, "TNS:connection closed" // *Cause: "End of file" condition has been reached; partner has disconnected. // *Action: None needed; this is an information message. oerr tns 507 00507, 00000, "Connection closed" // *Cause: Normal "end of file" condition has been reached; partner has // disconnected. // *Action: None needed; this is an information message.
If you are still unable to resolve your problems, or if you are requested to contact Oracle Support Services to report the error, please have the following information at hand:
|
 Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|