Flashback Data Archive: History Tablespace Quota and Retention Enforcement

Flashback Data Archive Storage Constraints

Oracle Flashback Data Archive (FDA) utilizes a dedicated history tablespace to store row versions for long-term tracking. While the RETENTION parameter defines the logical window for historical queries, the physical availability of space is governed by the archive tablespace quota.

Storage Exhaustion vs. Retention Purge

There is a design uncertainty regarding the priority of operations when the history tablespace reaches its quota limit before the defined retention period has elapsed. It is unclear whether the database prioritizes the success of new DML on the source table by aggressively purging the oldest historical versions, or if DML on the tracked table fails once the archive storage is exhausted.

Furthermore, the asynchronous nature of the purge process means that AS OF TIMESTAMP queries may return inconsistent results when operating exactly at the retention boundary.

• Does the system trigger an automatic purge of the oldest records to accommodate new DML when the history quota is reached?
• If the quota is strictly enforced, does the source table's DML fail with a storage error, or is the archiving process silently suspended?