Method for managing database recovery from failure of a shared store in a system including a plurality of transaction-based systems of the write-ahead logging type

Patent 5280611 Issued on January 18, 1994. Estimated Expiration Date:

November 8, 2011. Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.

Abstract Claims Description Full Text

Patent References

Method and means for the retention of locks across system, subsystem, and communication failures in a multiprocessing, multiprogramming, shared data environment
Patent #: 4480304
Issued on: 10/30/1984
Inventor: Carr , et al.

Method for restoring a database after I/O error employing write-ahead logging protocols
Patent #: 4945474
Issued on: 07/31/1990
Inventor: Elliott, et al.

Soft checkpointing system using log sequence numbers derived from stored data pages and log records for database recovery
Patent #: 5043866
Issued on: 08/27/1991
Inventor: Myre, Jr., et al.

Concurrently applying redo records to backup database in a log sequence using single queue server per queue at a time Patent #: 5170480
Issued on: 12/08/1992
Inventor: Mohan, et al.

Inventors

Application

No. 790241 filed on 11/08/1991

US Classes:

707/8, Concurrency (e.g., lock management in shared database)707/202, Recoverability710/242, Decentralized arbitrating714/20Plural recovery data sets containing set interrelation data (e.g., time values or log record numbers)

Examiners

Primary: Heckler, Thomas M.

Attorney, Agent or Firm

Baker, Maxham, Jester & Meador

International Classes

G06F 011/30
G06F 012/16
G06F 015/40

Abstract

In a multi-system data sharing complex, a database system can write updated pages to a shared electronic store for a fast write. Other database systems can obtain pages written to the shared store for further modification without the pages first being written to stable storage. However, pages are eventually written to the stable storage in a castout process. Recovery of a database from failure of the shared store is bounded by determination of a recovery boundary which, when applied to the union of database system transaction logs, establishes a point in front of which are found log records of modifications to pages which were in the shared store when it failed. These log records are applied to page versions obtained from stable storage to recover from failure of the shared store.

Other References

Research Disclosure, May 1986, No. 265, Kenneth Mason Publications Ltd., England, Improved Write-Ahead Logging
Research Report, RJ 6649, Aries: A Transaction Recovery Method Supporting Fine-Granularity Locking and Partial Rollbacks Using Write-Ahead Logging, Co. Mohan, pp. 1-58
Distributed Data Bases, Bruce G. Lindsay, "Single and Multi-Site Recovery Facilities", pp. 261-265
Data Recovery in IBM Database 2, R. A. Crus, IBM Systems Journal, vol. 23, No. 2, 1984, pp. 178-188
Journal of Systems Management, Information Access Company; Association for Systems Management 1990, vol. 41, No. 1, p. 33, Current Trends in Transaction Processing Systems, Kumar, Vija