Material Number: 50131774docshare01.docshare.tips/files/30511/305119138.pdfWhat is really new in SAP...

HA215 Coll: 10

Material Number: 50131774

Training Manual

HA215

SAP HANA Performance optimization and in-depth administration knowledge

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]



SAP SE Copyrights and Trademarks© 2015 SAP SE. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

• Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

• IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System zlO, System z9, zlO, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/0S, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, P0WER6+, P0WER6, P0WER5+, P0WER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks 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 either trademarks or registered trademarks of

Adobe Systems Incorporated in the United States and/or other countries.• Oracle is a registered trademark of Oracle Corporation• UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.• Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems, Inc.• HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.• Java is a registered trademark of Sun Microsystems, Inc.• LabNetscape.• SAP, SAP Fiori, SAP SAPUI5, R/3, SAP Fiori, SAP NW Gateway, SAP NetWeaver, Duet, PartnerEdge,

ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries.

• 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 Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.



http://www.sap.com

CONTENTS

ABOUT THIS HANDBOOK................................................................................................................................. 4

UNIT 1: SAP HANA SHORT INTRODUCTION.................................................................................................. 5Lesson 1 : SAP HANA and Threads........................................................................................................................7

UNIT 2 TOOLS FOR ANALYSIS....................................................................................................................... 24Lesson HANA Studio / HANA Cockpit.................................................................................................................. 25Exercise : Analysis of threads with HANA Studio and HANA cockpit.............................................................36Lesson DBA/DBOS.............................................................................................................................................. 64Exercise . Thread and DBA cockpit...................................................................................................................... 70Lesson : Solution Manager..................................................................................................................................... 78Lesson WEB based developer Workbench......................................................................................................... 97UNIT 3 ROOT CAUSES FOR PERFORMANCE PROBLEMS...................................................................... 102Lesson : Memory consumption / hdbcons....................................................................................................... 103Lesson Parameters...............................................................................................................................................136Lesson Mini Checks..............................................................................................................................................147Exercise Implementation Mini Checks and their use...................................................................................... 153Lesson CPU realted issues.................................................................................................................................. 170Lesson : Disk related issues................................................................................................................................ 176Lesson Delta merge compression......................................................................................................................185Lesson Transactional problems.......................................................................................................................... 190Lesson system hanging situation........................................................................................................................204Lesson Workload Management............................................................................................................................207UNIT 4 DAY TO DAY PERFORMANCE BUSINESS.....................................................................................212Unit 4 ........................................................................................................................................................................ 213Topic : Troublesshooting authorization problems...........................................................................................225UNIT 5 STATEMENT & APPLICATION PERFORMANCE ANALYSIS........................................................227Unit 5 : Statement & Application Analysis......................................................................................................... 228Lesson SQL Statement Analysis and optimization - SQL traces.................................................................229Lesson Query plan analysis................................................................................................................................ 234Exercise Query Plan.............................................................................................................................................. 242UNIT 6 PERFORMANCE ANALYSE IN S/4 HANA....................................................................................... 269UNIT 6 : Performance Analyse im Backend....................................................................................................... 270Lesson Important transaction for analysis in S/4 HANA.................................................................................271Exercise : Analyse SAP - ERP Backend..............................................................................................................312

UNIT 7 ADDITIONAL ANALYSIS TOOLS FOR SUPPORT.......................................................................... 360



About This Handbook

This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. American English is the standard used in this handbook. The following typographic conventions are also used:

Use Example/Visualization

D em onstration by InstructorA hint or advanced detail is shown or clarified by the instructor - please indicate reaching any of these points to the instructor

W arning or CautionA word of caution - generally used to point out limitations or actions with potential negative impact that need to be considered consciously AHintA hint, tip or additional detail that helps increate performance of the solution or help improve understanding of the solution (DA dditional in form ationAn indicator for pointing to additional information or technique beyond the scope of the exercise but of potential interest to the participant CDD iscussion /G roup ExerciseUsed to indicate that collaboration is required to conclude a given exercise. Collaboration can be a discussion or a virtual collaboration. 0U ser In terface T ext Find the Flavor Gallery button

Solution or SAP S pecific term E.g. Flavors are transaction specific screen personaslization created and rendered using SAP Screen Personas.



Unit 1: SAP HANA short introduction

e For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]


