Supported source and targets

The first step in deploying a CDC Replication configuration solution is to establish your replication needs. You need to determine each source database for replication and its corresponding target for replication. A CDC Replication source engine captures changed data in your source database and sends source table changes to the target engine.

The following table lists all of the databases, middleware, and messaging middleware providers that CDC Replication supports.

Supported source databases Supported target databases and middleware applications
Db2® on Cloud (formerly dashDB® for Transactions)2
Db2 Warehouse (formerly dashDB Local)3
Db2 Warehouse on Cloud (formerly dashDB for Analytics)3
IBM® Db2 for Linux®, UNIX and Windows (LUW)
IBM Db2 for i
IBM Db2 for z/OS®
IMS
Informix®
Microsoft SQL Server
MariaDB
MySQL
Oracle
PostgreSQL (including Amazon RDS for PostgreSQL, Amazon Aurora PostgreSQL, Azure Database for PostgreSQL)
Sybase
VSAM
Apache Hadoop
Apache Kafka (known compatible commercial distributions include Amazon MSK, Confluent Platform, Cloudera Distribution of Apache Kafka, Hortonworks Data Platform, IBM BigInsights®, IBM Event Streams)
Amazon Redshift
CDC Replication Engine for Event Server1
CDC Replication Engine for FlexRep
Db2 on Cloud (formerly dashDB for Transactions)2
Db2 Warehouse (formerly dashDB Local)
Db2 Warehouse on Cloud (formerly dashDB for Analytics)
EDB Postgres Advanced Server
Google BigQuery
IBM Cloudant®
IBM Db2 for Linux, UNIX and Windows (LUW)
IBM Db2 for i
IBM Db2 for z/OS
IBM InfoSphere® DataStage®
IBM Integrated Analytics System
IBM MQ for z/OS (using Classic CDC for z/OS)
IBM Performance Server (IPS)
Informix
Microsoft Azure SQL Database
Microsoft Azure SQL Database Managed Instance
Microsoft SQL Server
MySQL
Netezza®
Netezza Performance Server (NPS®)
Oracle
PostgreSQL (including Amazon RDS for PostgreSQL, Amazon Aurora PostgreSQL, Azure Database for PostgreSQL)
SingleStoreDB
Snowflake
Sybase
Teradata
YugabyteDB
  1. Version 11.3.3
  2. Only Enterprise Edition supported
  3. Only Enterprise Edition and row-organized tables supported

Each database that acts as a source for replication must have an instance of the CDC Replication replication engine installed, as does each target for replication.

Both the Management Console and Access Server applications must also be installed to configure and monitor replication between the source database and the target of replication.

If you are replicating from a non-relational database by using IBM Classic Change Data Capture for z/OS, you must also install Classic Data Architect.

For CDC Replication, 11.3.3 engines can inter-operate with 11.4 engines.