Method for ensuring referential integrity in replication engines by serializing base level change queue data

A computer-implemented method of processing base level data of a change queue in which an order of the data is not serialized at a logical level due to multi-threading in one or more extractors, communication channels or appliers, the base level change queue data being transaction data previously posted to a source database, the method comprising:

• (a) providing a logical replication engine which uses multi-threading in the one or more extractors, communication channels or appliers to replicate the base level change queue data in which the order of the base level change queue data is not serialized at the logical level to a target database;
• and
• (b) posting the base level change queue data that is not serialized at the logical level due to the multi-threading in the one or more extractors, communication channels or appliers to the target database by asynchronous database access operations, which ensures that subsequent database accesses on the target database are initiated in natural flow order by resolving required foreign keys, and preserving required intra- and inter-transaction dependencies, in the target database.

A computer program product for processing base level data of a change queue in which an order of the data is not serialized at a logical level due to multi-threading in one or more extractors, communication channels or appliers, the base level change queue data being transaction data previously posted to a source database, the computer program product comprising a non-transitory computer-readable storage medium encoded with computer-executable instructions for performing the steps of:

• (a) providing a logical replication engine which uses multi-threading in the one or more extractors, communication channels or appliers to replicate the base level change queue data in which the order of the base level change queue data is not serialized at the logical level to a target database;
• and
• (b) posting the base level change queue data that is not serialized at the logical level due to the multi-threading in the one or more extractors, communication channels or appliers to the target database by asynchronous database access operations, which ensures that subsequent database accesses on the target database are initiated in natural flow order by resolving required foreign keys, and preserving required intra- and inter-transaction dependencies, in the target database.