In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

(312) #community-jdbc > can bind a LONG value only for insert into a LONG column - debezium - Zulip (zulipchat.com)

What Debezium connector do you use and what version?

Postgres Connector and Debezium 2.7

What is the connector configuration?

<Your answer>

What is the captured database version and mode of deployment?

(E.g. on-premises, with a specific cloud provider, etc.)

Source: Postgres V13

Target: Oracle 11.2

What behavior do you expect?

My source Postgres table has TEXT data type. It should be synced in Target Oracle table CLOB data type.

What behavior do you see?

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

Do you see the same behaviour using the latest released Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

I already raised this issue in (311) #community-jdbc > can bind a LONG value only for insert into a LONG column - debezium - Zulip (zulipchat.com) forum. I was asked to raise Jira ticket for this. Please refer the above link.

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

The error log is available in the below link.

(312) #community-jdbc > can bind a LONG value only for insert into a LONG column - debezium - Zulip (zulipchat.com)

Also attached in the file.Connector_logs.txt

How to reproduce the issue using our tutorial deployment?

The source table should have TEXT data type. And the target should have CLOB data type. 

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Enhancement

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

<Your answer>