[Bug]: varchar to CLOB data corruption on Linux with hop-run.sh (works on Windows GUI)

[ajabshinde]

Apache Hop version?

2.12

Java version?

openjdk 17.0.18

Operating system

Windows

What happened?

varchar to CLOB data corruption on Linux with hop-run.sh (works on Windows GUI)

Description:
Scenario:

• Using Apache Hop 2.12
• Pipeline fetches data from MSSQL varchar columns
• Inserts data into Oracle CLOB columns
• Works fine with hop-gui.bat on Windows
• Fails on Linux with hop-run.sh (data corruption or encoding issues)

Expected Result:

• Data should be correctly inserted into CLOB columns on Linux

Actual Result:

• Data not inserting for to the target table
  but when we run the same pipeline from Windows machine via Hop-gui.bat then its run fine and also inserts data into target table

General Information:

• Hop Version: 2.12
• Operating System: Linux VM
• Java Version: openjdk 17.0.18
• MSSQL JDBC Driver: mssql-jdbc-12.10.0.jre11.jar
• Oracle JDBC Driver: ojdbc11.jar
• Error Message/Log: 026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - ERROR: Because of an error, this transform can't continue:
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - ERROR: org.apache.hop.core.exception.HopException:
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - Error batch inserting rows into table [TMP_COMMENTS].
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - Errors encountered (first 10):
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - ORA-01461: can bind a LONG value only for insert into a LONG column
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 -
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - https://docs.oracle.com/error-help/db/ora-01461/
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 -
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 -
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - Error updating batch
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - ORA-01461: can bind a LONG value only for insert into a LONG column
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 -
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - https://docs.oracle.com/error-help/db/ora-01461/
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 -
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 -
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - at org.apache.hop.pipeline.transforms.tableoutput.TableOutput.writeToTable(TableOutput.java:339)
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - at org.apache.hop.pipeline.transforms.tableoutput.TableOutput.processRow(TableOutput.java:116)
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - at org.apache.hop.pipeline.transform.RunThread.run(RunThread.java:54)
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - at java.base/java.lang.Thread.run(Thread.java:840)
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - Caused by: org.apache.hop.core.exception.HopDatabaseBatchException:
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - Error updating batch
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - ORA-01461: can bind a LONG value only for insert into a LONG column
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 -
  2026/04/12 22:42:46 - TMP_STG_SNHUB_L1_BORIS_LOG_UNION 2.0 - https://docs.oracle.com/error-help/db/ora-01461/

Issue Priority

Priority: 3

Issue Component

Component: Hop Run

[bamaer]

Finding a proper reproduction path for ORA-1461 turns out to be tricky. Can you give us some more details on your

• Oracle database version
• Oracle JDBC driver version (you mentioned ojdbc11.jar, but these also have a version that is shown at the "installed driver" field in your Relational Database Connection metadata item).
• Linux distribution and version

[ajabshinde]

On Thu, Apr 30, 2026 at 8:39 AM Bart Maertens ***@***.***> wrote: *bamaer* left a comment (apache/hop#7057) <#7057 (comment)> Finding a proper reproduction path for ORA-1461 turns out to be tricky. Can you give us some more details on your - Oracle database version :- oracle 19c Oracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production

Also, it wokrs in Acceptance but not in production and the as below are the datatype: ACC:- [image: image.png] but it doesn't work in production, see below screenshot. PROD:- [image: image.png]

- Oracle JDBC driver version (you mentioned ojdbc11.jar, but these also have a version that is shown at the "installed driver" field in your Relational Database Connection metadata item). - Linux distribution and version :-

PRETTY_NAME="Ubuntu 22.04.5 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.5 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL=" https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy Please look into it and let me know if more information is required. Thanks and Regards,

…

— Reply to this email directly, view it on GitHub <#7057 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CBXGI6WKAG3Q2OEDO6TO3YD4YLYJLAVCNFSM6AAAAACYJS2WN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGNJQGIZDCMRYGE> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[bamaer]

Your screenshots are missing.
What are the differences between your ACC and PROD environments (operating system, Oracle version, java version, table structure, ...)?
I'm not saying there can't be an issue, but we need a reproduction path before we can start working on a fix.