Return
-
Title
How does SharePlex handle replication of an Oracle partitioned table whose partition definition differs across Source and Target? -
Description
It is possible for Oracle partitioned tables to differ in terms of partition definition across Source and Target.This could be mainly due to how applications wish to access the data on the Target database.This article delves on how SharePlex handles such replication.Where an Oracle partitioned table on Source is replicating to an Oracle partitioned table on Target, the partition definition can differ.The Source table might have Range Partition and the Target Table has Interval Partition.The Partition Key may also differ on Source and Target though the structure is identical except for the key definition.The question is, how does SharePlex handle replication where the partition definition differs from Source to Target. -
Resolution
Replication should work normally even if the Oracle partitioned table differs from Source to Target in terms of partition definition.The SharePlex Post process simply submits the SQL to the Target database and the Target database applies it to the appropriate partition (where the Target table is an Oracle partitioned table) or to the Target table (where the Target table is a non-partitioned table).