Why not just turn sqltrace on for the session that's doing the changes. And then verify the tracefile for unexpected SQL-statements. On Mon, Jan 11, 2010 at 6:24 PM, 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 > -- Toon Koppelaars RuleGen BV Toon.Koppelaars@xxxxxxxxxxx www.RuleGen.com TheHelsinkiDeclaration.blogspot.com (co)Author: "Applied Mathematics for Database Professionals" www.RuleGen.com/pls/apex/f?p=14265:13