Symantec Identity Governance (v14.5) Database Tablespace Sizing, Rapid Growth, and UNDO Tablespace Outage

Products

• CA Identity Suite

Issue/Introduction

A customer running Symantec Identity Suite - Identity Governance v14.5 on Oracle Database 19c experienced substantial and unexpected database tablespace growth (from approximately 8 GB to 275 GB in nine months) and a service interruption caused by the exhaustion of the Oracle UNDO tablespace. The customer explicitly requested official Broadcom guidance, a reference model, or a capacity planning calculator to determine the optimal tablespace sizing for their Governance schemas, as their production workload requires retaining certification data for 18 months and exceeds the maximum values cited in general installation guides.

Environment

 Identity Governance v14.5 Vapp
Oracle Database 19c as external DB

Cause

Exact database sizing for Identity Governance is highly dependent on customer-specific factors such as the volume of monthly imports (users, roles, resources), the number and complexity of certification campaigns, and the local retention policies configured. This requirement often falls under professional consulting/capacity planning services rather than standard support. The customer's environment confirmed that their production workload's UNDO requirements significantly surpassed the 20 GB maximum recommended in the general installation guide (growing to an observed peak of 30 GB).

Resolution

As vendor-provided optimal sizing depends on unique data characteristics and is not a fixed product value, the following actions and guidance were provided, emphasizing that the Oracle-native database tasks are the responsibility of the customer's DBA Team:

1. Oracle UNDO Tablespace Management:
Immediate Action (DBA): The DBA should set the MAXSIZE parameter for the UNDO tablespace (e.g., UNDO_13) to a value that comfortably exceeds the observed 30 GB peak (e.g., 40 GB or higher) to prevent service interruptions, as the workload clearly necessitates a size larger than the 20 GB general recommendation.

2. Long-Term Sizing (DBA): The DBA should establish the definitive optimal size by continuously monitoring the Oracle-native V$UNDOSTAT view during peak operations (like full imports and certification assignments) to accurately capture the maximum space required for the undo retention guarantee.

3. Governance Tablespace (IGA) Management:
-> Purge Optimization (IGA Administrator): Validate and ensure that the Identity Governance Purge Data Utility is enabled and running regularly with specific retention criteria. High-volume DML on tables like USERACTIONS, UAPREVIOUSOWNERS, and TRACEMESSAGES indicates they are primary contributors to the growth in the IGA_GOVERNANCE_EUR schema, and must be purged according to the customer's business and compliance retention policies (e.g., the 18-month certification data requirement).
-> Capacity Planning (Customer/DBA): Accurate future capacity projections require the customer to provide a consistent, multi-month growth trend (schema sizes) and the list of the Top 10 largest permanent data tables within their IGA Databases for Identity Governance including Workpoint database schemas to pinpoint the core sources of permanent storage consumption.