Upgrade SAP BW/4HANA 2.0 – the time is now …

Last Changed: 29th of November 2021

Upgrade SAP BW/4HANA 2.0 – the time is now …

Note 3087277 – End of 2021 is the end of Mainstream Maintenance of BW/4HANA 1.0

Since SAP BW/4HANA 2.0 initially was available, it was only possible to start an Upgrade to Version 2.0 without any Add-On’s like BPS or BCS which are available now.
The current Version brings additional Features to the Market
– SAP BW/4HANA – Technical Overview
To implement SAP BW/4HANA 2.0 either as on-premise or IaaS see
– SAP BW/4HANA 2.0 – CAL for it …

Please also Note, that SAP BW/4 differs from an SAP ABAP 1809 Foundation or higher as follows:

Evolution of the SAP BW/4HANA Stack

SAP Help: SAP BW/4HANA Master Guide – What’s new in SAP BW/4 HANA 2.0

Now let’s see the Upgrade process in the Maintenance Planner (MP)

Preparations for the usage of the Maintenance Planner

• Update the SLD with tx. RZ70 from your BW/4 Backend System
• Synchronize the LMDB from SLD in the SAP Solution Manager
• Upload the Data to the Maintenance Planner

This is described in detail in the Blog – S/4HANA 1709 FPS03 – back on the Mothership again … Or as an Alternative, create the system.xml and upload this directly to the MP

If the “Installed Software Component Versions” differ from the “Installed Product Versions”, please make sure that a proper and corrected source system template is used for the maintenance process.

Steps in the Maintenance Planner

MP – Select the target release and released support package(s) …

MP – Check the Plan Changes for your System

MP – Add the Non-ABAP components …

Optionally you can deselect the Language Packages you don’t need here to save time/space for the download of the load based export. Download the stack.xml and the software content and you are ready the run the SUM tool

MP – final check of the selected files

MP – download the stack.xml and push to Download Basket

MP – the MP process is finished

Steps in the Software Update Manager (SUM)

Disclaimer
Please Note the following screenshots are already based on SUM 2.0 SP06. So you might see differences in higher versions. You will just see the most important screens. Additional Details can also be seen in the Blog – Upgrade to S/4HANA 1809 SPSx – the final frontier

Always get the latest Version from – Software Logistics Toolset

Note 2832250 – Central Note – Software Update Manager 2.0 SP08 [lmt_020]
Note 2882379 – Central Note – Software Update Manager 2.0 SP09 [lmt_021]
Note 2935104 – Central Note – Software Update Manager 2.0 SP10 [lmt_022]

As you can imagine, a current Version of SAP HANA 2.0 is mandatory. I chose the latest Version from SP04 – SAP HANA 2.0 SPS 04 Database Revision 042. Meanwhile the latest Version (20.11)

Note 2993533 – SAP HANA 2 SPS05 Revision 054.00
Note 3021026 – SAP HANA 2 SPS05 Revision 055.00
Note 3043459 – SAP HANA 2 SPS05 Revision 056.00

Don’t forget to update the SAP HANA Client for the ABAP System as well, especially when you use a SAP HANA Version from 2.0.40.0 onwards …

Note 2954097 – Checks after phase MAIN_SHDCRE/CREATEDBCON_SHDONTARGET were negative!

Since the Blog – Upgrade was never been easier… was created, the SUM tools for DMO and Upgrade were improved a lot, including the SUM Utilities …

use you resources in the best possible manner and change the process parameters to improve the performance in certain phases over the time and systems …

As for NetWeaver/SAP Application Server based systems like BWoH and BW/4HANA the option “Single Server” is the optimal option in terms of overall runtime, a shadow instance mandatory used as the BW/4HANA 2.0 sources are available as “load-based” delivery.

Update 20th November 2020: SAP UI_754 Add-On is now included in the Maintenance Planer Request. SAP UI_754 is the highest Version you can apply on SAP BW/4 2.0

In case you choose the option “near zero downtime optimisation” (nZDM) for a SAP BW/4 HANA system (which nor really make sense … ) the following issue can happen, if some prerequisites are not applied at this time.

Blog – New dialog sequence with SUM 2.0 SP 06

optional: nZDO option with SAP BW/4 HANA Upgrade

Possible Problems/Issues:

