Prepartitioned Siebel Tables

Siebel CRM provides in the storage control file templates the partitioned tables shown in the following table. The database tables listed represent partitioned Core product tables; seven exceptions are identified as Siebel Industry Applications (SIA) product tables.

For each table in the following table, the partitioning key columns for the table are listed, as is the recommended clustering index for the table. A partitioning index is defined for three of the partitioned tables (S_CONTACT, S_OPTY, and S_ORG_EXT); the name of the index is listed for these tables.

When determining the partitioning strategy for your implementation, you must assess whether the partitioning key columns and recommended clustering indexes specified for the prepartitioned tables are appropriate for your environment. For example, in assessing the most appropriate partitioning column to use for intersection tables, take into account the relationship of candidate partitioning columns to their respective parent tables. Additionally, if multiple organizations are defined in your Siebel application, the BU_ID column might be the most appropriate partitioning column for a table. For information on customizing partitioned tables, see Changing the Number of Table Space Partitions.

Table	Partitioning Key Columns	Recommended Clustering Index
S_ACT_EMP	PARTITION_COLUMN	S_ACT_EMP_M1
S_ADDR_ORG	PARTITION_COLUMN	S_ADDR_ORG_U1
S_ADDR_PER	PARTITION_COLUMN	S_ADDR_PER_U1
S_APPLD_CVRG Siebel Industry Applications (SIA) table	PARTITION_COLUMN	S_APPLD_CVRG_U1
S_ASSET	PARTITION_COLUMN	S_ASSET_U1 (ASSET_NUM, PROD_ID, REV_NUM, BU_ID, CONFLICT_ID)
S_ASSET_CON	PARTITION_COLUMN	S_ASSET_CON_U1 (ASSET_ID, CONTACT_ID, RELATION_TYPE_CD, CONFLICT_ID)
S_ASSET_POSTN Siebel Industry Applications (SIA) table	PARTITION_COLUMN	S_ASSET_POSTN_M1
S_COMMUNICATION	PARTITION_COLUMN	S_COMMUNICATION_U1
S_CONTACT A partitioning index, S_CONTACT_M12, is defined for this table.	LAST_NAME Note: If multiple organizations are defined in your Siebel application, the BU_ID column might be a more effective partitioning key than the LAST_NAME column. In this case, cluster on the S_CONTACT_M14 index (BU_ID, LAST_NAME, FST_NAME, PRIV_FLG).	S_CONTACT_M12 (LAST_NAME, FST_NAME, MID_NAME, PRIV_FLG, ALIAS_NAME)
S_EVT_ACT	PARTITION_COLUMN	S_EVT_ACT_P1
S_EXP_ITEM	PARTITION_COLUMN	S_EXP_ITEM_U1
S_FN_ACCNT_TXN Siebel Industry Applications (SIA) table	PARTITION_COLUMN	S_FN_ACCNT_TXN_U1
S_FNCVRG_ELMNTS Siebel Industry Applications (SIA) table	PARTITION_COLUMN	S_FNCVRG_ELMNTS_U1
S_INS_CLAIM Siebel Industry Applications (SIA) table	PARTITION_COLUMN	S_INS_CLAIM_U1
S_INS_ITEM Siebel Industry Applications (SIA) table	PARTITION_COLUMN	S_INS_ITEM_U1
S_INSCLM_ELMNT Siebel Industry Applications (SIA) table	PARTITION_COLUMN	S_INSCLM_ELMNT_U1
S_OPTY A partitioning index, S_OPTY_U1, is defined for this table.	NAME Note: If multiple organizations are defined in your Siebel application, the BU_ID column might be a more effective partitioning key than the NAME column. In this case, cluster on the BU_ID, NAME columns.	S_OPTY_U1 (NAME, PR_DEPT_OU_ID, BU_ID, CONFLICT_ID)
S_OPTY_POSTN	PARTITION_COLUMN	S_OPTY_POSTN_U1 (OPTY_ID, POSITION_ID, CONFLICT_ID) Note: If your Siebel application is configured to use My Views to access the S_OPTY_POSTN table by the POSITION_ID column, cluster on the S_POSTN_CON_M12 index.
S_ORG_EXT A partitioning index, S_ORG_EXT_U1, is defined for this table.	NAME	S_ORG_EXT_U1 (NAME, LOC, BU_ID, CONFLICT_ID)
S_PARTY	PARTITION_COLUMN	S_PARTY_P1
S_PARTY_REL	PARTITION_COLUMN	S_PARTY_REL_U1
S_POSTN_CON	PARTITION_COLUMN	S_POSTN_CON_M1 (POSTN_ID, CON_LAST_NAME, CON_FST_NAME) Note: If the S_POSTN_CON table is not implemented as partitioned, cluster on either the POSTN_ID or the CON_ID column, depending on the one-to-many relationship of each column to its parent table.
S_REVN	PARTITION_COLUMN	S_REVN_U1 (REVN_ITEM_NUM, BU_ID, CONFLICT_ID)
S_SRV_REQ	PARTITION_COLUMN	S_SRV_REQ_U1 (SR_NUM, BU_ID, CONFLICT_ID)