Re: sql_trace deprecated on 10gr2 what to use instead?
- From: Juan Carlos Reyes Pacheco <juancarlosreyesp@xxxxxxxxx>
- To: lex.de.haan@xxxxxxxxxxxxxx
- Date: Fri, 11 Nov 2005 11:54:30 -0400
If you don't like dbms_monitor, you can use this (on 10g at least)
DBMS_SESSION.SESSION_TRACE_ENABLE(
waits IN BOOLEAN DEFAULT TRUE,
binds IN BOOLEAN DEFAULT FALSE);
On 11/11/05, Lex de Haan <lex.de.haan@xxxxxxxxxxxxxx> wrote:
> Egor,
>
> you probably mean dbms_session.set_sql_trace --
> but onfortunately, that procedure doesn't allow you
> to include/exclude bind and wait info in your trace files...
>
> kind regards,
>
> Lex.
>
> ---------------------------------------------------------------------
> Jonathan Lewis Seminar http://www.naturaljoin.nl/events/seminars.html
> ---------------------------------------------------------------------
>
> > DBMS_SESSION , few optoins
> > DBMS_SUPPORT, not documented
> > DBMS_MONITOR, the winner!!
>
> The only problem is that execute of DBMS_MONITOR is not granted by default to
> PUBLIC (contrary to DBMS_SESSION).
> So, for ordinary developer dbms_session.session_trace_enable is the winner.
>
> As for SQL_TRACE, I think that it's deprecated because you need to have 'alter
> session' privilege (which might be a bit dangerous) for using it. So it might
> be
> better to just revoke 'alter session', grant execute on dbms_session to public
> and document sql_trace as deprecated. :)
>
>
>
--
Oracle Certified Profesional 9i 10g
Orace Certified Professional Developer 6i
8 years of experience in Oracle 7,8i,9i,10g and developer 6i
--
//www.freelists.org/webpage/oracle-l
Other related posts:
