The Deferred-Restructure Dimension Builds is valuable method when you are using more than one single data source for a dimension build.
By default, each time you make changes to an outline, Essbase considers the type of change and restructures the database if needed. Restructuring the database rebuilds the database, which takes time, requires more disk space for its process, and can cause file defragmentation.
Deferred-restructure dimension builds, also known as incremental dimension builds, read multiple data sources for dimension builds and delay restructuring until all data sources have been processed.
The following methods for performing deferred-restructure builds use different approaches to specifying the action:
When the files listed are all dimension builds, a deferred-restructure dimension build option is available. Selecting this option delays restructuring until all sources have been processed. The outline is validated after each dimension build is processed. See “Performing a Data Load or Dimension Build” in the Oracle Essbase Administration Services Online Help.
You can control whether outline validation is performed for each file. You must enable outline validation for the last file. See “import database” and “import dimension” in the MaxL section of the Oracle Essbase Technical Reference.
In all cases, the data sources are processed in the order in which they are listed.
MaxL and ESSCMD enable you to enforce or suppress outline verification for each file. To ensure a valid outline, ensure that the last build verifies the outline. Deferred-restructure dimension builds in Administration Services verify the outline after each data source is processed.