Unit 1 Introduction



Lesson 1: SAP HANA and Threads



SAP HANA is famous for its performance , why we need this course about Performance ?

For sure ...With SAP HANA, you can analyze data at incredible speeds, for example, with scans of 1 billion rows per second per core and join performance of 10 million rows per second.

However, such results are only possible if the system is monitored and performance issues are kept to a minimum.

This course will give methods to the hand to identify and resolve specific performance issues and what you can do to enhance the performance of your SAP HANA database in the following areas:

• Host resources (CPU, memory, disk)• Size and growth of data structures• Transactional problems• SQL statement performance• Security, authorization, and licensing• Configuration

© 2014 SAP SC or an SAP affiliate company AN rights reserved

Image 3: SAP HANA is famous for its performance, why we need this course about Performance?

Finally all the fast things like Formula 1, ICE, Shinkansen, and Maglev need continuously maintenance and control.

But extremely important is that the new generation of ERP -System S/4 HANA achieving its full potential only with SAP HANA.

Therefor please let’s have a look only for one slide what are the benefits.



SAP HANA importance is growing in light of S/4 HANA

SAP HANA

• In-memory platform

2011

^ I SAP SAP SAP^ Business Business Simple

^ Warehouse Suite FinanceA powered ^■p o w ered ^ p o w e re d

A by SAP W by SAP W by SAPM HANA V A HANA W A HANA

• Real-time analysis ■ Real-time reporting

• Real-time business• OLAP and OLTP

together

1 Instant financial insightNo aggregates • Simplified data model

2012

SAP HANA • Single source of • New user experienceEnterprise Cloud for truth ■ Advanced processingSAP Business Suite on SAP HANA

• Choice of deployment

1• Multitenancy

2013 2014 2 0 1 5

SAP S/4HANAis the next generation business suite to help lines of business and industries run simple, with all that only HANA can do. SAP S/4HANA combines the most recent innovations (SAP HANA platform, SAP Fiori UX) with +40 years of experience in mastering complex industry challenges in a new Suite that caters to digital, networked economy

© 2014 SAP S£ or an SAP affiliate company All rights reserved

Image 4: SAP HANA importance is growing in light of S/4 HANA

What is really new in SAP S/4HANA compared to SAP Business Suite powered by SAP HANA?

• First, enterprises can now easily connect to people, devices, and business networks to deliver new value to their customers on any channel - the Internet of Things and Big Data become accessible to any business.

• Second, enterprises can dramatically simplify their processes, drive them in real-time and change them as needed to gain new efficiencies - no more batch processing is required.

• And finally, business users can now get any insight on any data from anywhere in real-time: planning, execution, prediction, and simulation - decisions may be made on the fly with a high level of granularity for faster business impact.

From an IT value perspective, this means that S4/HANA creates unique opportunities to simplify the landscape and help reduce total cost of ownership (TOO) with SAP HANA as the great simplifier.



The red line of HA215

SAP S/4HANA Real-Time Analytics ArchitectureFoundation for New Class of Applications

Unit 6SAP S/4HANA

applications

SAP Netweaver PLATFORM

d SAP HANA Database Layer

Unit 2 - 5

