Oracle database partitioning for Identity Manager transactional tables

Products

• CA Identity Suite

Issue/Introduction

Identity Manager server outages, connection drops, or performance degradation occur when transactional tables (such as EVENT12_5, RUNTIMESTATUSDETAIL12, or ARCHIVE_OBJECT12_5) grow excessively large and DBA is indicating that needs partition the ARCHIVE_OBJECT12_5 table in Oracle because it is too big, almost 7Tb.

Symptoms:

• Daily system crashes requiring service restarts.
• "Too many hanging connection threads" in application server logs.
• Database monitoring shows high usage (e.g., 80%) linked to duplicate requests or table locks.
• Slow performance during bulk tasks or identity syncs.
  
  
  Question: Can Broadcom Support consider the environment Supported yet if DBA does the partition in this table or Broadcom Support will require rollback the partition in case have any issue?

Environment

• CA Identity Suite 14.x, 15.x
• Oracle Database

Cause

Task Persistence (TP) tables exceeding recommended row counts (typically >100,000 rows) cause database contention and connection pool exhaustion.

Resolution

Broadcom does not officially certify or provide specific Oracle partitioning templates, as partitioning is managed at the database layer. Use the following guidance for implementation:

1. Support Stance: Any partitioning must be transparent to the Identity Manager application. Broadcom Support continues to support the environment provided the partitioning does not interfere with standard application operations.
2. Testing Requirements: Thoroughly validate the configuration in a QA environment with functional and load testing before applying changes to Production.
   
   
3. Cleanup Configuration: Review the "Cleanup Submitted Tasks" configuration to ensure row counts stay within manageable limits, regardless of partitioning.
   
   

 

Additional Information

• For database pool tuning, see KB 245333.
• To stay updated on fix statuses, subscribe to this article.
  
  
• Another alternative is to open an enhancement request. This enhancement process is outside the Support case in which Product Management assesses the feasibility of implementing or not.