Database Migration Option (DMO) for SUM 1.0 SP11

Upgrade Guide Software Update Manager Document Version: 1.3 – 2014-07-31

CUSTOMER

Database Migration Option (DMO) for SUM 1.0 SP11

Typographic Conventions

Type Style

Description

Example

Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents.

2

Example

Emphasized words or expressions.

EXAMPLE

Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example

Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example

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



Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE

Keys on the keyboard, for example, F 2 or E N T E R .

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Typographic Conventions

Document History

Caution Before you start the update, make sure you have the latest version of this document. You can find the latest version on SAP Service Marketplace at http://service.sap.com/sltoolset Software Logistics Toolset 1.0 Documentation System Maintenance Updating SAP Systems Using Software Update Manager .

Version

Date

Change

1.0

2014-07-08

First version

1.1

2014-07-15

Changes in the list for SAP Notes for DMO

1.2

2014-07-21

Follow-up activity concerning the Transport Management System added

1.3

2014-07-31

New minimum required patch level for SAP Host Agent No credentials needed anymore to install the SAP HANA database client

.

Database Migration Option (DMO) for SUM 1.0 SP11 Document History

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

3

Table of Contents

1 1.1 1.2 1.3

Introduction..............................................................................................................................................6 About this Document .............................................................................................................................................. 6 Integration/Further Documentation...................................................................................................................... 6 Before You Start ...................................................................................................................................................... 7 1.3.1 Naming Conventions .............................................................................................................................. 7 1.3.2 SAP Notes ................................................................................................................................................ 7 1.3.3 Constraints .............................................................................................................................................. 9

2 2.1 2.2 2.3 2.4

Planning .................................................................................................................................................. 10 DMO Concept......................................................................................................................................................... 10 Dual-Stack Split ...................................................................................................................................................... 11 Unicode.................................................................................................................................................................... 11 ICNV ........................................................................................................................................................................ 12

3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18

Preparation ............................................................................................................................................. 13 Checking SAP Notes for Latest Information ....................................................................................................... 13 Unicode Conversion: Preparatory Steps ............................................................................................................. 13 BW: Checking RFC Destination into BW client.................................................................................................... 13 BW: Deleting InfoObject 0BCTCOMP .................................................................................................................. 14 BW: Applying BW-Related SAP Notes ................................................................................................................. 14 Checking Pool Tables and Cluster Tables ........................................................................................................... 14 Oracle: Suppress Long-Running Phases EU_CLONE_DT_SIZES/EU_CLONE_UT_SIZES ............................. 14 Installing SAP HANA Database ............................................................................................................................ 15 Getting the Migration Key for SAP HANA Database........................................................................................... 15 Getting the Latest HANA Client Software ........................................................................................................... 15 Getting a Permanent SAP License ....................................................................................................................... 15 Getting the Latest SUM ......................................................................................................................................... 16 Unpacking the SUM archive SUM.SAR................................................................................................................ 16 Changing the Schema Name on SAP HANA ....................................................................................................... 16 Using SAP HANA Mass Import Feature ............................................................................................................... 16 Installing Latest SAP Host Agent ......................................................................................................................... 17 Configuring SUM for Use with SAP Host Agent .................................................................................................. 17 Downloading Necessary Files from Maintenance Optimizer............................................................................. 17

4 4.1 4.2

Running the Software Update Manager ............................................................................................... 19 Starting SUM via SAP Host Agent........................................................................................................................ 19 SAPUI5-based User Interface...............................................................................................................................20 4.2.1 Options ...................................................................................................................................................20 4.2.2 Changing processing parameters during runtime ............................................................................. 21 4.2.3 Problems with the User Interface ........................................................................................................ 21 Phases of the Update and Migration Process ..................................................................................................... 21 4.3.1 Extraction............................................................................................................................................... 21 4.3.2 Configuration ......................................................................................................................................... 22 4.3.3 Checks.................................................................................................................................................... 23

4.3

4

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Table of Contents

4.4 4.5 4.6

4.3.4 Preprocessing ....................................................................................................................................... 23 4.3.5 Execution............................................................................................................................................... 24 4.3.6 Postprocessing ..................................................................................................................................... 24 Landscape reorganization for the SAP HANA scale out ................................................................................... 25 Table Comparison with SUM ............................................................................................................................... 25 Reset Procedure ................................................................................................................................................... 26 4.6.1 Reset from a SUM dialog ..................................................................................................................... 26 4.6.2 Manual Reset on OS-Level....................................................................................................................27

5 5.1 5.2

Follow-Up-Activities ...............................................................................................................................29 Unicode Conversion: Post-Processing Steps..................................................................................................... 29 Transport Management System: Domain Controller Configuration................................................................ 29

6

Troubleshooting .................................................................................................................................... 30

Database Migration Option (DMO) for SUM 1.0 SP11 Table of Contents

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

5

1

Introduction

1.1

About this Document

This document describes specifics, when you want to update your existing SAP systems based on SAP NetWeaver ABAP using the Software Update Manager (SUM) with subsequent migration of your database to SAP HANA database. To smooth the way to SAP HANA, SAP introduced on a one-step procedure that combines system update and database migration for the migration to SAP HANA. This is provided with the Database Migration Option (DMO) feature, which is delivered with Software Update Manager (SUM) in the Software Logistics Toolset (SL Toolset). The DMO is an option of the SUM for a combined update and migration: Update an existing SAP system to a higher software release, and migrate the database to SAP HANA database. The main benefits of DMO are: Migration steps are simplified System update and database migration are combined in one tool Business downtime is reduced The source database remains consistent, so a fast fallback is possible This guide includes special preparations and follow-up activities as well as information about using SUM with DMO. At the end, you will find some troubleshooting information and further information. The information in this document is intended for SAP system administrators with operating system, database, and SAP NetWeaver Application Server knowledge.

1.2

Integration/Further Documentation

In addition to this document, you also require other information such as the SAP Notes that are specific to the SUM and DMO (see section 1.3.2 SAP Notes), and the following documents: Upgrade Master Guide – SAP NetWeaver The Upgrade Master Guide guides you through the complete update process and refers you to the required documentation for each step. You can get the latest version of this document on the SAP Service Marketplace o for SAP Enhancement Package 1 for NetWeaver 7.3 at http://service.sap.com/upgradenw73 o for SAP NetWeaver 7.4 and higher at http://service.sap.com/upgradenw74 Update Guide – Update of SAP Systems Using Software Update Manager

Note In this document, we use the abbreviation SUM Guide.

6

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Introduction

This document describes how to update SAP systems based on SAP NetWeaver using the Software Update Manager (SUM). It includes general planning, preparation and follow-up activities, information about using the Software Update Manager, and troubleshooting information. You can get the latest version of this document on the SAP Service Marketplace at: http://service.sap.com/sltoolset Software Logistics Toolset 1.0 Documentation Updating SAP Systems Using Software Update Manager

System Maintenance

Upgrade and Update Guide: SAP NetWeaver ABAP This document describes the application-specific preparations and follow-up activities, which you have to perform when you update your SAP system to SAP NetWeaver 7.4 ABAP. It supplements the SUM Guide and refers to various SAP NetWeaver applications such as SAP NetWeaver Business Warehouse. You can get the latest version of this document on the SAP Service Marketplace o for SAP Enhancement Package 1 for NetWeaver 7.3 at http://service.sap.com/upgradenw73 o for SAP NetWeaver 7.4 and higher at http://service.sap.com/upgradenw74

1.3

Before You Start

1.3.1

Naming Conventions Note See the SUM Guide for a comprehensive overview about naming conventions.

SUM Guide Abbreviation for Update Guide – Update of SAP Systems Using Software Update Manager Update For clarity and readability, the generic term “update” is used in this document in the context of release upgrade, enhancement package installation and Support Package Stack application with SUM. SAPup The DMO procedure is only available for systems based on AS ABAP, so on technical level, the executable SAPup (as part of SUM) is used, for example, in the log files or in commands. anyDB DMO migrates from an existing relational database type (called “anyDB”) to SAP HANA This spelling is used when referring to “/SUM”.

1.3.2

SAP Notes

To prepare and perform the update of your SAP system and the migration of your database to SAP HANA database, you require some additional information that is not included in this document. This information is in a

Database Migration Option (DMO) for SUM 1.0 SP11 Introduction

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

7

