How to Configure SAP HANA Table-Distribution for …...How To Configure SAP HANA Table Distribution for BW-on-HANA Scale-Out Systems August 2014 3 1.1 General Recommendation This section

SAP Netweaver How-To Guide SAP NetWeaver BW 7.30 SP5 / BW 7.40 SP5 on HANA and more current versions

SAP HANA™ Appliance SPS7+ and more current versions

Applicable Releases:

SAP HANA 1.0 SPS07+

This How to Guide should help to better understand the various concepts of SAP HANA and SAP BW powered by SAP HANA. The purpose of these documents is to deliver additional information besides SAP Help and Blogs to get a better understanding of the concepts of SAP HANA and SAP BW on HANA.

Version 1.0

June 2014

How to Configure SAP HANA Table-Distribution for BW-on-HANA Scale-Out Systems

© Copyright 2014 SAP AG. All rights reserved. No part of this publication may be reproduced or tran smitt ed in any form or for any purpose wi thout the express p ermission of SAP AG. Th e information cont ained herein may b e changed wi thout prior notice.

Some softw are products market ed by SAP AG and its dist ributors contain propri et ary softw are component s of other software vendors. Microsoft, Windows , Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM , DB2, D B2 Universal Datab ase, Syst em I, Syst em i5, Syst em p, Syst em p5, Syst em x, System z, Syst em z 10, System z9, z 10, z9, iSeri es, pSeri es, xSeries , zSeri es, eServ er, z /VM , z/OS, i5 /OS, S/39 0, OS/390, OS/400, AS/4 00, S/39 0 Parall el Enterpris e Serv er, Po werVM, Pow er Archit ecture, P OWE R6+, PO WER6 , PO WER5 +, PO WE R5, PO WER, OpenPow er, PowerPC, Bat chPipes, Bl adeC enter, System Storage, G PFS, H ACMP, RET AIN, D B2 Connect, RACF, Redbooks, O S/2 , Parall el Sysplex, MVS/E SA, AIX,

Intelligent Miner, WebSph ere, N etfinity, Tivoli and Informix are trademarks or regist ered trad emarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are eith er trademarks or regist ered t rad emarks of Adobe Systems In corporated in the United Stat es and /or other countries. Oracl e is a regist ered trad emark of Oracle Corporation.

UNIX, X/Op en, OSF /1, and Motif are regist ered trademarks of the Open Group.

Citrix, ICA, Program N eighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trad emarks or regist ered trad emarks of C itrix Systems, Inc.

HTML, XML, XH TML and W3C are t rad emarks or r egistered trademarks of W3C®, World Wid e Web Consortium, M ass achus etts Institut e of Technology.

Jav a is a registered trademark of Sun Micro syst ems, Inc. Jav aScript is a registered trademark of Sun Microsyst ems, Inc., used under licen se for technology invented and i mplement ed by N etscape.

SAP, R/3, SAP N etWeaver, Duet, Partn erEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP product s and se rvices mentioned herein as w ell as thei r respective logos are trademarks or regist ered trad emar ks of SAP AG in Germany and other co untries.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other

Business Objects products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of Business

Objects Software Ltd. Business Objects is an SAP company. Sybase and Adapti ve Serv er, iAnywh ere, Sybas e 365, SQL Anywhere, and other Sybas e products and services mentioned herein as well as thei r respective logos are trademarks or regist ered t rad emarks of Sybase, Inc. Sybase is an SAP comp any.

All other product and service names mentioned are the trademarks of their resp ectiv e co mpani es. Dat a cont ained in this document serves information al purposes only. N ational product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may b e rep roduced, copied, or trans mitted in an y form or for any purpos e without the express prior writ ten permis sion of SAP AG.

This document is a preli minary v ersion and not subject to your licens e agreement or any other agreement with SAP. This document contains only int ended strat egies, d evelop ments , and functionalities of the SAP® product and is not intended to be binding upon SAP to an y parti cular course of business , product strategy, and /or dev elopment. Pl eas e note that this docu ment is subject to ch ange and may be ch anged by SAP at any ti me without notice.

SAP assu mes no responsibility for errors or omissions in this document. SAP does not w arrant the accuracy or compl et eness of the information, text, graphics, links , or other items contained within this mat erial . This document is provided without a warrant y of any kind, either express or i mplied, including but not limited to the i mplied w arranties of merchant ability, fitness for a particular purpose, or non -infringement.

SAP sh all hav e no liability for damages of any kind including without limit ation direct , special, indirect , or consequ ential d amages that may result from the us e of these materi als. Thi s limit ation shall not apply in cases of intent or gross negligence. The statutory liability for p ersonal injury and defectiv e products is not affected. SAP has no control over the information t hat you may access th rough the use of hot links contained in thes e materials and does not endors e your use of third-party Web pag es nor provide an y warranty whatso ever rel ating to third-part y Web pages .

SAP “How-to” Guides are intended to simplify the product implement-

tation. While specific product features and procedures typically are

explained in a practical business context, it is not implied that those

features and procedures are the only approach in solving a specific

business problem using SAP NetWeaver. Should you wish to receive

additional information, clarification or support, please refer to SAP

Consulting.

Any software coding and/or code lines / strings (“Code”) included in this

documentation are only examples and are not intended to be used in a

productive system environment. The Code is only intended better explain

and visualize the syntax and phrasing rules of certain coding. SAP does

not warrant the correctness and completeness of the Code given herein,

and SAP shall not be liable for errors or damages caused by the usage of

the Code, except if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Any code change

in these components may cause unpredictable and severe malfunctions

and is therefore expressively prohibited, as is any decompilation of these

components.

Any Java™ Source Code delivered with this product is only to be used by

SAP’s Support Services and may not be modified or altered in any way.

Document History

Document Version Description

1.00 Final version of this guide

Typographic Conventions

Type Style Description

Example Text Words or characters quoted

from the screen. These

include field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

Cross-references to other

documentation

Example text Emphasized words or

phrases in body text, graphic

titles, and table titles

Example text File and directory names and

their paths, messages,

names of variables and

parameters, source text, and

names of installation,

upgrade and database tools.

Example text User entry texts. These are

words or characters that you

enter in the system exactly

as they appear in the

documentation.

<Example

text>

Variable user entry. Angle

brackets indicate that you

replace these words and

characters with appropriate

entries to make entries in the

system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Description

Caution

Note or Important

Example

Recommendation or Tip

How To Configure SAP HANA Table Distribution for BW-on-HANA Scale-Out Systems

August 2014 1

Table of Contents

1. Introduction .......................................................................................................................... 2

1.1 General Recommendation .......................................................................................... 3

1.2 BW InfoCube & DSO Standard table Partitioning ....................................................... 4

2. Configuration of Table-Partitioning and Table-Distribution in Scale-Out System

Configurations ...................................................................................................................... 5

2.1 SAP HANA Preparation ............................................................................................... 6

2.1.1 Role of Table TABLE_PLACEMENT ................................................................ 7

2.1.2 Configuration settings in table TABLE_PLACEMENT .................................... 8

2.2 BW System Preparation ............................................................................................ 10

2.2.1 Verify Table Consistency Check .................................................................... 11

3. Execute “Optimize Table Distribution” Operation ............................................................. 19

3.1 Step-by-Step Procedure ........................................................................................... 19

3.1.1 Generate the Table Redistribution Plan ....................................................... 20

3.1.2 Verify and Execute the Table Redistribution Plan........................................ 23

4. Summary ............................................................................................................................. 27

5. Appendix ............................................................................................................................. 28


August 2014 2

1. Introduction

The topic of SAP HANA Table Partitioning in BW-on-HANA Scale-Out Systems becomes relevant when table sizes and table growth rates need to aligned and HANA-Memory allocation has to be balanced across the HANA Slave nodes in a Scale-Out System configuration. This option further improves the overall system stability (reduce out-of-Memory situations), performance and enables the system administrator to optimize the Scale-Out System setup.

We assume that the reader has a good understanding on the topic of SAP HANA Table Partitioning and Scale-Out System Configuration including the related framework.

