Bug 40553

GemStone/S 64 Bit

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.4.6, 2.4.4.5, 2.4.4.4, 2.4.4.3, 2.4.4, 2.4.3, 2.4.2, 2.4.1, 2.4, 2.3.1.6, 2.3.1, 2.3, 2.2.5.4, 2.2.5.3, 2.2.5.2, 2.2.5.1, 2.2.5, 2.2.x, 2.2, 2.1.x

All

3.2

Migrating invariant objects in indexes may corrupt indexes

Invariant objects may be added to indexed collections and participate in
indexes, but they do not get dependencyMaps since they cannot be modified.
However, it is currently permitted to migrate invariant objects. If invarient
objects are in an indexed collection, and are migrated, the index may not
be correctly updated due to the lack of dependency list. This means the
index may be corrupted regarding the invariant object.

Workaround

Do not migrate instances that are invariant and participate in indexed
collections. Drop indexes on collections that contain invariant objects
prior to migration, and re-index after migration is complete.


Last updated: 4/30/10