IP Library › Granted Patent US 12,693,935
Granted Patent B2
US 12,693,935 · App. 17/991,949 · Granted Jul 28, 2026

Handling data errors

Inventors: Shailesh Chandra Jamloki (Noida, IN); Awajeet Kumar Arya (Bengaluru, IN)
Assignee: International Business Machines Corporation
G06F11/1435G06F11/1469G06F16/27
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,693,935
App. No.
17/991,949
Filed
Nov 22, 2022
Granted
Jul 28, 2026
Kind
B2
Art Unit
2168
USPC
707/691
Abstract

An approach is disclosed that corrects database replication errors. The approach runs a replication tool that replicates a source database of a source database type to a target database of a target database type. When a replication error is encountered that cannot be resolved by the replication tool, the approach matches the replication error to a business logic recovery rule that is selected from a set of business logic recovery rules that are external to the replication tool. The matching business logic recovery rule is applied to the replication error to correct the replication error.

Claims (57)

1 . A method comprising:

running a replication tool that replicates a source database of a source database type to a target database of a target database type; and

in response to encountering a replication error that cannot be resolved by the replication tool:

matching the replication error to a business logic recovery rule selected from a plurality of business logic recovery rules, wherein the plurality of business logic recovery rules are stored in a business logic recovery rules data store that is external to the replication tool; and

applying the business logic recovery rule to the replication error, wherein the applying of the business logic recovery rule corrects the replication error.

2 . The method of claim 1 , wherein the running of the replication tool is halted when the replication error is encountered, the method further comprising:

resuming the running of the replication tool at a point in the replication where the replication error was encountered.

3 . The method of claim 1 , further comprising:

in response to failing to match the replication error to one of the plurality of business logic recovery rules:

receiving the business logic recovery rule from a user of the replication tool; and

writing the business logic recovery rule to the plurality of business logic recovery rules.

4 . The method of claim 1 , further comprising:

determining one or more data points in the replication of the source database to the target database where replication may fail; and

writing one or more of the plurality of business logic recovery rules.

5 . The method of claim 1 , wherein the plurality of business logic recovery rules are written in a human-readable data-serialization language.

6 . The method of claim 5 , wherein the plurality of business logic recovery rules include a rule name, an error identifier, an applicable range, an error type, and a resolution policy.

7 . The method of claim 1 , further comprising:

injecting the plurality of business logic recovery rules into a set of native replication tool recovery resolutions.

8 . An information handling system comprising:

a processor set;

one or more computer readable storage media; and

program instructions stored on the one or more computer readable storage media to cause the processor set to perform operations comprising:

running a replication tool that replicates a source database of a source database type to a target database of a target database type; and

in response to encountering a replication error that cannot be resolved by the replication tool:

matching the replication error to a business logic recovery rule selected from a plurality of business logic recovery rules, wherein the plurality of business logic recovery rules are stored in a business logic recovery rules data store that is external to the replication tool; and

applying the business logic recovery rule to the replication error, wherein the applying of the business logic recovery rule corrects the replication error.

9 . The information handling system of claim 8 , wherein the running of the replication tool is halted when the replication error is encountered comprises:

resuming the running of the replication tool at a point in the replication where the replication error was encountered.

10 . The information handling system of claim 8 , wherein the operations further comprise:

in response to failing to match the replication error to one of the plurality of business logic recovery rules:

receiving the business logic recovery rule from a user of the replication tool; and

writing the business logic recovery rule to the plurality of business logic recovery rules.

11 . The information handling system of claim 8 , wherein the operations further comprise:

determining one or more data points in the replication of the source database to the target database where replication may fail; and

writing one or more of the plurality of business logic recovery rules.

12 . The information handling system of claim 8 , wherein the plurality of business logic recovery rules are written in a human-readable data-serialization language.

13 . The information handling system of claim 12 , wherein the plurality of business logic recovery rules include a rule name, an error identifier, an applicable range, an error type, and a resolution policy.

14 . The information handling system of claim 8 , wherein the operations further comprise:

injecting the plurality of business logic recovery rules into a set of native replication tool recovery resolutions.

15 . A computer program product comprising:

one or more computer readable storage media; and

program instructions stored on the one or more computer readable storage media to perform operations comprising:

running a replication tool that replicates a source database of a source database type to a target database of a target database type; and

in response to encountering a replication error that cannot be resolved by the replication tool:

matching the replication error to a business logic recovery rule selected from a plurality of business logic recovery rules, wherein the plurality of business logic recovery rules are stored in a business logic recovery rules data store that is external to the replication tool; and

applying the business logic recovery rule to the replication error, wherein the applying of the business logic recovery rule corrects the replication error.

16 . The computer program product of claim 15 , wherein the running of the replication tool is halted when the replication error is encountered comprises:

resuming the running of the replication tool at a point in the replication where the replication error was encountered.

17 . The computer program product of claim 15 , wherein the operations further comprise:

in response to failing to match the replication error to one of the plurality of business logic recovery rules:

receiving the business logic recovery rule from a user of the replication tool; and

writing the business logic recovery rule to the plurality of business logic recovery rules.

18 . The computer program product of claim 15 , wherein the operations further comprise:

determining one or more data points in the replication of the source database to the target database where replication may fail; and

writing one or more of the plurality of business logic recovery rules.

19 . The computer program product of claim 15 , wherein the plurality of business logic recovery rules are written in a human-readable data-serialization language.

20 . The computer program product of claim 19 , wherein the plurality of business logic recovery rules include a rule name, an error identifier, an applicable range, an error type, and a resolution policy.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 22, 2022
From: JAMLOKI, SHAILESH CHANDRA; ARYA, AWAJEET KUMAR
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 061850/0851 →
Continuity (1)
Related Publication 20240168850A1 · May 23, 2024
References Cited (11)
US 9639436B2 · Arnold · 2017 [cited by applicant]
US 10089148B1 · Blitzer · 2018 [cited by applicant]
US 11032361B1 · Chen · 2021 [cited by examiner]
US 11308125B2 · Chen · 2022 [cited by examiner]
US 20210216509A1 · Jayanthi · 2021 [cited by applicant]
AU 2003252183A1 · 2004 [cited by examiner]
“Data Error,” Qlik Replicate, Attunity Ltd., Nov. 2020, 2 pages. [cited by applicant]
“Administering Oracle GoldenGate Cloud Service for UNIX Testing and Transforming Data,” Oracle 1994, 6 pages. [cited by applicant]
“Setting data translations on column mappings,” IBM Documentation, International Business Machines Corporation, Mar. 2021, 3 pages. [cited by applicant]
“Attunity Replicate Setup and User Guide,” Version 6.3, Qlik, Attunity Ltd., Jan. 2019, pp. 1-949. [cited by applicant]
“Qlik Enterprise Manager Setup and User Guide,” Qlik Enterprise Manager, Apr. 2020, Version 6.6, 368 pages. [cited by applicant]