• Shadow Instance Port is occupied
• Several sapstartsrv commands are running simultaneously
• Mixup of the profile parameters used for ENSA 1.0 and ENSA 2.0
• cleanup of SAP-IPC-Objects (cleanup <nr> remove and restart)
• Problems with the SAP HANA Client 2.0 SP05 connectivity
• Issues accessing the SAP HANA secure store

Note 2630416 – Support for Standalone Enqueue Server 2
Note 2681666 – Shadow Instance start hangs while using SUM – Phase START_SHDI_PREPUT
Note 2754662 – SUM upgrade/Installation of S/4HANA fails due to Enqueue problem
Note 2967389 – SAP HANA Client 2.6.54
Note 3033226 – SAP HANA Client 2.7.26
Note 3027730 – SAP HANA Client 2.8.16
Note 2876608 – Error (91009) Timeout Waiting for the Secure Store Access Lock
Note 2940886 – SJOBREPO: Generate job should not be triggered in shadow system
Note 2954097 – Checks after phase MAIN_SHDCRE/CREATEDBCON_SHDONTARGET were negative!

Even that the Process List of the Enqueue Server (03) shows “YELLOW”, the Shadow Instance (04) can connect like the primary instance (03).

server:b4hadm> DIR_PUT/exe/sapcontrol -nr 02 -function GetProcessList
17.09.2020 23:48:48
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
msg_server, MessageServer, YELLOW, Running but not responding, 2020 09 17 22:21:40, 1:27:08, 140954
enserver, EnqueueServer, YELLOW, Running but not responding, 2020 09 17 22:21:40, 1:27:08, 140955
server:b4hadm> DIR_PUT/exe/sapcontrol -nr 03 -function GetSystemInstanceList
17.09.2020 23:49:12
GetSystemInstanceList
OK
hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus
lt5088, 3, 50313, 50314, 3, ABAP|GATEWAY|ICMAN|IGS, GREEN
lt5088, 2, 50213, 50214, 1, MESSAGESERVER|ENQUE, YELLOW
server:b4hadm> DIR_PUT/exe/sapcontrol -nr 04 -function GetProcessList
17.09.2020 23:49:20
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
enq_server, Enqueue Server 2, GREEN, Running, 2020 09 17 23:13:11, 0:36:09, 157134
msg_server, MessageServer, GREEN, Running, 2020 09 17 23:13:11, 0:36:09, 157135
disp+work, Dispatcher, GREEN, Running, 2020 09 17 23:13:11, 0:36:09, 157136
gwrd, Gateway, GREEN, Running, 2020 09 17 23:13:12, 0:36:08, 157140
icman, ICM, GREEN, Running, 2020 09 17 23:13:12, 0:36:08, 157141
server:b4hadm>

Depending on the used scenarios, mixes scenarios (SAP BW/4HANA and native SAP HANA) are recognized as “MCOD System”, it is one system …

Even you didn’t checked the system before either with the ASU toolbox or the usage of the task list, you can always do the configuration dynamically … (in this case tx. SE14 – clean)

If you will be asked for certain upgrade strategies in the Phase
SUM-Phase: PREP_INIT/ADDON_INFO

Note 2452819 – Release strategy for the ABAP add-on BPC4HANA
Note 1330000 – SAP BW/4HANA, Business Consolidation Add-On ( “BCS/4HANA” )
Note 2805174 – Release strategy and Maintenance Inform for the ABAP add-on BCS4HANA 200
Note 2393067 – Release strategy for the ABAP add-on BW4CONT / BW4CONTB
Note 2705605 – Release strategy and Maintenance Information for the ABAP add-on SAP DSIM 1.0 FOR BW/4HANA

Only Install the Languages you need to save additional runtime …

depending on the installed Add-On’s there might be inconsistencies with the result of the MP and the created stack.xml with the SAP Backend. In this case, you only can go back to the MP and create a new stack.xml based on the updated system.

The minimum installed Version of the BPC 11.0 Add-On on SAP BW/4HANA 1.0 is SP07

SUM-Phase: PREP_EXTENSION/BIND_PATCH

Update from 20th of November 2020: SAP UI_754 SP05 as Target Level, as coming from 7.53 SP07 (update is shown a bit “unsuitable” … ;-))

Franz Beckenbauer would say: “it’s a classic, ein Klassiker” this is BW my friends … 😉
from now on the time counts …

Now it is time to improve the runtime and the real downtime starts …

Note 2597660 – Lack of performance in phase RUN_RUTDDLSCREATE

SUM-Phase: MAIN_SHDCRE/EU_IMORT_ALL 

SUM-Phase: MAIN_SHDCRE/SHADOW_IMPORT_UPG1

The Shadow Instance 

check the Blog – Upgrade to S/4HANA 1809 SPS0x for the solution …

enhance the shadow instance profile with these parameters.

check /usr/sap/SUM/abap/system/B4H/SYS/profile
add the profile parameters in advance

abap/buffersize = 1400000
abap/heap_area_total = 108197104800
abap/shared_objects_size_MB = 1024
em/initial_size_MB = 65536
em/global_area_MB = 49152
em/proc_max_size_MB = 128000000
em/proc_use_stdheap = TRUE
ipc/shm_psize_10 = 198000000
ipc/shm_psize_40 = 1978000000
rsdb/esm/buffersize_kb = 524288
rsdb/obj/buffersize = 524288
rsdb/otr/buffersize_kb = 16384
rsdb/tbi_buffer_area_MB = 2048
rdisp/PG_MAXFS = 128000
rdisp/PG_SHM = 128000
ztta/roll_extension = 40000000000

Like already described with the SAP S/4HANA Upgrades: don’t ignore anymore the ACT_UPG Phase, as the return will follow immediately in Phase PARCONV_UPG …

Note 2793766 – CDS View cannot be created/activated – Repair tool
Introducing tx. SDDLAR

the Issue in the exchange of the SAP Kernel executables prevents the SUM process to replace the file sapuxuserchk and it is DB independent

cd /usr/sap/B4H/SYS/exe/uc/linuxx86_64/
server:/usr/sap/B4H/SYS/exe/uc/linuxx86_64 # dir sapuxuserchk
-rwsr-xr-x 1 root sapsys 1327618 Sep 17 19:42 sapuxuserchk
server:/usr/sap/B4H/SYS/exe/uc/linuxx86_64 # rm sapuxuserchk
server:/usr/sap/B4H/SYS/exe/uc/linuxx86_64 #

Note 2793766 – CDS View cannot be created/activated – Repair tool
Introducing tx. SDDLAR

make sure your BW-MT and ABAP in Eclipse access is updated to the latest versions – SAP First Guidance – Implementing BW-MT as the new SAP BW Modeling Experience

Note 2607883 – Checking Column view and calculation scenario/ calculation model errors in BW Queries

Phase MAIN_NEWBAS/TABIM_UPG

Phase MAIN_NEWBAS/HANA_DEPLOY_UPG

Phase MAIN_NEWBAS/XPRAS_AIMMRG

Is this the end?

the software components and the product versions are in sync …

SAP BW/4HANA 2.0 – Installed Software Component Versions

after a short check running SPAU, it seems I have earned some objects in the /SPN/ namespace which were not in the system before …

Update from 10th of April: Installed Product Versions

Finally: The timing and runtime

Overall I have spent a half day running the MP process and downloading the necessary software. after this I started the Upgrade. Later this day I have continued the SUM procedure and finished the day after. So the netto runtime was 7h, which actually is a good mark. (1st brutto runtime 2d)

Update 18th of September: addition run with the nZDO option

the Upgrade run with the nZDO option was running slightly longer, nevertheless more support packages and an additional Add-On was selected. So an overall runtime of 8h looks pretty good.

SAP BW/4 HANA – Upgrade with the nZDO option

SAP BW/4HANA on premise is back …

• What’s new with SAP BW/4HANA 2.0 SP04
• What’s new with SAP BW/4HANA 2.0 SP07

Hot of the press: BW-PCA is available for SAP BW/4HANA!

Note 2743291 – PCA for BW/4HANA
Note 2570363 – Availability of BW PCA for BW/4HANA
Note 1707321 – BW System Copy: Post Copy Automation (BW-PCA)
Note 1614266 – System Copy: Post-Copy Automation (PCA) / SAP Landscape Management (LaMa)
Note 2821852 – HANA SDA & SDI connections in context of BW and BW/4HANA system copies

Roland Kramer, SAP Platform Architect for Analytics SAP SE
@RolandKramer

“I have no special talent, I am only passionately curious.”