Symptom
In SAP Datasphere, Space Audit Log is already enabled by selecting 'Enable Audit Log for Read Operations' or/and 'Enable Audit Log for Change Operations' options in Space Management > <Your Space> > Edit Space > Auditing. The Audit Log (DPP_AUDIT_LOG) however does not record any new entry after reading or changing the data of an object in the space, for example, updating a table data entry.
Environment
SAP Datasphere
Reproducing the Issue
- In Datasphere Space Management > <Your Space> > Edit Space > Auditing, select 'Enable Audit Log for Read Operations' or/and 'Enable Audit Log for Change Operations' options.
- Perform a data change (insert/update/delete) on a local table in the space.
- Check the view that uses DPP_AUDIT_LOG as source and observe no corresponding entry for the performed actions is recorded.
Cause
Audit logging options were enabled in the space, but the space was not deployed afterward, the Deployment status of the Space is 'Changes to deploy'. The auditing policies were therefore not active, and read/change actions were not recorded in DPP_AUDIT_LOG.
Resolution
After enabling space audit log, ensure to deploy the space, so that following audit policies becomes active.
Audit Policy Name Applies To Actions Logged
DWC_DPP_<spaceID>_READ main schema of space <spaceID> successful SELECT
DWC_DPP_<spaceID>_CHANGE main schema of space <spaceID> successful INSERT, UPDATE, DELETE
This implies that policies DWC_DPP_<spaceID>_READ and DWC_DPP_<spaceID>_CHANGE log successful SELECT queries and DML changes (INSERT, UPDATE, DELETE) respectively in DPP_AUDIT_LOG.
Keywords
audit log, dpp_audit_log, not recording, datasphere audit, space deployment, changes to deploy, audit policy, dwc_dpp_change, insert update delete, activity log, local table, data change tracking, enable audit logs, space management, audit retention , KBA , DS-SM , Space Management , Problem
SAP Knowledge Base Article - Public