Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Non Unicode systems are no longer supported, Migration procedure may have to cover the Unicode
Conversion as well
DMO and SUM, Procedure is simplified, Sys update and Migration are in ojne tool
DMO Rules
DMO Phases
1. Preparation such as providing stack xml, passwords, dload folders, only makes users and
schemas
2. Creation of shadow repository on source db., done in uptime
3. Switch to downtime, system no longer available, source DB is still running but cant change data
4. Migration of Application Data
5. Finalize Upgrade and migration, change of SAP kernel
6. Start SAP SYStem on new DB and on new Software release
DMO Specifics
- Select both kernel files for source DB and target DB because DMO will need both of them
Dual-Stack Split
- SPAM/SAINT update
- SUM
- SAP Host agent latest patch
- HANA Client Installation
- Migration Key
- License File for target system
Host agent – where browser start the SUM for DMO procedure using HTTP Requests to Host agent
- SAPUI5
Supply SID Admin user and password because SAP Host Agent needs to start the SAPup
- HANA DB is required during DMO, it partitions and distributes tables across HANA Nodes
- 2 Scenarios
o Scale up (Only one node)
o Scale out (several nodes, currently only available for SAP BW)
- DMO offers section HANA SCALE OUT checkbox “Landscape Reorganization
- Scale Out: select checkbox, dialog opens before table creation to import file to HANA
- Scale up: do not select checkbox, UT migration asking you to manually import a file for the table
partitioning
o For tables with more than 2 billion entries
Unit 3 Lesson 2: Continuing DMO Configuration
Steps
Shadow Repository –