Client and server integration for replicating data

A computer-readable medium carrying one or more sequences of instructions for a replication client coupled with a target database server, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

• receiving a plurality of change records for a plurality of transactions performed on a source database;
• transmitting the plurality of change records to a database server over a stream of change records;
• detecting an unsupported change record, wherein the unsupported change record is associated with a current transaction;
• after detecting the unsupported change record:
• pausing transmission of the plurality of change records over the stream;
• transmitting a synchronization command over the stream to the database server;
• receiving a notification from the database server in response to the synchronization command;
• after receiving the notification, causing execution of the current transaction by submitting at least one database command to the database server;
• resuming transmission of the plurality of change records over the stream after completion of the function.

A computer-readable medium carrying one or more sequences of instructions for a database server coupled with a replication client, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

• receiving a plurality of change records from a replication client over a stream of change records associated with a plurality of transactions performed on a source database;
• determining at least one batch, each batch of the at least one batch comprising change records for at least one transaction received over the stream;
• for a particular batch selected from the at least one batch:
• generating dependency data for at least one change record in the particular batch based on at least one constraint identifier for at least one column associated with the at least one change record;
• determining an ordered grouping of the change records of the particular batch based on an operation type of each change record, and the dependency data of each change record, wherein change records sharing operation types are grouped together unless a division based on the dependency data is determined;
• generating a reordered transaction comprising a plurality of reordered operations based on the ordered grouping of the change records of the particular batch;
• executing the reordered transaction.

An apparatus comprising:

• a network interface that is coupled to the data network for receiving one or more packet flows therefrom;
• at least one processor;
• one or more stored sequences of instructions which, when executed by the processor, cause the at least one processor to perform:
• receiving a plurality of change records for a plurality of transactions performed on a source database;
• transmitting the plurality of change records to a database server over a stream of change records;
• detecting an unsupported change record, wherein the unsupported change record is associated with a current transaction;
• after detecting the unsupported change record:
• pausing transmission of the plurality of change records;
• transmitting a synchronization command over the stream to the database server;
• receiving a notification from the database server in response to the synchronization command;
• after receiving the notification, causing execution of the current transaction by submitting at least one database command to the database server;
• resuming transmission of the plurality of change records after completion of the function, wherein change records associated with the transaction are not transmitted.