SAP HANA Table Partitioning needs to be separated in two major sections:

1) SAP HANA Table Partition and 2) SAP HANA Table Partition Specification (Partition Spec)

Partitioning is available for column store tables only.

A non-partitioned table cannot store more than 2 billion rows. The limitation can be eliminated by distributing the rows to several table partitions, where the individual table partitions can be located on a single-host system or distributed across a scale-out system.

The topic of SAP HANA Table Partitioning is well described in the SAP HANA Cookbook – accessible via below link:

https://cookbook.experiencesaphana.com/bw/operating-bw-on-hana/hana-database-administration/system-configuration/partitioning-and-distribution-large-tables/

The SAP HANA Administration Guide within http://help.sap.com provides the relevant information on the topic of “Table Distribution in SAP HANA” http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf

The SAP HANA Landscape Redistribution with SP6 is also described in below SCN blog: http://scn.sap.com/community/hana-in-memory/blog/2013/09/03/sap-hana-landscape-redistribution-with-sp6



http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf

http://scn.sap.com/community/hana-in-memory/blog/2013/09/03/sap-hana-landscape-redistribution-with-sp6




August 2014 3

1.1 General Recommendation

This section provides you with a general recommendation on how to analyze and optimize your BW Applications for migration to SAP Netweaver BW on HANA.

SAP Note 1729988 (SAP Netweaver BW powered by SAP HANA – Checklist Tool) is a great starting point if you are looking for a quick and easy way to check your BW system for certain types of BW-on-HANA migration topics including Transformation and Optimization potential.

SAP Note 1909597 (SAP Netweaver Migration Cockpit for SAP HANA) is referred to with subsequent links to further valuable check and optimization Notes, like

1908367 SAP NetWeaver BW Transformation Finder

1847431 SAP NetWeaver BW ABAP Routine Analyzer

1736976 Sizing Report for BW on HANA

http://service.sap.com/sap/support/notes/1729988


https://websmp130.sap-ag.de/sap/support/notes/1908367




August 2014 4

1.2 BW InfoCube & DSO Standard table Partitioning

The SAP Netweaver BW on HANA system creates BW InfoCube and BW DSO InfoProvider with some specific standard table definitions, where the 2 billion rows limitation per Table Partition need to be overcome in certain customer situations.

BW InfoCube F-Table Partitioning (incl. non-cumulative Keyfigure / Inventory InfoCube)

The design of the HANA-optimized InfoCube Partitioning is pre-defined by SAP BW and need to stay unchanged.

HANA-optimized Inventory InfoCubes are setup with first level partitioning (ROUNDROBIN n) and second level partitioning (RANGE 0,1,2,*).

The number of first level partitions is based on rules depending on the size of the InfoCube.

Standard Partitioning of F-Table ‘/BIx/F<techn. Name>’:

ROUNDROBIN 1; RANGE KEY_<tech. Name>P 0,1,2,* You’ll find further details starting with chapter 2. Configuration of Table-Partitioning and Table-Distribution in Scale-Out System Configurations on the Table-Partition Partitioning Enhancement to overcome the 2 billion row limitation per Partition. The Table Sub-Partitioning need to stay stable and the it’s only allowed to change the first level Table Partitioning (ROUNDROBIN n) to specify the number of table partitions.

Please also check the relevant Document on SAP First Guidance – SAP Netweaver BW 7.30 on HANA Inventory InfoCubes, available at http://scn.sap.com/docs/DOC-28525

BW DSO Partitioning

The design of the DSO Partitioning is pre-defined by SAP BW and need to stay unchanged.

DSO’s are setup with first level partitioning (HASH n) including the DSO Key-Fields.

The numbers of first level partitions are based on rules depending on the size of the DSO.

BW Standard Partitioning of “/BIC/A<tech_name>00”, “/BIC/A<tech_name>40” and “/BIC/<CHANGELOG tech_name>” DSO-Tables

HASH 1 <DSO Key-Fields>

