Sps Upgrade Procedure

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 10

SPS UPGRADE PROCEDURE

Preparation

Below are the preparation steps,


 Send an e-mail to Functional Managers, Functional team members, Infra Team,
Database backup Team and ABAP Team.
 Check with ABAP Team who are responsible for SPDD and SPAU activities.
 Set a System message that upgrade activity is scheduled.
Pre-Upgrade Tasks

Below are the pre-upgrade steps which  SAP Host Agent need to be
need to be followed. updated.
 Verify the System Hardware and  SPAM version need to be
SAP software components.
updated.
 Stack File Generation and
 Check SM12, SM13, SM37-
download the software
components. No background jobs running.
 Database backup, Profile backup,  Check availability of space in
and kernel backup. path /usr/sap/trans, Kernel,
 Check if License is valid. HANA log and data directory.
Software Update Manager Execution

 Execute the script ./SUMSTART confighostagent <SID>


 Use SUM ABAP URL and enter sidadm credentials.
 Enter a Valid stack configuration file.
 Specify the Upgrade scenario strategy.
Software Update Manager Phases

Extraction Phase Configuration Phase


 Specify the credentials of DDIC,  Enter Configuration Parameters.
HANA TENANT and DATABASE  SPDD and SPAU Transport Request to
HANA SCHEMA.
be added.
 Scanning of download directory and  Pre-requisite SAP notes.
extracts the packages.
 Verify BIND_Patch selections.
 Check SPAM version,source and
target system is valid for update and
system profiles.
Software Update Manager Phases

Checks Phase Pre-Processing Phase


 Space checks in Database.  Lock Development environment phase.
 Background jobs RSVBCHCK.  Repository and Modification Phase
(SPDD and SPAU adjustments).
 Preparation of Downtime.
Software Update Manager Phases

Execution Phase Post-Processing Phase


 System Upgrade  SPAU adjustment
 Downtime Completed  Check SPAU, SPAU_ENH
Post Activities

 Run SGEN
 Backup of HANA Database
 Release the background jobs
 Release the system
 Communicate to all Teams members that the system is ready to be accessed
Issues and Lesson Learnt

 Missing SAP Notes


 SM13: failed update need to be deleted.
 We found the missing components during the initial phase of the SUM tool, so we
rectified again with the stack file
 During the Pre-processing phase we found that CRR replication job was in active
state and in hung state, we check manually through process monitor but still it got
failed within a minute. Later we raised an issue with SAP support and their
development team investigated the issue and found that Global allocation limit
parameter was set incorrectly compared with the physical memory . Once we
rectified the parameter our issue is resolved.
 In post Processing phase, we faced issue with DDLS entity as it clearly mentioned
in error screen with SAP note, so we executed a report to overcome this error.

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