Controls how many invalid block-header messages are returned to the client or server log, relative to the number of level-0 blocks written to disk.
This setting does not apply to aggregate storage databases.
IBHFIXTHRESHOLD appName | xxxx dbName | xxxx percentage
appname—Optional. If you supply an application name but use xxxx in place of dbName, the setting applies to all databases within the named application. If you use xxxx in place of appName and dbName, the setting applies to all applications and databases on the server.
dbname—Optional. If you supply a database name and an application name, the setting applies only to the named database. If you use xxxx in place of dbName, the setting applies to all databases within the named application. If you supply a database name, you must also supply an application name.
xxxx–If used in place of appName, and dbName, specifies all databases on the Essbase Server.
If used in place of dbName, specifies all databases on the application.
percentage—Percentage of invalid block-header errors to report, relative to the number of level-0 blocks on disk. Once the threshold is reached, a message is sent to the client requesting that the user rebuild the database, and the Essbase Server shuts down. Valid values are integers 0 to 100.
You must set the server configuration setting IBHFIXTHRESHOLD in the server essbase.cfg file and restart Essbase Server before you can find and fix invalid block-header problems.
This setting controls how many invalid block-header messages are returned to the client or server log, relative to the number of level 0 blocks written to disk. After the threshold is reached, no corrective action can be performed, and a message is sent to the client suggesting that the database be rebuilt.
If messages are written to the client or server log indicating the presence of invalid block-header errors, but the threshold that requires the database be rebuilt is not reached, you can either rebuild the database or you can find and fix the errors using MaxL: Alter Database DBS-NAME validate data to local | server logfile FILE-NAME.
If Essbase runs in uncommitted mode when it receives an invalid block-header error message, the current transaction may stop without any rollback, meaning that some data may have changed. Be sure to verify that all transactions that you expected to finish have finished. If not, you may need to clean up the data or rebuild the database.
For information about types of invalid block-header errors and how to rebuild a database, see the Oracle Essbase Database Administrator's Guide.
IBHFIXTHRESHOLD sample basic 10
Specifies that on Sample Basic, if 10% of the data blocks have invalid block-header errors, it is time to rebuild the database.
IBHFIXTHRESHOLD sample xxxx 15
Specifies that for any database in the Sample application, if 15% of the data blocks have invalid block-header errors, it is time to rebuild the database.
IBHFIXTHRESHOLD xxxx xxxx 5
Specifies that for any database, if 5% of the data blocks have invalid block-header errors, it is time to rebuild the database.
Alter Database (MaxL statement)