Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

BatchUpdateException when max length exceeds 4k

SA-46173

Summary



Severe SQL Exception and BatchUpdateException occur when extracting a text property, with values that are greater than 4K in length, to a target database.


Error Messages



ERROR - Severe SQL 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


Steps to Reproduce

  1. Create a text property.
  2. Enter the value that is greater than 4K in length.
  3. Run the BIX extract.


Root Cause



An issue in the custom application code or rules. When extracting a property with text length of 4K or greater, the target database column must be a CLOB as the varchar2 column has a 4K byte limit.

Resolution



Perform the following local-change:
  1. Click the gear icon besides the property name, in the extract rule, and change the type to LongText.
  2. Change the target database column to type CLOB.

Published December 9, 2017 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us