Re: Catch table droppers

Hi,
If you don't want to use the utilities to do what you want to do, you can't do it. It's not recommended - nor always possible, to define triggers on the system/sys dictionary.

AUDIT is the only option for tracing DDL commands. Enabling it requires shutdown - you're right. But you're up 5 seconds later. Change your init script to set AUDIT_TRAIL=TRUE, stop the database and restart it. That's it - it's enabled and ready. Then issue the AUDIT commands from SVRMGR or SQL*Plus.

Most databases are shut down during the night. Very few databases require 24hours availability. If that is the case, you must work with the DBA to find when they will shut it down to change the status. In the old days, using Audit would touch performance - but today the effect is so little that it's almost impossible to measure.

• Peter H. Larsen

krishnanand_at_hotmail.com wrote:

> Hi,
>
> Problem:
>
> I wish to trace out the people who drop any table in the Database &
> store details like username,date of action,... etc in a history table
> accessible only to me.
>
> " I can't USE the database auditing feature for this purpose
> since currently our DB is not audited and if I wish to start
> auditing I need to edit AUDIT_TRAIL , shutdown and startup the
> databse, which I am strictly porhibited from doing currently."
>
> I tried creating Triggers on sys.obj$ as SYS but still it says
> can't create triggers on objects owned by SYS.
>
> Is there any other way ?
>
> Thanx.
>
> Platform: Oracle 7.3 on HP-UX 10.20
>
> -------------------==== Posted via Deja News ====-----------------------
> http://www.dejanews.com/ Search, Read, Post to Usenet
Received on Mon Oct 27 1997 - 00:00:00 CST