Upgrading SAP HANA with Software Update Manager for HANA. Serge Muts Customer Solution Adoption (CSA) SAP Labs

Upgrading SAP HANA with Software

Update Manager for HANA

Disclaimer

This presentation outlines our general product direction and should not be relied on in

making a purchase decision. This presentation is not subject to your license

agreement or any other agreement with SAP. SAP has no obligation to pursue any

course of business outlined in this presentation or to develop or release any

functionality mentioned in this presentation. This presentation and SAP's strategy and

possible future developments are subject to change and may be changed by SAP at

any time for any reason without notice. This document is provided without a warranty

of any kind, either express or implied, including but not limited to, the implied

Agenda

SAP Host Agent SAP HANA studio

SAP HANA appliance software

SAP HANA installation and configuration

A well-defined and validated stack of HW and SW components

The SAP HANA appliance software from a deployment point of view:

SAP HANA platform edition

–

SAP HANA database

–

SAP HANA client

–

SAP HANA studio GUI | P2 repository

–

SAP Host Agent

Additional components installed

–

Machine-readable product description

(LM structure files)

–

SAP Software Update Manager

for SAP HANA

–

SAP Solution Manager Diagnostics

Agent

–

SAPCAR

–

Operating system configuration

SAPCAR

SAP HANA clients

Machine-readable product description (LM structure files) SAP HANA database SLES 11 SP1/SP2

Server Management Tools (HW vendor-specific)

Storage Subsystem (HW vendor specific) SUM for SAP HANA

SLES 11 SP1/SP2 Server Mgmt. Tools Storage Subsystem

SAP Host Agent

SAP HANA clients

SAP HANA database

SAP HANA system landscape

Connectivity overview

SAP HANA Appliance

SAP HANA

SAP HANA Database Host agent/ SMD Agent SUM for SAP HANA … Direct Extractor Connection (DXC) Data acquisition from SAP Business Content DataSource Extractors E.g., SAP NW BW SAP Data Services For ETL-based loading E.g., third-party EDW SAP Landscape Transformation (SLT) For real-time replication

E.g., SAP ERP

Primary Persistence

SAP Business Suite Powered by HANA SAP NW 7.3 BW

Powered by SAP HANA as primary persistence below SAP NW 7.3 AS ABAP SAP Service Marketplace (SMP) For downloading SP-stacks and patches

SAP Support (OSS)

For remote support of the SAP HANA

system Side-by-Side SAP Business Objects BI Suite For analytical scenarios using BI suite products HANA UI for Information Access

For search and text capabilities inside

SAP HANA

HANA Information

Composer

For easy data upload into SAP

HANA Platform/Runtime HANA Apps Applications running natively on/against SAP HANA Database R-runtime

For direct integration with R-runtime

libraries

SAP Solution Manager

SAP HANA update and patching

Overview

SAP HANA SP-Stack Update

• Automated download and

implementation of new Support

Package Stacks (SPS) can be done

from within the SAP HANA Studio

LM-perspective through Software

Update Manager (SUM) for SAP

HANA

SAP HANA Revision

Patching

• Implementation of individually and

intermediate patches/revisions,

for example, of the SAP HANA

database component, can be done

from within the SAP HANA Studio

LM-perspective through Software

Update Manager (SUM) for SAP

HANA

SLES OS patching

• Pre-validated HW/OS stack

configurations reduce risk of

operating system SP update while

leaving flexibility to implement

SAP HANA revisions

With the release of SAP HANA SPS5 the manual update guide was removed and SUM for HANA is

strongly recommended as the update tool to use for customers and partners.

Concept of revisions used in SAP HANA

Updates and patches of the database

HANA is no ABAP application

Shipping of

corrections as new versions of the binaries

(Revisions)

There are no correction notes with individual coding corrections

Revisions are

cumulative

Corrections are applied with the latest available revision

No individual corrections based on older revisions

Note:

Good practice to have a recent backup

There is a

short downtime

at the end of the patch process (exchange of binaries)

During the update there is a built-in check for certified hardware

High Level Steps

1. Stop all processes.

2. Make a system backup if necessary.

3. Perform an automated Update with the Software Update Manager for SAP

HANA.

4. Update the depending components.

5. Perform the post-update steps.

SAP HANA

(Customer Side)

SAP HANA update and patching

Standalone scenario/direct download from Service Marketplace (optional*)

HANA Studio +

Lifecycle Mgmt.

SAP Service Marketplace

Infrastructure

SAP Service

Marketplace

SAP-hosted

Maintenance

Optimizer

3

Transfer HANA setup

4

Request_Packages

5

Download_Packages

6

U p d a te

2

1

Start and

Control Update Execute SUM for_{SAP HANA} “Self-Update” process

1

Manual Update Steps

1

Automatic Update Steps

HANA Server

SAP Host Agent

