hana supportability and monitoring setup

7/16/2019 HANA Supportability and Monitoring Setup

http://slidepdf.com/reader/full/hana-supportability-and-monitoring-setup 1/55

HANA Supportability and Monitoring

Setup

Active Global Support

V16, 2012



© 2012 SAP AG. All rights reserved. 2

Setup

Hostagent and Diagnostics Agent

Setup in Solution Manager

Setup of EarlyWatch Alert

Configuration of System Monitoring

Moving to SLD (without unified installer)

Configuring Detailed OS Monitoring

1

2

3

4

5

6




Managed System Configuration: Landscape Data Provider

Involved Components: SAP Hostagent (communicates with SAP HANA Database )

Diagnostics Agent (communicates with SAP Hostagent )

SAP Solution Manager (has to be assigned to Managed System of SAP Solution

Manager )

Applications consume landscape information from Landscape Management Database

Solution Manager HANA Appliance Server

HANA

Database

Hostagent

Landscape

Managed

Database(LMDB)

DBACockpit

1

2

34

Performance

Warehouse Alerting

Framework

1

2

3

4

Agents are installed on

every host of the

appliance by thehardware partner




Managed System Configuration: Hostagent User

Hostagent: Configuration of the HDB User Store

1. Create a Database user on HANA wich has the role ‚MONITORING‘

2. Connect via HANA studio once with this user execute the initially required password

change.

Because of securityreasons: Hostagent

should not be called

with user / password




Managed System Configuration: Hostagent in

hdbuserstore

HDB Client: Configuration of the HDB User Store is described inSAP Note 1625203

Read the userstore

Test the settings

Hdbuserstore is

shipped as part of the

HDB client.

Set the user with password (Databasename is IN1) with the user <SID>adm

Important to use

<SID>adm user on OS

level.

A successful test

provides a list of theserver processes

statuses




Managed System Configuration: Web Service Test

SAP Hostagent: Web Service Test

Outside Discovery: Webmethod GetDatabaseProperties

Status: Webmethod GetDatabaseStatus


http://slidepdf.com/reader/full/hana-supportability-and-monitoring-setup 7/55© 2012 SAP AG. All rights reserved. 7

2. Technical System Setup: Diagnostics Agent

Ensure that Diagnostics Agent communicates with Hostagent Diagnostics Agent needs Permission to execute Hostagent executables

File host_profiles

Check in SAP Hostagent profile that Diagnostics Agent <SID>adm user

is amongst admin_users



Setup





Moving to SLD without unified installer


1

2

3

4

5

6



1. Technical System Setup in Solution Manager

Configuration of SAP HANA Database:

Solution Manager Workcenter ‘Configuration’

Purpose

Setup of DBACockpit

Setup of Performance Warehouse

Setup of Technical System Monitoring



Technical System Setup: DBA Cockpit Setup

Prerequisite: Please ensure that the HANA Database Clients are installed on the Solution Manager

according to SAP Note 1597627

– Including sufficient Kernel Patch

– SAP DBSL for SAP HANA Database

– DB Client Software for SAP HANA

DBA Connection Setup: SAP Note 1612172 (relevant for SP4+SP5, only in SP4 master

note only)

Integration of HANA Database Extractors for Solution Manager 7.10 SP 04: SAP Note

1655601 (in SP4 master note)

Setup Issue of the Technical System ‚HANA Database‘: SAP Note 1672429 (relevant for SolMan 7.1 SP04, in SP4 master note)

Automatic Prefilling of necessary HANA Attributes: SAP Note 1721598.

(relevant for SolMan 7.1 SP04 + SP05, only on SP4 master note)

New extractor definitions for SP05 and SP06: SAP Note 1653635.

(relevant for SolMan 7.1 SP05+SP06, only in SP5 master note)



Technical System Setup: DBA Cockpit Setup

Latest UI updates:

In order to get latest content and screens for Root Cause Analysis in older SolMan Sps

BI content required to leverage new extractor: SAP Note TBD.

New extractor definition for SP5 + SP6 following Note 1749921 (not in any master note)



Requirements for BW on HANA

IF HANA is the Database of an ABAP Application (e.g. BW on HANA) the ABAP

System needs to send the information that it uses the HANA Database.

Therefore 2 SAP Notes have to be implemented:

1652485: RZ70: Enhancement for HANA database

1649323: SLD: Enhancement for HANA database



Requirements for HANA SPS 4 and Solution Manager 7.10

SP 05

With HANA SPS 4 and Solution Manager 7.10 SP 05 the HANA Database

recognize itself via SLDREG in the Solution Manager Directory.

Minimum HANA Revision 1.00.28

To register the HANA Database at the Solution Landcspae Directory :

(a) Switch to the HANA Database user <sid>adm

(b) Change in the directory /usr/sap/<sid>/SYS/global

(c) Execute the command for creation of SLD Configuration Filessldreg -configure slddest.cfg –usekeyfile(SAP Note 1018839)

(d) Execute the command to register in SLD:sldreg -connectfile /usr/sap/<SID>/SYS/global/slddest.cfg –

file /usr/sap/<SID>/HDB<InstNr>/<Host>/trace/sldreg.xml



1. Technical System Setup

Configuration of SAP HANA Database: Solution Manager Workcenter ‘Configuration’

Managed System Configuration

2

1

(1) Technical System has to

be modified in System

Oprations

(2) Setup of the System



Technical System Setup

(1) Configuration of SAP HANA Database - Software

Technical System SetUp -> Manual Step -> Adding Product Instance




Configuration of SAP HANA Database - Software:

Ensure that the software is complete:

– Product Instance

– Software Component Version




Configuration of SAP HANA Database - Instance:

2 properties of the Instance have to be added

– ServerType

– Instance Number





Configuration of SAP HANA Database - Instance:

2 properties of the Instance have to be added

– System Name

– System Home

THE ROLE

SAP_SYSTEM_REPOSITORY_ALL

has to be assigned to the

SOLMAN_ADMIN user to modifythese properties





(2) Solution Manager Setup of the Managed System:

Assigning Diagnostics Agent to system

System Parameters:

– Database Related Configuration

– Enterprise Manager

Starting Extractors





After this Setup:

DBACockpit is configured

Configuration Change Database is configured

Database Performance Warehouse is configured





Technical Monitoring Setup:

Configuration Workcenter -> Technical Monitoring





Technical Monitoring Setup:Configuration Workcenter -> Technical Monitoring (Assign Templates)





Technical Monitoring Setup:

Configuration Workcenter -> Technical Monitoring -> Setup Monitoring -> DirectoryBrowser




Technical Monitoring – Verification of Setup

Technical Monitoring

Workcenter ‚Technical Monitoring‘ ‚System Monitoring‘

Availability

Alerts (by Hostagent)

Configuration Alerts

(by DBACockpit)

Special HANA Alerts

like

- General Exceptions

- Table Exceptions

(by DBACockpit)




Setup







1

2

3

4

5

6




SAP EWA for SAP HANA Setup Landscape (old)

SAP SolutionManager 7.0 SAP

„back-end“

system

SAP HANA database

SAP Hana 1.0

Host agent

Script

5. SAP EWA session is

executed on SAP

Solution Manager and

SAP EWA report iscreated

1. Batchjob triggers data

collection on SAP HANA via

host agent

2. Host agent starts data

collection script

3. Information is passed back to

background job (XML-format)

4. Results in background job is

collected in sdcc and send toSAP Solution Manager

In short:

•Method uses the consumer proxy Web service technology

•Configuration of the host agent necessary

•Configuration of the back-end necessary

TOO complex




New Setup of SAP EWA for SAP HANA (Download Based

via DBCON)

New Method:

Uses the database connection to

retrieve data from the SAP HANA

database

No further configuration on the SAP

„back-end system“ is required

except scheduling the download

(SDCCN)

No special configuration of the host

agent is required

SAP SolutionManager 7.0

SAP

„back-end“

system

SAP HANA

database

SAP Hana 1.0

Database

connection




Requirements of the ‚Standard (New) Data Collection

approach‘

On the „back-end system“:

ST-PI 2008_1_7xx SP 06 has to be implemented

SAP Note 1741541 has to be implemented

On SAP Solution Manager

ST-SER (SAP Solution Manager service tools) 701_2010_1 SP14 or higher

(or) automated service content update activated as per SAP Note 1143775




