SAP Knowledge Base Article - Preview

3397830 - Partitioning of High Cardinality InfoObject Tables not as expected

Symptom

According the consulting note 2374652, the following rules apply to the master data tables (P/Q) of a Characteristic, which has the 'High Cardinality' flag set:

Tables generated for InfoObjects with property 'High Cardinality' are hash partitioned at the first level. All other InfoObject tables are not partitioned.

  • In scale-out systems, InfoObject tables are located on worker nodes. All tables of a high cardinality InfoObject and their partitions are located on the same worker host (LOCATION = 'slave#1' in SYS.TABLE_PLACEMENT).
  • In single-node systems, InfoObject tables are located on the coordinator. A single first level partition is created per table - unless the total number of records in the largest table of an InfoObject exceeds 1.5 billion records.

However when such a Characteristic is created, then the master data tables are not created with the proper partitioning schema (PART_SPEC).


Read more...

Environment

  • SAP BW/4HANA

Product

SAP BW/4HANA all versions

Keywords

part_spec, partitioning of high cardinality characteristics, hash, hash partition , KBA , BW4-ME-IOBJ , InfoObjects , BC-DB-HDB-POR , Dictionary & Consistency checks for SAP HANA , BW4-DM-MD , Masterdata , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.