Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

Table structure
of facttable
Indices on F-facttable:
Nonunique Compound Index ~P:
( unique for APO cubes )
Figure 2-11 Indices for fact tables
Figure 2-11 shows the various indexes that are created for fact tables on the DB2
database. The P means packet-dimension, T stands for time dimension, and U
stands for unit dimension. D1 and D2 are for dimension 1 and dimension 2,
respectively, and kf is for keyfigure. So you see, there are some differences
between the indexes for E and F- fact tables.
dimensions Part. field Keyfigures
P T U D1 D2 D3 D4 calmonth kf1 kf2 kf3
Nonunique secondary indexes on every single dimension, except
P and U. Not on T when partitioned
P
T D1 D2 D3 D4 U
Without leading P, when partitioned: T D1 D2 D3 D4 U
Indices on E-facttable:
Unique Compound Index ~0:
(as DPSI nonunique)
Nonunique secondary indexes on every single
dimension, except T and U. On P only for
noncumulative cubes
T D1 D2 D3 D4
T D1 D2 D3 D4 U
P D1 D2 D3 D4
+ These indices ensure a sufficient base performance
+ Additional 2- or 3-column indexes in SE11 may give better performance for certain queries
- Numeric index id (e.g. `800`): index is recreated like the default indices
- Character index id (e.g. `X01`): index is not touched by the system
+ the definition of the compound ~0 index on E-facttable within the DDIC differs from DB (different
ordering of fields)
+ the compound index on the F-facttable ~P is not defined in DDIC
Chapter 2. Overview of SAP BI and related data 23
P