Re: DBMS_APPLICATION_INFO

From: ExecMan <artmerar_at_yahoo.com>
Date: Thu, 23 Feb 2012 11:09:38 -0800 (PST)
Message-ID: <549285f1-dea7-4dbb-9aba-ce5a7818efba_at_p7g2000yqk.googlegroups.com>



On Feb 23, 12:53 pm, Svend Jensen <svend.SPAMKILLjen..._at_secret.dk> wrote:
> Hi
>
> Besides the set_client_info, you have the set_module with two columns,
> module and action. I believe a clever combination could fit your needs.
> /Svend
>
> > Hi,
>
> > We are using DBMS_APPLICATION_INFO to help track which procedures are
> > running.  However, one issue we are having is when procedures call
> > other procedures.
>
> > For example, at the top of PROCEDURE_A we have this:
> >     DBMS_APPLICATION_INFO.SET_CLIENT_INFO('PROCEDURE_A');
>
> > And at the end of PROCEDURE_A we have this:
>
> > DBMS_APPLICATION_INFO.SET_CLIENT_INFO(null);
>
> > Now, say PROCEDURE_A calls PROCEDURE_B, then PROCEDURE_B has:
> >     DBMS_APPLICATION_INFO.SET_CLIENT_INFO('PROCEDURE_B');
> > .
> > .
> >     DBMS_APPLICATION_INFO.SET_CLIENT_INFO(null);
>
> > That wipes out the value and when control is returned to PROCEDURE_A,
> > there is no value set anymore.  So, this is great for a single
> > procedure, but how can one integrate nested procedure calls and being
> > able to use DBMS_APPLICATION_INFO more dynamically?
>
> > Any thoughts or suggestions?

Thanks everyone for all your suggestions. This gives me some good starting points. Received on Thu Feb 23 2012 - 13:09:38 CST

Original text of this message