Re: Triggers
From: ddf <oratune_at_msn.com>
Date: Tue, 8 Sep 2009 09:20:12 -0700 (PDT)
Message-ID: <067e745d-6b1c-4735-962a-c81bce26b7ff_at_o10g2000yqa.googlegroups.com>
On Sep 8, 11:05 am, The Magnet <a..._at_unsu.com> wrote:
> Hi,
>
> Probably a nutty question, but, is it possible to find out what
> program contained the DML which fired the trigger?
>
> We have a particular situation, and next to mining the logs, we're not
> sure how to find who or what is updating a certain row. So, we should
> a trigger on the table testing for this particular user ID and
> capturing information is the best way to go.
>
> If there are others, I'm all ears.
Date: Tue, 8 Sep 2009 09:20:12 -0700 (PDT)
Message-ID: <067e745d-6b1c-4735-962a-c81bce26b7ff_at_o10g2000yqa.googlegroups.com>
On Sep 8, 11:05 am, The Magnet <a..._at_unsu.com> wrote:
> Hi,
>
> Probably a nutty question, but, is it possible to find out what
> program contained the DML which fired the trigger?
>
> We have a particular situation, and next to mining the logs, we're not
> sure how to find who or what is updating a certain row. So, we should
> a trigger on the table testing for this particular user ID and
> capturing information is the best way to go.
>
> If there are others, I'm all ears.
You could set event 10046 at the instance level, but that would be overkill, I think. An after update trigger would work, provided you populate an auditing table with the desired information. You'll need to regularly monitor the table for size, unless this is a 'one-shot' event where once you find the 'cuplrit' you disable the trigger.
Of course others may have differing opinions.
David Fitzjarrell Received on Tue Sep 08 2009 - 11:20:12 CDT