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.
If you purge an audit log in application administrator and then decide to cancel it then the purge activity keeps restarting itself (Stopping JBOSS and rebooting server makes no difference). Contact Support for information on how to stop this activity permanently.
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.
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 .
Only complex/participating packages are affected by this problem, even when just a single XAP application is defined in the audit . Changing the affected participating package to a simple package allows the autoresolve request to complete successfully.
Show History for a file does not show only the history for that specific file. Clicking Show History on a specific file in an area or a project returns the history for every file in the entire area/project with that same file name. The home path information is not available in the audit trail and therefore, the searches are only by area name/project name.