[Operational | Reporting

| latency'

S A P H A N A View s (Virtual Data Model)Core Data Services (CDS)

Phystcal Tables

I“ Applications (incl. insight-to-

— action)

QueryTools

© 2014 SAP SE or an SAP affiliate company All rights reserved

Image 5: The red line of HA215

Let us first consider a usually landscape with:

SAP HANA Netweaver Platform

An ERP - System preferable S/4 HANA

BW -System and Operational Reporting

In HA215 it is focused on SAP HANA Database Layer in four units and in methods of performance analyze in S/4 HANA applications and BW.



ISAP HANA Database Layer

Analyse Tools - Unit 2


Image 6: Units inside HANA Database layer



Main Components of the SAP HANA System


Image 7: Main Components of the SAP HANA System

An SAP HANA system consists of several servers, the most important of which is the index server. The index server contains the actual data stores and the engines for processing the data.

Index serverThe index server contains the actual data stores and the engines for processing the data.

Preprocessor serverThe preprocessor server is used by the index server to analyze text data and extract the information on which the text search capabilities are based.

Name serverThe name server owns the information about the topology of the SAP HANA system.In a distributed system with instances of the SAP HANA database on multiple hosts, the name server knows where the components are running and which data is located on which server.

XS server



SAP HANA Extended Application Services (SAP HANA XS) provides applications and application developers with access to the SAP HANA database using a consumption model that is exposed via HTTP. In addition to providing application-specific consumption models, SAP HANA XS also host system services that are part of the SAP HANA database, for example: search services and a built- in Web server that provides access to static content stored in the SAP HANA repository.

Compile serverThe compile server performs the compilation of stored procedures and programs, for example, SQLScript procedures. It runs on every host and does not persist data.

Script serverThe script server is used to execute application function libraries written in C++. The script server is optional and must be started manually. For more information, see SAP Note 1650957.

SAP Web DispatcherThe Web Dispatcher processes inbound HTTP and HTTPS connections to XS services.

SAP start serviceThe SAP start service is responsible for starting and stopping the other services in the correct order. It also performs other functions, such as monitoring their runtime state.



SAP HANA Database Landscape


Image 8: SAP HANA Database Landscape

The name server of one of the SAP HANA instances acts as the cluster manager that pings all hosts regularly. If a failing host is detected, the cluster manager ensures that the standby host takes over the role and the failing host is no longer allowed write access to the files (called fencing) so that they do not become corrupted



What is a Thread ?

A thread of execution is the

smallest sequence of programmed

instructionsA thread is a

component of a process.

Process

execution, running on a single processor

The SAP HANA work, like executing of SQL statements or background tasks is performed by threads.Each SAP HANA process like indexserver or xsengine consist of a set of threads.Thread samples are regular samples of thread activities which are historized.


Image 9: What is a Thread?

So threads are only active for a very short time. This short time frame also explains why you can see these threads only for your own user and not for others.

Service thread samples are a helpful source of information in order to understand the database load in the past. See SAP Note 2114710 for more information.



For what purpose do I need to evaluate the SAP HANA thread activities?

By checking SAP HANA thread information you can get a current or historic snapshot of thread activities.

This can help you to answer questions related to the SAP HANA workload, e.g.:

• Activities responsible for CPU consumption

> Activities responsible for lock situations

• Activities responsible for bad performance

Expensive SQL statements.


Image 10: For what purpose do I need to evaluate the SAP HANA thread activities?



Where do I find information about SAP HANA threads?

Information about current SAP HANA threads can be found at the following locations:

SAP HANA Studio -> Administration -> Performance -> Threads

B “fb SYS

Monitoring view M_SERVICE_THREADS 1® M_S£RVICE_n*EADS I s M_SERVICe_Trt*E*0_CAaSTACKS V M.SERVICE_TW(EA0.5AMPIES

DBACOCKPIT-> Performances Threads


Image 11: Where do I find information about SAP HANA threads?

Information about historic thread activities are available at:

Monitoring view: M_SERVICE_THREAD_SAMPLES

Retention is usually at least 2 hours

For more details see SAP Note 2088971

History: HOST_SERVICE_THREAD_SAMPLES

Only available if embedded statistics server is used.

Default retention time may be quite small (1 day)Retention should be increased to 42 days as described in SAP Note 2147247 ("What is a good retention time for statistics server histories?")

SQL: "HANA_Threads_ThreadSamples_FilterAndAggregation" (SAP Note 1969700)

SQL: "HANA_Threads_ThreadSamples_AggregationPerTimeSlice" (SAP Note 1969700)



Statement Execution and Resource Handling

Application A

'statement'

Session Layer

ExecutionPlan

"(simple) OLTP"

SQLExecutor

0 5Thread-Pool

'assign available threads *

i V

Plan"(complex) OLAP" Operators Jobs

'read config data"

mi files

system-tables

3JobExecutor

Oftop *

'may delegate statement execibon’’

"assign available threads'

"set statement-context per session"

t mm-2HANA system-tasks'

Information about resource policy for memory, concurrency, priority for a statement

Session Context for Application A


Image 12: Statement Execution and Resource Handling

Different from many other DBMS is that the session itself does not permanently map to a specific process or thread in SAP HANA!

Let’s give you an example:

The session with ConnectionID 1001211 started to work on the create ..column table .... with data“command. The purpose of this command is to copy an existing table with the records stored in it.To process the command, the connection got assigned to a SQLExecutor thread with Thread Id 23045.

Because SAP HANA is a column store database, the task of copying table can be split into copying each column. Each column can independently be copied, which means that it can be done in parallel.

To work on these column in parallel a thread for each column is required

And also these worker threads need to be controlled and coordinated!



Which information are available for a thread?

' n T h re a d D e ta ils

I wdflbmt7194 32007I wdflbmt7194 32001

wdflbmt7194 Caned Operations

wdflbmt7194 Show Detailswdflbmt7194 Navigate To ►wdflbmt7!94 Configure Trace ►wdflbmt7194

Group and Sortwdflbmt7194| wdflbmt7194 32010t 4 =1

ptatus: nul Host: wdflbmt7194 Port: 32003 Service: indexserver Hierarchy: 300037/-1/2S Connection ID: 300037 Thread ID: 1S3S CaMng:Caler: 1484@>wdfbmt7194:32003 Thread Type: Request Thread Method: core/stat Thread Det ad:Duration (m s): 0User: SYSTEMAppfccation User: train-01CPU Tme: -1Cumulative CPU Time: -1Transaction ID : 2SUpdate Transaction ID : *1Thread Status: RunningConnection Transaction ID : 2SConnection Start Tm e: 2015-08-18 10:57:48.016405Connection Idle Time (m s): 0Connection Status: RUNNINGClient Host: wdfbmt5048.vvdt.sap.corpClient IP: 10.22.112.66Client PID: 2712Connection Type: RemoteO w n Connection: TRUEMemory Size per Connection: -1Auto Commit: TRUELast Action: ExecuteStatementCurrent Statement ID : 1288651403172305Current Operator Name: HASH JO IN (LEFT O U TER )

y g jx

© 2014 SAP S t or an SAP affiliate company All rights reserved

Image 13: Which information are available for a thread?



Where comes the statics from ?

|Performance'"i flumes Configuration System Information Diagnosis Fles Trace Configuration

— -------1------------------1-------- 1--- 1ed Transactions ’ SQl Plan Cache Expensive Statements Trace 3o6 Process Load

» ] Service: <AI> w Thread Type: ~T 1 ▼] X 1* Group and sort P Create cal stacks rtdeSessons * J Sav

