Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 
 

SQL*Net Tracing Tips

Expert Oracle Database Tips by Donald BurlesonDecember 3, 2015

Question: I am getting the ORA-12560 error and I need to take a full SQL*Net trace to find the root cause of my problem.  What is the procedure for doing a SQL*Net trace?

Answer:  You should check the details on ORA-12560 error troubleshooting.

Also note that when you see bad SQL*Net performance, you can trace the SQL*net round trips.

There are several ways to trace SQL*net connections, and here is how to do a SQL*net trace for both a SQL*Net client trace and server SQL*Net tracing:

Server side SQL*Net trace:

By default, trace on UNIX systems is written to $ORACLE_HOME/network/trace/sqlnet.trc, and log is written to sqlnet.log file under the same directory. On the server side, log and trace destinations can be defined with the following parameters: log_directory_, log_file_, trace_directory_ and trace_file_.

All these parameters should be configured in the listener.ora file. By default, server logs and traces are stored in listener.log and listener.trc files under the $ORACLE_HOME/network/trace directory.

Note that, by default, logging is turned on and this behavior can be changed with the logging_ parameter of the listener.ora file. One can switch between different trace standards on the client side using the trace_level_client parameter of sqlnet.ora. At the server side, the trace level parameter is called trace_level_ and it should be included in the listener.ora.

Client side SQL*Net tracing:

On the client side, it is possible to define the directory where to put log and trace files in the sqlnet.ora file using the log_directory_client and trace_directory_client parameters, respectively.  The SQL*Net tracing log and trace file names are defined with the log_directory_client and trace_directory_client parameters of the sqlnet.ora file.

STEP 1:  Make a SQL*net trace file directory on the client machine called c:\trace

STEP 2:  Add the following lines to your sqlnet.ora file on your client PC:

trace_level_client = 16
trace_file_client = cli
trace_directory_client = c:\trace
trace_unique_client = on
trace_timestamp_client = on
trace_filelen_client = 100
trace_fileno_client = 2
log_file_client = cli
log_directory_client = c:\trace\log
tnsping.trace_directory = c:\trace\trace
tnsping.trace_level = admin

STEP 3:  When you are finished with the SQL*trace, be sure to remove the lines from the sqlnet.ora file.

Also, check this page for additional SQL*Net troubleshooting and diagnostics tips.

 
Get the Complete
Oracle SQL Tuning Information 

The landmark book "Advanced Oracle SQL Tuning  The Definitive Reference"  is filled with valuable information on Oracle SQL Tuning. This book includes scripts and tools to hypercharge Oracle 11g performance and you can buy it for 30% off directly from the publisher.

 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2016

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.


 

��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster