Jared Still wrote,on my timestamp of 12/01/2010 2:31 PM:
The point is that there are 200 tables, so how do you verify that somehow the new features didn't make a change to another table that you assumed wasn't touched by the tests.
Couldn't just turning the monitoring on for those tables resolve the issue?All the auditor wants to know is if the tables got changed, not by how much and where. Together with verifying last_ddl from dba_objects, that would solve the problem?
-- Cheers Nuno Souto in sunny Sydney, Australia dbvision@xxxxxxxxxxxx -- //www.freelists.org/webpage/oracle-l