Resolve Duplicate Key Violation SQLException in Workflow Process - Identity Manager
search cancel

Resolve Duplicate Key Violation SQLException in Workflow Process - Identity Manager

book

Article ID: 127875

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Suite

Issue/Introduction

This article provides instructions for resolving "SQLException occurred: A duplicate key violation has occurred" errors when creating or saving workflow processes in Identity Manager. This error typically occurs when Workpoint database IDs are out of synchronization.

Environment

Identity Manager 14.5

Cause

During the initial product installation, the Workpoint database is initialized with default identifiers. Importing the base workflow archive can lead to ID collisions if the existing IDs are not synchronized to the current maximum value in the database.

Resolution

To resolve this synchronization issue, use the IdCheck tool to resync the Workpoint Database identifier.

  1. Prerequisite: Perform a full backup of the Workpoint database before running any synchronization tools.
  2. Locate Tool: Navigate to the IdCheck.bat file located in the Identity Manager tools directory.
  3. Configure Classpath: Ensure the Database Vendor JAR files are present in the classpath and that the JAR names in the IdCheck.bat file are accurate for your environment.
  4. Execute Tool: Run IdCheck.bat from the command line to resync the database identifiers.
  5. Restart Services: Once the tool completes successfully, restart the application server. This action clears the Workpoint cache and forces the application to reinitialize with the updated, synchronized IDs.

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.