Bug: 37829

Impact:

Product:
GemStone/S 64

Versions:
2.2.3, 2.2.2, 2.2.1, 2.2, 2.1.4, 2.1.x, 2.1, 2.0.5, 2.0.4, 2.0.3, 2.0.x, 1.2, 1.1.14, 1.x

Platform:
All

Fixed In:
1.2.1, 2.2.4

Incorrect >>_oopNumberHighWaterMark following restore

Immediately after a restore from backup, _oopNumberHighWaterMark
reports the wrong value.  The value reported was a cached value that
was not updated properly after a restore.

Workaround:

none/not applicable