Symptom
- Currently, it is possible to configure the retention period of Audit Log on SAP DI 3.3, however the cron schedule is always fixed
- It can run into issues if the system has other workflows running at the same time consuming HANA connections
- Audit log cleanup does not recover after HANA pod stability issues, leading to prolonged memory and disk space consumption until the system goes down
Read more...
Environment
SAP Data Intelligence (DI) 3.3 - On Premise Edition
Product
SAP Data Intelligence 3.0
Keywords
audit log cleanup, HANA POD stability, memory consumption, disk space consumption, connection pool timeout, SAP Data Intelligence, cleanup failure, cron schedule adjustment, error ECONNRESET, retention job , KBA , CA-DI-CP-EHA , HANA , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview