Skip to end of metadata
Go to start of metadata


For a recovery technique based on WAL (Write-Ahead Logging) protocol, DBMS records redo log and then changes/saves/deletes data is a general transaction process. Both redo logs and data require persistent physical storage space. Each storage space can be organized on the same disk or on a separate physical disk. When configuring the redo log and data storage space on the same disk, it must take as consideration because I/O contention for disk access may occur in the process of processing numerous transactions at the same time. This document describes how  ALTIBASE handles the redo log recording storage and data recording state, and recommends disk configuration methods to minimize the disk bottlenecks.

The test environment of this document is as follows.

  • ALTIBASE: Altibase version 6 or later

For errors and improvements related to this document, please contact the technical support portal or technical support center




  • No labels