You would have either to add the columns to each table and update them with a trigger, or have the trigger write this info to an audit or log file.
----------------------------------------------------------------------------
The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb
Oracle's AUDIT command has a couple of problems: 1) It carries with it an inordinate amount of Oracle-server overhead, and 2) It really is not a good "auditor" in terms of "when" did "who" do "what" to "whom". The best auditing methodology is follow LKBrwnDBA's advice: create an audit trigger. That way you incur CPU costs only when necessary (i.e., when the trigger fires) and you can track precisely what you want.
If you do not have experience with audit triggers, please re-post such and we can provide you with code samples.
Mufasa
(aka Dave of Sandy, Utah, USA @ 19:41 (28Jul04) UTC (aka "GMT" and "Zulu"), 12:41 (28Jul04) Mountain Time)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.