System Monitoring (SAP EWA)

Currently supported scenarios for monitoring the SAP HANA database withthe SAP EWA service are:

SAP Business Suite application, side-by-side (SAP ERP, SAP CRM …),

SAP BW on SAP HANA system

or SAP LT system

Workaround exists for pure SAP BusinessObjects scenarios (SAP EWA scheduling via SAP

Solution Manager)




Setup of SAP EWA in SAP Solution Manager

in Managed System Setup in Solution Manager I

Required RFC Destinations: READ Destination (from Solution

Manager to the Managed System)

RFC Destination from the Managed

System to Solution Manager (to the

Application Client)




Setup of SAP EWA in SAP Solution Manager in Managed System Setup in Solution Manager II

Configuring and activating sdccn.

Step 8 ‚Configure Automatically‘ -> Activate Services

Transaction sdccn on the Managed System -> GoTo -> Settings -> Task Specific -> RFC

Destinations: The Solution Manager should be inserted.

Managed

System





Step 1: Create logical component of the ABAP stack to which the SAP HANA

DB is connected

Workcenter ‚SAP Solution Manager Configuration‘

– Choose corresponding system in ‚Managed System Configuration‘

– Step 10: Create logical components, assign system, client, and type of system (productive, test )





Step 2: Assign logical component to a solution

Workcenter : „Service and Delivery“

– Maintain ‚Solution Data‘





Step 3: Scheduling

SAP EWA download

collection

Workcenter : „System

Administration“

– Choose ‚Solutions‘

Mark Solution

Operations Setup EarlyWatch Alert





Step 4: Checking SAP EWA Reports / See SAP EWA Reports

Workcenter „SAP Engagement and Service Delivery“ Choose Corresponding SolutionMark ‚Reports‘ EarlyWatch Alert




Setup







1

2

3

4

5

6




Prerequisites

Prerequisite:

The latest monitoring content version has to be uploaded and applied (content version 8 for

SolMan 7.1 SP5 and content version 9 for SolMan 7.1 SP6).

System Monitoring content for HANA has been updated for Solution Manager SP5.

You need to apply SAP notes 1748192 and 1702711 (relevant for SolMan 7.1 SP5, SP6)(only 1748192 included only in SP6 master note)

For SolMan 7.1 SP4 + SP5 you need SAP note 1700043 to fix a bug that leads to missing

or gray metrics in HANA system monitoring. (not in any master note)

With SolMan 7.1 SP5 additionally SAP note 1725434 to fix LMDB problem for HANA. (notin master note)

If you want to setup system monitoring for an SLT system (available as of SolMan 7.1 SP5)

you also need to apply SAP note 1743562 and 1558756.




General configuration of System Monitoring

Workcenter: Technical Administration:

Work Mode Management

Notification Management





Work Mode Management:

The setting of the Work Mode Management has influence of the Alerting.

Example: During a Planned Downtime of a System no Alerts should be

generated.





Specify Time and Notification of the Downtime

General configuration of SystemMonitoring





After saving and refreshing the following overview list is obtained





Notification Management:

General Settings of the recepiants list (Present / Absence)




Configuration of System Monitoring for special systems

Solution Manager: Configuration





Maintaing recepient list:





Custom Settings of a template: Change of thresoholds




Setup







1

2

3

4

5

6




Moving to SLD from a system installed without unified

installer

You want to change the registration of your HANA DB from Outside Discovery

to SLD. The registration with SLD exists only with unfied installer.

Nevertheless there might be cases for which you have to change manually to

the SLD registration.

You have installed HANA SPS 3 and upgrade to HA NA SPS 4. Here the registration via

SLD is available

You have installed HANA without unified installer (e.g. BW on HANA) – and want to change

the registration to the SLD Registration





installer

Download from the Service Marketplace when you upgrade your HANA Database also the

componentSAP HANA related SL Tools -> LM STRUCTURE INST HANA 1.0

Copy this on the HANA Server and unpack the LM Structure package

In the directory SAP_HANA_LM_STRUCTURE call the commandhdbinst –a lm

You should see directory lm_structure in the directory /usr/sap/<SID>





installer

Please check the Parameter sld->enable. It has to be set to ‚YES‘. If a system is not installed with the unified installer it is set per default to ‚NO‘

