Yes, Mario, but only if you create a TRIGGER on the table(s) that you want to monitor. You could have a table that has columns for OWNER, TABLE_NAME, LAST_UPDATED, then whenever any INSERT, UPDATE, or DELETE occurs, the trigger would simply update the row for the table with the current value of SYSDATE. The nice efficiency about that is that there would be only one UPDATE statement occurring to the table no matter how many rows in the subject table that you are working on.
Let us know if this gives you the vision you need to resolve this issue.
set init.ora parameter audit_trail=true. this only enables the feature, does not actually do anything. second, issue command AUDIT ALL ON COUNTRY_LIST BY ACCESS; The results are produced faster and safer than when using triggers. Third, to see the results SELECT * FROM DBA_AUDIT_TRAIL WHERE ....
To turn off auditing for a table just do NOAUDIT ALL ON <table_name>; Or, set init.ora parameter audit_trail=false. In this case all table audit settings are preserved but not used.
MarkRem
Author, Oracle Database 10g: From Nuts to Soup
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.