Method of detecting write conflicts in replicated databases without memory overhead

• US 20020042910A1
• Filed: 09/24/2001
• Published: 04/11/2002
• Est. Priority Date: 09/23/2000
• Status: Abandoned Application

• Current Assignee: Koninklijke Philips Electronics N.V. (Koninklijke Philips N.V.)
• Original Assignee: Koninklijke Philips Electronics N.V. (Koninklijke Philips N.V.)
• Inventors: Baumeister, Markus, Klabunde, Karin, Hauptmann, Steffen
• Application Number:
  US09/961,956
• Publication Number:
  US 20020042910A1
• Time in Patent Office: Days
• US Class Current: 717/172
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

The invention relates to a network comprising network nodes (1 to 3) and to a software system distributed over all the network nodes which comprises a database management system (7 to 9) which is provided for calculating a characterizing unit of the data object when a user, referred to as a client (10 to 12), of the database management system (7 to 9) accesses a data object, and the characterizing unit is provided for being transferred to the client (10 to 12) and the client (10 to 12) is provided for storing the characterizing unit.

Claims

1. A network comprising network nodes (1 to 3) and a software system distributed over all the network nodes, which software system comprises a database management system (7 to 9) which is provided for calculating a characterizing unit of the data object when a user referred to as a client (10 to 12) accesses a data object of the database management system (7 to 9), and the characterizing unit is provided for being transferred to the client (10 to 12) and the client (10 to 12) is provided for storing the characterizing unit.

2. A network as claimed in claim 1, characterized in that the database management system (7 to 9) is provided for comparing the characterizing unit stored at the client (10 to 12) with the actual characterizing unit, in that the database management system (7 to 9) is provided for executing the write access if the characterizing units match, and in that the database management system (7 to 9) is provided for executing alternative actions if the characterizing units do not match.

3. A network as claimed in claim 2, characterized in that the remote database management system (7 to 9) receives a change indication and a characterizing unit in a respective joint message when there is a distributed write operation.