Ha250 en Col09 Fv Inst Ltr

(1)

HA250

Migration to SAP HANA Using DMO

SAP HANA Date Training Center Instructors Education Website

Instructor Handbook

Course Version: 09

Course Duration: 2 Day(s) Material Number: 50128514 Owner: Boris Rubarth (D029945)

(2)

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

Trademarks

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.

Apple, App Store, FaceTime, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Citrix, ICA, Program Neighborhood, MetaFrame now XenApp, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

Edgar Online is a registered trademark of EDGAR Online Inc., an R.R. Donnelley & Sons Company. Facebook, the Facebook and F logo, FB, Face, Poke, Wall, and 32665 are trademarks of Facebook. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik, and Android are trademarks or registered trademarks of Google Inc.

HP is a registered trademark of the Hewlett-Packard Development Company L.P.

HTML, XML, XHTML, and W3C are trademarks, registered trademarks, or claimed as generic terms by the Massachusetts Institute of Technology (MIT), European Research Consortium for Informatics and Mathematics (ERCIM), or Keio University.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.

INTERMEC is a registered trademark of Intermec Technologies Corporation. IOS is a registered trademark of Cisco Systems Inc.

The Klout name and logos are trademarks of Klout Inc.

Linux is the registered trademark of Linus Torvalds in the United States and other countries. Motorola is a registered trademark of Motorola Trademark Holdings LLC.

(3)

Novell and SUSE Linux Enterprise Server are registered trademarks of Novell Inc. OpenText is a registered trademark of OpenText Corporation.

Oracle and Java are registered trademarks of Oracle and its affiliates. QR Code is a registered trademark of Denso Wave Incorporated.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld are trademarks or registered trademarks of Research in Motion Limited.

SAVO is a registered trademark of The Savo Group Ltd. The Skype name is a trademark of Skype or related entities.

Twitter and Tweet are trademarks or registered trademarks of Twitter.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Wi-Fi is a registered trademark of Wi-Fi Alliance.

SAP, R/3, ABAP, BAPI, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, Sybase, Adaptive Server, Adaptive Server Enterprise, iAnywhere, Sybase 365, SQL Anywhere, Crossgate, B2B 360° and B2B 360° Services, m@gic EDDY, Ariba, the Ariba logo, Quadrem, b-process, Ariba Discovery, SuccessFactors, Execution is the Difference, BizX Mobile Touchbase, It’s time to love work again, SuccessFactors Jam and BadAss SaaS, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany or an SAP affiliate company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

Disclaimer

These materials are subject to change without notice. These materials are provided by SAP SE and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

(4)

(5)

About This Handbook

This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.

Typographic Conventions

American English is the standard used in this handbook. The following typographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options.

Also used for cross-references to other documentation both internal and external.

Example text Emphasized words or phrases in body text, titles of graphics, and tables

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Example text Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

(6)

Icons in Body Text

The following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point Exception or caution

Procedures

Indicates that the item is displayed in the instructor’s presentation.

(7)

Course Overview

This course covers the one-step migration procedure to SAP HANA database called Database Migration Option (DMO) of Software Update Manager (SUM).

Target Audience

This course is intended for the following audiences: • System administrators

• Technical consultants

Course Prerequisites

Required Knowledge

• ADM328 or similar experience with system maintenance using Software Update Manager (SUM)

• HA100 SAP HANA – Introduction

Course Duration Details

Unit 1: Getting Familiar with DMO

Listing DMO benefits 15 Minutes

Explaining DMO basics 25 Minutes

Exercise 1: Check source system status 10 Minutes Exercise 2: Check status of SAP HANA database 15 Minutes

Unit 2: Preparing DMO Procedure

Ensuring DMO prerequisites are fullfilled on the host 20 Minutes Exercise 3: Ensure DMO prerequisites are fulfilled 15 Minutes Configuring SAP Host Agent for DMO 15 Minutes Exercise 4: Configure SAP Host Agent for DMO 15 Minutes

Examining the DMO UI 15 Minutes

Unit 3: Configuration of DMO Procedure

Starting the DMO run 10 Minutes

Exercise 5: Start the DMO procedure 30 Minutes

Continuing DMO configuration 15 Minutes

Exercise 6: Continue DMO configuration 40 Minutes Configuring DMO step Preprocessing 15 Minutes

(10)

Listing DMO procedure steps 45 Minutes Analyzing logs and tuning the DMO downtime 30 Minutes Exercise 8: Analyze DMO migration logs 45 Minutes

Resetting the DMO procedure 10 Minutes

Exercise 9: Reset the DMO procedure 30 Minutes Exercise 10: Prepare and run DMO procedure again 30 Minutes DMO steps after lock of development environment 20 Minutes

DMO release schedule 35 Minutes

Unit 4: Appendix

Listing migration options to SAP HANA 20 Minutes

Course Goals

This course will prepare you to:

• Evaluate the migration options to SAP HANA • Plan and execute the DMO procedure using SUM

Course Objectives

After completing this course, you will be able to:

• Use the one-step migration procedure (DMO) to SAP HANA autonomously

Important Information

It is strongly recommended to check necessary information published on the SAP Service Market Place. All information essential for course preparation like instructor guides, system setup guides, trouble shooting guides, logon information, and so on, you will find under the alias /curr-info (http://service.sap.com/curr-info).

In case you cannot access this site please ask the responsible education coordinator (the sender of this document) to make the relevant information available to you.

(11)

Unit 1

1

Getting Familiar with DMO

.

Unit Overview

Overview on DMO.

Unit Objectives

After completing this unit, you will be able to: • list the benefits of the DMO procedure • list information sources for DMO

• explain DMO from a technical perspective

Unit Contents

Lesson: Listing DMO benefits ... 2

Lesson: Explaining DMO basics ... 10

Exercise 1: Check source system status ... 15

(12)

Lesson:

2

Listing DMO benefits

Lesson Duration: 15 Minutes

Lesson Overview

This lesson discusses the benefits of DMO compared to the classical migration.

Lesson Objectives

After completing this lesson, you will be able to: • list the benefits of the DMO procedure .

Business Example

As a member of the implementation team for a system migration, you need to know more about DMO.

DMO benefits

DMO in a nutshell is listed below:

Scenario

- You want to migrate your existing ABAP-based SAP system to SAP HANA DB - You choose the inplace-migration avoiding landscape changes

(SID, host name, …) so you need an update of your SAP system

- Classical migration is complex and requires several steps to be considered

Solution

(13)

HA250 Lesson: Listing DMO benefits

Benefits

- Migration steps are simplified

- System update, Unicode Conversion and database migration are combined in one tool

- Business Downtime is reduced

- Well known tool SUM is used, with improved UI

Migrating your existing SAP system to the SAP HANA database means switching the SAP system to a new database that is running on a new host, since SAP HANA is an appliance.

Note: Although the following example explains the principle for an SAP

Business Warehouse (SAP BW) system, the same applies as well for an SAP Business Suite system.

The following figure illustrates the scenario in which the SAP system is switched from the source database (traditional database) to the SAP HANA database.

Figure 1: Goal of a database migration

Running an SAP system on SAP HANA database requires a specific SAP software level. For a SAP BW system, the minimum level is SAP BW 7.3.

This means that the SAP system has to be updated before the migration takes place.

Note: Update can be an update in terms of EHP implementation or a upgrade

(14)

Figure 2: SAP system update required before migration

If the SAP system is updated, this may result in requirements for the database host software, especially the database software release. So for some scenarios, the source database software has to be updated before the update of the SAP system takes place.

Figure 3: DB software update required before SAP system update

As with the SAP HANA database, non-Unicode systems are no longer supported. So the migration procedure may have to cover the Unicode conversion as well.

(15)

Figure 4: Optionally, Unicode conversion required

Now with the database migration option (DMO) of the Software Update Manager (SUM), the procedure is simplified. SAP system update and database migration are combined in one tool, in one procedure. If required, the Unicode conversion may be included as well. And for some source database types, it is not required to update the source database software for the migration.

(16)

The figures above illustrate a process where the SAP application server is separate from the database host, which is referred to as a distributed installation. The DMO procedure works independent of the installation type. It can be used for a central installation in which the database runs on the same host as the SAP application server, as illustrated below.

Figure 6: DMO is an inplace procedure

In a similar way as for the SAP BW system above, the following figure illustrates the classical migration procedure for an SAP ERP system.

(17)

The classical migration is the sequence of SAP software update (using Software Update Manager, SUM) and heterogenous system copy (using Software Provisioning Manager, SWPM).

DMO simplifies the migration and is often referred to as the one-step procedure to SAP HANA.

Figure 8: DMO simplifies migration

Another benefit is that the DMO procedure offers a new user interface (UI) compared to standard update scenarios with SUM. The new UI is based on SAPUI5, and will be introduced in a later lesson.

(18)

Figure 9: DMO is using SAPUI5

The DMO benefits are summarized below

Combined procedure needs only one maintenance phase (not two)

Reduces business downtime (TCO), less regression tests necessary

Inplace migration keeps application server and System-ID stable

Low impact on system landscape: only database server is new

Original database is kept, can be reactivated as fallback

Reduces risk, no restore required, more time for testing before cutover

Lower prerequisites for SAP and DB start releases

(19)

Lesson Summary

You should now be able to:

(20)

Lesson:

10

Explaining DMO basics

Lesson Overview

This lesson provides a more technical introduction to DMO.

Lesson Objectives

After completing this lesson, you will be able to: • list information sources for DMO

• explain DMO from a technical perspective .

Business Example

As an administrator, you want to learn more about the technical basics of DMO.

Introduction to technical aspects of DMO

Let us start with some remarks on naming first:

Software Update Manager (SUM)

SUM is the standard tool for update of SAP systems (based on SAP NetWeaver)

Database migration option (DMO)

DMO is an option of SUM for a migration scenario (it is not a tool).

Software Provisioning Manager

Tool for system installation / copy / rename, dual-stack split (fka SAPinst), especially used for the heterogenous system copy (“classical migration”)

SUM4HANA

“Software Update Manager for HANA” (SUM4HANA) was a different tool, updates SAP HANA DB software, now part of “SAP HANA Lifecycle Manager”

(21)

HA250 Lesson: Explaining DMO basics

It is important to know about the relevant information sources about DMO: • SAP Note 1813548 Database Migration Option for SUM

• DMO documentation see service.sap.com/sltoolset

(-> SL Toolset 1.0 / documentation / system maintenance)

For the heterogenous system copy, a certification is required. For DMO, this is different:

• No certification required for consultants using DMO of SUM

• No migration check service required for DMO on productive systems

• Still the migration key has to be entered during the DMO run, as R3load requires the key

• Certification training TADM70 (SAP System: OS and DB Migration) useful DMO is a new option inside the SUM. Currently, it does not cover all possible start releases, so you have to consider the supported start releases for DMO:

SAP Business Suite Systems:

SAP Business Suite 7 (or above)

SAP ECC 5.0 or SAP ERP 6.0 (or above)

SAP BW systems:

SAP BW 7.0 (or above)

Hint: SP17 (or higher) required for SAP_BASIS 7.0

SP17 is required for all systems based on Software Component Version SAP_BASIS 7.0. Reason is that for lower levels, report SMIGR_CREATE contains syntax errors.

The required start release levels are described in the respective SAP Notes on DMO (listed above).

Open the attachments to SAP Note 1813548 and explain the possible start releases. SAP BW 7.3 runs on SAP HANA as well, but is not supported as target release for DMO.

(22)

The “EHP 6 version for SAP HANA” of SAP ERP 6.0 can be used as well, but it not positioned here, as SAP recommends to target EHP7 instead.

The “EHP 2 version for SAP HANA” (for ’SAP CRM/SCM/SRM) can be used as well, but it not positioned here, as SAP recommends to target EHP3 instead. Typically, an update of the database software is required before updating the SAP software. For DMO, this is not required for some cases. The following figure illustrates one case.

Figure 10: MaxDB update not required for DMO

Check the SAP Note for DMO for the complete information which database types require an update for DMO and which do not.

(23)

Some scenarios are not possible with DMO:

• DMO supports a migration to SAP HANA DB (& SAP ASE) only,

a homogenous migration is not supported (e.g. SAP HANA -> SAP HANA) • DMO can be started only for a maintenance:

you need to apply at least one SP, e.g. for ST-PI

• SAP HANA requires a single stack, so DMO works only for AS ABAP based

systems;

a dual-stack split option will not be included in DMO

• DMO keeps the application server & SID - no switch possible

The dual-stack split is relevant for systems combined in a dual-stack, like SAP ERP with SAP NetWeaver Portal. DMO cannot be used for SAP Solution Manager for SAP NetWeaver PI (classical installation as dual-stack).

The following figure illustrates a brief overview of the DMO phases that are executed by the SUM tool.

Figure 11: Introduction of DMO phases

Step 1 includes some preparations are done, like providing stack.xml, passwords, download folder. On the SAP HANA database, the DMO procedure only creates required users and schema.

(24)

Step 2 includes the creation of the shadow repository on the source database. This is still uptime processing, so the system is available for end users. The shadow repository is then copied to the SAP HANA database.

Step 3 is the switch to the downtime. The system is not available any longer. Still the source database is running, but not used any longer to store new or changed data. Step 4 is the migration of application data.

Step 5 finalizes the upgrade and migration, like switching the SAP system to the new kernel.

Step 6 finally starts the SAP system which is now running on the new database and on the new SAP software release.

During the complete procedure, the source database continues to run. The DMO procedure offers an easy reset in case this may be required. As the source database was not changed, the reset is fast and without the need of manual interactions. The DMO reset will delete the shadow repository from the source database, and all other artefacts are reset as well.

(25)

15

Exercise 1: Check source system status

Exercise Duration: 10 Minutes

Exercise Objectives

After completing this exercise, you will be able to: • check the system prior to a DMO procedure

Business Example

You have to check the status of the ABAP source system prior to a DMO procedure

System Data

System: ABAP source system

Client:

User ID: admin

Password:

Set up instructions: Data

Data Type Data Value

Task: Check ABAP source system for status and release

Check the status, number of instances, and the release of the ABAP source system. 1. Log on to the operating system (OS) of your source system host.

2. Use the SAP Microsoft Management Console (SAP MMC) to check the system status, the number of instances, and the number of work processes.

3. Log on to the ABAP source system and check the component and software component versions.

4. Check the level of SPAM/SAINT 5. Check the DBACockpit in ABAP.

(26)

Solution 1: Check source system status

Task: Check ABAP source system for status and release

Check the status, number of instances, and the release of the ABAP source system. 1. Log on to the operating system (OS) of your source system host.

a) Connect to the Common Training WTS.

b) From within Common Training WTS, open a remote desktop connection to connect to your system landscape HB-HA250SPSx-###.

c) Log on with train-##.

d) From within HB-HA250SPSx-###, open a remote desktop connection to the host of the ABAP source system.

e) Logon with user <SID>adm. (Password is provided separately by your instructor.)

2. Use the SAP Microsoft Management Console (SAP MMC) to check the system status, the number of instances, and the number of work processes.

a) Open the SAP Microsoft Management Console on the ABAP source system host, e.g. by using the shortcut on the desktop.

b) Check that the system is running.

If the system is listed with a green icon, the system is running.

If the system is not running: start the system using the context menu on the icon with the systemID, and choose All Tasks –> Start ... You will have to provide the password of the <SID>adm user.

c) Check the number of instances listed. In the left hand area, below Console

Rool –> SAP Systems –-> <sid>, there is only one instance listed: <hostname> 0.

Note: <hostname> has to be replaced by the host name of your

ABAP source system.

d) Check the number of work processes of type Dialog (DIA) and Batch (BTC), e.g. by using the menu entry “AS ABAP WP Table”. There are 10 DIA and 10 BTC work processes.

(27)

3. Log on to the ABAP source system and check the component and software component versions.

a) Start the SAP Logon from the start menu of the server HB-HA250SPSx-###. b) Use the existing Logon entry to log on to client 800 with user admin. c) Use menu System/Status to open the system information popup. d) Check that the component version is listed as SAP ECC 6.0 e) Check that the database system is listed as Sybase 15.7.

f) Use the button below the Component version to display the Software Component Version list.

g) Check that SAP_BASIS is listed as 740.

h) Check that SAP_APPL is listed as 6.17, which is equivalent to the product version Enhancement Package 7 for SAP ERP 6.0.

i) You may check the number of instances listed in transaction SM51: there is only one instance listed, like in the SAP MMC.

4. Check the level of SPAM/SAINT a) Start transaction SPAM.

b) SPAM/SAINT will be started, and you will get the information that only display functions are available (as you have started SPAM in a client different to 000).

c) The title lists SPAM/SAINT version 7.40/0053.

d) You may optionally check in SAP Service Marketplace for the latest patch version for SPAM/SAINT.

5. Check the DBACockpit in ABAP. a) Start transaction DBACOCKPIT.

b) If a browser logon is shown, use the first button Switch to SAPGUI above the browser control to switch to the SAPGUI display.

c) The system is listed on the right hand side with DB System as Sybase ASE, and Release 7.40.

(28)

(29)

19

Exercise 2: Check status of SAP HANA

database

Exercise Objectives

After completing this exercise, you will be able to: • use the SAP HANA studio

Business Example

As an administrator, you are responsible for a DMO procedure and have to monitor the SAP HANA database

System Data

System: H00 on wdflbmt7215

Client:

User ID: SYSTEM

Password:

Set up instructions:

1.

-Task: Check the status of the SAP HANA database H00

Start the SAP HANA studio, and configure the access to the SAP HANA database. 1. Start the SAP HANA studio on your server HB-HA250SPSx-###.

2. Configure general settings for the SAP HANA studio, like Active

provider=Directfor Network Connections, and Internet Explorer as

External Browser.

3. Add an entry for the SAP HANA database H00 in the Administration Console in a new folder H00 SYSTEM.

4. Check the version of SAP HANA database H00. 5. Check H00 for user DBACOCKPIT and SAP<sid>. 6. Check the status of the SAP HANA database H00.

(30)

Solution 2: Check status of SAP HANA

database

Task: Check the status of the SAP HANA database H00

Start the SAP HANA studio, and configure the access to the SAP HANA database. 1. Start the SAP HANA studio on your server HB-HA250SPSx-###.

a) Start the SAP HANA studio on your server HB-HA250SPSx-### using

Start –> All Programs –> SAP HANA –> SAP HANA studio.

b) Confirm the proposed Workspace.

c) The Overview page is shown, and the popup Secure Storage is displayed. d) Read the text of the popup, and choose No to close it.

2. Configure general settings for the SAP HANA studio, like Active

provider=Directfor Network Connections, and Internet Explorer as

External Browser.

a) On the Overview page, choose menu Window –> Preferences. b) The Preferences popup is displayed.

c) Open the first section General. d) Select the entry Network Connections.

e) In the drop down menu for Active Provider, switch from Native to

Direct.

f) Choose Apply to apply the change.

g) In section General, select the entry Web Browser.

h) Switch the first option (radio button) from Use internal web

browserto Use external web browser.

i) In the list of External web browser, select the checkbox for Internet

Explorer.

j) Choose Apply to apply the change, and OK to close the popup..

(31)

3. Add an entry for the SAP HANA database H00 in the Administration Console in a new folder H00 SYSTEM.

a) Switch to the Administration Console, either by choosing the first link on the Overview page, or by using menu Window –> Open Perspective –>

SAP HANA Administration Console.

b) Use the menu File –> New –> Folder to open the New Folder popup. c) In the field Folder Name: below, enter H00 SYSTEM. Choose Finish to

close the popup.

d) On the folder H00 SYSTEM, use the context menu Add System ... (right mouse click) to open the System popup.

e) Specify Host Name as wdflbmt7215, Instance Number 00, Description H00 as target for DMO. Choose Next.

f) Keep the option Authentication by database user. Enter User Name as

SYSTEMand the password.

g) Choose Finish to create the system entry.

h) The system is listed, with a folder structure below. 4. Check the version of SAP HANA database H00.

a) In your folder H00 SYSTEM, use the context menu on your system entry H00, and choose Properties.

b) The Properties popup is shown.

c) In the menu left hand, select Version History.

d) The Version History lists the version, like 1.00.090.00.xxx, and optionally earlier versions.

(32)

5. Check H00 for user DBACOCKPIT and SAP<sid>.

a) In the folder hierarchy below system H00, open Security –> Users. The users are listed.

b) The user DBACOCKPIT is not (yet) existing. It will be created during the DMO procedure.

Note: In case that two DMO procedures migrate onto the same

SAP HANA database (for test purposes), only one of the two DMO procedures will have to create the user.

c) The user SAP<sid> is not yet existing either.

Note: In case that two DMO procedures migrate onto the same

SAP HANA database (for test purposes), they cannot use the same user SAP<sid>, which is used for the schema as well.

6. Check the status of the SAP HANA database H00.

a) In your folder H00 SYSTEM, use the context menu on your system entry H00, and choose Administration.

Note: A double click on the H00 system entry will do the same.

b) The System Overview page is shown.

(33)

Lesson Summary

• list information sources for DMO

(34)

Unit Summary

• list the benefits of the DMO procedure • list information sources for DMO

(35)

HA250 Test Your Knowledge

25

Test Your Knowledge

1. Which are advantages of the DMO procedure? Choose the correct answer(s).

□ A DMO combines several steps into one procedure

□ B DMO allows a lower target release on SAP HANA database □ C DMO allows an easy reset during the procedure

(36)

26

Answers

1. Which are advantages of the DMO procedure?

Answer: A, C, D

DMO does combine several steps, offers an easy rest, and it is an inplace procedure. But the requirements concerning the target release on SAP HANA are not changed by DMO.

(37)

Unit 2

29

Preparing DMO Procedure

.

Unit Overview

Preparation steps for DMO.

Unit Objectives

After completing this unit, you will be able to:

• list the required steps and files to prepare a DMO procedure • prepare the archives for a DMO procedure

• Update SAP Host Agent

• Configure SAP Host Agent to start SAPup • Check SAPup processes in the process list • use the DMO UI

Unit Contents

Lesson: Ensuring DMO prerequisites are fullfilled on the host ... 28 Exercise 3: Ensure DMO prerequisites are fulfilled ... 35 Lesson: Configuring SAP Host Agent for DMO ... 41 Exercise 4: Configure SAP Host Agent for DMO... 49 Lesson: Examining the DMO UI ... 54

(38)

Lesson:

30

Ensuring DMO prerequisites are fullfilled on the host

Lesson Overview

This lesson explains the required steps on the host to prepare a DMO procedure.

Lesson Objectives

After completing this lesson, you will be able to:

.

Business Example

You have the task to prepare a DMO procedure and need to know the required steps.

Fullfilling the prerequisites for DMO

Required considerations for DMO include:

• SAP HANA appliance is available (>= 1.00.62)

(SAP_BASIS 7.40 SP08: >=1.00.82) • Dual-stack has to be split beforehand

• OS/DB software update may be required

• Stack.xml file has to be created (& software files downloaded: MOpz)

• Web Browser update may have to be applied

• SAP BW: consider house keeping, NLS, and BW-PCA

(see SCN blog http://scn.sap.com/docs/DOC-46824)

Hint: See SAP Note 1829728 on BW Housekeeping Task List. DMO specifics

(39)

HA250 Lesson: Ensuring DMO prerequisites are fullfilled on the host

For a DMO procedure, you will have to select both the kernel files for the source database and the target database, as the DMO procedure will require and use both of them, as explained in a separate section.

Figure 12: MOpz: selecting kernel files for DMO

Hint: Consider SAP Note 1795851 about the report in SAP Solution Manager

to copy an existing stack.xml (from the previous system maintenance). • SAP Note 1912445: ABAP custom code migration for SAP HANA

• SAP Note 1872170: Suite on HANA memory sizing report

• SAP Note 1736976: Sizing report for BW on HANA Dual-stack split

(40)

Only pure ABAP systems can be migrated onto the SAP HANA database. In case the system is a dual-stack system (both ABAP and Java stacks on one database, one System-ID), the dual-stack has to be split beforehand.

Note: The dual-stack split procedure is now part of the Software Provisioning

Manager. There are no plans to include the dual-stack split procedure into the DMO procedure

Note: With SAP NetWeaver 7.40 SP03 (and above), it is possible to operate

an SAP system based on AS Java (e.g. BI-Java) on an SAP HANA database.

Unicode Conversion

With SUM SP10, the DMO procedure allows to include the Unicode Conversion (for single-code-page systems).

OS/DB software update

Depending on the update path, the operating system and/or the database software may have to be updated prior to the DMO procedure. For specific source databases, the DMO procedure has lower requirements than the “classical migration”. The DMO documentation lists the latest requirements.

stack.xml and software files

This was already discussed in a previous lesson (Maintenance Optimizer in SAP Solution Manager).

Web Browser

The user interface (UI) of the DMO procedure is based on SAPUI5 and requires a specific internet browser version. The DMO documentation lists the latest requirements. See list below for an overview:

• Internet Explorer 9 or higher (not using compatibility view)

• Chrome 28 or higher

• Firefox 21 or higher

(41)

Required software download from SAP Service Marketplace for DMO includes: • SPAM/SAINT update for SAP source release has to be downloaded

• Software Update Manager (SUM) latest version has to be downloaded

• SAP Host Agent latest patch has to be downloaded

• SAP HANA Client installation files have to be downloaded

• Migration key has to be requested

• SAP license file for target system has to be requested SPAM/SAINT update for source release

The latest update for the source release is not included by the MOpz, so the file has to be downloaded separately. The SUM requires specific functionality in the ABAP stack to prepare the source system and to create the shadow system. This functionality is not shipped with the SUM, it is part of the SPAM/SAINT.

Task: move the SPAM update archive into the download folder. SUM latest update

Although for some scenarios the MOpz will add the SUM into the download basket, it is recommended to always check for the latest update of the SUM in SAP Service Marketplace. This includes the latest patch level for a SUM SP version as well. Use the quick link /sltooset in SAP Service Marketplace to navigate to the SUM patches.

Task: extract the SUM archive into the system folder. SAP Host Agent latest patch

Although the MOpz will add the SAP Host Agent into the download basket, it is recommended to always check for the latest update of the SAP Host Agent in SAP Service Marketplace. Use the quick link /patch in SAP Service Marketplace to navigate to the SAP Host Agent patches.

Hint: Path to SAP Host Agent patches: http://service.sap.com/patch –>

Browse download catalog --> SAP Technology Components --> SAP HOST AGENT --> SAP HOST AGENT 7.20 --> <choose your OS>

Task: execute a self update.

SAP HANA Client installation files

The SUM will establish a connection to the SAP HANA database and requires the SAP HANA client for this. The installation files have to be provided, and the SUM will ask for the location of these files during the DMO procedure.

(42)

Task: extract the SAP HANA Client installation archive. Migration Key

For a heterogenous database migration, a migration key is required. The kernel tool R3load is used for the migration and requires this migration key. The DMO procedure will ask for the key and provide it to the R3load tool. Use the link support.sap.com/migrationkey in SAP Support Portal to request the migration key for your SAP system.

Task: provide the migration key when the DMO procedure asks for it. SAP license file

The SUM will have to install a new license on the target system. The DMO procedure will ask for the license file. Use the quick link /licensekey in SAP Service Marketplace to request the license file for your SAP system.

Task: provide the license file location when the DMO procedure asks for it.

The task list is summarized below:

• Move the stack.xml file into the download folder

• Move the SPAM update archive into the download folder • Extract the SUM archive into the system folder

• Execute a self update for SAP Host Agent

• Extract the SAP HANA Client installation archive • Keep migration key ready (DMO procedure asks for it) • Keep SAP license file ready (DMO procedure asks for it)

The following figure shows the folder D:\HA250 that has been prepared on the host in the training landscape.

(43)

Figure 13: Prepared files for exercise

The last figure illustrates the target state of the exercise.

(44)

(45)

37

Exercise 3: Ensure DMO prerequisites are

fulfilled

Exercise Objectives

After completing this exercise, you will be able to: • list the required files for a DMO activity • prepare the files and archives

Business Example

A colleague has already prepared the DMO procedure by downloading required files like the SPAM update for the source release, a license file, among other files. You have to check the location of the files.

Note: Some of these actions are optional, but serve to understand the special

requirements for DMO, especially the additional files required, and additional steps compared to a standard update/upgrade using the SUM.

Note: You will have to replace <sid> with the system-id of the ABAP source

system assigned to you, e.g. T60 or T64.

System Data

Client:

User ID: admin

Password:

Set up instructions:

Task 1: Check files and folders

Check the host of the ABAP source system for required files and folders. 1. Check the content (files and folders) provided in the folder D:\HA250.

2. Examine the system folder D:\usr\sap\<sid>\. Check if a folder SUM is already existing.

(46)

Task 2: Prepare files and folders

Prepare the required files and folders on the host of the ABAP source system. 1. Extract the Software Update Manager archive into the system folder using

SAPCAR.

2. Move the file stack.xml into the download folder. 3. Move the download folder into the system folder. 4. Extract the SAP HANA Client installation archive.

(47)

Solution 3: Ensure DMO prerequisites are

fulfilled

Task 1: Check files and folders

Check the host of the ABAP source system for required files and folders. 1. Check the content (files and folders) provided in the folder D:\HA250.

a) Switch to the Remote Desktop Connection to your ABAP source system host.

b) Open a Windows Explorer window, and navigate to the folder D:\HA250\. c) Check the content of the folder for the following files / folder:

Note: On your host, some of the files may have a slightly different

name suffix.

• download: folder containing the software and kernel files, which were

downloaded from download basket (in SAP Service Marketplace), provided by Maintenance Optimizer (“MOpz”, in SAP Solution Manager)

• IMDB_CLIENT100_90_0-10009664.SAR: installation files for the

SAP HANA client, which had to be downloaded separately from SAP Service Marketplace

• SAPHOSTAGENT20x_20x-20005735.SAR: SAP Host Agent

archive with latest patch

Note: Only if a newer patch for SAP Host Agent (compared

to the one in the download folder) was made available, this file is existing here.

• stack.xml: the definition file for the SUM, downloaded from directly

from Maintenance Optimizer (in SAP Solution Manager)

• SUM.SAR: Software Update Manager (SUM) archive, downloaded

either from SAP Service Marketplace (/sltoolset), or provided by MOpz in download basket

Note: Only if a newer patch for SUM (compared to the

one in the download folder) was made available, this file is existing here.

(48)

• <sid>_multiple.txt: License file for the target system, created

separately

2. Examine the system folder D:\usr\sap\<sid>\. Check if a folder SUM is already existing.

a) Open a second Windows Explorer window. b) Navigate to the folder D:\usr\sap\<sid>\.

Note: This folder is referenced as the system folder in this training

material.

c) The system folder does not (yet) contain a SUM folder. d) Keep this folder open, as we will work in it later.

Task 2: Prepare files and folders

Prepare the required files and folders on the host of the ABAP source system. 1. Extract the Software Update Manager archive into the system folder using

SAPCAR.

a) Open a command prompt on the host of the ABAP source system, e.g. from the shortcut on the desktop.

b) Execute sapcar.exe using the option “-R” to specify the target directory. The exact statement depends on the location and name of your SUM archive, see step above.

the following command to execute the archive SUM.SAR into the system folder D:\usr\sap\<sid>\ :

SAPCAR.EXE -R D:\usr\sap\<sid>\ -xvf D:\HA250\SUM.SAR

Note: Keep the command prompt open as we will use it for further

commands later.

c) Check if the folder SUM was created in the system folder. Use the existing Windows Explorer window for this.

d) Optional: you may open the SUM folder to see the folders abap and java, among other folders.

(49)

2. Move the file stack.xml into the download folder.

a) Switch to he Windows Explorer window showing the content of D:\HA250\. b) Move the stack.xml file into the download folder.

Note: For a DMO procedure like for a standard maintenance with

SUM, it is required that the stack.xml is located in the download folder, as the SUM only asks for the stack.xml file and presumes that it is located in the download folder.

3. Move the download folder into the system folder. a) Move D:\HA250\download\ to D:\usr\sap\<sid>\.

Note: The download folder may have a different name. But it is

common (and useful, as we will see soon) to name it download and place it into the system folder.

4. Extract the SAP HANA Client installation archive. a) Switch to the command prompt window.

b) Extract the SAP HANA Client installation archive

IMDB_CLIENT100_90_0-10009664.SAR using the following

command:

SAPCAR.EXE -xvf D:\HA250\IMDB_CLIENT100_90_0-10009664.SAR

Note: You may have to adapt the name of the archive to the actual

(50)

Lesson Summary

(51)

HA250 Lesson: Configuring SAP Host Agent for DMO

Lesson:

42

Configuring SAP Host Agent for DMO

Lesson Overview

This lesson explains the preparation necessary steps to configure the SAP Host Agent for a DMO run.

Lesson Objectives

After completing this lesson, you will be able to: • Update SAP Host Agent

• Configure SAP Host Agent to start SAPup • Check SAPup processes in the process list

The role of SAP Host Agent and the required preparation steps shall be motivated.

Business Example

You are responsible for preparing a DMO run, so you have to prepare the communication between the SAP Host Agent and the SUM.

Collaboration between SAP Host Agent and SUM

The Software Update Manager (SUM) is the tool for system maintenance of SAP systems based on SAP NetWeaver. For the DMO procedure, a new way of starting the tool and a new user interface (UI) was introduced. The following figure illustrates the different approach of the “classical” way of starting and using SUM compared to the DMO way of starting and using SUM.

(52)

Figure 15: Architecture overview for DMO

The same tool SUM can be used for a system maintenance, or for a DMO procedure. Only the DMO procedure uses the new UI which is based on SAPUI5.

Note: Currently, the new UI is only available for the DMO procedure. It

is planned to extend the new UI to standard maintenance scenarios as well in the future.

Note: SAPUI5 is based on jQuery, a javascript library

You use a browser window to start the SUM for a DMO procedure by sending an appropriate HTTP request to the SAP Host Agent. The URL that you use contains the information for the SAP Host Agent what to do. http://<host>:<hostagentport>/lmls/sumabap/<SID>doc/gui

Note: “lmsl” is the abbreviation for Lifecycle Management Software Logistics.

<host> is the hostname of the primary application server of the source system <port> is the port of the SAP Host Agent (1129, or 1128 for plain HTTP) <SID> has to be replaced with the System-ID of the source system Before the SAP Host Agent starts the SUM, it requests user and password of <SID>adm user. This is required to start the SUM.

(53)

Figure 16: Starting SUM via SAP Host Agent

Note that if you enter a wrong password or a wrong URL, you will get an error message which depends on the browser type. Some browser output “File cannot be found”. With user and password of <SID>adm user, the SAP Host Agent starts the SAPup. The SAPup is the part of the SUM that is responsible for the ABAP stack. As DMO is only working on ABAP systems, the SAPup is used for the DMO procedure (and some SUM scripts, as described below).

The SAPup process is started with option gt=httpchannel, it acts as a kind of dispatcher, as it handles all request coming from the SAP Host Agent. This SAPup process will start a second SAPup which triggers additional tools like R3load or tp.

(54)

Both SAPup processes are visible in the process list of the PAS host.

Figure 18: SAPup processes visible on OS level

In the unlikely situation that you want to end the SAPup process the hard way, you will have to end the process tree for the SAPup with mode httpchannel.

The HTTP communication between SUM and SAP Host Agent requires a minimum patch level for SAP Host Agent. That is the reason why it is important to know how to update the SAP Host Agent. In addition, the SAP Host Agent has to be configured so that for starting the SUM, it knows the location of SUM.

Required preparation steps for SAP Host Agent

The required steps to configure the SAP Host Agent for a DMO run are listed below: • Checking the patch level of SAP Host Agent

• Upgrading SAP Host Agent (if required) • Configuring SAP Host Agent for starting SUM

Checking and upgrading SAP Host Agent

For a Windows host, the SAP Host Agent is installed in C:\Program

Files\SAP\hostctrl\exe. The option “-version” allows to check the version:

(55)

The SAP Host Agent archive is typically part of the download folder. Still it makes sense to check for a newer patch in SAP Service Marketplace.

You do not have to unpack the archive of the new SAP Host Agent, as the upgrade option can use an archive as well.

To upgrade the existing saphostexec.exe, use the option “-upgrade” and reference the archive with the new SAP Host Agent with option “-archive”, as illustrated in the figure below:

saphostexec.exe -upgrade

-archive D:\usr\sap\<SID>\SAPHOSTAGENT.SAR.

Figure 19: Updating SAP Host Agent using selfupdate

Hint: The existing SAP host Agent needs patch level 134 (or higher) to

support the direct upgrade from an archive. For lower patch levels, you will have to unpack the archive first.

The operation should return in a success statement like

[OK] SAPHostExec / SAPHostControl successfully upgraded. You may check the version of the SAP Host Agent afterwards again to proof the upgrade worked.

(56)

Configuring SAP Host Agent for starting SUM

The SAP Host Agent needs to know the location of SUM to be able to start the SUM (triggered by an appropriate HTTP request from the browser). This information is stored in a configuration file called sumabap.conf. You do not have to create or edit this file on your own, as the SUM has an option to create the file for you:

SUMSTART confighostagent.

The interconnection is illustrated in the figure below.

Figure 20: Creating SAP Host Agent configuration file for starting SUM

Note: The option confighostagent does not start the SUM or SAPup

permanently, only for the short time it takes to create the file. The operation should return a success message like

Registering SUM in SAP Host Agent finished.

The configuration file is created in a new sub directory operations.d. You may check the configuration file using Notepad, but do not change the content of the file.

Hint: The configuration file sumstart.conf was used for the previous

(57)

Figure 21: Examining SAP Host Agent configuration file

Note: Do not replace the placeholder terms in square brackets, as they are

interpreted by SAP Host Agent.

You have to be able to check whether the file exists. If it does not exist, the SAP Host Agent will return an error message when you try to start the DMO process from within a browser window.

(58)

(59)

49

Exercise 4: Configure SAP Host Agent for

DMO

Exercise Objectives

After completing this exercise, you will be able to: • check the version of the SAP Host Agent • update the SAP Host Agent

• create the configuration file for the SAP Host Agent for starting the SUM

Business Example

As an administrator, you are responsible for preparing a DMO procedure. You have to ensure that the SAP Host Agent fulfills the requirements.

Note: You will have to replace <SID> with the actual System-ID of your

ABAP source system, e.g. T60.

System Data

System: ABAP source system host

Client:

-User ID: <SID>adm

Password:

Set up instructions: Data

Data Type Data Value

Task: Check and update the SAP Host Agent

Check the version of the SAP Host Agent and update it to a newer patch level. 1. Check the version of the actual SAP Host Agent.

2. Use the selfupdate function of the SAP Host Agent.

(60)

Solution 4: Configure SAP Host Agent for

DMO

Task: Check and update the SAP Host Agent

Check the version of the SAP Host Agent and update it to a newer patch level. 1. Check the version of the actual SAP Host Agent.

a) Switch to the Remote Desktop Connection to your ABAP source system host.

b) Switch to the command prompt window on the host of your ABAP source system.

c) Change to the directory of the actual SAP Host Agent. D:\>C:

cd C:\Program Files\SAP\hostctrl\exe

d) Use option “-version” of saphostexec.exe to check the version: saphostexec.exe -version

The console shows patch number 187, which is sufficient for the DMO procedure, but not sufficient for the new URL /sumabap/.

(61)

2. Use the selfupdate function of the SAP Host Agent.

a) Use the option “-upgrade” to do a selfupgrade, referencing the archive with option “-archive”:

C:\Program Files\SAP\hostctrl\exe>saphostexec.exe -upgrade -archive

D:\usr\sap\<SID>\download\SAPHOSTAGENT20x_20x-20005735.SAR Replace <SID> with the system-ID of your ABAP source system, and

specify the full name of the SAP Host Agent.

Note: You may have to adapt the location of the archive if there is

a newer SAP Host Agent archive in folder D:\HA250. b) You should get a success message like

[OK] SAPHostExec / SAPHostControl successfully upgraded You may have to press enter to end saphostexec.exe.

c) Check if the upgrade worked: saphostexec.exe -version It should write a patch level 20x.

(62)

3. Create the configuration file for the SAP Host Agent for starting the SUM. a) Check if the actual directory of the SAP Host Agent contains a folder

operations.d (check in the Windows Explorer, or use the command dir in

the command prompt).

The folder operations.d does not yet exist.

b) In the command prompt, navigate to the SUM\abap folder: D:

cd D:\usr\sap\<SID>\SUM\abap

c) Use the option “confighostagent” of the SUM to create the configuration file for the SAP Host Agent:

D:\usr\sap\<SID>\SUM\abap>SUMSTART confighostagent

Note: There is no minus sign required in front of the option

“confighostagent”

d) You should get a success message like

Registering SUM in SAP Host Agent finished.

Note: Note that with SUM 1.0 SP12 and higher, the SUMSTART

script restarts the SAP Host Agent so that the new configuration file is taken into consideration.

e) Verify that the actual directory of the SAP Host Agent now contains a folder operations.d with a file sumabap.conf.

f) Optional: you may open the file sumabap.conf in Notepad.exe to check the content. It contains the command

