Bug 39292

Critical

GemStone/S 64 Bit

2.2.5.4, 2.2.5.3, 2.2.5.2, 2.2.5.1, 2.2.5, 2.2.4, 2.2.3, 2.2.2, 2.2.1, 2.2

All

2.3

Upgrade/conversion problems with Segments

During the upgrade or conversion process from 1.x or 2.0.x to 2.2.x,
Segments are set up, since Segments are not used in the originating
repository but are supported in 2.2.x with new protocol, and a
Segment 20 is now required.

However, when the originating repository was previously upgraded
from a version that did support Segments, such as GemStone/S 6.x,
there were a number of problems, including:
- Several extra Segments were created.
- When the originating repository Segment count plus number of
   created Segments added up to 20, an incorrect limit check
   resulted in an error.
- A duplicate Segment remained in the Repository.
- Segment groups and authorization were not correctly setup for
   all Segments in all cases.

Additional Segment issues problems existed in upgrading Repositories
that originally started on much older versions of GemStone, such
as 4.x.

Workaround

If no errors occur during conversion, and you do not intend to use
Segments for security, the Segment problems are not serious.

Contact GemStone Technical Support for Segment audit code and
upgrade/conversion files with fixes.


Last updated: 10/23/08