On Tue, 17 Aug 2004 09:25:16 -0500, Tracy Rahmlow
<tracy.rahmlow_at_aexp.com> wrote:
> 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
Issue the alter session statement from the client itself - my
preferred option? Use the thick client for troubleshooting? I have no
idea whether the statement is true or not, but it *may* be true that
the 10046 event requires a session to have been established over OCI.
If this is true then presumably the wire-protocol drivers from merant
would also be affected. If I get a chance I'll test it on the way home
tonight - tracing jdeveloper might be fun.
--
Niall Litchfield
Oracle DBA
http://www.niall.litchfield.dial.pipex.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 - 10:17:34 CDT
