Re: Database comparisons
Date: Mon, 11 Jan 2010 14:01:33 -0600
In my situation, that wouldn't be an issue. There won't be any DDL executed during the application tests. But thanks for pointing that out.
On Mon, Jan 11, 2010 at 1:58 PM, William Muriithi < william.muriithi_at_epicadvertising.com> wrote:
> Not sure this would satisfy the auditors. Flashback version query does not
> capture changes across DDL.
> At least this is what I inferred from the documentation when I looked at
> flashback version
> *From*: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org>
> *To*: oracledba.williams_at_gmail.com <oracledba.williams_at_gmail.com>
> *Cc*: Oracle-L Freelists <oracle-l_at_freelists.org>
> *Sent*: Mon Jan 11 11:52:07 2010
> *Subject*: Re: Database comparisons
> You can use Flashback Version Query to look at all changes to data in a
> given table, if that helps and if the UNDO is available.
> Robert G. Freeman
> Oracle ACE
> Ask me about on-site Oracle Training! RMAN, DBA, Tuning, you name it!
> Oracle Database 11g RMAN Backup and Recovery (Oracle Press) - ON ITS WAY
> OCP: Oracle Database 11g Administrator Certified Professional Study Guide
> Oracle Database 11g New Features (Oracle Press)
> Oracle Database 10g New Features (Oracle Press)
> Other various titles
> Blog: http://robertgfreeman.blogspot.com
> Check out my new blog series on installing Oracle Database 11gR2 on Windows
> using VMWare!
> *From:* Dennis Williams <oracledba.williams_at_gmail.com>
> *To:* oracle-l_at_freelists.org
> *Sent:* Mon, January 11, 2010 10:24:35 AM
> *Subject:* Database comparisons
> 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
> 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