EHP Upgrade (SUM)

 Introduction:

SAP Technical Upgrade is a periodic project that is implemented across companies to upgrade their SAP system to the latest released version. Most of the upgrade activities are done by the technical team, and functional consultants' role is limited and mostly confined to regression testing.

Reasons for SAP Technical Upgrade :

Since technology and businesses evolve, companies need to maintain a technological infrastructure that can support that change. This is the major reason why companies should undertake a technical upgrade of their SAP system. Of course, there are many secondary reasons, the significant one being the fact that like all software vendors SAP supports a released version of its software only for a limited period.

Now we can go through the detailed phases included in the SUM upgrade process.

latest SPAM version and Kernal also considered prerequisites 

Prerequisites :

1.Check SYSTEM user is De-active, if yes, it should be activated.

Passwords for the below users should be in hand

DDIC  -->000

SIDADM -- >Linux

SIDADM -->SAP Instance

SYSTEM --> HANA

2.Check the file system space for below directories 

HANA DB :

/usr/sap/

/hana/data

/hana/shared/

/hana/log/

/var/lib

3.Generate stack XML via maintenance planner and download the media to the respective app server.

Take a backup of profiles and any other config files prior to upgrade

Take a backup of reginfo secinfo from the dir data from each of the app-server

Add data file, cofile for SPDD transport at the os level

Perform language checks

4. Extract SUM :

SAPCAR -xvf /upgrademedia/SID_Media/EHP_Media/SUM20SP05_2-80002456.SAR -R /usr/sap/SID/


Registering SUM in SAP Host Agent

Before you start the update, you have to register the Software Update Manager in SAP Host Agent. The following steps run through the registration of the Software Update Manager:

Go to the sum folder and execute the below command

On registration host agent with sum tool, it will provide the below URL.https://:1129/lmsl/sumabap/SID/sluigui

In the dialog box that appears, enter the user name adm and the password.

Here SUM tool will get started, and we need to provide the path for the file Stack.xml, which we have downloaded through the maintenance planner.

Launch SUM as root

hostname:/usr/sap/SID/SUM/abap # ./SUMSTART confighostagent SID


Paste the URL in the browser https://hostname:1129/lmsl/sumabap/SID/sluigui

                                                                                  or

                                                http://hostname:1128/lmsl/sumabap/SID/sluigui


Enter SIDADM user and password 



Browse the Stackfile and click Next




SUM Having mainly 6 steps,

  • Extraction
  • Configuration
  • Checks
  • Preprocessing
  • Execution
  • Postprocessing
SUM Start:

-> Stack XML files browse

-> Scenario Strategy
  •  1.Single System (Longer Duration, no shadow instance)

         2.Standard (Standard configuration, Moderate Resource Assignment) 
               Created a shadow instance from the existing repository.

        3.Advanced (Downtime minimization capabilities, higher complexity, high resource assignment) -
             shadow Instance creates from the software DVD.
  • Input parameters for the type of upgrade (downtime optimizes, higher complexity, high resource assignment)
-> Switch Expert Mode On
 
Step 1.Extraction :
  • DDIC username and password
  • Database Username and password
  • Scanning of download directory where all the patches are placed
  • Extract files to move to EPS/in
  • Identify database & SAP version
  • Check the SPAM version. Skip this if SPAM is already in the latest version
  • <SID>ADM credentials
  • Checks if the source and target system is valid for the update
  • Checks SAP system release
  • Checks the system profiles







Step 2. Configuration:
  • Keep database archiving on
  • Execution strategy for transaction SGEN
  • Maximum number of processes to be used for load generation. SGEN Processes
     (SGen)SAP load generator activates the new repo objects.
  • Batch Process(Uptime) & Batch Process(Downtime)
  • Maximum number of DDL processes (Uptime and Downtime)
  • Number of parallel import processes (R3trans -Uptime, and Downtime)
  • Parallel Phases (Uptime and downtime)
  • Update Instances (update all additional APP servers also)
  • Pre-upgrade S-note list implementation
  • Enhancement package inclusion
  • Add-On selection
  • Modification Adjustment (SPDD transport request and SPAU transport request)







  Mounted SUM on all the application servers to fix the above error

