Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Tracking Procedures

Re: Tracking Procedures

From: <amerar_at_iwc.net>
Date: 17 May 2007 06:09:35 -0700
Message-ID: <1179407375.716338.12050@l77g2000hsb.googlegroups.com>


On May 15, 3:38 pm, sybra..._at_hccnet.nl wrote:
> On 15 May 2007 12:03:10 -0700, "ame..._at_iwc.net" <ame..._at_iwc.net>
> wrote:
>
> >What about a script to parse v$sql every 3 minutes to get the names of
> >the stored procedures that are running or have run, then I can trace
> >it that way........
>
> >I assume that entries stay in v$sql for a bit of time once they are
> >done running???
>
> Horrible suggestion, as you would temporarily lock the library cache.
>
> Actually you could very easily 'instrument' those stored procedures,
> by wrapping them up in one new procedure per procedure, logging it's
> call in a table, and calling the original procedure.
> Obviously you would need a second user and synonyms to have the
> application call your wrappers.
> I know the idea is horrible, but as you seem to be already in an
> undocumented mess, it doesn't matter that much, does it.
>
> BTW did you consider using dba_dependencies?
>
> --
> Sybrand Bakker
> Senior Oracle DBA

Actually Sybrand, dba_dependencies is something that did not cross my mind.

Yes, this place is an undocumented mess, fortunately I did not create it.

At any rate, I'll take a look at that view and see if it offers me any hope in cleaning this place up.

Thanks for the suggestion, anything else, throw it my way......... Received on Thu May 17 2007 - 08:09:35 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US