An IBM Data Replication connector provides data connectivity and metadata integration for both internal and external data sources. You can configure a data store to be used by your Data Replication asset and add a connection to the data store in your project.
Tech preview This is a technology preview and is not yet supported for use in production environments.
All sources can replicate to all targets.
| Data store | Source | Target |
|---|---|---|
| Amazon RDS for PostgreSQL | ✓ | |
| Apache Kafka | ✓ | |
| IBM Db2 on Cloud | ✓ | ✓ |
| IBM Db2 Warehouse | ✓ | |
| Oracle | ✓ |
Restrictions
Some objects are not eligible for data replication. When you select a table that is ineligible for data replication, either by replicating the schema in which it exists or by selecting the table, you can save the Data Replication asset, start it and edit it as usual. When you run the Data Replication asset, the asset will change status to Running even if no tables are eligible for replication. However, the event log will display messages for objects, tables or columns that are not replicating because they are ineligible and the reason why they cannot replicate.
The following objects in the source database cannot be replicated when you use the Data Replication service:
- Column-oriented tables
- Synonyms
- System tables
- Tables without a primary key or unique constraint Exception: You can replicate tables without a primary key or unique constraint to Apache Kafka and IBM watsonx.data databases.
- Table columns that contain data types that are incompatible in the target table
- Temporary tables
- Views
Certain source operations are not replicated to the target. These operations include:
- Truncating PostgreSQL source tables
- Altering columns of Db2 on Cloud source tables
Parent topic: Data Replication (beta)