BW on HANA Upgrade & Migration via SUM DMO

SAP






BW on HANA Upgrade & Migration via SUM DMO — Step-by-Step Guide


BW on HANA Upgrade & Migration via SUM DMO (System Move) — Step-by-Step Guide

Project highlight: Migrated a BW system from DB2 11.5 (NW 7.3) to SAP HANA 2.0 SP07 Patch 59 (NW 7.5 SP33) using SUM DMO with System Move. The database compressed from 1.2 TB to ~300 GB (~1/4), demonstrating HANA’s strong compression and storage benefits.

Source & Target System Details

  • Source: DB2 11.5, SAP NW 7.3 — DB Size: 1.2 TB
  • Target: SAP HANA 2.0 SP07 Patch 59, SAP NW 7.5 SP33 — DB Size: ~300 GB

Why SUM DMO (System Move)?

SUM DMO with System Move automates the combined upgrade and database migration. It supports a parallel-mode approach (preprocessing on source and target) and uses rsync during downtime to transfer the exported data. This method reduces manual steps and shortens downtime when planned correctly.

High-level Checklist for BASIS Consultants

Below checklist as a baseline; always validate against the official SAP NetWeaver Upgrade & Update Master Guide and relevant SAP Notes.

Sr. No. Activity Location Comments
1 Perform BASIS refresh steps after cutover Source VM On source POC DB
2 Build HANA DB VM with OS Hardening Target VM Validate SAP Notes for Hardening
3 Build a SHELL System on HANA DB with NW 7.5 App Target VM —
4 Pre Upgrade BW Cleanup Steps in Source System Source VM Follow NetWeaver Upgrade Guide
4.1 Activity from Guide 2.4 till 2.13 Source VM As per Master Guide
4.2 Cleanup of old SPAU/SPDD from last upgrade Source VM —
4.3 Implement missing SAP Notes (capture in TR) Source VM Notes: 2344014, 2408559 — move to Production
4.4 Cleanup via report RSDDSTAT_DATA_DELETE Source VM As per SAP Note 2471950 — select Query Statistics, Static Logging, DTP, WHM, Workspace Proposal
5 Trigger SUM Upgrade — Uptime Phase (Select System Move) Source VM Target DB = SAP HANA
5.1 Require DDIC-000 Password Source VM —
5.2 Generate Migration Key Source VM —
5.3 BI_CONT 757 Password Source VM Example: 3821837 (ensure secure handling)
5.4 /ASU/upgrade in working client Source VM —
5.5 Release Open TRs Source VM Lock development
5.6 DMO with System Move (Parallel Mode) — Put Target Hostname Source VM Ensure SSH between source & target without password via <sid>adm
5.6.1 Move source SUM folder to target (same location) Target VM Include SUM DVDs (language & export)
5.6.2 Continue with SUM — Preprocessing Phase Source VM Preprocessing on source
5.6.3 Continue with SUM — Downtime Phase Source VM Take backup; rsync will sync data export to target (25–30% of existing DB size copied to load dir)
5.6.4 Post Downtime — wait for SYNC completion Target VM Downtime completed in source system
5.6.5 Trigger SUM in Target System (parallel) Target VM Auto detect hostname change — target starts preprocessing
5.6.6 Continue SUM in Target System Target VM Fill required fields, passwords, tenant DB, stack config dir
6 Choose HANA default migration parameters Target VM —
7 Adapt HANA Configuration Parameters (default) Target VM Continue with SUM screen
8 SPDD changes in Shadow System Target VM Handover for SPDD modifications; capture in TR
9 Continue with SUM post-SPDD confirmation Target VM —
10 Continue with SUM — Downtime Phase Target VM —
11 Post Downtime — Apply SAP Note 1908075 Target VM Run command on tenant DB (post processing)
12 Continue with SUM — Post apply 1908075 Target VM Take HANA DB backup on local mount point
13 Handle PSA_VERSION_CREATE failures Target VM See SAP Notes 3134813 & 2875170 — may relate to RSA1 connections
14 SPAU Modifications Target VM Capture in TR; move to production post-upgrade
15 Cleanup Processing — Post Processing Target VM —
16 Post Processing Completed Target VM Inform Functional team to complete SPAU/SPDD steps
17 Trigger SGEN in system Target VM —
18 Handover system for functional upgrade Target VM —
19 Backup Configuration Target VM Finalize backup and recovery plan

Key Learnings

  • SUM DMO with System Move provides a robust way to combine upgrade and database migration.
  • Pre-upgrade cleanup (SPAU/SPDD, statistics cleanup) is crucial to avoid long post-processing cycles.
  • HANA delivers excellent compression — reduced database footprint and improved query performance.
  • Close collaboration with functional teams is required for post-upgrade activities (SPAU, SGEN, RSA1 checks).

Conclusion

Upgrading BW to HANA using SUM DMO (System Move) is a practical and efficient approach. Proper planning, pre-upgrade cleanup, and post-upgrade validation are essential to a successful migration. The compression observed on this project (about 1/4 the original size) highlights a major advantage of moving to SAP HANA.

Important SAP Notes for BW on HANA Upgrade & Migration –

1275776 – Linux: Preparing SLES for SAP environments
2684254 – SAP HANA DB: Recommended OS settings for SLES 15 / SLES for SAP Applications 15
2235581 – SAP HANA: Supported Operating Systems
2578899 – SUSE Linux Enterprise Server 15: Installation Note
1437105 – Operating system limits for SAP instances
3614625 – SAP HANA 2 SPS07 Revision 079.06
2547309 – Downtime-optimized DMO with SUM 2.0
3573801 – Database Migration Option (DMO) of SUM 2.0 SP23
1600929 – SAP BW powered by SAP HANA DB: Inform
2203650 – Important SAP Notes for SAP BW 7.50, powered
1943931 – Installation or upgrade for the ABAP add-on BI_CONT or BI_CONT_XT 757
1734333 – BW Pre and Post Upgrade and Migration Tasks
3448609 – List of documents important for a SAP BW / SAP BW/4HANA upgrade
1829728 – BW Housekeeping Task List

Important SAP Guides for BW on HANA Upgrade & Migration-

https://learn.microsoft.com/nl-nl/azure/sap/workloads/hana-get-started
https://help.sap.com/doc/85bfb5ab1de94c42856aa8bc4c4476c6/7.5/en-US/upg_mg_nw_75.pdf
https://help.sap.com/doc/38301960cfe4484587f9cedb8c6a740f/dmosum20.23/en-US/dmo_of_sum2_to_hana.pdf
https://help.sap.com/doc/7dd31bd5171046948130cfe87b91fa20/7.5/en-US/UUG_NW75_ABAP.pdf

See also – HANA DB Calculation

#SAP
#SAPBASIS
#SAPHANA
#BWonHANA
#SUMDMO
#SAPUpgrade
#SAPMigration
#HANA2
#SAPNetWeaver
#SAPBTP


Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.