RE: 10046 - Unable to trace JDBC thin client?

From: Wolfgang Breitling <breitliw_at_centrexcc.com>
Date: Tue, 17 Aug 2004 10:45:51 -0600
Message-Id: <6.1.0.6.2.20040817104045.031cb0c8@pop.centrexcc.com>

I can't believe that the type of connection would have anything to do with the ability to trace. My theory is that perhaps the jdbc thin client is doing frequent re-connects. If I'm correct you should see that the sid stays the same, but that the serial# constantly changes. I would certainly check that. If that is the case, then the session for which you turned on the trace (you need to specify sid AND serial#) doesn't even exist anymore by the time you managed to issue the statement to enable the trace, being replaced by a new sid/serial# session.
I don't have anything handy at the moment to test that.

At 08:44 AM 8/17/2004, you wrote:
>Are you confirming that this feature (tracing jdbc thin client) is not
>supported? Why would Oracle not support the tracing of a jdbc thin
>client?

Regards

Wolfgang Breitling
Centrex Consulting Corporation
http://www.centrexcc.com

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Tue Aug 17 2004 - 11:41:37 CDT