HANA Client

HANA DB

SUM

for HANA

SAP HANA

(Customer Side)

SAP HANA update and patching

SAP Solution Manager scenario/pre-fetched stack download

HANA Studio +

Lifecycle Mgmt.

SAP Service Marketplace

Infrastructure

SAP Service

Marketplace

SolMan 7.1

SP05

1

Register_HANA

3

Execute MOPZ and Request Packages

4

Download Packages using

Download Manager

6

Execute_Self-Update

Manual Update Steps

Customer

SLD

2

Set up LMDB

1

Automatic Update Steps

HANA Server

SAP Host Agent

HANA Client

HANA DB

SUM for HANA

5

Start and Control Update

7

U p d a te

Pre-requisites

Prerequisites for Software Update Manager for SAP HANA System In the SAP HANA system, the following prerequisites have to be fulfilled:

The SAP HANA system needs access to the SAP Service Marketplace using HTTPS with optional proxy, unless you have already manually downloaded and copied the target stack to your SAP HANA system.

You need an S-User login

You have stopped the data replication before you start the automated update.

You have performed a system backup before you start the automated update. Also note that during the automated update there is a business downtime for your SAP HANA system.

You need SUMHANA*.SAR archive and the lm_structure present on the system. You know the <SID>adm and sapadm passwords.

You have applied a valid license key to the SAP HANA system. SAP HANA database is up and running.

SAP Host Agent is up and running. Stop all processes accessing SAP HANA

What is updated with SUM for HANA?

Everything in red, plus (if installed)

Application Function Libraries (AFLs)

LiveCache Applications

SAP HANA Application Content

Also Supported:

Multi-SID Support – one SID at a time

Scale Out – saphostagent has to installed

on all nodes

Note: Clients not on the appliance are not

updated by SUM for HANA. This is an

additional manual step.

SAP Host Agent SAP HANA studio

SAP HANA appliance software

SAPCAR

SAP HANA clients

Machine-readable product description (LM structure files) SAP HANA database SLES 11 SP1/SP2

Server Management Tools (HW vendor-specific)

Storage Subsystem (HW vendor specific)

SUM for SAP HANA

SAP SMD Agent*

SAP HANA Live for SAP Business Suite

SAP HANA ANALYTICS FOR CRM 1.0

SAP HANA ANALYTICS FOR ERP 1.0

SAP HANA ANALYTICS FOR GRC 1.0

SAP HANA ANALYTICS FOR SCM 1.0

SAP HANA CONTENT TOOLS 1.0

SAP APO ANALYTICS 1.0

SAP GRC ANALYTICS 1.0

SAP GRC ANALYTICS 1.0

Configure SUM – Option 1

Start modes: to automate startup of SUM set keystore password in catalina.properties.

If this is not deemed secure in your organization enter it upon startup of SUM. Make

sure this catalina.properties is accessible only by <sid>adm user.

Start SUM without catalina.properties – Option 2

Implications of saving password in catalina.properties:

Start the Update

Download SAP HANA Revision Components Manually

When internet access from the SAP HANA appliance is not an option:

1.

Find components to download, include the HANA Clients for correct OS (appliance and

non-appliance)

2.

Download latest versions from service.sap.com, including the latest SUMHANA*.SAR and

copy to directory ../trans/SMPPatches (e.g. /sapmnt/<SID>/trans/SMPPatches)

Agenda

Background: Install/Update combinations

Older installations were installed with hdbinst -> update with hdbupd

Newer installations were installed with the unified installer -> update

with SUM for HANA

SUM works with unified installer installed HANA:

What if I use hdbupd anyway?

LM_STRUCTURE not updated, hostagents not updated, handle content

upgrade manually

How to recognize which installation was used

Do directories /usr/sap/<SID>/SUM and /usr/sap/<SID>/lm_structure exist?

No -> hdbinst was used

Yes -> unified installer was used

How to add missing components like lm_structure and SUM

Troubleshooting

SUM log: /usr/sap/TT1/SUM/log

Lmtp.log (also linked in HANA Studio)

Ljs.log

Upgrade log is located in directory (owned by root):

/var/tmp/hdb_TT1_upgrade_2013-04-22_11.47.22/hdbupd.log

Did the upgrade really fail…?

Issue during the upgrade or after?

Did content import fail?

Most common error: the restart failed -> check work directory

Important Notes & Documentation

Main documentation on

http://help.sap.com/hana

SAP HANA Master Update Guide

SAP HANA Automated Update Guide

SAP HANA Installation Guide with Unified Installer

Central Note: SAP Release Note for SUM for SAP HANA 1.0:

https://service.sap.com/sap/support/notes/1545815

Install and Configure SUM:

Thank You!

Contact information:

Serge Muts

© 2013 SAP AG. 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 AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP AG 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.

SAP 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.