Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Audit Log Purge History does not Clear
SBM 2009 R3
CMS-XML High CPU on database for Application Repository at midnight and also when selecting to purge the "Audit History log"
SBM 11.4
CMS-XML Purging the audit log history impossible to cancel permanently on SQL Server and can cause deadlocks with Oracle - java.exe CPU 100% even after restarting
SBM 10.1.1.2
CMS-XML SBM: Repository Purge History always adds 2000 to the year
When trying to purge data (Repository > Advanced > Audit History > Purge History ), you can give a date. However, no matter what the user enters as the year, the system always adds 2000 to the year.
CMS-XML SBM 11.4.2 Hotfix 3: Ability to turn on/off the automatic Audit Monitoring purge (workaround for DEF320998)
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.
PDF Serena Dimensions RM Integration Guide for SBM
 The act_as_user attribute is optional. If specified with a value of "true", actions targeting the SBM server will be performed under a named user (as opposed to the "SyncAdmin" user specified in the user attribute). This is recommended so that state changes and change history reflect a real user in the system for better auditing ability.
PDF Dimensions RM Integration Guide for SBM
 The act_as_user attribute is optional. If specified with a value of "true", actions targeting the SBM server will be performed under a named user (as opposed to the "SyncAdmin" user specified in the user attribute). This is recommended so that state changes and change history reflect a real user in the system for better auditing ability.
PDF SBM Application Repository Guide
Audit History [page 81] • Server Statistics [page 82] • Application Repository Log [page 83]
PDF SBM Application Repository Guide
The Purge History dialog box is used to remove the history of events from the Audit Log or Event Manager Log. This operation also deletes the corresponding process app versions. You can delete all events, or events prior to a specific date.
PDF SBM Application Administrator Guide
Audit Log A historical record of deployments, promotions, and application changes shown in Application Administrator.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs