Bug 40054

GemStone/S

6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.2.2, 6.2.1, 6.2, 6.1.6, 6.1.5, 6.1.4, 6.1.3, 6.1.2, 6.1.1, 6.1.x, 6.1

All

6.5.4

Large SPC specifications not handled correctly

If you specify a SHR_PAGE_CACHE_SIZE_KB larger than can be accomodated
by 32-bit GemStone, but within the capacity of the hardware, GemStone
does  not handle cache sizing correctly.

The results depend on the size specified.  Values somewhat out of range,
such as 4000000, fail to start the stone, with a spcmon coredump.  With
larger values, such as 5000000, the stone starts up with a cache that
is  smaller than the size specified by the SHR_PAGE_CACHE_SIZE_KB setting.

The actual cache size started is not reported in the log files. You can
determine the cache size by examining the segment size using ipcs, or
check  the pcmon log file "Number of pages" * 8192.

Workaround

Carefully check the SHR_PAGE_CACHE_SIZE_KB, and when adjusting this value,
verify the actual cache size started.


Last updated: 6/11/09