US5884327A
Expired / Lapsed
US
⏱️ 0.0 years remaining
System, method and program for performing two-phase commit with a coordinator that performs no logging
Assignee: International Business Machines Corp
•
Filing: 1996-09-25
•
Granted: 1999-03-16
•
Expires: 2016-09-25
Abstract
Abstract The system, method, and program of this invention allows a two-phase commit protocol to work properly, even when the client acting as the coordinator does not have a log to record two-phase state information. In a preferred embodiment, the client in a client/server distributed transaction processing system is a personal computer. The client, without a recovery log, acts as a coordinator of a commit process. The coordinator migrates, i.e., passes, responsibility for resynchronization, and any associated logging requirement, to a server, e.g., to any of the connected relational database management system (RDBMS) servers, which is a participant in the transaction. The server uses its own recovery log for use in satisfying the logging requirement.
Inventors
- 👤 Curt Lee Cotner
- 👤 Richard Anthony Crus
- 👤 Brian Keith Howell
- 👤 James Willis Pickel
- 👤 David Joseph Wisneski
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-31 21:26
CPC Classifications
G; G06; G06F; G06F16/00; G06F16/20; G06F16/23; G06F16/2379; Y; Y10; Y10S; Y10S707/00; Y10S707/99931; Y10S707/99938; Y10S707/99951; Y10S707/99952; Y10S707/99953
Claims Analysis
Total Claims: 66
Claim 1
Independent Claim
87 words
A method of performing a two phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the method comprising: coordinating the two-phase commit procedure, at the coordinator, independently of a logging step required to guarantee the outcome of a unit of work, including when at least one participant of the plurality of DBMS's votes to commit; and migrating resynchronization responsibilities for the two-phase commit procedure from the coordinator to a DBMS selected as a resync server.
Claim 2
Independent Claim
87 words
A method of performing a two phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the method comprising: coordinating the two-phase commit procedure, at the coordinator, independently of a logging step required to guarantee the outcome of a unit of work, including when at least one participant of the plurality of DBMS's votes to commit; and migrating resynchronization responsibilities for the two-phase commit procedure from the coordinator to a DBMS selected as a resync server.
Claim 3
Dependent Claim
23 words
The method of claim 1 further comprising the step of performing a logging step, during the two-phase commit procedure, at the resync server.
Claim 4
Independent Claim
137 words
A method of performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the method comprising: selecting, by the coordinator, a DBMS server as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; initiating, by the coordinator, the two-phase commit procedure by sending a "prepare to commit" message to each DBMS participating in the transaction as a participant except the resync server; coordinating the two-phase commit procedure, at the coordinator, independently of a logging step required to guarantee the outcome of a unit of work, including when at least one participant of the plurality of DBMS's votes to commit; and sending, by the coordinator, an outcome message to the resync server after receiving votes from each participant.
Claim 5
Independent Claim
137 words
A method of performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the method comprising: selecting, by the coordinator, a DBMS server as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; initiating, by the coordinator, the two-phase commit procedure by sending a "prepare to commit" message to each DBMS participating in the transaction as a participant except the resync server; coordinating the two-phase commit procedure, at the coordinator, independently of a logging step required to guarantee the outcome of a unit of work, including when at least one participant of the plurality of DBMS's votes to commit; and sending, by the coordinator, an outcome message to the resync server after receiving votes from each participant.
Claim 6
Dependent Claim
23 words
The method of claim 3 further comprising receiving a "migrated resync" message from the resync server after the resync server has been selected.
Claim 7
Dependent Claim
41 words
The method of claim 3 further comprising rolling back and forgetting a unit of work if a failure occurs during a transmission of a "migrated resync" message from the resync server to the coordinator after the resync server has been selected.
Claim 8
Dependent Claim
19 words
The method of claim 3 wherein the "prepare to commit" message includes a network address of the resync server.
Claim 9
Dependent Claim
29 words
The method of claim 3 wherein the outcome message sent to the resync server is a "commit" message with a list of all participants that voted "request to commit".
Claim 10
Dependent Claim
30 words
The method of claim 7 further comprising force-writing, by the resync server, a "commit" log record with the list of participants and sending a "committed" reply message to the coordinator.
Claim 11
Dependent Claim
74 words
The method of claim 8 further comprising reading, by the resync server, one or more commit log records if a failure occurs between the coordinator and the resync server after the "committed" reply message is sent to the coordinator from the resync server; and periodically attempting to resynchronize, by the resync server, with each participant voting to commit after recovering from the failure and determining all "commits" from reading the "commit " log records.
Claim 12
Dependent Claim
34 words
The method of claim 9 further comprising writing, by the resync server, a non-forced "forget" log record after resynchronization is complete with each participant; and forgetting, by the resync server, the unit of work.
Claim 13
Dependent Claim
26 words
The method of claim 8 further comprising sending, by the coordinator to each participant, except the resync server, that returned a non-read-only vote, a "committed" message.
Claim 14
Dependent Claim
39 words
The method of claim 11 further comprising force-writing, by each participant that received the "committed" message, a "commit" log record; sending to the coordinator a message indicating forget; committing the unit of work; and forgetting the unit of work.
Claim 15
Dependent Claim
15 words
The method of claim 12 wherein the message indicating forget is an explicit "forget" message.
Claim 16
Dependent Claim
30 words
The method of claim 12 wherein the message indicating forget is an implicit "forget" message where a next reply message from a corresponding participant to the coordinator implies a forget.
Claim 17
Dependent Claim
33 words
The method of claim 12 further comprising sending a "forget" message from the coordinator to the resync server after a message indicating forget is received from each participant that received the "committed" message.
Claim 18
Dependent Claim
23 words
The method of claim 15 further comprising writing, by the resync server, a non-forced "forget" log record; and forgetting the unit of work.
Claim 19
Dependent Claim
13 words
The method of claim 3 wherein the outcome message is a "rollback" message.
Claim 20
Dependent Claim
18 words
The method of claim 17 wherein the "rollback" message is sent to each participant voting "request to commit."
Claim 21
Dependent Claim
33 words
The method of claim 18 further comprising writing, by each participant that received the "rollback" message, a non-forced "rollback" log record; rolling back the unit of work; and forgetting the unit of work.
Claim 22
Dependent Claim
25 words
The method of claim 17 further comprising writing, by the resync server, a non-forced "rollback" log record after receiving the "rollback" message from the coordinator.
Claim 23
Dependent Claim
21 words
The method of claim 3 wherein the outcome message is a "request to commit" message if each participant voted to forget.
Claim 24
Dependent Claim
25 words
The method of claim 21 wherein each participant is read-only and does not participate with the coordinator during a second phase of the commit procedure.
Claim 25
Dependent Claim
55 words
The method of claim 21 further comprising writing, by the resync server, a "forget" log record after receiving the "request to commit" message from the coordinator if the resync server performed any updates; and sending to the coordinator from the resync server a "forget" reply message if the resync server performed updates or performed read-only.
Claim 26
Dependent Claim
46 words
The method of claim 3 wherein the outcome message is a "request to commit" message with a list of each participant voting to commit if at least one participant voted to commit and no participant voted to rollback and each previous communication was free of error.
Claim 27
Dependent Claim
31 words
The method of claim 3 wherein the outcome message is a "rollback" message if any participant voted to rollback or a communication error occurred while sending the "prepare to commit" message.
Claim 28
Independent Claim
108 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction as participants; the system comprising: the coordinator having means for coordinating the commit procedure independently of a logging function required to guarantee the outcome of a unit of work, including when at least one participant of the plurality of DBMS's votes to commit; and a DBMS server, communicatively connected to the coordinator and each participant, and designated as a resync server by the coordinator, for performing a logging function during the commit procedure and for performing resynchronization if the commit procedure fails.
Claim 29
Independent Claim
108 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction as participants; the system comprising: the coordinator having means for coordinating the commit procedure independently of a logging function required to guarantee the outcome of a unit of work, including when at least one participant of the plurality of DBMS's votes to commit; and a DBMS server, communicatively connected to the coordinator and each participant, and designated as a resync server by the coordinator, for performing a logging function during the commit procedure and for performing resynchronization if the commit procedure fails.
Claim 30
Independent Claim
206 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the system comprising: means for selecting, by the coordinator, a DBMS server as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; means for initiating, by the coordinator, the two-phase commit procedure by sending a "prepare to commit" message to each DBMS participating in the transaction as a participant except the resync server; means for coordinating the two-phase commit procedure, at the coordinator, independently of a logging function required to guarantee the outcome of a unit of work, including when at least one participant of the plurality of DBMS's votes to commit; means for sending, by the coordinator, a "request to commit" message to the resync server after receiving votes from each participant if at least one participant voted to commit and no participant voted to rollback; means for receiving, by the coordinator from the resync server, a "commit" message; means for sending, by the coordinator to each participant, except the resync server, that returned a non-read-only vote, a "committed" decision message; and means for sending a "forget" message to the resync server.
Claim 31
Independent Claim
206 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the system comprising: means for selecting, by the coordinator, a DBMS server as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; means for initiating, by the coordinator, the two-phase commit procedure by sending a "prepare to commit" message to each DBMS participating in the transaction as a participant except the resync server; means for coordinating the two-phase commit procedure, at the coordinator, independently of a logging function required to guarantee the outcome of a unit of work, including when at least one participant of the plurality of DBMS's votes to commit; means for sending, by the coordinator, a "request to commit" message to the resync server after receiving votes from each participant if at least one participant voted to commit and no participant voted to rollback; means for receiving, by the coordinator from the resync server, a "commit" message; means for sending, by the coordinator to each participant, except the resync server, that returned a non-read-only vote, a "committed" decision message; and means for sending a "forget" message to the resync server.
Claim 32
Dependent Claim
19 words
The system of claim 27 wherein the "prepare to commit" message includes a network address of the resync server.
Claim 33
Dependent Claim
37 words
The system of claim 27 further comprising means for writing a non-forced "forget" log record and means for forgetting the unit of work, by the resync server, after the "forget" message is sent to the resync server.
Claim 34
Dependent Claim
20 words
The system of claim 27 wherein the "request to commit" message includes a list of each participant voting to commit.
Claim 35
Dependent Claim
30 words
The system of claim 27 further comprising means for force-writing, by the resync server, a "commit" log record with the list of participants after receiving the "request to commit" message.
Claim 36
Dependent Claim
38 words
The system of claim 31 further comprising means for force-writing, by each participant that received the "committed" decision message, a "commit" log record; means for committing the unit of work; and means for forgetting the unit of work.
Claim 37
Independent Claim
187 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the system comprising: means for selecting, by the coordinator, a DBMS server as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; means for initiating, by the coordinator, the two-phase commit procedure by sending a "prepare to commit" message to each DBMS participating in the transaction as a participant, except the resync server; means for coordinating the two-phase commit procedure, at the coordinator, independently of a logging function required to guarantee the outcome of a unit of works including when at least one participant of the plurality of DBMS's votes to commit; means for sending, by the coordinator, a "rollback" message to the resync server after receiving votes from each participant and at least one participant voted to rollback or a communication error occurred while sending the "prepare to commit" message; and means for sending, by the coordinator to each participant, except the resync server, that returned a non-read-only vote, a "rollback" decision message.
Claim 38
Independent Claim
187 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the system comprising: means for selecting, by the coordinator, a DBMS server as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; means for initiating, by the coordinator, the two-phase commit procedure by sending a "prepare to commit" message to each DBMS participating in the transaction as a participant, except the resync server; means for coordinating the two-phase commit procedure, at the coordinator, independently of a logging function required to guarantee the outcome of a unit of works including when at least one participant of the plurality of DBMS's votes to commit; means for sending, by the coordinator, a "rollback" message to the resync server after receiving votes from each participant and at least one participant voted to rollback or a communication error occurred while sending the "prepare to commit" message; and means for sending, by the coordinator to each participant, except the resync server, that returned a non-read-only vote, a "rollback" decision message.
Claim 39
Dependent Claim
27 words
The system of claim 33 further comprising means for writing, by the resync server, a non-forced "rollback" log record after receiving the "rollback" message from the coordinator.
Claim 40
Dependent Claim
40 words
The method of claim 33 further comprising means for writing, by each participant that received the "rollback" decision message, a non-forced "rollback" log record; means for rolling back the unit of work; and means for forgetting the unit of work.
Claim 41
Independent Claim
81 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction as participants; the system comprising: a "migrate resynchronization" message, from the coordinator to a DBMS server selected as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; and a "prepare to commit" message, sent from the coordinator to each participant, including a network address of the resync server.
Claim 42
Independent Claim
81 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction as participants; the system comprising: a "migrate resynchronization" message, from the coordinator to a DBMS server selected as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; and a "prepare to commit" message, sent from the coordinator to each participant, including a network address of the resync server.
Claim 43
Dependent Claim
29 words
The system of claim 36 further comprising a "request to commit" message, sent from the coordinator to the resync server, having a list of each participant voting to commit.
Claim 44
Independent Claim
99 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the system comprising: a message request, received in a DBMS server selected as a resync server from the coordinator, to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; a "request to commit" message, received at the resync server from the coordinator, having a list of each participant voting to commit; and means for force-writing a "commit" log record, at the resync server, after receiving the "request to commit" message.
Claim 45
Independent Claim
99 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the system comprising: a message request, received in a DBMS server selected as a resync server from the coordinator, to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; a "request to commit" message, received at the resync server from the coordinator, having a list of each participant voting to commit; and means for force-writing a "commit" log record, at the resync server, after receiving the "request to commit" message.
Claim 46
Dependent Claim
77 words
The system of claim 38 further comprising means for reading, by the resync server, one or more commit log records if a failure occurs between the coordinator and the resync server after a "committed" reply message is sent to the coordinator from the resync server; and means for periodically attempting to resynchronize, by the resync server, with each participant voting to commit after recovering from the failure and determining all "commits" from reading the commit log records.
Claim 47
Dependent Claim
36 words
The system of claim 39 further comprising means for writing, by the resync server, a non-forced "forget" log record after resynchronization is complete with each participant; and forgetting, by the resync server, the unit of work.
Claim 48
Independent Claim
82 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the system comprising: a message request, received at a DBMS server selected as a resync server from the coordinator, to perform resynchronization on behalf of the coordinator; a "rollback" message, received at the resync server from the coordinator; and means for writing a non-forced "rollback" log record, at the resync server, after receiving the "rollback" message.
Claim 49
Independent Claim
82 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the system comprising: a message request, received at a DBMS server selected as a resync server from the coordinator, to perform resynchronization on behalf of the coordinator; a "rollback" message, received at the resync server from the coordinator; and means for writing a non-forced "rollback" log record, at the resync server, after receiving the "rollback" message.
Claim 50
Dependent Claim
100 words
A program on a computer medium for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the program comprising: means for causing a coordination of the two-phase commit procedure, at the coordinator, independently of a logging function required to guarantee the outcome of a unit of work, including when a "request to commit" message is to be sent from the coordinator; and means for causing a migration of resynchronization responsibilities for the two-phase commit procedure from the coordinator to a DBMS selected as a resync server.
Claim 51
Dependent Claim
100 words
A program on a computer medium for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the program comprising: means for causing a coordination of the two-phase commit procedure, at the coordinator, independently of a logging function required to guarantee the outcome of a unit of work, including when a "request to commit" message is to be sent from the coordinator; and means for causing a migration of resynchronization responsibilities for the two-phase commit procedure from the coordinator to a DBMS selected as a resync server.
Claim 52
Dependent Claim
132 words
A program on a computer usable medium for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction as participants, the program comprising: means for causing a selection, by the coordinator, of a DBMS server as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; means for causing a coordination of the two-phase commit procedure, at the coordinator, independently of a logging function required to guarantee the outcome of a unit of works including when a "request to commit" message is to be sent from the coordinator; means for causing a "prepare to commit" message, including a network address of the resync server, to be sent from the coordinator to each participant.
Claim 53
Dependent Claim
132 words
A program on a computer usable medium for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction as participants, the program comprising: means for causing a selection, by the coordinator, of a DBMS server as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; means for causing a coordination of the two-phase commit procedure, at the coordinator, independently of a logging function required to guarantee the outcome of a unit of works including when a "request to commit" message is to be sent from the coordinator; means for causing a "prepare to commit" message, including a network address of the resync server, to be sent from the coordinator to each participant.
Claim 54
Dependent Claim
39 words
A program on a computer usable medium of claim 43 further comprising means for causing a "request to commit" message, to be sent from the coordinator to the resync server, having a list of each participant voting to commit.
Claim 55
Dependent Claim
108 words
A program on a computer usable medium for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction as participants; the program comprising: means for receiving a message request, at a DBMS server selected as a resync server from the coordinator, to perform resynchronization on behalf of the coordinator; means for receiving a "request to commit" message, at the resync server from the coordinator, having a list of each participant voting to commit; and means for causing a "commit" log record to be force-written, at the resync server, after receiving the "request to commit" message.
Claim 56
Dependent Claim
108 words
A program on a computer usable medium for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction as participants; the program comprising: means for receiving a message request, at a DBMS server selected as a resync server from the coordinator, to perform resynchronization on behalf of the coordinator; means for receiving a "request to commit" message, at the resync server from the coordinator, having a list of each participant voting to commit; and means for causing a "commit" log record to be force-written, at the resync server, after receiving the "request to commit" message.
Claim 57
Dependent Claim
87 words
The program on a computer usable medium of claim 45 further comprising means for causing a reading of, by the resync server, one or more "commit" log records if a failure occurs between the coordinator and the resync server after a "committed" reply message is sent to the coordinator from the resync server; and means for causing a periodic attempt to resynchronize, by the resync server, with each participant voting to commit after recovering from the failure and determining all "commits" from reading the "commit" log records.
Claim 58
Dependent Claim
46 words
The program on a computer usable medium of claim 46 further comprising means for causing, by the resync server, a non-forced "forget" log record to be written after resynchronization is complete with each participant; and means for forgetting, by the resync server, the unit of work.
Claim 59
Dependent Claim
94 words
A program on a computer usable medium for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the program comprising: means for receiving a message request, at a DBMS server selected as a resync server from the coordinator, to perform resynchronization on behalf of the coordinator; means for receiving a "rollback" message, at the resync server, from the coordinator; and means for causing a non-forced "rollback" log record to be written, at the resync server, after receiving the "rollback" message.
Claim 60
Dependent Claim
94 words
A program on a computer usable medium for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the program comprising: means for receiving a message request, at a DBMS server selected as a resync server from the coordinator, to perform resynchronization on behalf of the coordinator; means for receiving a "rollback" message, at the resync server, from the coordinator; and means for causing a non-forced "rollback" log record to be written, at the resync server, after receiving the "rollback" message.
Claim 61
Independent Claim
131 words
A method of performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the method comprising: selecting, by the coordinator, one of the plurality of DBMS's as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; initiating, by the coordinator, the two-phase commit procedure by sending a "prepare to commit" message with a network address of the resync server to each of the DBMS's participating in the transaction participant except the resync server; and coordinating the two-phase commit procedure, at the coordinator, independently of a logging step required to guarantee the outcome of a unit of work, including when a "request to commit" message is to be sent from the coordinator.
Claim 62
Independent Claim
131 words
A method of performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the method comprising: selecting, by the coordinator, one of the plurality of DBMS's as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; initiating, by the coordinator, the two-phase commit procedure by sending a "prepare to commit" message with a network address of the resync server to each of the DBMS's participating in the transaction participant except the resync server; and coordinating the two-phase commit procedure, at the coordinator, independently of a logging step required to guarantee the outcome of a unit of work, including when a "request to commit" message is to be sent from the coordinator.
Claim 63
Independent Claim
137 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the system comprising: means for selecting by the coordinator, one of the plurality of DBMS's as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; means for initiating, by the coordinator, the two-phase commit procedure by sending a "prepare to commit" message with a network address of the resync server to each of the DBMS participating in the transaction participant except the resync server; and means for coordinating the two-phase commit procedure, at the coordinator, independently of a logging function required to guarantee the outcome of a unit of works including when a "request to commit" message is to be sent from the coordinator.
Claim 64
Independent Claim
137 words
A system for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction; the system comprising: means for selecting by the coordinator, one of the plurality of DBMS's as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; means for initiating, by the coordinator, the two-phase commit procedure by sending a "prepare to commit" message with a network address of the resync server to each of the DBMS participating in the transaction participant except the resync server; and means for coordinating the two-phase commit procedure, at the coordinator, independently of a logging function required to guarantee the outcome of a unit of works including when a "request to commit" message is to be sent from the coordinator.
Claim 65
Dependent Claim
153 words
A program on a computer usable medium for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction, the program comprising: means for causing a selection of, by the coordinator, one of the plurality of DBMS's as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; means for causing an initiation of, by the coordinator, the two-phase commit procedure by a sending of a "prepare to commit" message with a network address of the resync server to each of the DBMS's participating in the transaction participant except the resync server; and means for causing a coordination of the two-phase commit procedure, at the coordinator, independently of a logging function required to guarantee the outcome of a unit of work, including when at least one participant of the plurality of DBMS's votes to commit.
Claim 66
Dependent Claim
153 words
A program on a computer usable medium for performing a two-phase commit procedure for a transaction between a coordinator and a plurality of database management systems (DBMS's) participating in the transaction, the program comprising: means for causing a selection of, by the coordinator, one of the plurality of DBMS's as a resync server to perform resynchronization for the two-phase commit procedure on behalf of the coordinator; means for causing an initiation of, by the coordinator, the two-phase commit procedure by a sending of a "prepare to commit" message with a network address of the resync server to each of the DBMS's participating in the transaction participant except the resync server; and means for causing a coordination of the two-phase commit procedure, at the coordinator, independently of a logging function required to guarantee the outcome of a unit of work, including when at least one participant of the plurality of DBMS's votes to commit.
References Cited (Backward Citations)
US4648031A
Cited
US4819159A
Cited
US5586329A
Cited
US5327532A
Cited
US5371886A
Cited
US5586312A
Cited
US5625811A
Cited
US5594329A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2002-03-15 | 2002-09-14 | 2003-03-16 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2006-03-15 | 2006-09-14 | 2007-03-16 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2010-03-15 | 2010-09-14 | 2011-03-16 | $7700.00 | Window Closed / Lapsed |