Encyclopedia of Database Systems

2018 Edition
| Editors: Ling Liu, M. Tamer Özsu

Multilevel Recovery and the ARIES Algorithm

  • Gerhard WeikumEmail author
Reference work entry
DOI: https://doi.org/10.1007/978-1-4614-8265-9_225


In contrast to basic database recovery with page-level logging and redo/undo passes, multi-level recoveryis needed whenever the database system uses fine-grained concurrency control, such as index-key locking or operation-based “semantic” conflict testing, or when log records describe composite operations that are not guaranteed to be atomic by single page writes (as a consequence of concurrency control or for other reasons). Advanced methods perform logging and recovery at multiple levels like pages and data objects (records, index entries, etc.). Page-level recovery is needed to ensure the atomicity and applicability of higher-level operations, and also for efficient redo. Higher-level recovery is needed to perform correct undo for composite operations of loser transactions. In addition, logged actions at all levels must be testable at recovery-time, by embedding extra information in database pages, typically using log sequence numbers (LSNs), and appropriate logging of...

This is a preview of subscription content, log in to check access.

Recommended Reading

  1. 1.
    Mohan C. Repeating history beyond ARIES. In: Proceedings of the 25th the International Conference on Very Large Data Bases; 1999. p. 1–17.Google Scholar
  2. 2.
    Mohan C, Haderle DJ, Lindsay BG, Pirahesh H, Schwarz PM. ARIES: a transaction recovery method supporting fine-granularity locking and partial rollbacks using write-ahead logging. ACM Trans Database Syst. 1992;17(1):94–162.CrossRefGoogle Scholar
  3. 3.
    Gray J, McJones PR, Blasgen MW, Lindsay BG, Lorie RA, Price TG, Putzolu GR, Traiger IL. The recovery manager of the system R database manager. ACM Comput Surv. 1981;13(2):223–43.CrossRefGoogle Scholar
  4. 4.
    Borr AJ. Robustness to crash in a distributed database: a non shared-memory multi-processor approach. In: Proceedings of the 10th International Conference on Very Large Data Bases; 1984. p. 445–53.Google Scholar
  5. 5.
    Crus RA. Data recovery in IBM database 2. IBM Syst J. 1984;23(2):178–88.CrossRefGoogle Scholar
  6. 6.
    Gray J, Reuter A. Transaction processing: concepts and techniques. San Francisco: Morgan Kaufmann; 1993.zbMATHGoogle Scholar
  7. 7.
    Lomet DB. MLR: a recovery method for multi-level systems. In: Proceedings of the ACM SIGMOD International Conference on Management of Data; 1992. p. 185–94.Google Scholar
  8. 8.
    Moss JEB, Griffeth ND, Graham MH. Abstraction in recovery management. In: Proceedings of the ACM SIGMOD International Conference on Management of Data; 1986. p. 72–83.CrossRefGoogle Scholar
  9. 9.
    Weikum G, Hasse C, Brössler P, Muth P. Multi-level recovery. In: Proceedings of the 9th ACM SIGACT-SIGMOD-SIGART Symposium on Principles of Database Systems; 1990. p. 109–23.Google Scholar
  10. 10.
    Weikum G, Vossen G. Transactional information systems: theory, algorithms, and the practice of concurrency control and recovery. San Francisco: Morgan Kaufmann; 2001.Google Scholar
  11. 11.
    Kuo D. Model and verification of a data manager based on ARIES. ACM Trans Database Syst. 1996;21(4):427–79.CrossRefGoogle Scholar

Copyright information

© Springer Science+Business Media, LLC, part of Springer Nature 2018

Authors and Affiliations

  1. 1.Department 5: Databases and Information SystemsMax-Planck-Institut für InformatikSaarbrückenGermany

Section editors and affiliations

  • Gottfried Vossen
    • 1
  1. 1.Dep. of Inf. SystemsWestf. Wilhelms-UniveristätMünsterGermany