RE: sql_trace deprecated on 10gr2 what to use instead?

From: Lex de Haan <lex.de.haan_at_naturaljoin.nl>
Date: Fri, 11 Nov 2005 16:45:13 +0100
Message-Id: <20051111154516.5D123225023@turing.freelists.org>

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. :)

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

Received on Fri Nov 11 2005 - 09:47:27 CST