Bug 46148

Bug: 46148

Impact:

Critical

Product:

GemStone/S 64 Bit

Versions:

3.3, 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.x, 3.0.x, 2.4.8, 2.4.4.8, 2.4.4.7, 2.4.4.6, 2.4.4.5, 2.4.x, 2.3.x, 2.2.6.5, 2.2.5.4, 2.2.x, 2.x

Platform:

Fixed In:

3.3.1, 3.2.15

Repeated replay of transaction log can cause corruption

If a partial transaction log is restored into a repository, and then the completed transaction log is restored again into this same repository, some records in the later part of the tranlog may not be replayed, which results in corruption.

The scenario in which this may occur is in a warm backup system, where the current transaction log of the production system is inadvertently replayed into the standby while the production system is still writing records to it.  After the production system completes writing to that transaction log, if the partially-replayed log is re-restored, this bug is exposed.

Workaround

Ensure that your system does not replay partial logs.