When you purge the audit log on some large projects running on Oracle it can take a really long time. The gui doesn't give any indication that the purge is still running especially if you close the browser window.
At midnight the SBM system runs SQL statements in the database against the TS_AUDITENTRY table to check how many records are in the " Audit History log ". If there are a large number of records in the Audit History log, this calculation can run for a long time and can affects the performance of the SBM database for the Application Repository. If the Repository database is stored on the same server as the AE database, the user front-end may also be affected.
ENH335067: As a workaround to DEF320998 (High CPU on database at midnight and when selecting to purge the " Audit History log ") which cannot be addressed in a patch, this enhancement will give the ability to turn on/off the automatic Audit Monitoring purge . After this hotfix is installed, the mashupmgr.cfg will have option called "AR_MONITORING_ENABLE" which will be set to "false" to disable the automtic purge.
Old data can be removed from a project by purging the old information. This is done under Project | Audit Log | Purge Log . The term "log" is misleading.
By default, the audit monitoring feature logs Application Repository events such as when items were added to or purged from the repository, as well as deployment and promotion activities. This log is displayed as part of the Purge Audit History tab. Audit monitoring can cause high CPU usage when SQL statements are run against the repository or during audit history purges .
