Upgrade v9.2 to v9.3 fails with Database error 2601: Cannot insert duplicate key row in object 'dbo.DialogColumn' with unique index 'QBM_XA2DialogColumn'

Question

Hi, 
 The database upgrade procedure fails with the error Database error 2601: Cannot insert duplicate key row in object 'dbo.DialogColumn' with unique index 'QBM_XA2DialogColumn' . The duplicate key value is (UID_CutOffTask, QBM-T-DialogDatabase). These are not, as seen, custom columns. 
 Is this upgrade path allowed (v9.2 to v9.3) or is it mandatory to upgrade to 9.2.1 previously? Thanks!

CVU · Accepted Answer

Hi. 
 Thanks so much for your help. Apologies for the delay, I was running more tests. 
 Eventually, here are the steps I've followed, they might be useful for other users: 
 
 Restore backup from production 
 Configwizard->Enable a restored database. Compilation ends with no errors. 
 Ran Designer, updates applied. 
 Checked db consistency according to the documentation. Only two errors that could not be automatically corrected, but they were related to PWO pointing to apps that no longer exist. So I skipped that. 
 Installed v93, ran config wizard -> update database. Cleared DialogDBQueue. 
 Upgrade ended with no errors this time. 
 
 As Markus Weiss-Ehlers pointed out at one point errors might have ocurred on a previous attempt, but I cannot recall having done so. We know how updates work: Should the process fails, recover from backup and retry. 
 Only thing I can think of: The DB I was trying our first testing was: 
 
 An already dev database that's been thoroughly used for our testings. 
 Running on SQLServer dev edition on Linux. In this case, I have to say v93 won't install at all and will fail later on during the upgrade process. 
 
 Thanks again!

Upgrade v9.2 to v9.3 fails with Database error 2601: Cannot insert duplicate key row in object 'dbo.DialogColumn' with unique index 'QBM_XA2DialogColumn'

Top Replies