I Port Service Connection ID | Thread ID | CaAng 1 Caler 1 Thread Type32001 name server •1 0 Main32010 compHeserver -1 0 Man32002 preprocessor -1 0 Man3200732003 ndexserver - l 28961 Worker Thread (StatisticsServer)32003 ndexserver •1 28962 Worker Thread (StatisticsServer)32003 ndex server -1 28964 Worker Thread (StatisticsServer)3200332003 ndexserver 301233 12894 | 28919 28894 JobWorker32007 xsengne 301233 28995 wdftmt7194:* Request32006 webdispatcher 301233 29428 wdffemt7194:# Request32010 compileserver 301233 28983 wdflbmt7194:* Request32001 name server 301233 28534 wdffcmt7194:* Request32002 preprocessor 301233 28770 wdflbmt7194:* Request32003 ndexserver 301233 2892S 28919®wdffcmt... Request

The Statistics Server is now embedded in the Index Server. It needs only ~5% of the total memory.

© 2014 SAP SE or an SAP afhkate company AH rights reserved

Image 14: Where comes the statics from?

As an SAP HANA database administrator, you need to monitor the status of the system and its services and the consumption of system resources. When critical situations arise, you need to be notified so that you can take appropriate action in a timely manner. For data center operation and resource allocation planning, you need to analyze historical monitoring data. These requirements are met by SAP HANA's internal monitoring infrastructure. A central element of this infrastructure is, depending on your system set-up, the statistics service or the statistics server.

