http://technology.amis.nl/2005/09/29/sqlnet-debugging-quick-reference-guide/?utm_source=rss&utm_medium=rss&utm_campaign=sqlnet-debugging-quick-reference-guide Fri, 12 Apr 2013 10:04:09 +0000 hourly 1 http://wordpress.org/?v=3.5.1 http://technology.amis.nl/2005/09/29/sqlnet-debugging-quick-reference-guide/#comment-2485 Marco Gralike Fri, 14 Oct 2005 09:34:40 +0000 /?p=823#comment-2485 Thanks, Natalka for your comment. In the sqlnet.ora file you can enable listener logging, client logging, names logging etc, but as mentioned this excercise is a “Small introduction to SQL*Net debugging” (and even when you print this, it is alread 7 pages…)

]]> http://technology.amis.nl/2005/09/29/sqlnet-debugging-quick-reference-guide/#comment-2484 Natalka Roshak Wed, 12 Oct 2005 16:42:39 +0000 /?p=823#comment-2484 Great post! I would add something about sql*net tracing — this is set up in the sqlnet.ora and can give you a shortcut to the solution. Just add something like this to the sqlnet.ora:
trace_level_client=admin
trace_directory_client=C:\oracle\oracli92\network\trace
trace_file_client=C:\oracle\oracli92\network\trace\cli.trc
trace_unique_client=true
The trace files will show up in the trace directory, C:\oracle\oracli92\network\trace in this example, and give you a pretty good idea of what’s going on. The information is similar to what trcroute gives you, but more detailed and less structured, and available in every client installation.

]]>