My Oracle Support Banner

Essbase v11.1.2+ Database Corruption/Invalid Block Header (IBH)) Errors "Invalid transaction status for block -- Please use the IBH Locate/Fix utilities to find/fix the problem" or "1006032 Invalid stored logical data block size (xxxx)" (Doc ID 1679625.1)

Last updated on DECEMBER 04, 2023

Applies to:

Hyperion Essbase - Version to [Release 11.1 to 21]
Hyperion Planning - Version to [Release 11.1 to 11.2]
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:

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 and code lines.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.