Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: 10046 - Unable to trace JDBC thin client?

Re: 10046 - Unable to trace JDBC thin client?

From: Tanel Põder <tanel.poder.003_at_mail.ee>
Date: Wed, 18 Aug 2004 12:42:14 +0300
Message-ID: <0b2101c48508$cf92e640$c1859fd9@porgand>


The trace should definitely be written, independent on any client, as long as you manage to set the 10046 event.

If you manage to erase the tracefile of a unix process which has the tracefile open or has had the tracefile open, then when re-enabling trace, the server process continues to write trace to this erased file (using file handle which it got before erasing).

Could this be the problem? Just try to trace with a new (dedicated server) session or use alter session set tracefile_identifier to direct trace to another file.

Otherwise, enable the trace, query your processes SPID and use truss or strace to find out whether trace write calls are actually made.

Tanel.

> None taken, sometimes it is the obvious. In this case I have cleared out
> the entire directory prior to my tests. In addition, I have successfully
> executed the same process with a SQL*Plus session.
> I will be researching the oradebug and set_ev methods to see if I receive
> similar results. Thanks for all the input.
>



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 Wed Aug 18 2004 - 04:48:42 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US