KB-1746 Unique constraint error upon importing/saving a WebAPI

Parmida Borhani — Fri, 12 Oct 2018 02:50:49 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 10/12/2018 2:50:49 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently:

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

The error is generally associated with using Oracle Real Application Clusters (RAC) as the database for the Appian primary datasource.

Oracle RAC has a sequence cache on each node, which is used to determine the next sequence value. In some scenarios this caused the uniqueness constraint to be violated due to a mismatch between RAC node sequence caches.

This issue has been addressed via AN-105127 in the following Appian hotfixes/versions:

The fix guarantees to return the correct value of the sequence in order across all nodes in the RAC cluster.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to Appian 18.1 and earlier using Oracle Real Application Clusters (RAC) as the Appian primary datasource.

Last Reviewed: October 2018

Tags: known issues, database, integration, fixed issues, infrastructure

DRAFT INT-XXXX Unique constraint error upon importing/saving a WebAPI

Jordan Horwat — Thu, 11 Oct 2018 05:17:57 GMT

Revision 16 posted to Appian Knowledge Base by Jordan Horwat on 10/11/2018 5:17:57 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently:

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

The error is generally associated with using Oracle Real Application Clusters (RAC) as the database for the Appian primary datasource.

This issue has been addressed via AN-105127 in the following Appian hotfixes/versions:

The fix guarantees to return the correct value of the sequence in order across all nodes in the RAC cluster.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to Appian 18.1 and earlier using Oracle Real Application Clusters (RAC) as the Appian primary datasource.

Last Reviewed: October 2018

Tags: known issues, database, integration, fixed issues, infrastructure

INT-XXXX Unique constraint error upon importing/saving a WebAPI

Jordan Horwat — Thu, 11 Oct 2018 05:15:44 GMT

Revision 15 posted to Appian Knowledge Base by Jordan Horwat on 10/11/2018 5:15:44 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently:

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

The error is generally associated with using Oracle Real Application Clusters (RAC) as the database for the Appian primary datasource.

This issue has been addressed via AN-105127 in the following Appian hotfixes/versions:

The fix guarantees to return the correct value of the sequence in order across all nodes in the RAC cluster.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to Appian 18.1 and earlier using Oracle Real Application Clusters (RAC) as the Appian primary datasource.

Last Reviewed: October 2018

Tags: known issues, database, integration, fixed issues, infrastructure

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Jordan Horwat — Thu, 11 Oct 2018 05:13:37 GMT

Revision 14 posted to Appian Knowledge Base by Jordan Horwat on 10/11/2018 5:13:37 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently:

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

The error is generally associated with using Oracle Real Application Clusters (RAC) as the database for the Appian Primary Datasource.

This issue has been addressed via AN-105127 in the following Appian hotfixes/versions:

The fix guarantees to return the correct value of the sequence in order across all nodes in the RAC cluster.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to Appian 18.1 and earlier using Oracle Real Application Clusters (RAC) for the Appian Primary Datasource.

Last Reviewed: October 2018

Tags: known issues, database, integration, fixed issues, infrastructure

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Jordan Horwat — Thu, 11 Oct 2018 05:10:30 GMT

Revision 13 posted to Appian Knowledge Base by Jordan Horwat on 10/11/2018 5:10:30 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently:

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

The error is generally associated with using Oracle Real Application Clusters (RAC) as the database for the Appian Primary Datasource.

This issue has been addressed via AN-105127 in the following Appian hotfixes/versions:

The fix guarantees to return the correct value of the sequence in order across all nodes in the RAC cluster.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to Appian 18.1 and earlier using Oracle Real Application Clusters (RAC) for the Appian Primary Datasource.

Last Reviewed: October 2018

Tags: known issues, database, integration, fixed issues, infrastructure

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Jordan Horwat — Thu, 11 Oct 2018 05:10:17 GMT

Revision 12 posted to Appian Knowledge Base by Jordan Horwat on 10/11/2018 5:10:17 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently:

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

The error is generally associated with using Oracle Real Application Clusters (RAC) as the database for the Appian Primary Datasource.

This issue has been addressed via AN-105127 in the following Appian hotfixes/versions:

The fix guarantees to return the correct value of the sequence in order across all nodes in the RAC cluster.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to Appian 18.1 and earlier using Oracle Real Application Clusters (RAC) for the Appian Primary Datasource.

Last Reviewed: October 2018

Tags: known issues, database, integration, fixed issues, infrastructure

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Tom Ryan — Thu, 11 Oct 2018 00:30:00 GMT

Revision 11 posted to Appian Knowledge Base by Tom Ryan on 10/11/2018 12:30:00 AM

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently:

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

The error is generally associated with using Oracle Real Application Clusters (RAC) as the database for the Appian Primary Datasource.

This issue has been addressed via AN-105127 in the following Appian hotfixes/versions. The fix guarantees to return the correct value of the sequence in order across all nodes in the RAC cluster.

Action

Apply the latest hotfix to your Appian installation.

Affected Versions

This article applies to Appian 18.1 and earlier using Oracle Real Application Clusters (RAC) for the Appian Primary Datasource.

