Build: Processing Options

The data processing options enable you to control dimension and cube maintenance.

Atomic Refresh: Controls whether the refreshed dimensions and cubes are committed to the database together in a single transaction or in individual transactions. Atomic refresh commits the changes in a single transaction so that either all of the objects are refreshed or none of them are. Select this option when you want to present a consistent view of the data to users during the refresh period, or when you want to roll back the entire refresh if an error occurs. When Atomic Refresh is deselected, each object that is refreshed successfully is immediately committed. An error later in the maintenance task does not affect these objects.

Refresh After Errors: Controls whether processing can continue after an error occurs. Deselect Atomic Refresh when selecting this option, so that each object is refreshed in a separate transaction. Otherwise, maintenance will continue after an error, but eventually the entire transaction is rolled back.

When Refresh After Errors is selected, an error causes the current transaction to roll back so that the object retains its old data. Objects that have already been refreshed are unaffected, and the refresh continues for any additional objects. For example, suppose the Global analytic workspace is being refreshed. The dimensions are refreshed first, then the Units Cube, and then the Price Cube. If an error occurs when refreshing the Units Cube, then only the Units Cube retains the old data. The maintenance task can continue and refresh the Price Cube.

When Refresh After Errors is deselected, an error causes the current transaction to roll back and halts the maintenance task so that no more objects are refreshed. In the previous example, the dimensions are refreshed, but both the Units Cube and the Price Cube retain the old data.

Build Log Logging Level: Select one of these levels:

Action: Logs the status of each command used to build the cube dimensions and cubes, the use of slave processes, and summary records.
Notice: Logs messages from the OLAP engine, such as start and finish records for SQL Import, Aggregate, and Update.
Information: Provides more detailed explanations than Notice.
Statistics: Logs messages that provide tuning information, such as composite lengths, partitioning details, object sizes, and aggregation work lists. This level is intended for use by Oracle Field Services.
Debug: Logs debugging messages and other information typically sent to a trace file. This level is intended for use by Oracle Support Services.

To change the default logging level, choose Preferences from the Tools menu to display the OLAP Preferences Build Log panel.

Maximum Number of Errors Logged Per Build Step: The maximum number of records that can be written to the Rejected Records Log or the Dimension Compile Log in a single maintenance run before it fails with an error. A value of 0 turns off both logs. To change the default number, choose Preferences from the Tools menu to display the OLAP Preferences Build Log panel.