Bug 46032

Bug: 46032

Impact:

Product:

GemStone/S 64 Bit

Versions:

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

Platform:

All Platforms

Fixed In:

3.2.13

Corrupt object error, DataPgAllocSpace allocation failure

It is possible to get an error during or after upgrade to 3.2.x, when the system finds an object referencing a cluster bucket ID that does not have a corresponding ClusterBucket object in AllClusterBuckets. The system reports a corrupt object error containing the seemingly unrelated message:

DataPgAllocSpace: allocation failure

This is usually exposed during an upgrade to a 3.2.x release, when the SymbolGem will fail with this error during the first 3.2.x startstone on the pre-3.2.x extents.  More rarely, it can occur after the upgrade during normal 3.2.x operation.

See section 14.1 of the GemStone Programming Guide for details on cluster buckets.

Workaround

Create new cluster buckets to fill all 255 possible IDs:

topaz 1> run 
(System maxClusterBucket + 1) to: 255 do:
   [:i | ClusterBucket new ]. System commitTransaction.
%