Tags: known issues, fixed issues

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Tristan Newmann — Wed, 10 Oct 2018 02:44:06 GMT

Revision 10 posted to Appian Knowledge Base by Tristan Newmann on 10/10/2018 2:44:06 AM

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently:

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

The error is generally associated with using Oracle Real Application Clusters (RAC) as the database for the Appian Primary Datasource.

This issue has been addressed via AN-105127 in the following Appian hotfixes/versions. The fix guarantees to return the correct value of the sequence in order across all nodes in the RAC cluster.

Action

Apply the latest hotfix to your Appian installation.

Affected Versions

This article applies to Appian 18.1 and earlier.

Tags: known issues, fixed issues

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Tristan Newmann — Wed, 10 Oct 2018 02:43:13 GMT

Revision 9 posted to Appian Knowledge Base by Tristan Newmann on 10/10/2018 2:43:13 AM

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently:

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

The error is generally associated with using Oracle Real Application Clusters (RAC) as the database for the Appian Primary Datasource.

Oracle RAC has a node sequence cache, which the sequence.nextval uses to determine the node. The associated fix for this issue guarantees that the next value of the sequence will be in order across the entire RAC cluster, not just for that particular RAC cluster node's sequence cache.

This issue has been addressed via AN-105127 in the following Appian hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation.

Affected Versions

This article applies to Appian 18.1 and earlier.

Tags: known issues, fixed issues

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Afzal Shah — Mon, 04 Jun 2018 11:45:13 GMT

Revision 8 posted to Appian Knowledge Base by Afzal Shah on 6/4/2018 11:45:13 AM

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently:

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

The error is generally produced when using Oracle Real Application Clusters (RAC). As Oracle RAC has a node sequence cache, which the sequence.nextval uses to determine the node, the fix guarantees to return the next value of the sequence in order across the RAC cluster, not just for that particular RAC cluster node's sequence cache.

This issue has been addressed via AN-105127 in the following Appian hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation.

Affected Versions

This article applies to Appian 18.1 and earlier.

Tags: known issues, fixed issues

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Afzal Shah — Mon, 04 Jun 2018 11:40:07 GMT

Revision 7 posted to Appian Knowledge Base by Afzal Shah on 6/4/2018 11:40:07 AM

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently:

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

This issue has been addressed via AN-105127 in the following Appian hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation.

Affected Versions

This article applies to all versions of Appian.

Tags: known issues, fixed issues

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Afzal Shah — Mon, 04 Jun 2018 11:31:15 GMT

Revision 6 posted to Appian Knowledge Base by Afzal Shah on 6/4/2018 11:31:15 AM

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently:

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

Action

This issue has been addressed via AN-105127 in the following Appian hotfixes/versions:

Affected Versions

This article applies to all versions of Appian.

Tags: known issues, fixed issues

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Afzal Shah — Mon, 04 Jun 2018 10:37:02 GMT

Revision 5 posted to Appian Knowledge Base by Afzal Shah on 6/4/2018 10:37:02 AM

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

Action

Apply the latest hotfix to your Appian installation.

Affected Versions

This article applies to all versions of Appian.

Tags: known issues, fixed issues

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Afzal Shah — Mon, 04 Jun 2018 10:34:41 GMT

Revision 4 posted to Appian Knowledge Base by Afzal Shah on 6/4/2018 10:34:41 AM

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

Action

Apply the latest hotfix to your Appian installation.

Affected Versions

This article applies to all versions of Appian.

Tags: known issues, fixed issues

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Afzal Shah — Mon, 04 Jun 2018 10:34:02 GMT

Revision 3 posted to Appian Knowledge Base by Afzal Shah on 6/4/2018 10:34:02 AM

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

Action

Apply the latest hotfix to your Appian installation.

Affected Versions

This article applies to all versions of Appian.

Tags: known issues, fixed issues

[DRAFT ]INT-XXXX Unique constraint upon importing/saving a WebAPI

Afzal Shah — Wed, 23 May 2018 14:33:13 GMT

Revision 2 posted to Appian Knowledge Base by Afzal Shah on 5/23/2018 2:33:13 PM

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

The error is generally produced when using Oracle Real Application Clusters (RAC). Negative consequence, if any, is that it may take a fraction of a second longer for oracle to determine that the sequence.nextval is in order across the cluster instead of just grabbing it from that node's sequence cache, when trying to create or update a web api object. Web api objects are not created by end users. They are created by designers when designing an application or when importing an application that contains web api objects.

Action

undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.

Affected Versions

This article applies to all versions of Appian.

Tags: known issues, fixed issues

Unique constraint upon importing/saving a WebAPI

Afzal Shah — Wed, 23 May 2018 14:29:56 GMT

Revision 1 posted to Appian Knowledge Base by Afzal Shah on 5/23/2018 2:29:56 PM

Symptoms

When attempting to import a package that contains a WebAPI or saving a WebAPI, the following error is produced intermittently

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;

 org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update;
 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (APPIANJ_PRIMARY.TEST_DATA_UC) violated

Cause

Action

undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.

Affected Versions

This article applies to all versions of Appian.

Tags: known issues, fixed issues