...

{scrollbar}

...

O3 Builder is the component responsible for building the cube files from the models defined in O3 Designer. Using the O3 model definition from the .mdl file generated in O3 Designer, you can retrieve data the data from the specified sources and build the cube for use with O3 Browser.
You can build cubes using one of the following methods:

...

• text file directory locations for text data sources
• SQL data sources through JDBC/ODBC connections

The building of the cubes can be complete (full) or incremental.

The full build can be done directly from O3 Designer, using the Generate Cube option the the File menu, or with the O3 Builder.

The incremental build can only be done with the O3 Builder.

O3 Builder can send information about the final status of builds through e-mail. In the model definition, you can determine e-mail recipients based on the build type (incremental or complete) and the build result (OK or errors).

Using the model definition, you can also determine who should be informed in different situations such as: complete updating OK, incremental updating OK, or errors.

You can also specify that in the case of certain errors, such as when the database source for retrieving data is inaccessible, the build should retry a given number of times after a given interval. Anchor_Toc94582603_Toc94582603

Complete See Defining Build Actions

Full Builds

When you execute the build from O3 Designer, the generated cube corresponds to the model currently active in O3 Designer. If you wish, you can change the order that elements of each dimension hierarchy's level displays in for the O3 Browser prior to a complete build.
Notes

• If you change the order prior to an incremental build, the changes are ignored.

...

Incremental Builds

Use an incremental cube build to update the information in the cube information. This avoids complete rebuilds of cubes with lengthy build times. Two features support the incremental build:

...

• ensure that the text data source contains only records to be added
• limit SQL query data sources by using appropriate WHERE expressions

For SQL queries, you can include build parameters in the WHERE expression that limit the records obtained in accordance with the value they take in each build. The WHERE expressions can contain conditions dependent on record dates or ranges of values such as invoice numbers.
We recommend conditions based on dates as their management is easily automated through build parameters, as shown in the following example. For incremental builds, it is very important to verify the Input set configuration and the constructions parameters.

Datasources that belong to an incremental input set should provide only new data to the cube. If they provide information already in the cube, that information will be duplicated.

SQL datasources can limit the data retrieve using WHERE clauses combined with Parameters defined in the model. For instance, there could be conditions that limit the data based on timestamps, invoice numbers, etc.

During incremental builds the model definition used is the one stored in the cube itself. This means that any change in the .mdl file requires a full build before any incremental build.

Example

Consider an incremental build for a cube with sales information. Every day new data is added to the cube with information of the previous day. The SQL sentence that retrieves the data could be defined using date limits and the followint parameters:

Besides, O3 keeps track of the previous value of every parameter. Therefore it would be possible to refer to a parameter as follows:

This means that both the current and previous values of a parameter can be used in the WHERE clause.

For isntance:

Notice that these parameters are not predefined. They need to be created in the General Panel for the Model. See Defining Parameters

...

{scrollbar}