Re: ddl audit trigger

  • From: rjamya <rjamya@xxxxxxxxx>
  • To: GLeonard@xxxxxxxxxxxxx
  • Date: Thu, 13 Jan 2005 07:36:13 -0500

let me put it this way ... 

if you shot yourself  dead, would you still call 911 and report yourself? 

since drop will acquire a ddl lock (loose term), execution will be
prevented as execution also needs a lock to stop the underlying object
from being modified. If what you want must happen, this will become a
classic example of a race condition. Basically first one to get the
lock wins, in this case the 'drop' got the lock first.

obviously I could be wrong, but a correction is appreciated.

On Thu, 13 Jan 2005 14:06:14 +0200, Leonard, George
<GLeonard@xxxxxxxxxxxxx> wrote:
> Hi all
> Written a database trigger ddltrigger that fires on ddl on database.
> Owned by system
> Prompt Creating Trigger ddltrigger
> =09ddlaudit.audit;
> END;
> This then calls a package that does a small amount of work (also owned
> by system), this then calls the meaty packaged owned by another user
> (not system) that does the actual logging.
> Problem I am having is this trigger does not fire when it is dropped
> itself.
> Any ideas
> George
> =20________________________________________________
> George Leonard
> Oracle Database Administrator
> New Dawn Technologies @ Wesbank
> E-mail:gleonard@xxxxxxxxxxxxx
> =20
> You Have The Obligation to Inform One Honestly of the risk, And As a
> Person
> You Are Committed to Educate Yourself to the Total Risk In Any Activity!
> Once Informed & Totally Aware of the Risk,
> Every Fool Has the Right to Kill or Injure Themselves as They See Fit!
> =20
> _________________________________________________________________________=
> __________________________
> The views expressed in this email are, unless otherwise stated, those of =
> the author and not those
> of the FirstRand Banking Group an Authorised Financial Service Provider o=
> r its management.
> The information in this e-mail is confidential and is intended solely for=
> =20the addressee.
> Access to this e-mail by anyone else is unauthorised.
> If you are not the intended recipient, any disclosure, copying, distribut=
> ion or any action taken or=20
> omitted in reliance on this, is prohibited and may be unlawful.
> Whilst all reasonable steps are taken to ensure the accuracy and integrit=
> y of information and data=20
> transmitted electronically and to preserve the confidentiality thereof, n=
> o liability or=20
> responsibility whatsoever is accepted if information or data is, for what=
> ever reason, corrupted=20
> or does not reach its intended destination.
> =20                              ________________________________
> --
> //

select standard_disclaimer from company_requirements where category =

Other related posts: