KB-1122 Incompatible/inconsistent data type errors thrown in the application server log after 12 hours

Parmida Borhani — Mon, 30 Jul 2018 03:53:26 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 3:53:26 AM

Symptoms

The following errors are seen in the server log repeatedly, after 12 hours of starting the application server, while using SQL Server or Oracle as the Appian datasource:

SQL Server

[Appian Timer - 1] ERROR org.hibernate.util.JDBCExceptionReporter - The data types ntext and nvarchar(max) are incompatible in the equal to operator."

Oracle

[Appian Timer - 1] ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00932: inconsistent datatypes: expected - got CLOB

Cause

This is an issue when using Sites with SQL Server or Oracle databases. The query that throws the error is invoked to populate sites.csv. This error appears only after 12 hours since the data-metrics logs are written every 12 hours.

This issue has been reported to the Appian product team. The reference number for this issue is AN-69032.

Action

The error can be safely disregarded since it doesn’t have any impact except an empty sites.csv log.

To avoid the logs from getting populated with these error messages and to prevent the increase in disk usage, perform the following steps:

Open appian_log4j.properties under <APPIAN_HOME>/ear/suite.ear/resources.
Disable the log by adding log4j.logger.org.hibernate.util.JDBCExceptionReporter=OFF at the bottom of the file.

Affected Versions

This article applies to Appian 16.1 and later using SQL Server or Oracle databases.

Last Reviewed: July 2017

Tags: known issues, database, infrastructure, open issues

KB-1122 Incompatible/inconsistent data type errors thrown in the application server log after 12 hours

Nick Vigilante — Tue, 25 Jul 2017 11:17:01 GMT

Revision 2 posted to Appian Knowledge Base by Nick Vigilante on 7/25/2017 11:17:01 AM

Symptoms

The following errors are seen in the server log repeatedly, after 12 hours of starting the application server, while using SQL Server or Oracle as the Appian datasource:

SQL Server

[Appian Timer - 1] ERROR org.hibernate.util.JDBCExceptionReporter - The data types ntext and nvarchar(max) are incompatible in the equal to operator."

Oracle

[Appian Timer - 1] ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00932: inconsistent datatypes: expected - got CLOB

Cause

This issue has been reported to the Appian product team. The reference number for this issue is AN-69032.

Action

The error can be safely disregarded since it doesn’t have any impact except an empty sites.csv log.

To avoid the logs from getting populated with these error messages and to prevent the increase in disk usage, perform the following steps:

Open appian_log4j.properties under <APPIAN_HOME>/ear/suite.ear/resources.
Disable the log by adding log4j.logger.org.hibernate.util.JDBCExceptionReporter=OFF at the bottom of the file.

Affected Versions

This article applies to Appian 16.1 and later using SQL Server or Oracle databases.

Last Reviewed: July 2017

Tags: known issues, database, open issues

KB-1122 Incompatible/inconsistent data type errors thrown in the application server log after 12 hours

Nick Vigilante — Fri, 24 Feb 2017 13:48:24 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/24/2017 1:48:24 PM

Symptoms

The following errors are seen in the server log repeatedly, after 12 hours of starting the application server, while using SQL Server or Oracle as the Appian datasource:

SQL Server

[Appian Timer - 1] ERROR org.hibernate.util.JDBCExceptionReporter - The data types ntext and nvarchar(max) are incompatible in the equal to operator."

Oracle

[Appian Timer - 1] ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00932: inconsistent datatypes: expected - got CLOB

Cause

This issue has been reported to the Appian product team. The reference number for this issue is AN-69032.

Action

The error can be safely disregarded since it doesn’t have any impact except an empty sites.csv log.

To avoid the logs from getting populated with these error messages and to prevent the increase in disk usage, perform the following steps:

Open appian_log4j.properties under <APPIAN_HOME>/ear/suite.ear/resources.
Disable the log by adding log4j.logger.org.hibernate.util.JDBCExceptionReporter=OFF at the bottom of the file.

Affected Versions

This article applies to Appian 16.1 using SQL Server or Oracle databases.

Last Reviewed: February 2017

Tags: known issues, database, open issues