Error "DEBUG - The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.rootcause'" appears in the install_mdb.log while migrating from 11.2 to R12.5.

ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Error "DEBUG - The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.rootcause'" appears in the install_mdb.log while migrating from 11.2 to R12.5.

book

Article ID: 51083

calendar_today

Updated On:

Products

CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service KNOWLEDGE TOOLS CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

Description:

This error may occur if duplicate rows exist in the 'rootcause' table and will cause the migration to fail.

The "SQLCheckr12UniqueIndexes.sql" and "OracleCheckr12UniqueIndexes.sql" scripts provided identify duplicate rows for some tables but not for the 'rootcause' table.

Solution:

To resolve the issue, manually run the following SQL statement to identify any duplicate rows:

   SELECT sym, COUNT(*) AS 'NumberOfDups' FROM rootcause GROUP BY sym HAVING COUNT(*) > 1

If any duplicates are identified, take a backup of the 'rootcause' table, update the sym values and set the records to inactive via the Service Desk GUI.

Now re-run the migration and it should complete successfully.

Environment

Release:
Component: ARGIS

Feedback

thumb_up Yes

thumb_down No