Browse Prior Art Database

Method for verifying integrity of database replications

IP.com Disclosure Number: IPCOM000247521D
Publication Date: 2016-Sep-14
Document File: 2 page(s) / 31K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a mechanism to verify the integrity of a DB (database) replication process, without stopping data updates in a non-stop database system. The system will reduce the workload at a lower cost, without installing any addtional integrity and verification products.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 2

Method for verifying integrity of database replications


1.Background.

In a large-scale system, to verify the data integrity between a source DB and a target DB, the DB replication process has become a major challenge. Although it may be possible to ensure the integrity of the collateral data by using the DB replication software product, the process for ensuring the replication should be verified in another way in a critical system such as the one that handles financial data, .

In addition, in order to verify the data integrity. it is possible to ensure the stationary point comparison by temporarily stopping the process of DB data updates. However, for keeping a 24/365 operation in a nonstop system, it can not ensure the quiescent point of such DB updates.


2.Requirements for DB data integrity verification.

(1) It does not stop the updates of DB (i.e. it cannot be assured of a rest point by the stop).

(2) In mass data processing, it is necessary to complete the integrity verification within a short period of time.

(3) Using the current state of the mechanism, it is realized by suppressing the system load.


3.Problems in a current solution.

To verify the integrity of DB replication processes, the following conventional methods are being provided.

(a) Compare by matching all replica records between source DB and target DB.

(b) Create a Update history DB including product logs separated to application DBs. The Update history is to make sure that the replication has been completed successfully.

(c) Create the Update history DBs in both the source and target DBs. They are compared by all records matching between the two DBs.

Each of the verification methods has the following problems.

For (a), in a system that handles data exceeding tens of thousands records, due to the high system workload, verification time takes so long and consistent deficiencies cannot be detected.

In (b), checking tampering updates in history records ensures normal pr...