Question

3
Replies
1504
Views
Deni Soemeri (DESATSBAML)
Bank of America Corporation
Application Developer
Bank of America Corporation
US
DESATSBAML Member since 2010 2 posts
Bank of America Corporation
Posted: June 29, 2016
Last activity: January 23, 2017
Posted: 29 Jun 2016 23:21 EDT
Last activity: 23 Jan 2017 2:58 EST
Closed
Solved

ORA-01461: can bind a LONG value only for insert into a LONG column

SR-A77450


Detailed Description
Receive production alert from BIX:

11:55:03,501 [ia.bankofamerica.com] ( internal.access.ExtractImpl) ERROR - Batch Update Exception: ORA-01461: can bind a LONG value only for insert into a LONG column


java.sql.BatchUpdateException: ORA-01461: can bind a LONG value only for insert into a LONG column

.

.

SR-A77450

Detailed Description
Receive production alert from BIX:
11:55:03,501 [ia.bankofamerica.com] ( internal.access.ExtractImpl) ERROR - Batch Update Exception: ORA-01461: can bind a LONG value only for insert into a LONG column
java.sql.BatchUpdateException: ORA-01461: can bind a LONG value only for insert into a LONG column
.
.
.
We ran into this issue before and determined some characters were from windows (smart quote) being embedded in the case history note. Now we run into this issue again and root cause is still unknown.
We'd like to request,
a.  How to find the case causing this issue and what character in the blob is causing this issue. We can not look at a case in UI because data is truncated.  We can't look from Developer UI because trying to look at just one case is throwing internal server error.
b.  If there's a way to fix this data from the back-end (without user having to reopen the case and edit the data) that'd be awesome as well.
 
Steps to Reproduce
Rerun BIX
 
Error Message
java.sql.BatchUpdateException: ORA-01461: can bind a LONG value only for insert into a LONG column  at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10055)
  at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:213)
  at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.executeBatch(DatabasePreparedStatementImpl.java:532)
  at com.pega.pegarules.data.internal.access.ExtractImpl.addDbRow(ExtractImpl.java:3866)
  at com.pega.pegarules.data.internal.access.ExtractImpl.writeRow(ExtractImpl.java:3654)
  at com.pega.pegarules.data.internal.access.ExtractImpl.WritetoOutput(ExtractImpl.java:3569)
  at com.pega.pegarules.data.internal.access.ExtractImpl.doExtract(ExtractImpl.java:2478)
  at com.pega.pegarules.data.internal.access.ExtractImpl.runExtract(ExtractImpl.java:1280)
  at com.pega.pegarules.data.internal.access.ExtractImpl.run(ExtractImpl.java:1050)
  at com.pega.pegarules.data.internal.access.ExtractImpl.init(ExtractImpl.java:1024)
  at com.pega.pegarules.data.internal.access.ExtractImpl.main(ExtractImpl.java:976)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
  at java.lang.reflect.Method.invoke(Method.java:611)
  at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:348)
  at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:389)
  at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:438)
  at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:88)
 
 

Message was edited by: Lochan to add Category

Data Integration System Administration Support Case Exists
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.