Re: Trigger on v$sql catalog table

db dude wrote:

> Why is this a bad idea. Will it degrade performance or cause any other problems?
>
> Auditing seems to degrade performance which I am trying to avoid or lessen.
>
> "Anurag Varma" <avdbi_at_hotmail.com> wrote in message news:<e0oPa.5037$4p1.2640_at_news02.roc.ny>...
> > "Anurag Varma" <avdbi_at_hotmail.com> wrote in message news:AVnPa.5036$Wp1.548_at_news02.roc.ny...
> > >
> > > "db dude" <db_guy_2002_at_yahoo.com> wrote in message news:f4a8da28.0307101513.23c0f2ce_at_posting.google.com...
> > > > Hi,
> > > >
> > > > Can anyone tell me what is the base table for public.v$sql. The DDL
> > > > for v$sql points to v_$sql (which is again a view).
> > > >
> > > > I am interested in creating a trigger on the base table of
> > > > public.v$sql to moniter sql queries.
> > >
> > > forget about it. Not possible. Don't even think about it.
> > > <insert_your_favorite_warning_here>
> > >
> > > Anurag
> > >
> > >
> >
> > select * from V$FIXED_VIEW_DEFINITION where view_name = 'GV$SQL';
> > The table name comes up as x$kglcursor
> >
> > ;) Now let me see if after all those warnings you still go ahead and try it.
> >
> > Anurag

Along with all of the other good advice you are getting consider the following:

What would be the implication if the trigger raised an error?

--
Daniel Morgan
http://www.outreach.washington.edu/extinfo/certprog/oad/oad_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)