2158927 - Inconsistent BW table partitioning and distribution on Hana

Symptom

When using report RSDRI_CONVERT_CUBE_TO_INMEMORY or report RSMIGRHANADB to convert InfoProviders to their SAP Hana-optimized counterparts, you experience the following errors:

1. column store error: [2575] flatten scenario failed;no rest partition found in dest F table, host: <hostname>:port
2. column store error: [2575] flatten scenario failed;source F table is not existing or invalid, host: <hostname>:port
3. column store error:  [2575] flatten scenario failed;multiple source F tables assigned to the same host, should not happen

The following errors may be found in the index server traces:

1. [48751]{525594}[447/-1] <timestamp> e bw_datastore     DSOActivation.cpp(04097) : Potential performance problem: Table SAP<SID>:/BIC/A<providername>00 is split and table SAP<SID>:/BIC/A<providername>40 is split by an appropriate criterion but corresponding parts are located on different servers. This will not prevent the Data Store from working but it may significantly degrade performance.

Additionally, you experience InfoProvider-related performance issues in a distributed Hana landscape.

Environment

• BW on Scale-out HANA
• Hana Rev 63 (SPS06) or above
• BW Release 730 SP08, Release 731 SP07, Release 740 SP02, or higher

Cause

InfoProvider tables and/or their partitions are either:

• Not located on the correct host
• Partitioned by inappropriate criteria
• And/or classified incorrectly

This could indicate incorrect landscape configuration. Table/Partition distribution is largely governed by entries in the following two tables:

• SYS.TABLE_GROUPS_
• _SYS_RT.TABLE_PLACEMENT

SYS.TABLE_GROUPS_ logically groups related InfoProvider tables and _SYS_RT.TABLE_PLACEMENT (when maintained as per SAP note 1908075) determines what host the classified tables should be on. If these tables are not maintained correctly, the distribution of InfoProvider tables are likely to be inconsistent causing the symptoms mentioned above.

Resolution

1. Ensure SAP note 1908075 is implemented and _SYS_RT.TABLE_PLACEMENT is populated with the recommended rows.
2. Implement SAP note 1862584 to ensure newly created tables are classified and grouped.
3. Implement SAP note 1756099 to enable the RSDU_TABLE_CONSISTENCY report.
4. Implement SAP notes 2093836 and 2099114 to ensure the structures supporting RSDU_TABLE_CONSISTENCY are up to date.

The following steps can be restricted to individual or a limited set of tables via the Data Selection section of the report as certain repairs can be resource intensive. For detailed information regarding the operation and usage of RSDU_TABLE_CONSISTENCY please refer to SAP note 1937062 - Usage of RSDU_TABLE_CONSISTENCY.

5. Correct any table classification issues by using the RSDU_TABLE_CONSISTENCY report with the CL_SCEN_TAB_CLASSIFICATION check selected.
6. Correct any partitioning specification issues by using the RSDU_TABLE_CONSISTENCY report with the CL_SCEN_PARTITION_SPEC check selected.
7. Correct table location issues by opening RSDU_TABLE_CONSISTENCY, typing “expert” into the command bar, and turning on the “enable table location check” option. Use the new CL_SCEN_TABLE_LOCATION check option to repair table location issues.

Remarks:

Most of these inconsistencies can be repaired directly in the database. If for some reason RSDU_TABLE_CONSISTENCY does resolve the issue:

• Symptoms 1 & 2 can be corrected by following SAP note 2046987.
• Symptom 3 & 4 can be corrected by following SAP note 2103469.

See Also

SAP Note 1695778 Partitioning of BW tables in the SAP HANA database

Keywords

BW;Hana;RSDU_TABLE_CONSISTENCY;RSMIGRHANADB;Hana-optimized;InfoCube;DSO;PSO;distribution;

Header Data

Released On	23.04.2015 22:53:23
Release Status	Released to Customer
Component	HAN-DB-ENG-BW SAP HANA BW Engine
Other Components	BW-SYS-DB BW Database Platforms
Priority	Normal
Category	How To
Database	HDB 1.0