This section provides detailed information about the configuration file parameters:
On UNIX and Windows NT servers, the RDB_NAME parameter specifies the name of an existing database in which DB2 OLAP Server stores your OLAP application data. The format of this parameter is:
RDB_NAME = databasename
This parameter is required in the RSM section.
The RDB_USERID parameter specifies the user ID that DB2 OLAP Server uses to log on to your relational database. This user ID must be set up on your relational database. This parameter is optional. If the RDB_USERID and RDB_PASSWORD parameters are omited, DB2 OLAP Server logs on to DB2 UDB using the operating system session user ID and password.
The format of this parameter is:
RDB_USERID = userid
The RDB_PASSWORD parameter specifies the password for the user ID that DB2 OLAP Server uses to log on to your relational database. This parameter is optional. If the RDB_USERID and RDB_PASSWORD parameters are omited, DB2 OLAP Server logs on to DB2 UDB using the operating system session user ID and password.
The format of this parameter is:
RDB_PASSWORD = password
The TABLESPACE parameter specifies a string that is appended to each CREATE TABLE statement issued by DB2 OLAP Server. The TABLESPACE parameter determines the table space in which DB2 OLAP Server creates relational tables.
This parameter is optional.
The format of this parameter is:
TABLESPACE = string
where string is the string that you want to append to each CREATE TABLE statement issued by DB2 OLAP Server to control the table space in which tables are created. Any table space that you specify in this string must be an existing table space.
Because the string is appended to a CREATE TABLE statement, you must specify the full TABLESPACE clause. All options of the clause are available. The default is "" (empty string).
Example for Windows NT and UNIX:
TABLESPACE=IN TS1 INDEX IN TSIDX
Example for OS/390:
TABLESPACE=IN OLAP.TS32
See the SQL reference for your relational database for complete syntax of SQL statements.
The ADMINSPACE parameter determines the table space in which DB2 OLAP Server creates relational tables for administration purposes. For OS/390, the table space must be a 32 KB page table space. The ADMINSPACE parameter specifies a string that is appended to a CREATE TABLE statement issued by DB2 OLAP Server.
This parameter is required when accessing data on OS/390 and is optional for other operating systems.
The format of this parameter is:
ADMINSPACE = string
where string is the string that you want to append to each CREATE TABLE statement issued by DB2 OLAP Server to control the table space in which administration tables are created. Any table space that you specify in this string must be an existing table space.
Because the string is appended to a CREATE TABLE statement, you must specify a full TABLESPACE clause. All options of the clause are available. The default is "" (empty string).
For example:
ADMINSPACE=IN OLAP.ADMINDATA
See the SQL reference for your relational database for complete syntax of SQL statements.
If you do not specify this parameter, the administration tables are stored in the table space named in the TABLESPACE parameter.
The KEYSPACE parameter specifies the table space in which DB2 OLAP Server creates key tables for relational cubes. The KEYSPACE parameter is a string that DB2 OLAP Server appends to the CREATE TABLE statement when you create a key table.
You can improve DB2 OLAP Server performance by specifying a table space that uses a fast storage device.
This parameter is optional.
The format of this parameter is:
KEYSPACE = string
where string is the string that you want to append to each CREATE TABLE statement issued by DB2 OLAP Server when you create a key table. Any table space that you specify in this string must be an existing table space.
Because the string is appended to a CREATE TABLE statement, you must specify the full TABLESPACE clause. All options of the clause are available. If you do not specify this parameter, the key table is stored in the table space named in the TABLESPACE parameter. If you do not specify the TABLESPACE parameter, the default is "" (empty string).
Example for Windows NT and UNIX:
TABLESPACE=IN TS1 INDEX IN TSIDX
See the SQL reference for your relational database for complete syntax of SQL statements.
The FACTS parameter specifies a string that is appended to each CREATE TABLE statement issued by DB2 OLAP Server when it creates a fact table. The FACTS parameter determines the table space in which DB2 OLAP Server creates the fact table for a relational cube.
Because the fact table is the largest and most important table in a relational cube, you can improve performance by specifying a table space that uses a very fast storage device. You can also use a partitioned table space to improve performance if partitioned table spaces are supported by your database.
This parameter is optional.
The format of this parameter is:
FACTS = string
where string is the string that you want to append to each CREATE TABLE statement issued by DB2 OLAP Server when it creates a fact table. Any table space that you specify in this string must be an existing table space. This string is appended directly to the CREATE TABLE statement, so you must specify the full FACTS clause.
All options of the clause are available. If you do not specify this parameter, the fact table is stored in the table space named in the TABLESPACE parameter. If you do not specify the TABLESPACE parameter, the default is "" (empty string).
Example for Windows NT and UNIX:
FACTS=IN TS1 INDEX IN TSIDX
On OS/390, DB2 OLAP Server supplies the fact table number for you, for example:
FACTS=IN OLAP.TSPRF? where ? is the fact table number
See the SQL reference for your relational database for complete syntax of SQL statements.
The TRACELEVEL parameter specifies the level of detail that the DB2 OLAP Server trace facility provides.
Important: The TRACELEVEL parameter should be used only at the request of IBM for diagnosing problems. Because the use of this parameter can severely degrade the performance of DB2 OLAP Server, the parameter should not be used during normal use of the product.
This parameter is optional.
The format of this parameter is:
TRACELEVEL = level
where level is one of the following values:
The TRACEFILESIZE parameter specifies the maximum size of the file in which the trace facility stores trace information (RSMTRACE.LOG). When the trace file reaches the size specified with this parameter, it is flushed.
Important: The TRACEFILESIZE parameter should be used only at the request of IBM for diagnosing problems. Because the use of this parameter can severely degrade the performance of DB2 OLAP Server, the parameter should not be used during normal use of the product.
This parameter is optional.
The format of this parameter is:
TRACEFILESIZE = size
where size is the maximum size in megabytes (MB) to which the trace file can grow before being flushed. The default file size is 1 MB.
The ISOLATION parameter specifies the isolation level that DB2 OLAP Server uses when working with your relational database. The isolation level determines how data is locked or isolated from other transactions and processes while the data is being accessed. Higher isolation levels provide greater integrity by isolating more data sooner. However, higher isolation levels might reduce concurrency because transactions and processes might have to wait to access isolated data.
This parameter is optional.
The format of this parameter is:
ISOLATION = level
where level is one of the following values:
Cursor stability locks any row accessed by a transaction while the cursor is positioned on the row. This lock remains in effect until the next row is fetched or the transaction is terminated. However, if any data in a row is changed, the lock is held until the change is committed.
No other transaction or process can update or delete a row that a cursor stability application has retrieved while any updateable cursor is positioned on the row. However, other applications can insert, delete, or change a row on either side of the locked row with the following exceptions:
Cursor stability transactions cannot see uncommitted changes of other applications. Cursor stability is the default isolation level and should be used when you want the maximum concurrency while seeing only committed rows from other transactions or processes.
Uncommitted read allows a transaction to access uncommitted changes of other transactions. Transactions do not lock other transactions or processes out of the row being read unless a transaction attempts to drop or alter the table. Changes made by other transactions can be read before they are committed or rolled back. The uncommitted read isolation level is most commonly used when updates are not possible, or when you do not care whether you see uncommitted data from other transactions. Uncommitted read results in the lowest number of locks and the highest level of concurrency.
With read stability, only the rows that are retrieved are isolated. This ensures that any qualifying row read during a unit of work is not changed by another transaction or process until the unit of work completes, and that any row changed by another transaction or process is not read until the change is committed by that process. The read stability isolation level provides both a high degree of concurrency and a stable view of the data.
With repeatable read, every row that is referred to is isolated, not just the rows that are retrieved. Appropriate locking is performed so that another transaction or application cannot insert or update a row that would be added to the list of rows referred to by this transaction.
Repeatable read can acquire and hold a considerable number of locks. These locks can quickly escalate to the equivalent of a whole table lock.
Repeatable read provides the highest degree of integrity, but any rows referred to by one transaction or process are immediately isolated. This results in the lowest degree of concurrency.
Repeatable read is not normally recommended for DB2 OLAP Server.
For more information about isolation levels, see your relational database documentation.
The MAXPOOLCONNECTIONS parameter specifies the maximum number of relational database connections that an OLAP application can hold in its pool.
This parameter is optional.
The format of this parameter is:
MAXPOOLCONNECTIONS = maxnumber
where maxnumber is the maximum number of connections each OLAP application can hold in its pool. The default is 20.
The minimum value that you can specify is 0. If you specify 0, an OLAP application will not hold any connections in its pool and will make a new connection each time it needs one.
The maximum value that you specify should not be greater than the maximum number of concurrent connections supported by your relational database.
The STARTCONNECTIONS parameter specifies the number of connections that an OLAP application establishes with your relational database when the application is activated.
This parameter is optional.
The format of this parameter is:
STARTCONNECTIONS = number
where number is the number of connections with your relational database that DB2 OLAP Server pre-starts when an OLAP application is activated. The default is 3.
The minimum value that you can specify is 0. If you specify 0, an OLAP application will not establish any connection with your relational database when the application is activated.
The maximum value that you specify should not be greater than the value that you specify for MAXPOOLCONNECTIONS.
Use this parameter to partition the DB2 UDB table space in which the fact table is stored, or to let DB2 OLAP Server know how the OS/390 table space for the fact table is partitioned.
If you are using DB2 UDB Extended Enterprise Edition V5 or higher: The PARTITIONING parameter adds a partitioning key clause to the CREATE TABLE statement when the fact table is created. Then DB2 OLAP Server uses the currently defined sparse dimensions to determine which columns to use as the partitioning key columns.
If you are using DB2 for OS/390: The PARTITIONING parameter creates a cluster index for your table space, based on the number of partitions specified when the OS/390 table space was created.
This parameter is applicable only if you are using DB2 UDB Extended Enterprise Edition V5 or DB2 for OS/390, and is optional.
The format of this parameter is:
PARTITIONING = value
Set value to the number of partitions that the OS/390 database administrator created for the table space.
If you are using DB2 UDB: Set value to either 0 or 1. If you set the value to 0 the clause will not be added to the CREATE TABLE statement; 0 is the default value. If you set the value to 1, the clause will be added.
See the documentation for your relational database to learn more about partitioning a databases. See the SQL reference for your relational database for complete syntax of SQL statements.
Use this parameter to specify the index space for the index of a fact table when you are using DB2 OLAP Server to access data in DB2 on OS/390. DB2 OLAP Server generates the number of the fact table. The FINDEX parameter adds a USING STOGROUP clause to the CREATE INDEX statement for the fact table.
This parameter is optional, and is applicable only if you are you are accessing data in DB2 for OS/390.
The format of this parameter is: FINDEX =string
where string is the string that specifies the USING STOGROUP block of the CREATE INDEX statement.
You must use a question mark as the last character in the SGPR parameter. DB2 OLAP Server generates a number from 1 to 4 to replace the question mark. For example:
FINDEX = USING STOGROUP SGPR? BUFFERPOOL BP2
Use this parameter to specify the index space for the index of a key table in DB2 on OS/390. The parameter adds a USING STOGROUP clause to the CREATE INDEX statement for the key table. A relational database key table is the equivalent of an index for a multidimensional database.
This parameter is optional, and is applicable only if you are accessing data in DB2 for OS/390.
The format of this parameter is: KINDEX =string
where string is the string that specifies the USING STOGROUP block of the CREATE INDEX statement.
For example:
KINDEX = USING STOGROUP SGPR0 BUFFERPOOL BP2