Sei sulla pagina 1di 42
SAP EarlyWatch ® Alert (EWA) Example Setup for SAP HANA February 2015

SAP EarlyWatch ® Alert (EWA)

Example Setup for SAP HANA

February 2015

SAP EarlyWatch ® Alert (EWA) Example Setup for SAP HANA February 2015

Agenda

Scenario-dependent Steps of the EWA Set-up

Scenario-independent Steps of the EWA Set-up

SAP HANA Content in EWA

Questions & Answers

Two scenarios for setting up EWA for HANA

Scenario I

Sol. Manager S01

for setting up EWA for HANA Scenario I Sol. Manager S01 SAP EarlyWatch Alert Report SID:

SAP EarlyWatch Alert Report

SID: P01

SAP HANA Technology HANA0

SAP HANA Technology HANA1

SAP HANA Technology HANA2

SAP HANA Technology HANA1 SAP HANA Technology HANA2 ABAP system P01 DB connections: • HANA1 SDCCN
ABAP system P01 DB connections: • HANA1 SDCCN • HANA2 • …. Default database HANA0
ABAP system P01
DB connections:
HANA1
SDCCN
HANA2
….
Default database
HANA0
SAP HANA database HANA1
SAP HANA database
HANA1
SAP HANA database HANA2
SAP HANA database
HANA2

Scenario II

Sol. Manager S02 DB connections: SDCCN • HANA3 SAP HANA database HANA3
Sol. Manager S02
DB connections:
SDCCN
HANA3
SAP HANA database
HANA3

SAP EarlyWatch Alert Report

SID: HANA3

SAP HANA Technology HANA3

See SAP Note 1958910

Setting up Scenario I

Scenario description:

SAP EarlyWatch Alert for an ABAP system which has at least one of the following:

1. SAP HANA as the default database

2. SAP HANA database as a side-car scenario

3. Several SAP HANA databases connected via DB connections

(The options 1.-3. can also be mixed.)

Prerequisites:

On the ABAP system:

ST-PI 2008_1_7xx SP 10 or ST-PI 740 has to be implemented

SAP Note 1985402 has to be implemented (includes newest corrections to ST-PI SAP HANA Download Module)

On SAP Solution Manager

ST-SER (SAP Solution Manager service tools) automated service content update activated as per SAP Note 1143775

Setup Of EWA Scenario I

Setup Of EWA Scenario I © 2015 SAP SE or an SAP affiliate company. All rights

Setup Of EWA Scenario I

Solution Manager Configuration: Create logical component for technical

system type “Application Server ABAP”

Choose corresponding system in ‚Managed System Configuration‘

Assign Product, Edit Diagnostics-relevance , Assign Logical Component

Edit Diagnostics-relevance , Assign Logical Component © 2015 SAP SE or an SAP affiliate company. All

Setup Of EWA Scenario I

Setup Of EWA Scenario I RFC Destinations are required:  RFC READ Destination (from SAP Solution

RFC Destinations are required:

RFC READ Destination (from SAP Solution Manager to the Managed System)

RFC READ Destination from the Managed System to SAP Solution Manager (to the Application Client)

System to SAP Solution Manager (to the Application Client) © 2015 SAP SE or an SAP

Setup Of EWA Scenario I

Setup Of EWA Scenario I Managed System Configuring and activating sdccn.  Step 8 ‚Finalize Configuration‘:
Managed System
Managed
System
Setup Of EWA Scenario I Managed System Configuring and activating sdccn.  Step 8 ‚Finalize Configuration‘:
Setup Of EWA Scenario I Managed System Configuring and activating sdccn.  Step 8 ‚Finalize Configuration‘:

Configuring and activating sdccn.

Step 8 ‚Finalize Configuration‘: Perform the automatic activity “Activate Services”. This will add the Solution Manager Destination in the settings of SDCCN on the managed system automatically.

This can be checked in transaction sdccn on the Managed System -> Go To -> Settings -> Task Specific -

> RFC Destinations: The SAP Solution Manager should be inserted.

Setting up Scenario II

Scenario description:

SAP EarlyWatch Alert for SAP HANA (which only contains the SAP HANA relevant checks).

Prerequisites:

One or several SAP HANA databases are connected via DB connections to Solution Manager.

On SAP Solution Manager:

ST-PI 2008_1_7xx SP 10 or ST-PI 740 has to be implemented

SAP Note 1985402 has to be implemented (includes newest corrections to ST-PI SAP HANA Download

Module)

ST-SER (SAP Solution Manager service tools) automated service content update activated as per SAP

Note 1143775

Create DB connection and test it

Transaction DBACOCKPIT -> System Landscape ->Database Connections -> SAP HANA databases

->Database Connections -> SAP HANA databases © 2015 SAP SE or an SAP affiliate company. All

Check Landscape Management Database (LMDB)

Transaction LMBD -> Technical Systems -> Type = SAP HANA Database

-> Technical Systems -> Type = SAP HANA Database Check that SLD data is automatically supplied

Check that

SLD data is

automatically

supplied

How to register SAP HANA in SLD is described here:

Setup Of SAP EWA In SAP Solution Manager

Setup Of SAP EWA In SAP Solution Manager © 2015 SAP SE or an SAP affiliate

Setup Of SAP EWA In SAP Solution Manager

Solution Manager Configuration: Create logical component for technical

system type “SAP HANA Database”

Choose corresponding system in ‚Managed System Configuration‘

Assign Product SAP HANA Platform Edit. 1.0

Edit Diagnostics-relevance , Assign Logical Component

– Edit Diagnostics-relevance , Assign Logical Component © 2015 SAP SE or an SAP affiliate company.

Setup Of SAP EWA In SAP Solution Manager

Manual Activity:

Step 6 ‚Finalize Configuration‘ -> Set Up Remote Connection to SAP HANA DB

-> Set Up Remote Connection to SAP HANA DB © 2015 SAP SE or an SAP
-> Set Up Remote Connection to SAP HANA DB © 2015 SAP SE or an SAP

Maintain technical system in LMDB

Maintain technical system in LMDB • Open transaction LMDB and select the technical system of type

Open transaction

LMDB and select the technical

system of type

“SAP HANA

Database”.

Set the attribute “Remote Database

Connection” to the name of the DB

connection.

Scenario-independent Steps of the EWA Set-up

Scenario-independent Steps of the EWA Set-up

Scenario-independent Steps of the EWA Set-up

Assign Logical Component to a Solution

Assign Logical Component to a Solution © 2015 SAP SE or an SAP affiliate company. All

EarlyWatch Management Optional Configuration

Workcenter Solution Manager Configuration -> EarlyWatch Alert Management:

Manager Configuration -> EarlyWatch Alert Management: • Check prerequisites • Activate/de-activate EWA •

Check prerequisites

Activate/de-activate EWA

Check Service Plugin

levels

Maintain email recipients

Configure optional content

Create ad-hoc EWA session

The next run of the EWA background job will create a new session for the chosen

workday (default is Monday).

If you don’t want to wait, you can create an EWA session ad-hoc. See the

instruction:

In scenario II (stand-alone HANA) the SDCCN download is scheduled in the

Solution Manager for the Solution Manager ID and not for the SAP HANA database ID !

Solution Manager ID and not for the SAP HANA database ID ! © 2015 SAP SE
Solution Manager ID and not for the SAP HANA database ID ! © 2015 SAP SE

Where you find the EWA Reports

Checking SAP EWA Reports / See SAP EWA Reports

Workcenter „SAP Engagement and Service Delivery“ Choose Corresponding Solution

Mark ‚Reports‘ EarlyWatch Alert

Solution  Mark ‚Reports‘  EarlyWatch Alert © 2015 SAP SE or an SAP affiliate company.
SAP HANA Content in EWA

SAP HANA Content in EWA

SAP HANA Content in EWA

Chapter “SAP HANA Technology” In EWA Report

Chapter “SAP HANA Technology” In EWA Report The chapter starts with a rating table giving an

The chapter starts with a rating table giving an overview on all topics checked.

SAP HANA Content in SAP EWA: SAP HANA Architecture

Name server

Index server

Statistic server

sapstartsrv

daemon

xsengine

Global operations (like back-up)

Data container, etc.

Historical statistical data, alerting engine

Important for general connectivity to the SAP HANA database

Checks whether all servicse are available

Service with application content and Web server

Stability and Alerts

Stability and Alerts Red Alerts:  More than 4 SAP HANA dumps.  name- and/or index

Red Alerts:

More than 4 SAP HANA dumps.

name- and/or index server had 3 or

more restarts.

Yellow alerts:

Alerts with priority medium or high were raised (thresholds maintainable in HANA Studio or DBACockpit).

Any statistic server alert was raised.

Up to 4 SAP HANA dumps.

name- and/or index server had up to

2 restarts or the remaining servers had 2 or more restarts

Configuration

Configuration Red Alerts:  CPU frequency lower than expected Yellow alerts:  Critical Parameter setting 

Red Alerts:

CPU frequency lower than expected

Yellow alerts:

Critical Parameter setting

If the DATA and LOG areas are not on exclusive devices.

If GPFS file system type is used.

Trace levels differ from default.

SAP HANA Content In SAP EWA: Configuration

The are three different sections for parameters:

Important SAP HANA Parameters

These parameters are rated automatically and a recommended value is given. For

some parameters a link to an SAP Note is provided.

SAP HANA Parameters deviating from default

These parameters are listed for documentation only. They have been changed from default, but there is no SAP recommendation given by the service report.

Parameters to be checked

These parameters have to checked manually by the database administrator with the

help of the SAP note provided as a link.

SAP HANA Content In SAP EWA: Configuration

SAP HANA Content In SAP EWA: Configuration Configuration: Organization:  Configuration files (e.g. indexserver.ini)

Configuration:

Organization:

Configuration files (e.g. indexserver.ini)

Within them we have different sections (e.g. mergedog)

Parameter values

The parameter values can be of the

following ‚type‘:

Default: Default value

System: Changed to a system wide

value

Host: Changed to a value only valid for a host

These attributes are called layers in SAP

EWA.

Size And Growth

Size And Growth Red Alerts:  Free disk space drops below 10%  Technical limit of

Red Alerts:

Free disk space drops below 10%

Technical limit of row store is almost

reached

Column store table or partition approaches limit of records

Yellow alerts:

Fragmentation of row store

Large size of row store

High number of records in a column store table or partition

Size And Growth: Column Table Size

Size And Growth: Column Table Size The largest column-based tables are also shown sorted by the

The largest column-based tables are also shown sorted by the number of entries

A column-based table or partition can handle only up to 2 billion entries and should be

partitioned as soon as 1,5 billion entries are reached.

For Partitioning see SAP HANA Administration guide and SAP Note 1650394.

Resource Consumption

Resource Consumption Red Alerts:  CPU consumption exceeds 90%  Total HANA instance used memory >=

Red Alerts:

CPU consumption exceeds 90%

Total HANA instance used memory

>= 90% of the global allocation limit

Memory consumption of tables >= 70% of the available allocation limit

Indexserver memory used >= 90 %

of its effective allocation limit

Yellow alerts:

CPU consumption exceeds 75%

Max. total used memory on server

>= 95% of the available physical

memory

Memory consumption of tables >= 50% of the available allocation limit

Resource Consumption

Resource Consumption © 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 31
Resource Consumption © 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 31
Resource Consumption © 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 31
Resource Consumption © 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 31

Performance: Memory Consumption

When you are manually checking the system:

Are there out-of memory dumps? (oom diagnosis files: Operations took too much memory)

Are there table unloads? (unloads diagnosis files: Column based tables were unloaded)

– diagnosis files: Column based tables were unloaded) © 2015 SAP SE or an SAP affiliate