Setting the parameter to ‚YES‘ creates a file sldreg.xml in the directory

/usr/sap/<SID>/HDB<Inst_nr>/<servername>/trace





installer

Registering at SLD: To generate the configuration file change in the directory

/usr/sap/<SID>/SYS/global

Call the commandsldreg -configure slddest.cfg -usekeyfile

To send the information to SLD use the following command:sldreg -connectfile /usr/sap/<SID>/SYS/global/slddest.cfg –file

/usr/sap/<SID>/HDB<Inst_Nr>/<servername>/trace/sldreg.xml




Setup







1

2

3

4

5

6





Enable saposcol process monitoring

Download and unzip the attachment "SAP_HANA_Unix_procmon.zip“ from SAPNote

1747682

Copy the file "SAP_HANA_Unix_procmon.ini" under the directory /usr/sap/tmp/procmon/

(create the directory if it does not yet exist).This file configures the list of processes that must be monitored (cpu & memory) by

saposcol (SAP Operating SystemCollector).

Remark: depending on the saposcol configuration, the default

folders indicated above might change. More information regarding

SAPHOSTAGENT and process monitoring with SAPOSCOL are available from SAP

notes 1031096 and 790639. After the files have been properly copied, you

must restart saposcol (SAPHOSTAGENT), then the SMD agent.




Required SAP Notes

System Version Note Why In master note

SolMan 7.1 All versions 1597627 HANA client on SolMan N.A.

SolMan 7.1 SP4 + SP5 1612172 HANA in DB setup wizard SP4: yes, SP5: no

SolMan 7.1 SP4 1655601 HANA DB extractors SP4: yes

SolMan 7.1 SP4 1672429 Fix for setup issue SP4: yes

SolMan 7.1 SP4 + SP5 1721598 Prefil HANA attributes SP4: yes, SP5: no

SolMan 7.1 SP5 + SP6 1653635 New HANA DB extractors SP5: yes, SP6: no

SolMan 7.1 SP5 + SP6 1749921 New HANA extractor definitions N.A.

SolMan 7.1 SP5 + SP6 TBD New BW content (PILOT NOTE) N.A.

SolMan 7.1 SP5 + SP6 1702711 HANA system mon update SP5: no, SP6: no

SolMan 7.1 SP5 + SP6 1748192 HANA system mon validity fix SP5: no, SP6: yes

SolMan 7.1 SP4 + SP5 1700043 Fix for missing HANA metrics SP4: no, SP5: no

SolMan 7.1 SP5 1725434 Fix for LMDB bug for HANA SP5: no

SolMan 7.1 SP6 1729270 HANA in DB setup wizard SP6: yes




Required SAP Notes

System Version Note Why In master note

SLT ST-A/PI 01P* 1743562 Manual corrections for SLT mon N.A.

Hostagent All versions 1625203 Setup hdbuserstore N.A.

HANA box All versions 1542651 Enable EWA for HANA N.A.

SLD See note 1649323 Enable SLD for HANA N.A.

BW (on HANA) BASIS 730 SP5 1652485 Enable RZ70 for HANA N.A.



No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

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

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, 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 registeredtrademarks 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 aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, 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 AG in Germany and other countries.

© 2012 SAP AG. All rights reserved

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarksof Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts 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 respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.

The information in this document is proprietary to SAP. No part of this document may bereproduced, copied, or transmitted in any form or for any purpose without the express prior

written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or anyother agreement with SAP. This document contains only intended strategies, developments,and functionalities of the SAP® product and is not intended to be binding upon SAP to anyparticular course of business, product strategy, and/or development. Please note that thisdocument is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does notwarrant the accuracy or completeness of the information, text, graphics, links, or other itemscontained within this material. This document is provided without a warranty of any kind,either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct,special, indirect, or consequential damages that may result from the use of these materials.

This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has nocontrol over the information that you may access through the use of hot links contained inthese materials and does not endorse your use of third-party Web pages nor provide anywarranty whatsoever relating to third-party Web pages.

hana supportability and monitoring setup

Documents

sap ag

setup hostagent

sap hostagent profile

hostagent user hostagent

sap hana dba connection

technical system setup

diagnostics agent setup

database user