RE: Re-setting V$tables

Hi,

Um, why reinvent the wheel?

If you're on 10g, just use dbms_monitor for selectively tracing and calculating stats based on service, module, action and client id...

DBMS_MONITOR is not just another wrapper around 10046 trace event, it's a completely new dimension to tracing and statistics collection which allows you to instrument your code at a very fine grained level, across sessions and even across instances.

Look at DBMS_STATS.SERV_MOD_ACT_STAT_ENABLE and DBMS_STATS.SERV_MOD_ACT_TRACE_ENABLE for example..

Tanel.  

> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of rjamya
> Sent: Wednesday, October 11, 2006 19:04
> To: knecht.stefan_at_gmail.com
> Cc: mgogala_at_verizon.net; oracle-l
> Subject: Re: Re-setting V$tables
>
> I like this idea about wrapping dbms_application_info and do
> the captures whenever set_module is called.
>
> Mladen, looks like you found the easiest solution ... oh yeah
> and don't forget to give your duhvelopers a cookie for using
> dbms_application_info.

--
http://www.freelists.org/webpage/oracle-l