Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Audit Log Purge History does not Clear
Audit Log Purge History does not Clear
CMS-XML High CPU on database for Application Repository at midnight and also when selecting to purge the "Audit History log"
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.
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
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.
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.
CMS-XML Disable Audit Monitoring in Application Repository
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 .
CMS-XML Fails to get the snapshot list if last promote activity was deleted and purged
2. In the activity view, delete the promote activity. 3. In the Audit Log view, purge all history items 4. Refresh the snapshot view
CMS-XML Audit autoresolve using wrong component history in complex/participating packages
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.
CMS-XML KM-Dim9: Does Dimensions track user login history? Yes with DM_USER_AUDIT_LOGFILE set in dm.cfg
KM-Dim9: Does Dimensions track user login history ? Yes with DM_USER_AUDIT_LOGFILE set in dm.cfg
CMS-XML Audit Trail does not show history for a specific file.
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.
CMS-XML Audit Trail -The ability to do show history for files for a particular directory and its sub-folders.
How to list all the files for a specific directory and its sub-directories but not the entire area in the DS audit Trail.
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