Bug 48276

GemStone/S 64 Bit

3.5.1, 3.5, 3.4.4, 3.4.3, 3.4.2, 3.4.1, 3.4

3.5.2, 3.4.5

Scan errors on repositories upgraded from early GemStone versions with sparse security policies

Repositories that originated in early versions of GemStone, such as 32-bit GemStone/S, and that had less than 20 Segments (since relabled ObjectSecurityPolicies), were assigned an ObjectSecurityPolicy with ID 20 during upgrade to 2.x, to support a nil security policy.  If there were less than 20 security policies in the original repository, the intermediate slots for object security policy IDs were nil.

Code changes in v3.4 for repository scan code did not handle nil slots for object security policies, and operations such as objectAudit and listInstances would error.

Workaround

Creating dummy object security policies will avoid errors. For example:

1 to: SystemRepository size do: [:i | 
   (SystemRepository at: i) isNil ifTrue: [GsObjectSecurityPolicy new.]].


Last updated: 1/8/20