Scribd
Upload
944 views14 pages

HANA Revision Upgrade

The document provides instructions for upgrading an SAP HANA database from revision 96 to 122.08. It notes the location of revision 122 files and importance of checking OSS notes for required update paths and operating system packages. Steps include extracting files, stopping SAP, backing up directories, launching the upgrade tool, resolving errors, and checking services and versions after completion.

Uploaded by

HMI Project
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
944 views14 pages

HANA Revision Upgrade

The document provides instructions for upgrading an SAP HANA database from revision 96 to 122.08. It notes the location of revision 122 files and importance of checking OSS notes for required update paths and operating system packages. Steps include extracting files, stopping SAP, backing up directories, launching the upgrade tool, resolving errors, and checking services and versions after completion.

Uploaded by

HMI Project
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 14

HANA REVISION UPGRADE FROM 96 to 122.

08
Location of Rev_122 : /software/SAPCD/REV_122

Extract HANA SERVER and HANA CLIENT here. For HANA client , do read the OSS note 2339267. SAP
intentionally not keeping the client version same starting from SPS12.

IMPORTANT NOTE BEFORE YOU START UPGRADE :

1.Please check the OSS note 1948334 to check the update paths for Maintanence revision before
starting the upgrade.

2. In order to run the SAP HANA Database Revision 110 (or higher) on SLES 11, additional operating
system software packages are required.Before you start the upgrade or the installation of Revision 110
or higher, please see SAP Note 2228351 - Linux: SAP HANA Database SPS 11 revision 110 (or higher) on
RHEL 6 or SLES 11

3. Check the corresponding release notes to understand whats included in SPS12.


After extraction, we have below files
Stopsap
Prior upgrade
Take backup of /hana/shared/CXP directory.

Taken here

Launch hdblcmgui.
Got this error.

This error normally occurs if you dont have the correct signature file in the hdblcm installation
directory. If several SAP HANA component SAR archives have been downloaded and extracted into a
single directory, it might happen that the SIGNATURE.SMF file of the SAP HANA Database archive gets
overriden by some other component's signature. As a result, the wrong SIGNATURE.SMF gets copied
to the <sapmnt>/<SID>/hdblcm directory, hence SAP Host Agent is not able to verify and deploy the
hdblcm tool. The problem is most probably caused by improper extraction of the SAP HANA
compoennt archives before installation or upgrade.

Follow the below steps from OSS note 2074825 to resolve the issue
Go to the extracted folder and run the hdblcmgui again. The error disappears
Faced error below

The service related to port 1129 is not started on server gotsap220.It is for saphostctrl. Started as shown
below in screenshot.

OSS note referred : 2078425. See section Resolving problems with SAP Host Agent integration.
This note can be used as a troubleshooting guide for other issues as well. Attached below is the snippet
from the OSS note
Once 1129 port is opened, Upgrade started !!

Upgrade completed
Check version using HDB version

Check if Application is able to communicate with DB


Check all services are up and running from HANA studio

SICK

DBACOCKPIT : Check version and check for errors

Check version from HANA studio


Alerts shows password of SYSTEM will expire on 02nd June, 2017. So action will be taken accordingly.

Fire backup via BACKINT

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy