IDUG NA 2025

Prior to Db2 12.1, with Db2 audit enabled for the database using the db2audit facility, an unsustainably large amount of audit data is generated which has an impact on the general database performance, I/O, and space. This is especially true for the “execute” category of Db2 auditing. Almost all the data is generated by the SAP application and the SAP database connect user. Unfortunately, the db2audit facility provides very little in terms of application context that comes from the SAP system such as SAP logon user, reports, and so on.
On the other hand, there are SAP–level auditing functions and auditing within the SAP system which can provide application–related details.
However, auditing on SAP application level has its limits: You cannot audit statements that execute directly against the database and that come from outside the local ABAP stack.With Db2 12.1, the Db2 audit facility has been enhanced to overcome the above–mentioned limitation. Generally, the database data should only be accessed in a trusted way from the SAP application through the SAP database connect user, and all other connections to the database should be audited.
As of Db2 12.1, you can exclude auditing for connections originating from the local SAP application by the SAP connect user. This reduces the amount of audit data generated by the Db2 audit facility to something more manageable.