IBM Support

CM Advanced Parameters that help with Content Store locking issues

Question & Answer


Question

There are several Advanced parameters that can be added ad advised by IBM Cognos support to prevent/mitigate Content Store locking issues.  What do they do exactly?
You might see the following type of error in the logs:
"CM-SYS-5133 While processing your request, Content Manager has waited for 601.043 seconds for access to objects that are currently locked"

Cause

A deeper dive into what is causing the locks might be necessary with a thorough analysis of the logs, and, the activities that are potentially causing it.  Find out how the users are being impacted (running schedules, logging on, etc).

Answer

CM.CAMSEARCHDEFERREDLOCKING = true
-This setting is specific to addressing issues with users logging in to Cognos Connection when a directory search is being performed thus holding the CM.
CM.MAXPATHLOCK
-Specifies number of locks that are maintained during the fetching objects by blocks, increasing the value results in shorter locking times.
CM.DBDEADLOCKRETRYMAX
-The default value is 2 and it means Cognos will retry 2 times in a deadlock.
CM.DBDEADLOCKRETRYTIME
-The default value is 5000, (5 sec) meaning that Cognos retries connecting in a deadlock two times (In relation to the CM.DBDEADLOCKRETRYMAX setting), 5 seconds apart.
CM.ENABLE_SEPARATETRANSACTIONS_ONUPDATE_RETENTIONRULE = true
Set when Cognos is under heavy load and running simultaneous executions of the same Job agent or report on distributed installs of Cognos.
CM.IPF_AUDIT_SECURITY_OBJECTS
-Provides the ability to control the logging of security objects to prevent multiple CAM requests by CM.
-Default Behavior is CM.IPF_AUDIT_SECURITY_OBJECTS = 'namesOnlyPath' - It returns security object names by issuing multiple requests to CAM.
-Three possible values for CM.IPF_AUDIT_SECURITY_OBJECTS:
1. namesOnlyPath (default): This resolves all security steps default name and can be extensive.
2. defaultName: This logs the default name of the single step, cannot look for any ancestors.
3. camid (recommended): This logs the CAMID without requiring
information from CAM/LDAP.
Syntax:
Name: CM.IPF_AUDIT_SECURITY_OBJECTS Value: namesOnlyPath
Name: CM.IPF_AUDIT_SECURITY_OBJECTS Value: defaultName
Name: CM.IPF_AUDIT_SECURITY_OBJECTS Value: camid
Examples
1. namesOnlyPath (default): /Directory/Series7/Users/Bob.Dumelie
2. defaultName: bobumelie
3. camid (recommended): CAMID("Series7:r:authid=1234567890")
Our recommendation: is to use advanced setting CM.IPF_AUDIT_SECURITY_OBJECTS = camid

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTSF6","label":"IBM Cognos Analytics"},"ARM Category":[{"code":"a8m50000000Cl3zAAC","label":"Administration"}],"ARM Case Number":"TS004600768","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
04 July 2023

UID

ibm16382264