Re: Tracing the given client id
From: Mladen Gogala <no_at_email.here.invalid>
Date: Fri, 2 Jul 2010 19:41:34 +0000 (UTC)
Message-ID: <pan.2010.07.02.19.41.33_at_email.here.invalid>
On Fri, 02 Jul 2010 21:26:17 +0200, Maxim Demenko wrote:
> Such situation may happen if trace was already enabled by other means
> for session in question and tracefile was (re)moved, but session is
> still open. If that was the case, then, oradebug
>
close_trace;dbms_monitor.client_id_trace_disable;dbms_monitor.client_id_trace_enable
> should make tracefile "reappear".
>
> Best regards
>
> Maxim
Date: Fri, 2 Jul 2010 19:41:34 +0000 (UTC)
Message-ID: <pan.2010.07.02.19.41.33_at_email.here.invalid>
On Fri, 02 Jul 2010 21:26:17 +0200, Maxim Demenko wrote:
> On 02.07.2010 20:42, Mladen Gogala wrote:
>> I executed the following code: >> >> >> 1 begin >> 2 DBMS_MONITOR.CLIENT_ID_TRACE_ENABLE( 3 client_id => >> 'Insight', >> 4 waits => TRUE, >> 5 binds => False); >> 6* end; >> SQL> / >> >> There aren't any trace files. I also enabled statistics collection but >> all the stats are zero. The database is 10.2.0.5, Linux x86-64, RH 4.4. >> Has anybody seen anything like that? I opened a TAR >> >>
> Such situation may happen if trace was already enabled by other means
> for session in question and tracefile was (re)moved, but session is
> still open. If that was the case, then, oradebug
>
close_trace;dbms_monitor.client_id_trace_disable;dbms_monitor.client_id_trace_enable
> should make tracefile "reappear".
>
> Best regards
>
> Maxim
That's not the case. At any rate, I want to trace 27 processes. Doing the oradebug trick would defeat the purpose.
-- http://mgogala.byethost5.comReceived on Fri Jul 02 2010 - 14:41:34 CDT