The statistics service (or statistics server) collects and evaluates information about status, performance, and resource consumption from all components belonging to the system. In addition, it performs regular checks and when configurable threshold values are exceeded, issues alerts.

For example, if 90% of available disk space is used, a low priority alert is issued; if 98% is used, a high priority alert is issued

The monitoring and alerting features of the SAP HANA database can be performed by 2 mechanisms: the statistics server or the statistics service.



The "new" Statistics Server (is available from revision 74 onward) is also known as the embedded Statistics Server or Statistics Service.

Prior to SP7 the Statistics Server was a separate server process - like an extra Index Server with monitoring services on top of it. But it can migrate to the new statistics by following SAP note 1917938.

Data is collected remotely from the other servers and stored in measurement tables in the statistics server.

The Statistics ServiceThe statistics service is a simplified, more flexible implementation of the statistics server.

It is implemented by a set of tables and SQLScript procedures in the master index server and by the statistics scheduler thread that runs in the master name server. The SQLScript procedures either collect data (data collectors) or evaluate alert conditions (alert checkers). Procedures are invoked by the scheduler thread at regular intervals, which are specified in the configuration of the data collector or alert checker. Data collector procedures read system views and tables, process the data (for example, if the persisted values need to be calculated from the read values) and store the processed data in measurement tables for creating the measurement history.

Alert checker procedures are scheduled independently of the data collector procedures.

They read current data from the original system tables and views, not from the measurement history tables. After reading the data, the alert checker procedures evaluate the configured alert conditions. If an alert condition is fulfilled, a corresponding alert is written to the alert tables. From there, it can be accessed by monitoring tools that display the alert. It is also possible to have e-mail notifications sent to administrators if an alert condition is fulfilled. Depending on the severity level of the alert, summary emails are sent with different frequency (hourly, every 6 hours, daily). You can also trigger alert checker procedures directly from monitoring tools (for example, SAP HANA studio and SAP HANA cockpit).

Statistics Server or Statistics Service?

As of revision 93, the embedded statistics service is enabled by default after installation or upgrade.



Where comes the statics from ?

$ ~ a l a _SYS_STATISTICS• •

B & TablesI T a O B A L .D E C _ E X T R A C T O R _ S T A T U S .B A S E

GLOBAL _D ISKS_BASE

T T a O B A L .IN T E R N A L .E V E N T S .B A S E

T T G L O B A L _P E R S IS TE N C E _S TA TIS TIC S _B A S E

® G L 0 8 A L _ R 0 W S T 0 R E _ TA B L E S _ S IZ E _ B A S E

f f l GLOBAL _TA B LE _C O N S IS TE N C Y _B A S E

® a O B A L _ T A B L E .P E R 5 IS T E N C E _ S T A T IS T IC S .B A S E

= L C L P E R .A L E R T .B L O C K E D .T R A N S A C T IO N S .P E R C E N T AGE

= HELPER .A L E R T .C H E O C .D IS K .S P A C E .L A S T V A L U E S

= H E L P E R .A L E R T .C H E C K .H O S T S .C P U .L A S T V A L U E S

" H ELPER_ A L E R T .C H E O C _ IN A C T IV E _ S E R V IC E S .A G E


Image 15: Schema _SYS_STATISTICS

Monitoring and alert information are stored in database tables in a dedicated schema (_SYS_STATISTICS). From there, the information can be accessed by administration tools, such as the SAP HANA studio, SAP HANA cockpit, or SAP DB Control Center.



SAP HANA Platform SPS 10 Document Version 10 - 2015-06-24

SAP HANA Troubleshooting and Performance Analysis Guide

Note: 2000000 FAQ: SAP HANA Performance Optimization


Image 16: Info sources

This note is the universal starting point for different topics around troubleshooting and performance analysis.



Unit 2 Tools for Analysis

e For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]


SAP HANA Admin and Monitoring Tools

Image 18: Lesson HANA Studio / HANA Cockpit



Material Number: 50131774docshare01.docshare.tips/files/30511/305119138.pdfWhat is really new in SAP...

Documents

Transcript of Material Number: 50131774docshare01.docshare.tips/files/30511/305119138.pdfWhat is really new in SAP...