METHOD FOR IDENTIFYING LOGICAL DATA DISCREPANCIES BETWEEN DATABASE REPLICAS IN A DATABASE CLUSTER

• US 20080140734A1
• Filed: 12/07/2007
• Published: 06/12/2008
• Est. Priority Date: 12/07/2006
• Status: Abandoned Application

• Current Assignee: Robert Edward Wagner
• Original Assignee: Robert Edward Wagner
• Inventors: Wagner, Robert Edward
• Application Number:
  US11/952,460
• Publication Number:
  US 20080140734A1
• Time in Patent Office: Days
• US Class Current: 707/202
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

A method and system for monitoring the consistency of replicated databases in a shared-nothing database cluster architecture is presented. The method involves the continuous monitoring of the database transaction logs that are maintained by the autonomous database managers that manage the individual database replicas in the cluster. In the event that data discrepancies are detected via the comparison of the transaction logs of the individual database replicas, remedial action is carried out according to configured rules in the main cluster controller. Additionally, if the database management system running within each node of the cluster possesses a database history file that records key events pertaining to a database replica, such as the occurrence of non-logged bulk loads of table data, or the modification of tables, a method can be instituted for the monitoring of the history files for discrepancies between the database replicas.

Claims

1. A system for monitoring data consistency comprising:

a plurality of database nodes each capable of operating independently, each containing at least one database;

a transaction log for recording each insertion, deletion or modification of data for each of the at least one databases in the database nodes;

a controller node in communication with the database nodes for receiving at least one database transaction request from at least one client node, the controller node sending all database transaction requests from at least one client nodes to all of the database nodes, and monitoring the results of each of the database transaction requests sent to the database nodes;

whereby the transaction logs of each of the database nodes which are determined by the controller node to have completed the same database transaction requests are compared to detect any inconsistency.

2. The system of claim 1 wherein upon detecting an inconsistency remedial action is taken.

3. The system of claim 2 wherein the remedial action comprises at least one of making at least one of the database nodes inactive and recording the inconsistency.

4. The system of claim 2 wherein the remedial action comprises alerting an operator of the inconsistency.

5. The system of claim 1 further comprising a standby controller node for replacing the controller node if the controller node is rendered inoperable.

6. The system of claim 2 wherein the inconsistencies upon which remedial action is taken is determined by the configuration of the system.

7. The system of claim 1 further comprising

at least one trigger associated with at least one of the databases in the database nodes triggered by content changes to the at least one of the databases;

where the transaction log for each of the at least one database in the database nodes is generated by the at least one trigger;

8. The system of claim 7 wherein the remedial action is at least one of making at least one database node inactive and recording the inconsistency.

9. The system of claim 7 wherein the remedial action comprises alerting an operator of the inconsistency.

10. The system of claim 7 further comprising a standby controller node for replacing the controller node if the controller node is rendered inoperable.

11. The system of claim 7 wherein the inconsistencies upon which remedial action is taken is determined by the configuration of the system.

12. A system for maintaining data consistency comprising:

a plurality of slave database nodes each capable of operating independently, each containing at least one database;

a master database node capable of operating independently, containing at least one database such that all changes to the at least one database are replicated to all of the at least one databases contained in the slave database nodes;

a transaction log for recording each insertion, deletion or modification of data for each of the at least one databases in the slave database nodes and the master database node;

a controller node in communication with the slave database nodes and the master database node for receiving at least one database transaction request from at least one client node, the controller node sending all database transaction requests from the at least one client node to the master database node, the master database node replicating all changes to all of the at least one slave database nodes, the controller node monitoring the results of each of the database transaction requests sent to the slave database nodes;

whereby the transaction logs of the master database node and each of the slave database nodes which are determined by the controller node to have completed the same database transaction request are compared to detect any inconsistency.

13. A method of monitoring consistency between a plurality of database nodes each containing at least one database, comprising the steps of:

receiving at least one database transaction request from at least one client node;

sending the at least one database transaction request from the at least one client node to all of the database nodes;

recording each insertion, deletion or modification of data for each of the least one databases in the database nodes in a transaction log;

monitoring the results of each of the database transaction requests sent to the database nodes; and

comparing the transaction logs of each of the database nodes which are determined to have completed the same database transaction requests

14. The method of claim 13 comprising, upon detecting an inconsistency, the step of taking remedial action.

15. The method of claim 14 wherein the remedial action comprises at least one of the steps of making at least one of the database nodes inactive and recording the inconsistency.

16. The method of claim 14 wherein the remedial action comprises the step of alerting an operator of the inconsistency.

17. A system for monitoring data consistency comprising:

a plurality of database nodes each capable of operating independently, each containing at least one database;

a controller node in communication with the database nodes for receiving at least one database transaction requests from at least one client node, the controller node sending all database transaction requests from at least one client nodes to all of the database nodes, and monitoring the results of each of the database transaction requests sent to the database nodes;

whereby the data changes induced by each of the database transaction requests at each of the database nodes are compared to detect any inconsistency.

18. The system of claim 17 wherein upon detecting an inconsistency remedial action taken.

19. The system of claim 18 wherein the remedial action comprises at least one of making at least one of the database nodes inactive, and recording the inconsistency.

20. The system of claim 18 wherein the remedial action comprises alerting an operator of the inconsistency.

21. A method of maintaining consistency between a plurality of database nodes each containing at least one database comprising the steps of:

receiving at least one database transaction request from at least one client node;

sending the at least one database transaction request from the at least one client node to all of the database nodes;

monitoring the results of each of the database transaction requests sent to the database nodes and obtaining information on all data changes induced by the database transaction request; and

comparing the data changes induced at each of the database nodes which are determined to have completed the same database transaction request.

22. The method of claim 21 comprising, upon detecting an inconsistency, the step of taking remedial action.

23. The method of claim 22 wherein the remedial action comprises at least one of the step of making at least one of the database nodes inactive and recording the inconsistency.

24. The method of claim 22 wherein the remedial action comprises the step of alerting an operator of the inconsistency.