Multi transaction control system with update access counter owned by the transaction process at the start point to keep transaction consistency

Abstract

To achieve a multi-transaction processing system which assumes real-time update having practical throughput being a requirement, in multi-transaction processing in which consistency should be maintained. An update access-counter technology is applied which assumes a time when a counter is returned to an initial value depending on the up-down counting of the counter identified by a process ID of a process that is a starting point of multi-transaction processing being the completion of one multi-transaction processing, thus solving the problem.

1 . The distributed multi transaction control system characterized in below
 located on the network, said distributed multi distributed transaction control system comprising:   one or more database object management apparatus/apparatuses managing database/databases;   and one or more database object storage apparatus/apparatuses corresponding to each said database object management apparatus/apparatuses in order to store database/databases managed by said database object management apparatus/apparatuses;   and distributed multi transaction processing apparatus/apparatuses for implementing and maintaining transaction consistency in distributed multi transaction processing;   and one or more database meta information management repository apparatus/apparatuses in order to manage meta information held by said database/databases;   said one or more database meta information management repository apparatus/apparatuses having:   update access counter/counters which is/are characterized to be identified by the process identifier which identifies the process which is the starting point of one or more said update access/accesses requested;   said distributed multi transaction processing apparatus/apparatuses has/have distributed multi transaction process executing portion characterized in below:   in transaction processing for database object/objects which is/are requested from client computer/computers or server computer/computers to access as one or more update process/processes such as insertion or modification or deletion directly or indirectly, and is/are managed by database object management apparatus/apparatuses,   herein said update access counter has initial value specified beforehand,   the count in said update access counter concerned which is identified by process identifier which identifies the process which is the starting point of said update access/accesses concerned is counted up by the constant number each time when update access/accesses is/are occurred requested by the process/processes or thread/threads on the client computer/computers or server computer/computers inside its/their own said database domain if said process/processes or thread/threads which is/are caused by the starting process itself or process/processes which is/are caused by the starting process, directly or indirectly exist/exists;   and the count in said update access counter which is identified by process identifier which identifies the process which is the starting point of said update access/accesses concerned is counted down by the constant number same as said constant number concerned each time when the information that actual update access succeeded reach to said distributed multi transaction processing apparatus/apparatuses;   and when the value of said counter concerned matches said initial value concerned, commit operation/operations is/are executed for all update access/accesses executed by the process/processes or thread/threads which is/are caused by the starting process itself or process/processes which is/are caused by the starting process directly or indirectly on the client computer/computers or server computer/computers inside its/their own database domain directly or indirectly;   and in case of that the information that actual update access failed reach to said distributed multi transaction processing apparatus/apparatuses, further update access/accesses is/are stopped, and without waiting for the result/results, rollback operation/operations for all update access/accesses executed already by the process/processes or thread/threads which is/are caused directly or indirectly by the starting process itself or process/processes or thread/threads if exists/exist on the client computer/computers or server computer/computers inside its/their own database domain is executed promptly.