Building app around Flashback Versions Query

Hi everyone,

Currently we have an app that maintains an audit trail manually via triggers, almost identical to the way Flashback Versions Query provides results with the pseudocolumns versions_operation, versions_starttime, versions_endtime, etc.

What I'd like to do is remove the admin overhead of the manual history tracking and enable an undo retention period of 7 years. I've checked the Oracle docs and a value of (2 to the power of 32) - 1 in seconds is the max, which is more than enough. If I create a bigfile undo tablespace on ASM and turn on retention guarantee with autoextend on and maxsize unlimited, and assuming we have enough disk space in the ASM disk group, do you think this would work? We would also enable flashback database on our logical standby to the same level so that we can flashback across major DDL changes, open the database is read-only mode, and then recover and resume redo apply.

The company I work for wants to know if anyone out there is building apps around Flashback Query and Flashback Database. I know many apps exist that were built off LogMiner, but they're very cautious and need some assurance. Does anyone know of companies on 10g r1 or r2 using flashback and building apps around this functionality? It's a very powerful technology and solves the problem of adding the dimension of time to standard relational databases.

I realize the existing history will be lost, but the application is only one month old.

Thanks in advance for all replies. Received on Thu Dec 01 2005 - 09:42:10 CST