You’ll find further details starting with chapter 2. Configuration of Table-Partitioning and Table-Distribution in Scale-Out System Configurations on the Table-Partition Partitioning Enhancement to overcome the 2 billion row limitation per Partition. The Table Sub-Partitioning need to stay stable and the it’s only allowed to change the first level Table Partitioning (HASH n) to specify the number of table partitions.

http://scn.sap.com/docs/DOC-28525


August 2014 5

2. Configuration of Table-Partitioning and Table-Distribution in Scale-Out System Configurations

The configuration, preparation and execution of Table-Partitioning and –Distribution in Scale-Out System configurations need to be separated into 4 steps

BW System Preparation

BW System Table Consistency Check

Special Table-Partitioning / -Distribution Configuration

Execution of optimize Table Distribution

Please also consider the Blog on “SAP HANA Landscape Redistribution with SP6” available at http://scn.sap.com/community/hana-in-memory/blog/2013/09/03/sap-hana-landscape-redistribution-with-sp6 and always check first if there are additional SAP notes available on components HAN-STD-ADM-DBA or HAN-DB-ENG-BW to be applied to your system BEFORE moving on.

Here are some common SAP notes to be considered, like

1908073 BW on HANA Scale Out: Table distribution/partitioning

1908082 HANA DB: Priorities of TABLE_PLACEMENT entries

1908133 Landscape Redistribution – force split rules

The process of adjusting table partitioning in scale-out system / shared-nothing database configurations is a complex topic, where it’s highly recommended to take a full system backup before finally executing the “Optimize Table Distribution” Step to be prepared for unforeseen error situations.





August 2014 6

2.1 SAP HANA Preparation The SAP HANA “Optimize Table Distribution” Run leverages the configuration setting in "_SYS_RT"."TABLE_PLACEMENT" to control the create table partition creation and table partition distribution process (across the Scale-Out System Slave Nodes)

The main task of the Table-Distribution / -Partitioning activity will be performed from the SAP HANA Studio, where additional configuration is required.

Additional records need to be added to a central table “_SYS_RT”.”TABLE_PLACEMENT”, which is leveraged by any SQL-DDL Statement executed on the BW-on-HANA system.

Please check SAP Note 1908075 (BW on SAP HANA SP06: Landscape redistribution) incl. the referenced SAP Notes like 1908073 (BW on HANA scale out: Table distribution/partitioning) and apply all listed HANA parameter & add the initial list of TABLE_PLACEMENT records and SQL GRANT commands to the system.

Next to the initial records added to TABLE_PLACEMENT table - specifying the default partition criteria’s on the level of #records (like: If a table contains less than 40 million records, it stays with one table partition/part. If a table contains more than 40 million records, it is split into three table partitions/parts …) - it’s also possible overrule the default settings and specify BW-Object specific partition criteria’s.

Default Configuration: #Record to Table partition/parts (Slave nodes) mapping:

#Records #Table partitions/parts (Slave nodes)

< 40 million 1

