Question
JPMorgan Chase
US
Last activity: 18 Sep 2019 11:52 EDT
Data base: ORA-01461: can bind a LONG value only for insert into a LONG column
Hi All,
Getting the below error. can any one please let me know how to fix the issue without converting the varchar column to CLOB
ORA-01461: can bind a LONG value only for insert into a LONG column
Pegasystems Inc.
FR
Hello,
Actually CLOB might not be supported on your Pega version. Which one is it? How did you get this issue?
Pegasystems Inc.
IN
Can you please look into below posts related to this issue
https://pdn.pega.com/troubleshooting-ora-01460-and-ora-01461-errors-database-operations-oracle-10203
https://pdn.pega.com/support-articles/ora-01461-can-bind-long-value-only-insert-long-column
PEG
GB
Is the underlying column actually a CLOB or a LONG
I doubt we support the latter in any version (at least those in the last 9-10 years)
JPMorgan Chase
US
This is Varchar(4000) and in the input we are appending more than 4000 Character how erver pega is truncating the data to 4000 but due to special characters it was not saving the data properly as DB considers one Special character as multiple characters.
PEG
GB
I think that may be out of our control, as 4000 bytes this is the Oracle limit.
If we add an character check before performing the same this would introduce performance overheads which would be unfavourable (in my opinion).