Fast intersystem page transfer in a data sharing environment with record locking

• US 5,327,556 A
• Filed: 05/11/1993
• Issued: 07/05/1994
• Est. Priority Date: 02/15/1991
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Narang, Inderpal S., Mohan, Chandrasekaran
• Primary Examiner(s): Ray, Gopal C.
• Application Number:
  US08/059,734
• Time in Patent Office: 420 Days
• Field of Search: 395/600, 395/425, 395/725, 395/200, 395/700, 371/10.1
• US Class Current: 707/695
• CPC Class Codes: G06F 12/0815 Cache consistency protocols
• CPC Class Codes: G06F 16/1774 Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files
• CPC Class Codes: Y10S 707/922 Communications
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99939 Privileged access
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A fast technique for transferring units of data between transaction systems in a shared disk environment. The owning system, having updated the page, generates a version number for the page which is stored with a lock possessed by the owning system. When a requesting system seeks a record on the page, its request for a lock illicit an indication that a more recent version of the page is required in the local memory. The buffer management component of a DBMS, with assistance from the lock management, triggers a memory to memory transfer of the page from the owning DBMS to the requesting DBMS using a low overhead communication protocol. The transfer of page is without disk I/O or the log I/O for the updates made to the page.

Claims

1. In a system for sharing access to data among a plurality of database management systems (DBMS'"'"'s) by issuing locks to processes executing in the DBMS'"'"'s, the data being held in units of transfer ("data units") in DBMS buffers or being copied to the DBMS buffers from one or more disks to which all of the DBMS'"'"'s are coupled, the locks being issued and managed by a global lock manager to which each of the DBMS'"'"'s is coupled by a respective communications link, the locks including P locks on data units and L locks on records in the data units, the system including means for coupling each DBMS to all other DBMS'"'"'s for transferring data, a method for providing fast access to data units, the method comprising the steps of:

maintaining a global lock table at the global lock manager, the global lock table including one or more entries, each entry corresponding to a lock granted to a DBMS;

issuing a P lock for updating a data unit to a first DBMS;

entering an entry for the P lock in the global lock table;

providing a first version of the data unit from a disk to a buffer of the first DBMS;

generating an updated version of the data unit in the buffer by updating the first version of the data unit at the first DBMS;

in response to updating the first version of the data unit;

generating a version number for the updated version of the data unit in the buffer of the first DBMS, the version number being a monotonically increasing number;

attaching the version number to the updated version of the data unit in the buffer of the first DBMS; and

storing the version number in the entry for the P lock in the global lock table;

issuing a request from a second DBMS for an L lock to read a record in the data unit;

in response to the request for the L lock, providing the second DBMS with the version number stored in the global lock table and granting the L lock;

if a buffer version of the data unit is in a buffer of the second DBMS, comparing the version number in the buffer version of the data unit with the version number from the global lock table and requesting the data unit from the global lock manager if the version number in the buffer version of the data unit is less than the version number from the global lock table;

otherwise,

if no version of the data unit is in a buffer of the second DBMS, issuing a request from the second DBMS for a P lock to read the data unit;

providing a request from the global lock manager to the first DBMS to transfer the data unit to the second DBMS in response to the P lock request;

transferring the updated version of the data unit from the first DBMS to the second DBMS and providing the version number of the updated version of the data unit from the first DBMS to the global lock manager;

forwarding the version number received from the first DBMS by the global lock manager to the second DBMS;

if the version number provided to the second DBMS is greater than the version number in the updated version of the data unit received by the second DBMS or if the updated version of the data unit has not been received at the second DBMS when the version number arrives, writing the updated version of the data unit to a disk from the first DBMS, providing the updated version of the data unit to the second DBMS from the disk and reading the record;

otherwise,

reading the record from the updated version of the data unit transferred to the second DBMS from the first DBMS.

2. The method of claim 1, wherein the system further includes a plurality of transaction logs, each transaction log coupled to a respective DBMS for storage of log data, each version number including a log sequence number (LSN) corresponding to an entry in a transaction log coupled to a DBMS recording updating of a data unit.

3. The method of claim 2, further including the steps of:

maintaining recovery version numbers for a plurality of data units in the global lock table, each recovery version number including a log sequence number representing a first update to a data unit following providing the data unit from a disk to a DBMS;

detecting failure of an owning DBMS holding a P lock to update a data unit before the data unit is written to disk; and

at a requesting DBMS, recovering the data unit by obtaining the recovery version number for the data unit from the global lock table, obtaining from the transaction log of the updating DBMS updating log entries for the data unit having LSN'"'"'s equal to or greater than the recovery version number of the data unit, and applying the update log entries to the data unit in version number sequence.

4. In a system for sharing access to data among a plurality of database management systems (DBMS'"'"'s) by issuing locks to processes executing in the DBMS'"'"'s, the data being held in units of transfer ("data units") in DBMS buffers or being copied to the DBMS buffers from one or more disks to which all of the DBMS'"'"'s are coupled, the locks being issued and managed by a global lock manager to which each of the DBMS'"'"'s is coupled by a respective communications link, the locks including P locks on data units and L locks on records in the data units, the system including means for coupling each DBMS to all other DBMS'"'"'s for transferring data, a method for providing fast access to data units, the method comprising the steps of:

maintaining a global lock table at the global lock manager, the global lock table including one or more entries, each entry corresponding to a lock granted to a DBMS;

issuing a P lock for updating a data unit to a first DBMS;

entering an entry for the P lock in the global lock table;

providing a first version of the data unit from a disk to a buffer of the first DBMS;

generating an updated version of the data unit in the buffer by updating the first version of the data unit at the first DBMS;

in response to updating the first version of the data unit;

generating a version number for the updated version of the data unit at the first DBMS, the version number being a monotonically increasing number;

attaching the version number to the updated version of the data unit in the buffer of the first DBMS; and

storing the version number in the entry for the P lock in the global lock table;

issuing a request from a second DBMS to the global lock manager for an L lock to update a record in the data unit;

granting the L lock on the record to the second DBMS;

issuing P lock request to update the data unit by the second DBMS;

providing a request from the global lock manager to the first DBMS to transfer the data unit to the second DBMS in response to the request from the second DBMS for the P lock on the data unit;

transferring the updated version of the data unit from the first DBMS to the second DBMS and providing the version number of the updated version of the data unit to the global lock manager from the first DBMS;

writing the updated version of the data unit to a disk from the first DBMS in response to the request for the P lock from the second DBMS and releasing the P lock held by the first DBMS;

providing the version number from the global lock manager to the second DBMS;

if the version number provided to the second DBMS is greater than the version number in the updated version of the data unit received by the second DBMS from the first DBMS, or if the updated version of the data unit has not been received at the second DBMS, providing the updated version of the data unit to the second DBMS from the disk and updating the record;

otherwise,

updating the record in the updated version of the data unit transferred to the second DBMS from the first DBMS.

5. The method of claim 4, wherein the system further includes a plurality of transaction logs, each transaction log coupled to a respective DBMS for storage of log data, any version number including a log sequence number (LSN) corresponding to an entry in a transaction log coupled to a DBMS recording updating of a data unit.

6. The method of claim 5, further including the steps of:

maintaining recovery version numbers in each entry in the global lock table, each recovery version number including a LSN representing a first update to a data unit following providing the data unit from a disk to a DBMS;

detecting failure of an owning DBMS holding a P lock to update a data unit before the data unit is written to disk; and

at a recovering DBMS, recovering the data unit by obtaining the recovery version number for the data unit from the global lock table, obtaining from all transaction logs updating log entries for the data unit having LSN'"'"'s equal to or greater than the recovery version number of the data unit, and applying the updating log entries to the data unit in version number sequence.

7. In a system for sharing access to data among a plurality of database management systems (DBMS'"'"'s) by issuing locks to processes executing in the DBMS'"'"'s, the data being held in units of transfer ("data units") in DBMS buffers or being copied to the DBMS buffers from one or more disks to which all of the DBMS'"'"'s are coupled, the locks being issued and managed by a global lock manager to which each of the DBMS'"'"'s is coupled by a respective communications link, the locks including P locks on data units and L locks on records in the data units, the system including means for coupling each DBMS to all other DBMS'"'"'s for transferring data, a method for providing fast access to data units, the method comprising the steps of:

maintaining a global lock table at the global lock manager, the global lock table including one or more entries, each entry corresponding to a lock granted to a DBMS;

issuing a P lock for updating a data unit to a first DBMS;

entering an entry for the P lock in the global lock table;

providing a first version of the data unit from a disk to a buffer of the first DBMS;

generating an updated version of the data unit in the buffer by updating the first version of the data unit at the first DBMS;

in response to updating the first version of the data unit;

generating a version number for the updated version of the data unit at the first DBMS, the version number being a monotonically increasing number;

attaching the version number to the updated version of the data unit in the buffer of the first DBMS; and

storing the version number in the entry for the P lock in the global lock table;

issuing a request from a second DBMS to the global lock manager for an L lock to update a record in the data unit;

granting the L lock on the record to the second DBMS;

issuing a P lock request to update the data unit by the second DBMS;

providing a request from the global lock manager to the first DBMS to transfer the data unit to the second DBMS in response to the request from the second DBMS for the P lock on the data unit;

transferring the updated version of the data unit from the first DBMS to the second DBMS without writing the updated version of the data unit to disk and providing the version number of the updated version of the data unit to the global lock manager from the first DBMS;

releasing the P lock held by the first DBMS;

providing the version number from the global lock manager to the second DBMS;

if the version number provided to the second DBMS is greater than the version number in the updated version of the data unit received by the second DBMS from the first DBMS, or if the updated version of the data unit is not received by the second DBMS, providing a disk version of the data unit to the second DBMS from the disk, recovering the disk version of the data unit to the updated version of the data unit at the second DBMS and updating the record;

otherwise,

updating the record in the updated version of the data unit transferred to the second DBMS from the first DBMS.

8. The method of claim 8, wherein the system further includes a plurality of transaction logs, each transaction log coupled to a respective DBMS for storage of log data, any version number including a log sequence number (LSN) corresponding to an entry in a transaction log coupled to a DBMS recording updating of a data unit.

9. The method of claim 8, further including the steps of:

maintaining a recovery version number in each entry for a plurality of data units in the global lock table, each recovery version number including a LSN representing a first update to a data unit following providing the data unit from a disk to a DBMS;

detecting a failure of an owning DBMS holding update locks on one or more data units before the data units are written to disk; and

at a recovering DBMS, recovering each data unit of the one or more data units by obtaining the recovery version number for the data unit from the global lock table, obtaining from all transaction logs updating log entries for the data unit having LSN'"'"'s equal to or greater than the recovery version number of the data unit, and applying the updating log entries to the data unit in version number sequence.

10. The method of claim 9, wherein the step of transferring the updated data unit is further without ensuring the writing log records of the step of generating an updated data unit, the method further including the steps of:

maintaining the recovery version number in each entry in the global lock table, each recovery version number including a LSN representing a first update to a data unit following providing the data unit from a disk to a DBMS;

the step of recovering the data unit including forcing any unlogged log entries held by an DBMS into the transaction log for the DBMS, obtaining the recovery version number for the data unit from the global lock table, obtaining from all transaction logs updating log entries for the data unit having LSN'"'"'s equal to or greater than the recovery version number of the data unit, and applying the updating log entries to the data unit in version number sequence.

11. The method of claim 10, further including the steps of:

detecting a failure of an owning DBMS holding update locks on one or more data units before the data units are written to disk; and

at a recovering DBMS, recovering each data unit of one or more data units by forcing any unlogged log entries held by any operating DBMS for updates to the data unit into the transaction log for the operating DBMS, obtaining the recovery version number of the data unit from the global lock table, obtaining from all logs updating log entries for the data unit having LSN'"'"'s equal to or greater than the recovery version number of the data unit, and applying the updating log entries to the data unit in version number sequence.

12. The method of claims 9 and 11, further including:

maintaining a global lock table log;

periodically logging the contents of the global lock table into the global lock table log;

detecting a failure in the system;

recovering from the system failure by;

establishing a lowest recovery version number from all version numbers in the global lock table at the time of the system failure;

creating a merged log by merging the contents of all transaction logs from the lowest recovery version number at the end of each log in time-ordered sequence; and

recovering each data unit represented in the merged log by obtaining the data unit from the disk and applying the log records for that data unit from the merged log.