Knowledge Base >> Workaround for "ORA-01461: can bind a LONG value only for insert into a LONG column"

Workaround for "ORA-01461: can bind a LONG value only for insert into a LONG column" - Confio Article 1545

Confio Article: 1545 Published: Apr 29 2009 11:55 AM
Version: 4.3 Topic(s): Install and Setup Database Problems Ignite Management
Product(s): Ignite
Database(s): Oracle

Symptom

If you see errors in the Ignite logs similar to below, this article will provide a workaround.  The location of the error can change, i.e. it can occur in modules other than TextPollJob.

 

org.quartz.JobExecutionException: TextPollJob failed [See nested exception: org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL [INSERT INTO CONST_4 (H, P, ST, SS, SE, PNAME, LN, TRUNCATED, D) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)]; SQL state [72000]; error code [1461]; ORA-01461: can bind a LONG value only for insert into a LONG column

 

 

Detailed Analysis

More discussion about this problem can be found in the following articles:

- http://vsadilovskiy.wordpress.com/2007/10/19/ora-01461-can-bind-a-long-value-only-for-insert-into-a-long-column

- Metalink Note: 3756847.8

 

Workaround

The workaround for this problem is to do the following:

1. Edit the <ignite_home>/iwc/tomcat/ignite_config/idc/repo.properties file on the Ignite PI server machine and add the following line:

 repo.additionalProperties=oracle.jdbc.RetainV9LongBindBehavior=true

2. Restart the Ignite PI Server

  • On Windows, restart the Ignite PI service
  • On Linux/Unix, run shutdown.sh followed by startup.sh

 

Tags: bind ORA-1461 jdbc long insert 1461 72000