3802499 - Object Store table total storage does not decrease after VACUUM - SAP Datasphere

• An Object Store table in SAP Datasphere shows total storage significantly larger than active records storage, even after VACUUM has been executed one or more times.
• Running VACUUM repeatedly or waiting beyond the standard retention window does not bring total storage down to the active data size.
• The VACUUM task completes without errors, yet the storage difference persists.

SAP Datasphere

VACUUM removes only record versions that satisfy two conditions: they are older than the configured retention period, and they are no longer referenced by any consuming Transformation Flow.

If a Transformation Flow uses the Object Store table as a delta source and has not yet processed older record versions, those versions are retained regardless of how many times VACUUM runs or how long you wait. The delta capture watermark of the consuming flow marks the boundary; versions within that boundary cannot be deleted until the flow advances its watermark past them.

Check whether a Transformation Flow consumes the table. If one does, the versions it has not yet read are retained by design and VACUUM cannot remove them; they are reclaimed once the flow processes them.

Deleting Local Table (File) Records | SAP Help Portal

Object Store, VACUUM, total storage, active storage, storage not released, storage not decreasing, storage not reclaimed, capacity units, CU consumption, Transformation Flow, delta capture, watermark, inactive storage , KBA , DS-DI-TAB , Table Persistency , Problem