1972214 - Error during Upgrade: ABAP batch job fails with this error "Log writer aborted with RC 1"




Imported the OSS note transport SIDK9A01HL  (Created in DEV box)


Continued with the defaults




Transport request (Co file & data file)  of SPDD must be available in Trans Directory




Step 3. Checks:

  • Space check-in database, if space is Insufficient then extend tablespaces with the script
  • BW checks and phases
  • Activation and conversion checks
  • obsolete & non-adjusted notes in SPDD & SPAU from earlier upgrades
  • Preliminary upgrade processing
  • List Locked SAP objects

Select yes in the above screen and continue. This job is to save the ABAP variants           (Can be performed after upgrade also)


Not required in ECC system

Step 4. Preprocessing:

  • Check for locked objects
  • ABAP Workbench locking
  • Run shadow system for preparation of new release (ACT_UPG, PARDIST, SGEN)
  • SPDD Adjustments
  • Downtime Starts


Transport request (SIDK9A01HP)created in Dev needs to be imported here for fixing the activation error's  


Ignore the phase errors for CEEFISI , /BMC/ (/icorp/ , RWD, PI and continue with the upgrade



Click on Ignore and check later. (Above screen shows locked objects)


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Phase: JOB_RSVBCHCK2 
CHECK OF UPDATE TASK ERRORS 
Find the detailed log in RSVBCHCK.CEP 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
1 ETH010 RSVBCHCK: Checking for open update requests 
3 ETG011 " " 
3 ETG045 ************************************************************************* 
1 ETG011 "Begin of check for open update tasks" 
3 ETG011 " " 
2EETG050 Open update tasks found; please clean them up 
3 ETG011 " " 
2EETG013 "677 Update header records found;" "see transaction SM13 according to SAP Note" "1705774, scenario A" 
3 ETG011 " " 
2EETG011 "End of check for open update tasks" 
3 ETG045 ************************************************************************* 
3 ETG011 " " 
3 ETG010 "Current system is a plugin system;" "checks for queued RFCs and" "extractor queues are being executed" "(if requested)" 
3 ETG011 " " 
3 ETG045 ************************************************************************* 
2EETG012 "Begin of check for pending RFC calls" "in outbound queues" 
3 ETG011 " " 
2EETG011 "8 pending RFC calls in outbound queues found;" 
2EETG012 "please clean them up using transaction SMQ1" "according to SAP Note 1705774, scenario B" 
2EETG012 "See also long text of message MCEX 151" "using transaction SE91" 
3 ETG011 " " 
2EETG012 "1 pending RFC call for application '&2'" "in outbound queues found" 
2EETG012 "1 pending RFC call for application '&2'" "in outbound queues found" 
2EETG012 "1 pending RFC call for application '&2'" "in outbound queues found" 
2EETG012 "2 pending RFC calls for application '05'" "in outbound queues found" 
2EETG012 "1 pending RFC call for application '&2'" "in outbound queues found" 
2EETG012 "1 pending RFC call for application '&2'" "in outbound queues found" 
2EETG012 "1 pending RFC call for application '&2'" "in outbound queues found" 
3 ETG011 " " 
2EETG012 "End of check for pending RFC calls" "in outbound queues" 
3 ETG045 ************************************************************************* 
3 ETG011 " " 
3 ETG045 ************************************************************************* 
2EETG012 "Begin of check for entries in" "extractor queues" 
3 ETG011 " " 
2EETG012 "148279 MC*SETUP entries in extractor queues" "found; please clean them up" 
2EETG012 "See also long text of message MCEX 141" "using transaction SE91" 
3 ETG011 " " 
2EETG012 "Client 700, application 02:" "125288 MC*SETUP entries found" 
2EETG012 "Client 700, application 05:" "22984 MC*SETUP entries found" 
2EETG012 "Client 700, application 11:" "7 MC*SETUP entries found" 
3 ETG011 " " 
A2EEMCEX 141 Struct. appl. "05" cannot be changed due to setup table -> Long text" ""MC05Q00ITMSETUP""700" 
A2EEMCEX 141 Struct. appl. "05" cannot be changed due to setup table -> Long text" ""MC05Q00NTFSETUP""700" 
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0CGRSETUP""700" 
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0SCNSETUP""700" 
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0SGRSETUP""700" 
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0HDRSETUP""700" 
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0ITMSETUP""700" 
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0SCLSETUP""700" 
A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long text" ""MC11VA0HDRSETUP""700" 
A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long text" ""MC11VA0ITMSETUP""700" 
A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long text" ""MC11VA0SCLSETUP""700" 
A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long text" ""MC11VA0STISETUP""700" 
A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long text" ""MC11V_0ITMSETUP""700" 
A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long text" ""MC11V_0SCLSETUP""700" 
A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long text" ""MC11V_0SSLSETUP""700" 
3 ETG011 " " 
2EETG012 "End of check for entries in" "extractor queues"


Ignore the errors and continue. These can be fixed during the downtime phase.

 Enclosed the note for reference

1705774 - Error in phases MAIN_SWITCH/JOB_RSVBCHCK2 or MAIN_SWITCH/JOB_RSVBCHCK_D; Checks after phase MAIN_INIT/JOB_RSVBCHCK* were negative.

Selected lock the development environment later option




The above issue got fixed, Click Next

Release the transport in client 000 (Created for spdd adjustment in 2015 in Prod)



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Phase: ACT_UPG 
DDIC ACTIVATION ERRORS 
Find the detailed log in /usr/sap/CEP/SUM/abap/log/CEDA9A01IZ.CEP 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
<NO ERROR LINES FOUND, BUT HIGHEST EXIT CODE WAS: "8"> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Phase: ACT_UPG 
DDIC ACTIVATION ERRORS 
Find the detailed log in /usr/sap/CEP/SUM/abap/log/SAPA-10003INMDGMDC.CEP 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
<NO ERROR LINES FOUND, BUT HIGHEST EXIT CODE WAS: "8"> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Phase: ACT_UPG 
DDIC ACTIVATION ERRORS 
Find the detailed log in /usr/sap/CEP/SUM/abap/log/SAPA-60841INEAHR.CEP 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
<NO ERROR LINES FOUND, BUT HIGHEST EXIT CODE WAS: "8"> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Phase: ACT_UPG 
DDIC ACTIVATION ERRORS 
Find the detailed log in /usr/sap/CEP/SUM/abap/log/SAPA-61809INSAPAPPL.CEP 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
<NO ERROR LINES FOUND, BUT HIGHEST EXIT CODE WAS: "8"> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Phase: ACT_UPG 
DDIC ACTIVATION ERRORS 
Find the detailed log in SAPA731ESI.CEP 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 

1EEDO519X"DDL Source" "DATABASETABLEALERTQUERY_CDS" could not be activated 
1EEDO519 "DDL Source" "DATABASETABLEALERT_CDS" could not be activated 
1EEDO519 "DDL Source" "DATABASETABLEQUERYUNION_CDS" could not be activated 
1EEDO519 "DDL Source" "DATABASETABLEQUERY_CDS" could not be activated 
1EEDO519 "DDL Source" "DATASETSMEMORYAGGREGATION1_CDS" could not be activated 
1EEDO519 "DDL Source" "DATASETSMEMORYAGGREGATION2_CDS" could not be activated 
1EEDO519 "DDL Source" "DATASETSMEMORYSOURCE1" could not be activated 
1EEDO519 "DDL Source" "DATASETSMEMORYSOURCE3" could not be activated 
1EEDO519 "DDL Source" "DATASETSMEMORY_CDS" could not be activated 
1EEDO519 "DDL Source" "DATASETSTOTALMEMORYSIZE2_CDS" could not be activated 
1EEDO519 "DDL Source" "DATASETSTOTALMEMORYSIZES_CDS" could not be activated 
1EEDO519 "DDL Source" "DATASETSTOTALMEMORYSIZE_CDS" could not be activated 
1EEDO519 "DDL Source" "DATASETSTOTALMEMSIZEAGGR1_CDS" could not be activated 
1EEDO519 "DDL Source" "DATASETSTOTALMEMSIZEAGGR2_CDS" could not be activated 
1EEDO519 "DDL Source" "DATASETSTOTAL_CDS" could not be activated 
1EEDO519 "DDL Source" "STATCURRENTALERT_CDS" could not be activated 
1EEDO519 "DDL Source" "STATCURRENTALERT_TABFUNC" could not be activated 
1EEDO519 "DDL Source" "STATHOSTCOLMNTABSIZE_TABFUN" could not be activated 
1EEDO519 "DDL Source" "STATHOSTCOLMTABSIZE_CDS" could not be activated 
1EEDO519 "DDL Source" "SYSTEMTABLEDESCRIPTION" could not be activated 
1EEDO519 "DDL Source" "SYSTEMTABLEDESCRIPTION_TABFUNC" could not be activated 

3 EDO548XActivate dependent search help "COM_PRWB_01" 
1EEDH006 Search help parameter "COM_PRWB_01"-"PRODUCT_GUID" assigned to nonexistent parameter "ZOM_PRWB_01_GEN"-"PRODUCT_GUID" 
1EEDH003 Search help "COM_PRWB_01" does not include active search help "ZOM_PRWB_01_GEN" 
3 EDH109 Search help "COM_PRWB_01" was not activated 
1EEDO519 "Srch Help" "COM_PRWB_01" could not be activated 
1 ETP111 exit code : "8" 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Phase: ACT_UPG 
DDIC ACTIVATION ERRORS 
Find the detailed log in /usr/sap/CEP/SUM/abap/log/SAPACCC751.CEP 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
<NO ERROR LINES FOUND, BUT HIGHEST EXIT CODE WAS: "8">

 

Repeat the above phase to fix some of the errors


Values are  checked as per note 686357. Continuing with the next steps


Note: Breakpoints can be set on the right-hand side of the browser window, the SUM user interface offers you the option to maintain breakpoints from a list of available breakpoints to pause the update procedure at a specified point.


Vardata values are again checked as per the note and continued to the next steps














Step 5. Execution :

  • Merging of shadow and Real Instance
  • system upgrade
  • Table conversion
  • Downtime Complete


 


Repeat the above phase



Step 6. Post-processing 

  • SPAU change
  • Backup
  • Create folder in trans directory (EHPi)
  • Cleanup process

Select the check box in the above screen and continue




Execute SGEN

Target versions and validation



To know the exact downtime taken for this upgrade, Please find UPGANA.XML file for detailed information from the below-mentioned path:

Location of the file as below
./SUM/abap/htdoc/UPGANA.XML for SUM 1.0
../SUM/abap/doc/analysis/UPGANA.XML for SUM 2.0

for better screenshots :- check site https://www.hightechnology.in/sum-ehp-upgrade-from-ehp6-to-ehp8-part-2/

Explaining the shadow system

A shadow (SHD) system can be used by SUM during system maintenance (or update) parallel to the existing ABAP system.

A shadow system uses the same system-ID as the original system but has a separate instance (shadow instance, own instance number) and a separate repository (shadow repository).

/wp-content/uploads/2014/04/shadow_system_418165.jpg

ℹ An instance combines some processes on the OS level (like work processes, gateway, dispatcher, …) that can be started and stopped together. It is sometimes also called an application server (software view).

ℹ The ABAP repository is a specific part of the database and consists of all development objects like programs, classes, database table definitions, and so on.

The shadow repository contains selected tables: basis tables, some customizing tables, but no application tables. The advantage is that the shadow instance is working on the shadow repository to update these tables to the new software level (target release) already during uptime processing so that the downtime processing is faster.

ℹ Uptime processing is the time during which the SUM is already preparing the update of the system, but the system is still available for end-users to change data.

The shadow system has the advantage that the downtime is reduced, but you have to consider additional resources: memory on the application server for running the additional instance, and space on the database for the additional tables of the shadow repository. (Remember that the repository is typically only a very small part of the database content, and it is independent of the total DB size.)

The work on the shadow repository makes it necessary to prohibit changes on the original repository. That is why transport and development of ABAP objects are forbidden once the creation of the shadow repository started..

When and how a shadow system is used

If you now think that the preconfiguration mode Single System (see first figure above) means that no shadow system is being used, you may or may not be correct, as this depends on the type of system maintenance you are executing (explained below). All we can say right now is that both preconfiguration mode Standard and Advanced do use the shadow system.

Remember the two possibilities above to create the shadow house: “copy your house, or create from blueprint”?

For system maintenance, this is equivalent to the difference between update and upgrade:

An upgrade

  • is a release change (like SAP ERP 5.0 to 6.0)
  • creates the shadow repository from DVD

An update

  • is an implementation of EHP or SPs (like SAP ERP 6.0 EHP3 -> EHP7)
  • creates the shadow repository from the existing repository

     ❗ Note that the path to SAP ECC 6.0 EHP 8 is an upgrade path! See Why EHP 8 is different

     ℹ Note that in the documentation, we just say update for all scenarios, like the name of SUM contains only update as the general term.

EHP8 uses DVD to create shadow instance .so, it is called upgrade instead of update.

Single System Mode

If you choose single system mode in the preconfiguration mode (see first screenshot above), this means:

  • An update (implementing SPs or EHPs) does not create or use a shadow system at all
    This maintenance type is sometimes also referred to as “transport like”
  • An upgrade (release change) creates a shadow repository (from DVD) and a shadow instance, but the original instance is stopped as long as the shadow instance works on the shadow repository; only a single system (instance) is running at a time -> “Single System Mode”
    Note:
    with SUM 2.0 SP 07 and higher, the single system mode is no longer offered for upgrades.

ℹ Single System Mode is sometimes also referred to as resource-minimized mode, as only few additional resources are required. On the other hand, the Standard and the Advanced Mode are both referred to as downtime-minimized mode, as only they offer downtime minimization. After handling the preconfiguration mode dialog (first screenshot above), the next dialog “Parameters for procedure” allows setting the number of processes, and it lists the mode as resource or downtime minimized (e.g. “The tool uses strategy Downtime-minimized.”).

Difference between Standard and Advanced Mode

  • Both use a shadow system to minimize the downtime
  • Choosing Advanced Mode sets the default parameters for the number of processes to higher values
    (which could be achieved manually with Standard Mode as well)
  • But only the Advanced Mode offers the option near Zero Downtime Maintenance (nZDM),
    as described in the following blog Near-Zero Downtime Maintenance for SAP Business Suite Systems

  • NZDM quick facts:   High resource allocations and record & reply to avoid manual intervention



Space requirement: Minimum of 40 GB for SUM directory and 20 GB for DIR_TRANS.
                               
                                      For Database, it ranges from 50 to 200 GB


Log files for SUM : usr/sap/SID/abap/log

Start shadow instance : cd /usr/sap/SID/SUM/abap/bin --> ./SAPup  startshd
Stop shadow instance :  cd /usr/sap/SID/SUM/abap/bin --> ./SAPup  stopshd
Lock Shadow Instance : cd /usr/sap/SID/SUM/abap/bin --> ./SAPup  lockshd
unlock shadow instance: cd /usr/sap/SID/SUM/abap/bin --> ./SAPup  unlockshd

How to log in to Shadow Instance?

1.Create a new logon in SAP GUI with the same SID and Host with shadow instance number (Instance number can be found in SUM utilities --> Sum Shadow system parameters)

2.Login to an original instance and go to Sm59 --> RFC SAP_UPGRADE_SHADOW_SYSTEM -->Remote login to shadow Instance.

  How we will know that shadow instance has been created in preprocessing Phase?
     A. Pf – ef | grep shd Note: Shadow instance will be +1 more than instance, 00 will 01

  There is a report we need to run in preprocessing Phase during SPAU/SPAD?
     A. UPGACTKORR Its Activate Request in Shadow System.













































































Comments

Post a Comment

Popular Posts

Interview Questions

Image
1. Startup profile from 7.3? Answer: Now the Start profile contents are merged with the Instance profile. With help of the new Instance, profile SAP processes are started and at the same time, instance-specific parameters are read. 2. SAP Application server connects with Database using database client. 3. Difference b/w profiles? Default.PFL - default profile Instance Profile - SID_DVEBMGS"nr"_Hostname location = usr/sap/SID/SYS/Profile 4. Below are the common errors in SAP transport management Return code 4:  Imported with warnings Generation of program, colomns or row missing . Return code 8 :  Imported with errors Syntax error Program generation error Dictionary activation error or method execution error Return code 12 :  Indicates Import Cancelled Program cancelled due to job Import cancelled due to object missing Import cancelled due to object not active Return code 18 :  Indicates Import Cancelled Due to system down while import Due to user expired during import Due to
Read more

SAP Logon Configuration(Load Balancing)

Image
Logon groups (or work groups) are configured to dynamically distribute the load being processed by the dialog work processes. Setting up logon groups helps in uniform distribution of the work load across the available instances. While logging on using a logon group, the ABAP message server is contacted to identify the instance with best performance statistics within the selected logon group . A report runs in SAP every 5 minutes which determines the load across each server and updates in the memory area of the message server. This information will be used by SAP GUI to determine the best instance to distribute the next user.   SAP Logon Process Let’s start with discussing an overview of SAP Logon process. High-level understanding of the process will help to explain details of SAP Logon configuration. SAP Logon Process Overview When user(s) accessing SAP system via  SAP GUI , the request is forwarded into ABAP dispatcher for the direct logon. If SAP GUI is using logon group, the logon w
Read more

SAP Startup Troubleshooting

Image
  1. IS DATABASE UP AND RUNNING? This is an  absolute  prerequisite for SAP SYSTEM to start. In order to test this, operating system command  R3trans -d   can be executed (as SIDadm user). Any return code different than 0 means that DB cannot be reached by DIALOG work processes, and so SAP system will not initiate. The following return indicates that the database is up, running, and reachable by SAP work processes: <hostname>:SIDadm > R3trans -d This is R3trans version X.xx (release 742 - 18.11.14 - 20:14:09). unicode enabled version R3trans finished (0000). -->There is  NO POINT  in moving the analysis further while the return code is different than zero. --> In case the return code is different than zero, please involve your DBA/Network/OS teams. 2 . IS SAP STARTUP AGENT (SAPSTARTSRV) RUNNING? There must be  ONLY ONE  sapstartsrv process running for each instance. Examples for each platform below: Examples As an example, we will use a centralized system with the follow
Read more

HANA Installation & upgrade

Image
  Software Download: SAP HANA System Types : Ø   Single-host system - One  SAP HANA  instance on one host Ø   Multiple-host (distributed) system - Multiple  SAP HANA  instances distributed over multiple hosts, with one instance per host. SAP HANA Deployment Types : Tenant Databases : The tenant database deployment type makes it possible to run several SAP HANA instances on the same hardware in a production environment. Multiple Components on One Database (MCOD) : MCOD deployments are characterized by multiple applications on one SAP HANA system. SAP supports deploying and running multiple applications on a single SAP HANA production database  only  for packaged applications and scenarios listed on the "White List" included in SAP Note 1661202. Virtualized : SAP HANA systems can be run on virtual machines with restrictions to the hypervisor (including logical partitions). Multiple Components on One System (MCOS): MCOS deployments are characterized by
Read more

SAP HANA Backup

Image
  SAP HANA Persistence To ensure optimal performance, the SAP HANA database holds most of its data in-memory. However, it still uses persistent storage to provide a fallback in case of failure.   During normal database operation, data is automatically saved from memory to disk at regular savepoints . Additionally, all data changes are recorded in the redo log . The redo log is saved from memory to disk with each committed database transaction. After a power failure , you can restart the database as you would with any disk-based database. It then returns to its last consistent state by replaying the redo log since the last savepoints . Although savepoints and log writing protect your data against power failures, savepoints do not help if the persistent storage itself is damaged . To protect against data loss because of disk failures, backups are required . Backups save the payload (the actual data) of the data area and log area to different locations.   Types of Back-ups: 1.
Read more

SAP Transport Management System (STMS)

Image
TMS is used to move, manage and control copy development objects and customizing settings in an orderly fashion across SAP Landscape. STMS [SAP Transport Management System] Domain Controller–:  It is used to control the landscape. There will be only one domain controller in the landscape. Initially, it is set to development and later can be moved to on higher available system such as PRD/QAS/Pre7/ production but to keep things simple most of the cases we keep DEV as Domain Controller Member Systems–: The other systems are included in the domain referred to as member systems.  How to Configure   STMS Log on to the SAP system, which is decided to be the Domain Controller, in client  000  and enter the transaction code  STMS. If there is no Domain Controller already, a system will prompt you to create one. When the Transport Domain is created for the first time, the following activities happen in the background: Initiation of the Transport Domain / Landscape / Group Creating the user  TMS
Read more

SAP Kernel Upgrade in Distributed System

Image
What is the kernel of an SAP system? The kernel is a central program that acts as an interface between the SAP application and operating system. These files help startup the R/3 system, initialize the memory, create buffers and start managing the requests from users and effectively utilizing of hardware resources. The kernel is also responsible for starting and stopping all the application services like dispatcher, message server, collector, etc. Why Kernel Upgrade? SAP Kernel is the core of the application. Like all other applications, the Kernel contains the executable files (.EXE files for stating various processes in SAP). The Kernel is the heart of the operating system. It contains those files which are used to run every event in SAP. E.g.|: starting database, shutdowns of the database, starting sap, shutdown of sap, saposcol, to uncar the sap files etc. That's the reason why when a Kernel upgrade is done it means new versions of the various EXE files replace the older version
Read more

Set Up SAP HANA System Replication with hdbnsutil

Image
  Procedure:                                               SITE -A Enable system replication on the primary system(SITE A) as follows: In the Administration editor of SAP HANA studio, choose the  Configuration  tab and ensure that  log_mode  is set to "normal" in the  persistence  section of the  global.ini  file. Log mode  normal  means that log segments must be backed up. Log mode  overwrite  means log segments are freed by the savepoint (therefore only useful for test installations without backup and recovery). Do an initial data backup or create a storage snapshot. In multiple-container systems, the system database and all tenant databases must be backed up. As  <sid>adm  on the command line enable the primary for system replication and give it a logical name with the following command. The primary system must be online at this time: cd /usr/sap/<sid>/HDB<instancenr>/exe hdbnsutil -sr_enable --name=SITEA To check if the site has been successfully enable
Read more

SAP Client Copy

Image
Client copy means " transferring client-specific data"  within the same instance(SID) or between different instances(SID). Client copy can be performed with three different methods - Local client copy. Local client copy. Remote client copy. Client Import/Export. Prerequisites : Disconnect and lock dialog users. Suspend background jobs : This can be done using the report BTCTRNS1. The jobs will be released afterward using the report BTCTRNS2. Client Space check by using the report "RSSPACECHECK" in SE38. 1. Local Client Copy A local client copy copies between clients within the same SAP system. The local client copy must be initiated from the target client. The steps to perform a local client copy: Create an entry for the target client in the client maintenance table, choose transaction  SCC4 . In this example, client 101 will be created: Log on to the target client (client 101) as  SAP*  with the initial password pass (The user SAP* with the password pass is only ac
Read more