Bug 27082

Informational

GemStone/S

6.7, 6.6.5, 6.6.4, 6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7.5, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.2.x, 6.2, 6.1.6, 6.1.5, 6.1.x, 6.0.2, 6.0.1, 6.0

Repository >> restoreStatusNextFileId not aware of final fileId

When the stone is in restore mode, the method
   Repository>>restoreStatusNextFileId
should report the ID number of the next transaction log file
to be restored.  However, after all the transaction logs have
been restored, it will erroneously return the next ID in the
sequence, although a transaction log file with this ID does
not exist.

Workaround

Do not rely on this method to determine when all transaction logs
have been restored.


Last updated: