SAP System Operations Guide

Operations Guide

Software Provisioning Manager 1.0 SP21

Document Version: 2.6 – 2017-09-11

CUSTOMER

System Copy for SAP Systems Based on the

Application Server ABAP of SAP NetWeaver 7.3 to

7.5 on UNIX : SAP HANA Database

Content

1

1.1

1.2

1.3

1.4

1.5

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7

Homogeneous and Heterogeneous System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7

Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9

Accessing the SAP Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13

Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13

2

2.1

Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16

Before You Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16

2.2 Use Cases for System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17

2.3 System Copy Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18

2.4 Creating A System Copy Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19

2.5 Various Planning Aspects and Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19

2.6 Migration to SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21

General Information About the Migration to SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21

Prerequisites and Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24

Involved Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24

Considerations for Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

27

Database Instance Export on Additional Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

27

3

3.1

Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

28

General Technical Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

28

3.2 Product-Specific Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31

3.3 Preparing the Migration to SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

32

3.4 Preparing the Media Required for Performing the Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

36

Downloading and Extracting the Software Provisioning Manager Archive. . . . . . . . . . . . . . . . . .

37

Downloading Dedicated Kernel Archives for the Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

39

4

4.1

Database Independent System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

41

System Copy Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

42

Generating DDL Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

50

Using a Dedicated Kernel for the Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

51

Preparing the Table Split. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

52

Preparing the Package Split. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

56

Preparing Parallel Export and Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

58

Additional Considerations for the Migration to SAP HANA Database (Export). . . . . . . . . . . . . . .

58

Exporting the Source System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

60

Setting Up the Target System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

82

2

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Content

5

5.1

Database-Specific System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

91

SAP HANA Database-Specific Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

92

6

6.1

Copying Single Instances Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

93

Copying the Primary Application Server Instance Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

93

6.2 Copying the Database Only – Move Database Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

94

6.3 Copying the Database Only – Refresh Database Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

95

6.4 Copying the Database Only – Refresh Database Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

96

7

7.1

7.2

Follow-Up Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

98

Performing Follow-Up Activities in the Source System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

98

Performing Follow-Up Activities in the Target System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

98

SAP Solution Manager: Connection Between SLD and LMDB. . . . . . . . . . . . . . . . . . . . . . . . . . .

99

Performing Follow-Up Activities for ABAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

99

8

8.1

Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110

R3load Procedures Using the Migration Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110

About the Migration Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

111

Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

112

Assigning DDL Files to Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

128

Defining Groups of Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

128

Processing Split Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

129

Starting the Migration Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

130

Using the “migmonCtrl” Add-On for the Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

135

Using the migmonCtrl Add-On of the Import Migration Monitor. . . . . . . . . . . . . . . . . . . . . . . .

136

Output Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

137

8.2 Analysis of the Export and Import Times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

138

8.3 Table Comparison with Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

138

Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

139

Modes of the Table Comparison Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

139

Using the Table Comparison Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

140

8.4 Using the Package Splitter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

142

Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

143

Starting the Package Splitter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

146

Output Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

147

Executing the STR Splitter and the WHERE Splitter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

148

8.5 Troubleshooting for Migration to SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

148

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Content

C U S T O M E R

3

Document History

The following table provides an overview on the most important document changes.

Note

Before you start the implementation, make sure you have the latest version of this document, which is available at https://support.sap.com/sltoolset

Software Provisioning Manager

.

System Provisioning System Copy Option of

Table 1:

Version

2.6

Date

2017-09-11

2.5

2017-05-22

Description

Updated version for software provisioning manager 1.0 SP21 (SL Toolset 1.0 SP21)

● New Features:

○ Media Signature Check, documented in: New Features, Running the Installer, Pre­

paring the Media Required for Performing the Export .

This feature implies that section Creating Kernel Archives from an Existing SAP

System has been deleted from this documentation because the related option in the installer had to be removed.

○ Load tools are now available as LOADTOOLS.SAR in the Software Provisioning

Manager archive, documented in: New Features, Downloading and Extracting the

Software Provisioning Manager Archive, System Copy and Migration Optimization,

Database Independent System Copy, R3load Procedures Using the Migration

Monitor

○ Simplified additional application server instance installation, documented in: New

Features, Preparing the Installation Media, Downloading SAP Kernel Archives (Ar­

chive-Based Installation)

Updated version for software provisioning manager 1.0 SP20 (SL Toolset 1.0 SP20)

● New Features:

○ New SAPUI5-based graphical user interface (GUI) “SL Common GUI”, docu­ mented in: Prerequisites for Running the Installer, Running the Installer, Useful In­

formation About the Installer

○ Cleanup of operating system users, documented in: SAP System Parameters,

Creating Operating System Users and Groups

○ Refresh database content using a database backup enabled for SAP MaxDB , documented in: Copying the Database Only - Refresh Database Content .

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Document History

4

C U S T O M E R

1.8

1.7

1.6

1.5

1.4

2.1

2.01

2.0

1.9

1.81

Version

2.4.

2.3

2.2

Date

2017-02-06

2016-10-07

2016-06-06

2016-02-15

2015-10-12

2015-10-12

2015-09-14

2015-04-29

2015-04-27

2014-11-24

2014-07-07

2014-03-17

2014-03-05

Description

Updated version for software provisioning manager 1.0 SP19 (SL Toolset 1.0 SP19)

● New Features:

Verification of the integrity of data units in Software Provisioning Manager, docu­ mented in: New Features, Downloading the Software Provisioning Manager Archive

Using a dedicated kernel for the export, documented in: New Features, Using a Dedi­

cated Kernel for the Export , Downloading Dedicated Kernel Archives for the Export,

System Copy Procedure

Refreshing database content using a database backup, documented in: New Features,

Copying the Database Only - Refresh Database Content .

Option to restrict access to database export directory, documented in: New Features,

System Copy Procedure

● Section

Preparing the Media Required for Performing the Export [page 36]

refac­

tored, created subsections Downloading and Extracting the Software Provisioning

Manager Archive [page 37]

,

Downloading Dedicated Kernel Archives for the Export

[page 39]

Updated version for software provisioning manager 1.0 SP18 (SL Toolset 1.0 SP18)

● New Features:

Refreshing database content using a database backup, documented in:

Copying the

Database Only – Refresh Database Content [page 96]

Using RMOSSWPM*.SAR instead of SWPM*.SAR for outdated OS versions not sup­ ported by SAP kernel 7.40 and higher, documented in:

Introduction

Constraints

Updated version for software provisioning manager 1.0 SP17 (SL Toolset 1.0 SP17):

● Archive-Based Installation (see

New Features [page 9] )

● Export option description corrected in

Running the Installer [page 63]

Updated version for software provisioning manager 1.0 SP10 (SL Toolset 1.0 SP16)

Updated version for software provisioning manager 1.0 SP09 (SL Toolset 1.0 SP15)

Updated version for software provisioning manager 1.0 SP09 (SL Toolset 1.0 SP15)

Updated version for software provisioning manager 1.0 SP09 (SL Toolset 1.0 SP14)

Updated version for software provisioning manager 1.0 SP08 (SL Toolset 1.0 SP13)

Updated version for software provisioning manager 1.0 SP08 (SL Toolset 1.0 SP13)

Updated version for software provisioning manager 1.0 SP07 (SL Toolset 1.0 SP12)

Updated version for software provisioning manager 1.0 SP06 (SL Toolset 1.0 SP11)

Updated version for software provisioning manager 1.0 SP05 (SL Toolset 1.0 SP10 )

Updated Version

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Document History

C U S T O M E R

5

Version

1.3

1.2

1.1

1.0

Date

2013-11-22

2013-10-28

2013-08-19

2013-07-17

Description

Updated version

Updated version

Updated version

Initial version

6

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Document History

1 Introduction

1.1 Homogeneous and Heterogeneous System Copy

This document describes how to perform a homogeneous or heterogeneous system copy of an SAP ABAP system based on SAP NetWeaver 7.3 and higher with source operating system UNIX to SAP HANA database as target database, using Software Provisioning Manager 1.0 SP21 (“installer” for short), which is part of SL

Toolset 1.0 SP21.

You can use either database-specific methods or database-independent methods.

For a detailed list of supported SAP system products and releases, see SAP Note 1738258 . For information about supported operating system and database platforms, see the Product Availability Matrix at http:// support.sap.com/pam .

Note

Not all SAP NetWeaver releases or SAP Business Suite applications that are available in Software

Provisioning Manager 1.0 and are described in this guide might have been released already. Always check

SAP Note 1680045 to ensure that the system copy options you want to perform are already supported.

Note

Alternatively, you can copy your system with a completely automated end-to-end framework available using SAP Landscape Management (LVM). For more information, see http://help.sap.com/nwlvm .

1.2 Naming Conventions

●

Software Provisioning Manager

Software provisioning manager is the successor of the product- and release-specific delivery of provisioning tools, such as SAPinst. Before you perform an installation or system copy, we recommend that you always

download the latest version of the software provisioning manager [page 36]

, which is part of the Software Logistics Toolset (“SL Toolset” for short). This way, you automatically get the latest

SAPinst version including latest fixes in the tool and supported processes. For more information about software provisioning manager as well as products and releases supported by it, see SAP Note 1680045

.

SAPinst has therefore been renamed to software provisioning manager 1.0 (the “installer” for short) in this documentation. However, the term “SAPinst” is still used in:

○ Texts and screen elements in the software provisioning manager 1.0 (“installer”) GUI

○ Naming of executables, for example sapinst

○ Naming of Command line parameters, for example SAPINST_USE_HOSTNAME

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Introduction

C U S T O M E R

7

○ Operating system user groups, for example additional group sapinst

In the following, we generally refer to software provisioning manager 1.0 as the “installer”. We only use the term “software provisioning manager” if this is required for technical reasons.

● “usage type”, “technical usage”, and “product instance”

As of software provisioning manager 1.0 SP07 (SL Toolset 1.0 SP12), the term “product instance” replaces the terms “ usage type” and “technical usage” for SAP systems based on SAP NetWeaver 7.3 including enhancement package 1 and higher. For more information, see SAP Note 1877731 . Note that there is no terminology change for older releases and all mentioned terms can be used as synonyms. As this guide is a generic document, the currently used terms remain but only “product instance” is going to be used from now on when referring to SAP NetWeaver 7.3 EHP1 and higher.

For more information, see

New Features [page 9]

.

●

System Copy

Duplication of an SAP system. Certain SAP parameters might change in a copy. When you perform a system copy, the installer installs all the instances again, but it uses a copy of the source system database to set up the database.

●

Source System and Target System

The SAP system containing the original database is called the source system and the system to which the database copy is to be imported is called the target system. Their SAP system names are abbreviated to

SOURCE_SAPSID and TARGET_SAPSID. The terms source database and target database are also used in this description.

●

Homogeneous System Copy

During homogeneous system copy, you use the same operating system and database platform as the original system.

You can perform it using either

Database Independent System Copy [page 41] or

Database-Specific

System Copy [page 91] methods.

●

Heterogeneous System Copy

During heterogeneous system copy, you change either the operating system or the database system, or both. Heterogeneous system copy is a synonym for migration.

You can perform it using the

Database Independent System Copy [page 41] method.

Use this system copy to migrate data of any database platform to the SAP HANA Database platform.

●

Database Copy

Database-dependent part of the system copy.

●

Placeholders

Placeholders such as

<SAPSID>

are used in commands. They are used in the same way as in the SAP system installation documentation. You must replace them with the values valid for your site.

The following additional placeholders are used:

Table 2:

Placeholder Meaning How to find out

<SAPSID>

SAP system ID —

<S_HOST>

System name of the source host Command hostname

<T_HOST>

<S_SAPSID>

System name of the target host

SAP system ID of the source system

Command hostname

<SAPSID> of the original system

8

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Introduction

Placeholder

<T_SAPSID>

<S_DBSID>

<T_DBSID>

Meaning

SAP system ID of the target system

Database ID of the source system

Database ID of the target system

How to find out

<SAPSID> of the target system

<DBSID> of the original system

<DBSID> of the target system

Note

Database ID

<DBSID>

identifies the database instance. The installer prompts you for the

<DBSID>

when you are installing the database instance.

The

<DBSID>

can be the same on IBM i as the

<SAPSID>

.

1.3 New Features

The table below provides an overview of the new features in Software Provisioning Manager.

Make sure that you also read the release notes for your SAP product at http://help.sap.com

Area> <Product> <Release>

What’s New – Release Notes

.

Table 3:

Feature

Media Signature

Check

<Product

Description

The signature of media is checked automatically by the installer during the

Define Parameters

phase while processing the

Media

Browser

screens. As of now the installer only accepts media whose signature has been checked. See also the description of this new security feature in SAP Note 2393060 .

For more information, see

Preparing the Media Required for Per­ forming the Export [page 36]

and Running the Installer [page

63] .

Availability

Software Provisioning Manager

1.0 SP21 (SL Toolset 1.0 SP21)

Note

This feature required the deprecation of feature “Creating

Kernel Archives from existing SAP System” which was intro­ duced with Software Provisioning Manager 1.0 SP09 (SL Tool­ set 1.0 SP14). This deprecation is also stated below in a note in the line related to this deprecated feature in this table (see be­ low).

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Introduction

C U S T O M E R

9

Feature Description Availability

LOADTOOLS.SAR archive in Software

Provisioning Man­ ager

An up-to-date version of the load tools - such as R3load,

R3szchk, R3ldctl, SAPuptool - which were available so far only in the SAPEXEDB.SAR archive of the kernel media, has now been made available in the Software Provisioning Manager ar­ chive

(SWPM10SP

<Support_Package_Number> _ <Version_Number>

.SAR), in a sub-archive named

LOADTOOLS.SAR

, located in the

COMMON/LOADTOOLS folder. For a system copy using Unicode kernel version 7.40 or higher, the load tools from the

SWPM10SP <Support_Package_Number> _ <Version_Number>

.SAR are used automatically instead of the loadtools available in the SAPEXEDB.SAR archive of the kernel media. There is no ac­ tion required from your side, the installer uses the relevant load­ tools automatically once you run it from the extracted

SWPM10SP <Support_Package_Number> _ <Version_Number>

.SAR archive.

Software Provisioning Manager

1.0 SP21 (SL Toolset 1.0 SP21)

Support of Oracle

12.2

Software Provisioning Manager (the “installer”) now supports system copy for SAP systems with Oracle 12.2.

Software Provisioning Manager

1.0 SP21 (SL Toolset 1.0 SP21)

SL Common GUI with SAPINST 7.49

Cleanup of Operat­ ing System Users

With the new installer framework version SAPINST 7.49, you can now use the new SAPUI5-based graphical user interface (GUI)

“SL Common GUI”. For more information, see Useful Information

About the Installer [page 68]

, Running the Installer [page 63] ,

and SAP Note 2336746 .

Software Provisioning Manager

1.0 SP20 (SL Toolset 1.0 SP20)

You can now specify during the

Define Parameters

phase that the operating system users are to be removed from group sapinst after the execution of the installer has completed.

Software Provisioning Manager

1.0 SP20 (SL Toolset 1.0 SP20)

Verification of Integ­ rity of Data Units in

Software Provision­ ing Manager

The integrity of data units extracted from the Software Provision­ ing Manager archive is verified. For more information, see

Down­ loading and Extracting the Software Provisioning Manager Ar­ chive [page 37]

.

Software Provisioning Manager

1.0 SP19 (SL Toolset 1.0 SP19)

In addition, check SAP Note 1680045 whether additional in­ formation is available.

Support of Linux on

IBM Power Systems

(little endian)

Software Provisioning Manager supports as of now Linux on IBM

Power Systems (little endian) as operating system platform for

SAP systems based on SAP NetWeaver 7.5 and higher. For more information, see SAP Note 2378874 .

Software Provisioning Manager

1.0 SP19 (SL Toolset 1.0 SP19)

Option to Restrict

Access to Database

Export

When running the database export, you can specify restricted ac­ cess to the export directory. For more information, see Prerequi­

sites in

System Copy Procedure [page 42] .

Software Provisioning Manager

1.0 SP19 (SL Toolset 1.0 SP19)

10

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Introduction

Feature Description Availability

Use Dedicated Ker­ nel for System Copy

During the

Define Parameters

phase of the source system export, you can now specify dedicated SAP kernel archives that you want to use for the system copy. For more information, see

Download­ ing Dedicated Kernel Archives for the Export [page 39] .

Software Provisioning Manager

1.0 SP19 (SL Toolset 1.0 SP19)

Refresh Database

Content for SAP

HANA

You can now refresh the content of an existing database using a database backup.

For more information, see

Copying the Database Only – Refresh

Database Content [page 96] .

Software Provisioning Manager

1.0 SP18 (SL Toolset 1.0 SP18)

Archive-Based In­ stallation

You can now download the required installation archives instead of the complete SAP kernel installation media. For more informa­ tion, see section Downloading Specific Installation Archives (Ar­

chive-Based Installation) in section Preparing the Installation Me­

dia in the target system installation guides at http:// support.sap.com/sltoolset

System Provisioning

Installation Option Guide for Systems Based on SAP NetWeaver

7.1 and Higher

.

Software Provisioning Manager

1.0 SP17 (SL Toolset 1.0 SP17)

System Provision­ ing for SAP

NetWeaver 7.5 and

SAP NetWeaver 7.5based Products

All system provisioning tasks (installation, system copy, system rename) are available for the new SAP NetWeaver 7.5 release.

The Dual Stack option, which integrates an AS ABAP and AS Java in a single system (common System ID

<SAPSID>

, common startup framework, common database), is no longer supported in

SAP systems based on SAP NetWeaver 7.5.

Software Provisioning Manager

1.0 SP09 (SL Toolset 1.0 SP15)

● After upgrading to SAP NetWeaver 7.5 PI, you first have to split the still existing dual stack-system before you can use

SAP NetWeaver 7.5 PI productively.

For more information, see the Upgrade Master Guide - SAP

NetWeaver 7.5 at: http://help.sap.com/nw75

Installation and Upgrade

● SAP NetWeaver 7.5 is Unicode only

● The primary application server instance directory has been renamed from /usr/sap/

<SAPSID> /

DVEBMGS <Instance_Number>

to /usr/sap/

<SAPSID> /

D <Instance_Number>

.

● Declustering and depooling of tables during the installation is enabled by default. For more information, see SAP Note

1892354 .

System Provision­ ing for SAP Solution

Manager 7.2

All system provisioning tasks (installation, system copy, system rename) are available for the new SAP Solution Manager 7.2 re­ lease. Compared to previous SAP Solution Manager releases,

SAP Solution Manager 7.2 is no longer provided as a classical dual-stack system (ABAP system with Java Add-in), but consists of a separate ABAP and Java stack.

Software Provisioning Manager

1.0 SP09 (SL Toolset 1.0 SP15)

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Introduction

C U S T O M E R

11

Feature Description Availability

Creating Kernel Ar­ chives from existing

SAP System

You can reuse the binaries of a dedicated SAP system for a new

SAP system installation or target system installation in the con­ text of a system copy by creating *.SAR archives based on the

*.lst files from the executable (exe) directories of the source

SAP system.

Software Provisioning Manager

1.0 SP09 (SL Toolset 1.0 SP14)

Note

This feature is only available for Unicode systems.

Caution

This feature has been deprecated with Software Provisioning

Manager 1.0 SP21 (SL Toolset 1.0 SP21) and the related option has been removed from the

Welcome

screen. This depreca­ tion has been accomplished to ensure compliancy with the new feature “Media Signature Check” of Software Provision­ ing Manager 1.0 SP21 (SL Toolset 1.0 SP21) described above in this table.

Executing R3szchk in Parallel

You can now execute R3szchk in parallel. Using this feature you can improve the runtime of the export.

Software Provisioning Manager

1.0 SP08 (SL Toolset 1.0 SP13)

Database Instance

Export on Additional

Hosts

To increase the performance of the export you can use more than one SAP application server of the source system for the export.

For more information, see

Database Instance Export on Addi­ tional Hosts [page 27]

Software Provisioning Manager

1.0 SP07 (SL Toolset 1.0 SP12)

Usage Type Library

Deprecation for

SAP Systems Based on SAP NetWeaver

7.3 EHP1 and Higher

Software Provisioning Manager 1.0 no longer uses the “Usage

Types” definitions in its business logic for SAP systems based on

SAP NetWeaver 7.3 EHP1 and higher. This is done to unify model­ ing and terminology across all SAP tools used during the plan­ ning, installation and maintenance activities. The “Product In­ stance” definition replaces “Usage Types” regarding product modeling. For more information, see SAP Notes 1970349 and

1877731 .

Software Provisioning Manager

1.0 SP07 (SL Toolset 1.0 SP12)

Feedback Evalua­ tion Form

SAP SE’s aim is to provide fast and efficient procedures. To eval­ uate the procedure you just carried out, we need information gen­ erated by the tool during process execution and your experience with the tool itself. A new evaluation form contains a simple ques­ tionnaire and XML data generated during the procedure.

Software Provisioning Manager

1.0 SP07 (SL Toolset 1.0 SP12)

Port 4239 is used for displaying the feedback evaluation form.

For more information, see

Prerequisites for Running the Installer

[page 60]

.

12

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Introduction

Feature Description Availability

Option

Verify Signed

Media

The digital signature ensures that the signatory of a digital docu­ ment can be identified unambiguously and signatory’s name is documented together with the signed document, the date, and the time.

For more information, see SAP Note 1979965 .

Software Provisioning Manager

1.0 SP06 (SL Toolset 1.0 SP11)

1.4 Accessing the SAP Library

The references to the SAP NetWeaver Library documentation in this guide always refer to the following on

SAP Help Portal:

● SAP systems based on SAP NetWeaver 7.3: http://help.sap.com/nw73

Application Help Function-Oriented View: English

● SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1: http://help.sap.com/nw731

Application Help Function-Oriented View: English

● SAP systems based on SAP NetWeaver Application Server for ABAP 7.4: http://help.sap.com/soh

<Release>

Application Help SAP Library: English SAP NetWeaver

● SAP systems based on SAP NetWeaver 7.4: http://help.sap.com/nw74

Application Help Function-Oriented View: English

● SAP systems based on SAP NetWeaver 7.5: http://help.sap.com/nw75

Application Help Function-Oriented View: English

1.5 Constraints

● Only perform a system copy if you have experience in copying systems and thorough knowledge of the operating system, the database, and the ABAP Dictionary . Only perform a heterogeneous system copy (of a production, development, or test (QA) system) if you are a certified system support consultant or a certified SAP Technical Consultant.

● Declustering with Software Provisioning Manager only works if you perform a system copy of the

complete system using the method described in section Database Independent System Copy [page 41]

.

An “inplace-declustering” solution with Software Provisioning Manager is not supported.

● SAP ASE is not supported on SAP NetWeaver 7.1 / 7.1 EHP1 for banking services from SAP and SAP

NetWeaver Mobile 7.1 / 7.1 EHP1.

● System copy is not supported for the Diagnostics Agent.

For more information and guidance see the Diagnostics Agent Maintenance Procedures article at http:// wiki.scn.sap.com/wiki/x/n4efFg .

● SAP does not support client transport as a system copy method. Transporting production clients is not supported at all. You can use client transport for the initial setup of an SAP system infrastructure. This documentation does not cover the client copy procedure.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Introduction

C U S T O M E R

13

● This documentation does not describe how to export and import a database with the installation tools for reorganization purposes. Use the appropriate tools for database reorganization, as SAP does not support this installation option.

● If you have made modifications in your development system and want to copy your quality assurance or production system onto the development system, see SAP Note 130906 .

● This documentation describes how to copy data from one SAP system to another SAP system based on

SAP NetWeaver Application Server. This documentation does not describe how to copy data from non-

SAP systems to SAP systems.

● If you want to perform a Unicode Conversion, see one of the following SAP Notes:

○ SAP Note

551344 – Unicode Conversion Documentation

○ SAP Note

1051576 – Conversion of Single Code Page Systems to Unicode

○ SAP Note

928729 – Combined Upgrade & Unicode Conversion (CU)

● SAP does not support all data archiving operations after a system copy.

If you used data archiving in the source system, you might not always have access from the target system to the archive files that were created. For more information, see SAP Note 153433 and Data

Management Landscape & Transformation Solutions at https://support.sap.com/dm&lt .

Access from the target system to archived files in the source system without a dedicated archive migration project is only supported as follows:

○ You have copied a source system that uses external data archiving. The target system has read-only access to this archive.

○ You have copied a source system that uses data archiving locally. You can either arrange network access for appropriate archive file sharing or copy all archive files to the file system of the target system.

Note

Only valid for SAP Business Warehouse:

If you use ADK-based archiving of request administration data in SAP Business Warehouse, you have to copy all archive files related to archiving object BWREQARCH to the file system of the target system.

Only then write access (like deletion of requests, deletion of the complete data target content, further upload of data to other targets, changing the quality status of requests or InfoProvider rebuild) to requests with archived administration data is possible in the target system of the copy.

In all other cases, contact Data Management Landscape & Transformation Solutions at https:// support.sap.com/dm&lt or [email protected].

● When you perform a system copy, all product instances or usage types in the source system are copied to the target system. This means that none of the product instances or usage types in the target system can be excluded from the system copy, nor can you select product instances or usage types.

● “Dos and Don'ts” for system copy:

○ Do:

○ Follow the Open SQL standard.

○ Make sure that all communication runs through the database pool.

○ Don't:

○ Save any system and infrastructure-specific data in business objects. Use a pointer to the central storage of such information, for example:

○ SAP system ID and SID (SAPSID = SID = SAP system name)

○ Host name

14

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Introduction

○ IP addresses

○ Services and ports

○ Logical destinations and logical system names

○ Other technical infrastructure names

○ Use file system persistency.

○ Set up dependencies between Java and ABAP.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Introduction

C U S T O M E R

15

2 Planning

This section describes how to plan your system copy.

Before You Start [page 16]

Use Cases for System Copy [page 17]

System Copy Methods [page 18]

Creating A System Copy Plan [page 19]

Various Planning Aspects and Parameters [page 19]

General Information About the Migration to SAP HANA [page 21]

Prerequisites and Restrictions [page 24]

Involved Tools [page 24]

Considerations for Performance [page 27]

Database Instance Export on Additional Hosts [page 27]

2.1 Before You Start

● The SAP OS/DB Migration Check prepares you in an optimal way for a successful migration and supports smooth continued operations on the new platform. The OS/DB Migration Check is mandatory, if you are going to migrate a productive system.

For more information, see https://support.sap.com/support-programs-services/services/os-dbmigration.html

. In addition to the information contained on this page, check the

SAP OS/DB Migration

Planning Guide

that is available in the

Media Library

.

● Before you start the system copy, you must read the following :

○ SAP Notes

Read the following SAP Notes for up-to-date information on system copy and corrections to the system copy documentation:

○ SAP Note

1680045 – Release Note for Software Provisioning Manager 1.0

○ SAP Note

1738258 – System Copy of Systems Based on SAP NetWeaver 7.1 and Higher

Make sure that you have the most recent version of the SAP Notes, which you can find at: https://support.sap.com/notes .

○ Guides for the target system installation

This system copy guide describes only the source system export in full detail. As for the installation of the target system, this system copy guide describes only the system copy-specific steps in section

Setting Up the Target System [page 82]

, but refers for all steps that are identical with a new system installation to the appropriate operating system and database-specific installation guide available at http://support.sap.com/sltoolset

System Provisioning Installation Option of Software

Provisioning Manager

.

16

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Planning

○ SAP System Copy and Migration at https://wiki.scn.sap.com/wiki/display/SL/System+Copy+and

+Migration

○ SAP system landscape copy:

○ Best Practice document SAP System Landscape Copy for SAP NetWeaver and SAP Solutions available at https://support.sap.com/esacademy

○ SAP Note

885343 – SAP System Landscape Copy

○ SAP Note

1990240 – Support of mixed landscapes (Unicode and Non-Unicode)

○ SAP Note

82478 – SAP system OS/DB migration

● If you have problems during the system copy, create a customer message using the application area BC-

INS-MIG.

2.2 Use Cases for System Copy

You can apply the system copy for the following:

● Setting up system landscapes (where the SAP systems have different

<SAPSID> s).

● Providing systems for testing, demonstration, training, and standby.

To create these systems you can either perform an initial system copy or use a database export to overwrite the database of an already existing target system (refresh use case).

Depending on the purpose of the system, it might be advisable to use the same SAP system ID, even though this prevents you from including the system in a system group for transports.

Note

○ Oracle only: You cannot create standby systems with a system copy.

○ You should perform system copy in a test system first. This way you can identify customer-specific problems that might result from modifications.

● Changing the operating system, the database, or both.

You can use different operating system releases or database releases for the source and target systems, but the SAP system release of the source and target systems must be the same.

● Changing the hardware.

Note

You can set up the SAP system infrastructure (development, quality assurance, and production system) without making a system copy as follows:

1. Install all SAP systems, starting with the development system. Customize the development system as described in the implementation documentation.

2. Transport the client-dependent and client-independent data to the quality assurance and production systems.

However, if you do not follow this concept, you can also install a system, customize it, and then perform a system copy.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Planning

C U S T O M E R

17

2.3 System Copy Methods

You can choose between the following system copy methods:

Before making your decision, read the documentation SAP System Copy and Migration at https:// wiki.scn.sap.com/wiki/display/SL/System+Copy+and+Migration in order to make yourself familiar with the available system copy and migration procedures.

● The database-independent procedure using SAP tools

Use this method if database-specific methods are either not available or not suitable. For more

information, see Database-Independent System Copy [page 41]

.

● The database-specific procedure using tools provided by the database vendor

For more information, see

Database-Specific System Copy [page 91] .

● Copy single instances only

The following options are supported:

○ You can move a primary application server instance to a different host within your system.

For more information, see Copying the Primary Application Server Instance Only [page 93] .

○ You can move a database instance to a different host within your system.

For more information, see Copying the Database Only – Move Database Instance [page 94]

○ You can refresh an existing database instance without having to copy the primary application server instance and to reinstall additional applications servers.

For more information, see Copying the Database Only – Refresh Database Instance [page 95]

○ You can refresh the content of an existing database without having to export the database content, but using a database backup.

Recommendation

We recommend that you use option

Refresh Database Content

if you need to equalize the database content of two or more already existing and configured systems, for example in automatized system landscapes with “template” systems which have to correspond to precisely defined standards, such as predefined host names, network settings, users, security policies.

For more information, see Copying the Database Only – Refresh Database Content [page 96]

Caution

You cannot copy single product instances, usage types, or components!

● Changing the system variant

If you want to change your system variant (for example, if you want to make your standard system a distributed or high-availability system), proceed as follows:

1.

Perform the export [page 60]

.

2. For the import, choose the relevant system copy options as described in the process flows of the

system copy procedure [page 42]

.

18

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Planning

2.4 Creating A System Copy Plan

Create a plan to perform the system copy.

Procedure

1. When copying a system that contains production data, choose the moment for the copy carefully. This could be a month-end or year-end closing.

2. Consider the downtime of the source system (for preparations and copying) when planning the system copy.

3. Consider a test run.

Perform a test run of the system copy. You can use the time taken by the test run to calculate the system downtime:

○ If you want your target system to replace your source system, try to perform a complete test run. This means that the entire database is exported from the source system, transferred to the target system, and imported there. System downtime is approximately equal to the total test time (that is, time for export, transport, and import).

○ If you do not want to replace your source system, a partial test run (export of the entire database or parts of it) can be sufficient to calculate the system downtime. The source system is only down for the time of the export.

Calculating the system downtime is particularly important for very large databases (VLDB) or when tapes are being used. The test run is also to determine the amount of export data. Choose the best data transfer method (for example, FTP or tape). We recommend that you only perform read/write actions on local file systems.

4. Define a schedule for the test migration and the final migration.

2.5 Various Planning Aspects and Parameters

This section provides information about various planning aspects and parameters required for system copy.

Support of Mixed Landscapes (Unicode and Non-Unicode)

If your system landscape is mixed with Unicode and Non-Unicode systems, or if you have third party software in your system landscape which does not support Unicode at all, check SAP Note 1990240 for potential support restrictions.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Planning

C U S T O M E R

19

Using NFS-Mounted File Systems

Note that the overall performance of the system copy depends on all links in the chain, starting from the performance of the source database to the following:

● Performance of the server on which the export is executed

● File system to which the export data is written

● Target side that reads from the export medium and imports it into the target database

You have to make sure that all aspects are configured for optimal performance. For recommendations on NFS configuration, see SAP Note 2093132 .

Note

If you want to use NFS for the system copy export, make sure that you create secure file share permissions.

Be aware that the communication protocol for NFS needs to be a safe one, for example SSFS.

Configuration Analysis and Hardware Configuration

● In the event of a major change in hardware configuration (for example, new machine type, new hard disk configuration, new file system type), consult your SAP-authorized hardware partner.

● You need to determine the following:

○ Number of application servers

○ Expected size of the database

○ Additional disks or other hardware required

○ Required memory

Note

Refer to the section on hardware and software requirements in the SAP system installation documentation to determine the system requirements.

Choosing an SAP system ID

You can choose the new SAP system ID

<TARGET_SAPSID>

freely during a new installation.

Caution

To meet the requirements of the Workbench Organizer, you must choose different SAP system IDs for different SAP systems.

Make sure that your SAP system ID:

● Is unique throughout your organization

Do not use an existing

<SAPSID>

when installing a new SAP system.

20

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Planning

● Consists of exactly three alphanumeric characters

● Contains only uppercase letters

● Has a letter for the first character

● Does not include any of the reserved IDs listed in SAP Note

1979280 .

● If you want to install an additional application server instance, make sure that no Gateway instance with the same SAP System ID (SAPSID) exists in your SAP system landscape.

SAP License

Once the installation is completed and the SAP system copy has been imported, you require a new license key for the target system. The license key of the source system is not valid for this system. For information about ordering and installing the SAP license, see the

SAP Library [page 13]

for your release at:

● SAP NetWeaver 7.3 and higher:

SAP NetWeaver Library: Function-Oriented View Solution Life Cycle

Management SAP Licenses

For more information about SAP license keys, see http://support.sap.com/licensekey or SAP Note 94998

.

Archiving files

Data that has been archived in the source system (data that does not reside in the database but was moved to a different storage location using SAP Archive Management) must be made accessible in the target system.

Adapt the file residence information in the target system. For more information, see the following:

● The

SAP Library [page 13] for your release at:

○ SAP NetWeaver 7.3 and higher:

SAP NetWeaver Library: Function-Oriented View Solution Life

Cycle Management Data Archiving

● The blogs at https://blogs.sap.com/2016/10/11/software-application-lifecycle-management-sap-bw/ regarding SAP NetWeaver Application Lifecycle Management and housekeeping

Access to archive files is platform-independent.

2.6 Migration to SAP HANA Database

2.6.1 General Information About the Migration to SAP HANA

To migrate your source database to the SAP HANA database, you perform a heterogeneous system copy using standard tools, such as software provisioning manager 1.0 (the “installer”), R3load, and the

Migration Monitor.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Planning

C U S T O M E R

21

A heterogeneous system copy has the following characteristics:

● Operating system is changed (in this case, system copy is called OS migration – not relevant for the migration to SAP HANA) or

● Database system is changed (in this case, system copy is called DB migration) or

● Operating system and database system are changed (in this case, system copy is called OS/DB migration)

You perform a heterogeneous system copy using a database-independent procedure (with some exceptions for certain OS migrations, where cross-platform backup or restore is supported).

You can migrate your database to SAP HANA database as of the following releases:

● SAP Business Warehouse only: SAP NetWeaver 7.3 Support Package 5

● SAP Business Warehouse only: SAP NetWeaver 7.3 EHP1 Support Package 4

● SAP NetWeaver Application Server for ABAP 7.4

To migrate your database to SAP HANA database, the following conditions have to be met:

● Your SAP system must meet the minimum hardware and software requirements listed in the following table:

Table 4:

Requirement Values

Hardware

Operating System Version

Database Software

SAP Kernel

SAP Java Virtual Machine (SAP

JVM)

Your operating system platform must be 64-bit.

For a comprehensive list of supported operating system releases, see the Prod­ uct Availability Matrix (PAM) at: https://support.sap.com/pam .

The following source database platforms are supported:

○ Oracle 11.2 or higher

○ MS SQL Server 2008 or higher

○ IBM DB for Linux, UNIX, and Windows V9.7 or higher

○ SAP MaxDB 7.8 or higher

○ SAP Sybase ASE 15.7 or higher

○ IBM DB2 for i 6,1 or higher

○ IBM DB2 for z/OS V9 or higher

○ SAP NetWeaver 7.3/ 7.3 EHP1 only: SAP Kernel 7.20 EXT 64-bit is instal­ led.

○ SAP NetWeaver AS for ABAP 7.4 (SP0 and SP01) only: SAP Kernel 7.38 is installed.

○ SAP NetWeaver AS for ABAP 7.4 (SP02 and higher) only: SAP Kernel

7.40 or higher is installed.

SAP JVM 6 or higher is installed.

● SAP HANA database is available only for SAP systems based on SAP NetWeaver Application Server ABAP or for SAP systems based on SAP NetWeaver Application Server Java. It is not available for SAP

NetWeaver dual-stack (ABAP+Java) systems such as SAP Process Integration.

22

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Planning

Note

If your system is a dual-stack (ABAP+Java) one, you first have to split it into one ABAP and one Java stack before migrating to SAP HANA database. For example, perform a dual-stack split procedure before upgrading to SAP NetWeaver 7.3 (or higher) or uninstall the Java stack and re-install it as a separate system if it is possible for your scenario.

For more information about how to perform a dual-stack split procedure, see the Dual-Stack Split guide, which is available at: https://support.sap.com/sltoolset

System Provisioning Split Option of

Software Provisioning Manager Dual-Stack Split Guides

● SAP HANA runs only on Unicode.

Generic Information

● Read the following information:

○ The blog Migration to SAP HANA: SAP Kernel update for the migration in SAP Community Network about R3* tools provided with the SAP kernel that are involved in the migration to SAP HANA

(Migration to SAP HANA: SAP Kernel Update for the Migration): http://scn.sap.com/community/it-management/alm/software-logistics/blog/2013/09/30/ migration-to-sap-hana-sap-kernel-update-for-the-migration

○ In addition, take a look at the blog Migration to SAP HANA using Software Provisioning Manager: How

to Begin? at: http://scn.sap.com/community/it-management/alm/software-logistics/blog/2013/10/04/ migration-to-sap-hana-using-swpm-how-to-begin

○ The blog SAP BW Powered by SAP HANA- Some points to remember for Database Migration to HANA providing further details for the migration to SAP HANA – with focus on SAP BW, but partly also valid for general migrations to SAP HANA: http://scn.sap.com/community/netweaver-bw-hana/blog/2013/08/29/sap-bw-powered-by-saphana-some-points-to-remember-for-database-migration-to-hana

● For an overview of migration path options to SAP NetWeaver 7.4 or SAP NetWeaver 7.5 running on SAP

HANA, see the End-to-End Implementation Roadmap guides available at: https://help.sap.com/nw

SAP NetWeaver

<7.4 or 7.5>

Integration

● See also page Migration of SAP Systems to SAP HANA at https://blogs.sap.com/2013/12/03/migrationof-sap-systems-to-sap-hana/ for information on planning the migration procedure of your SAP systems to in an on-premise landscape.

● For more information about release and roadmap information around the kernel versions and their relationship to SAP NetWeaver support packages including important notes on downward compatibility and relSAP HANAease dates, see the document Understanding Kernel Releases for the SAP NetWeaver AS

ABAP at: https://archive.sap.com/documents/docs/DOC-54170

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Planning

C U S T O M E R

23

Application-Specific Information

For the migration of SAP Business Warehouse (SAP BW), see the following information:

● For SAP BW running on SAP HANA, see the End-to-End Implementation Roadmap for SAP NetWeaver BW

powered by SAP HANA at https://help.sap.com/nw

SAP NetWeaver

<7.4 or 7.5>

Integration

● SAP NetWeaver BW Application Lifecycle Management at: https://blogs.sap.com/2016/10/11/softwareapplication-lifecycle-management-sap-bw/

● Best practice information for SAP NetWeaver BW powered by SAP HANA scale out at: https:// blogs.sap.com/2013/03/27/sap-netweaver-bw-powered-by-sap-hana-scale-out-best-practices/

2.6.2 Prerequisites and Restrictions

Make sure that you take the following prerequisites and restrictions into consideration:

● Delivery of SAP HANA appliances can take some time – therefore, order required target hardware early.

● Before starting the database migration, perform a hardware check using the script HanaHwCheck.py – for more information, see SAP Note 1652078 . In case the hardware check fails, try the latest version of the script that is attached to SAP Note 1658845 .

● For recommended Linux settings, refer to SAP Note

1824819 (SAP HANA DB: Recommended OS settings for SLES11 / SLES4SAP SP2).

● Install the latest available revision of SAP HANA before the migration.

● Make sure that you install a current SAP HANA client that has the same version as the SAP HANA database. For more information about how to install a current SAP HANA client, see SAP Note 1825053

.

● Install the SAP HANA studio as described in the SAP HANA Studio Installation Guide available at http:// help.sap.com/hana_appliance

● Installation and Upgrade Information and in SAP Note

1789632 .

● Installation of external software on the SAP HANA appliance must be in compliance with SAP Note

1730928 .

● To prepare the adjustment of your custom code, install the ABAP Development Tools as described in the guide provided in SAP Note 1718399 .

● For SAP Warehouse (SAP BW), check SAP Note

1600929 , providing further information relevant for the migration to SAP HANA.

2.6.3 Involved Tools

This section provides expert information and recommendation for some of the involved migration tools.

For an overview of the most important migration tools for ABAP, see https://archive.sap.com/documents/ docs/DOC-34258 .

24

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Planning

Software Provisioning Manager 1.0

Software Provisioning Manager 1.0 (the “installer”) offers many services, including system installation and system copy. For our use case of database migration, it orchestrates all involved tools.

For more information about latest corrections in Software Provisioning Manager 1.0 for the migration to SAP

HANA, see the corresponding blog Migration to SAP HANA: Latest News about Software Provisioning Manager

1.0 in SAP Community Network at: https://blogs.sap.com/2013/09/30/latest-news-about-swpm-10-sltoolset/

Migration Monitor (Migmon)

The Migration Monitor is part of software provisioning manager 1.0. It uses the EXT, WHR, STR,

TPL files to control the unload and load, to accelerate the load by automatic parallelization, and to generate the

R3load task and command files (TSK and CMD files).

Especially for SAP HANA, the Migration Monitor comprises a migmonctrl.jar add-on that gets invoked automatically to adjust the amount of R3load jobs dynamically during the import – this is described in the

Import section below.

For more information, see:

●

R3load Procedures Using the Migration Monitor [page 111]

● SAP Note

784118 (System Copy Tools for ABAP Systems)

●

Restarting R3load Processes [page 80]

.

R3load

R3load performs all load tasks in a database- and platform-independent format. It generates the database export of all SAP objects that are defined in the ABAP Dictionary and archives the configuration and components in the file system. Then, it performs the load of ABAP tables into the target database. It is available via the kernel of the ABAP application server.

R3ldctl

R3ldctl makes information of source system database tables available for migration tools offline by reading

ABAP Dictionary structures from the source database. It creates structure (STR) files that describe the definition of tables, indexes and views, and it creates database-specific template (TPL) files containing commands in Data Definition Language (DDL), which define data structures. R3ldctl is also available via the kernel of the ABAP application server.

For more information, see Exporting the Source System [page 60]

.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Planning

C U S T O M E R

25

R3ta

To copy large tables, use the R3ta table splitter tool – it automatically generates WHERE conditions with which a subset of table data can be accessed and with which the export and import of one table can be performed in parallel by starting several R3load processes that work on packages. These WHERE conditions are integrated into the R3load TSK files. If the export or import of a table is cancelled with an error, only the processing of the package with the error has to be repeated instead of loading or unloading the complete table another time.

R3ta is available via the kernel of the ABAP application server.

Package Splitter

Package Splitter reduces the overall runtime of export and import by distributing packages in an optimal way from the existing structure files (STR + EXT). It is part of software provisioning manager 1.0.

Time Analyzer (Migtime)

To get statistical data about runtimes, use Migtime. It supports you in analyzing the runtimes of the export and the import:

● It calculates the runtime per package

● It lists the long running objects within a package for further splitting

● It creates a list (either a text or an HTML file) with start and end date or time per package

● It is provided with software provisioning manager 1.0 (MIGTIME.SAR is available in

<Extracted_Software_Provisioning_Manager_Archive> \COMMON\INSTALL)

For more information, see SAP Note 784118 .

Tools Specific for SAP BW

For SAP BW, consider to use the following specific tools:

● A specific checklist tool for SAP BW (see SAP Note

1729988 – SAP NetWeaver BW powered by SAP

HANA - Checklist Tool) automates the check of best practice guidelines for operations and pre-requisites for the migration of an existing SAP BW system to SAP HANA.

● Before migrating to SAP BW on SAP HANA, you can use the SAP BW ABAP Routine Analyzer to identify

ABAP statements that can potentially be optimized for SAP HANA – for more information, see SAP Note

1847431 (SAP NetWeaver BW ABAP Routine Analyzer).

● To make the migration of an existing SAP BW deployment to SAP HANA easier, the SAP NetWeaver

Migration Cockpit for SAP HANA combines several tools – for more information, see SAP Note 1909597

(SAP NetWeaver BW Migration Cockpit for SAP HANA).

26

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Planning

2.6.4 Considerations for Performance

Note the following recommendations for the performance of the migration procedure:

● As a rule of thumb, it is recommended that you configure two or three parallel R3load processes per CPU on the host on which the corresponding R3load is running.

● Closely monitor the CPU and I/O utilization to adapt the number to actual project conditions.

● If possible, keep a dedicated internal disk with an own controller for the export directory.

● Only change table type from column store to row store, if proposed by SAP HANA development support.

● We recommend to use the mass loader option of the installer:

○ For this, SAP HANA Revision 51 or higher is required (see SAP Note

1806935 )

○ To activate the option, set the environment variable HDB_MASSIMPORT=YES before starting the installer.

● With the latest versions of the installer, parallel export/import is available for products based on SAP

NetWeaver 7.3 and SAP NetWeaver 7.3 including EHP1. For latest information, see SAP Note 1775293 .

● If scale-out is released for your product, consider to use an SAP HANA standby server node for the import to improve performance. For more information, see the corresponding information in

Installing the Target

System - Additional Considerations for the Migration to SAP HANA Database [page 87] .

● Throughput is quite individual and depends on the hardware configuration and other factors. You can use the Java tool Migtime to evaluate the runtime of export/import – for more information, see SAP Note

784118 . It might require multiple runs to find bottlenecks and optimize them.

● For comparing ABAP code execution times after a migration to SAP HANA, consider the recommendations in SAP Note 1942889 (Comparing ABAP code execution times after HANA migration).

● To increase the performance of the export you can use more than one SAP application server of the source system for the export. For more information, see

Database Instance Export on Additional Hosts

[page 27]

.

2.6.5 Database Instance Export on Additional Hosts

Especially for the migration to SAP HANA, it has become common to use an SAP HANA standby server for the import into the database instance. As SAP HANA servers are very powerful, the import is delayed because it has to wait for the relatively slow data delivery from the export.

To increase the performance of the export you can use more than one SAP application server of the source system for the export. For example, you can use the hosts of the existing additional application server instances of the source system.

You can do this by choosing

Database Instance Export on Additional Host

in the installer after starting the

Database Instance Export

.

During the procedure, if the feature is chosen, “package-filter files” are created, which split the packages into equal (by size or runtime) parts according to the number of hosts entered.

For more information about the additional steps required for this procedure, see System Copy Procedure

[page 42]

.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Planning

C U S T O M E R

27

3 Preparations

Before you start the system copy, you must perform the following preparation steps.

Related Information

General Technical Preparations [page 28]

Product-Specific Preparations [page 31]

Preparing the Migration to SAP HANA Database [page 32]

Preparing the Media Required for Performing the Export [page 36]

3.1 General Technical Preparations

To make a consistent copy of the database, you need to prepare the source system and perform some subsequent actions on the target system. This is not necessary when performing a test run.

Context

The following section describes important preparations on the source system before you perform homogeneous or heterogeneous system copy.

For more information about SAP System Administration, see the Administration Information in the SAP Library for your release at:

● SAP systems based on SAP NetWeaver 7.3: https://help.sap.com/nw73

Operations Technical

Operations for SAP NetWeaver

● SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1: https://help.sap.com/ nw731

Operations Technical Operations for SAP NetWeaver

● SAP systems based on SAP NetWeaver 7.4: https://help.sap.com/nw74

Operations for SAP NetWeaver

Operations Technical

● SAP systems based on SAP NetWeaver 7.5: https://help.sap.com/nw75

Operations Technical

Operations for SAP NetWeaver

● SAP systems based on SAP NetWeaver Application Server for ABAP 7.51 innovation package: https:// help.sap.com/nw

SAP NetWeaver AS for ABAP 7.51 innovation package Operations Technical

Operations for SAP NetWeaver

28

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

● SAP systems based on SAP NetWeaver Application Server for ABAP 7.52: https://help.sap.com/nw

SAP NetWeaver Application Server for ABAP 7.52

Operations Technical Operations for SAP

NetWeaver

Procedure

1. Before you start a system copy, check the minimum kernel patch level required by the support package level of the source system.

It might be necessary to replace the SAP kernel delivered with the installation kit and installed during the installation of the target system by a newer kernel patch level before starting the target system. If you have to replace the delivered SAP kernel, you can do this after the installation of the primary application server instance.

For more information about release and roadmap information around the kernel versions and their relationship to SAP NetWeaver support packages including important notes on downward compatibility and release dates, see the document Understanding Kernel Releases for the SAP NetWeaver AS ABAP at: https://archive.sap.com/documents/docs/DOC-54170

2. Check if canceled or pending update requests exist in the system. If canceled or pending updates exist, you must update these again or delete them from all clients. Proceed as follows: a. Call transaction

SM13

.

b. Delete the default values for the client, user, and time.

c. Choose all update requests.

d. Check if table VBDATA contains any entries. If there are entries, update or delete the corresponding update requests.

e. To check whether this action was successful, call transaction

SE16

for table VBDATA.

3. Set all released jobs from

Released

to

Scheduled

using transaction

SM37

.

You also need to do this for jobs that must run periodically. For more information, see SAP Note 16083 .

To select all jobs (include

start after event

), choose

Job Released Scheduled

4. Adapt the operation mode timetable to make sure that no switching of operating modes takes place while a system is being copied (transaction

SM63

).

5. Write down the logical system names of all clients:

○ If you plan to overwrite an existing system with a system copy, make sure you write down the logical system names of all clients in the system that will be overwritten (transaction

SCC4

).

Since the logical system names will be overwritten, in the event of differences, you must change them back to their original names (as they existed in the system that is overwritten) in the follow-on actions after the system copy.

○ If you create a new system with a system copy (for example, create an upgrade test system), make sure that the logical naming strategy for this new system is consistent with your existing logical system naming convention.

SAP Business Warehouse (BW) only: If you are still in the process of planning your BW system landscape, see SAP Note 184447 for information about how to set up your system landscape, especially for information about system naming.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

C U S T O M E R

29

○ If your system copy is used to replace hardware for the DB server, migrate to a different database system or operating system (that is, source system for the copy is the same as the copy target), no changes to logical system names are required.

6. Before you run the export of the SAP HANA database, check the fragmentation of the rowstore and – if required – defragment it as described in SAP Note 1813245 .

7. Before performing the source system export, make sure that you do the following: a. Delete QCM tables from your source system:

1. Before you delete the QCM tables, ensure the following:

○ The tables are consistent – no restart log or conversion procedure termination must be displayed.

○ The data of the original table can be read.

○ The application programs that use the affected original table run correctly.

2. Call transaction SE14.

3. Choose

Extras Invalid temp. table

All QCM tables that can be deleted are displayed.

4. Mark the tables and delete them.

b. Run report RS_SCRP_D020S_CLEAN to check if there are invalid entries in tables D020S and

DYNPSOURCE. If invalid entries are detected, remove them before running the export. See also SAP

Note 870601 .

8. To avoid stopping the database due to a log directory being full, make sure that the log backup is enabled during the import.

9. Heterogeneous System Copy: If you plan to migrate your database to SAP HANA database, do the following: a. Perform the preparation steps described in SAP Note 1600929 .

b. Perform the following preparation steps:

○ SAP BW only:

Perform the preparation steps described in SAP Note 1600929 .

○ SAP NetWeaver AS for ABAP 7.4 only:

○ For more information about the SAP HANA database migration, check the Administrator's

Guide for your SAP Business Suite application available at:

○ https://help.sap.com/viewer/p/SAP_ERP,_VERSION_FOR_SAP_HANA

Administrator’s Guide

○ https://help.sap.com/viewer/p/

Operations

SAP_CUSTOMER_RELATIONSHIP_MANAGEMENT_FOR_HANA

Installation and

Upgrade Administrator’s Guide

○ https://help.sap.com/viewer/p/SAP_SUPPLY_CHAIN_MANAGEMENT

Application Operations Guide

Operations

○ https://help.sap.com/viewer/p/SAP_SUPPLIER_RELATIONSHIP_MANAGEMENT

Operations Application Operations Guide

○ Perform the steps described in SAP Note

1851549 .

10. Prepare the

media required for the export [page 36] :

a. Prepare the Software Provisioning Manager archive as described in Downloading and Extracting the

Software Provisioning Manager Archive [page 37] .

30

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

b. If you want to use a dedicated kernel, you can specify this on the screen

Use Dedicated Kernel for

System Copy

while performing the export. If you choose this option, you are prompted for the required kernel archives.

For more information, see Downloading Dedicated Kernel Archives for the Export [page 39]

.

3.2 Product-Specific Preparations

FI Customers

● You can perform an additional consistency check by running the job SAPF190 before copying the source system, as well as after copying the target system, and then compare the results. Make sure that no customer data is changed in the meantime. You can do this as follows:

In transaction SAPF190, for classic FI, choose

Accounting Financial Accounting General ledger

Periodic Processing Closing Check/count Reconciliation

.

For a new general ledger, choose

Accounting Financial Accounting General ledger Periodic

Processing Closing Check/count Reconciliation (New)

.

● You can further check consistency by running the jobs listed below before copying the source system, as well as after copying the target system, and then compare the results.

○ RFUMSV00 (tax on sales/purchases)

○ RAGITT01 (asset history sheet)

○ RAZUGA01 (asset acquisitions)

○ RAABGA01 (fixed asset retirements)

Make sure that no customer data is changed in the meantime.

CO Customers

You can perform an additional consistency check by running the report group 1SIP before copying the source system, as well as after copying the target system, and then compare the results. Make sure that no customer data is changed in the meantime.

Caution

Prerequisites for an export:

Before performing an export, make sure that no incremental conversion is in progress.

To test if an incremental conversion is in progress, run transaction

ICNV

. If there are any table entries in table TICNV, an incremental conversion is in progress. In this case, you have the following options:

1. Defer the migration until the incremental conversion has finished.

2. Try to finish the incremental conversion by performing the following steps:

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

C U S T O M E R

31

● If the tables are in state For conversion or in state Done, delete the entries by choosing

Control

Delete Entry

.

● If the tables are in any other state, you have to finish the incremental conversion. Choose Assistant and proceed according to the online documentation.

Caution

Heterogeneous system copy only:

Before you start the export of your source system, make sure that the tables TATGPC and TATGPCA are empty. To do so, use your database utility and delete the contents of these tables with the following statements:

DELETE from TATGPC

DELETE from TATGPCA

If the tables are not empty and you do not delete the contents of these tables you encounter problems while importing the data to your target system because of non-NULL capable fields in these tables.

SAP Business Warehouse

● When planning the copy of an SAP Business Warehouse (BW) system, read SAP Notes

886102 and

1707321 .

● Especially if you want to perform a heterogeneous system copy to another database, make sure that all the data from the Persistent Staging Area (PSA) associated with a 7.X DataSource are extracted and loaded to the Data Targets using Data Transfer Process (DTP) before you perform the database migration.

For more information, see SAP Note 2129192 .

● For special preparations regarding the migration to SAP HANA database, see

Preparing the Migration to an SAP HANA Database [page 32]

3.3 Preparing the Migration to SAP HANA Database

This section provides references to information about how to prepare the migration to SAP HANA database.

Note

SAP Kernel Version 7.38 and higher: Cluster and pool tables are made transparent during the migration to the SAP HANA database. Once you migrate to SAP HANA database, currently there is no automatic way to return back to your source database.

32

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

Prerequisites

Apply SAP Note 1783937 , so that partitioning restrictions are recognized when SQL files are created.

Otherwise, the import of tables with more than 2 billion records will fail.

Unicode Conversion

SAP HANA requires Unicode. Should you have a non-Unicode system, perform a Unicode conversion before the migration or plan a combined migration with Unicode conversion, which is technically also possible. Be aware that R3load requires significantly more CPU time with a combined Unicode conversion, resulting in a reduced number of configurable R3load jobs. For more information, see the Unicode Conversion Overview

Guide available at: https://blogs.sap.com/2009/04/08/unicode-conversion-overview-guide/

The Distribution Monitor can optimize the downtime of a Unicode conversion by distributing the R3load workload to several machines – nevertheless, the Distribution Monitor is not released for SAP HANA, so it cannot be used in a combined migration and Unicode conversion procedure, but only if you convert to

Unicode as separate activity before the migration. Because the approach with Distribution Monitor increases the complexity of the conversion, use it only if really needed. For more information, see:

● SAP Note

855772 (Distribution Monitor)

● SAP Note

1001383 (Distribution Monitor - Known problems and fixes)

● User guide that is part of the tool archive (DISTMON.SAR)

● SAP Note

989116 (Distribution Monitor: Troubleshooting Guide)

Migration Tool Versions

Always use latest versions of the migration tools:

● R3* tools (R3load, R3ldctl, R3szchk, R3ta):

○ An up-to-date version of the load tools - such as R3load, R3szchk, R3ldctl, SAPuptool is available in the Software Provisioning Manager archive

(SWPM10SP

<Support_Package_Number> _ <Version_Number> .SAR). They are automatically used by the installer if you use Unicode kernel version 7.40 or higher. For more information, see

Downloading and Extracting the Software Provisioning Manager Archive [page 37]

.