range of SAP Notes in SAP Support Portal (http://service.sap.com/notes), some of which you have to read before you start with the preparations. Central Software Update Manager Note and the SAP Note for your database: See section SAP Notes in the SUM Guide that is related to the SUM version that you use. SAP Notes for the DMO: SAP Note Number

Description

1813548

Database migration option (DMO) for Software Update Manager

Recommendation See also the PDF documents, which are attached to the DMO Note and the central SUM note, for a graphical representation of the supported update and upgrade paths. SAP Notes regarding SAP NetWeaver Business Warehouse: SAP Note Number

Description

1142427

Trace cannot be deleted regularly

1388287

RSRD_BOOKMARK_REORGANISATION: Specified time not used

1695112

Activities in BW after migrating to the SAP HANA database

1714734

Functions RSPC_SHUTDOWN and RSPC_STARTUP do not exist

1860274

SAP HANA adj. for BW Workspaces: Inactive CompositeProviders (only required for BW Workspaces and target releases below BW 7.31 SP 9)

1958346

BW on SAP HANA: Landscape redistribution check procedures

1908075

BW on SAP HANA SP06: Landscape redistribution

Other SAP Notes that contain additional information In addition to the SAP Notes that you need to prepare the update, this document also refers you to other SAP Notes that contain additional information. The following lists contain these SAP Notes

8

SAP Note Number

Description

816861

Migrating entries in the secure storage

928729

Combined Upgrade & Unicode Conversion (CU&UC)

1031096

Installing Package SAPHOSTAGENT

1784377

Checking pool tables and cluster tables

1788379

Transport of SAP NOTES

1845061

Background user has no authorization for scheduling

1929357

HDB client installation on HP-UX

1968508

Release change & Single Code Page Conversion to Unicode with DMO

1899817

SAP Business Suite on distributed SAP HANA database (scaleout): Landscape redistribution

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Introduction

1.3.3

Constraints

Please take into account the following main differences to the standard SUM procedure, that is, the system update without combined migration to SAP HANA database in a one-step procedure. Different prerequisites Supported are: All database versions listed in the Product Availability Matrix (PAM) of the source release, and all operating system versions listed in the PAM of the target release.

Caution See also the latest SAP Notes for DMO mentioned in section 1.3.2 SAP Notes for the current prerequisites and restrictions. This involves information regarding o operating systems and databases o minimum support packages o source and target release Different start procedure SUM starts in a different way: A browser request to the SAP Host Agent is used to start SUM, instead of starting SUM from the prompt or console. Different UI SUM shows a new user interface that is based on SAP's UI development toolkit for HTML5 (SAPUI5). Download directory One of the first DMO dialogs in the browser is the question where the stack configuration file stack.xml is located. The SUM presumes that the stack.xml is located in the download directory, so there is no separate question about the location of the download directory. (The download directory includes the kernel and software files that were downloaded after using the Maintenance Optimizer.) Additional kernel files required When you select the required kernel files in the Maintenance Optimizer, you have to select the kernel files of the target software release for both the anyDB and the SAP HANA database (in addition to the other files). Additional Steps Since the migration is an additional part of the DMO procedure (compared to the update procedure of the SUM), during the DMO procedure you will have to provide specific information for migration and for the SAP HANA database, such as a migration key, or providing access to the HANA database client installer. Technically, SUM triggers the R3load to export and import the data. Further on, the shadow repository is created on anyDB first, and then copied to the SAP HANA database. Easy reset An easy fallback to the traditional database is possible, as long as the source database (anyDB) and the SUM directory (of the existing update) exist. See section 4.6 Reset Procedure for more information. A reset should not be done in a productive environment after the end users started working on the new system on the SAP HANA database. Password restrictions for SAP HANA database Currently, the password restrictions for users on SAP HANA database are different to those of the SUM. You will have to take that into consideration when creating users for the SAP HANA database. Hint: Start the password with a capital letter, and use only alphanumerical characters.

Database Migration Option (DMO) for SUM 1.0 SP11 Introduction

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

9

2

Planning

This part of the document contains information about planning your SAP system update and the database migration.

2.1

DMO Concept

The Software Update Manager 1.0 SP08 or higher is equipped with a new feature: the Database Migration Option (DMO). This new feature helps you avoiding landscape changes (SID, host name). The SUM tool combines all relevant steps for the in-place migration to SAP HANA: Unicode Conversion, Update, and Migration. Further benefits are the reduced Business Downtime and the remaining consistency of the source database so that a fast fallback is possible.

Note When targeting for a product based on SAP_BASIS 740, you need at least Software Update Manager 1.0 SP9 or an equivalent preliminary version. If you want to migrate an existing SAP system to SAP HANA, several steps may be necessary. The in-placemigration (instead of a new installation) updates the existing system with the advantage that you keep the system-ID, host name, and connectivity. Assuming that you run your SAP system on anyDB, required steps may be a dual-stack split, a Unicode conversion, a database update of anyDB, an update of your SAP software, and a database migration to SAP HANA. The Software Update Manager (SUM) includes an option that combines the update with the database migration. This option is called DMO: database migration option for SUM. It even makes the database update of anyDB unnecessary, because DMO requirements for the anyDB version are reduced compared to the standard update. The processing sequence is based on the shadow system functionality of SUM: 1.

The SUM creates the shadow repository on the traditional database until downtime phase, while in parallel the SAP HANA database is being setup (client, schema etc.).

2.

The shadow repository is copied to SAP HANA, and the database connection of the SAP system is switched to SAP HANA database. Then the downtime starts.

3.

After the migration of the application data (including data conversion), the update is finalized and the SAP system runs on SAP HANA. The traditional database continues to run and it is not modified at all, so it remains a fallback throughout the complete process.

The following figure shows the different phases of the DMO during the procedure:

10

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Planning

2.2

Dual-Stack Split

Since the DMO works only with ABAP systems, so a dual-stack split may be required beforehand. If a dual-stack split is necessary, make sure that it has already been performed before you start the update procedure. For more information about the Dual-Stack split, see the Upgrade Master Guide, which is mentioned in section 1.2 Integration/Further Documentation.

2.3

Unicode

The DMO is available for Unicode and non-Unicode SAP systems. If you want to apply the DMO from an existing non-Unicode Single Code Page SAP system, a conversion to Unicode is mandatory, since HANA database runs on Unicode systems only. The conversion will take place automatically during the update with DMO, provided that you have carried out the preparatory steps for the Unicode conversion as described in the Release Change & Single Code Page Conversion Guide with Database Migration. This guide is available as attachment to SAP Note 1968508. It provides you with detailed information about the steps necessary to convert an existing non-Unicode SAP System with one standard non-Unicode system code page to Unicode. This includes a general description of the conversion, preparatory steps, and follow-up activities as well.

Note MDMP-systems are not supported for the conversion.

Database Migration Option (DMO) for SUM 1.0 SP11 Planning

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

11

2.4

ICNV

ICNV, the transaction for incremental conversion of tables, is not possible in a DMO run and will be automatically disabled beforehand.

12

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Planning

3

Preparation

This part of the document contains information about the preparations that you need to make before you update your system and migrate your database to SAP HANA database. You can prepare for the update while the system is in production operation. Careful preparation of the update is the best guarantee that it runs without errors. The Software Update Manager supports you here by making a range of checks automatically in the preparation roadmap steps (Initialization, Extraction, Configuration, and Checks). To make sure that all requirements are met, run the preparation roadmap steps of Software Update Manager as soon as possible. You can reset and repeat the preparation roadmap steps as often as you need by choosing Back before you start the actual procedure in roadmap step Preprocessing. The successful execution of the preparation roadmap steps is a prerequisite for starting the roadmap step Preprocessing.

3.1

Checking SAP Notes for Latest Information

Check the SAP Note 1813548 for the latest information regarding Database migration option (DMO) for Software Update Manager. See section 1.3.2 SAP Notes for further DMO-related SAP Notes.

3.2

Unicode Conversion: Preparatory Steps

If you want to convert an existing SAP NetWeaver non-Unicode SAP System with one standard non-Unicode system code page to SAP NetWeaver Unicode during the update with DMO, you have to perform pre-processing steps for the conversion. See for this the Conversion Guide mentioned in chapter 2.3 Unicode, and in this guide you check the sections 1 Preparation and 2 Unicode Preconversion Phase.

3.3

BW: Checking RFC Destination into BW client

Ensure that the RFC connection from client 000 to the BW client is working. Check that the RFC destination into the BW client for import post-processing is working, and make sure that the user assigned to this destination (usually the BW-user for background processes) is authorized to submit programs of group SODQADM for background processing. Apply for this SAP Note 1845061 (only required for target releases below BW 7.31 SP 08). If the SAP Note is not applicable to the source release or SP-level, you have to authorize the BW background user to execute programs in the authorization group SODQADM (authorization object S_PROGRAM with field P_ACTION = 'BTCSUBMIT' and P_GROUP = 'SODQADM').

Database Migration Option (DMO) for SUM 1.0 SP11 Preparation

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

13

3.4

BW: Deleting InfoObject 0BCTCOMP

Check if the obsolete InfoObject 0BCTCOMP is used. If not, delete the InfoObject (active version) in transaction RSD1. Otherwise, edit the InfoObject (active version) in transaction RSD1 and de-select "short text exists" and "with texts", save your changes, and activate the InfoObject. Note that this InfoObject is not delivered anymore with BW 7.30 and higher (no new D version).

3.5

BW: Applying BW-Related SAP Notes

You apply the following SAP Notes regarding SAP BW: 1142427 1714734 1388287 1860274 (only required for BW Workspaces and target releases below BW 7.31 SP 9)

3.6

Checking Pool Tables and Cluster Tables

It is recommended that you check all pool tables or cluster tables in the system before the migration. For this purpose, some reports are available, with which you can check if there are corrupt or initial cluster records for a certain table pool the contained pool tables for their readability if the BCD number are correct in a table that you have to specify individually Note, that some reports may have long runtimes for large datasets. For more information about the reports, see SAP Note 1784377.

3.7

Oracle: Suppress Long-Running Phases EU_CLONE_DT_SIZES/EU_CLONE_UT_SIZES

During the update with Database Migration Option, the following phases can be long-running: EU_CLONE_DT_SIZES EU_CLONE_UT_SIZES In the course of these phases, the system updates the database statistics regarding the usage of space that the tables need on the database. The aim is a better distribution of the tables during the system cloning. Before you start the update, you have the option to suppress these long-running phases using the following procedure: 4. Log on to the host where the Oracle database instance is running. Use ora for UNIX system, or user adm for Windows. 5.

14

Open a command prompt and execute the following command:

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Preparation

brconnect -u / -c -f stats -o -t all -f allsel,collect,space –p 8 6. Add to file SAPup_add.par the following line: /ORA/update_spacestat = 0 The file SAPup_add.par is located in the subdirectory bin of the SUM-directory. If this file does not exist yet, create it. In this way, you can suppress the abovementioned phases.

3.8

Installing SAP HANA Database

Make sure, that you have successfully installed an SAP HANA database and that you are prepared to enter system details and the password of user SYSTEM as well.

3.9

Getting the Migration Key for SAP HANA Database

Make sure, that you have a valid migration key for the new SAP HANA database. You can get the key from the SAP Service Marketplace at: http://service.sap.com/migrationkey.

3.10 Getting the Latest HANA Client Software Make sure, that you have the latest HANA client software. You can download the software from the SAP Service Marketplace. After the download, extract it on the server that runs the DMO. The DMO will request the path to the executable hdbinst.

Caution UNIX systems other than Linux: If you are using a UNIX-based operating system with the exception of Linux, you have to install the HANA database client manually to avoid the error described in section 6 Troubleshooting. See item "The HANA database client installation on HP-UX (and other Unix-based operating systems except for Linux) fails with an error."

3.11 Getting a Permanent SAP License Make sure, that you have a permanent SAP license for your system migrated to SAP Hana. You can obtain a new license key from the SAP Service Marketplace at: http://Service.sap.com/licensekey. It is mandatory that you keep your installation number to avoid a secure store migration. Copy the SAP license file to the server that runs the DMO. The DMO will request the path to this license file.

Database Migration Option (DMO) for SUM 1.0 SP11 Preparation

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

15

3.12 Getting the Latest SUM Makes sure, that you have the latest version of the Software Update Manager. For more information, see the SAP Service Marketplace at http://service.sap.com/sltoolset Toolset 1.0 Software Maintenance Software Update Manager 1.0 .

Software Logistics

3.13 Unpacking the SUM archive SUM.SAR You unpack the SUM archive SUM.SAR to the defined SUM directory.

3.14 Changing the Schema Name on SAP HANA By default, the new database schema and schema user will be created as SAP, where is the ID of the SAP System to be migrated. If required, it is possible to choose another value instead of . However, make sure that the schema name starts with ‘SAP’. To change the schema name, proceed as follows: 1.

Extract the SUM archive

2.

After the extraction, create the file /abap/bin/SAPup_add.par.

3.

Add the following line: /migrate/targetschemasid = is the desired identifier to be appended to form the schema name SAP.

3.15 Using SAP HANA Mass Import Feature As of SAP HANA 1.0 Revision 53 you can use the mass import feature which will improve import time dramatically. To activate this feature, you add the following line to the file SUM/abap/bin/SAPup_add.par. /clonepar/imp/procenv = HDB_MASSIMPORT=YES

Caution Do not use mass import with SAP HANA 1.0 revisions lower than 53. It will lead to corrupted data in the target SAP HANA DB.

Note The automatic activation of the mass import feature depending on SAP HANA revision is planned for R3load. The availability is planned for Q2/2014.

16

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Preparation

3.16 Installing Latest SAP Host Agent The SAP Host Agent is a tool that can be used for monitoring and control of SAP instances and non-SAP instances, operating systems, and databases. The SAP Host Agent is automatically installed with every SAP instance based on SAP NetWeaver 7.0 Enhancement Package 2 or higher. As part of an SAP instance, the SAP Host Agent is automatically upgraded with the SAP kernel. However, it can also be installed and upgraded independently from an SAP instance. Make sure, that you have installed the latest version of the SAP Host Agent. For more information, see SAP Note 1031096.

Note The minimum required version is SAP Host Agent 7.20 with patch level 189. Also ensure that you have configured the Secure Socket Layer (SSL) for secure communication. The configuration of Secure Socket Layer (SSL) for the SAPHostAgent is described in the SAP Help Portal at: http://help.sap.com/nw74 Application Help Function-Oriented View Solution Life Cycle Management SAP Host Agent SAP Host Agent Configuration SSL Configuration for the SAP Host Agent.

3.17 Configuring SUM for Use with SAP Host Agent After having installed the proper SAP Host Agent version, and before you use the DMO, you have to configure the Software Update Manager to ensure that it works together with the SAP Host Agent. To carry out the configuration, call the SUMSTART script as follows: Linux:

/abap/SUMSTART confighostagent

Windows:

\abap\SUMSTART confighostagent

Note o Linux: Call the script with the root user. o If you are working with symbolic links for the SUM directory, you need to call the SUMSTART script with the logical path information.

Caution After the configuration with the SUMSATRT script, you have to restart the SAP Host Agent. Use the following command: Linux:

/exe/saphostexec -restart

Windows:

\exe\saphostexec -restart

3.18 Downloading Necessary Files from Maintenance Optimizer 1.

In the Maintenance Optimizer (MOpz), you select for the download the following options:

Database Migration Option (DMO) for SUM 1.0 SP11 Preparation

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

17

721 EXT kernel# when targeting for SAP_BASIS 731 SAPEXEDB archives for both databases, SAP HANA database and the source database

Note o For the database migration from SAP Adaptive Server Enterprise (SAP ASE), you need at least SAP Solution Manager 7.01 with SP level 25 or higher. o When you select the kernel files using the Maintenance Optimizer, take into consideration that you have to select the kernel files of the target software release for both the anyDB and the SAP HANA database. The reason is that the shadow instance is created for the target software release on the existing anyDB first, and then copied to the SAP HANA database. o It is recommended to use the path /usr/sap//download to store the required files. Alternatively you could create a symbolic link. 2. You upload the following files to a folder on the Primary Application Server: SAP NetWeaver 7.x files calculated by MOpz (including kernel for the source and target database) stack.xml file SAP HANA Client for the required operating system SAPCryptoLib (if encryption is used in the source system)

Note Additional SPAM files might be required: The Maintenance Optimizer only offers the latest SPAM version for the target software release. If the Software Update Manager prompts you during the SPAM version check to import the latest SPAM update for your source release, you have to download the latest SPAM version for the current software release manually and extract the files to the directory /usr/sap/trans/EPS/in. Afterwards you confirm the directory in the dialogue so that SUM can find and check this SPAM version. If you have already put the latest SPAM version for the source release into the download directory before the update, the Software Update Manager will extract the files during automatically.

18

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Preparation

4

Running the Software Update Manager

This part of the document provides information about starting and running the Software Update Manager. This section describes required user input and actions, as well as critical points during the update.

Note All required planning and preparation actions must be completed. The Software Update Manager controls the entire procedure, from checking the system requirements and importing the necessary programs through stopping production operation until production operation is resumed. The procedure is divided up into a number of different roadmap steps. The roadmap steps are in turn divided into individual steps. The successful completion of a step is a precondition for the success of all subsequent steps.

4.1

Starting SUM via SAP Host Agent

To use the DMO, you start the Software update Manager not as described in SUM Guide but by means of the SAP Host Agent. However, this requires the following: You have installed the SAP Host Agent 7.20 SP189 or higher as described in section 3.16 Installing Latest SAP Host Agent. You have configured the SAP Host Agent as described in section 3.17 Configuring SUM for Use with SAP Host Agent. The SAP Host Agent needs the configuration file so that it knows where to find and start SUM. To start the Software Update Manager via the SAP Host Agent, you open a browser window and enter the following internet address in the address bar: https://:1129/lmsl/sumabap//doc/gui

Note o has to be replaced with the System-ID o 1129 is the https port of the SAP Host Agent. o Use http instead of https if the SSL is not configured. http://:1128/lmsl/sumabap//doc/gui A dialogue box appears in which you enter as user name the adm and the password. After the log on, the SAP Host Agent starts the Software Update Manager by calling internally the SAPup executable.

Note Technically, the executable SAPup will be started twice, which is visible in the process list. One entry with gt=httpchannel represents the SAPup handling the requests coming from SAP Host Agent. The second SAPup with parameter guiconnect is triggering tools such as R3trans, tp, or R3load. The Software Update Manager starts with the SAPUI5-based user interface.

Database Migration Option (DMO) for SUM 1.0 SP11 Running the Software Update Manager

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

19

4.2

SAPUI5-based User Interface

The DMO for SUM is administrated using a new user interface (UI) technology that is based on the UI Development Toolkit for HTML5 (SAPUI5). The SAPUI5 runtime is a client-side HTML5 rendering library with a rich set of standard and extension controls and a lightweight programming model. The client-side rendering library provides a rich set of controls. You can extend these controls as well as develop new custom controls. Note, that the standard SUM functionality cannot be used with SAPUI5. SAPUI5 is based on a JavaScript library (including jQuery). Its benefits are: zero foot print only a browser is required you can view logs in the browser window you can open the current phase list from the UI Supported browsers for SAPUI5 are: IE 9 or higher (not using compatibility view) Chrome 28 or higher Firefox 21 or higher Roadmap steps and progress bar On the UI of SUM with SAPUI5, you see the different roadmap steps, and a progress bar that shows in percentage how much of a roadmap step is already processed. When you hover with the mouse over the bar, you get information about the runtime estimation. Phase list On the right side of the interface, you can open and close the current phase list. It informs you, which phase of the update and migration procedure is currently processed.

4.2.1

Options

The menu bar of SUM with SAPUI5 offers besides Cockpit and Statistics the Options. With Options, you have the possibility to access logs or to set breakpoints.

Options -> Logs You can either access the log files of the update and migration procedure on the file system level in the subdirectory /SUM/abap/log. Alternatively, you choose on the user interface the menu items Options Logs. You can use the filter functionality to search for the required log files. Some phases generate log files in different sub-directories so that you still might need a file system access to analyze them.

Options -> Breakpoints The SUM offers the possibility to use breakpoints, which allow you to stop the update procedure at a specified point. Using breakpoints, you can also set a breakpoint that allows the DMO procedure to stop before a certain phase. From the user interface, you can set or remove the breakpoints by choosing the menu items Options -> Breakpoints. You can use the filter functionality to search for the required phase.

20

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Running the Software Update Manager

4.2.2

Changing processing parameters during runtime

To maintain background process and tool parameters to configure the update process additionally, you have two possibilities to change processing parameters during runtime: Browser Access Enter in the browser the following internet address: http://:1128/lmsl/sumabap//set/procpar Telnet Access You use the telnet access in scroll mode by entering the command: SAPup set procpar gt=scroll

4.2.3

Problems with the User Interface

In case of problems with the user interface during the update and migration procedure, you can create support files as follows: 1.

Choose the menu item Help

Get Support File.

2.

A new browser window opens.

3.

Save the file locally (no copy & paste of content)

4. Provide file to the support.

Note This procedure is only relevant for UI problems.

4.3 4.3.1

Phases of the Update and Migration Process Extraction

In this phase, the following actions are carried out: Provisioning of the path to the download directory and stack.xml Provisioning of passwords for DDIC and DB user in the source system Checking relevant tools and system parameters DMO specific actions: Provisioning of target database type and a migration key Decision about landscape reorganization for SAP HANA scale out (see section 4.4) Decision about table comparison with SUM (see section 4.5) Checking the relevant SAP Notes

Database Migration Option (DMO) for SUM 1.0 SP11 Running the Software Update Manager

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

21

Further features: The DMO UI can be accessed concurrently by several users. However, it is not possible to define different roles when using the SAP Host Agent URL. In the new phase PREP_INPUT/MIG2NDDB_INI you decide if you want to migrate your system to SAP HANA or keep the existing database. The option Do not migrate to a different DB corresponds to the known SUM functionality, that is, update without migration. In the phase PREP_PARSETUP/CHECK4NOTES_TOOL, DMO displays a list of SAP Notes which are prerequisite for a successful update. The list of SAP Notes is more precise then in previous SUM versions. To transport SAP Notes which cannot be implemented in the SAP Note Assistant (SNOTE), use the report SCWN_TRANPORT_NOTES as described in the SAP Note 1788379 or SCN blog Provide SAP Note for SUM by transport, not SNOTE

4.3.2

Configuration

In this phase, the following actions are carried out: Configuring a number of processes and other performance relevant parameters DMO specific actions: Provisioning of SAP HANA connection parameters and users Installing SAP HANA Client on the DMO host

Note If you encounter problems with the installation of the SAP HANA client, you can install it manually. Make sure that you use the correct directory for the installation. Extracting of Kernels for the source and for the target databases Uploading additional packages, customer change requests, and modifications Further features: When you execute a migration to SAP HANA, use either the Standard” or Advanced option in the tool configuration. The option Single System is not relevant for DMO. The number of R3load processes which you can set in the phase PREP_CONFIGURATION/INITSUBST is the only visible parameter which affects the migration performance in the downtime. Note that you can configure the number of processes dynamically at a later point in time. In the new DMO specific phases, you need to provide connection data and user credentials for SAP HANA. In the phase PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/INSTHDBCLI, you provide details required for the installation of the SAP HANA database client.

22

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Running the Software Update Manager

4.3.3

Checks

In this phase, the following actions are carried out: Calculating the space for the shadow system System health checks (such as Nametab, transport system) BW checks and phases Further features: In the new phase MIG2NDDB_HANA_BW_PARAMS for the usage of BI specific reports phase, you provide parameters for BW specific cleanup tasks. This includes: o Temporary BW query bookmarks o Sent BW query bookmarks o BW traces o BW statistics. Temporary DB space which is required for the shadow system and is calculated during the execution of the roadmap step Checks is too generous. You can use the command /abap/bin/SAPup dmpspc to check the used space at different points of time.

4.3.4

Preprocessing

In this phase, the following actions are carried out: Check for locked objects ABAP Workbench locking Run shadow system for preparation of new release (ACT_UPG, PARDIST, SGEN) DMO specific actions: Uptime migration: Repository Execution of SMIGR_CREATE_DDL BW phases Transition to the downtime (system isolation) Further features: In the phase MIG2NDDB_HANA_BW_PARAMS, you provide parameters for BW specific cleanup tasks. Temporary database space, which is required for the shadow system and is calculated during the execution of the roadmap step Checks, is too generous. You can use the command /abap/bin/SAPup dmpspc to check the used space at different points of time.

Database Migration Option (DMO) for SUM 1.0 SP11 Running the Software Update Manager

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

23

4.3.5

Execution

In this phase, the following DMO specific actions are carried out: Migration of application data Repository & kernel switch Adoptions of structures to new release (PARCONV) Main import (TABIM) XPRAS Further features: Migration of application data from anyDB to SAP HANA database To change the number of R3load processes dynamically use the following commands: cd /abap/bin ./SAPup set procpar gt=scroll Consistency of the migrated content is checked by COUNT(*) on each table in the source and in the target database (Target Release SAP NW 7.31 only) Table type in SAP HANA database (row store vs. column store) is controlled based on the file /abap/bin/ROWSTORELIST.TXT

Note As of target release SAP NetWeaver 7.4, this information is part of the ABAP dictionary. Time estimation for the overall process and for long-running phases is written to the file /abap/log/SAPupStat.log

4.3.6

Postprocessing

In this phase, the following actions are carried out: Cleanups Transaction SPAU Transport unlock DMO specific actions: BW phases Runtime evaluation Further features: Post-processing includes several BW specific phase Evaluation of the update and migration process is written to the file /abap/htdoc/UPGANA.XML.

24

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Running the Software Update Manager

To display this file in a human-readable form, the file UpgAnalysis.xsl must be stored in the same directory.

4.4

Landscape reorganization for the SAP HANA scale out

The automated landscape reorganization feature for the SAP HANA scale out scenario is available with Software Update Manager SP10. Scale out scenario means the deployment of multiple server nodes if memory requirements exceed the available memory of a single server node after the migration on SAP HANA database. For this, several phases are carried out during the run of the SUM: REQ_LANDSCAPE_REORG In this phase, SUM prompts you in a dialogue to import an SQL file from SAP Note 1958346 into the database. Phase REQ_LANDSCAPE_REORG_2 In this phase, SUM prompts you in a dialogue to import an SQL file from a note into the database according to your product: o BW on Hana: SAP Note 1908075 o Suite on Hana: SAP Note 1899817 The following phases run automatically: HDB_CHK_LANDSCAPE_REORG_PRE Check, whether the prerequisites for the landscape reorganization are met. HDB_LANDSCAPE_REORG The landscape reorganization is performed. HDB_CHK_LANDSCAPE_REORG_POST: Check, whether the landscape reorganization has been performed correctly.

4.5

Table Comparison with SUM Caution o This function is only available for update and migrations procedures with Unicode SAP systems. o This function is only intended for SAP tables that belong to the ABAP dictionary. Other tables such as system catalog or database schema tables will not be processed.

After the migration of tables in both the uptime and the downtime, SUM compares with the function Table Comparison with SUM the contents of tables on the target database with the table contents on the source database on the basis of calculated checksums. In a dialog in roadmap step Extraction, SUM offers the following options: Do not compare the table content Compare the content of all tables Compare only the content of selected tables

Database Migration Option (DMO) for SUM 1.0 SP11 Running the Software Update Manager

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

25

The last option offers the possibility to check and compare the table contents of certain tables only. If you choose this option, you are prompted afterwards to enter the location of the file that includes the table names to be checked.

Recommendation Note that the scope of the selected tables influences the runtime of the subsequent phases. That is, the more tables have to be compared, the longer are the affected phases during uptime or downtime. To avoid in particular a long downtime, we strongly recommend comparing the content of selected tables only, such as important application tables. The function Table Comparison with SUM calculates after the migration the checksum for an entire table on both the target database and the source database and compares the values. If the values are not equal, SUM displays an error message depending on uptime or downtime either in the Preprocessing roadmap step in phase MAIN_SHDIMP/SUBMOD_MIG_UPTIME_RUN/EU_CLONE_MIG_UT_CRC_RUN or during the Execution roadmap step in phase MAIN_SWITCH/SUBMOD_MIG_SWITCH/EU_CLONE_MIG_DT_CRC_RUN. In parallel, a LST-file is generated by the system, which informs you about the affected tables and about the possible fixing or ignoring options and their consequences during the phase repeat. The location of the file is displayed in the dialog, which accompanies the error message. In case of errors, SUM offers the following options: 1.

You exit the program.

2.

You fix the errors in the affected tables on the SAP HANA database. 1.

You can fix all errors.

2.

You can fix the severe errors only and accept the non-severe errors.

Afterwards, you repeat the phase so that the table comparison runs again and the phase continues at the point it stopped. 3.

You can fix the errors in the affected tables on the source database. Afterwards, you initialize the phase to restart it from the beginning. The tables will be migrated and checked again.

4.6

Reset Procedure

4.6.1

Reset from a SUM dialog

The SUM offers different procedures for resetting the update, that is, to undo all changes that have been made in the system by the SUM. (For more information, see chapter 5.Running the Software Update Manager Resetting the Software Update Manager in the SUM Guide.) However, when you use the built-in database migration option described in this guide, SUM offers a sole resetprocedure in which all update and migration activities that are carried out until this point in time will be revoked, and the connection to the source database will be re-established. To perform this reset-procedure, SUM displays a Reset-button in the dialogues of every roadmap step. This means that you can carry out the reset at every step of the update and migration procedure, even during or after the Business Downtime.

26

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Running the Software Update Manager

The system is not only reset to run on anyDB afterwards, but completely reset to its status before the update and migration procedure was started. You can then start the update and migration with the SUM again. Note that after you click on the Reset-button, a Confirmation dialog box appears first to prevent an unintended reset.

Note Prerequisites for the reset To carry out the reset, it is required that o anyDB is still available o the SUM directory is not cleaned up Limitations o SAP HANA Client is not deleted from PAS/AAS automatically o BR tools are not restored o User DBACOCKPIT and related roles are not deleted in SAP HANA

4.6.2

Manual Reset on OS-Level

On operating system-level, you can also reset the SUM. Change to the SUM directory and start the SAPup using the parameter gt=scroll. Then choose the BACK-option to trigger the execution of the REVOKE-module.

Procedure: 1.

Start SAPup in scroll mode by entering the following command: cd /usr/sap//SUM/abap/bin ./SAPup gt=scroll

2.

Choose the option Back 01) - Back 02) * Exit 03) - Cleanup and start afresh. [Exit]: 01

