Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390 > Understanding Siebel Partitioning > Strategies for Special Types of Tables >

About EIM Considerations for Table Space Partitioning

The mechanism by which EIM generates the ROW_ID can result in an uneven distribution of data if you use EIM with one of the default partitioning schemes to import data into a base table.

When EIM imports data into a base table, EIM automatically generates the base table ROW_ID by concatenating the prefix with a unique number; for example, 1-SB3-123. EIM relies on database functions to make sure that each number is unique under the same prefix.

Uneven data distribution occurs because one of the default partitioning approaches uses the last two characters of ROW_ID as the partition key for partitioning of base tables; these characters can be letters, numbers, or a combination of letters and numbers, but the last two characters in a ROW_ID generated by EIM are numbers.

In order for your storage control file to use partitioning keys that reflect the nature of your data, consider your data distribution with regard to your EIM process before you begin your database installation. Then modify your partitioning keys accordingly. Alternatively, you can repartition the table after an uneven distribution has occurred.