Saturday, 5 March 2016

SAP HANA REVISION UPDATE – SPS10

Reason for HANA DB patch level update
We are copying HANA DB from SLES 11.3 revision 102.01 to RHEL 6.5 revision 102.00 through Backup / Restore method using SWPM (homogeneous system copy). While restoring any HANA DB it is necessary to have at least same or higher patch level into the target environment. This is reason we are updating target HANA DB environment from revision 102.00 to latest available patch level 102.04.

Download SAP HANA patches
Download following updates (Database, Studio & Client) from SAP marketplace and transfer to HANA server

SAP HANA Certifications and Material

SAP HANA Material and Certifications

Current available patch level is 102.04 (PL04). So we are updating into PL 04. We will download Studio, Client & DB for update.

SAP HANA Backup before update
Take complete backup before rev update start

SAP HANA REVISION UPDATE – SPS10

Extract HANA Patches
Move all SAR files into HANA host server and extract using switch –manifest SIGNATURE.SM

SAP HANA REVISION UPDATE – SPS10

If you extract more than one component SAR into a single directory, you need to move the SIGNATURE.SMF file to the subfolder (SAP_HANA_DATABASE, SAP_HANA_CLIENT, SAP_HANA_STUDIO etc.), before extracting the next SAR in order to avoid overwriting the SIGNATURE.SMF file. For more information, see also SAP Note 2178665 in Related Information.

SAP HANA Certifications and Material

SAP HANA Certifications and Material

Do the same for client & studio as well

SAP HANA REVISION UPDATE – SPS10

HANA Update via STUDIO
Run SAP HANA Platform Lifecycle Management from HANA STUDIO

SAP HANA Revision Update

SAP HANA SPS10


SAP HANA REVISION UPDATE – SPS10

Select the location from HANA host

SAP HANA SPS10

SAP HANA REVISION UPDATE – SPS10

SAP HANA REVISION UPDATE – SPS10

SAP HANA SPS10

SAP HANA Certifications and Material

SAP HANA REVISION UPDATE – SPS10

SAP HANA REVISION UPDATE – SPS10

SAP HANA Certifications and Material

This completes HANA patch level update.

Source: scn.sap.com

No comments:

Post a Comment