# US 11,442,962 B1 · Method for replacing a currently operating data replication engine with a new data replication engine without application downtime and while preserving target database consistency, and by joining the source database transactions

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,442,962 B1
- Document ID: US11442962B1
- Status: Granted
- Kind: B1
- Application number: 17/335,221
- Filed: 2021-06-01
- Granted: 2022-09-13
- Earliest claimed: 2016-12-20
- Assignees: Gravic, Inc.
- Applicants: Gravic, Inc.
- Inventors: Paul J. Holenstein; Bruce D. Holenstein; John R. Hoffmann; Wilbur H. Highleyman
- Web page: https://patentgrep.com/patent/US11442962B1

## CPC

- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/273: {Asynchronous replication or reconciliation}
- G06F 9/466: {Transaction processing}
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 11/2097: {maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups)}
- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 11/1471: involving logging of persistent data for recovery
- G06F 11/1474: in transactions (updating of structured data in databases G06F16/23)
- G06F 2201/80: Database-specific techniques
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An automated method is provided for replacing a currently operating data replication engine with a new data replication engine. The currently operating data replication engine replicates source database transactions including any new source database transactions committed in an audit trail of the source database before the currently operating data replication engine stops replicating. All new source database transactions that the currently operating data replication engine has not completed replicating are joined. The currently operating data replication engine is stopped when all of the source database transactions that were not joined have completed replicating. All joined transactions are then voted to be committed and are replicated. The new data replication engine replicates all new source database transactions started after the currently operating data replication engine stops.

## Claims

### Claim 1

An automated method for replacing a currently operating data replication engine with a new data replication engine without application downtime and while preserving target database consistency, the currently operating data replication engine and the new data replication engine replicating source database transactions from an audit trail of a source database in a source system to a target database, the method comprising replacing the currently operating data replication engine with the new data replication engine, the replacing comprising the steps of:
(a) replicating, by the currently operating data replication engine, source database transactions, including any new source database transactions committed in the audit trail of the source database before the currently operating data replication engine stops replicating;
(b) starting the new data replication engine;
(c) joining as a voting participant, by the new data replication engine, all new source database transactions that the currently operating data replication engine has not completed replicating;
(d) stopping the currently operating data replication engine when all of the source database transactions not joined in step (c) have completed replicating;
(e) voting, by the new data replication engine, to commit all transactions joined in step (c); and
(f) replicating, by the new data replication engine:
(i) all source database transactions that are committed in step (e), and
(ii) all new source database transactions started after the currently operating data replication engine stops.

### Claim 2 (depends on 1)

The method of claim 1 wherein the replicating occurs in the source database transaction commit order.

### Claim 3 (depends on 1)

The method of claim 1 further comprising:
(g) generating a list of new source database transactions, wherein the list of new source database transactions is provided by the data replication engine.

### Claim 4 (depends on 1)

The method of claim 1 further comprising:
(g) generating a list of new source database transactions, wherein the list of new source database transactions is provided by a database management system (DBMS) or a transaction management facility (TMF).

### Claim 5 (depends on 1)

The method of claim 1 further comprising:
(g) generating a list of new source database transactions, wherein the list of new source database transactions is provided by searching the audit trail from a current time stamp back to or past an abort timer time.