[Bug] [dinky1.2.0] Oracle synchronization data query to paimon Lake reported an error

[lexoning]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Oracle synchronization data query to paimon Lake reported an error

What you expected to happen

Oracle sync data to Lake paimon can be queried

How to reproduce

flinkcdc3.1, flink17, paimon0.9 synchronize Oracle data to paimon data lake, but data cannot be queried using dinky

Anything else

oracle ddl :CREATE TABLE "READ_BG"."AOP_PERFORMANCE_TEST"
( "ID" NUMBER(9,0) NOT NULL ENABLE,
"YEAR_D" NUMBER(4,0),
"BG" VARCHAR2(100),
"CENTER" VARCHAR2(100),
"ONE_DEPARTMENT" VARCHAR2(100),
"DEPARTMENT" VARCHAR2(100),
"COST_CENTER" VARCHAR2(100),
"USER_NAME" VARCHAR2(100),
"USER_CODE" VARCHAR2(100),
"USER_TYPE" NUMBER(1,0),
"IS_CLOSE" NUMBER(1,0),
"CREATE_USER" NUMBER(5,0),
"UPDATE_USER" NUMBER(5,0),
"CREATE_DATE" DATE,
"UPDATE_DATE" DATE,
"CREATE_USER_NAME" VARCHAR2(20),
PRIMARY KEY ("ID")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "CUX_DATA" ENABLE,
SUPPLEMENTAL LOG DATA (ALL) COLUMNS
)

Version

1.2.0

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[medivh511]

建议使用dbz的cdc方式到kafka, 再使用paimon cdc的方式到paimon, oracle cdc的方式在flink cdc是非常不全面和不稳定的，这和oracle的一些特殊性有关，要么用最新版本的dbz，要么使用收费的ogg.
dinky不会在oracle上面有太多的改动，以前尝试过，但都不理想，针对oracle cdc，dinky有专门的微信oracle cdc群，基本上做oracle cdc都不会采用dinky的固有方式，dinky这边负责cdc的人也建议尽量不采用dinky oracle cdc的方式，因为flink cdc问题太多

[lexoning]

dbz cdc的方式怎么使用的呢，有没具体文档哈，还有就是我实时更新的数据能体现在湖里吗

[medivh511]

dbz cdc的方式怎么使用的呢，有没具体文档哈，还有就是我实时更新的数据能体现在湖里吗

你可以让文末加你进Oracle CDC群