Product Documentation

c-treeACE V11.0 Release Notes

Previous Topic

Next Topic

Ensure Correct Log Update for Very Large Transactions

A single large transaction log write (for example, a checkpoint holding a large transaction spanning millions of record deletes; potentially a single very large data record image) caused the log to be extended. In certain cases where the write was very large, the transaction log extension was smaller than required, which resulted in the log write extending past the physical EOF. This caused later log extensions to partially overwrite this log region with 0xff, as all log extensions are written at the physical EOF. Error 75 may have been seen.

Note: Using the log template feature should prevent this bug from occurring. All existing logs must be removed when the LOG_TEMPLATE keyword is added or LOG_SPACE is changed, or potentially vulnerable log extensions could still occur. LOG_TEMPLATE is a default configuration option as of V9.

TOCIndex