Oracle^® Business Intelligence Server Administration Guide > Query Caching in the Oracle BI Server > Creating Aggregates for Oracle BI Server Queries >

Post Creation Activities

This section discusses the following topics:

• About Database Index Creation
• About Error Handling

About Database Index Creation

Currently, database table indexes are not generated automatically. If required, the database Administrator has to manually create these indexes on the database tables. Since the dimension tables are automatically generated, it is useful to set the logging level to 2 or higher to view the Aggregate Creation Plan in NQQuery.log. This plan, along with the aggregate specifications, can be used as a reference to locate automatically generated tables in the database.

You can manually embed dropping and building indexes in the logical SQL script using the EXECUTE PHYSICAL capability. The following is an example of the statements that you might add to the beginning of your script:

EXECUTE PHYSICAL CONNECTION POOL "SQL_Paint"."SQL_Paint" DROP INDEX demo_index1;

CREATE AGGREGATES......;

EXECUTE PHYSICAL CONNECTION POOL "SQL_Paint"."SQL_Paint" CREATE INDEX demo_index1 ON table1(col1);

About Error Handling

The following is a list of some reasons errors can occur:

• Network failure.
• No disk space on the database.
• Bad aggregate request.

If there is an error in the creation of any aggregate, the entire aggregate request is aborted and subsequent aggregates are not created. Aggregates that are already created and checked in, remain checked in. If there are errors, you need to remove them at the time of the error or at the next ETL run in one of the following ways:

• Manually remove the aggregates from the metadata and the database.
• Automatically remove all the aggregates using the Delete Aggregates specification.