3.

Provide the password for user DDIC in client 000 Following activities are executed automatically: o Shutdown of the SAP system immediately o Startup of the original anyDB o Cleanup of clone tables/views in the original anyDB o Restore of the old environment of ADM o Cleanup of the kernel replication directory /usr/sap//SYS/exe/… o Restore of the original kernel to the replication directory /usr/sap//SYS/exe/… o Restore original profiles

Database Migration Option (DMO) for SUM 1.0 SP11 Running the Software Update Manager

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

27

o Unlocking SAP system 4. Provide the password for user SYSTEM in SAP HANA Following activities are executed automatically: o Drop of the SAP user in SAP HANA o Reset of shadow tables and update control tables (batch job RSUPGREV)

28

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Running the Software Update Manager

5

Follow-Up-Activities

5.1

Unicode Conversion: Post-Processing Steps

See the Conversion Guide mentioned in chapter 2.3 Unicode, and check in this guide the section 4. Unicode Conversion Completion Phase for the post-processing steps. This section describes the steps which have to be performed in the Unicode system after the conversion and import of the database has been successfully completed.

5.2

Transport Management System: Domain Controller Configuration

After an upgrade, you have to distribute the information about the new release to all systems in the transport domain. This procedure is described in the SUM Guide in section 6 Follow-Up Activities Transport Management System: Distributing the Configuration. However, due to the database change it is necessary to configure the domain controller before you update the configuration.

