Bug 27065

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

All

Recovery fails with unused extents

When extents are added programmatically, the configuration file is
updated immediately, but the change is not recorded until the next
checkpoint.  If there is an unexpected shutdown occurs before the
next checkpoint, the stone recovery may fail with the error message:

File already exists; you must delete it before recovery can succeed.

Workaround

Removed the recently added extent file/s.  As long as the transaction
logs are available, any data in these extents will be restored by the recovery process.


Last updated: 11/21/07