Object and page audit errors after restore of NonTranloggedGlobals
When a repository is using NotTranloggedGlobals, and performs a backup and restore from logs, there are some circumstances in which OOPs end up neither allocated nor on the free OOP list.
This causes object and page audit to report errors:
objectAudit:
The object [nnnn] does not exist, but is neither dead nor in the FreeOop List.
pageAudit:
Error: Found oops that do not exist and are not in the root page freeOops
These OOPs will not get used and are effectively lost; otherwise, this error is benign.
The exact circumstances that produce this issue are not yet determined.
Workaround
Making a programmatic backup and restoring it rebuilds the free oop list and fixes the problem.
Last updated: 7/31/18