Re: DBMS_APPLICATION_INFO

From: Peter Schneider <pschneider1968_at_googlemail.com>
Date: Tue, 21 Feb 2012 19:50:56 +0100
Message-ID: <ji0p4d$et3$1_at_online.de>

Am 21.02.2012 16:04, schrieb ExecMan:
> 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?

Write a wrapper around DBMS_APPLICATION_INFO and implement a stack; with calls for push_and_set and pop_and_set...

Regards
Peter

-- 
The only way to keep your health is to eat what you don't want, drink what
you don't like, and do what you'd rather not. -- Mark Twain

Received on Tue Feb 21 2012 - 12:50:56 CST