If you want to use the latest version of the tools contained in the kernel media, you can get them from: https://launchpad.support.sap.com/#/softwarecenter

Support Packages and Patches A - Z

Index K SAP KERNEL

<VERSION><Release><Platform>

.

○ For more information, see the blog Migration to SAP HANA: SAP Kernel Update for the Migration in the

SAP Community Network at: https://blogs.sap.com/2013/09/30/migration-to-sap-hana-sapkernel-update-for-the-migration/

○ Verify that the versions are compatible. R3* tools must fit the kernel version of your SAP system.

● SAPCAR:

You can get the latest version from the tools from: https://launchpad.support.sap.com/#/softwarecenter

Support Packages and Patches A - Z Index S SAPCAR

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

C U S T O M E R

33

Kernel

Use the latest kernel media for the installer as listed in SAP Note 1680045 (

Release Note for software provisioning manager 1.0

Kernel media for SWPM*

). Make sure to use the same kernel version both for

export and import. For more information, see General Technical Preparations [page 28] .

For more information about release and roadmap information around the kernel versions and their relationship to SAP NetWeaver support packages including important notes on downward compatibility and release dates, see the document Understanding Kernel Releases for the SAP NetWeaver AS ABAP at: https:// archive.sap.com/documents/docs/DOC-54170

Creating DDL Statements

Before you start the export, make sure to run the report SMIGR_CREATE_DDL that generates DDL statements for the migration.

For more information, see Generating DDL Statements [page 50]

.

Table Splitting Preparation

For more information about how to prepare table splitting, see

Preparing the Table Split [page 52]

Package Splitting

Package splitting is activated by default. Do not deactivate it.

For more information about how to prepare table splitting, see

Preparing the Package Split [page 56]

Housekeeping

Before the migration, delete and archive obsolete data from tables that show the largest growth in data volume. For more information, see:

● The Data Management Guide for SAP Business Suite available in SAP Service Marketplace at: https:// support.sap.com/en/solution-manager/processes-72.html

Processes Data Volume

Management

● SAP Note

679456 (Reducing data volume before Unicode conversion).

If not instructed otherwise, carry out the corresponding activities to reduce the data volume during system uptime.

34

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

Implement SAP Note 1659622 in the source system. It provides the ABAP report

SMIGR_BIG_ROW_STORE_TABS. This report can be used to identify large tables that will be stored as row store tables in SAP HANA. A small memory footprint of the row store is beneficial to minimize the database startup time.

Especially for SAP Business Warehouse (SAP BW), you can profit from an automated housekeeping, offered as task list of the ABAP task manager for lifecycle management automation. For more information, see SAP

Note 1829728 (BW Housekeeping Task List).

Further Preparations

● Read SAP Note

1775293 (Migration/system copy to SAP HANA using the latest SWPM 1.0)

Note

If you want to get automatic notifications about changes to this SAP Note, you can configure to receive email notifications on this page in SAP Community Network.

● R3szchk calculates space requirements on the target database for ABAP tables and indexes and rough estimation of overall size for target database. Per default, R3szchk gets executed by the installer. The result is an EXT and a DBSIZE.XML file.

Note

If the target database is SAP HANA, the DBSIZE.XML file is not used as the sizing is done already by

SAP’s sizing tools for SAP HANA.

If R3szchk is very slow, check SAP Note 1047369 .

● Request or generate a migration key. For more information, see https://support.sap.com/en/mysupport/keys.html

.

● Before the export, run the reports SDBI_CLUSTER_CHECK_PERFORM and SDBI_CHECK_BCD_NUMBERS.

This avoids issues during the export and import because of corrupt or initial cluster records or decimal numbers. For more information, see SAP Note 1784377 (Checking pool tables and cluster tables).

● Avoid more than one statistics server for your SAP HANA database. Otherwise, the import step can fail because of a “standby” statistics server. Remove any configured standby statistics servers before the import.

● Perform a test run of the system copy procedure to calculate downtimes of your source system based on experiences made during the test run. Adapt the general process to your system and environment. For

more information, see Creating A System Copy Plan [page 19]

.

● Order and install a new SAP license. For more information, see

Various Planning Aspects and Parameters

[page 19] .

● Prepare the source system as described in

General Technical Preparations [page 28]

and

Product-

Specific Preparations [page 31]

. For example, check for canceled or pending update requests and operation mode

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

C U S T O M E R

35

SAP Business Suite Applications

For more information about the overall migration process, see SAP Note 1785057 .

To ensure a successful migration, you should perform the following preparation steps:

1. If there are tables with high data volume in your source database where the number of records exceeds a certain limit, partitioning of these tables in your SAP HANA database is required. For more information, see SAP Note 1783937 .

2. Note that for both SAP tables and customer tables, cluster tables will be automatically transformed into transparent tables during the migration. Also pool tables will be converted into transparent tables. For more information about which pool tables are converted into transparent tables and when, see SAP Note

1785057 .

To verify that this transformation will work properly during the migration, the source database should be checked. For more information, see SAP Note 1784377 .

For example, cluster or pool tables that contain invalid values cannot be migrated.

Check if there is custom code (customer development) in your system that can directly access tables that can be resolved. Such code is no longer valid.

Note that applications may not rely on implicit sorting of result sets of accesses to former pool and cluster tables that have been transformed to transparent tables. For more information, see SAP Note 1785057 .

SAP Business Warehouse

● Perform the preparation steps described at:

○ The document Best Practice Guide - Classical Migration of SAP NetWeaver AS ABAP to SAP HANA available at: https://archive.sap.com/documents/docs/DOC-47657

○ https://blogs.sap.com/2016/10/11/software-application-lifecycle-management-sap-bw/

Additional Information about the Lifecycle Management with SAP NetWeaver BW 7.x

SAP

NetWeaver 7.3 - BW Systemcopy ABAP

○ https://rapid.sap.com/bp/#/RDS_RDBMS_4_BW

Solution Deployment: Configuration Guide of the SAP Rapid Deployment Solution "Rapid Database Migration of SAP NetWeaver BW to SAP HANA"

● Perform the preparation steps described in SAP Note

1600929 .

3.4 Preparing the Media Required for Performing the

Export

For performing the export on the source system, you only need to download and extract the Software

Provisioning Manager 1.0 archive which contains the installer.

For the media required for performing the target system installation, see section Preparing the installation

Media in the installation guide for the operating system platform and database of your target system at http:// support.sap.com/sltoolset

System Provisioning System Copy Option of Software Provisioning Manager

System Copy Guides - Installing the Target System

.

36

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

Note

The signature of media is checked automatically by the installer during the

Define Parameters

phase while processing the

Media Browser

screens. As of now the installer only accepts media whose signature has been checked. See also the description of this new security feature in SAP Note 2393060 .

Related Information

Downloading and Extracting the Software Provisioning Manager Archive [page 37]

Downloading Dedicated Kernel Archives for the Export [page 39]

3.4.1 Downloading and Extracting the Software Provisioning

Manager Archive

You must always download and extract the Software Provisioning Manager 1.0 archive from the SAP Software

Download Center because you must use the latest version.

Context

You require the SAPCAR tool to be able to unpack and verify software component archives (*.SAR files). *.SAR is the format of software lifecycle media and tools that you can download from the SAP Software Download

Center. For more information about how to get this tool, see the Procedure section below.

An up-to-date version of the load tools - such as R3load, R3szchk, R3ldctl, SAPuptool - which were available so far only in the SAPEXEDB.SAR archive of the kernel media, has now been made available in the

Software Provisioning Manager archive

(SWPM10SP

<Support_Package_Number> _ <Version_Number> .SAR), in a sub-archive named

LOADTOOLS.SAR, located in the COMMON/LOADTOOLS folder. For a system copy using Unicode kernel version

7.40 or higher, the load tools from the SWPM10SP

<Support_Package_Number> _ <Version_Number> .SAR are used automatically instead of the loadtools available in the SAPEXEDB.SAR archive of the kernel media.

There is no action required from your side, the installer uses the relevant loadtools automatically once you run it from the extracted SWPM10SP

<Support_Package_Number> _ <Version_Number> .SAR archive.

Procedure

1. Download the latest version of the Software Provisioning Manager 1.0 archive

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR from:

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

C U S T O M E R

37

https://launchpad.support.sap.com/#/softwarecenter

SUPPORT PACKAGES & PATCHES By

Alphabetical Index (A-Z) S SOFTWARE PROVISIONING MANAGER

2. Get the latest version of the SAPCAR tool on the host where you want to run the installer: a. Go to https://launchpad.support.sap.com/#/softwarecenter

SUPPORT PACKAGES &

PATCHES

and search for “

sapcar

”.

b. Select the archive file for your operating system and download it to an empty directory.

c. Rename the executable to

sapcar.exe

.

For more information about SAPCAR, see SAP Note 212876 .

3. Using the latest version of SAPCAR, you can verify the signature of the downloaded

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR archive as follows: a. Get the latest version of the SAPCRYPTOLIB archive to your installation host as follows:

1. Go to https://launchpad.support.sap.com/#/softwarecenter

SUPPORT PACKAGES &

PATCHES

and search for “

sapcryptolib

”.

2. Select the archive file for your operating system and download it to the same directory where you have put the SAPCAR executable.

3. Use the following command to extract the SAPCRYPTOLIB archive to the same directory where you have put the SAPCAR executable:

sapcar –xvf sapcryptolibp_84…sar –R <target directory>

4. Download the Certificate Revocation List from

https://tcs.mysap.com/crl/ crlbag.p7s

and move it into the same directory.

b. Verify the signature of the downloaded

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR archive by executing the following command:

Note

Check SAP Notes 2178665 and 1680045 whether additional information is available.

/<Path to SAPCAR>/sapcar -tvVf <Path to Download Directory>/

SWPM10SP<Support_Package_Number>_<Version_Number>.SAR -crl<file name of revocation list>

4. Unpack the Software Provisioning Manager archive to a local directory using the following command:

/<Path to SAPCAR>/sapcar -xvf <Path to Download Directory>/

SWPM10SP<Support_Package_Number>_<Version_Number>.SAR <Path to Unpack Directory>

Note

Make sure that all users have read permissions for the directory where you want to unpack the installer.

Caution

Make sure that you unpack the Software Provisioning Manager archive to a dedicated folder. Do not unpack it to the same folder as other installation media.

38

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

3.4.2 Downloading Dedicated Kernel Archives for the Export

If you want to use a dedicated kernel for the database export , you must download the SAPEXE.SAR and

SAPEXEDB.SAR for your operating system, kernel release and database beforehand.

Context

Using this feature, you no longer have to do kernel updates in your systems just for the purpose of being able to copy it. Instead, the installer provides you the option to use a different kernel just for the purpose of system copy. This means you do not provide a kernel to be installed but only to be used by the installer for performing the export. For this option, you have to provide a separately downloaded SAPEXEDB.SAR and SAPEXE.SAR archive.

Procedure

1. Go to http://support.sap.com/swdc

Software Downloads SUPPORT PACKAGES & PATCHES

By Category Additional Components SAP Kernel

<Version>

2. Choose the required package:

Caution

○ Make sure that you always choose SAPEXE

<Version> .SAR, SAPEXEDB <Version> .SAR of the same SAP kernel release and extension:

Example

○ If SAPEXE

<Version> .SAR is of version 7.42 EXT, then SAPEXEDB <Version> .SAR must also be of version 7.42 EXT.

○ If SAPEXE

<Version> .SAR is of version 7.45, then SAPEXEDB <Version> .SAR must also be of version 7.45.

○ SAPEXE

<Version> .SAR

SAP KERNEL

<Version> <UC | NUC> <Operating System>

#DATABASE

INDEPENDENT

Note

SAP KERNEL

<Version> <NUC>

is only available for SAP systems based on SAP NetWeaver 7.4 or lower

○ If you want to install an SAP system based on SAP NetWeaver 7.5, you can only choose 7.45

UNICODE for

SAP KERNEL

<Version>

.

○ If you want to install an SAP system based on SAP NetWeaver 7.4, you can choose either 7.45 or

7.42 for

SAP KERNEL

<Version>

.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

C U S T O M E R

39

○ If you want to install an SAP system based on SAP NetWeaver 7.3 including EHP1 or lower, choose

7.21 EXT for

SAP KERNEL

<Version>

○ SAPEXEDB

<Version> .SAR

SAP KERNEL

<Version> <UC | NUC> <Operating System>

#DATABASE

INDEPENDENT

Note

SAP KERNEL

<Version> <NUC>

is only available for SAP systems based on SAP NetWeaver 7.4 or lower

○ If you want to install an SAP system based on SAP NetWeaver 7.5, you can only choose 7.45

UNICODE for

SAP KERNEL

<Version>

.

○ If you want to install an SAP system based on SAP NetWeaver 7.4, you can choose either 7.45 or

7.42 for

SAP KERNEL

<Version>

.

○ If you want to install an SAP system based on SAP NetWeaver 7.3 including EHP1 or lower, choose

7.21 EXT for

SAP KERNEL

<Version>

40

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Preparations

4 Database Independent System Copy

With the installer, you can export and import your database content in a database-independent format. The installer uses the R3load tool for exporting and importing the database content .

R3load generates a database export of all SAP objects that are defined in the ABAP Dictionary, including the configuration and components in the file system.

Note

Make sure that you have the most recent version of the R3load tool , which you can download from https://launchpad.support.sap.com/#/softwarecenter .

An up-to-date version of the load tools - such as R3load, R3szchk, R3ldctl, SAPuptool - which were available so far only in the SAPEXEDB.SAR archive of the kernel media, has now been made available in the

Software Provisioning Manager archive

(SWPM10SP

<Support_Package_Number> _ <Version_Number> .SAR), in a sub-archive named

LOADTOOLS.SAR, located in the COMMON/LOADTOOLS folder. For a system copy using Unicode kernel version 7.40 or higher, the load tools from the

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR are used automatically instead of the loadtools available in the SAPEXEDB.SAR archive of the kernel media. There is no action required from your side, the installer uses the relevant loadtools automatically once you run it from the extracted

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR archive.

Note

Declustering / depooling of ABAP tables is supported for SAP systems based on SAP NetWeaver 7.4 SP03 and higher. For more information, SAP Note 1892354 .

Constraints

R3load Restrictions

● The installer generates a database dump of all SAP objects that are defined in the ABAP Dictionary

(R3load). Other objects are not exported by the installer.

● For a consistent database export, no transactions on export-relevant database objects are allowed during the export. Otherwise, the export has to be restarted. Therefore, we recommend that you shut down the

SAP system (excluding the database!) for the export. The database must still be running.

● Changes to database objects that cannot be maintained in the ABAP Dictionary (transaction

SE14

), such as the distribution of tables over several tablespaces or dbspaces, are lost after the system copy.

● Indexes longer than 18 characters are not allowed on the database to be exported.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

41

Multiple Applications in SAP HANA Systems

For more information about multiple applications in SAP HANA systems, see SAP Notes 1826100 and

1661202 .

If the database configuration of your database is stored in the file system, we recommend you to back up these configuration files before deleting the database.

Splitting STR Files

● During the standard system copy process, all tables of the SAP system are grouped into packages, whereby all tables with the same data class belong to the same package. The processing unit for one unload/load process is a package. The packages differ in number and size of contained tables, resulting in varying unload/load runtimes. The overall runtime can be reduced by creating packages of the same size, that is, creating packages with a similar processing time. You can achieve this by splitting the default packages (one package per data class) into more and smaller pieces.

● There are several options of how to split packages. For a detailed description of the options, see the

F1 help about the parameters prompted on the

Split STR Files

screen while running the installer to export the database. The options can be used separately or – when using the new Java based splitting tool – combined.

● “Splitting of STR Files” is part of the “Advanced Export Parameters” and is enabled by default. If you select the splitting option (if you did not already perform some tests before), using the splitting tool parameters selected by the installer is a good starting point.

Caution

If you want to split STR files, you must first create the EXT files for the target database system. You can find the EXT files in your export dump directory, subdirectory DB/

<DBTYPE>

, for example DB/ORA.

4.1 System Copy Procedure

This section describes the system copy procedure using R3load.

Prerequisites

Specify an empty directory with sufficient disk space for the export dump on the host where you want to perform the export. Make sure that this directory does not contain any files from any previous system copy exports. If you cancelled a system copy export and want to perform the export again, make sure that you remove all files from the previously cancelled export before you start the export from scratch.

Note

As a result of the export, a dump of the database schema belonging to the SAP system is stored in the export directory. During the entire life-cycle of this export dump, you must ensure adequate protection from unauthorized read access and modification of the data exported. Therefore, you now have the option

to specify a restricted access level for the export directory when you run the installer [page 63]

to perform

42

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

the export. You are enabled to specify that only the

<sapsid> adm executing the export has permission to read and modify the database export.

Process Flow on the Source System (Export)

When performing the export, the installer creates a migration export media which contains the data of the exported system, and which you use to install the target system.

The following figure shows the export options and the resulting output files.

Figure 1: Overview on Export Options

Follow the sequence of steps described below for a:

● Standard system

○ Standard system – Performing the Export on the Source System

○ Standard system – Setting Up the Target System

● Distributed system or high-availability system

○ Distributed system or high-availability system – Performing the Export on the Source System

○ Distributed system or high-availability system – Setting Up the Target System

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

43

Standard System – Performing the Export on the Source System

To perform the export for a standard system, proceed as follows on the standard system host:

1. Heterogeneous system copy only: Generate the migration key at https://support.sap.com/migrationkey

, entering the installation number of your source system when prompted.

2. Perform the export on the standard system host:

1. Make sure that the QCM tables are deleted from your system as described in

General Technical

Preparations [page 28] .

2.

Generate DDL statements [page 50] .

3.

Prepare the system for table splitting [page 52] (optional).

4. You run the installer [page 63]

to prepare the source system for the export.

On the

Welcome

screen, choose the

Export Preparation

option.

Note

You must run this option if you want to perform export processes in parallel with import processes during the system copy. Otherwise this step is optional.

5. If required, you

prepare parallel export and import [page 58]

.

6.

Start the installer [page 63] from an application server instance host to export the database

instance.

Note

If you want to run a system copy with parallel export/import using the Migration Monitor, for example with the socket option, and the target database is declustered, start the installer with command line option

SUPPORT_DECLUSTERING=false

.

On the

Welcome

screen, choose option

Database Instance Export

.

Note

If you are running a system copy with parallel export/import using the Migration Monitor and the target database is declustered - that is you started the installer with command line option

SUPPORT_DECLUSTERING=false

