Deployment failing due to database error at uniqueness constraint diagnostics: Table does not exist

0
I am trying to deploy an application but it is not going past uniqueness constraint violation diagnostics. The error thrown is: ERROR - M2EE: An error occurred while initializing the Runtime: java.sql.SQLSyntaxErrorException: (conn:4236730) Table 'itsc.ran_integration$emailsettings_accountgroup_ran' doesn't exist Query is : SELECT COUNT(*) FROM (SELECT `mainmodule$accountgroupid` FROM `ran_integration$emailsettings_accountgroup_ran` GROUP BY `mainmodule$accountgroupid` HAVING COUNT(`mainmodule$accountgroupid`) > 1) `inner` ERROR - M2EE: com.mendix.m2ee.api.AdminException: An error occurred while initializing the Runtime: java.sql.SQLSyntaxErrorException: (conn:4236730) Table 'itsc.ran_integration$emailsettings_accountgroup_ran' doesn't exist Query is : SELECT COUNT(*) FROM (SELECT `mainmodule$accountgroupid` FROM `ran_integration$emailsettings_accountgroup_ran` GROUP BY `mainmodule$accountgroupid` HAVING COUNT(`mainmodule$accountgroupid`) > 1) `inner` at com.mendix.basis.impl.MxRuntimeImpl.start(MxRuntimeImpl.java:325) This association table is supposed to be added into this deployment so this error doesn’t make any sense. There was failed deployment before this too, I have a feeling that the database changes of that deployment were not properly rolled back and now mendix thinks that this table exists.
asked
1 answers
1

If you have the feeling that it should not be because you just added this association, can you try to deploy the old version again? It should roll back the database changes. After that you can deploy the new one.

If this stil fails, Mendix has a migration toolkit called module to resolve such violations. But you can only get it when asking mendix support.

answered