The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Feb. 03, 2026
Filed:
Jan. 09, 2025
Gravic, Inc., Malvern, PA (US);
John R. Hoffmann, Kennett Square, PA (US);
Paul J. Holenstein, Downingtown, PA (US);
Bruce D. Holenstein, Media, PA (US);
Dylan R. Holenstein, Newtown Square, PA (US);
GRAVIC, INC., Malvern, PA (US);
Abstract
An automated method is provided for comparing a source database and a target database that are intended to be kept in synchronization with each other. An application processes transactions that are posted to the source database, and a synchronization process processes transactions that are posted to the target database. Change log data is chunked from a change log associated with the source database to create first chunks of change log data. Change log data is also chunked from a change log associated with the target database to create second chunks of change log data. A comparison engine compares representations of the first chunks of change log data with representations of the second chunks of change log data, wherein the second chunks of change log data correspond to the same respective first chunks of change log data that were made to the source database and kept in synchronization with the target database via the synchronization process. The source database and the target database are presumed to be in synchronization with each other via the synchronization process when the comparison indicates that the representations of the first chunks of change log data match the representations of the second chunks of change log data. The source database and the target database are presumed not to be in synchronization with each other when the comparison indicates that the representations of the first chunks of change log data do not match the representations of the second chunks of change log data. An action is performed when the comparison indicates that the representations of the first chunks of change log data do not match the representations of the second chunks of change log data. The action may be a corrective action that resynchronizes the target database with the source database, or that suspends or stops the application from processing transactions.