Delta Store

Change Mechanism:

Changes in column-based tables are first written in ‚delta store‘

Data in delta store is not compressed

Huge amounts of data in delta store slow down the performance

Data is written in the ‚main‘ store according to the ‚merge‘ mechanism

--------- --------- Delta store Main store
---------
---------
Delta store
Main store
mechanism --------- --------- Delta store Main store Merge --------- --------- Delta store Main store © 2015
Merge
Merge
--------- --------- Delta store Main store
---------
---------
Delta store
Main store

Workload and Performance

Workload and Performance Red Alerts:  More than 100,000 column unloads  Column table size or

Red Alerts:

More than 100,000 column unloads

Column table size or partition size in delta store > 10 GB

Yellow alerts:

1,001 to 100,000 column unloads

Column table size or partition size in delta store > 5 GB

table size or partition size in delta store > 5 GB © 2015 SAP SE or

Workload and Performance

Workload and Performance © 2015 SAP SE or an SAP affiliate company. All rights reserved. Public
Workload and Performance © 2015 SAP SE or an SAP affiliate company. All rights reserved. Public
Workload and Performance © 2015 SAP SE or an SAP affiliate company. All rights reserved. Public
Workload and Performance © 2015 SAP SE or an SAP affiliate company. All rights reserved. Public

Administration

Administration Red Alerts:  Backups are not performed at all Yellow alerts:  Many diagnosis files

Red Alerts:

Backups are not performed at all

Yellow alerts:

Many diagnosis files or large disk

space occupied

There are fewer than 5 successful data backups in the monitored timeframe or log backups are not performed daily.

Important SAP Note for the specific HANA revision

Administration: Diagnosis Files

Administration: Diagnosis Files Checking against 3 types: Trace, Log, Dmp.  Trace, log, dmp files from

Checking against 3 types: Trace, Log, Dmp.

Trace, log, dmp files from last week:

Only dmp files are important. Dmp files are crashdumps. If none occurred, no dmp files are shown here.

Trace files have a definite size (10 Mbyte, parameter maxfilesize) and number (maxfiles) and are

overwritten when all files are full.

SLT Performance

SLT Performance If the scenario includes replication via SLT the EarlyWatch Report contains a separate chapter

If the scenario includes replication via SLT the EarlyWatch Report contains a separate chapter on SLT configuration

and performance.

The latency information is judged with

a rating.

SLT Performance Statistics

SLT Performance Statistics The performance development is shown in a rating table and a graph. ©

The performance development is shown in a rating table and a graph.

development is shown in a rating table and a graph. © 2015 SAP SE or an
Questions & Answers

Questions & Answers

Questions & Answers

Questions & Answers

1. How is the EWA for a stand-alone SAP HANA DB created?

Either as chapter in an EWA report for any ABAP system, or as EWA for a

system of type SAP HANA Platform Edition.

2. With DB Connections to multiple SAP HANA DBs: How can I specify which

specific SAP HANA should (not) be included?

Maintenance in DBACockpit: Add Remote DB with a description starting

with EWA_* (NON_EWA_* opposite)

3. Is it possible to add more than one SAP HANA DB to an EWA Report?

Yes: The EWA Report for an ABAP system will include all HANA DBs that are

maintained in the DB connections.

->

Thank you © 2015 SAP SE or an SAP affiliate company. All rights reserved.

Thank you

© 2015 SAP SE or an SAP affiliate company. All rights reserved.