Detected unique constraint violation (or) Database Uniqueness Validation is supported.

0
Hi @Team I Have upgraded my application from 8.13.2 to 9.24.3 ,after while runing the application locally with prod db connected externally or deploying to the environment unable to run the application getting and below error. As its an production bit affraid about the data, Can you please help me here to overcome this below error or did any one faced the same below error.   “ An error occurred while initializing the Runtime: Detected unique constraint violation [association: DRL_KOL.KOLAttachment_ActivityACT, column: DRL_KOL.ActivityID] Since Mendix 9, only Database Uniqueness Validation is supported. If your project still uses Runtime Uniqueness Validation, please contact support. -------- com.mendix.m2ee.api.AdminException: An error occurred while initializing the Runtime: Detected unique constraint violation [association: DRL_KOL.KOLAttachment_ActivityACT, column: DRL_KOL.ActivityID] Since Mendix 9, only Database Uniqueness Validation is supported. If your project still uses Runtime Uniqueness Validation, please contact support.     at com.mendix.basis.impl.MxRuntimeImplBase.start(MxRuntimeImplBase.java:267) Caused by: com.mendix.connectionbus.ConnectionBusRuntimeException: Detected unique constraint violation [association: DRL_KOL.KOLAttachment_ActivityACT, column: DRL_KOL.ActivityID] Since Mendix 9, only Database Uniqueness Validation is supported. If your project still uses Runtime Uniqueness Validation, please contact support.     at com.mendix.connectionbus.modelsynchronization.ModelSynchronizationUpdater.validateConstraints(ModelSynchronizationUpdater.scala:141)     at com.mendix.connectionbus.modelsynchronization.ModelSynchronizationUpdater.analyzeAndRender(ModelSynchronizationUpdater.scala:86)     at com.mendix.connectionbus.modelsynchronization.SynchronizationManager.analyzeMappingModel(SynchronizationManager.scala:236)     at com.mendix.connectionbus.modelsynchronization.SynchronizationManager.analyzeModel(SynchronizationManager.scala:227)     at com.mendix.connectionbus.modelsynchronization.SynchronizationManager.analyzeCurrentDatabase(SynchronizationManager.scala:143)     at com.mendix.connectionbus.modelsynchronization.SynchronizationManager.$anonfun$stateMachine$3(SynchronizationManager.scala:76)     at com.mendix.connectionbus.modelsynchronization.SimpleStateMachine$SimpleStateMachine.effect(SynchronizationManager.scala:47)     at com.mendix.connectionbus.modelsynchronization.SynchronizationManager.analyze(SynchronizationManager.scala:133)     at com.mendix.connectionbus.ConnectionBusImpl.collectDatabaseSynchronizationInformation(ConnectionBusImpl.scala:276)     at com.mendix.basis.impl.MxRuntimeImplBase.collectDdlCommands(MxRuntimeImplBase.java:373)     at com.mendix.basis.impl.MxRuntimeImplBase.doSynchronization(MxRuntimeImplBase.java:285)     at com.mendix.basis.impl.MxRuntimeImplBase.startConnectionBus(MxRuntimeImplBase.java:274)     at com.mendix.basis.impl.MxRuntimeImplBase.start(MxRuntimeImplBase.java:246)     at com.mendix.m2ee.appcontainer.actions.StartAction.startRuntime(StartAction.scala:30)     at com.mendix.m2ee.appcontainer.actions.StartAction.execute(StartAction.scala:17)     at com.mendix.m2ee.appcontainer.server.handler.HttpAdminHandlerBase.service(HttpAdminHandlerBase.java:128)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)     at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764)     at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:529)     at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221)     at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1385)     at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:176)     at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:484)     at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:174)     at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1307)     at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:129)     at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122)     at org.eclipse.jetty.server.Server.handle(Server.java:563)     at org.eclipse.jetty.server.HttpChannel.lambda$handle$0(HttpChannel.java:505)     at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:762)     at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:497)     at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:282)     at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:314)     at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100)     at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53)     at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:936)     at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1080)     at java.base/java.lang.Thread.run(Thread.java:834) ”   The above screen shot is of 8.1.32 settings where i dont have the aboue option to change in 9.24.3 version. Thanks in advance ..!!!
asked
2 answers
1

Did you read this documentation: https://docs.mendix.com/refguide8/uniqueness-constraint-migration/

You might want to contact Mendix support to get access to the migration toolkit.

 

Regards,

Ronald

 

answered
0

As Ronald suggested, contact Mendix support to get the migration tooling.

You need to run this tooling in your 8.13.2 application and remove the duplicate constraints when running the application. After that you can run the upgraded model version.

answered