daixixidai commented on issue #8463:
URL: https://github.com/apache/seatunnel/issues/8463#issuecomment-4170197697
> `# 定义运行时环境 env { parallelism = 1 job.mode = "STREAMING" }
>
> source { Oracle-CDC { username = "C##CDC_TEST" password = "xxxxx"
database-names = ["CDC_TEST"] schema-names = ["AAA"] table-names =
["CDC_TEST.AAA.BBB"] url = "jdbc:oracle:thin:@//192.168.1.1:1521/CDC_TEST"
startup.mode = "initial" source.reader.close.timeout = 120000 #
use_select_count = false # 全量阶段，是否用 select count(_) 获取数据量；当 count(_) 比 analyze
table 速度快时，可设置为 true # skip_analyze = false # 全量阶段，是否跳过 analyze
table。如果表数据变更不频繁，可以设为true。 connection.pool.size = 1 # schema-changes.enabled =
true # 启用 schema evolution 功能 # exactly_once = true # 默认为
false。是否启用数据的精确一次性处理。启用 extractly one 语义，可确保数据不会重复 # snapshot.split.size=100000
debezium { database.name = "TESTDB" # 需指定 CDB 名称 database.pdb.name = "CDC_TEST"
# 需指定 PDB 名称 # debezium.log.mining.strategy="online_catalog" #
debezium.database.tabl
ename.case.insensitive="false" } }
>
> }
>
> sink { ... }`
>
> I'm using Oracle 19c for CDC synchronization, and the cdb+pdb mode and
Debezium configuration have been bothering me for a long time. I've made many
configuration changes but always end up with errors. I checked the underlying
dependency and found that Debezium is at version 1.9. Is this compatible? Or
should I switch to Flink for CDC?
I was wrong，the config path and permission must be same as the manual.notice
the path just like
alter system set db_recovery_file_dest = '/opt/oracle/oradata/recovery_area'
scope=spfile;
CREATE TABLESPACE logminer_tbs DATAFILE
'/opt/oracle/oradata/ORCLCDB/logminer_tbs.dbf' SIZE 25M REUSE AUTOEXTEND ON
MAXSIZE UNLIMITED;
CREATE TABLESPACE logminer_tbs DATAFILE
'/opt/oracle/oradata/ORCLCDB/ORCLPDB1/logminer_tbs.dbf' SIZE 25M REUSE
AUTOEXTEND ON MAXSIZE UNLIMITED;
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
