Method for restoring a database after I/O error employing write-ahead logging protocols
April 8, 2008. 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.Patent References 3736566 Instruction retry mechanism for a data processing system Method for assuring atomicity of multi-row update operations in a database system Method and apparatus for logging journal data using a log write ahead data set Method and apparatus for restarting a computing system Database backup method Asynchronous checkpointing system for error recovery Virtual command rollback in a fault tolerant data processing system Virtual memory recovery system using persistent roots for selective garbage collection and sibling page timestamping for defining checkpoint state Data recovery system capable of performing transaction processing in parallel with data recovery processing Inventors
AssigneeApplicationNo. 179195 filed on 04/08/1988US Classes:714/16, Forward recovery (e.g., redoing committed action)707/202RecoverabilityExaminersPrimary: Lee, Thomas C.Attorney, Agent or FirmInternational ClassesG06F 011/00G06F 015/40 AbstractMethod for reducing data loss during I/O errors and power failure during non-atomic writes to media in a transaction management system using write-ahead logging protocol. A recovery log is written during forward processing. On system restart processing, the log is traversed and a REDO executed. Recovery is effected from detected incomplete log writes or log write failures and uncommitted transactions are undone. A technique is provided in which files having I/O errors are identified, whereby subsequent restart operations are prevented from accessing these files. In one embodiment index files with such error are renamed, serving to indicate that corresponding original files contain errors, and the error index files are automatically rebuilt whereby I/O error on the files causes no data loss. The index file rebuild does not invalidate access plans related to the failed index.Other References
| |
