On Mon, Jan 11, 2010 at 11:38 AM, Dennis Williams < oracledba.williams@xxxxxxxxx> wrote: > > The auditor's question was essentially that "you are making changes to > table A and verifying those changes, but how do you know the application > didn't also change table B". I wasn't involved in the original question that > led to the finding. > > If I understand this correctly, the changes referred to are made as part of the process to apply development changes to production. Is that correct? If so, DML triggers could be temporarily placed on the apps tables to capture what was done, store the changes in another set of tables, and drop/disable the triggers. There are many methods to accomplish that, but this one makes reporting a bit easier. Assuming my assumption was correct that is. :) Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com