SAP Knowledge Base Article - Public

3416979 - Datasphere Audit Log Data occupies more storage considering the number of entries in system configuration

Symptom

It is found that Datasphere Audit Log Data occupies more storage compared the number of entries in system configuration.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Environment

SAP Datasphere

Reproducing the Issue

  1. Check the "Number of Entries" in System/Configuration, Audit part. For example, there are total 22,053 number of entries.
  2. Check System Monitor --> Storage Distribution --> Audit Log Data. For the above example, the disk storage for audit log is 2.11GB.

Cause

The audit log overview in configuration tab shows only the audit log policies from the spaces. But internally there are some more e.g. for Analysis Users, Support Users etc.

Resolution

Audit logs can consume a large quantity of GB of disk in your database, especially when combined with long retention periods (which are defined at the space level). Please consider decreasing the retention period (minimum 7 days) in the space details.

See Also

The retention period of 7 days is the minimum value and no more configurations in regards of the granularity are possible.

Monitor Database Operations with Audit Logs: https://help.sap.com/docs/SAP_DATASPHERE/9f804b8efa8043539289f42f372c4862/110404abd2d044008102c871b39fdf65.html?locale=en-US

Keywords

Datasphere, Audit Logs, Audit Log. , KBA , DS-SM , Space Management , Problem

Product

SAP Datasphere all versions