Hi Muhammed
you can use the dbms_monitor package (serv_mod_act_trace_enable) to enable
tracing for all (future) sessions
Like
First: dbms_application_info.set_module( module_name => 'module',
action_name => 'what I am doing' );
then
begin
dbms_monitor.serv_mod_act_trace_enable (
service_name => 'ora10g',
module_name => 'module',
action_name => dbms_monitor.all_actions,
waits => true,
binds => false,
instance_name => null );
end;
You can take a look at
http://www.oraconsult.de/index.php?option=com_content&task=view&id=30&Itemid=71.
It's written in German but I think you can get an idea when looking at the
code snippets
Felix
-----Ursprüngliche Nachricht-----
*Von:* Muhammed Soyer [mailto:msoyer@xxxxxxxxx]
*Gesendet:* Montag, 12. Juni 2006 08:08
*An:* Castillo Sánchez, Félix (HZD)
*Cc:* oracle-l@xxxxxxxxxxxxx
*Betreff:* Re: Forms/reports Application and DB security
Hi Castillo,
What do you mean by future sessions ?
2006/6/12, F.Castillo@xxxxxxxxxxxxx < F.Castillo@xxxxxxxxxxxxx>:
>
> Hola Juan
>
> Using set_module has also the side effect to give us the possibility to
> monitor and trace even future sessions.
>
>
> Gracias
>
> Felix
>
> -----Ursprüngliche Nachricht-----
> Von: Juan Carlos Reyes Pacheco [mailto:juancarlosreyesp@xxxxxxxxx]
> Gesendet: Freitag, 9. Juni 2006 15:11
> An: Castillo Sánchez, Félix (HZD)
> Cc: oracle-l@xxxxxxxxxxxxx
> Betreff: Re: Forms/reports Application and DB security
>
>
> Hi Castillo
> If you want to enable control by applications you can think in using
> DBMS_APPLICATION_INFO.SET_MODULE( module_name => cXNombre, action_name =>
> 'Apertura' );
>
> But I see this can be more complex, beacuse you must guarantee every
> session had set this variables.
>
> role with password is a better solution, unles I didn't understand your
> comment.
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