Procedure: 1.

Log on to the system that is configured as the domain controller.

2.

Call transaction STMS and choose System

3.

Select the updated SAP System that runs on the HANA database and choose SAP System Configuration.

Overview Update

4. Choose tab Transport Tool, replace the current parameters DBHOST and DBTYPE with the parameters of your target database and save your changes. 5.

Go back to the system overview.

6. Select the system again and choose SAP System 7.

Choose Extras

Update Configuration.

Distribute and Activate Configuration.

Database Migration Option (DMO) for SUM 1.0 SP11 Follow-Up-Activities

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

29

6

Troubleshooting

This part of the document contains additional information about how to proceed when you want to correct known problems that have occurred during the update. Known problems and issues: Symptom: You run a dialogue instances installation after a DMO, and the database SID is shown incorrectly in the dialogue. Solution: Set the parameter j2ee/dbname = in the default profile and start the installation again Symptom: The HANA database client installation on HP-UX (and other Unix-based operating systems except for Linux) fails with an error. Solution: See SAP Note 1929357 for more information and for instructions to solve the issue. Symptom: RFC connection errors occur during the Post-processing roadmap step. Solution: Check the connection information for DBACOCKPIT to SAP HANA database after the downtime processing of SUM, and during Post-processing step if RFC connection errors occur. If the user is locked, choose Activate user now and Reset connect attempts. Symptom: The system does not accept the password of user SYSTEM in phase DBQUERY_PRE Solution: Move the 720 database administration tools to the subdirectory /abap/exe of your SUM directory. Symptom: Error in the Post-processing roadmap step in phase RUN_PSA_VERSION_CREATE Solution: Check with transaction SECSTORE your system for any inconsistent entries. Repair the connection to the SAP BW client following SAP Note 816861 after you have applied the new license. Symptom: Some secondary indexes, that are to be created on selected databases only, can be inconsistent after the migration. These inconsistencies are found in phase RUN_RSDB02CK_END and reported in the log file. Solution: In order to fix the inconsistencies, use transaction SE14 or SE11 and repeat the phase after the correction. Symptom: The creation of a logical index for the master data terminates after the migration to the SAP HANA database. The error messages issued during the execution of the query are for example: table config error; column store error: fail to create scenario/Index does not exist Solution: See SAP Note 1695112 for further information and for a solution.

30

CUSTOMER © 2014 SAP AG or an SAP affiliate company. All rights reserved.

Database Migration Option (DMO) for SUM 1.0 SP11 Troubleshooting

www.sap.com/contactsap

© 2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG 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. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Material Number: