My Oracle Support Banner

Essbase v11.1.2+ Database Corruption/Invalid Block Header (IBH)) Error "Invalid transaction status for block -- Please use the IBH Locate/Fix utilities to find/fix the problem" (Doc ID 1679625.1)

Last updated on DECEMBER 04, 2018

Applies to:

Hyperion Essbase - Version 11.1.2.2.100 and later
Hyperion Planning - Version 11.1.2.3.500 to 11.1.2.3.500 [Release 11.1]
Information in this document applies to any platform.

Symptoms

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



Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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