How do I properly use Oracle Flashback to audit table changes with user information?

524 views Asked by At

My organization has chosen to use Oracle Flashback to replace manually created audit tables. However, the DBA set the TUNED_AUTORETENTION values and UNDO_RETENTION to only 14400 seconds. Unfortunately, we have to keep the audit values for 7 years on this data. Is there a way to query "expired" version data so specific changes can be audited by timespan, or does UNDO_RETENTION and the individual TUNED_AUTORETENTION values need to be set to 220800000? I looked into flashback_transaction_query but it only shows the transaction general data, not which column values were changed.

The database in question currently has its tablespace files set to automatically allocate more physical layer space on the logical drive.

1

There are 1 answers

6
pmdba On

For this purpose you should be using Flashback Data Archive, not basic Flashback. The parameters you mentioned only apply to basic flashback.

A Flashback Data Archive provides the ability to track and store transactional changes to a table over its lifetime. A Flashback Data Archive is useful for compliance with record stage policies and audit reports.

See here: https://docs.oracle.com/en/database/oracle/oracle-database/19/adfns/flashback.html#GUID-06AA782A-3F79-4235-86D5-2D136485F093