System and method for heterogeneous database replication from a remote server

Patent metadata

Field	Value
Publication number	US-11645261-B2
Application number	US-201916394876-A
Country	US
Kind code	B2
Filing date	Apr 25, 2019
Priority date	Apr 27, 2018
Publication date	May 9, 2023
Grant date	May 9, 2023

Abstract

In accordance with an embodiment, described herein is a system and method for heterogeneous database replication from a remote server, for example a remote database server. A capture process can be registered as a replication slave to the remote server, and configured to receive transaction event data from that server. Transaction log events associated with a modification to the database at the remote server can be processed, and output as change data, in a canonical format output, for use with one or more heterogeneous targets, for example a target database server or message queue. The process enables capture of transaction log events associated with database transactions at a remote server that may be located on a different computer or network, or within an access-restricted environment such as a cloud environment, without the need to create additional copies of its transaction logs.

First claim

What is claimed is:

1. A system for heterogeneous database replication from a remote server, comprising:
a computer including a processor, and change data system operating thereon that enables replicating of data between database servers;
wherein a capture component, operable to access records at a database via a network connection and perform a capture process, which is registered to the remote server, wherein the database is associated with the remote server, and wherein the remote server is associated with connection parameters that enable the capture process to connect to the remote server and to receive transaction log events that are indicative of database transactions to modify data at the database associated with the remote server;
wherein the capture process is configured to appear and operate as a replication slave to the remote server, including use of a process for:
determining a slave server identifier that enables operation with the remote server, and
determining a log positioning information, including a start position, which information is provided to the remote server for use by the remote server in sending transaction log data beginning from the start position; and

wherein as the data at the database associated with the remote server is modified, the capture process continues to request transaction log events from the remote server indicative of the database transactions to modify the data at the database associated with the remote server, which transaction log events are processed by the capture process operating as the replication slave to the remote server, and output as change data, in a canonical format output for use by a delivery process in applying the change data to one or more target database server or other systems.

2. The system of claim 1 ,
wherein the capture process is registered to operate as a replication slave to the remote server; and
wherein the capture process uses a method to be registered as the replication slave to the remote server, and to receive information from that server, including transaction event data.

3. The system of claim 1 , wherein the environment is a change data capture system, and wherein the transaction log events are written to an output or trail file for use by the change data capture system with the target database server.

4. The system of claim 3 , wherein the change data capture system is provided at a different computer or on a different network from the remote server.

5. The system of claim 1 , wherein the remote server is provided within an access-restricted or cloud environment.

6. The system of claim 1 , wherein the remote server is a MySQL server.

7. The system of claim 1 , wherein the capture component includes one or more access thread and reader thread for accessing the records at the database via the network connection,
wherein as the data at the database associated with the remote server is modified, the capture process requests the transaction log events from the remote server indicative of the database transactions to modify the data at the database associated with the remote server, which transaction log events are processed as the change data for use by the delivery process.

8. The system of claim 1 , wherein one or more delivery processes are used to convert the change data that is read from the database of a first type, for consumption by a plurality of heterogeneous targets, including at least one of a second type of target server and/or a third type of target server, by forming commands or queries according to each particular target, and applying the commands or queries to that target.

9. A method for heterogeneous database replication from a remote server, comprising:
providing, at a computer including a processor, a change data system operating thereon that enables replicating of data between database servers and a capture component, operable to access records at a database via a network connection and perform a capture process, wherein the database is associated with the remote server, and wherein the capture process is:
registered to a remote server, wherein the remote server is associated with connection parameters that enable the capture process to connect to the remote server and
configured to receive transaction log events that are indicative of database transactions to modify data at the database associated with the remote server;

wherein the capture process is configured to appear and operate as a replication slave to the remote server, including use of a process for:
determining a slave server identifier that enables operation with the remote server, and
determining a log positioning information, including a start position, which information is provided to the remote server for use by the remote server in sending transaction log data beginning from the start position; and

wherein as the data at the database associated with the remote server is modified, the capture process continues to request transaction log events from the remote server indicative of the database transactions to modify the data at the database associated with the remote server, which transaction log events are processed by the capture process operating as the replication slave to the remote server, and output as change data, in a canonical format output for use by a delivery process in applying the change data to one or more target database server or other systems.

10. The method of claim 9 ,
wherein the capture process is registered to operate as a replication slave to the remote server; and
wherein the capture process uses a method to be registered as the replication slave to the remote server, and to receive information from that server, including transaction event data.

11. The method of claim 9 , wherein the environment is a change data capture system, and wherein the transaction log events are written to an output or trail file for use by the change data capture system with the target database server.

12. The method of claim 11 , wherein the change data capture system is provided at a different computer or on a different network from the remote server.

13. The method of claim 9 , wherein the remote server is provided within an access-restricted or cloud environment.

14. The method of claim 9 , wherein the remote server is a MySQL server.

15. A non-transitory computer readable storage medium, including instructions stored thereon which when read and executed by one or more computers cause the one or more computers to perform a method comprising:
providing a change data system that enables replicating of data between database servers and a capture component, operable to access records at a database via a network connection and perform a capture process, wherein the database is associated with the remote server, and wherein the capture process is:
registered to a remote server, wherein the remote server is associated with connection parameters that enable the capture process to connect to the remote server and
configured to receive transaction log events that are indicative of database transactions to modify data at the database associated with the remote server;

wherein the capture process is configured to appear and operate as a replication slave to the remote server, including use of a process for:
determining a slave server identifier that enables operation with the remote server, and
determining a log positioning information, including a start position, which information is provided to the remote server for use by the remote server in sending transaction log data beginning from the start position; and

wherein as the data

Assignees

• Oracle Int Corp

Inventors

• Kumar Ashish
• Dubey Avinash
• Sachdev Vinay
• Corbin Scott Roger

Classifications

• G06F16/254

  Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses · CPC title

• G06F16/2358 Primary

  Change logging, detection, and notification (replication G06F16/27) · CPC title

• G06F16/273 Primary

  Asynchronous replication or reconciliation · CPC title

• H04L67/1095

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title