RE: 10046 - Unable to trace JDBC thin client?

  • From: DENNIS WILLIAMS <DWILLIAMS@xxxxxxxxxxxxx>
  • To: "'oracle-l@xxxxxxxxxxxxx'" <oracle-l@xxxxxxxxxxxxx>
  • Date: Tue, 17 Aug 2004 09:25:41 -0500

Tracy
   Where does your problem lie? Are you able to locate the session? Having
located the session, are you then unable to produce a trace file? I haven't
tried this, but like you we use thin client a lot so I have a keen interest
in the answer.

Dennis Williams
DBA
Lifetouch, Inc.

"We all want progress, but if you're on the wrong road, progress means
doing an about-turn and walking back to the right road; in that case,
the man who turns back soonest is the most progressive." 
-- C.S. Lewis


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Tracy Rahmlow
Sent: Tuesday, August 17, 2004 9:25 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: 10046 - Unable to trace JDBC thin client?


Oracle EE 8.1.7.4 on AIX 4.3.3 utilizing IBM Websphere - 
I can currently trace a SQL*Plus session and I receive the trace file. 
Here is what I am executing:

 - exec sys.dbms_support.start_trace_in_session(13, 2358, true, false) 
  -  some sql statement
  -  exec sys.dbms_support.stop_trace_in_session(13, 2358)

However, when attempting to trace a "JDBC thin client" in the same fashion 
I never can produce a trace file.  I saw a brief reference on Metalink in 
a forum that tracing a JDBC thin client was not possible.  Is this true 
and is it documented other than in a forum?  If true, do I have any 
alternatives since most of our new applications will be utilizing the jdbc 
thin client?  Thanks

American Express made the following
 annotations on 08/17/2004 07:25:07 AM
----------------------------------------------------------------------------
--
****************************************************************************
**

     "This message and any attachments are solely for the intended recipient
and may contain confidential or privileged information. If you are not the
intended recipient, any disclosure, copying, use, or distribution of the
information included in this message and any attachments is prohibited.  If
you have received this communication in error, please notify us by reply
e-mail and immediately and permanently delete this message and any
attachments.  Thank you."

****************************************************************************
**


============================================================================
==


----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Other related posts: