AW: Forms/reports Application and DB security

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@gmail.com]
Gesendet: Montag, 12. Juni 2006 08:08
An: Castillo Sánchez, Félix (HZD)
Cc: oracle-l@freelists.org
Betreff: Re: Forms/reports Application and DB security

Hi Castillo,

What do you mean by future sessions ?

2006/6/12, F.Castillo@hzd.hessen.de < F.Castillo@hzd.hessen.de>:

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@gmail.com]
Gesendet: Freitag, 9. Juni 2006 15:11
An: Castillo Sánchez, Félix (HZD)
Cc: oracle-l@freelists.org
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.
--
http://www.freelists.org/webpage/oracle-l

AW: Forms/reports Application and DB security

F Castillo

2006-06-12