Last updated on JULY 06, 2017
Applies to:Hyperion Essbase - Version 22.214.171.124.100 and later
Hyperion Planning - Version 126.96.36.199.500 to 188.8.131.52.500 [Release 11.1]
Information in this document applies to any platform.
If an Essbase application is abnormally terminated, either by a crash or user intervention, it can cause a corruption in the database. One of the types of database corruption is an "Invalid Block Header (IBH)". Errors in the application log include:
- Invalid block header: Block numbers do not match -- Please use the IBH Locate/Fix utilities to find/fix the IBH problem
- Invalid transaction status for block -- Please use the IBH Locate/Fix utilities to find/fix the problem -- Please use the IBH Locate/Fix utilities to find/fix the IBH problem
- Duplicate key found in AVL-Tree.
Another issue that has been mistakenly reported to be an IBH problem is when you see the presence of the following error:
Corrupted Node Page in the B+tree. [adIndPromoteSafeWrite] aborted
This is not an IBH issue, and has been fixed already in the 184.108.40.206.106 and 220.127.116.11.500 code lines.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms