Unique Constrain Violation for ACT_UNIQ_VARIABLE

Camunda 7 Topics Discussion & Questions
1

Hi,

we have a similar problem to

Is there any way to easily identify which variable causes the constraint violation?

thanks,
Patrick

2

Hi Patrick,

You can enable debug logging for the Mybatis mapper for variable-related statements. This will then log all SQL statements with their parameters. The logger name is org.camunda.bpm.engine.impl.persistence.entity.VariableInstanceEntity.

Cheers,
Thorben

3

@PatrickG , One way to identify duplicates will be to disable this constraint on ACT_RU_VARIABLE and let it work for some time. Later you can enable constraint back and log all duplicates into some other table.

1.) Disable the unique constraint in ACT_RU_VARIABLE
2.) Create one table (Under same schema) like:
CREATE TABLE EXCEPTIONS(ROW_ID ROWID, OWNER VARCHAR2(30),
TABLE_NAME VARCHAR2(30), CONSTRAINT VARCHAR2(30));
3.)Execute your application for some time
4.) ALTER TABLE ACT_RU_VARIABLE
ENABLE VALIDATE CONSTRAINT ACT_UNIQ_VARIABLE
EXCEPTIONS INTO EXCEPTIONS;

Thanks,
Sudhanshu

4