Bug 45295

GemStone/S 64 Bit

3.4.2, 3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.1, 3.3, 3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8.1, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, 3.1.0.6, 3.1.0.5, 3.1.0.4, 3.1.0.3, 3.1.0.2, 3.1.0.1, 3.1, 3.0.1, 3.0, 2.4.8, 2.4.7, 2.4.6, 2.4.5.1, 2.4.5, 2.4.4.8, 2.4.4.7, 2.4.x, 2.3.1.6, 2.3.x, 2.2.5.4, 2.2.x, 2.x, 1.x

In partial logging mode, not all tranlogs may be deleted

In partial logging mode (STN_TRAN_FULL_LOGGING =FALSE), transactions smaller than STN_TRAN_LOG_LIMIT are written to the tranlog (larger transactions trigger a checkpoint).  If the period starting from a begin_data until commit completes spans the point where a new tranlog is started, the previous tranlog cannot be deleted at the time the new log is started.  The way tranlog deletion is handled does not allow later automatic deletion, so the old tranlog is remains until manually removed.

Workaround

You will need to periodically check and manually delete leftover tranlogs.

Partial logging is not intended for production use, since it does not provide the ability to restore from backup and apply tranlogs. While partial logging mode allows you to recover from minor problems, if there is a serious problem such as repository corruption, the system may not be recoverable if using partial logging mode.


Last updated: 7/22/15