Hi, that sounds a bit daft but still wouldn't a db audit trail with reports periodically sent to the auditor do the job? You know audit update, insert delete on .... On 1/11/10, Dennis Williams <oracledba.williams@xxxxxxxxx> wrote: > List, > > We have an audit finding related to data integrity. I'm looking for a way to > detect all database changes on a small test database. Fortunately the > environment is well-contained. Typically when we've made application > changes, we verify that the data changes are what we expect. The auditors > are insisting that we somehow verify there aren't unexpected changes in > other tables. The environment is Oracle 10.2.0.4 on Solaris. I have three > thoughts: > > 1. The test database is freshly loaded from an export. After the tests, take > an export and use UNIX "diff" and compare with the import. > 2. Log Miner, or somehow more directly inspecting the archive logs. > 3. Use some of the new flashback features to detect changes. This just > occurred to me and I haven't had time to investigate it. > > Has anyone else done anything like this before? > > Dennis Williams > -- Sent from my mobile device Niall Litchfield Oracle DBA http://www.orawin.info -- //www.freelists.org/webpage/oracle-l