Later versions of the MDB will add a Foreign Key Constraint:
This will fail if there are broken references in the table.
This is a known issue when ITCM/DSM are using the same MDB as Service Desk/CMDB.
Problem #: 1147 - Upgrade from R12.2 SP4 to R12 failed with 1603 error.
MDB log files shows following error:
The error on the MDB log file is "The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "$ca_di_r000002ac00000000".
The conflict occurred in database "mdb", table "dbo.ca_asset_source", column "asset_source_uuid".
Root Cause: A row or rows in the "ca_discovered_hardware" table contains a bad value for "asset_source_uuid" and hence the SQL to add the foreign key constraint fails.
Please execute following queries:
- Select asset_source_uuid from ca_discovered_hardware where asset_source_uuid NOT IN(select asset_source_uuid from ca_asset_source)
- Select asset_source_uuid from ca_discovered_software where asset_source_uuid NOT IN(select asset_source_uuid from ca_asset_source)
If either of the queries above returns results; please open an issue with ITCM/DSM Support to request the patch for problem #1147.