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

Bind a LONG value only for insert into a LONG column Exception



The user was observing 'can bind a LONG value only for insert into a LONG column' error in Pega log file.

Error Messages

2016-12-30 00:40:26,152 [ PegaRULES-Batch-4] ( internal.access.DatabaseImpl) ERROR - Encountered problem when performing a Commit; ORA-01461: can bind a LONG value only for insert into a LONG column;;DatabaseException caused by prior exception: java.sql.BatchUpdateException: ORA-01461: can bind a LONG value only for insert into a LONG column;; |

Steps to Reproduce

Not Applicable

Root Cause

An issue in the custom application code or rules. User was inserting page XML data to one of the column in the data base table. Checked the structure of data base table and observed that the column data type has been specified as VARCHAR2(4000) in order to insert large data which is causing the issue.


Change the data type of the column to CLOB from VARCHAR2(4000) in the data base table. Below are the links to articles that are suggesting to use the CLOB data type.

Published February 18, 2017 - Updated October 8, 2020

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