Re: Tracing the given client id
From: Maxim Demenko <mdemenko_at_gmail.com>
Date: Fri, 02 Jul 2010 21:26:17 +0200
Message-ID: <4C2E3D59.5060004_at_gmail.com>
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
>
Date: Fri, 02 Jul 2010 21:26:17 +0200
Message-ID: <4C2E3D59.5060004_at_gmail.com>
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 Received on Fri Jul 02 2010 - 14:26:17 CDT