as described above - add the following load options parameter in the screen for advanced load configuration (

SAP System Advanced Load Configuration

screen:

-sort_cluster

You can check the parameter within the import_monitor_cmd.properties file located in the installation directory. The relevant entry is taskArgs=-sort_cluster.

Note

○ If parallel export and import has been prepared, ensure the following:

○ You choose

Parallel Export and Import

for the database instance ABAP export on the

SAP

System Database Export

screen.

○ If you decided to transfer the export directory instead of sharing it to the target host, make sure that you transfer it while you are processing the

Database Instance Export

option, after you have stopped the source system and before you proceed with the export procedure.

44

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

○ If table splitting for ABAP tables has been prepared before the data export via the installer, the installer export automatically does the following:

○ It forces package splitting.

○ It forces the use of an input file for table splitting.

○ It uses the existing whr.txt file from the dump directory as default for the package splitter input file.

You only have to execute the following steps if you intend to

run the export on additional hosts [page

27] :

1. If you want to use additional hosts for the export, you have to mark the

Use Additional Export

Hosts

checkbox on the

SAP System Database Export

screen.

Some additional screens now appear where you can specify the additional hosts on which you intend to run the export and the size of the packages each export run is to contribute to the complete export dump.

2. Follow the instructions on these screens and then finalize the export on the database instance host.

Note

The total number of jobs should only be the number of jobs which are processed on the current host.

As a result, the first part of the export dump is created in the export directory.

3. Mount the export directory on each of the additional hosts on which you want to perform the export.

In addition, you have to mount the SGN (signal) directory if you run the export/import in parallel.

For more information about the SGN directory, see the documentation of the netExchangeDir option in the

Migration Monitor Configuration [page 112]

documentation.

4.

Run the installer [page 63]

on each of the additional hosts on which you want to perform the export.

On the

Welcome

screen, choose the system copy option

Database Instance Export on Additional

Hosts

.

Follow the instructions on the screens and finalize the export on the additional hosts.

Note

If R3load processes fail due to an error, solve the problem, and perform the restart as described in

Restarting R3load Processes [page 80]

.

3. If you want to perform

table comparison with Software Update Manager (SUM) [page 138] , proceed as

follows:

1. Stop all instances of the source system once the export has completed.

2.

Run table comparison [page 140] for the source system.

3. You can restart the instances of the source system.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

45

Standard System – Setting Up the Target System

You use the installer to set up the target system and import the database files that you have exported from the source system.

Note

This system copy guide describes only the source system export in full detail. As for the installation of the target system, this system copy guide describes only the system copy-specific steps in section

Setting Up the Target System [page 82]

, but refers for all steps that are identical with a new system installation to the appropriate operating system and database-specific installation guide available at http:// support.sap.com/sltoolset

System Provisioning Installation Option of Software Provisioning

Manager

.

You perform the following steps on the standard system host:

Caution

You must choose parameter mode

Typical

when performing a system copy with database tools.

Note

The SAP HANA database is part of the SAP HANA appliance. It is pre-installed by SAP partners before the installation of your SAP system. Therefore, the SAP HANA database instance always runs on a separate host, even if your SAP system is a standard system.

Only valid for 'Platform': Linux

As of Software provisioning manager 1.0 SP06 (SL Toolset 1.0 SP11), you can also install SAP systems based on SAP NetWeaver Application Server for ABAPsame host as the SAP HANA database, without applying additional environment settings. For more information, see SAP Note 1953429 .

End of 'Platform': Linux

1. You prepare the standard system host for the installation of your target system as described in the installation guide.

2. If you have already prepared the export [page 58] on the source system because you want to perform

export processes in parallel to import processes, you perform the following steps:

1. If you use the

FTP Exchange

option during the export (transfer type

FTP

on the

SAP System > Data

Transfer Parameters for Export

screen and communication type

Exchange Directory

on the

SAP

System > Communication Parameters for Export

screen), make sure that you have transferred all files

that have been generated in step Preparing Parallel Export and Import [page 58] on the source

system.

2. You install the target system.

For more information, see Installing the Target System [page 84]

.

If you did not prepare the export on the source system, you install the target system.

For more information, see

Installing the Target System [page 84]

3. If required, on the host or hosts of the application server instance, you install further additional application server instances as described in the installation guide.

46

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

Distributed System or High-Availability System – Performing the Export on the Source System

To perform the export for a distributed system or a high-availability system, proceed as follows:

1. Heterogeneous system copy only: Generate the migration key at https://support.sap.com/migrationkey

, entering the installation number of your source system when prompted.

2. You perform the database instance export.

We recommend that you perform this step on the database instance host. If your source database is SAP

HANA, you perform this step on any application server instance host.

1. Make sure that the QCM tables are deleted from your system as described in

General Technical

Preparations [page 28] .

2.

Generate DDL statements [page 50] .

3. You run the installer [page 63]

to prepare the source system for the export.

On the

Welcome

screen, choose the

Export Preparation

option.

Note

You must run this option if you want to perform export processes in parallel with import processes during the system copy. Otherwise this step is optional.

4.

Prepare the system for table splitting [page 52] (optional).

5. If required, you

prepare parallel export and import [page 58]

.

6.

Run the installer [page 63] to export the database instance.

Note

If you want to run a system copy with parallel export/import using the Migration Monitor, for example with the socket option, and the target database is declustered, start the installer with command line option

SUPPORT_DECLUSTERING=false

On the

Welcome

screen, choose the system copy option

Database Instance Export

.

Note

If you are running a system copy with parallel export/import using the Migration Monitor and the target database is declustered - that is you started the installer with command line option

SUPPORT_DECLUSTERING=false

as described above - add the following load options parameter in the screen for advanced load configuration (

SAP System Advanced Load Configuration

screen:

-sort_cluster

You can check the parameter within the import_monitor_cmd.properties file located in the installation directory, in the taskArgs=-sort_cluster entry.

Note

○ If parallel export and import has been prepared, ensure the following:

○ You choose

Parallel Export and Import

for the database instance ABAP export on the

SAP

System Database Export

screen.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

47

○ If you decided to transfer the export directory instead of sharing it to the target host, make sure that you transfer it while you are processing the

Database Instance Export

option, after you have stopped the source system and before you proceed with the export procedure.

○ If table splitting for ABAP tables has been prepared before the data export via the installer, the installer export automatically does the following:

○ It forces package splitting.

○ It forces the use of an input file for table splitting.

○ It uses the existing whr.txt file from the dump directory as default for the package splitter input file.

You only have to perform the following steps if you intend to run the

run the export on additional hosts

[page 27] :

1. If you want to use additional hosts for the export, you have to mark the

Use Additional Export

Hosts

check box on the

SAP System Database Export

screen.

Some additional screens now appear where you can specify the additional hosts on which you intend to run the export and the size of the packages each export run is to contribute to the complete export dump.

2. Follow the instructions on these screens and then finalize the export on the database instance host.

Note

The total number of jobs should only be the number of jobs which are processed on the current host.

As a result, the first part of the export dump is created in the export directory.

3. Mount the export directory on each of the additional hosts on which you want to perform the export.

In addition, you have to mount the SGN (signal) directory if you run the export/import in parallel.

For more information about the SGN directory, see the documentation of the netExchangeDir option in the

Migration Monitor Configuration [page 112]

documentation.

4.

Run the installer [page 63]

on each of the additional hosts on which you want to perform the export.

On the

Welcome

screen, choose the system copy option

Database Instance Export on Additional

Hosts

.

Follow the instructions on the screens and finalize the export on the additional hosts.

Note

If R3load processes fail due to an error, solve the problem, and perform the restart as described in

Restarting R3load Processes [page 80]

.

3. If you want to perform

table comparison with the Software Update Manager (SUM) [page 138] , proceed

as follows:

1. Stop all instances of the source system once the export has completed.

2.

Run table comparison [page 140] for the source system.

3. You can restart the instances of the source system.

48

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

Distributed System or High-Availability System – Setting Up the Target

System

You use the installer to set up the target system and import the database files that you have exported from the source system.

Note

This system copy guide describes only the source system export in full detail. As for the installation of the target system, this system copy guide describes only the system copy-specific steps in section

Setting Up the Target System [page 82]

, but refers for all steps that are identical with a new system installation to the appropriate operating system and database-specific installation guide available at http:// support.sap.com/sltoolset

System Provisioning Installation Option of Software Provisioning

Manager

.

In the following, we refer to this guide as “installation guide”.

Perform the following steps on the relevant installation hosts of your target system:

1. You prepare the ASCS instance host, the database instance host, and the host of the primary application server instance for the installation of the corresponding instances of your target system as described in the installation guide.

2. You install the ASCS instance for the target system as described in the installation guide.

3. You perform the following steps from any application server instance host:

○ If you have already

prepared the export [page 58]

on the source system because you want to perform export processes in parallel to import processes, you perform the following steps:

1. If you use the

FTP Exchange

option during the export (transfer type

FTP

on the

SAP System >

Data Transfer Parameters for Export

screen and communication type

Exchange Directory

on the

SAP System > Communication Parameters for Export

screen), make sure that you have

transferred the files, which have been generated in step Preparing Parallel Export and Import

[page 58] on the source system.

2. You install the database instance of the target system.

For more information, see

Installing the Target System [page 84] .

○ If you did not prepare the export on the source system, you install the database instance of the target system.

For more information, see Preparing Parallel Export and Import [page 58] and

Installing the Target

System [page 84]

.

4. On the host of the primary application server instance, you install the primary application server instance of the target system.

5. If required, on the host or hosts of the additional application server instance, you install further additional application server instances as described in the installation guide.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

49

4.1.1 Generating DDL Statements

To migrate nonstandard database objects, you need to generate DDL statements using the ABAP report

SMIGR_CREATE_DDL.

Prerequisites

● Only valid for SAP NetWeaver 7.4 systems on SAP HANA (not for SAP BW 7.3x and SAP BW 7.4): If you want to migrate your system to a distributed SAP HANA database, make sure that you also consider the prerequisites as listed in SAP Note 1781986 (Business Suite on SAP HANA Scale Out), such as running report SHDB_GROUP_TABLES_LOAD_BASED in order to classify tables in the context of the migration. You must execute the report before the migration, in particular before running report

SMIGR_CREATE_DDL.

● In addition, make sure that you applied all SAP Notes referenced in SAP Note

1921023 in the source system. Especially for migrations to SAP BW on SAP HANA, also apply the SAP Notes listed in the attachment REQUIRED_CORRECTION_NOTES.TXT of SAP Note 1908075 . These SAP Notes contain corrections and enhancements to SMIGR_CREATE_DDL, such as:

○ Rowstore list:

○ For SAP NetWeaver 7.3 or 7.3 EHP1, the file rowstorelist.txt is used to distinguish between row-store and column-store packages, which can get created via an additional option of the report

SMIGR_CREATE_DDL.

○ For SAP NetWeaver 7.4, corresponding information is stored in DDIC instead of rowstorelist.txt, so no action is required.

○ Table list with estimated record count:

○ SMIGR_CREATE_DDL creates a file HDB_ESTIMATES.TXT or ESTIMATED_ROW_COUNT.TXT that contains a list of all relevant tables and the estimated number of rows per table. This information is used during migration into scale-out systems after the initial table creation and before the actual load of data. At that point, the installer performs an initial landscape redistribution of the empty tables. The estimated record counts are used in this step to ensure an equal distribution of data across the index server slave nodes.

○ The blog SAP HANA Landscape Redistribution with SP6 at http://scn.sap.com/community/hanain-memory/blog/2013/09/03/sap-hana-landscape-redistribution-with-sp6 provides additional information on table placement and landscape redistribution.

● For migrations into scale-out systems:

○ Follow the recommendations provided in SAP Note

1908075 (set database parameters, maintain

entries in control table for table placement, grant authorizations).

○ Check SAP Note

1958216 (HANA landscape redistribution configuration) for revision-specific parameter settings.

● For partitioning, make sure that SAP Note

1783937 (SMIGR_CREATE_DDL Enhancement for Suite on

HANA) is applied, so that partitioning restrictions are recognized when SQL files are created (that is, large tables get partitioned during the migration). Otherwise, the import of tables with more than 2 billion records (German: 2 Mrd.) will fail.

● If you want to migrate an SAP Business Suite system to a distributed SAP HANA database, see SAP

Note 1899817 (Suite on distributed HANA database - table redistribution).

50

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

Context

You must perform this procedure before starting the installer.

For additional database-specific information, see also SAP Note 888210 .

Procedure

1. Log on to the system as a system administrator in a productive client.

2. Call transaction SE38 and run the program SMIGR_CREATE_DDL.

3. Select the target database. Depending on the database manufacturer, you might need to select the database version. The value help supports you in selecting the database version.

Note

Only enter a database version that is available in the value help.

4. You are able to select

Unicode Migration

if you also wish to perform a Unicode system copy (from Unicode to Unicode) or a Unicode conversion (from non-Unicode to Unicode).

5. Specify an empty working directory to which the files generated by the report are to be written.

6. If required, you can restrict the generation of DDL statements to specific table types or individual tables.

7. Execute the program.

The DDL statements are generated and are written to the specified directory.

Note

Ensure that the user

<sapsid> adm of the source system has write access and the user <sapsid> adm of the target system has read access to the directory with the generated SQL files.

From there, the installer copies them to the

<Export_Dump_Directory> /ABAP/DB export directory.

Caution

If no database-specific objects exist in the database, no SQL files will be generated. As long as the report terminates with status

Successfully

, this is not an error.

4.1.2 Using a Dedicated Kernel for the Export

As a customer running a productive system, you are sometimes confronted with kernel patches that are required for an ABAP system copy. Since you do not want to change the kernel for your productive landscape, you would like to be able to use a dedicated kernel just for software lifecycle activities for the system, whereas the system itself is to remain unchanged. During the system copy export, while processing the

Use Dedicated

Kernel for System Copy

screen, you can specify that you want to use a dedicated kernel. Having chosen this

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

51

option, on the next screen you are prompted for SAP kernel archives that you want to use for the export itself -

SAPEXE.SAR and SAPEXEDB.SAR. The installer then uses these archives instead of those installed in the source system for running the export.

Related Information

Preparing the Media Required for Performing the Export [page 36]

System Copy Procedure [page 42]

4.1.3 Preparing the Table Split

The R3ta tool processes large tables. Instead of exporting/importing one table with one R3load process, the table is processed in, for example, 10 entities.

Prerequisites

● For prerequisites, see SAP Note

1783927 (Prerequisites for Table Splitting with target HANA database).

● We recommend that you perform a test run to identify the tables with the longest runtime, as not always the largest tables require the longest runtime. To get statistical data about runtimes, use Migtime during the export and import (for more information, see SAP Note 784118 ).

● Otherwise, create a list of the largest tables in the database before the export to identify candidates for table splitting (by using transaction DBACOCKPIT or DB02).

● For using the R3ta tool, consider the following:

○ The installer offers a corresponding option in the export dialog – see below for more information.

○ Under certain conditions, it is recommended that you create additional temporary indexes on the column used in the WHERE condition. Depending on the database, this may not be feasible during productive operation because of time and table locking.

○ In contrast to previous statements, you can also use database-specific splitters, not only the generic

R3ta.

○ As for all R3* tools, always use the latest version of R3ta. Using an outdated version of R3ta increases your risk of receiving incomplete WHR files, which can cause data corruption.

○ If parallel processing is not optimal or if the single packages are serially processed, the complete processing time for one table can increase when using WHERE conditions.

○ The export and import must be performed with Migration Monitor if the table splitting feature is used.

○ Some platforms allow the creation and usage of an R3ta_hints.txt file, with which you can instruct

R3ta to use specific columns of a table to create a WHERE condition. For more information, see section

Using Hints.

If you plan to use R3ta_hints.txt, check whether it contains a valid column for the table that you want to split. You can reduce the runtime of R3ta significantly by choosing a table column with a good selectivity. If no field is provided, a selectivity analysis has to be performed over several columns, which will increase the overall runtime of the splitting.

52

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

Context

Each entity can be processed by different R3load processes. The advantages of splitting the tables are:

● Large tables are processed in smaller packages. If the export or import of a table aborts with an error, only the processing of the package where the error occurred has to be repeated and not for the complete table.

● The export and import of one table can be performed in parallel by starting several R3load processes to work on some packages in parallel.

● The export and import has to be performed with the Migration Monitor when the table splitting feature is used. For more information about the Migration Monitor, see

R3load Procedures Using the Migration

Monitor [page 111] .

Restrictions

● Only tables that are described in the SAP dictionary can be split.

● The following tables cannot be split:

○ DDNTF

○ DDNTF_CONV_UC

○ DDNTT

○ DDNTT_CONV_UC

○ DDLOG (is never copied, but created empty in the target system)

○ REPOLOAD (is never copied, but created empty in the target system)

● Parallel data export of a table is supported by all database platforms but not parallel data import. When the target database platform does not support the parallel data import, the Migration Monitor has to be configured in the way that the data import processes the packages are sequentially. For more information, see Processing Split Tables.

Procedure

1. Create a file that contains lines of the form

<table> % <nr_of_splits>

for all tables to be split.

Oracle PL/SQL splitter only: Use the form

<table> % <nr_of_splits> ; <rowid_or_column>

. For more information about the Oracle PL/SQL splitter, see SAP Note 1043380 .

Caution

The tables listed in this file have to appear in alphabetical order!

2. Start the installer as described in

Running the Installer to Perform the Export [page 63] .

3. On the Welcome screen, choose

<Product> <Database>

System Copy Source System Based on

<Technical_Stack>

Table Splitting Preparation

.

4. Follow the instructions on the installer screens and enter the requested parameters, including the

<SAPSID>

, the file that contains the split information, the export directory, and the number of parallel

R3ta jobs.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

53

Caution

The specified path to the export directory must not contain blanks!

5. After you have entered all requested input parameters, the installer displays the

Parameter Summary

screen. This screen shows both the parameters that you entered and those that the installer set by default. If required, you can revise the parameters before starting the table split.

6. To start the table split, choose

Start

.

Now the *.WHR files and the whr.txt file are created in the export directory.

Caution

When doing a code page conversion (non-Unicode

→ Unicode; 4102 ↔ 4103), make sure not to use a

WHERE condition with the

PAGENO

column included. If the

PAGENO

column is included in the WHERE condition, repeat the table splitting – either with different splitting parameters or by defining a suitable column for this table using the R3ta_hints.txt.

7. Check in the export directory

<Export_Dump_Directory> /ABAP/DATA if *.WHR files have been created for all tables that are to be split.

○ If no *.WHR files could be produced for some of these tables, create fewer packages for these tables:

1. Create a new, empty installation directory.

2. Define a new, empty export dump directory

<Temporary_Dump_Directory>

.

3. Run the

Prepare Table Splitting

service again and provide an input file that contains only the missing tables with a lower number of packages for each defined table.

○ If the *.WHR files have been created for the missing tables, merge these results with the results from the first

Prepare Table Splitting

run:

1. Copy the *.WHR files from

<Temporary_Dump_Directory> /ABAP/DATA to

<Export_Dump_Directory> /ABAP/DATA.

2. Add the lines from

<Temporary_Dump_Directory> /ABAP/DATA/whr.txt to

<Export_Dump_Directory> /ABAP/DATA/whr.txt.

8. If required, create the temporary index on the tables of the source system to be split.

Oracle only: This is not required if you perform a database export using the Oracle-specific method with the Oracle PL/SQL splitter.

For more information, see paragraph Creating a Temporary Index.

Related Information

Using Hints [page 55]

Creating a Temporary Index [page 55]

Processing Split Tables [page 129]

54

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

4.1.3.1 Using Hints

Some platforms allow the creation and usage of an R3ta_hints.txt file, with which you can instruct R3ta to use specific columns of a table to create a WHERE condition.

With the file R3ta_hints.txt, you can instruct R3ta to use specific columns of a table to create a WHERE condition. The file has to be located in the directory in which you start R3ta.

With one line in the file R3ta_hints.txt, you specify the table name followed by one or more column names, separated by a blank. The columns have to be part of the primary key of the table. These specifications are used by R3ta to create the WHERE condition.

A file R3ta_hints.txt with column hints for several tables is delivered with the installation media (folder

IM_ <OS>

). If you want to modify this file, copy it from the directory IM_

<OS> /COMMON/INSTALL to the installation directory and adapt it according your requirements as soon as the

Parameter Summary

dialog appears and before starting the processing phase.

4.1.3.2 Creating a Temporary Index

If required, create the temporary index on the tables of the source system to be split.

IBM DB2 z/OS only: Create the corresponding temporary index on the database with database tools. Only create a temporary index if you want to perform an unsorted unload. This is the case when you use a

DDLDB2.TPL file with no ORDER_BY_PKEY and the R3load does not overrule this setting. Which tables cannot be unloaded unsorted is described in SAP Note 954268 .

Example

1. Use the DEFER YES parameter to create the index.

2. Afterwards, use the REBUILD INDEX job to speed up the index creation process.

For each table to be split, R3ta creates the following files to facilitate the creation of the temporary index:

Table 5:

File Description

<table>_IDX.STR

<table>_IDX.TSK

Contains the description of the temporary index; the default index name is <table>~IMG.

Contains the task to create the temporary index.

R3load command file for creating the temporary index.

<table>_IDX.cmd

DRP_<table>_IDX.TSK

DRP_<table>_IDX.cmd

Contains the task to drop the temporary index.

R3load command file for dropping the temporary index.

You can use the R3load cmd, STR, and TSK files created by R3ta to create the index.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

55

1. IBM DB2 for IBM i; IBM DB2 for Linux, UNIX and Windows; IBM DB2 for z/OS; SAP MaxDB; MS SQL

Server, Oracle only:Make sure that you do not lock the table while creating the temporary index.

Depending on your database platform it might be necessary to modify the create index statement in the

DDL <DBTYPE> .TPL file.

2. Call R3load as user

<sapsid> adm with the following parameters:

R3load -dbcodepage <dbcodepage_of_source_system> -i

<table>_IDX.cmd -l <table>_IDX.log

If your source system is a non-Unicode system, the dbcodepage is 1100. If your source system is a

Unicode system, the dbcodepage is 4102 (big-endian) or 4103 (little-endian).

4.1.4 Preparing the Package Split

You can use the Package Splitter for splitting the following:

● STR (initially created by R3ldctl) and EXT files (provide sizes of tables, created by R3szchk)

● 6.40: TSK files with WHERE clauses (including an adaptation of the corresponding STR and EXT files)

● 7.00: WHR files with WHERE clauses (including an adaptation of the corresponding STR and EXT files)

The Package Splitter (and R3ta) offers the following options that you can set in the corresponding export dialog of the installer:

56

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

●

Number of tables to be extracted

Defines how many of the largest tables of each package will be extracted, default value is 10. As some packages might contain many tables (in the range of about 10.000 tables), you might want to increase this value (see values below).

●

Package Size Limit

This parameter defines the maximum size of an STR package, comprising all tables. In case the size should be above this limit, the package will be split. Default value is 1000MB.

●

Number of Tables Limit

This new split feature (available with the latest tool versions) runs after the other package splitting options finished. It takes care that every STR file contains the maximum amount of tables or less. This is helpful in case a package contains a lot of tables with less content (or empty tables – for example, in case of SAP

Business Warehouse (SAP BW) migrations, where you might have a lot of empty tables in one STR file): while the other split options would not get active due to the small size, this split feature would help to reduce the corresponding runtimes.

●

Table Size Limit

This parameter defines the maximum table size – if a table should be larger, it gets extracted from the STR file. Default value is 300MB.

●

Split Predefined Tables

Optionally, specify a file containing tables (in most cases: your largest tables) that you want to get split into several pieces. As soon as the export of one split part has finished, the target side can already start processing (instead of having to wait for the export of the whole table).

Table splitting is done by R3ta (see above). For the other options, the Package Splitter is used by the installer.

The best way to find the optimum of these parameters is to run migration tests and afterwards analyze them using the Migtime tool – for more information, see SAP Note 784118 . As a starting point, try the following parameters:

● Extract the 150 largest tables

● Extract tables larger as 200MB from the package

● Package size: 1000MB

● Corresponding command line (can also be triggered in corresponding dialog):

./str_splitter.sh -strDirs -top 150 -tableLimit 500 -packageLimit 1000

More Information

For more information, see:

● SAP Note

784118 (system copy tools for ABAP systems)

●

Using the Package Splitter Tool [page 142]

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

57

4.1.5 Preparing Parallel Export and Import

If you want to perform export processes in parallel to import processes, you have to prepare the source system for the export.

Context

The preparation includes creating the export directory structure.

Caution

Parallel export and import without

Export Preparation

is not supported. If you do not prepare the export, you have to wait for the export results before you can start with the target system setup.

Procedure

1. Run the installer to perform the

Export Preparation

as described in Exporting the Source System [page

60]

.

This step creates the export directory structure.

2. Share or transfer the complete export directory with its structure to the target host.

If you transfer the export directory instead of sharing it, make sure that you transfer it while you are processing the

Database Instance Export

option, after you have stopped the source system and before you proceed with the export procedure.

For more information, see

Transferring the Export Files to the Target Host [page 82]

.

Related Information

About the Migration Monitor [page 111]

Transferring the Export Files to the Target Host [page 82]

4.1.6 Additional Considerations for the Migration to SAP

HANA Database (Export)

● Declustering is performed by default during the export – that is, cluster tables are made transparent. This is also the case if you are using parallel export/import with the Net Exchange or the FTP option. Only if you are using parallel export/import with the Socket Mode option, declustering has to take place during

58

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

import. Even in this case, no direct action is required from you, as the latest version of software provisioning manager/Migration Monitor adapts the procedure automatically.

● With parallel export/import, SAPNTAB gets imported first (sequentially), before parallel import is started.

● Perform the splitting as prepared above under

Preparing the Migration to SAP HANA Database [page 32] .

● Sorted versus unsorted export:

The default setting for the data export is unsorted (the default got changed from sorted to unsorted with only some hard-coded exceptions). It is recommended that you keep the defaults. Only change the default on explicit advice by development support.

Recommendation

It is recommended that you keep the defaults. Only change the default on explicit advice by development support.

● Performance-relevant considerations for the export:

○ Check if SAP Note

1775293 (Migration/system copy to SAP HANA using latest SWPM 1.0) contains any performance-relevant aspects.

○ Optionally, you can use more than one SAP application server to increase the performance of the export:

○ In the installer, start also here with the

Database Instance Export

option, but select the

Use

Additional Export Hosts

on the corresponding

SAP System Database Export

screen.

Note

It is not necessary to combine this feature with the execution of a parallel export and import.

With this, a package filter file is created for each host involved in the export – you can specify details in feature-specific screens that come up in the course of the

Define Parameters

phase - such as how many package filter files or hosts you want to involve in the export, the name of the files, and the unload order. By default, the same amount of packages (measured by size or runtime) is assigned to each single package filter file or host.

○ For each additional package filter file you have specified before, start the installer with option

Database Instance Export on Additional Host

, which exports the remaining packages, as defined in the package filter file. For this, you can start the installer on the same host or any other host on which an SAP instance of this SAP system is running.

● Update database statistics, if the source database requires a manual refresh of the database statistics.

Troubleshooting

If the output of the ABAP report SMIGR_CREATE_DDL is very large, read SAP Note 2022386 .

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

59

4.1.7 Exporting the Source System

Here you can find information about how to run the installer to perform the export on the source system.

For more information about the overall sequence of steps required for exporting the source system, see

System Copy Procedure [page 42]

.

Related Information

Prerequisites for Running the Installer [page 60]

Running the Installer [page 63]

Restarting R3load Processes [page 80]

4.1.7.1 Prerequisites for Running the Installer

Make sure you fulfil the following prerequisites before running the installer.

● If you want to use the SL Common GUI, make sure that the following web browser requirements are met:

○ You have one of the following supported browsers on the device where you want to run the SL

Common GUI: Google Chrome, Mozilla Firefox, Microsoft Edge, or Microsoft Internet Explorer 11.

Always use the latest version of these web browsers.

Recommendation

We recommend using Google Chrome.

○ If you copy the SL Common GUI URL manually in the browser window, make sure that you open a new

Web browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or private browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering with the SL Common GUI.

For more information about the SL Common GUI, see Useful Information About the Installer [page 68] .

● We recommend that you use the csh shell for the installation. If you want to use another shell, make sure that you have read SAP Note 202227 .

The installer uses csh scripts during the installation to obtain the environment for user

<sapsid> adm.

This is also true if user

<sapsid> adm already exists from an earlier SAP system installation, and the shell of this user is not csh. Before you start the installer, execute the following command as user

<sapsid> adm to make sure that the csh scripts are up-to-date:

/bin/csh -c "source /home/<sapsid>adm/.cshrc;env"

● Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example by using a crontab entry.

Make sure that the temporary directory has the permissions 777.

● Make sure that you have at least 300 MB of free space in the installation directory for each installation option. In addition, you need 300 MB free space for the installer executables. If you cannot provide 300

60

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or

TMPDIR to another directory with 300 MB free space for the installer executables.

You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation

directory as described in section Useful Information About the Installer [page 68] .

● The following information is only valid if you use the Java GUI:

Make sure that your DISPLAY environment variable is set to

<Host_Name>:0.0

, where

<Host_Name>

is the host on which you want to display the installer GUI.

You can set values for the DISPLAY environment variables as follows:

Table 6:

Shell Used Command

Bourne shell (sh)

DISPLAY=<Host_Name>:0.0

export DISPLAY

C shell (csh)

Korn shell (ksh)

setenv DISPLAY <Host_Name>:0.0

export DISPLAY=<Host_Name>:0.0

● Make sure that umask is set to

022

for the user with root permissions that you want to use for running the installer.

As the user with root permissions that you want to use for running the installer, enter the following command:

umask 022

●

Only valid for 'Platform': AIX

AIX: Make sure that you have set the limits for operating system users as described in SAP Note 323816

.

End of 'Platform': AIX

●

Only valid for 'Platform': HP-UX, Linux, Oracle Solaris

HP-UX, Linux, Oracle-Solaris: Make sure that you have set the limits for operating system users root,

<sapsid> adm, and your database-specific operating system users (see also section "Creating Operating

System Users and Groups" and "Running the Installer" in the installation guide).

Caution

Caution: the limit mechanism supports hard- and soft-limits. The soft-limit cannot be bigger than the hard-limit. The hard-limit can be set/increased by the root user like:

limit -h <limit>

<new_value>

, for example

limit -h datasize unlimited

.

○ Using csh shell, the output of command limit needs to be at least as follows:

Example

The following table lists example output taken from SUSE Linux Enterprise Server 11 (x86_64).

Table 7:

Output Properties cputime unlimited

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

61

Output filesize datasize stacksize coredumpsize descriptors memoryuse

Properties unlimited unlimited

8192 KB unlimited

8192 unlimited

○ Using sh or ksh shell, the output of command ulimit -a needs to be at least as follows:

Example

The following table lists example output taken from SUSE Linux Enterprise Server 11 (x86_64).

Table 8:

Output sh Output ksh Properties cpu time (seconds) file size (blocks) data seg size (kbytes) cpu time (seconds) file size (blocks) data size (Kibytes) unlimited unlimited unlimited stack size (kbytes) core file size (blocks) open files max memory size (kbytes) stack size (Kibytes) core file size (blocks) nofile max memory size (Kibytes)

8192 KB unlimited

8192 unlimited

End of 'Platform': HP-UX, Linux, Oracle Solaris

● Make sure that the database is up and running before starting the installation.

● Make sure that the following ports are not used by other processes:

○ When using the SL Common GUI:

○ Port 4237 is used by default as HTTPS port for communication between the installer and the SL

Common GUI.

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:

SAPINST_HTTPS_PORT=<Free Port Number>

○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing.

The filled-out evaluation form is then sent to SAP using HTTPS.

62

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:

SAPINST_HTTP_PORT=<Free Port Number>

○ When using the Java SDT GUI:

○ Port 21212 is used by default for communication between the installer GUI server and the installer

GUI client.

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:

SAPINST_DIALOG_PORT=<Free Port Number>

○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing.

The filled-out evaluation form is then sent to SAP using HTTPS.

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:

SAPINST_HTTP_PORT=<Free Port Number>

● Specify an empty directory with sufficient disk space for the export dump on the host where you want to perform the export. Make sure that this directory does not contain any files from any previous system copy exports. If you cancelled a system copy export and want to perform the export again, make sure that you remove all files from the previously cancelled export before you start the export from scratch.

● Caution: Make sure that you shut down all SAP application servers before the export. The database must still be running. Otherwise, the target system might be inconsistent.

4.1.7.2 Running the Installer

This section describes how to run the installer to perform the export for system copy.

Prerequisites

For more information, see Prerequisites for Running the Installer [page 60]

.

Context

Software Provisioning Manager (the “installer” for short) offers two GUIs:

● The new web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common

GUI” for short

● The “classic” Java-based GUI with a CUI client and server - “Java SDT GUI” for short

Note

If the SL Common GUI does not meet your requirements you can still use the “classic” Java SDT GUI.

You then have to start the sapinst executable with the command line option

SAPINST_SLP_MODE=false

.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

63

In cases where both GUIs behave the same way, we address them as “installer GUI”.

For more information, see Useful Information About the Installer [page 68] .

This procedure describes an installation where you use one of the following GUI scenarios:

● You run the installer and use the SL Common GUI. Then you can control the processing of the installer in the browser running on any device.

● You run the installer and use the Java SDT GUI. Both are running on the same host.

The following information is only valid if you use the Java SDT GUI:

● If you need to see the installation on a remote display, we recommend that you

perform a remote installation [page 73]

, where the installer GUI is running on a separate host from the installer.

● Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809 .

Procedure

1. Log on to the host where you want to run the installer.

Make sure that you log on as a user with root permissions.

Caution

Make sure that this user has not set any environment variables for a different SAP system or database.

Caution

Do not use an existing

<sapsid> adm user.

SL Common GUI only: If your security policy requires that the person running the installer is not allowed to know the credentials of a user with root permissions on the host where the installer is to perform the export , you can specify another operating system user for authentication purposes. You do this using the

SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524 .

2. Make the required media available.

For more information, see

Preparing the Media Required for Performing the Export [page 36]

.

Recommendation

Make the installation media available locally . For example, if you use Network File System (NFS), reading from media mounted with NFS might fail.

Only valid for 'Platform': Oracle Solaris

Note

If you mount installation media, make sure that you do this with option

nomaplcase

.

End of 'Platform': Oracle Solaris

64

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

3. Start the installer as follows:

Open a command prompt and enter the following command:

/<Path_To_Unpack_Directory>/sapinst

Note

If you want to run a system copy with parallel export/import using the Migration Monitor, for example with the socket option, and the target database is declustered, start the installer for the database instance export with command line option

SUPPORT_DECLUSTERING=false

The installer GUI starts automatically by displaying the

Welcome

screen.

Note

If you want to use a virtual host name, start the installer with the installer property

SAPINST_USE_HOSTNAME as follows:

/<Path_To_Unpack_Directory>/sapinst SAPINST_USE_HOSTNAME=<Virtual_Host_Name>'

Caution

Make sure that the installation directory is not mounted with NFS, or there might be problems when starting the Java Virtual Machine.

4. The installer is starting up.

Depending on the type of the installer GUI you want to use, do one of the following:

○ If you use the SL Common GUI, the installer now starts and waits for the connection with the SL

Common GUI.

You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you are running the installer.

Sample Code

...

*************************************************************************

*******

Open your browser and paste the following URL address to access the GUI https://[ <hostname> ]:4237/sapinst/docs/index.html

Logon users: [ <users> ]

*************************************************************************

*******

...

If you have a supported web browser (see

Prerequisites for Running the Installer [page 60]

) installed on the host where you run the installer, you can open this URL directly in the shell. Otherwise open the

URL in a supported web browser that runs on another device.

The SL Common GUI opens in the browser by displaying the

Welcome

screen.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

65

Note

Before you reach the

Welcome

screen, your browser might warn you that the certificate of the sapinst process on this computer could not be verified. Accept this warning to inform your browser that it can trust this site, even if the certificate could not be verified.

○ If you use the Java SDT GUI - that is you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

, the Java SDT GUI starts automatically by displaying the

Welcome

screen.

5. On the Welcome screen, choose

<Product> <Database>

System Copy Source System Based on

<Technical Stack>

.

Note

If you want to copy SAP Business Suite powered by SAP HANA 1.0, on the Welcome screen, choose

SAP Business Suite powered by SAP HANA

<Product> <Database>

System Copy Source

System Based on AS ABAP

.

Select the corresponding system copy option from the tree structure according to the sequence of the process flow for the

database-independent system copy procedure [page 41]

.

Note

Do not perform these steps if you use a database-specific method (see Database-Specific System

Copy [page 91] ).

6. Choose

Next

.

7. Follow the instructions in the installer input screens and enter the required parameters.

Note

To find more information on each parameter during the

Define Parameters

phase, position the cursor on the required parameter input field :

○ If you use the SL Common GUI, choose either

F1

or the

HELP

tab. Then the available help text is displayed in the

HELP

tab.

○ If you use the Java SDT GUI, choose

F1

. Then a dialog opens with the available help text.

Note

IBM DB2 for Linux, UNIX, and Windows only: When you are asked for the security administrator, enter a user that has DB2 SECADM authorities. By default, db2

<dbsid source>

has these authorities.

Caution

The signature of media is checked automatically during the

Define Parameters

phase while processing the

Media Browser

screens.

Keep in mind that this automatic check is only committed once and not repeated if you modify artefacts such as SAR archives or files on the media after the initial check has been done - that is if you

66

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

modify artefacts later on either during the remaining

Define Parameters

phase or later on during the

Execute Service

phase the signature is not checked again.

See also the description of this new security feature in SAP Note 2393060 .

8. After you have entered all requested input parameters, the installer displays the

Parameter Summary

screen. This screen shows both the parameters that you entered and those that the installer set by default.

If required, you can revise the parameters before starting the export procedure.

9. To start the execution, choose

Next

.

The installer starts the export and displays its progress of the system copy export during the processing phase.

10. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the installer has finished.

Sometimes these remain in the temporary directory.

Note

If there are errors with the installer extraction process, you can find the log file dev_selfex.out in the temporary directory.

Recommendation

Keep all installer directories until you are sure that the system, including all instances, is completely and correctly installed. Once the system is completely and correctly installed, make a copy of the installer directories with all their contents. Save the copy to a physically separate medium, such as a medium or a USB drive that is separate from your installation hosts.

This might be useful for analyzing any issues that might occur later when using the system. For security reasons, do not keep the installer directories on hosts where you processed it, but make sure that you delete them after saving them separately.

11. If you copied installation media to your hard disk, you can delete these files when the installer has successfully completed.

12. Java GUI only: For security reasons, we recommend that you delete the .sdtgui directory within the home directory of the user with which you ran the installer:

<User_Home> /.sdtgui/

13. For security reasons, we recommend that you remove the operating system users from the group sapinst after you have completed the installation.

Note

This step is only required, if you did not specify during the

Define Parameters

phase that the operating system users are to be removed from the group sapinst after the execution of the installer has completed.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

67

Related Information

Useful Information About the Installer [page 68]

Interrupted Processing of the Installer [page 70]

Performing Remote Processing of the Installer (Java SDT GUI only) [page 73]

Starting the Java SDT GUI Separately [page 75]

Running the Installer in Accessibility Mode [page 77]

Troubleshooting with the Installer [page 79]

4.1.7.2.1 Additional Information About the Installer

The following sections provide additional information about the installer.

Related Information

Useful Information About the Installer [page 68]

Interrupted Processing of the Installer [page 70]

Performing Remote Processing of the Installer (Java SDT GUI only) [page 73]

Starting the Java SDT GUI Separately [page 75]

Running the Installer in Accessibility Mode [page 77]

Troubleshooting with the Installer [page 79]

Troubleshooting during the Export Process [page 80]

4.1.7.2.1.1 Useful Information About the Installer

This section contains some useful technical background information about the installer and the installer GUI.

● Software Provisioning Manager (the installer) offers two GUIs:

○ The new web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common

GUI” for short

○ The “classic” Java-based GUI with a CUI client and server - “Java SDT GUI” for short

The SL Common GUI of the Software Provisioning Manager (or “SL Common GUI” for short) uses the SAP

UI Development Toolkit for HTML5 - also known as SAPUI5 - a client-side HTML5 rendering library based on JavaScript. The benefits of this new user interface technology for the user are:

○ Zero foot print, since only a web browser is required on the client

○ New controls and functionality, for example, view logs in web browser.

The SL Common GUI connects the web browser on a client with the sapinst executable - which is part of

Software Provisioning Manager - running on the installation host using the standard protocol HTTPS.

For the SL Common GUI the installer provides a pre-generated URL at the bottom of the shell from which you are running the installer . If you have a supported web browser installed on the host where you run the

68

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

installer, you can start the SL Common GUI directly from this URL. Otherwise, open a web browser supported by the SL Common GUI on any device and run the URL from there.

For more information about supported web browsers see

Prerequisites for Running the Installer [page

60]

.

If the SL Common GUI does not meet your requirements, you can still use the “classic” Java SDT GUI. To do so, you must start the sapinst executable with the command line option

SAPINST_SLP_MODE=false

.

You can switch back to the default installer GUI at any time with the following steps:

1. Stop the installer.

2. Restart the installer with command line option

SAPINST_SLP_MODE=false

.

3. On the

What do you want to do?

screen choose

Continue with the existing run

.

● The installer creates the installation directory sapinst_instdir directly below the temporary directory.

The installer finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR environment variable. If no value is set for these variables, the installer uses /tmp as default installation directory.

If you want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR to the required directory before you start the installer.

Table 9:

Shell Used Command

Bourne shell (sh)

TEMP=<Directory> export TEMP

C shell (csh)

Korn shell (ksh)

setenv TEMP <Directory> export TEMP=<Directory>

Caution

Make sure that the installation directory is not mounted with NFS, otherwise there might be problems when the Java Virtual Machine is started.

● For each option, the installer creates a subdirectory located in the sapinst_instdir directory.

● The installer extracts itself to the temporary directory. These executables are deleted again after the installer has stopped running.

Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can safely delete them.

The temporary directory also contains the log file dev_selfex.out from the extraction process, which might be useful if an error occurs.

Caution

If the installer cannot find a temporary directory, the installation terminates with the error FCO-00058.

● To see a list of all available installer properties, start the installer as described above with the option

-p

:

./sapinst -p

● This information is only relevant if you use the Java GUI of the installer: If you need to run the installer in accessibility mode, proceed as described in

Running the Installer in Accessibility Mode [page 77] .

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

69

● If you want to perform the export in unattended mode, see SAP Note

2230669 which describes an improved procedure using inifile.params.

● Before starting the export, make sure that you have at least the same amount of disk space available in / sapmnt/ <SAPSID> / <Instance_Name> / <SAPSID> /program as is used in /sapmnt/ <SAPSID> /

<Instance_Name> / <SAPSID> /root/origin.

During the export, some archives are written to the program subdirectories and the tool aborts if there is not enough space.

● Make sure that the DISPLAY environment variable is set to

<host_name> :0.0, where <host_name>

is the host where the tool GUI is displayed.

● If required, stop the installer by choosing one of the following, depending on the installer GUI you use:

○ In the SL Common GUI, choose the

Cancel

button.

○ In the Java SDT GUI, choose

SAPinst Exit Process

in the Java SDT GUI menu..

Note

If you need to terminate the installer, press

Ctrl

+

C

.

4.1.7.2.1.2 Interrupted Processing of the Installer

Here you find information about how to restart the installer if its processing has been interrupted.

Context

The processing of the installer might be interrupted for one of the following reasons:

● An error occurred during the

Define Parameters

or

Execute

phase:

The installer does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error.

● You interrupted the installation by choosing

○

Cancel

in the SL Common GUI

○

Exit Process

in the

SAPinst

menu in the Java SDT GUI

Caution

If you stop an option in the

Execute

phase, any system or component installed by this option is incomplete and not ready to be used. Any system or component uninstalled by this option is not completely uninstalled.

70

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

The following table describes the options in the dialog box:

Table 10:

Option Definition

Retry

Stop

The installer retries the installation from the point of failure without repeating any of the previous steps.

This is possible because the installer records the installation progress in the keydb.xml file.

We recommend that you view the entries in the log files, try to solve the problem, and then choose

Retry

.

If the same or a different error occurs, the installer displays the same dialog box again.

The installer stops the installation, closing the dialog box, the installer GUI, and the

GUI server.

The installer records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below.

Continue

View Log

The installer continues the installation from the current point.

Access installation log files.

The following procedure describes the steps to restart an installation, which you stopped by choosing

Stop

, or to continue an interrupted installation after an error situation.

Procedure

1. Log on to the installation host as a user with the required permissions as described in Running the Installer

[page 63] .

2. Make sure that the media required for the export are still available.

For more information, see

Preparing the Media Required for Performing the Export [page 36]

.

Recommendation

Make the installation media available locally. For example, if you use remote file shares on other

Windows hosts, CIFS shares on third-party SMB-servers, or Network File System (NFS), reading from media mounted with NFS might fail.

Only valid for 'Platform': Oracle Solaris

Note

Oracle Solaris: If you mount installation media, make sure that you do this with option

nomaplcase

.

End of 'Platform': Oracle Solaris

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

71

3. Restart the installer from the directory to which you unpacked the Software Provisioning Manager archive by executing the following command:

<Path_To_Unpack_Directory>/sapinst

4. The installer is restarting.

Depending on the type of the installer GUI you want to use, do one of the following:

○ If you use the SL Common GUI, the installer now starts and waits for the connection with the SL

Common GUI.

You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you are running the installer.

Sample Code

...

*************************************************************************

*******

Open your browser and paste the following URL address to access the GUI https://[ <hostname> ]:4237/sapinst/docs/index.html

Logon users: [ <users> ]

*************************************************************************

*******

...

If you have a supported web browser (see

Prerequisites for Running the Installer [page 60]

) installed on the host where you run the installer, you can open this URL directly in the shell. Otherwise open the

URL in a supported web browser that runs on another device.

The SL Common GUI opens in the browser by displaying the

Welcome

screen.

Note

Before you reach the

Welcome

screen, your browser might warn you that the certificate of the sapinst process on this computer could not be verified. Accept this warning to inform your browser that it can trust this site, even if the certificate could not be verified.

○ If you use the Java SDT GUI - that is you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

, the Java SDT GUI starts automatically by displaying the

Welcome

screen.

5. From the tree structure on the

Welcome

screen, select the installation option that you want to continue and choose

Next

.

The

What do you want to do?

screen appears.

6. On the

What do you want to do?

screen, decide between the following alternatives and continue with

Next

:

72

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

Table 11:

Alternative

Perform a new run

Continue with the existing one

Behavior

The installer does not continue the interrupted export for system copy option.

Instead, it moves the content of the old installer directory and all installer-spe­ cific files to a backup directory. Afterwards, you can no longer continue the old option.

The following naming convention is used for the backup directory: log_ <Day> _ <Month> _ <Year> _ <Hours> _ <Minutes> _ <Seconds>

Example log_01_Oct_2016_13_47_56

Note

All actions taken by the export for system copy before you stopped it (such as creating directories or users) are not revoked.

Caution

The installer moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.

The installer continues the interrupted export for system copy from the point of failure.

4.1.7.2.1.3 Performing Remote Processing of the Installer

(Java SDT GUI only)

Here you find information about how to process the installer on a remote host.

Note

This section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

.

Prerequisites

● The remote host meets the prerequisites for starting the installer as described in

Prerequisites for

Running the Installer [page 60]

.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

73

● Both computers are in the same network and can ping each other.

To test this:

1. Log on to your remote host and enter the command:

ping <Local_Host>

2. Log on to the local host and enter the command:

ping <Remote_Host>

● If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER command line parameter, make sure that this user exists on the remote host.

Context

You use this procedure to process the installer on a remote host. In this case, the installer runs on the remote host, and the installer GUI runs on the local host. The local host is the host from which you control the installation with the installer GUI. The installer GUI connects using a secure SSL connection to the installer.

If your security policy requires that the person performing the installation by running the installer GUI on the local host is not allowed to know the credentials of a user with root permissions on the remote host, you can specify another operating system user for authentication purposes. You do this using the

SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line.

You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524 .

Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809 .

Procedure

1. Log on to the remote host as a user with root permissions.

Caution

Make sure that this user has not set any environment variables for a different SAP system or database.

2. Make the installation media available on your remote host.

For more information, see

Preparing the Media Required for Performing the Export [page 36]

.

Recommendation

Make the installation media available locally . For example, if you use Network File System (NFS), reading from media mounted with NFS might fail.

Only valid for 'Platform': Oracle Solaris

Note

Oracle Solaris: If you mount installation media, make sure that you do this with option

nomaplcase

.

End of 'Platform': Oracle Solaris

3. Open a command prompt and change to the directory to which you unpacked the Software Provisioning

Manager archive.

74

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

4. Check the version of the sapinst executable by entering the following command:

<Path_To_Unpack_Directory>/sapinst -sfxver

The version of the sapinst executable must be exactly the same as the version of the sapinstgui executable on the local host (see also

Starting the Installer GUI Separately [page 75] ).

5. Start the installer by entering the following command:

<Path_To_Unpack_Directory>/sapinst

Note

If you need to specify another operating system user for authentication purposes, enter the following command:

<Path_To_Unpack_Directory>/sapinst

SAPINST_REMOTE_ACCESS_USER=<Specified_OS_User>

Note

If you are running a system copy with parallel export/import using the Migration Monitor and started the export with command line option

SUPPORT_DECLUSTERING=false

, you have to start the installer for the installation of the target database instance with command line option

SUPPORT_DECLUSTERING=true

for the import during the target system installation.

For more information, see the system copy guides at http://support.sap.com/sltoolset

Provisioning System Copy Option Guide for Systems Based on SAP NetWeaver 7.1 & Higher

System

The installer now starts and waits for the connection to the installer GUI. You see the following at the command prompt: guiengine: no GUI connected; waiting for a connection on host <Host_Name> , port

<Port_Number> to continue with the installation

6. Start the installer GUI on your local host as described in

Starting the Installer GUI Separately [page 75]

.

4.1.7.2.1.4 Starting the Java SDT GUI Separately

Here you find information about how to start the Java SDT GUI separately.

Note

This section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

75

Prerequisites

The host on which you want to start the installer GUI meets the prerequisites for starting the installer as described in

Prerequisites for Running the Installer [page 60]

.

Note

If you want to run the installer on a Windows host, make sure that you meet the prerequisites for the installer listed in the relevant Windows guide.

Context

You might need to start the installer GUI separately in the following cases:

● You closed the installer GUI using

File Close GUI only

from the installer menu while the installer is still running.

● You want to perform a remote installation, where the installer GUI runs on a different host from the

installer. For more information, see Performing Remote Processing of the Installer (Java SDT GUI only)

[page 73]

.

● You want to run the installer in accessibility mode. In this case, you have to start the installer GUI separately on a Windows host as described below with the command line parameter

-accessible

.

For more information, see

Running the Installer in Accessibility Mode [page 77] .

In the this procedure, the following variables are used:

<Remote_Host>

is the name of the remote host, and

<Port_Number_Gui_Server_To_Gui_Client>

is the port the GUI server uses to communicate with the GUI client (21212 by default).

Procedure

● Starting the Installer GUI on Windows a. Make the installer software available on the host on which you want to start the installer GUI.

For more information, see Preparing the Media Required for Performing the Export [page 36] .

b. Start the installer GUI by executing the sapinstgui executable with the appropriate command line parameters:

○ If you want to perform a remote installation, proceed as follows:

1. Check the version of sapinstgui.exe by entering the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -sfxver

The version of the sapinstgui executable must be exactly the same as the version of the sapinst executable on the remote host (see also

Performing a Remote Installation [page

73] ).

2. Start the installer GUI by entering the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -host <Remote_Host> -port

<Port_Number_Gui_Server_To_Gui_Client>

76

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

○ If you closed the installer GUI using

File Close GUI only

and want to reconnect to the installer, proceed as follows:

1. If you are performing a local installation with the installer and the installer GUI running on the same host, execute the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -port

<Port_Number_Gui_Server_To_Gui_Client>

2. If you are performing a remote installation with the installer and the installer GUI running on different hosts, execute the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -host <Remote_Host> -port

<Port_Number_Gui_Server_To_Gui_Client>

c. The installer GUI starts and connects to the installer.

● Starting the Installer GUI on UNIX a. Make the installer software available on the host on which you want to start the installer GUI.

For more information, see Preparing the Media Required for Performing the Export [page 36] .

b. Start the installer GUI by executing the sapinstgui executable with the appropriate command line parameters:

○ If you want to perform a remote installation, proceed as follows:

1. Check the version of the sapinstgui executable by entering the following command:

<Path_To_Unpack_Directory>/sapinstgui -sfxver

The version of the sapinstgui executable must be exactly the same as the version of the sapinst executable on the remote host (see also

Performing a Remote Installation [page

73] ).

2. Start the installer GUI by entering the following command:

<Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port

<Port_Number_Gui_Server_To_Gui_Client>

○ If you closed the installer GUI using

File Close GUI only

and want to reconnect to the installer, proceed as follows:

1. If you are performing a local installation with the installer and the installer GUI running on the same host, execute the following command:

<Path_To_Unpack_Directory>/sapinstgui -port

<Port_Number_Gui_Server_To_Gui_Client>

2. If you are performing a remote installation with the installer and the installer GUI running on different hosts, execute the following command:

<Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port

<Port_Number_Gui_Server_To_Gui_Client>

c. The installer GUI starts and connects to the installer.

4.1.7.2.1.5 Running the Installer in Accessibility Mode

You can also run the installer in accessibility mode.

Note

The information contained in this section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

77

If you use the SL Common GUI, apply the standard accessibility functions of your web browser.

Context

The following features are available:

● Keyboard access:

This feature is generally available for all operating systems.

● High-contrast color:

This feature is derived from the Windows display properties. Therefore, to enable this feature, perform a remote installation with the installer GUI running on a Windows host.

● Custom font setting:

This feature is derived from the Windows display properties. Therefore, to enable this feature, perform a remote installation with the installer GUI running on a Windows host.

Procedure

● Activating and Adjusting Accessibility Settings on Windows

You first have to activate and adjust the relevant settings for the font size and color schemes before you start the installer or the installer GUI.

Note

The following procedure applies for Windows Server 2012 and might be different when using another

Windows operating system.

a. Right click on your Windows desktop and choose

Personalize

.

b. Select

Adjust font size (DPI)

and choose

Larger scale (120 DPI)

.

To define other font size schemes, choose

Custom DPI

.

c. In the right-hand pane, select

Window Color and Appearance

.

Select a color scheme from the

Color scheme

drop-down box.

To define your own color schemes, choose

Advanced

.

● Running the Installer in Accessibility Mode

You perform a remote installation as follows: a. Start the installer on the remote host by executing the following command from the command line as described in

Performing Remote Processing of the Installer (Java SDT GUI only) [page 73]

:

<Path_To_Unpack_Directory>/sapinst

b. Start the installer GUI on a local Windows host by executing the following command from the command line as described in

Starting the Java SDT GUI Separately [page 75] :

<Path_To_Unpack_Directory>\sapinstgui.exe -accessible -host <Remote_Host> port <Port_Number_Gui_Server_To_Gui_Client>

78

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

4.1.7.2.1.6 Troubleshooting with the Installer

This section tells you how to proceed when errors occur while the installer is running.

Context

If an error occurs, the installer:

● Stops processing

● Displays a dialog informing you about the error

Procedure

1. Check SAP Note 1548438 for known installer issues.

2. If an error occurs during the

Define Parameters

or the

Execute Service

phase, do one of the following:

○ Try to solve the problem:

○ To check the installer log files (sapinst.log and sapinst_dev.log) for errors, choose:

○ The

LOG FILES

tab, if you are using the SL Common GUI.

○ The

View Logs

menu item, if you are using the Java SDT GUI.

○ To check the log and trace files of the installer GUI for errors:

○ If you use the SL Common GUI, you can find them in the directory

<User_Home> /.sapinst/ .

○ If you use the Java SDT GUI, you can find them in the directory

<User_Home> /.sdtgui/

○ If the GUI server or the installer GUI do not start, check the file sdtstart.err in the current

<User_Home>

directory.

○ If the installer GUI aborts without an error message, restart the installer GUI as described in

Starting the Installer GUI Separately [page 75] .

○ If you use an X Server for Microsoft Windows or other remote desktop tools for the

Remote Access of the Java SDT GUI on Windows workstations and you experience display problems such as missing repaints or refreshes, contact your X Server vendor.

The vendor can give you information about whether this X Server supports Java Swingbased GUIs and also tell you about further requirements and restrictions. For more information, see SAP Note 1170809 .

○ Then continue by choosing

Retry

.

○ If you cannot resolve the problem, abort the installer by choosing one of the following, depending on the type of installer GUI you use:

○ If you use the SL Common GUI, choose

Cancel

in the tool menu.

○ If you use the Java SDT GUI, choose

Stop

from the error message or

SAPinst Exit Process

in the tool menu.

For more information, see Interrupted Processing of the Installer [page 70] .

3. If you cannot resolve the problem, report an incident using the appropriate subcomponent of BC-INS*.

For more information about using subcomponents of BC-INS*, see SAP Note 1669327 .

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

79

4.1.7.2.1.7 Troubleshooting during the Export Process

If the export process aborts during the

Execute Service

phase (for example, due to a hardware failure, such as power outage, operating system crash, file system full), you have to repeat the export of the complete package.

Procedure

● System Copy – export (common issues) a. Remove the

<Package> .

<nnn>

dump files, the

<Package> .TOC file, and the <Package> .log file.

b. Make sure that all tables in the

<Package> .*TSK* file have the status flag xeq or err set.

c. Repeat the export of the complete package.

● System Copy – export on UNIX (especially for upgraded systems)

Symptom:

Processes started under the OS users

<sapsid> adm or ora <dbsid>

cannot create or open files in the installer directory.

Reason:

Only members of the sapinst UNIX group can access the installer directory. This group is created by the installer as of SAP NetWeaver 7.1.

Solution: a. Manually associate

<sapsid> adm and ora <dbsid>

OS users with sapinst group if this association is missing.

b. Verify the /etc/group file and check if the sapinst group exists and OS users are members of this group.

c. If the sapinst group does not exist yet, start the installer. The installer creates this group during startup before the product catalog list is displayed.

d. Edit /etc/group file and associate OS users with sapinst group.

e. Continue with the export.

4.1.7.3 Restarting R3load Processes

You can restart failed or canceled R3load processes while the Migration Monitor is still running.

Context

The state files export_state.properties and import_state.properties (see

Output Files [page 137] )

allow package states to be manually updated to restart failed R3load processes.

80

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

Example

If package processing failed and the package state has the value “–”, the state can be set to “0” and processing of the package is restarted.

If you want to restart failed or canceled R3load processes that are using the socket option, R3load processes that process the same package must not be running.

Procedure

● Restarting R3load Processes Without Using the Socket Option a. To restart package processing, set the package state from “–” to “0”.

b. To skip package processing, set the package state from “0” or “–” to “+”. (This is not recommended, because it can cause inconsistent data files or database content.) c. If the package is currently being processed (the package state is “?”), then any manual modifications to the package state are ignored.

● Restarting R3load Processes Using the Socket Option a. Make sure that no related R3load processes (export or import) are running. For example, if you want to restart an R3load export process and the corresponding import process that processes the same package is still running, cancel it or wait until it has finished.

b. There are four possible situations where an R3load restart may be required. Proceed as required:

○ If both the import and the export are completed successfully, there is nothing to do.

○ If the export was completed successfully, but the import is canceled with errors, proceed as follows:

○ If the export was successful but the import was canceled when creating the index or the primary key, set the status for export_state.properties from “+” to “0”.

○ If the export was completed successfully but the import was canceled when loading the table content, set the status for export_state.properties from “+” to “0” and for the export

TSK file from “ok” to “err”.

○ If both the export and the import are canceled with errors, proceed as follows:

○ If the errors in export and import relate to the same table, there is nothing to do.

○ If the errors relate to different tables, set the status of the first object with errors in both the export and the import TSK file to “err” and in the export_state.properties and import_state.properties files to “–”.

Example

Table 12:

Export TSK File

Table Name

TAB_1

Status ok

Import TSK File

Table Name

TAB_1

Status ok

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

81

Export TSK File

TAB_2

TAB_3

TAB_4 err xeq xeq

Import TSK File

TAB_2

TAB_3

TAB_4 ok err xeq

The first object with errors here is TAB_2 (export). This means that in the import TSK file the status for TAB_2 must be set from “ok” to “err”. The entry in the export_state.properties and import_state.properties files also must be set from “+” to “0”.

○ If the import is completed successfully but the export was canceled with errors, you can set the status in the export_state.properties from “–” to “+”.

c. Restart the installer or the Migration Monitor to proceed with the system copy.

4.1.8 Setting Up the Target System

Related Information

Transferring the Export Files to the Target Host [page 82]

Installing the Target System [page 84]

4.1.8.1 Transferring the Export Files to the Target Host

This section describes how to transfer the complete export directory with its structure to the target host.

Context

As an alternative, you can also share the complete export directory so that it can be accessed from the target host.

82

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

Procedure

1. On the target host, create a directory

<EXPDIR>

with sufficient space for the database export files available.

Caution

Do not create this directory under the installation directory or another directory that contains installation information (such as the installation media or export files).

Otherwise, the installer does not ask you to specify the export directory and automatically chooses one that you may not want to use. In this case, the installer does not display the export directory and you cannot change it.

2. Transfer all files and directories (recursively) that are located on the source host in the migration export directory

<EXPDIR>

from the source host to the target host.

You can choose one of the following methods:

○ Use the migration monitor with the file transfer protocol (FTP) copy option.

Note

Make sure that you use binary mode for transferring the files.

○ Copy the export dump directory manually to the target host.

○ The export dump directory can be shared and thus made accessible on the target host (network share).

3. Check the permissions of the transferred files on the target host. All files have to be accessible for user

<sapsid> adm of the target system.

Related Information

Additional Considerations for the Migration to SAP HANA Database (Transfer of the Export File) [page 83]

4.1.8.1.1 Additional Considerations for the Migration to

SAP HANA Database (Transfer of the Export File)

You can transfer files from the source host to the SAP HANA host using different protocols, for example NFS or

FTP. In advance, consider the following aspects:

● Performance of the file transfer types

● Availability on different platforms (NFS, for example, is not available on Microsoft Windows hosts)

● Security requirements (for example, Migration Monitor currently only supports FTP, but not SFTP)

● Availability in a customer system landscape (FTP, for example, can be forbidden in customer landscapes)

● Which transfer mode and protocol is supported by the installer and the Migration Monitor for the parallel export and import?

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

83

● Which tool and process is in control of the overall export, transfer, and import process?

4.1.8.2 Installing the Target System

This section describes how to set up the target system using the installer.

Prerequisites

● There is enough free space on the target system for the database load.

● The installer automatically performs a reload. If the database software has already been unpacked or installed, or if the database already exists, the installer recognizes this automatically and skips the related steps.

Context

This system copy guide describes only the export of the source system in detail. For the installation of the target system, you use the installation guide for the database and operating system platform of your target system. This procedure describes only the additional system copy-specific steps for the target system installation and refers for the remaining steps to the target system installation guides. You find the target system installation guides at http://support.sap.com/sltoolset

System Provisioning System Copy

Option of Software Provisioning Manager System Copy Guides - Installing the Target System

.

In the following, we refer to this guide as “installation guide”.

Procedure

1. Prepare the target system host as described in the installation guide for the operating system and database platform intended for the target system.

2. Start the installer as described in the installation guide for the operating system and database platform intended for the target system.

Caution

If you plan to use Advanced Configuration options during the SAP System Database Import, make sure you have installed the most current version of the installer to avoid performance problems during the

Define Parameters

phase. You can find the latest version of the installer at: http://support.sap.com/sltoolset

Manager

System Provisioning Download Software Provisioning

84

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

Note

If you are running a system copy with parallel export/import using the Migration Monitor and started the export with command line option

SUPPORT_DECLUSTERING=false

(see System Copy Procedure

[page 42]

), you must now start the installer for the installation of the target database instance with command line option

SUPPORT_DECLUSTERING=true

for the import during the target system installation.

3. On the

Welcome

screen, navigate to the following folder according to the requirements of your target system:

<Product> <Database>

System Copy Target System

<System_Variant>

Based on

<Technical_Stack>

.

4. Run the option required for your system copy.

To install the target system, follow the instructions in the installer input screens and enter the required parameters.

Caution

Heterogeneous system copy: When installing the database instance, you either have to choose parameter mode

Custom

or have to check the

Database Import

screen on the summary screen and then revise this screen. Only then appears the screen where you can enter the migration key, which is required for a heterogeneous system copy. If you forget to revise this screen setting during the

Define

Parameters

phase, the installer will abort in the processing phase when checking the migration key and will ask you for a valid migration key.

Note

If you are running a system copy with parallel export/import using the Migration Monitor and the target database is declustered - that is you started the installer with command line option

SUPPORT_DECLUSTERING=true

as described above - make sure that you choose the

Custom

parameter mode . Otherwise the screen for advanced load configuration (

SAP System Advanced Load

Configuration

) will not appear.

Caution

○ If you perform a Unicode conversion, the data import into the target system might abort because of missing space in the database tablespace or dbspace. Enlarge the database or database container, in which the table DYNPSOURCE will be created in the target database. The required size for the table will be 15 times larger than in the non-Unicode source system.

○ Do not create the installation directory (for example: sapinst_instdir) in the following directories:

○ /usr/sap/

<SAPSID>

○ /sapmnt/

<SAPSID>

○ If you want to perform export processes in parallel to import processes and you have prepared the export, you must do the following:

○ Choose

Custom

on the

Parameter Mode

screen.

○ Select

Parallel Export and Import

on the

SAP System Database Import

screen.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

85

○ On the

SAP System Database

screen, choose

Standard System Copy/Migration (Load-Based)

.

The SAP data dump from the migration export media that was created during the database instance export is loaded in the newly installed SAP system database.

○ When the installer displays the

Media Browser

screen and prompts for the

Export Location

, enter the path to the export directory

<EXPDIR>

.

○ If you perform a heterogeneous system copy, enter the Migration Key on the

Database Import

screen.

○ If you are running a system copy with parallel export/import using the Migration Monitor and the target database is declustered - that is you started the installer with command line option

SUPPORT_DECLUSTERING=true

as described above - add the following load options parameter in the

SAP System Advanced Load Configuration

screen:

-datacodepage <datacodepage_of_source_system>

You can check the parameter within the import_monitor_cmd.properties file located in the installation directory, in the loadArgs entry.

5. Complete the installation as described in the installation documentation for your SAP component.

○ If you have to restart the import after an error, just restart the installer. The import continues with the table that has not yet been successfully imported.

○ If you have to restart failed R3load processes, see

Restarting R3load Processes [page 80]

.

○ You can use the Migration Checker tools to ensure that the import has been performed successfully. The package checker and the object checker automatically check that the import has started and that all objects have been imported. In addition, you can use the table checker tool to verify that the number of rows that have been exported is equal to the number of rows in the database by using the table of content (TOC) files. For more information about the table checker, see SAP Note 2009651 . For more information about all these checks see the Migration Checker

User Guide. It is contained in the MIGCHECK.SAR archive as MigrationChecker.pdf and is available in the following directory of the installer:

<Path_To_Unpack_Directory> /COMMON/INSTALL/MIGCHECK.SAR

○ As an alternative to the table checker, you can perform

Table Comparison with Software Update

Manager (SUM) [page 138] .

Proceed as follows:

1. Make sure that the primary application server instance is not started after the import has finished successfully.

If your system is based on SAP NetWeaver 7.4 or higher, you can mark the check box

Interrupt installation before starting the SAP system

on the screen

Exit Before Starting SAP System

to ensure this.

2.

Run table comparison [page 140]

for the target system.

3. Start the instances of the target system.

Note

If you have to restart failed R3load processes, see Restarting R3load Processes [page 80]

.

You can use the Migration Checker to ensure that the import has been performed successfully. The

Migration Checker automatically checks that the import has started and that all objects have been imported. For more information about additional checks with the Migration Checker, see the Migration

Checker User Guide contained in the MIGMON.SAR archive, which is available in the following directory:

You can use the Migration Checker tools to ensure that the import has been performed successfully. The package checker and the object checker automatically check that the import has started and that all objects have been imported. In addition, you can use the table checker tool

86

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

to verify that the number of rows that have been exported is equal to the number of rows in the database by using the table of content (TOC) files. For more information about the table checker, see SAP Note 2009651 . For more information about all these checks see the Migration Checker User

Guide. It is contained in the MIGCHECK.SAR archive as MigrationChecker.pdf and is available in the following directory of the installer:

<Path_To_Unpack_Directory> /COMMON/INSTALL/MIGCHECK.SAR

Related Information

Additional Considerations for the Migration to SAP HANA Database (Import) [page 87]

4.1.8.2.1 Additional Considerations for the Migration to

SAP HANA Database (Import)

Before you start the import for the migration to SAP HANA, consider the following:

Declustering

If you are using parallel export/import with the Socket Mode option, declustering has to take place during the import. For this, no direct action is required from you, as the latest versions of software provisioning manager and Migration Monitor adapt the procedure automatically.

Log Mode

Before the import, make sure that the log mode is set to overwrite (which is the initial value of the log mode after the initial setup of the database until a first data backup has been performed) to avoid a “disk full” situation.

If data backups already exist for this instance, you can set the log mode back to overwrite by changing the parameter log_mode from normal to

overwrite

and restarting the database, so that the new parameter becomes active.

Tuning of SAP HANA Data Load Performance

To improve the performance of SAP HANA INSERTs and data loads, consider the area about savepoints and corresponding parameter settings listed in section How can the performance of INSERTs and data loads be

tuned? of SAP Note 2000002 .

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

87

Table Placement

For scale-out systems, download the relevant TABLE_PLACEMENT text file that is attached to an SAP Note. The relevant SAP Note for your application and SAP HANA revision is documented in SAP Note 1900822 . You should then use the TABLE_PLACEMENT text file as parameter file for installer during the import. For additional information about table placement and landscape redistribution see the blog SAP HANA Landscape

Redistribution with SP6 in the SAP Community Network at: http://scn.sap.com/community/hana-inmemory/blog/2013/09/03/sap-hana-landscape-redistribution-with-sp6

Check Parameters for Dynamic Adjustment of Load Jobs

Especially for SAP HANA, the Migration Monitor comprises a migmonctrl.jar add-on that gets invoked automatically to adjust the amount of R3load jobs dynamically during the import. For this purpose, the addon maintains the ORDER_BY.TXT file, which is read by Migration Monitor every 30 seconds to start new jobs.

The adjustment is necessary because most of the tables need to be organized (merged) in memory before they can be flushed to the disk. Therefore, an additional amount of memory is necessary.

In general, all packages of an export are distributed over three groups inside the ORDER_BY.TXT file:

● [Large]

Group Large contains the biggest packages sorted by size from biggest to smallest.

● [Small]

Group Small contains the smaller packages sorted by size from smallest to biggest. As Migration Monitor starts the jobs according to the number of jobs defined for one group top-down, the first table of group

Large (the biggest) is loaded together with the first of group Small (the smallest). Due to this, SAP HANA memory is used more efficiently.

● [Rowstore]

This group contains packages that only contain one row-store table – that is, tables not listed here are column-store tables. Row-store tables always stay in the memory (also after import), whereas columnstore tables are merged, compressed and synchronized to disk after import, which reduces memory consumption.

The Rowstore group is loaded at the end of the import to avoid interferences with column-store tables.

The add-on has parameters that you can adjust in the MIGMONCTRL_CMD.PROPERTIES file. Check these parameters and if required, adjust them according to your situation. These are the most important parameters:

# Maximum number of R3load jobs defined in groups Large and Small.

maximumJobNum=100

# Factor of safety used to multiply the current size of all running jobs. The number of jobs is increased as long as enough free space is available within HANA.

memoryFactor=2

# Initial value for the number of R3load jobs for group Large. The value is also the minimum to which the number of jobs will be decreased.

initialLargeJobNum=5

# Initial value for the number of R3load jobs for group Small. The value is also the minimum to which the number of jobs will be decreased.

initialSmallJobNum=5

# If set to true migmonctrl stops to do changes to the order_by.txt.

pause=false

# Number of R3load jobs used for group Rowstore.

88

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

jobNumRowstore=33

# If set to true Rowstore tables are put in a separate group named

Rowstore. R3load jobs for this group are started after the last table specific package has finished.

loadRowstoreSeparate=true

You can change the parameters also while Migration Monitor is running, because they are read every 5 seconds by default.

To check the add-on version, run the following command:

./sapjvm/sapjvm_6/bin/java -jar migmonctrl.jar -V

Log files of the add-on are MIGMONCTRL.LOG and MIGMONJOBBER.CONSOLE.LOG.

Using an SAP HANA Standby Server for the Import of SAP Business

Warehouse

If scale-out is released for your product, consider to use an SAP HANA standby server node for the import to improve performance.

To achieve this, perform a

Distributed System

installation as follows:

1. Perform a Distributed System installation.

2. Install the ASCS instance on the SAP system host.

3. Perform the Database Instance installation (including data import) on the SAP HANA standby node:

1. As a prerequisite, copy the profiles directory /sapmnt/

<SAPSID> /profile from the SAP server, create user

<sapsid> adm and group sapsys with the same IDs as on the ASCS instance host and change the owner of the copied profile directory to

<sapsid> adm:sapsys.

2. You can use default settings (

Typical Mode

), but should consider to enable parallel export and import, if released for your product (see above). You do not need to start the Migration Monitor manually.

3. Enter the path to the newest kernel from SAP Service Marketplace.

4. Install the primary application server Instance on the SAP system host.

Analysis of Import

For further analysis after the import and optimization of further import runs, you can use the files

R3LOAD_JOBS.CSV, FREE_MEMORY.CSV, SAVEPOINT_STATISTIC.CSV and CPU_USAGE.CSV.

Example

The easiest way to use these files is to import them into Microsoft Excel, for example:

1. Open the CSV file in Microsoft Excel and mark all relevant values until the import has stopped.

If you are in doubt, check the import log file for the exact time.

2. Choose

Insert Line Line

.

3. In the inserted diagram, right-click on the values from the horizontal (category) axis and select

Format

Axis …

.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

C U S T O M E R

89

4. In the shown

Axis Options

dialog, select the

Text axis

value for the

Axis Type

parameter.

Result would be a diagram like the one taken from the example in the Appendix of this documentation:

Troubleshooting

● If you want to use virtual host names, see SAP Note

2141442 (SAP HANA client software: hdbuserstore

not found when using virtual host names).

● If you create a system copy of an SAP system based on SAP NetWeaver 7.40 SP5 or higher, in which the

ABAP source search is active (switch: SRIS_SWITCH_SOURCE_SEARCH), see SAP Note 2031638

(R3load terminates during creation of an index for a field of the type LOB).

● For potential problems during the installation of scale-out systems, see SAP Note

2041412 (Error

during initial landscape redistribution during migration)

● For migrations on the AIX platform, see SAP Note

1976256 (AIX: TCP/IP connections hang)

90

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database Independent System Copy

5 Database-Specific System Copy

The following sections describe the database-specific methods for the system copy.

Note

When performing a system copy using a database-specific method, it is no longer required to perform an export of the source system.

Process

Follow the sequence of steps described in the process flows below for a:

● Standard system

● Distributed system

● High-availability system

Standard System

Note

When performing a system copy using a database-specific method, it is no longer required to run the installer in the source system to export it. You only have to run the installer on the target host to install the target system.

Proceed as follows on the standard system host.

Process Flow on the Target System

1. Follow the instructions on the installer screens until you are requested to perform the database backup/ restore.

Note

If required, you have to restart the installer as described in the installation guide of your SAP solution.

2. To complete the system copy, you have to perform the

follow-up activities [page 98] .

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database-Specific System Copy

C U S T O M E R

91

Distributed System or High Availability System

Note

When performing a system copy using a database-specific method, it is no longer required to run the installer in the source system to export it. You only have to run the installer on the target host to install the target system.

To perform the export for a distributed or high-availability system, proceed as follows:

Process Flow on the Target System

To complete the system copy, you have to perform the follow-up activities [page 98]

.

5.1 SAP HANA Database-Specific Procedure

This section describes how to perform a homogeneous system copy of a SAP HANA database.

Procedure

Perform the steps described in SAP Note 1844468 .

92

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Database-Specific System Copy

6 Copying Single Instances Only

If you want to copy single instances of your SAP system only, you can use one of the following procedures, depending on your use case.

Caution

You cannot copy single product instances, usage types, or components!

Related Information

Copying the Primary Application Server Instance Only [page 93]

Copying the Database Only – Move Database Instance [page 94]

Copying the Database Only – Refresh Database Instance [page 95]

Copying the Database Only – Refresh Database Content [page 96]

6.1 Copying the Primary Application Server Instance Only

With this procedure, you can move a primary application server instance to a different host within your system.

Prerequisites

The ABAP central services instance (ASCS instance) is installed.

Procedure

1. Shut down all application servers.

2. Uninstall the old primary application server instance as described in the Additional Information section of the installation guide.

3. On your target host, start the installer as described in Running the Installer [page 63]

.

4. On the Welcome screen, navigate to the following folder according to the requirements of your target system:

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Copying Single Instances Only

C U S T O M E R

93

<Product> <Database>

System Copy Target System Distributed System or High-Availability

System Based on

<Technical Stack>

Primary Application Server Instance

.

5. After the installation has finished, restart all additional application server including the instance services.

6.2 Copying the Database Only – Move Database Instance

You can use this procedure to move a database instance to a different host within your system. You can perform the move using either database-specific methods or the SAP standard method based on R3load .

Context

“Move” means moving the database instance to a different host to refresh the database content.

If you only want to “refresh” the database content with the database instance staying on the same host, use

either the procedure described in Copying the Database Only – Refresh Database Instance [page 95]

or the

procedure described in Copying the Database Only – Refresh Database Content [page 96]

For more information, see https://blogs.sap.com/2017/03/02/refresh-database-content-withoutreinstalling-the-database-or-kernel-for-abap-systems/

Procedure

Caution

○ The

<DBSID>

must not be changed.

○ When copying the database only, you cannot change to another database but need to perform a database-homogeneous copy.

○ The old database instance cannot be uninstalled using the installer-based uninstall procedure. This always deletes the current database of the system.

1. On the source host, run the installer to perform the export in one of the following ways:

○ If you perform the export using R3load, on the Welcome screen, choose

<Product>

<Database>

System Copy Source System Based on AS ABAP Database Instance Export

to export the database.

○ If you perform the export using database-specific tools, you must start them manually.

2. On the target host, stop all SAP application server instances, but leave the ASCS instance running.

3. On the target system, run the installer and choose

<Product> <Database>

System Copy Target

System

<System_Variant>

Based on AS ABAP Database Refresh or Move

to install the database.

94

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Copying Single Instances Only

Note

Since the target database instance is to replace the source database, do not change the

<DBSID>

.

4. When the installer has completed the installation of the database, restart your system including all instance services.

5. Shut down the old database instance.

Related Information

Running the Installer [page 63]

6.3 Copying the Database Only – Refresh Database

Instance

Using option

Refresh or Move Database Instance

you can refresh an existing database instance without having to copy the primary application server instance and to reinstall additional applications servers. You can perform the refresh using either database-specific methods or the SAP standard method based on R3load .

Prerequisites

● The source system and the target system already exist.

● You must prepare the kernel media and the RDBMS media as described in Preparing the Installation Media in the documentation Installation Guide - SAP Systems based on the Application Server ABAP Dual-Stack

(ABAP+Java) on

Context

This procedure implies a “refresh of the database instance” using kernel and RDBMS media with the database instance staying on the same host.

If you want to “move” the database instance to a different host, use the procedure described in

Copying the

Database Only – Move Database Instance [page 94] .

If you want to only refresh the database content using a database backup - that is without using kernel and

RDBMS media - use the procedure described in Copying the Database Only – Refresh Database Content [page

96]

For more information, see https://blogs.sap.com/2017/03/02/refresh-database-content-withoutreinstalling-the-database-or-kernel-for-abap-systems/

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Copying Single Instances Only

C U S T O M E R

95

Procedure

1. On the source system, perform the export in one of the following ways:

○ If you perform the export using R3load, start the installer and on the Welcome screen choose

<Product> <Database>

System Copy Source System Based on AS ABAP Database

Instance Export

to export the database.

○ If you perform the export using database-specific tools, you must start them manually.

2. On the target host, stop all SAP application server instances, but leave the ASCS instance running.

3. Run the installer and choose

<Product> <Database>

System Copy Target System

<System_Variant>

Based on AS ABAP Database Refresh or Move

to install the database.

Related Information

Running the Installer [page 63]

6.4 Copying the Database Only – Refresh Database

Content

Using the

Refresh Database Content

option in the installer you can refresh the content of an existing database using a database backup. You do not have to copy the primary application server instance and to reinstall additional applications servers.

Prerequisites

The source system and the target system already exist.

Context

You must choose the same

<DBSID>

for the target system as the

<DBSID>

of the export or database backup.

However, you can choose a different instance number.

We recommend that you use option

Refresh Database Content

if you need to equalize the database content of two or more already existing and configured systems, for example in automatized system landscapes with

“template” systems which have to correspond to precisely defined standards, such as predefined host names, network settings, users, security policies.

96

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Copying Single Instances Only

Note

If you want to “move” the database instance to a different host, use the procedure described in Copying the

Database Only – Move Database Instance [page 94]

.

If you want to “refresh” the complete database instance - that is using kernel and RDBMS media - use the procedure described in

Copying the Database Only – Refresh Database Instance [page 95]

For more information, see https://blogs.sap.com/2017/03/02/refresh-database-content-withoutreinstalling-the-database-or-kernel-for-abap-systems/

Procedure

1. Perform a database backup as described in the SAP HANA Administration Guide at http://help.sap.com/ hana_platform

System Administration

.

Make sure that the database backup is accessible from the database host.

2. On the SAP system host, stop all SAP application server instances, but leave the ASCS instance running.

3. On the database host, run the installer and choose

Generic Options SAP HANA Database Refresh

Database Content

.

Follow the instructions on the installer screens. You are prompted for the following:

○ The

<DBSID>

of the target system.

Choose the same

<DBSID>

for the target system as the

<DBSID>

of the database backup. However, you can choose a different instance number.

○ The profile directory of your SAP system.

○ The location of the database backup.

○ The database administrator password for the backup.

Related Information

Running the Installer [page 63]

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Copying Single Instances Only

C U S T O M E R

97

7 Follow-Up Activities

To finish the system copy of your SAP system, you have to perform follow-up activities in the target system

Related Information

Performing Follow-Up Activities in the Source System [page 98]

Performing Follow-Up Activities in the Target System [page 98]

7.1 Performing Follow-Up Activities in the Source System

This section describes the steps that you have to perform in the source system to finish the system copy.

Procedure

1. If you canceled or scheduled released jobs and jobs that must run periodically before you started the copy procedure, reschedule these jobs (transaction SM37).

2. Using CCMS, adapt your operation mode timetable to the original status (transaction SM37).

7.2 Performing Follow-Up Activities in the Target System

To complete the system copy process, you need to perform several follow-up activities on the target system.

Related Information

SAP Solution Manager: Connection Between SLD and LMDB [page 99]

Performing Follow-Up Activities for ABAP [page 99]

98

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Follow-Up Activities

7.2.1 SAP Solution Manager: Connection Between SLD and

LMDB

● Consider the following if you move parts of a system, for example the database, or the complete system to new hardware:

○ Each change in the host name generates new elements in the system landscape directory (SLD) which can result in system duplicates.

○ SAP recommends using stable (virtual) host names which remain constant over time, in the system profiles. SAP Note 1052122 lists the profile parameters evaluated by the SLD Data Suppliers for the host names.

● If you omitted to use virtual host names at installation time or if you cannot use virtual host names now, the SLD offers a possibility to prevent the creation of system duplicates. For more information, see SAP

Note 1727294 .

● If you cannot apply SAP Note

1727294 to the SLD, and if you already found a duplicate registration for the system in the SLD, refer to SAP Note 1694004 for guidance how to clean up such inconsistencies. SAP

Note 1747926 describes the cleanup procedure for older SLD releases.

● If you want to copy an SAP Solution Manager system with a filled Landscape Management Database

(LMDB), see SAP Note 1797014 .

● If you want to create a new synchronization connection between the Landscape Management Database

(LMDB) and the System Landscape Directory (SLD), see SAP Note 1699142 .

● If you want to delete a synchronization connection between two SLD systems or between an SLD system and LMDB, see SAP Note 1770691 .

7.2.2 Performing Follow-Up Activities for ABAP

Related Information

Activities at Operating System Level [page 100]

Activities at Database Level [page 100]

Activities at SAP System Level [page 101]

Product-Specific Follow-Up Activities [page 105]

Checking the Target System [page 107]

Additional Activities After the Migration to SAP HANA [page 108]

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Follow-Up Activities

C U S T O M E R

99

7.2.2.1 Activities at Operating System Level

This section includes the adaptations that you have to make at operating system level in your target system.

Procedure

1. Adapt the configuration files at operating system level to meet network and SAP requirements.

2. Adapt additional SAP software components (for example, RFC, CPIC, SAP ArchiveLink) if required.

3. Adapt additional non-SAP software components (for example, archiving systems, monitoring tools, job schedulers) if required.

4. Adapt backup programs (for example, BRBACKUP, BRARCHIVE, BACKINT) if required.

5. Adapt non-SAP directories, file systems, NFS mounts, and so on, if required.

6. Check the SAP parameters of the default and instance profiles.

7. Check your UNIX shell files for special entries.

8. Check crontab or AT jobs.

9. Check operating system files (for example, .netrc, .rhosts).

10. Check operating system printers.

11. If the spool requests are stored at file system level, you must copy the subdirectories with the spool files to the new global directory. For more information, see SAP Note 20176 .

7.2.2.2 Activities at Database Level

This section includes the adaptations that you have to make at database level in your target system.

Procedure

1. Before starting the SAP system, make sure that the logging mechanism of the database is active.

2. Check the parameters in the database profiles.

3. Delete all entries from the following tables: ALCONSEG, ALSYSTEMS, DBSNP, MONI, OSMON, PAHI, SDBAD,

SDBAP, SDBAR.

4. Delete entries in the table DDLOG for buffer synchronization.

5. If your source database was SAP MaxDB, run report RSSDBTICMCLEANUP on the target system. This will delete data that is related to the source system.

100

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Follow-Up Activities

7.2.2.3 Activities at SAP System Level

This section includes the adaptations that you have to make at SAP system level in your target system.

Procedure

1. If you performed a Unicode conversion using as target system ID the same

<SAPSID>

as the source system ID and the (local or NIS-mounted) operating system users of the target system still have the environment of the operating system users of the source system, you need to update the user environment for the operating system users of the target system as follows:

Update the PATH variable so that it points to the platform-specific directory for Unicode.

Example

Update the PATH value /usr/sap/<SAPSID>/SYS/exe/nuc/linuxx86_64 to

/usr/sap/

<SAPSID>/SYS/exe/uc/linuxx86_64

2. Run an installation check (transaction SM28).

3. Delete all entries from the tables TPFET and TPFHT (transaction SE14).

These tables contain information about changes made to the profile of your source system.

4. Import the system profiles into the database (transaction RZ10).

5. If you changed the SAP system ID during the system copy, delete all entries from table TLOCK, which holds the repair requests from your source system.

6. Maintain the operation modes.

a. Create new operation modes and instance definitions (transaction RZ04).

b. Maintain the time table using the new operation modes (transaction SM63).

c. Delete the old operation modes and old instance definitions.

7. Adapt other CCMS settings (for example, alert thresholds, reorganization parameters of CCMS table

MONI) if required.

8. Check the logon groups and the assignment of the application servers to the logon groups (transaction

SMLG).

If required, create new logon groups and assign the new application servers to these logon groups.

9. Define or remove the SAP system users and revise the authorizations of the system users:

Tools

Administration User maintenance Users

(transaction SU01).

10. Synchronize the buffers as described in SAP Note 36283 and adapt the client information for the logical system.

11. Configure the spool server.

a. Adapt the definition of the printers to meet the new system requirements (transaction SPAD):

○ Device types and character set definitions

○ Spool server

○ Output management systems (OMS)

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Follow-Up Activities

C U S T O M E R

101

b. Delete obsolete spool requests and spool inconsistencies while executing the ABAP program

RSPO0041 (transaction SE38).

c. Call transaction SP12 and run report RSPO1043 for a spool data consistency check.

For more information, see SAP Notes 98065 and 48400 .

12. Configure batch jobs.

a. Delete canceled and finished batch jobs while executing the RSBTCDEL ABAP program, selecting

Delete with forced mode

(transaction SE38).

b. Adapt all jobs needed in the target system.

13. If you have used the DBA Calendar in the source system, redefine database actions (backup, update statistics, and so on) (transaction DB13).

14. Maintain the security configuration.

a. Call transaction STRUST.

b. Replace all existing PSE files in the target system with new ones, which contain the new system’s information.

For more information, see the

SAP Library [page 13]

for your release at:

○ SAP NetWeaver 7.3 and higher:

Security System Security System Security for SAP NetWeaver AS ABAP Only Trust

Manager Creating PSEs and Maintaining the PSE Infrastructure Creating or Replacing a PSE

Note

○ Since replacing a PSE will remove all of the previously used certificates, also import all necessary trusted certificates into the new PSE’s certificate list. (Check the old PSE’s certificate list.) Distribute the new PSE’s public-key certificate to the systems where it will be used.

○ Make sure the new PSE contains the new system ID.

○ Note the naming conventions to use for each PSE. The naming conventions are usually specified by the Certification Authority (CA) where you obtain the certificate, however, the type of PSE also has some restrictions, for example, for the SSL server PSE, the CN part of the

Distinguished Name must be the host name used to access the server. For the system PSE, we recommend using the SID as the CN part.

Therefore, make sure that the Distinguished Name used for the PSE conforms with the naming convention that applies.

15. Adapt RFC server groups.

Call transaction RZ12 and change the instance name of RFC server groups under

Group assignment

.

16. Adapt RFC destinations copied from the source system to the target system.

Caution

Before you delete RFC destinations, make sure that they are not needed in the target system.

a. To check and adapt qRFC destination, call transaction SMQR.

b. To check and adapt tRFC destination, call transaction SM58.

c. To delete obsolete RFC destinations, call transaction SM59.

17.

Check the ABAP Secure Store [page 104]

102

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Follow-Up Activities

18. Configure the Transport Management System (TMS).

a. Reschedule the transport dispatcher (RDDIMPDP) in client 000:

1. Log on as user DDIC.

2. Call transaction

SE38

.

3. Run program RDDNEWPP and set the priority to high.

b. Adapt the transport parameters and transport routes in the TMS as follows:

1. Call transaction

STMS

.

2. To adapt the transport parameters, choose

Overview Systems

<your system>

Transport Tool

.

3. To adapt the transport routes, choose

Overview Transport Routes

.

4. Configure the domain controller in the Transport Management System (TMS) by using transaction STMS.

Note

If you did not change the SAP system ID during the system copy, all open transport, repair, and customizing requests that have not been released in the source system will not be released automatically.

19. Make data archived in the source system (data that does not reside in the database but was moved to a different storage location using SAP Archive Management) accessible in the target system. Adapt the file residence information in the target system. For more information, see

Constraints [page 13] and the SAP

Library [page 13] for your release at:

○ SAP NetWeaver 7.3 and higher:

Solution Life Cycle Management Data Archiving

20.Check self-defined external commands (transaction SM69).

21. Check the logical system names. For more information, see

Preparations [page 28]

. If you need to change logical system names in the system that results from the copy, change the logical system names at this time, as described in SAP Notes 103228 and 544509 . Follow your corporate naming strategy for logical systems when making this change.

BW only: If you have copied an SAP BW system, see SAP Note 886102 .

22.For every client in your SAP system check the detail settings (client role, changes and transports for client-dependent objects, changes for client-independent objects, protection level, restrictions)

(transaction SCC4).

23.Check if you can delete clients that are no longer used in the target system (transaction SCC5).

24.Check the contexts and segments of remote application servers for the SAP Monitoring Infrastructure if required (transaction RZ21).

25. Post-processing for customer objects:

○ If customer objects are not original in the new system, modify the corresponding entries in table

TADIR.

○ If you encounter problems modifying a customer development class using transaction SMTS or SM31, try using the option

Validate

(ENTER) instead of the option

Save

to save your changes.

26.BW only: Start program RS_BW_POST_MIGRATION in the background. Program RS_BW_POST_MIGRATION performs necessary modifications on database-specific objects (mainly BW objects).

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Follow-Up Activities

C U S T O M E R

103

If you changed the database management system (for example, IBM i to MaxDB) when copying the system, you have to start program RS_BW_POST_MIGRATION in the background with variant

SAP&POSTMGRDB

Note

If you changed the database management system to SAP HANA database, use variant

SAP&POSTMGRHDB

27. Generate the ABAP load.

The ABAP loads are platform-dependent programs that are generated during runtime and stored in database tables. They are not exported when you use the R3load procedure to copy your SAP system. The

ABAP loads are generated in the target system when they are first used.

Note

Make sure that you have sufficient space available on your database. The generation of all existing objects requires about 2 to 9 GB of free space.

For a detailed description about how to generate the ABAP load, call transaction SGEN and choose

Information about the SAP Load Generator

.

Related Information

Checking the ABAP Secure Store [page 104]

7.2.2.3.1 Checking the ABAP Secure Store

Procedure

1. Start transaction SECSTORE.

2. Choose

Check Entries

and

Execute

.

3. Filter the result by error messages.

Depending on the SAP NetWeaver release your SAP system is based on, you have to proceed in one of the following ways:

○ Your SAP system is based on an SAP NetWeaver release lower than 7.40:

○ If you see at least one error message of type

SECSTORE 030 (“Incorrect global key for entry …”)

, proceed as follows:

1. Restore a legacy key-file that was used in the source system.

You can find information about this process in the SAP Library [page 13] for your release at:

Function-Oriented View Security System Security System Security for SAP

NetWeaver AS ABAP Only Secure Storage (ABAP) Key Management Legacy Method for

Using Individual Encryption Keys Importing Keys after a System Copy

104

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Follow-Up Activities

2. Repeat the check.

○ If you see at least one error message of type

SECSTORE 031 (“System-dependent data for entry … changed: …”)

, you must perform a record migration.

You can find information about this process in SAP Note 816861 .

○ Your SAP system is based on SAP NetWeaver 7.40 or higher:

○ If you see at least one error message of type

SECSTORE 089 (“Key … for entry … is missing in the secure storage in the file system”)

, proceed as follows:

1. Reimport encryption keys that were used in the source system and stored in the secure storage in the file system

You can find information about this process in the SAP Library [page 13] for your release at:

Function-Oriented View Security System Security System Security for SAP

NetWeaver AS ABAP Only Secure Storage (ABAP) Key Management Using Individual

Encryption Keys Importing Missing Encryption Keys

2. Repeat the check.

○ If you see at least one error message of type

SECSTORE 030 (“Incorrect global key for entry …”)

, you need to restore a legacy key-file that was used in the source system.

You can find information about this process in the

SAP Library [page 13]

for your release at:

Function-Oriented View Security System Security System Security for SAP NetWeaver AS

ABAP Only Secure Storage (ABAP) Key Management Legacy Method for Using Individual

Encryption Key Importing Keys after a System Copy

○ If you see at least one error message of type

SECSTORE 031 (“System-dependent data for entry … changed: …”)

, you must perform a record migration.

You can find information about this process in SAP Note 816861 .

7.2.2.4 Product-Specific Follow-Up Activities

Related Information

Business Warehouse (BW) Specific Follow-Up Activities [page 106]

Embedded Search [page 106]

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Follow-Up Activities

C U S T O M E R

105

7.2.2.4.1 Business Warehouse (BW) Specific Follow-Up

Activities

This section provides references to documentation describing how to perform BW-specific follow-up activities.

Perform the BW-specific follow-up activities as described at:

● https://blogs.sap.com/2016/10/11/software-application-lifecycle-management-sap-bw/

Additional

Information about the Lifecycle Management with SAP NetWeaver BW 7.x

SAP NetWeaver 7.3 – BW

Systemcopy ABAP

● https://rapid.sap.com/bp/#/RDS_RDBMS_4_BW

Solution Deployment: Configuration Guide of the

SAP Rapid Deployment Solution "Rapid Database Migration of SAP NetWeaver BW to SAP HANA"

If you have migrated to SAP HANA database, convert your BW InfoProvider to SAP HANA-optimized objects.

For more information, see the

SAP Library [page 13]

for your release at:

SAP NetWeaver Library: Function-Oriented View Business Warehouse Data Warehousing Modeling

Architected Data Mart Layer Creating InfoCubes SAP HANA-Optimized InfoCube Converting Standard

InfoCubes to SAP HANA-Optimized + DSO + SPO

7.2.2.4.2 Embedded Search

Use

Note

Valid for SAP NetWeaver 7.3 and higher.

This section includes the steps that you have to perform to connect TREX with the ABAP target system.

Prerequisites

You have applied SAP Note 1293026 .

Procedure

Note

After the migration to SAP HANA database, the connection to TREX/BWA does not work. To fix this, add the prefix

:RFC:

to the TREX/BWA RFC destination in table ESH_ADM_TREX. For example:

:RFC:TREX_123

106

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Follow-Up Activities

1. To establish the connection between TREX and the ABAP target server, run the script configureTrexRfcConnection.py on the host where TREX is installed.

2. On the ABAP server, perform the following steps:

1. To delete copied search object connectors, call transaction SE38. Run the report

ESH_ADM_INDEX_ALL_SC with option

Delete

.

2. Call transaction SE16 to find out the TREX destination from table ESH_ADM_TREX.

3. Call transaction SM59 to delete the program ID of the TREX destination. TREX retrieves the correct new program ID automatically.

Note

If you have applied SAP Note 1303185 , program ESH_ADM_INDEX_ALL_SC automatically deletes the program ID of the TREX destination.

4. Create new search object connectors.

For more information, see the

SAP Library [page 13]

for your release at:

Search Search Services in SAP NetWeaver AS ABAP Embedded Search Setting Up Embedded

Search Creating Connectors

7.2.2.5 Checking the Target System

The following actions are required for checking the consistency of the target system.

Procedure

1. Perform an initial consistency check (transaction SM28).

2. Check the system log on all application servers (transaction SM21). In case of warnings, see SAP Note

43434 .

3. Check the consistency of the database (transaction DB02).

4. Perform a server check (transaction SM51).

5. FI customers: Run the job SAPF190 (accounting reconciliation) and compare the results to those gained on the source system before the system copy (

Accounting Financial Accounting General ledger

Periodic Processing Closing Check/count Comparison

).

6. FI customers: Run the jobs RFUMSV00 (tax on sales/purchases), RAGITT01 (asset history sheet),

RAZUGA01 (asset acquisitions), andRAABGA01 (fixed asset retirements) and compare the results to those gained on the source system before the system copy.

7. CO customers: Run the report group 1SIP and compare the results to those gained on the source system before the system copy.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Follow-Up Activities

C U S T O M E R

107

7.2.2.6 Additional Activities After the Migration to SAP

HANA

Related Information

Performing Consistency Checks [page 108]

Additional Post-Processing After Migrations to SAP Business Warehouse on SAP HANA [page 109]

7.2.2.6.1 Performing Consistency Checks

This section describes how to perform consisteny checks.

Context

To verify that the import has been performed successfully, the installer performs Package Checker and

Object Checker runs as part of the default procedure. In addition, you can manually perform the Table

Checker – for more information, see SAP Note

784118 .

● The Package Checker is used to verify that the import of all packages was at least started.

● The Object Checker is used to verify that all objects (tables, views, indexes, primary keys) are successfully created or loaded into the database.

● The Table Checker is used to verify if the number of rows been exported is the same as the number of rows in the database (not usable in Socket mode).

Procedure

Proceed as follows to run the Table Checker manually:

1. Download MIGCHECK_

<Version> .SAR from SAP Service Marketplace at: https:// launchpad.support.sap.com/#/softwarecenter

Support Packages and Patches By Category

Additional Components SYSTEM COPY TOOLS GEN SYSTEM COPY TOOLS GEN

<Release>

OS independent

.

2. Proceed as described in the Migration Checker Users’ Guide that is part of the archive downloaded above.

108

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Follow-Up Activities

7.2.2.6.2 Additional Post-Processing After Migrations to

SAP Business Warehouse on SAP HANA

The following additional post-processing steps are only required after migrations to SAP Business Warehouse

(SAP BW) on SAP HANA.

● Before performing other post-processing activities, run the ABAP report RS_BW_POST_MIGRATION as documented in the system copy guide.

● Run the ABAP report RSDU_TABLE_CONSISTENCY to identify potential problems, such as with database indexes, table partitioning, table distribution, and table classification. For more information about using report RSDU_TABLE_CONSISTENCY, see SAP Note 1937062 .

Before you run the report, make sure that you applied all SAP Notes listed in the attachment

REQUIRED_CORRECTION_NOTES.TXT of SAP Note

1908075 .

● SAP Note

1695112 provides additional information about post-processing steps in SAP BW after the migration to the SAP HANA database.

● If you migrated an SAP NetWeaver BW 7.3 or SAP BW 7.31 system to an SAP HANA database, apply the

SAP Notes listed in the collective SAP Note 1846493 before you start using your SAP BW system productively.

● If you migrated an SAP BW 7.4 system to an SAP HANA database, apply the SAP Notes listed in the collective SAP Note 1949273 before you start using your SAP BW system productively.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Follow-Up Activities

C U S T O M E R

109

8 Additional Information

Related Information

R3load Procedures Using the Migration Monitor [page 110]

Analysis of the Export and Import Times [page 138]

Table Comparison with Software Update Manager [page 138]

Using the Package Splitter [page 142]

Troubleshooting for Migration to SAP HANA [page 148]

8.1 R3load Procedures Using the Migration Monitor

Related Information

About the Migration Monitor [page 111]

Configuration [page 112]

Assigning DDL Files to Packages [page 128]

Defining Groups of Packages [page 128]

Processing Split Tables [page 129]

Starting the Migration Monitor [page 130]

Using the migmonCtrl Add-On for the Export [page 135]

Using the migmonCtrl Add-On of the Import Migration Monitor [page 136]

Output Files [page 137]

110

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

8.1.1 About the Migration Monitor

This section lists the functions and features of the Migration Monitor.

Purpose

The Migration Monitor does the following:

● Creates R3load command files

● Creates R3load task files if required

● Starts R3load processes to unload the data

● Transfers packages from source to target host if required

● Starts R3load processes to load data as soon as a package is available

● Informs the person performing the system copy in the event of errors

Note

An up-to-date version of the load tools - such as R3load, R3szchk, R3ldctl, SAPuptool - which were available so far only in the SAPEXEDB.SAR archive of the kernel media, has now been made available in the

Software Provisioning Manager archive

(SWPM10SP

<Support_Package_Number> _ <Version_Number> .SAR), in a sub-archive named

LOADTOOLS.SAR, located in the COMMON/LOADTOOLS folder. For a system copy using Unicode kernel version 7.40 or higher, the load tools from the

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR are used automatically instead of the loadtools available in the SAPEXEDB.SAR archive of the kernel media. There is no action required from your side, the installer uses the relevant loadtools automatically once you run it from the extracted

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR archive.

The Migration Monitor is integrated in the Software Provisioning Manager (the “installer” for short), but it is also possible to start the Migration Monitor manually with the corresponding option in the software provisioning manager. To do this, you require a properties file.

Caution

For all SAP systems based on SAP NetWeaver 7.0 and higher, you can use the socket option without restrictions.

For more information about how to start the Migration Monitor manually, see

Starting the Migration Monitor

[page 130] .

When you start the Migration Monitor manually:

● You can adjust any parameters according to the Migration Monitor User's Guide user guide

● You gain flexibility – for example, you can repeat, test and abort runs of the Migration Monitor

● The process becomes more complex since it requires many additional manual activities

● The properties file has to be created manually

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

111

Recommendation

Reuse an existing properties file from previous runs of software provisioning manager as template

Tool

The tool is located in the MIGMON.SAR SAPCAR archive. The archive file contains the following:

● Scripts:

○ export_monitor.sh / export_monitor.bat

○ import_monitor.sh / import_monitor.bat

○ res_check.sh / res_check.bat

○ import_dirs.sh / import_dirs.bat

● jar archives:

○ migmon.jar

○ rescheck.jar

○ activation.jar

○ mail.jar

● Property files:

○ export_monitor_cmd.properties

○ import_monitor_cmd.properties

● migmonCtrl add-on:

○ Scripts

○ dyn_control_export_monitor.sh / dyn_control_export_monitor.bat

○ dyn_control_import_monitor.sh / dyn_control_import_monitor.bat

○ jar archives

○ migmonctrl.jar

○ Property files:

○ migmonctrl_cmd.properties

Prerequisites

The correct directory structure for R3load dump files must exist on both the source and target hosts.

8.1.2 Configuration

The following options can be specified using the property file or using the command line. Command line parameters take precedence over parameters specified in the property file. Options are case-sensitive, that is, options that are not recognized are ignored.

112

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Help

With the following command line options, the tool displays all parameters available: -help, -?

Version

With the following command line option, the tool displays version information: -version

General Options

Table 13: General Options

Name monitorTimeout

Description

Monitor timeout in seconds

Comment

During a timeout, the monitor thread sleeps and does not analyze any files or analyze its processing state. The de­ fault timeout value is 30 seconds.

Table 14: E-Mail Options

Name mailServer mailFrom mailTo

Description

SMTP server

“From” e-mail address

“To” e-mail address

Comment

-

Server name or IP address of the com­ pany SMTP server

Can contain an address list separated by “;” or blanks.

Table 15: Additional Options

Name bg

Description

Enables background mode

Name

Takes effect only as command line option

If the tool is running in background mode, the UNIX shell windows or Windows command prompt can be closed after startup.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

113

Name secure trace

Description

Enables secure mode

Trace level

Name

Takes effect only as command line option

If the tool is running in secure mode, command line pa­ rameters (for example, passwords) are hidden for Java processes. Secure mode implicitly enables background mode.

Note

Use this mode if you have to specify passwords on the command line.

Possible values: all, off, 1 (error), 2 (warning), 3 (info), 4 (config,

default

), 5, 6, 7 (trace)

Export Monitor – Options

Table 16: Export Options

Option installDir exportDirs client server

Description

Installation directory

List of export directories

Client operating mode

Server operating mode

Comment

Directory where the installation tool (software provision­ ing manager 1.0, R3SETUP) is started. If you run the Migra­ tion Monitor without using the installation tools, the instal­ lation directory is the directory where the R3load TSK and log files are written.

Separator on Windows: “;”

Separator on UNIX, IBM i: “:”

The exportDirs parameter points to the directory where the R3load dump files are written. In the exportDirs directory, the subdirectories DATA , DB , and DB/ <TARGET_DBTYPE> (for example, DB/ORA must exist.

Running in client mode means that the Migration Monitor runs parallel to standard installer export process and transfers the exported dump files to the import server.

Running in server mode means that the Migration Monitor creates R3load TSK files (if necessary), R3load cmd files, and starts the R3load processes.

114

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Option Description Comment

All options below are for server mode. The import monitor always runs in server mode. If you want to run the export moni­ tor in server mode, specify the server parameter in the properties file of the export monitor.

orderBy

Package order Can be the name or path of the file that contains package names. If the option value is omitted, package order is not determined.

ddlFile

DDL control file Path or filename of DDL control file

The default is DDL

<DBTYPE> .TPL.

If the filename is used without a path, the DDL control file from the export DB subdirectory is used.

ddlMap r3loadExe

DDL mapping file File with mapping between DDL files and package names

Path of the R3load executable Optional; default is R3load. If only the name of the

R3load executable is available, the JVM looks for the

R3load executable using operating system-specific proc­ ess search rules.

tskFiles yes to create task files; no to skip

Up to and including version 4.6, this must be set to no; as of version 4.7 set to yes. If the R3load task files *.TSK already exist, the monitor does not overwrite them.

dataCodepage taskArgs

Code page for data files

See SAP Note 552464 . Possible values: 4102, 4103,

1100

Additional R3load arguments for the TASK phase

Appended to the R3load command line

Options already set by the monitor: -ctf; -l loadArgs

Additional R3load arguments for the LOAD phase

Appended to the R3load command line. Options already set by the monitor: -e; -datacodepage; -l; -p; -r; socket (if the socket option is specified); -o (if the omit argument is specified and task files are not used, that is, the value of the tskFiles option is no).

jobNum decluster

(use this option only for tar­ get dbType = HDB)

Number of parallel export jobs, default:1

Any positive number

The value can be changed dynamically at runtime.

Default value is false Possible values : true or false

If this option is true, the Migration Monitor calls R3load with option -decluster.

firstExportSAPNTAB Default values is false Possible values: true or false

If this option is true, the Migration Monitor first exports the SAPNTAB package in single thread mode.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

115

Option onlyProcessOrderBy

Description

Table 17: Network Exchange Options

Option net

Description

Network operating mode

Comment

If set to true only the jobs from file configured with orderBy are processed.

netExchangeDir

Network exchange directory

Comment

Exported dump files must be visible on the import host to use this mode.

Caution

Clean up the netExchangeDir be­ fore starting a new export.

Used for communication between the export and import monitors. Must be writable for the export monitor and readable for the import monitor. The export monitor writes a

<Package> .SGN file to the network ex­ change directory as a signal to the im­ port monitor that the package has been exported successfully and that the im­ port can be started.

Table 18: FTP Exchange Options

Option ftp

Description

FTP operating mode ftpHost ftpUser

Remote FTP host

Name of the remote FTP user

Comment

Exported dump files are transferred au­ tomatically from the source host (di­ rectory exportDirs) to the target host (directory importDirs) using

FTP.

Name or IP address of the import server

The FTP user specified here should be

<sapsid> adm to make sure that the package files can be read during the import (which is started as

<sapsid> adm).

116

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Option ftpPassword ftpExportDirs ftpExchangeDir ftpJobNum

Table 19: Export Socket Host

Option socket host port

Description

Password of the remote FTP user

Comment

Caution

Security risk.

List of remote FTP directories for ex­ port dump

Remote FTP exchange directory

Number of parallel FTP jobs; the de­ fault is 1.

For more information, see the secure parameter in section Additional Op­

tions.

Both “;” and “:” separators are valid.

This is the directory on the target host to which the dump is transferred. The value is the same as for importDirs in the properties file of the import moni­ tor.

Used for communication between the export and import monitors.

Must be writable for the export monitor and readable for the import monitor.

The export monitor writes a

<Package> .SGN file to the FTP ex­ change directory as a signal for the im­ port monitor that the package is ex­ ported successfully and that the import can be started.

Any positive number; 0 for an unlimited number of jobs

The value can be changed dynamically at runtime.

Description

Socket operating mode

Remote import host

Host port number

Comment

R3load does not write dump files to the file system but the export and im­ port work through the socket connec­ tion.

Name or IP address of the import host.

Must be the same as the port number on the import host. Any free port on the import host from 1024 to 65535.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

117

Table 20: FTP Copy Options

Option ftpCopy

Description Comment

FTP copy operating mode Used as a separate program call for migration with sockets if no share directory is used. All files produced by R3lctl and R3szchk are transferred from the source to the target host using FTP.

exportDirs ftpHost ftpUser ftpPassword

List of export directories Separator on Windows: “;”

Separator on UNIX, IBM i: “:”

In the exportDirs directory, the subdirectories DATA, DB, and DB/

<TARGET_DBTYPE>

(for example, DB/ORA) must exist. The R3load

STR files have to exist in the subdirectory DATA, the DDL*.TPL files in the subdirectory DB , and the R3load EXT files (if required) in the subdirectory DB/

<TARGET_DBTYPE>

.

Remote FTP host

Password of the remote

FTP user

Name or IP address of the import server

Name of the remote FTP user

The FTP user specified here must be

<sapsid> adm to make sure that the package files can be read during the import (which is started as

<sapsid> adm).

Caution

Security risk ftpExportDirs List of remote FTPdirecto­ ries for export dump

Both “;” and “:” separators are valid. This is the directory on the target host to which the dump is transferred. The value is the same as for importDirs in the properties file of the import monitor.

Any other option is ignored by the export monitor.

Export Options for the “migmonCtrl” Add-On

The migmonctrl add-on was developed to improve the performance of the export by offering new export strategies.

These are the following:

● “export by size”

The *.EXT files are used.

● “export by runtime”.

The information is taken from the migration time analyzer output file export_time.txt. If you also did an import already, you can add the import_time.txt file as well. The additional options are added to the export_monitor_cmd.properties file.

118

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Table 21:

Option migmonCtrl orderBy jobNumLarge jobNumSmall customSortOrderFile -

Description

Enabling the add-on

File with package order

Comment

-

If migmonCtrl is set, the file is created dynamically. It still has the same format as the order_by file, which you can create manually.

If it is created by the add-on, the file has two groups called

LARGE and SMALL.

Depending on the sort order (size or runtime), the packages are listed from biggest/longest to smallest/shortest in group LARGE and from smallest to biggest in group SMALL.

Therefore the biggest and smallest packages are exported to­ gether. This ensures that the biggest tables are exported right from the beginning but also that input is provided to the import side by exporting the smallest table.

The number can be changed during runtime.

Amount of jobs set in group LARGE

Amount of jobs set in group SMALL

The number can be changed during runtime.

To keep up the number of jobNumLarge + jobNumSmall, pack­ ages from group LARGE are moved into group SMALL when the number of unprocessed packages in group SMALL becomes smaller than jobNumSmall.

In addition to that, jobNumSmall is increased when the number of unprocessed packages in group LARGE becomes smaller than jobNumLarge.

If certain jobs need to be exported right from the start, they can be configured in this file.

SAPAPPL0_24_1 REPOSRC T100 /BIC/MYBWTABLE

Table 22: Export by Size

Option extFileDir

Description

Absolute path of EXT files generated by

R3szchk

Comment

Mandatory if the export is to be sorted by size

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

119

Table 23: Export by Runtime

Option exportTimeFile

Description

Absolute path of file export_time.txt created by migtime.jar

Amount of analyzed packages used from file import_time.txt

Comment

Mandatory if the export is to be sorted by runtime importTop Can only be used if parameter importTimeFile is set

For parallel export/import, long run­ ning jobs on the import side need to be exported first.

The importTop option adds the long running jobs on top of group LARGE.

Optional importTimeFile Absolute path of file import_time.txt created by migtime.jar

Package Filter Files

With package filter files you can distribute the export over several servers. To use this feature you have to create the filter files first. This requires a separate run of the migration monitor. For this you can temporarily add the following options to the export_monitor_cmd.properties file or simply add them to the command line.

Table 24: Creating Package Filter Files

Option Description Comment createPackageFilter excludePackage outputFile hostNames

Comma separated string package_list_%hostName%.txt

Comma separated string

Needs to be set to create package filter files.

Packages that must not be included in the filter file

Location and name of result files

%hostName% is replaced with the ac­ tual name of the host.

The names are only used for the file name:

<outputFile> _ <hostName> .txt

Table 25: Using Package Filter Files

Option onlyProcessOrderBy -

Description Comment

If this option is set to

true

, only the jobs from orderBy file are processed.

120

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Option packageFilter netStatisticsFile

Description package_list_%hostName%.txt

package_filter_%hostName

%.statistics

Comment

File that contains packages used for the export. This can be used if the ex­ port is to be executed on multiple hosts.

If parallel export/import is chosen, this file is created when the Mi­ gration Monitor has finished all jobs from the package list.

Mandatory Options for the Export Monitor

● Client mode: installDir, exportDirs, one of the options ftp, net (and their related parameters)

● Server mode: installDir, exportDirs, tskFiles, one of the options ftp, net, socket (and their related parameters)

● FTP copy: exportDirs, ftpHost, ftpUser, ftpExportDirs, ftpExchangeDir

Note

The value of the dbType option is determined automatically in the shell script or batch files from the dbms_type environment variable.

Import Monitor – Options

Table 26: Import Options

Option installDir

Description

Installation directory

Comment

The installation directory is the directory in which the in­ stallation tools (software provisioning manager

1.0, R3SETUP) are started.

When you run the Migration Monitor without using the in­ stallation tools, the installation directory is the directory where the R3load TSK and log files are created.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

121

Option importDirs orderBy ddlFile ddlMap r3loadExe tskFiles extFiles

122

C U S T O M E R

Description

List of import directories

Package order

DDL control file

DDL mapping file

Path of the R3load exe­ cutable yes to create task files; no to skip yes to include EXT files; no to skip them

Comment

Separator on Windows: “;”

Separator on UNIX, IBM i: “:”

The importDirs parameter points to the directory where the R3load dump files are written. In the importDirs di­ rectory, the subdirectories DATA, DB, and DB/

<TARGET_DBTYPE>

(for example, DB/ORA) must exist.

This option is used only if the import monitor works with­ out the export monitor in standalone mode, that is, all ex­ port dump files are available on the import host before the import monitor is started.

Values can be:

● name:

Load packages in alphabetical order

● size:

Load packages starting with the largest one or a path of the file that contains the package names

If the option is omitted then the package order is not de­ fined.

Path or file name of DDL control file

The default is DDL

<DBTYPE> .TPL. If the file name is used without path, the DDL control file from the export DB sub­ directory is used.

File with mapping between DDL files and package names

Optional; default is R3load.

If only the name of the R3load executable is available, the

JVM looks for the R3load executable using operating sys­ tem-specific search rules for the process.

Before version 4.6, this must be set to no .

Starting from version 4.7, it must be set to yes .

If the R3load task files *.TSK already exist, the monitor does not overwrite them.

Add EXT file entries to cmd files.

If the EXT files cannot be found in the DB/

<TARGET_DBTYPE>

import dump subdirectory, the pack­ age processing is aborted.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Option Description Comment dbCodepage migrationKey omit taskArgs loadArgs

Database code page for the target database

Migration key -

See SAP Note 552464 .

Possible values are: 4102, 4103, 1100

R3load omit value

Can contain only DTPIV letters.

-o D: omit data; do not load data

-o T: omit tables; do not create tables

-o P: omit primary keys; do not create primary keys

-o I: omit indexes; do not create indexes

-o V: omit views; do not create views.

If you want to combine several omit options, list these op­ tions without blank (for example,-o TV).

Additional R3load argu­ ments for the TASK phase

Appended to the R3load command line

The following options are already set by the monitor:

-ctf; -l; -o (if the omit argument is specified).

Additional R3load argu­ ments for the LOAD phase

Appended to the R3load command line

The following options are already used by the monitor:

-i; -dbcodepage; -l; -p; -k; -r; -socket (if the socket option is specified);

-o (if the omit argument is specified and task files are not used, that is, the value of tskFiles option is no).

jobNum decluster (use this option only for target dbType = HDB)

Number of parallel import jobs; the default is 1.

Any positive number; 0 for an unlimited number of jobs

You can change the value dynamically at runtime.

false Possible values : true or false

If this option is true – migmon calls R3laod with option – decluster.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

123

Option Description ignorePackageSizeCalcula tion

Default is false collectLogicalPackages Default is false

Table 27: Import Exchange Options

Option Description exchangeDir Exchange directory

Comment

Possible values : true or false

Use this option if you see performance issue in the time be­ fore starting the first import jobs. The first task of the Mi­ gration Monitor is to collect all packages that are men­ tioned in the table line for the importDirs parameter.

In this first step, called CollectPackages, the Migration

Monitor also calculates the package size. If the packages are spread over many mounted locations this can take some time. To improve the performance of the

CollectPackages step, set this option to

true

. Later the packages are imported without following “size ordering” of packages. Use this option only if there is a big delay during the start of the first import jobs.

Possible values : true or false Import Migration Monitor is extended with this option for processing “logical” pack­ ages.

To one standard package corresponds either one STR or one WHR file (for example, SAPAPPL1.STR,

REPOSRC-1.WHR).

To one “logical” package corresponds either one

STR.logical or one WHR.logical file (for example

SAPCLU4.STR.logical, SAPCDCLS-1.WHR.logical).

The logical packages are located in the same directory where the standard packages are located, for example importDirs/ABAP/DATA. Set this option to

true

if an import is running on SAP HANA database (HDB) and an export was run with the decluster=true option.

Comment

If this option is not set, the monitor runs in standalone mode, that is, without the export monitor. All the export dump files or the

SAP export media from the installation kit must be available on the import host and be specified with the importDirs parameter

(for example, in the properties file).

If there is an old export_statistics.properties file (for ex­ ample, from a previous export run), remove this file.

124

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Table 28: Import Socket Options

Option socket port

Description

Socket operating mode

Server port number

Any other option is ignored by the import monitor.

Comment

-

Any free port from 1024 to 65535.

Mandatory Options for Import Monitor

● Server mode (default): installDir, importDirs, tskFiles, extFiles, one of the options exchangeDir or socket (and their related parameters)

● Standalone mode: installDir, importDirs, tskFiles, extFiles

● IBM i-specific: loadArgs= -nojournal

Note

The value of the dbType option is determined automatically in the shell script or batch files from the dbms_type environment variable.

Dynamic Control of Import Monitor for the SAP HANA database

The migmonCtrl add-on (migmonctrl.jar) was created to dynamically adjust the load of the SAP HANA database during the import. It measures the load of the database in short intervals and makes adjustments to the order_by.txt file. The Migration Monitor uses the orderBy option in this scenario and starts new

R3load jobs accordingly.

Options for the MigmonCtrl Add-On

The following options are set in file import_monitor_cmd.properties or can be added on the command line.

Table 29:

Option Description Comment username password host

User name of database user

Password of the database user

Database host

-

-

-

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

125

Option instanceNumber createTablesOnly

Description Comment

Instance number in two-digit format The instance number must be in twodigit format, for example 02.

Special mode forf Landscape Reorg scenario

This option is used for the first step in the Landscape Reorg scenario when the Migration Monitor creates all tables without importing any data.

Options for File migmonctrl_cmd.properties

MigmonCtrl creates a file migmonctrl_cmd.properties during startup if it does not exist. It reads through the file during every 5 seconds. Parameters can be changed during the run to manual do adjustments to the configuration.

Table 30:

Option Description Comment loadRowstoreSeparate memoryFactor

Load Rowstore tables after the

Columnstore tables

Default is set to false.

This parameter is only read once dur­ ing startup.

Factor to multiply the size of running

R3load jobs to have a memory cushion in the database for Merge operations

By default this value is set to 2.

initialLargeJobNum initialSmallJobNum smallJobWeight coreMultiplicator

Initial and minimum number of R3load jobs for group Large

By default this value is set to 5.

Initial and minimum number of R3load jobs for group Small

By default this value is set to 5.

Factor to calculate the ratio between number of jobs in group Large and

Small

By default this value is set to 6.

This means when the number of jobs in group Large is increased by 1, 6 jobs must be added to group Small before the number of jobs in group Large is increased again.

Factor to calculate the maximum num­ ber of R3load jobs

By default this value is set to 4.

Deprecated

126

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Option maximumJobNum jobNumRowstore pause customGroupLarge customGroupMedium customGroupSmall

Description

Maximum number of jobs in total

Comment

By default this value is set to 100. Only jobs from group Large, Small and

Rowstore are taken into account.

The number of jobs the Migration Moni­ tor starts in total might be slightly higher than this value as post jobs for split tables are not taken into account.

Amount of R3load jobs set for the

Rowstore group in case the

Columnstore tables on the master host are loaded

Sets Migmonctrl to pause mode where no changes are done to file order_by.txt

By default this value is set to 100

By default this value is set to false.

Separate groups for packages

Ifyou want to load a single package right from the start or with a defined number of jobs, you can add it to one of these groups.

Comma separated line customGroupLarge=REPOSRC

,SAPSDIC Order_by.txt

[REPOSRC] jobNum=...

REPOSRC-1 REPOSRC-...

[SAPSDIC] jobNum...

SAPSDIC

Fixed number of R3load jobs for the groups

customGroupLargeJobNum customGroupMediumJobNum customGroupSmallJobNum jobDependencies Packages that need to be loaded after each other can be defined here. Pack­ ages defined here must be also defined as customGroup

Example jobDependencies=REPOSRC,

SAPSDIC

SAPSDIC is started after REPOSRC has finished.

Mandatory Options for Dynamically Control of Import Monitor

Server mode (default): username, password, host, instanceNumber, importDirs, order_by

Note

The value of the dbType option is determined automatically in the shell script or batch files from the dbms_type environment variable.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

127

The Migration Monitor is started when the dyn_control_import_monitor.sh script is executed with the migmonctrl.jar in the classpath. This means that migmonctrl runs as a single thread within the

Migration Monitor. You do not have to start the Migration Monitor separately.

8.1.3 Assigning DDL Files to Packages

Use

It is possible to use several different DDL*.TPL templates during the export or import. The assignment of a specific DDL file to a single package is done within a simple text file, which then has to be specified using the ddlMap option within the properties file of the Migration Monitor. Packages not listed in the DDL mapping file use the default DDL control file.

Example

DDL Mapping File

# DDL mapping file ddl_mapping.txt # !!! line with [GROUP_NAME] can be skipped # used for documentation purposes only [ SORTED UNLOAD ] # DDL file for sorted unload ddlFile = /export_dump/ABAP/DB/ORA/DDLORA.TPL # package names SAPAPPL0

SAPAPPL1 SAPSDIC [ UNSORTED UNLOAD ] DDL file for unsorted unload ddlFile = ./

DDLORA_LRG.TPL # table names TABLE_A TABLE_B TABLE_C

8.1.4 Defining Groups of Packages

Use

The “package group” feature is an enhancement to defining a package order. By defining groups, you can for example prevent certain packages being executed in parallel and you can define how many large tables are exported or imported at the same time. In addition, you can specify different values for the parameters jobNum and taskArgs or loadArgs for each package. Package groups can be defined in the same text file in which the package order can be defined (see parameter orderBy). The previous package order format is also fully supported.

A group starts with any arbitrary name in brackets and ends when the next group starts.

If package groups are defined, the maximum number of parallel R3load jobs is the sum of jobNum of all packages. All packages without a package group will be assigned to a “default group” with the number of jobs that was defined in the properties file of the Migration Monitor.

Caution

Package groups defined with the orderBy parameter ignore the SAPVIEW and SAP0000 packages.

128

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Example

Package Order File with Group

# custom package order # package names SAPAPPL0 SAPAPPL1 SAPAPPL2 # package group [ SEQUENTIAL GROUP ] jobNum = 1 # table names TABLE_A TABLE_B TABLE_C

8.1.5 Processing Split Tables

If tables have been split during the export, ensure before the import starts that the table exists (only once) and that the primary key and the indexes are created (only once) before or after (as defined in the DDL template) the table data has been imported. These tasks are automatically synchronized by the Migration Monitor.

WHR files are part of the package and have to be copied to the DATA export subdirectory to make sure that the same WHR file is used for the export and import of the corresponding package.

The following database platforms do not support parallel data import:

● IBM DB2 UDB for UNIX and Windows

You can ensure this by using the Defining Groups of Packages [page 128] feature.

Example

The target database does not support parallel data import. This example is valid for all database platforms:

During the export you have split the table MY_FIRST_TABLE into 3 packages and MY_SECOND_TABLE into 5 packages. Now you want to run a maximum of 10 R3load processes for parallel data import.

Create the file inputFile.txt with the following content:

[ MY_FIRST_TABLE ] jobNum = 1

MY_FIRST_TABLE-1

MY_FIRST_TABLE-2

MY_FIRST_TABLE-3

[ MY_SECOND_TABLE ] jobNum = 1

MY_SECOND_TABLE-1

MY_SECOND_TABLE-2

MY_SECOND_TABLE-3

MY_SECOND_TABLE-4

MY_SECOND_TABLE-5

In this file, you can also define the processing order of packages or you can assign DDL files to packages.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

129

The inputFile.txt file has to be specified as a value for the Migration Monitor parameter orderBy.

An R3load job is started for every group (MY_FIRST_TABLE and MY_SECOND_TABLE). The number of parallel R3load jobs is the total of the number of R3load jobs of each group plus the number of R3load jobs defined for the default group (which is made up of all packages without an explicit group name) defined by the parameter jobNum.

In this example, the parameter jobNum in the import_monitor_cmd.properties file has to be set to 8 to ensure that no more than 10 R3load processes run in parallel.

Procedure

Re-Starting the Import of a Split Table Package

If the import of a package fails, the rows that belong to this package have to be deleted using the WHERE condition assigned to this package before the data import is started again. The deletion with a WHERE clause can be very time-consuming. Therefore, it is faster to delete all rows of the corresponding table manually and re-import all packages instead.

Only if the number of failed packages is low and a lot of the packages for this table have completed successfully, it might be faster to perform the automatic restart which includes the execution of a DELETE with

WHERE for each failed package.

The following steps describe the procedure in detail:

1. Identify the reason for the failure of the import of the packages.

2. Manually delete all rows of the table for which the import of one or more packages failed.

3. Remove the TSK files of all packages that import data into this table (<table name>-

<counter>__TPI.TSK). Do not remove the TSK files that create either the table or the indexes for this table.

4. Adapt the file import_state.properties in the installation directory. Replace the status “+” of all packages for the corresponding table that had been imported successfully and has to be re-imported by

“0”.

For more information, see

Restarting R3load Processes [page 80]

.

5. Restart the import.

8.1.6 Starting the Migration Monitor

Use

The Migration Monitor has to be started on the source database host (export monitor) and on the target database host (import monitor).

You can start it using one of the following methods:

● The UNIX shell scripts export_monitor.sh / import_monitor.sh

● The Windows batch files export_monitor.bat / import_monitor.bat

130

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

● As part of the export / import procedure of software provisioning manager 1.0

You can specify options in the command line or in the export or import property files, as described in

Configuration [page 112] . The names of the property files are export_monitor_cmd.properties and

import_monitor_cmd.properties. Templates for these files are included in the application archive and must be located in the current user's working directory.

Any options specified in the command line take precedence over the corresponding options in the application property file. Options are case-sensitive, that is, options that are not recognized are ignored.

Prerequisites

● Make sure that the export dump directory and its subdirectory exist as described in the following table:

Table 31:

Directory Description

<export dump dir>/DATA

<export dump dir>/DB

<export dump dir>/DB/

<DBTYPE>

Contains the STR files generated by R3ldctl

Contains the DDL<DBTYPE>.TPL files generated by R3ldctl

Contains the EXT files generated by R3szchk (optional)

● Make sure that the export dump directory can be accessed from the target host, either using a shared directory (local to the export host) or by using Migration Monitor's FTP feature.

Procedure

1. Start the tool in one of the following ways:

○ Use the following commands depending on your operating system:

○ UNIX shell scripts export_monitor.sh / import_monitor.sh

○ Windows batch files export_monitor.bat / import_monitor.bat

○ IBM i-specific

1. Set the environment variable

PASE_THREAD_ATTACH to “Y”

using:

ADDENVVAR PASE_THREAD_ATTACH 'Y'

2. Run the command:

CALL QP2TERM

3. ./export_monitor.sh / ./import_monitor.sh

○ Automatically as part of the installer export and import procedure

○ Manually within the installer:

1. On the

Parameter Mode Default Settings

installer screen, choose

Custom

.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

131

2. On the

SAP System Export for Target System

screen, select

Start Migration Monitor Manually

.

3. The installer stops and asks you to start the Migration Monitor manually and to continue with the installer as soon as the Migration Monitor has finished successfully.

Note

If you use FTP access and security is required, start the Migration Monitor in secure mode to prevent seeing the FTP password in the command line parameter string or in the property file (for example, on

UNIX or IBM i: ./export_monitor_secure.sh –ftpPassword

<password>

).

For more information about FTP, see

FTP Exchange Options

and

FTP Copy Options

in Configuration

[page 112] .

2. Close the shell window or command processor. The monitor process runs in the background.

3. Specify options as required in one of the following ways:

○ In the command line:

Specify the option in the format:

-optionName optionValue

○ In the application property file:

Add an option as a new line in the format:

optionName=optionValue

Example

Command line for UNIX or IBM i:

./export_monitor.sh –ftp

./export_monitor.sh –ftpCopy

./export_monitor.sh –socket –host <import_server> –port 5000

Example

Command line for Windows cmd.exe: export_monitor.bat –net export_monitor.bat –socket

4. Use monitor*.log and *.console.log files to check the monitor processing state.

Example export_monitor_cmd.properties file with export options:

# Export Monitor options

# Operating mode: ftp | net

#net ftp

#

# Common options

#

132

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

# List of export directories, separator on Windows ; on UNIX,IBM i: exportDirs=C:\TEMP\export_dump

# SAPinst start directory installDir=C:\install\start

# Monitor timeout in seconds monitorTimeout=30

#

# FTP options

#

# Remote FTP host ftpHost=server

# Name of remote FTP user ftpUser=sysadm

# Password of remote FTP user ftpPassword=password

# List of remote FTP directories for export dump, separator : or ; ftpExportDirs=/install_dir/export_dump

# Remote FTP exchange directory ftpExchangeDir=/install_dir/exchange

# Number of parallel FTP jobs ftpJobNum=3

#

# E-mail options

#

# SMTP server mailServer=sap-ag.de

# "From" email address [email protected]

# "To" email address [email protected] [email protected]

Example import_monitor_cmd.properties file with import options:

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

133

# Import Monitor options

#

# Common options

#

# List of import directories, separator on Windows ; on UNIX,IBM i: importDirs=/install_dir/export_dump

# SAPinst start directory installDir=/install_dir/start

# Exchange directory exchangeDir=/install_dir/exchange

# Generation of task files: yes | no tskFiles=yes

# Inclusion of extent files: yes | no extFiles=yes

# Monitor timeout in seconds monitorTimeout=30

#

# R3load options

#

# DB code page for the target database dbCodepage=1100

# Migration key migrationKey=

# Additional R3load arguments for TASK phase taskArgs=

# Additional R3load arguments for LOAD phase loadArgs=

# Number of parallel import jobs jobNum=3

#

# E-mail options

#

# SMTP server

134

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

mailServer=sap-ag.de

# "From" email address [email protected]

# "To" email address [email protected] [email protected]

8.1.7 Using the “migmonCtrl” Add-On for the Export

The add-on can be activated by starting the Migration Monitor with the following scripts and programs:

● The UNIX shell scripts dyn_control_export_monitor.sh

● As part of the export procedure of the software provisioning manager

UNIX – example for the export_monitor_cmd.properties file using sort by size: server dbType=ORA exportDirs=/hana/s2p_to_hana/exportDVD/ABAP installDir=. orderBy=./order_by.txt ddlFile=DDLORA_LRG.TPL r3loadExe=/hana/s2p_to_hana/ sapKernel/oracle/linuxx86_64/R3load tskFiles=yes dataCodepage=4103 jobNum=5 monitorTimeout=10 loadArgs=-continue_on_error trace=all migmonCtrl jobNumLarge=25 jobNumSmall=25 extFileDir=/hana/s2p_to_hana/exportDVD/ABAP/DATA

UNIX – example for the export_monitor_cmd.properties file using sort by time: server dbType=ORAexportDirs=/sapdb/exportDvD_741/ABAP installDir=/home/emroot/ export_plx110 orderBy=/home/emroot/export_plx110/order_by.txt ddlFile=DDLORA_LRG.TPL r3loadExe=/usr/sap/QO1/D01/exe/R3load tskFiles=yes dataCodepage=4103 jobNum=5 monitorTimeout=10 loadArgs=-continue_on_error trace=all migmonCtrl jobNumLarge=10 jobNumSmall=10 minRuntime=0 exportTimeFile=./ export_time.txt importTop=5 importTimeFile=./import_time.txt

Example

Example for a command line call to create package filter files:

./dyn_control_export_monitor.sh -createPackageFilter -outputFile package_list_

%hostName%.txt -hostNames plx101,plx110

UNIX – example for a export_monitor_cmd.properties file when using a package filter: server dbType=ORA exportDirs=/sapdb/exportDvD_741/ABAP installDir=/home/emroot/ export_plx110 orderBy=/home/emroot/export_plx110/order_by.txt ddlFile=DDLORA_LRG.TPL r3loadExe=/usr/sap/QO1/D01/exe/R3load tskFiles=yes dataCodepage=4103 jobNum=5 monitorTimeout=10 loadArgs=-continue_on_error trace=all decluster=true migmonCtrl jobNumLarge=10 jobNumSmall=10 extFileDir=/ sapdb/exportDvD_741/ABAP/DATA packageFilter=/sapdb/exportDvD_741/ABAP/DB/HDB/ package_filter_plx110.txt onlyProcessOrderBy=true

UNIX – example for an export_monitor_cmd.properties file when using a package filter and parallel export/import: server dbType=ORA exportDirs=/sapdb/exportDvD_741/ABAP installDir=/home/emroot/ export_plx110 orderBy=/home/emroot/export_plx110/order_by.txt

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

135

ddlFile=DDLORA_LRG.TPL r3loadExe=/usr/sap/QO1/D01/exe/R3load tskFiles=yes dataCodepage=4103 jobNum=0 monitorTimeout=10 loadArgs=-continue_on_error net netExchangeDir=/sapdb/exportDvD_741/SGN trace=all decluster=true migmonCtrl jobNumLarge=10 jobNumSmall=10 extFileDir=/sapdb/exportDvD_741/ABAP/DATA packageFilter=/sapdb/exportDvD_741/ABAP/DB/HDB/package_filter_plx110.txt onlyProcessOrderBy=true netStatisticsFile=package_filter_plx110.statistics

8.1.8 Using the migmonCtrl Add-On of the Import Migration

Monitor

Note

You can use the migmonCtrl add-on only when you have SAP HANA database as thetarget database. Make sure that the import_monitor_cmd.properties file has the following entry: dbType=HDB.

You can start the tool as follows:

● The UNIX shell scripts dyn_control_import_monitor.sh

● As part of the export / import procedure in the software provisioning manager

The application allows you to specify options in the command line. Options are case-sensitive; any options that are not recognized are ignored. To specify an option, enter the following in the command line:

-optionName optionValue

Example

Example of a command line for a UNIX terminal:

./dyn_control_import_monitor.sh -username myname -password mypass -host myhost instanceNumber 02 -

The application allows you to specify additional options in the application property file. The name of the property file is migmonctrl_cmd.properties. Templates for these files are included in the application archive and must be located in the working directory of the current user.

Example of a migmonctrl_cmd.properties file:

maximumJobNum=70

smallJobWeight=6

memoryFactor=2

minimumLargeJobNum=5

minimumSmallJobNum=5

initialLargeJobNum=15

initialSmallJobNum=15

coreMultiplicator=4

pause=false

jobNumRowstore=100

loadRowstoreSeparate=true

skipIsRelevantPackageCheck=false

###################################

# Default entries

# Comma separated string. Jobs from this definition are started one by one. Jobs must be also defined as Custom Group.

#jobDependencies=

# Number of R3load jobs for custom group[s] of type Small.

136

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

#customGroupSmallJobNum=0

# Number of R3load jobs for custom group[s] of type Medium.

#customGroupMediumJobNum=0

# Number of R3load jobs for custom group[s] of type Large.

#customGroupLargeJobNum=0

# Comma separated list which defines a group for each listed package.

#customGroupSmall=

# Comma separated list which defines a group for each listed package.

#customGroupMedium=

# Comma separated list which defines a group for each listed package.

#customGroupLarge=

8.1.9 Output Files

-

0

?

Export

● export_monitor.log

● export_state.properties

● ExportMonitor.console.log

Import

● import_monitor.log

● import_state.properties

● ImportMonitor.console.log

migmonCtrl add-on

● migmonctrl.log

● MigmonJobber.console.log

Both the export and import state files contain package state lines such as SAPUSER=+.

The format of state lines is

<PACKAGE> = <STATE>

. Possible values for state are listed in the following table:

Table 32:

Value Description

Package export/import not yet started

Package export/import in progress

Package export/import finished with errors

+ Package export/import finished successfully

If any ftp or net exchange options are used, then the export state file might contain a second

<STATE>

column that refers to the state of the package transfer.

Then the export state file contains package state lines such as SAPUSER=++.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

137

+?

+-

-

+0

++

0

?

The format of state lines is

<PACKAGE> = <STATE>

. Possible values for state are listed in the following table:

Table 33:

Value Description

Package export not yet started

Package export in progress

Package export finished with errors

Package export finished successfully; package transfer not yet started

Package transfer in progress

Package transfer finished with errors

Package transfer finished successfully

8.2 Analysis of the Export and Import Times

You can reduce the runtimes by splitting the packages in question or extracting long-running tables from the packages.

You can use the MIGTIME.SAR archive to analyze the runtimes of the individual packages. It is contained in the

<OS> /COMMON/INSTALL directory of the

70SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR archive. It is unpacked to the installation directory using SAPCAR and contains documentation in addition to the tools.

8.3 Table Comparison with Software Update Manager

This section describes how to compare table contents using the Software Update Manager 1.0 (SUM) tool during a system copy project.

We call this functionality “Table Comparison with SUM”. The tool only needs access to the database, so you can run it regardless of whether the ABAP system is running or not. The “Table Comparison with SUM” functionality is available as of Software Update Manager (SUM) 1.0 SP11.

Related Information

Modes of the Table Comparison Tool [page 139]

Restrictions [page 139]

138

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Using the Table Comparison Tool [page 140]

8.3.1 Restrictions

This section describes the cases when you cannot use Table Comparison with SUM.

You can only use Table Comparison with SUM:

● If both the source system and the target system use the same endian type. For details on the endian type of an SAP system, see SAP Note 552464 .

● If there has been no Unicode Conversion, that is no change from Non-Unicode to Unicode.

Related Information

Restrictions [page 139]

8.3.2 Modes of the Table Comparison Tool

You can run the table comparison tool either in “single” or “twin” mode.

The tool has the following modes of operation:

● In “single” mode, the tool only accesses the SAP database of the current system it is running on. This is supported for all database types supported by SAP. In this mode, the tool generates checksums for the selected user or for all SAP tables. The tool reports the directory containing the checksums at the end.

This directory must then be transferred to the target host. There the tool must be run again in “single” mode and must have read/write access to the previously generated checksum directory. It uses them as a reference and generates the corresponding checksums for the target database. Any discrepancy found is reported. checksums are only generated for ranges of rows, so the granularity of reported checksum differences is rather “coarse”.

“Single” mode means that you run the Table Comparison Tool with SUM separately and twice:

Single mode corresponds to the SUM options

Generate Export Checksums

(to be executed on the source system) and

Generate Import Checksums

(to be executed on the target system).

1. You execute SUM option

Generate Export Checksums

on the source system to create the checksums.

2. You execute SUM option

Generate Import Checksums

on the target system to verify the checksums by comparing them with the content of the tables in the target database.

● “Twin” mode is by default unavailable in a regular system copy because you cannot connect simultaneously from one application server to both the source and the target database system. Therefore we recommend using “single” mode.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

139

Related Information

Table Comparison with Software Update Manager [page 138]

8.3.3 Using the Table Comparison Tool

This section describes how to use the Table Comparison Tool.

Prerequisites

● Make sure that you run Table Comparison before the primary application server instance on the target system is started for the first time. Otherwise the comparison might return wrong results because table content was already updated when the instance was started.

● The database of the system for which you want to use the tool is up and running.

Make sure that

R3trans -x

works.

● You have downloaded the Table Comparison tool as described in SAP Note Central Note - Software Update

Manager 1.0 SP

<Latest_Number>

at https://support.sap.com/sltoolset

System Maintenance

.

● We strongly recommend that you do not perform productive operations while you apply table comparison with the Software Update Manager (SUM): Since the tool generates checksums, changing table contents might lead to incorrect results if you apply the tool while the system is running.

● Make sure that you have installed the latest version of the SAP Host Agent. For more information, see SAP

Note 1031096 and the

SAP Library for your release [page 13] at:

Function-Oriented View Solution

Life Cycle Management by Key Capability SAP Host Agent

.

● Make sure that you have configured SUM so that it works together with the SAP Host Agent:

1. Log on as user root and call the SUMSTART script as follows:

<SUM_Directory>/abap/SUMSTART confighostagent

If you are working with symbolic links for the SUM directory, you need to call the SUMSTART script with the logical path information.

2. Restart the SAP Host Agent using the following command:

<HOSTAGENT_Directory>/exe/saphostexec -restart

Procedure

1. Log on as user

<sapsid> adm.

2. Unpack the SUM archive by executing the following commands:

mkdir <SUM_Directory> cd <SUM_Directory>

SAPCAR -xvf SUM.SAR

140

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Example

mkdir /usr/sap/put cd /usr/sap/put

SAPCAR -xvf SUM.SAR

3. Proceed as follows to start SUM using the SAP Host Agent: a. Open a browser window and enter the following URL in the address bar:

https://<hostname>:1129/lmsl/migtool/<SAPSID>/doc/sluigui

Note

○ 1129 is the https port of the SAP Host Agent.

○ Use http instead of https if SSL is not configured. In this case, the URL you have to enter looks as follows:

http://<hostname>:1128/lmsl/migtool/<SAPSID>/doc/sluigui

b. A dialog box appears in which you enter as user name the

<sapsid> adm and the password.

After logon, the SAP Host Agent starts SUM by calling the SAPup executable in the background.

From a technical point of view, the SAPup executable is started twice, as can be seen from the process list:

○ One entry with gt=httpchannel represents SAPup handling the requests coming from SAP Host

Agent.

○ The second SAPup with parameter guiconnect is triggering tools such as R3trans, tp, or

R3load.

SUM starts with the SAPUI5-based user interface.

The initial screen is displayed.

4. On the initial screen, you can choose between the following options, which both work in “single” mode:

○ Generating export checksums

This is the option for checking tables in the source system.

○ Generating import checksums

This is the option for checking tables in the target system.

You cannot use the option for direct table content check for system copy purposes

5. You can specify the tables for which you want to compare content on the source and target system:

○ Compare all tables

When you decide to perform a full comparison, it is strongly recommended to exclude some tables where the content is changed during a regular system copy. Otherwise the verification for these tables fails. Create a file in the directory

<SUM_DIR> /abap/bin before you run the export.

Name this file EUCLONEDEFS_ADD.LST and enter the following content :

DDNTT nocontent igncrcdiffs

REPOLOAD nocontent igncrcdiffs

The list of tables to be ignored in the comparison check can be modified according to individual requirements, for example, if it is clear that the table has been changed on the target system and the difference is expected.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

141

It is also possible to run the check on the target system without the modification. If an error is raised on the two tables mentioned above, you can ignore the comparison check differences and continue

SUM in the dialog.

○ Provide a list of tables

If you only want to check a selected number of tables, provide an input file like this:

$ cat /tmp/CRCTableList.lst # Tables to be checked TAORA IAORA

Enter the full path to this file in the input field provided.

6. If no error occurs, you are informed that the tool has generated the checksum in the specified directory.

a. You can now move the directory to a host that has access to your target database.

b. Rerun the tool on the target system with option

Generate Target Checksums

. Before you rerun the tool, make sure that the primary application server instance is stopped.

This time you have to provide the path to this directory in the

Table List

field.

7. Verify the result of the table comparison. If the differences in the table contents of the source and target system are inconsistent, and you cannot explain the differences - for example, due to changes in the target system during the table comparison check on the source system - open an incident on component BC-

INS-MIG.

Related Information

Table Comparison with Software Update Manager [page 138]

8.4 Using the Package Splitter

Here you find information what you can do with the Package Splitter tool.

You can use the Package Splitter tool for splitting the following:

● STR/EXT files

● STR files

● WHR files

The tool is located in the SPLIT.SAR archive in the /

<OS> /COMMON/INSTALL folder in the directory structure of software provisioning manager 1.0.

Content of the archive file:

● split.jar

● str_splitter.sh / str_splitter.bat

● where_splitter.sh / where_splitter.bat

142

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Related Information

Configuration [page 143]

Starting the Package Splitter [page 146]

Executing the STR Splitter and the WHERE Splitter [page 148]

Output Files [page 147]

8.4.1 Configuration

Here you find information about command line options of the Package Splitter tool.

Help

The tool displays the available parameters, if you call it with one of the following command line options:

●

-help

●

-?

Version

The tool will display the version information (release branch and build date), if you call it with the following command line option:

-version

STR Splitter Options

Table 34:

Option strDirs

Description

List of STR file directories extDirs List of EXT file directories

Comment

Separator on Windows:

;

Separator on UNIX:

:

Separator on Windows:

;

Separator on UNIX:

:

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

143

Option outputDir top tableLimit packageLimit tableFile maxNumberOfTables

Description

Output directory

Maximum number of tables

Table size limit in MB

Package size limit in MB

Comment

If missing, then the directories that contain the corresponding STR/EXT files are used.

Largest N tables are extracted from the packages.

All tables larger than tableLimit are ex­ tracted from packages.

All packages larger than packageLimit are split into packages smaller than this limit.

File with the table names that are to be extracted

All tables from the file are extracted from the packages. This file must con­ tain the table names on separate lines

(one name on each line).

● Integer value

● Maximum number of tables in the package

Split the packages as keep the maxi­ mum number of tables in package.

Example maxNumberOfTables=500

This parameter is with higher prior­ ity

WHERE Splitter Options

Table 35:

Option whereDir strDirs

Description

WHERE file directory

List of STR file directories outputDir Output directory

Comment

Directory with WHR files.

Separator on Windows:

;

Separator on UNIX:

:

If missing, then the directory that con­ tains the corresponding WHR files is used.

144

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Option whereLimit whereFiles

Description Comment

Maximum number of WHERE clauses All WHR files that have more than whereLimit WHERE clauses are split into WHR files with whereLimit WHERE clauses.

Whitespace separated list of WHR files Names of WHR files to be split. WHR files should exist in WHERE file direc­ tory.

Trace Option

Table 36:

Option trace

Description

Trace level

Comment

Possible values:

all

,

off

,

1

(error),

2

(warning),

3

(info),

4

(config, default),

5

,

6

,

7

(trace)

Mandatory Options

● Splitting STR and EXT files: strDirs, extDirs, top and/or tableLimit and/or packageLimit and/or tableFile

● Splitting STR files: strDirs, tableFile

● Splitting WHR files: whereDir, whereLimit

Related Information

Using the Package Splitter [page 142]

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

145

8.4.2 Starting the Package Splitter

Here you find information about how to start the Package Splitter tool.

You can start the Package Splitter tool using one of the following:

● UNIX shell script str_splitter.sh / where_splitter.sh

● As part of the export procedure (STR Splitter) in the installer

The application allows you to specify options in the command line and/or in the application property file. The name of the property file is package_splitter_cmd.properties.

Any options specified in the command line take precedence over the corresponding options in the application property file. Options are case-sensitive; any options that are not recognized are ignored. To specify an option:

● in the command line, enter

-optionName optionValue

● in the application property file, insert the new line

optionName=optionValue

STR Splitter

Example of a command line for a UNIX terminal:

Example

./str_splitter.sh -strDirs /export_dump/DATA -extDirs /export_dump/DB/ORA outputDir /split_output -top 20 -tableLimit 50 -packageLimit 200 -trace all

WHERE Splitter

You can start the tool using the UNIX shell script where_splitter.sh.

Example

Example of a command line for a UNIX terminal:

./where_splitter.sh -whereDir /r3a_dir -strDirs /export_dump/DATA -outputDir / split_output -whereLimit 5 -trace all

Related Information

Using the Package Splitter [page 142]

146

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

8.4.3 Output Files

Here you find information about the output files of the Package Splitter tool.

STR Splitter

● Newly split STR/EXT files

● Original backup of STR/EXT files (*.STR.old/*.EXT.old)

● SAPSTR.LST file

● str_splitter.log

● PackageSplitter.console.log

WHERE Splitter

● Newly split WHR files

● Original backup of WHR files (*.WHR.old)

● SAPSTR.LST file

● where_splitter.log

● PackageSplitter.console.log

STR Splitter Notes

SAP0000 and SAPVIEW packages are never modified by the splitter. SAPNTAB package is always created and contains 5 predefined tables:

SVERS, DDNTF, DDNTF_CONV_UC, DDNTT, DDNTT_CONV_UC

Integration

Before you start to split files, we strongly recommend that you back up your original STR/EXT or WHR files in separate backup directories. These backup files can be used later to try other splitting options. If the output directory is specified, then the newly split files are generated in this directory; otherwise they are generated in the directories where the corresponding original files are located.

The original backup files (backup name is

<file_name> .old) are always located in the same directories where the corresponding original files are located.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

147

Related Information

Using the Package Splitter [page 142]

8.4.4 Executing the STR Splitter and the WHERE Splitter

Proceed as described in this section to execute the STR Splitter / WHERE Splitter.

Procedure

1. Prepare the properties file package_splitter_cmd.properties (optional).

2. Start the Package Splitter tool using the shell script or batch file.

3. Analyze the screen output and log file.

Related Information

Using the Package Splitter [page 142]

8.5 Troubleshooting for Migration to SAP HANA

General Information

See the blog Migration to SAP HANA: Analyzing Problems within Software Provisioning Manager to get hints how to identify the root cause of issues during the classical migration procedure: http://scn.sap.com/ community/it-management/alm/software-logistics/blog/2013/10/04/migration-to-sap-hana-analyzingproblems-within-software-provisioning-manager

Caution

Only increase the trace level if this is requested by support for troubleshooting purposes. Increasing the trace level has negative impact on the performance of the system and of the SAP HANA database.

148

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Increasing the Trace Level of R3* Tool

If R3load or any other R3* tool stops, it may be useful to increase trace level and repeat the failing step. For this, set the following environment variables and rerun the tool:

● R3load:

R3LOAD_TL = 3

● R3ldctl:

R3LDCTL_TL = 3

● R3szchck:

R3SZCHK_TL = 3

Increasing theTrace Level of SAP HANA

Consider to increase the trace level for the SAP HANA SQLDBC client by using the following commands:

Table 37:

Action Command

./hdbclient/hdbsqldbc_cons trace sql on

Enable trace*

Refresh trace*

Disable trace

Locate trace

./hdbclient/hdbsqldbc_cons trace refresh

./hdbclient/hdbsqldbc_cons trace sql off

./hdbclient/hdbsqldbc_cons show config

*) While “enable trace” enables the tracing only for newly started processes, “refresh trace” enables the tracing also for already running processes.

Checking Troubleshooting Information in SAP Notes

In addition to the SAP Notes for the migration procedure listed in the previous sections, here is a selection of further SAP Notes containing information for specific issues:

● SAP Note

1722395 (SAP HANA: Known problems) lists known issues that may occur during a migration to SAP HANA.

● SAP Note

1860493 (Out of memory during import migration to HANA) in case you are facing an out-ofmemory error during the migration to SAP HANA.

● SAP Note

1641210 (SAP HANA database: Checking for suspected problems) provides a checklist how to investigate a potential problem in the SAP HANA database.

Open an Incident

See SAP Note 752505 (SAP System Provisioning / Installation Problems). It describes the log files and which information is required in an SAP incident message so that it can be efficiently processed. With this

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

C U S T O M E R

149

information, create an SAP incident with a direct connection to the customer system under the following component:

● In case of migration tool issues: BC-INS-MIG-TLA

● In case of general migration procedure issues: BC-INS-MIG

● In case of database-related issues: BC-DB-HDB-INS

150

C U S T O M E R

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Additional Information

Important Disclaimers and Legal Information

Coding Samples

Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

Accessibility

The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral Language

As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as

"sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks

The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer ).

Open Source Software and Third Party Components

Please refer to https://scn.sap.com/docs/DOC-42044 for information respecting open source software components made available by SAP as part of SAP

NetWeaver and any specific conditions that apply to your use of such open source software components. Please refer to https://scn.sap.com/docs/DOC-42045 for information relating to SAP’s use of third party software with or within SAP NetWeaver.

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.5 on UNIX : SAP HANA Database

Important Disclaimers and Legal Information

C U S T O M E R

151

go.sap.com/registration/ contact.html

© 2017 SAP SE 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 SE or an SAP affiliate company. 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. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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 SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see http://www.sap.com/corporate-en/legal/copyright/ index.epx

for additional trademark information and notices.