You have done an insert in the trigger but have not committed it. so changes would not be visible. So use a commit along with PRAGMA AUTONOMOUS TRANSACTION and i hope it would help.No, please don't do this.
Padma.... wrote:Noooooo! Do not commit inside trigger (except perhaps when error logging).
You have done an insert in the trigger but have not committed it. so changes would not be visible. So use a commit along with PRAGMA AUTONOMOUS TRANSACTION and i hope it would help.
938946 wrote:If your requirement is to "write a trigger", then whoever created the requirement needs some serious re-eduction.
thank you all for quick response and my requirement is to write a trigger to capture "select,insert,update and delete" statements executed by the users(or clients) in the oracle database (10g or 10.2.0.3),from which machine(machine name)these statements executed,machine ipaddress,logon time of users who run the sql statements ,statements execution time .
your help HIGLY APPRECIATED.
938946 wrote:What, specifically, about your requirement do you feel cannot be met with either standard auditing or Fine Grained Auditing, already available as part of the oracle database? I seriously doubt you need to re-invent the wheel.
my requirement is to capture tha data plus sql statements.i want customised auditing (for a single db user).