Replicate - connect_cdc_sqdata - Latest

Connect CDC (SQData) Replicator Engine

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (SQData)
Version
Latest
Language
English
Product name
Connect CDC (SQData)
Title
Connect CDC (SQData) Replicator Engine
Copyright
2024
First publish date
2000
ft:lastEdition
2024-08-01
ft:lastPublication
2024-08-01T16:58:30.842568

The REPLICATE statement must be the first statement, other than comments, in the configuration script and may occur only once in the script. It indicates the nature and location of the source and the target of the replication. It also indicates the desired level of parallel processing to be used.

Source Target
DB2 z/OS Kafka, JSON format
DB2 z/OS Kafka, AVRO Confluent
DB2 z/OS HDFS, JSON format
DB2 z/OS HDFS, AVRO Container
DB2 z/OS File, JSON format
DB2 z/OS File, AVRO Container
IMS z/OS Kafka, CDC Raw Format, interim target with Apply Engine Consumer
VSAM z/OS Kafka, CDC Raw Format, interim target with Apply Engine Consumer
Syntax
REPLICATE <source_nature> <source_url> TO <target_nature> <target_url> [WITH <number> WORKER[S]];
Note:
  • The Kafka URL can be simplified by specifying the brokers in the sqdata_kafka_producer.conf file and when AVRO is used with the Confluent Schema Registry, the topic_id and partition will be automatically retrieved from the Schema Registry for each Source Table Reference. The "key" option specifies that the primary key(s), concatenated if necessary, that are defined in the source Db2 catalog, will be used for topic partitioning. This ensures that all rows captured with the same key will be processed in the same partition.
  • Kafka with Confluent managed AVRO schemas requires that the OPTIONS Statement specify the Confluent Schema Repository’s url.
  • The relationship between the source Subject, Topic and Alias are matters determined by the planners and architects of the organization's Confluent Schema Registry.
  • hdfs or file with AVRO Container require all source records to be sent to a single file because the container will contain all possible Schema's.
  • WITH <number> WORKERS clause applies only to Kafka targets and will be silently ignored for all others.
  • The addition of a new Table to the source Relational database will by default automatically initiate its Replication even if a SOURCE reference for each Table, as seen in later examples, has not been specified in the Replicator Engine script. This behavior can be eliminated however, by the creation of a user "Exit" program to either dynamically retrieve the required information or terminate the Replicator.
  • The CDC MESSAGE target_url supports only Connect CDC SQData Apply Engine Kafka Consumer targets.