Re: auditing dml

Ok, I figured this out. It was because the mask name I gave it after the -u ( sentrytest) was not a real user. As soon as I created the mask with a real username, then it worked. The problem is I am not getting enough data from the audit info. Does anyone have any good trigger schemes to put a trigger on every table on insert, delete, update, so that I can save the actual sql that was run ? Thanks ! Floyd ----- Original Message ----- From: "Floyd Wellershaus" <floyd@fwellers.com> Sent: Wed, October 29, 2008 7:46 Subject:Re: auditing dml Thanks. I just saw that, and have changed the audit path to $INFORMIXDIR/audit_test. I changed that directory permissions to 770 as the manual describes, and I still get the same results. A zero byte file gets created but nothing goes into it. ----- Original Message ----- From: "Clive Eisen" <clive@serendipita.com> Sent: Wed, October 29, 2008 7:18 Subject:Re: auditing dml Floyd Wellershaus wrote: > Thanks ! > Ok, so just for a test, I did the following. > > onaudit -a -u testsentry -e +CRTB > onaudit -l 1 > onaudit -p /db_reorg> > onaudit -c shows:> Current audit system configuration: > ADTMODE = 1 > ADTERR = 0 > ADTPATH = /db_reorg You don't have permission to write to / as informix Try onaudit -p $INFORMIXDIR/db_reorg -- Clive ----- End of original message ----- _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list ----- End of original message -----