Bug 46252

Bug: 46252

Impact:

Critical

Product:

GemStone/S 64 Bit

Versions:

3.3.3, 3.3.2, 3.3.1, 3.3, 3.2.17, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8.1, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, 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

Platform:

All Platforms

Fixed In:

3.3.4, 3.2.16

Operations may hang when oopHighWaterMark over 4 billion

In very large repositories with a oop high water mark greater than 4 billion, operations that scan oops over the entire repository may hang and run hot.

You can determine your oop high water mark by executing

   System _oopNumber oopNumberHighWaterMark.

or by checking the stone startup information in the stone log:

    Repository startup statistics:
        Pages Need Reclaiming =XXXXX
        Free Oops=XXXXX
        Oop Number High Water Mark=XXXXXXXX

The affected operations includes:
  MFC and subsequent processing such as write set union sweep
  restore from backup
  object audit
  list instances
  count instances
  find object

To diagnose this problem, take a stack trace (using either gdb/dbx or "kill -USR1") of the hanging gem.  This will include, in the C stack:
    UtlFindFirstBitSet

Most cases of this bug are fixed in v3.2.16 and later.  A further issue with restore from backup is fixed in v3.3.4.

Workaround

In some cases, you can kill the session and try the operation again.