OLAP Setup and User's Guide

Tuning DB2 OLAP Server

Most of the tuning and configuration information in the Database Administrator's Guide is valid for DB2 OLAP Server. The following guidelines are especially important for DB2 OLAP Server:

• Use the Commit block parameter to set the number of commit blocks as high as possible without exceeding the available DB2 log space. See Setting the Commit Block Parameter for more information on setting a commit block number.
• DB2 OLAP Server has two caches you can manage. The data cache buffers the data in the fact table, and the index cache buffers the data in the key table. You can either estimate how much memory each cache needs before loading data, or load the data and then adjust the cache settings. Make sure you do not overcommit memory. In either case, you need to tune these settings.
• Important: Turn tracing off by setting the TRACELEVEL parameter in the rsm.cfg file to 0 (TRACELEVEL=0). If you do not turn off tracing, the performance of DB2 OLAP Server can slow significantly and the trace file will consume large amounts of disk space. See TRACELEVEL for more information.