40 - 120 million 3 (or max. #Slave Nodes)

120 - 240 million 6 (or max. #Slave Nodes)

> 240 million 12 (or max. #Slave Nodes)




August 2014 7

2.1.1 Role of Table TABLE_PLACEMENT

The table “_SYS_RT”.”TABLE_PLACEMENT” is leveraged by SAP HANA for any executed SQL-DDL Statement, which also includes the handling of tables DDL-Statements during the import of SAP Transport-Requests.

The configuration records added to “_SYS_RT”.”TABLE_PLACEMENT” are specifying the table partitioning and distribution arguments, where the linkage to the “SYS”.”TABLE_GROUPS” is based on the GROUP_NAME column.

DSO “DSO1” created

The records in the table “SYS”.”TABLE_GROUPS” are automatically updated once a SQL-DDL Statement has been performed on SAP HANA.

Generated entries in table “SYS”.”TABLE_GROUPS” for GROUPNAME “DSO1”

The records in the table “_SYS_RT”.”TABLE_PLACEMENT” need to be maintained on the level of SCHEMA_NAME, GROUP_NAME, GROUP_TYPE, MIN_ROWS_FOR_PARTITIONING, INITAL_PARTITIONS, REPARTITIONING_THRESHOLD and LOCATION. Only records of persisted BW-Objects (like DSO and InfoCubes) are being leveraged, where MetaData Objects (like BW SPO’s, BW InfoSet, BW Multi-Provider and BW Composite-Provider) connected persisted BW-Objects need to be derived first.

When specifying a BW Provider (e.g. DSO) - only the DSO GROUP_NAME (derived from table “SYS”.”TABLE_GROUPS”) need to be added to “_SYS_RT”.”TABLE_PLACEMENT”, as the system will automatically derive the DSO Active-, Queue- and Changelog-Table names.

TABLE_PLACEMENT table structure and example data for DSO1 relevant GROUP_NAME: SCHEMA_NAME

TABLE_NAME

GROUP_NAME

GROUP_TYPE

SUBTYPE

MIN_ROWS_FOR_PARTITIONING

INITAL_PARTITIONS

REPARTITIONING_THRESHOLD

LOCATION

<DB-SCHEMA>

DSO1 sap.bw.dso

1 6 0 slave


August 2014 8

2.1.2 Configuration settings in table TABLE_PLACEMENT

This section provides you the details on how to configure the detail settings in "_SYS_RT"."TABLE_PLACEMENT” by BW-Object GROUP_NAME objects, with reference to records listed in table “SYS”.”TABLE_GROUPS_”.

The detail settings for BW InfoProvider DSO1 has to be maintained , where all relevant DSO tables are marked as GROUP_NAME “DSO1” in “SYS”.”TABLE_GROUPS_”.

SQL-Statement to add configuration detail settings for BW DSO-InfoProvider DSO1 to table "_SYS_RT"."TABLE_PLACEMENT”: insert into "_SYS_RT"."TABLE_PLACEMENT" values ('<DB-SCHEMA>', '', 'DSO1', 'sap.bw.dso', '', 1, 6, 0, 'slave' );

TABLE_PLACEMENT table structure and example data for DSO1 relevant GROUP_NAME: SCHEMA_NAME

TABLE_NAME

GROUP_NAME

GROUP_TYPE

SUBTYPE

MIN_ROWS_FOR_PARTITIONING

INITAL_PARTITIONS

REPARTITIONING_THRESHOLD

LOCATION

<DB-SCHEMA>

DSO1 sap.bw.dso

1 6 0 slave

The records in the table "_SYS_RT"."TABLE_PLACEMENT" provide the option to tweak the generated SQL-DDL statements to create tables in a partitioned fashion (1rst Level Table Partitioning) also if the table is created from scratch (0 Records) or hosts < 40 million records, where by default no table partitioning would have been leveraged.

The value in column GROUP_NAME refer to the values in table “SYS”.”TABLE_GROUPS_”. This is the Join-Column between the two tables "_SYS_RT"."TABLE_PLACEMENT" and “SYS”.”TABLE_GROUPS_” to identify the relevant BW-InfoProvider tables (here. GROUP_NAME is DSO1)

The value in column GROUP_TYPE specify the BW InfoProvider type (here: DSO), where also other GROUP_TYPES are available like: sap.bw.cube, sap.bw.iobj, sap.bw.openhub … . Please only consider the potential GROUPS_TYPES in lower-case letters, as the uppercase GROUP_TYPES are no longer considered.

The value in column MIN_ROWS_FOR_PARTITIONS specifies the minimum threshold in number of records to evaluate table partitioning for the corresponding GROUP_NAME tables at the next SAP HANA Optimize Table Distribution Run. By specify the value of 1 (One), also empty GROUP_NAME tables (0 Records) are treated as relevant, as this represents the option to import SAP Transport Requests to the target system and trigger the initial table creation process using the value from column INITIAL_PARTITIONS as the number of table partitions to be created. The value in column REPARTITIONING_THRESHOLD specifies the number of relevant records to repartition existing GROUP_NAME tables by using the value from column INITIAL_PARTITIONS as the number of table partitions to be created. By specify the value of 0 (Zero) no further activities will be performed and only the value from column MIN_ROWS_FOR_PARTITIONING is considered during the next SAP HANA Optimize Table Distribution Run.


August 2014 9

The value in column INITIAL_PARTITIONS specifies the number of table partitions to be created for the corresponding GROUP_NAME tables at the next SAP HANA Optimize Table Distribution Run, if the values from MIN_ROWS_FOR_PARTITIONS and REPARTITIONING_THRESHOLD are met. Recommendation: You’ll achieve the best control on the topic of “Optimize Table Distribution“ process (table partitioning and distribution), if MIN_ROWS_FOR_PARTITIONING value will be set to 1 (One) and REPARTITIONING_THRESHOLD value will be set to 0 (Zero) for the relevant GROUP_NAME’s.

This is a typical scenario if the relevant BW-InfoProvider / Tables have been identified to grow big in terms of #records and size. The GROUP_NAMEs not listed explicitly here are treaded by the default (NO GROUP_NAME specified) “#Record – Table partition/parts (Slave nodes) mapping”

The benefits of this option are related to:

“Efficient” balanced HANA-Memory allocation across the HANA Slave-Nodes for the partitioned tables (not partitioned table are distributed across the HANA Slave-Nodes, leveraging the partitioned tables)

Reduce Out-Of-Memory Situations on single HANA Slave-Nodes can be managed more efficiently which also increase the overall System Stability

Manage “Look-up” BW-InfoProvider / Tables not-to-be-partitioned, as “Look-up SELECT Statements” to partitioned tables setups across HANA Slave-Nodes are way more expensive compared to not-partitioned setups (keep value in column “INITAL_PARTITIONS” always “1”)


August 2014 10

2.2 BW System Preparation

Execute Table consistency check RSDU_TABLE_CONSISTENCY (Transaction SE38)

The RSDU_TABLE_CONSISTENCY report needs to be executed frequently to check all tables of the BW system for consistency and also specify the relevant table-classes.

Please check SAP Note 1756099 (RSHDB: Consistency check for tables (7.30 SP9) ) for enhancements and corrections of the consistency check report RSDU_TABLE_CONSISTENCY for BW tables on the SAP HANA database.

It’s also beneficial to frequently perform checks for all Consistency Checks



August 2014 11

2.2.1 Verify Table Consistency Check

All verified/checked tables and assigned table-classes are stored in the table “SYS”.”TABLE_GROUPS_”.

TABLE_GROUPS_ table structure and example data for DSO relevant tables: SCHEMA_NAME TABLE_NAME GROUP_TYPE SUBTYPE GROUP_NAME

<DB-SCHEMA> /BI0/ADSO100 sap.bw.dso ACTIVE DSO1

<DB-SCHEMA> /BI0/ADSO140 sap.bw.dso QUEUE DSO1

<DB-SCHEMA> /BI0/B00002140000 sap.bw.dso CHANGE_LOG DSO1

Execute Table consistency check RSDU_TABLE_CONSISTENCY (Transaction SE38)


August 2014 12

Output of the Table consistency check with some objects marked as “Red”


August 2014 13

Re-execute Table consistency check RSDU_TABLE_CONSISTENCY (Transaction SE38) with Option “Store issues”


August 2014 14

Output of the Table consistency check “Store issues” with some objects marked as “Red”


August 2014 15

Go back and check the displayed information on identified “issues: 29867”. Press the “Show” button to display the details from last run.

Mark and Double-Click the row from last run.


August 2014 16

Details from last run are displayed. Mark the relevant rows with Status “Repairable” and press “Save”


August 2014 17

Go back. The Number of previous selected and saved rows are displayed (see “selected: 30”)

Check “Repair” and “Execute”


August 2014 18

Result of the Repair-Run is displayed


August 2014 19

3. Execute “Optimize Table Distribution” Operation

The “Optimize Table Distribution Operation” is relevant for HANA Scale-Out System Configurations and can be kicked-off if the previous mentioned settings have been applied to the system.

The “Optimize Table Distribution Operation” is a two-step process (“Save” and “Execute”) to execute the table distribution process.

During the Operation, all Row-Store Tables are moved to the HANA Master Node and all Column-Store Tables are moved and balanced to the HANA Slave Nodes

Please refer to the SAP HANA Administration Guide, Section 4.3.7 Table Distribution in SAP HANA for further details https://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf,

3.1 Step-by-Step Procedure

1. Apply all notes listed in Section 2.1 SAP HANA Preparation of this document and also identify the list of relevant objects to be considered.

2. Create, Verify and Apply Records to be added to Table TABLE_PLACEMENT – described in Section 2.1.2 Configuration settings in table TABLE_PLACEMENT

3. Run report RSDU_TABLE_CONSISTENCY for all available Consistency Checks - described in Section 2.2 BW System Preparation

4. Verify the repair activities suggested by Report RSDU_TABLE_CONSISTENCY- described in Section 2.2.1 Verify Table Consistency Check

5. Verify that all tables are classified correct - described in Section 2.2.1 Verify Table Consistency Check

6. Generate the Table Redistribution Plan – described in Section 3.1.1 Generate the Table Redistribution Plan

7. Verify the Table Redistribution Plan– described in Section 3.1.2 Verify and Execute the Table Redistribution Plan

8. Execute the Table Redistribution Plan – described in Section 3.1.2 Verify and Execute the Table Redistribution Plan

9. Wait for the completion of the Table Redistribution Run, where the duration is pretty much driven by the number of Table Partitions and corresponding data records to be moved to the new target host location. The overall Table Redistribution Run execution should never be stopped or interrupted, as the runtime might exceed +12 hours !

https://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf


August 2014 20

3.1.1 Generate the Table Redistribution Plan

1. Open the SAP HANA Studio – “Administration” Perspective

2. Switch to the “Landscape” – “Redistribution” Tab

3. Select the “Optimize Table Distribution” Operation and click the “Save” button to store the

current Table Distribution configuration.


August 2014 21

4. Click “Next”

5. The current Table Distribution/Redistribution Plan is presented. Click “Execute” to Save.


August 2014 22

6. The current Table Distribution/Redistribution Plan has been successfully saved.


August 2014 23

3.1.2 Verify and Execute the Table Redistribution Plan 1. Open the SAP HANA Studio – “Administration” Perspective

2. Switch to the “Landscape” – “Redistribution” Tab

3. Select the “Optimize Table Distribution” Operation and click the “Execute” button to initiate

a new Table Redistribution Run.


August 2014 24

4. Click “Next”

5. The Table Partition Redistribution Process is executed to calculate the Table Partition

Distribution – based on the TABLE_PLACEMENT configuration records - across the Scale-

Out System Slave Nodes


August 2014 25

6. The Table Partition Redistribution Plan has been calculated and is displayed. Every

Redistribution activity is displayed with the information on Table Name / Table Partition/

Old Partition Spec (current) and the New Partition Spec including the Old (current) Host

(Slave Node) and New Host.

7. Click “Execute” to initiate the Table Redistribution Process. The overall Table Redistribution Run execution should never be stopped or interrupted, as the runtime might exceed +12 hours !


August 2014 26

8. Table Redistribution Process has been successfully completed.


August 2014 27

4. Summary

The HAP offers a great opportunity to use Predictive Analytics or Data Mining functionalities based

on BW data with the power of SAP HANA.

It is possible to analyze the data using different functions or scripts and HANA provides numerous

specialized libraries like PAL, AFL, R to understand the correlation of the data in the existing EDW

and accelerate the usage of the consolidated EWD data for data mining.

By using a SAP HANA database it is recommended to use the SAP HANA Analysis Process instead

of Analysis Process Designer (APD). The process is then performed exclusively in SAP HANA, thus

improving performance dramatically.

The main difference in functionality between the SAP HANA analysis process and APD is that only

InfoProviders that a column view exists for on the SAP HANA database are supported as data

sources.

In the future more and more algorithm will be developed for the usage of the HAP and the

importance of the APD will decrease.


August 2014 28

5. Appendix

www.sap.com/contactsap

http://www.sap.com/contactsap

Documents

How to Configure SAP HANA Table-Distribution for …...How To Configure SAP HANA Table Distribution for BW-on-HANA Scale-Out Systems August 2014 3 1.1 General Recommendation This section