Resolving Primary Key Constraint Violations in FWSERVICE_REQUEST Table - CA Identity Manager

Products

• CA Identity Manager
• CA Identity Suite
• SITEMINDER

Issue/Introduction

This article addresses the "SmApiWrappedException: Violation of PRIMARY KEY constraint" error encountered in CA Identity Manager. This error typically occurs when the application attempts to perform an operation on the FWSERVICE_REQUEST table within the object store database using a record identifier that already exists, which violates the table's unique primary key constraints.

Environment

Identity Manager 14.5

Siteminder 12.8

Cause

The error is triggered when the Identity Manager system attempts to perform an 'insert' or 'update' operation on the FWSERVICE_REQUEST table using a key value that is already present in the database. Because the object store is configured with a strict primary key constraint to ensure data integrity, the database prevents the insertion of duplicate records, resulting in the SmApiWrappedException failure.

Resolution

To resolve this constraint violation, you must remove the conflicting duplicate record from the object store database:

1. Access your object store database using your organization's authorized SQL client tool.
2. Locate the specific record in the FWSERVICE_REQUEST table that matches the duplicate key value identified in your error message (e.g., value 501).
3. Review the record to ensure it is safe to remove.
4. Delete the duplicate entry to resolve the constraint conflict.
5. Retry the operation that previously failed in the Identity Manager console.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.