Duplicate MCS profile detected

Document ID : KB000094159
Last Modified Date : 24/10/2018
Show Technical Document Details
Introduction:
During an upgrade from 8.4 to 8.51 or above, it is common to receive and error similar to the following:

Duplicate MCS database entries have been detected.
Please contact CA support to continue with your upgrade. 

MCS Duplicate entries error pop-up message

 
Background:
The above error will cause the UIM Upgrade from 8.4 to 8.51 or above to prevent a user from proceeding.



Environment:
UIM 8.5.1
MSSQL database
MYSQL database
Oracle database
Instructions:
To resolve the issue, a workaround can be issued by using a script within the file attached to this KB:
  •  clean_pre_851_mcs_db-master.zip

Within the file, there are three scripts:
  • mssql_clean_mcs_db.sql
  • mysql_clean_mcs_db.sql
  • oracle_clean_mcs_db.sql

NOTE: Make sure you have a full backup of your UIM database before proceeding. 

MS SQL or MySQL Steps:
The script is set up as a transaction that does not actually make any changes on the first run, as noted by the "Rollback" portion of each script. 

Perform the following steps: 
  1. Run the file pertaining to your DB type on the DB directly. (either MSSQL or MYSQL)
  2. After it is executed, if everything goes well, the result of the script should say "It is safe to upgrade to UIM 8.51". 
  3. If that is the case, edit the statement in the script (at the very end of the MSSQL script, or near the end of the MYSQL script) that says "rollback" to "commit" and run the entire script again. This will then make the required updates and enable you to proceed through the upgrade installer successfully. 

Your DBA will need to run the appropriate database script for either MYSQL or MSSQL as noted above to resolve this issue. 

You then can move forward with the installation upgrade. 


In the event that you do not receive the "It is safe to upgrade to UIM 8.51" message after running the script, or if you are running an Oracle database, please open a support case for assistance.

Oracle Steps:
1. Finding duplicate entries from the SSRV2ConfigValue table:
select profile, field, count(*) from SSRV2ConfigValue   group by profile, field having count(*) > 1;
2. Check for the profile in the SSRV2profile table:
select * from SSRV2profile where profileid = profile_value;
3. If there are any duplicates delete then from SSRV2ConfigValue table
 delete from SSRV2ConfigValue where profile = profile_value and field is null (If field is null);
 delete from SSRV2ConfigValue where profile = profile_value and field = field_value (if field value is not null);
4. Run the oracle_clean_mcs_db.sql file.   For example:
sqlplus CA_UIM/password @oracle_clean_mcs_db.sql

Sample output:
[oracle@<hostname>~]$ sqlplus CA_UIM/password @oracle_clean_mcs_db.sql
SQL*Plus: Release 11.2.0.1.0 Production on Wed Oct 24 09:57:33 2018
Copyright (c) 1982, 2009, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
PL/SQL procedure successfully completed.

 
 
 

 
Additional Information:
Please reference the Release Notes for UIM 8.51 prior to upgrading

MCS Users Can Run an SQL Script to Determine If Their Database is Ready to Upgrade to 8.5.1

Upgrading & Release Notes


 
File Attachments:
clean_pre_851_mcs_db-master.zip