Bug 50419

Bug: 50419

Impact:

Product:

GemStone/S 64 Bit

Versions:

3.7.1, 3.7, 3.6.8, 3.6.7, 3.6.6, 3.6.5, 3.6.4, 3.6.3, 3.6.2, 3.6.1, 3.6, 3.5.8, 3.5.7, 3.5.6, 3.5.5, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5, 3.4.5, 3.4.4, 3.4.3, 3.4.2, 3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.1, 3.3, 3.2.16, 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.1.x, 3.x, 3.2x

Platform:

Fixed In:

3.6.6

objectAudit that responds to sigAborts may miss problems; 3.6.6 and later may encounter CRB

There were kinds of corruption that could be missed by Repository >> objectAudit and related methods.

To avoid a commit record backlog, objectAudit aborts as needed after its initial scan. This allowed objectAudit to safely run while the repository was in use. However, the scan to detect invalid references did not report errors under some conditions, since it could not definitely determine corruption vs. valid state changes.

Workaround

Running objectAudit with no other sessions committing will ensure the audit results are reliable. You should ensure reclaim is complete, or disable to ReclaimGem.

In v3.6.6 and 3.7, objectAudit runs in transaction in order to provide reliable reports; you should check that this does not create commit record backlog issues in your environment. The previous behavior is available with methods objectAuditPartial*