Known issues and limitations for Data Replication

Replication fails with OutOfMemoryError and remains in Running state without replicating any data

Applies to: 5.2.0

Fixed in: 5.2.1

Problem: A data replication job fails within an hour or two with an OutOfMemoryError. However, the job remains in the Running state for several days and does not replicate any data to the target.

Cause: The replication job fails to deallocate memory for certain metrics leading to memory leaks that cause the OutOfMemoryError. The job run status is not reset and incorrectly shows the job as Running even though the service stops replicating data after the error occurs.

Workaround: For help resolving the error, contact IBM software support.

Timestamp column with default value fails to replicate to the target datastore

Applies to: 5.2.0

Fixed in: 5.2.1

Problem: When you run a data replication job with the Copy business goal setting, the job fails to replicate timestamp columns that contain a default value such as the current time value.

Cause: The replication job generates a query that incorrectly specifies default timestamp values in single quotes.

Replication fails when creating PostgreSQL tables with columns containing double precision and time zone data types

Applies to: 5.2.0

Fixed in: 5.2.1

Problem: When you try to replicate data from a PostgreSQL database, tables that contain double precision and time zone data types fail to replicate to the target database.

Cause: The double precision and timezone data types are not parsed correctly during the replication run.

Replication fails when updating Oracle tables with columns containing timestamps

Applies to: 5.2.0

Fixed in: 5.2.1

Problem: When you try to update tables in an Oracle database with the ALTER TABLE ADD COLUMN option, the operation fails.

Cause: Columns with timestamps are not parsed correctly.

New tables created without the CHANGE DATA CAPTURE flag enabled are not detected when the replication job is in the Running state

Applies to: 4.6.0 and later

Fixed in: 5.2.1

Problem: When replication is running and a new table is created without the CHANGE DATA CAPTURE flag, the table is not replicated, even if the flag is later enabled using an ALTER TABLE statement.

Cause: When the replication job is running, changes to new tables are captured only if the CHANGE DATA CAPTURE flag is present in the initial CREATE TABLE statement.

Workaround: Make sure the CHANGE DATA CAPTURE flag is included in the CREATE TABLE statement when you add new tables while replication is running.

You cannot modify the structure of target tables outside of Data Replication

When you run a Data Replication asset that has the Copy business goal, Data Replication owns the maintenance of the target tables. You will not be able to modify the structure of these target tables outside of Data Replication. If Data Replication is in the process of applying a structural change to a table, that table might be temporarily locked for reads.