997191 wrote:Yes, you can drop the trigger; but choose not to do so.
Hi Sybrand Bakker,
Thanks for the reply ....
We cant drop the trigger ,
because we have to stop unwanted DDL execution in business hours .I can stop unwanted DLL during business hours by firing anyone who issue DDL during business hours;
997191 wrote:Only DBA should be able to do DDL to start with.
Please find the trigger below ... Advice me how to write an exception ....
CREATE OR REPLACE TRIGGER no_ddl_trig
If (ora_login_user ='SYS')Why do you have logins as SYS doing DDL ?
ora_dict_obj_name like 'BIN$%'What sort of actions did you intend to capture with this ?
997191 wrote:I think you might be missing the point of what other users have suggested. Writing an exception to a trigger that prevents DDL won't fix your problem, as it's only a symptom of it. To fix your problem, work with management and your team to assure that DDL is not getting executed during business hours, and revoke privileges from users that don't need these permissions. You must understand, DDL creation during business hours is a problem that should not exist when security best practices have been followed, and when proper change control is in place.
I need help to write an exception in this trigger to allow that create global temporary query execution.