Ensuring the health of CA Identity Manager databases in large environments is essential to avoid performance issues experienced from rapid data growth\ sizing issues. The product documentation is a great source of information, however, this knowledge document aims to pull together a number of resources to offer guidance on maintaining the task persistence data and managing in-progress tasks.
CA Identity Manager 12.6.x
CA Identity Manager 14.x
CA Identity Suite 14.x
Task Persistence Database: Use, Performance, and Troubleshooting:
§ Can interfere with the performance
§ Can cause DB lock conditions
§ Avoid writing custom code or PX policies that access TP database
Database Space Usage
You can minimize the amount of data in TP tables using the following methodologies:
§ Use for ongoing cleanup
§ Not effective for massive cleanup
§ Run daily or weekly keeping only the most recent few days of data
§ Removes only Completed tasks—no risk of removing in-progress tasks
§ Stored procedure removes only completed tasks, not in-progress tasks.
§ Stored proc is installed into Object Store
§ Avoid running during busy hours
§ Can take a long time—run small batches
§ See the Readme and SQL Script for running the stored procedure in
..\CA\Identity Manager\IAM Suite\Identity Manager\tools\samples\TaskPersistence\SQLServer
§ See KB 43199, Cleanup Submitted Tasks Not Working; Database stored procedure for cleaning up task persistence is available.
Stuck In-progress Tasks
§ The Post-Events feature allows the user to resubmit events that get stuck in-progress. This feature is accessible via the Post Events button on the Identity Manager Environment Properties page.
§ See Post Events to the Identity Manager Event Service in Post Events to the Identity Manager Event Service
§ It’s OK to just leave them as is.
Overview of Diagnosing Stuck In-Progress Tasks
for more specific information on In-Progress Tasks please see KB 233003 IN-PROGRESS task issues - A Client’s Guide to Understanding and Resolving
o Usually due to a processing bottleneck
§ Bulk feed processing?
§ Explore Correlate running?
§ Check VST, look for patterns of stuck tasks
§ What is the last event (password sync to prov, for ex.)
§ Check for Task Persistence DB slowness
§ User directory or Object store DB connection issues
§ Check IDM application server logs for problems
§ Provisioning server issues
· Check Prov logs (etatrans, etanotify, JCS)
· Inaccessible endpoints
· Connector server not running
· CA directory errors
· Outbound sync (to IDM) failures to ETACallback servlet
· Notifications not processing, or not keeping up with load
§ Check Java Messaging Service (JMS) processing for problems