Mladen Gogala wrote:
> On Fri, 24 Dec 2004 07:32:49 -0800, fitzjarrell wrote:
>
> > If someone knows of a method of setting event 10046 for an unknown
> > session or fleeting sessions without knowing the SID or SERIAL#
that
> > is, I believe, what the OP is looking for.
>
> DBMS_MONITOR.CLIENT_ID_TRACE_ENABLE(
> client_id IN VARCHAR2,
> waits IN BOOLEAN DEFAULT TRUE,
> binds IN BOOLEAN DEFAULT FALSE);
>
> Client ID is an identifier set by using
> DBMS_APPLICATION_INFO.SET_CLIENT_INFO.
> DBMS_MONITOR package looks like this:
>
> SQL> desc dbms_monitor
> PROCEDURE CLIENT_ID_STAT_DISABLE
> Argument Name Type In/Out
Default?
> ------------------------------ ----------------------- ------
> CLIENT_ID VARCHAR2 IN
> PROCEDURE CLIENT_ID_STAT_ENABLE
> Argument Name Type In/Out
Default?
> ------------------------------ ----------------------- ------
> CLIENT_ID VARCHAR2 IN
> PROCEDURE CLIENT_ID_TRACE_DISABLE
> Argument Name Type In/Out
Default?
> ------------------------------ ----------------------- ------
> CLIENT_ID VARCHAR2 IN
> PROCEDURE CLIENT_ID_TRACE_ENABLE
> Argument Name Type In/Out
Default?
> ------------------------------ ----------------------- ------
> CLIENT_ID VARCHAR2 IN
> WAITS BOOLEAN IN
DEFAULT
> BINDS BOOLEAN IN
DEFAULT
> PROCEDURE SERV_MOD_ACT_STAT_DISABLE
> Argument Name Type In/Out
Default?
> ------------------------------ ----------------------- ------
> SERVICE_NAME VARCHAR2 IN
> MODULE_NAME VARCHAR2 IN
> ACTION_NAME VARCHAR2 IN
DEFAULT
> PROCEDURE SERV_MOD_ACT_STAT_ENABLE
> Argument Name Type In/Out
Default?
> ------------------------------ ----------------------- ------
> SERVICE_NAME VARCHAR2 IN
> MODULE_NAME VARCHAR2 IN
> ACTION_NAME VARCHAR2 IN
DEFAULT
> PROCEDURE SERV_MOD_ACT_TRACE_DISABLE
> Argument Name Type In/Out
Default?
> ------------------------------ ----------------------- ------
> SERVICE_NAME VARCHAR2 IN
> MODULE_NAME VARCHAR2 IN
DEFAULT
> ACTION_NAME VARCHAR2 IN
DEFAULT
> INSTANCE_NAME VARCHAR2 IN
DEFAULT
> PROCEDURE SERV_MOD_ACT_TRACE_ENABLE
> Argument Name Type In/Out
Default?
> ------------------------------ ----------------------- ------
> SERVICE_NAME VARCHAR2 IN
> MODULE_NAME VARCHAR2 IN
DEFAULT
> ACTION_NAME VARCHAR2 IN
DEFAULT
> WAITS BOOLEAN IN
DEFAULT
> BINDS BOOLEAN IN
DEFAULT
> INSTANCE_NAME VARCHAR2 IN
DEFAULT
> PROCEDURE SESSION_TRACE_DISABLE
> Argument Name Type In/Out
Default?
> ------------------------------ ----------------------- ------
> SESSION_ID BINARY_INTEGER IN
DEFAULT
> SERIAL_NUM BINARY_INTEGER IN
DEFAULT
> PROCEDURE SESSION_TRACE_ENABLE
> Argument Name Type In/Out
Default?
> ------------------------------ ----------------------- ------
> SESSION_ID BINARY_INTEGER IN
DEFAULT
> SERIAL_NUM BINARY_INTEGER IN
DEFAULT
> WAITS BOOLEAN IN
DEFAULT
> BINDS BOOLEAN IN
DEFAULT
>
> SQL>
>
>
>
> --
> Artificial Intelligence is no match for natural stupidity.
And that will work wonders if he could only use it outside of a
trigger, however he cannot as he stated originally:
- The problem is, I can not change the source code ...
So he can't directly use a call to dbms_application_info. So, it
appears he is left with a trigger-based solution. I imagine either
process (the modified trigger by Pete Finnigan, or writing a trigger
using dbms_monitor) should suffice.
I do thank you for the information, it's be quite educational.
David Fitzjarrell
Received on Fri Dec 24 2004 - 21:36:20 CST