D:\usr\sap\$[SID:#required]\SUM\abap\SUMSTART.BAT where the part $[SID:#required] will be replaced by the SAP Host Agent to start SUMSTART.BAT when requested.

(63)

Lesson Summary

You should now be able to: • Update SAP Host Agent

• Configure SAP Host Agent to start SAPup • Check SAPup processes in the process list

(64)

Lesson:

54

Examining the DMO UI

Lesson Overview

This lesson introduces the DMO UI.

Lesson Objectives

After completing this lesson, you will be able to: • use the DMO UI

.

Business Example

As an administrator, you have to configure the DMO procedure and need to know about the new UI and its features.

DMO UI

• SAPUI5 is an SAP library used in apps and offered for own development • The standard SUM functionality cannot be used with SAPUI5 (not yet) • SAPUI5 is based on a javascript library (including jQuery)

(65)

HA250 Lesson: Examining the DMO UI

Figure 22: Roadmap Steps

(66)

Figure 24: Notifications

(67)

Figure 26: Utilities: Log Files

Figure 27: Utilities: Breakpoints

The Top Level Menu consists of three objects: the role admin, the Help menu, and the Logoff button.

(68)

Figure 28: Top Level Menu

The role admin is the only role that currently exists, so you cannot switch the roles. There is no role model like for a standard maintenance in SUM with

administratorand observer.

The Help menu contains links to the DMO guide and to the SAP Note on DMO. The last option Get Support File is discussed below.

If you choose the Logoff button, you will be notified that you have to close the browser to log off. Some browsers do close the window, others do not.

(69)

Facilitated Discussion

SAPUI5 advantages

Discussion Questions

Use the following questions to engage the participants in the discussion. Feel free to use your own additional questions.

(70)

Lesson Summary

You should now be able to: • use the DMO UI

(71)

HA250 Unit Summary

Unit Summary

• Update SAP Host Agent

• Configure SAP Host Agent to start SAPup • Check SAPup processes in the process list • use the DMO UI

(72)

(73)

HA250 Test Your Knowledge

61

Test Your Knowledge

1. The configuration of SAP Host Agent to start SAPup is optional as the SAPup can be started without SAP Host Agent.

Determine whether this statement is true or false. □ True

(74)

62

Answers

1. The configuration of SAP Host Agent to start SAPup is optional as the SAPup can be started without SAP Host Agent.

Answer: False

The configuration of SAP Host Agent to start SAPup is not optional as the SAP Host Agent serves as entry point for the HTTP requests from the browser. So a configuration file is required, e.g. to start SAPup.

(75)

Unit 3

65

Configuration of DMO Procedure

.

Unit Overview

Executing DMO.

Unit Objectives

After completing this unit, you will be able to: • Start the DMO run

• Configure DMO phase “Configuration” • handle DMO error messages

• list the general steps of the DMO procedure

• explain why additional kernel files are required for the DMO procedure • List the DMO steps relevant for table migration

• Tune the DMO procedure downtime • reset the DMO procedure

• list the DMO steps after lock of development environment • explain the DMO release schedule

Unit Contents

Lesson: Starting the DMO run ... 67 Exercise 5: Start the DMO procedure ... 75 Lesson: Continuing DMO configuration... 87

(76)

Lesson: Configuring DMO step Preprocessing ... 104 Exercise 7: Configure roadmap Preprocessing ... 109 Lesson: Listing DMO procedure steps ... 112 Lesson: Analyzing logs and tuning the DMO downtime ... 123 Exercise 8: Analyze DMO migration logs ... 137 Lesson: Resetting the DMO procedure ... 140 Exercise 9: Reset the DMO procedure ... 145 Exercise 10: Prepare and run DMO procedure again ... 151 Lesson: DMO steps after lock of development environment... 156 Lesson: DMO release schedule ... 164

(77)

HA250 Lesson: Starting the DMO run

Lesson:

67

Starting the DMO run

Lesson Overview

Explains the start of DMO

Lesson Objectives

After completing this lesson, you will be able to: • Start the DMO run

.

Business Example

As an administrator, you are responsible for starting and executing the DMO procedure.

Start the DMO run

You start the DMO procedure with an HTTP request from a browser.

Hint: The following screenshot illustrates that the browser is opened on the

(78)

Figure 30: Starting SUM from a browser window

You have to supply the <SID>adm user and password, because the SAP Host Agent needs these to start the SAPup.

The first DMO dialog is the specification of the stack.xml file.

(79)

Figure 32: DMO dialog: Required System Passwords

(80)

If you want to provide a SPAM update after the DMO procedure was started, you will have to extract the archive manually, and place the update into the EPS\in directory.

Figure 34: DMO dialog: Database Migration Option

Caution: Do not forget to set the first option to SAP HANA, otherwise only

the system update will be executed.

Hint: With SUM SP12, target database type SAP ASE is only shown on

request (specific configuration required).

Table comparison as part of DMO

SUM conducts a count* for each table, counting the table rows.

With SUM 1.0 SP11, the option to compare the tables based on checksums was introduced:

Content checks for selected tables of source & target database (using cyclic redundancy checksums)

Generates checksums for e. g. every 10000 rows on source and target side and compare

(81)

Dig deeper where checksums do not match until conflicting rows are found Stop after discovering more than e. g. 200 differences -> points to systematic errors

Decision taken on dialog “Database Migration Option” (can’t be switched off later)

Checking all tables only for test systems due to performance load

Checking happens in parallel for multiple tables / one table via table splits Check only for application tables, repository tables not allowed

Runs during downtime -> configuring downtime processes Checksum discrepancies shown as error

Ignore possible (file MIGRATE_CHECK_CHECKDIFF.LST) and repeat SUM SP10 (and above) offers an automatic setup of Landscape Reorganization for a SAP HANA Scale-out scenario. You will have to check the option in this dialog for the Landscape Reorganization to be executed later.

Figure 35: DMO dialog: Missing SAP Notes for Tools

Use transaction SNOTE to apply the required SAP Notes.

SUM will now display the status of SPDD and SPAU. You should confirm all obsolete notes, and reset all not-adjusted objects with active SAP-version to SAP-standard.

(82)

Figure 36: Open actions in transaction SPDD and SPAU

Figure 37: DMO dialog: Continue roadmap Configuration

Folders for monitoring and troubleshooting

The following folders are relevant for monitoring and troubleshooting (all folders under SUM\abap\):

(83)

log

Log files (same like on DMO UI Utilities/logs), e.g. error logs, SAPupConsole.log, SAPupStats.log

tmp

temporary files, especially SAPupDialog.txt if a dialog is open (not for roadmap switches)

srv

HTTP log files of SAPup (gt=httpchannel)

htdoc

File UPGANA.XML contains information like timing, component level and much more

(84)

(85)

75

Exercise 5: Start the DMO procedure

Exercise Objectives

After completing this exercise, you will be able to: • start the DMO procedure

• configure the first steps of the DMO procedure

Business Example

As an administrator, you are responsible for executing the DMO procedure. You will start the DMO procedure, configure the phases of the first step Extraction, and get familiar with the new UI that the SUM offers exclusively for the DMO procedure.

System Data

Client:

User ID: <SID>adm

Password:

Set up instructions: none

Task 1: Start the DMO procedure

Start the DMO procedure and configure the first dialogs.

1. Open the Chrome browser on your server HB-HA250SPSx-### and start the DMO procedure.

2. Provide the location of the stack.xml file to the DMO procedure.

3. While the “Work in Progress” icon is shown, examine the UI of DMO, and detect the following elements: Tool Tabs; Roadmap steps; Progress

Bar; Work in Progress icon; Menu; Phaselist Toggle. You will examine the areas in detail later.

4. Display the phase list.

5. Examine the estimation of the progress bar.