140
System Copy Guide System Copy for SAP Systems Based on SAP NetWeaver 7.3 ABAP Target Audience System administrators Technology consultants PUBLIC Document version: 1.5 – 2011-12-15

System Copy NW 7.3

Embed Size (px)

Citation preview

Page 1: System Copy NW 7.3

System Copy GuideSystem Copy for SAP Systems Based on SAP NetWeaver 7.3 ABAP

Target Audience ■ System administrators ■ Technology consultants

PUBLICDocument version: 1.5 – 2011-12-15

Page 2: System Copy NW 7.3

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.

You can find the latest version on SAP Service Marketplace http://service.sap.com/

instguides.

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

Version Date Description

1.5 2011-12-15 Minor updates

1.4 2011-12-10 Minor updates

1.3 2011-11-07 Updates in Activities at SAP System Level, Transferring Export Files to the Target System; SAP HANA database

1.2 2011-01-18 Update in Activities at Database Level and Installing the Target System

1.1 2011-12-02 Formal update

1.0 2010-11-29 Initial version

2/140 PUBLIC 2011-12-15

Page 3: System Copy NW 7.3

Table of Contents

Chapter 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based

on SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.3 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.4 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 3 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.1 General Technical Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2 Usage-Type-Specific Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.3 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 4 Database Independent System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.1 System Copy Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.2 Generating DDL Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.3 Preparation for Table Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.4 Preparing Parallel Export and Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4.5 Exporting the Source System Using SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.5.1 Running SAPinst on UNIX or Windows to Perform the Export . . . . . . . . . . . . 29

4.5.2 Running SAPinst on IBM i to Perform the Export . . . . . . . . . . . . . . . . . . . . . . 32

4.5.2.1 Starting SAPinst on IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4.5.2.2 Preparing an IBM i User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4.5.2.3 Copying the Installation Media Manually to Your IBM i . . . . . . . . . . . . . . . . . 37

4.5.3 Restarting R3load Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.6 Setting Up the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.6.1 Transferring the Export Files to the Target Host . . . . . . . . . . . . . . . . . . . . . . . 41

4.6.2 Installing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter 5 Database-Specific System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

5.1 Oracle-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

2011-12-15 PUBLIC 3/140

Page 4: System Copy NW 7.3

5.1.1 Generating the Control File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5.1.2 Creating a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5.1.2.1 Creating an Offline Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5.1.2.2 Creating an Offline or Online Backup with BR*Tools . . . . . . . . . . . . . . . . . . . 52

5.1.3 Preparing the Target System (Oracle) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5.1.4 Restoring the Database Files on the Target System . . . . . . . . . . . . . . . . . . . . . 55

5.1.5 Restoring the Database Files on the Target System with BR*Tools . . . . . . . . . 56

5.2 SAP MaxDB-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.3 MS SQL Server-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

5.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures . . . . . . . . . . . . . 60

5.5 IBM DB2 for i Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.6 IBM DB2 for z/OS Specific Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.6.1 Step 1: Check Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.6.2 Step 2: Stop and Restart the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.6.3 Step 3: Run SQL Statements in the Source System . . . . . . . . . . . . . . . . . . . . . . 68

5.6.3.1 SQL Statement Number 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.6.3.2 SQL Statement Number 02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

5.6.3.3 SQL Statement Number 03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

5.6.3.4 SQL Statement Number 04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

5.6.3.5 SQL Statement Number 05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

5.6.3.6 SQL Statement Number 06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

5.6.3.7 SQL Statement Number 07 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

5.6.3.8 SQL Statement Number 08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5.6.3.9 SQL Statement Number 09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

5.6.4 Step 4: Capturing View Definitions with DB2 V9 (if the Schema Name is to be

Changed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

5.6.5 Step 5: Stop the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

5.6.6 Step 6: Making Copies of Source Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

5.6.7 Step 7: Creating the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

5.6.8 Step 9a: Changing the Bootstrap Data Sets (BSDS) . . . . . . . . . . . . . . . . . . . . . . 77

5.6.9 Step 9b: Start the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.6.10 Step 9c: Creating a New STOGROUP Using the HLQ of the Target

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

5.6.11 Step 9d: Stopping Index Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

5.6.12 Step 9e: Changing the User-Defined Indexes in the DB2 Catalog . . . . . . . . . . . 79

5.6.13 Step 9f: Restart the Index Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

5.6.14 Step 9g: Creating the Temporary Files for the DB2 Target System . . . . . . . . . . 79

4/140 PUBLIC 2011-12-15

Page 5: System Copy NW 7.3

5.6.15 Step 9h: Implementing HLQ of the Target System in the Work File

Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

5.6.16 Step 9i: Adjusting the DDF Location Name and Port Number . . . . . . . . . . . . . 80

5.6.17 Step 10 (DB2 V8 and Lower): Changing the VCAT of the Target

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

5.6.18 Step 10 (DB2 V9): Changing the VCAT of the Target System . . . . . . . . . . . . . . 81

5.6.19 Step 11 (DB2 V9): Changing the Schema of the Target System . . . . . . . . . . . . 81

5.6.20 Step 12: Adapting WLM Application Environments for DB2 Stored

Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 6 Copying Single Instances Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

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

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

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

Chapter 7 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

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

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

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

7.2.1.1 Activities at Operating System Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

7.2.1.2 Activities at Database Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7.2.1.3 Activities at SAP System Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7.2.1.4 Usage Type or Software Unit-Specific Follow-Up Activities . . . . . . . . . . . . . . . 92

7.2.1.4.1 Business Warehouse (BW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

7.2.1.4.2 Embedded Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

7.2.1.5 Checking the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

7.2.2 Performing Jobhead Correction after Homogeneous System Copy . . . . . . . . . 94

Chapter 8 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

8.1 R3load Procedures Using the Migration Monitor . . . . . . . . . . . . . . . . . . . . . . . 95

8.1.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

8.1.2 Assigning DDL Files to Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

8.1.3 Defining Groups of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

8.1.4 Processing Split Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

8.1.5 Starting the Migration Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

8.1.6 Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

8.1.7 Restarting R3load Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

8.1.8 Installing the Target System Using the Migration Monitor . . . . . . . . . . . . . . 112

2011-12-15 PUBLIC 5/140

Page 6: System Copy NW 7.3

8.2 Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

8.2.1 Useful Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

8.2.2 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

8.2.3 Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . 121

8.2.4 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

8.2.5 Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

8.2.6 Entries in the Services File Created by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . 130

8.2.7 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

8.2.8 Troubleshooting During the Database Load . . . . . . . . . . . . . . . . . . . . . . . . . . 132

6/140 PUBLIC 2011-12-15

Page 7: System Copy NW 7.3

1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver

Purpose

This document explains how to copy SAP systems in one run using either database-independent

methods or database-specific methods.

CAUTION

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 if you are a certified system support consultant or a certified SAP Technical

Consultant.

1.1 Terminology

■ System Copy

Duplication of an SAP system. Certain SAP parameters might change in a copy. When you perform

a system copy, SAPinst 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 the system copy, you use the same operating system and database platform as the original

system.

■ Heterogeneous System Copy

During the system copy, you change either the operating system or the database system, or both.

Heterogeneous system copy is a synonym for migration.

■ Database Copy

Database-dependent part of the system copy.

■ Placeholders

1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver

1.1 Terminology

2011-12-15 PUBLIC 7/140

Page 8: System Copy NW 7.3

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:

Placeholder Meaning How to find out

<SAPSID> SAP system ID —

<S_HOST> System name of the source host Command hostname

<T_HOST> System name of the target host Command hostname

<S_SAPSID> SAP system ID of the source system <SAPSID> of the original system

<T_SAPSID> SAP system ID of the target system <SAPSID> of the target system

<S_DBSID> Database ID of the source system <DBSID> of the original system

<T_DBSID> Database ID of the target system <DBSID> of the target system

1.2 Online Information from SAP

Before you start the system copy, you must read the documentation that is referenced in the following:

■ Read the following SAP Note for up-to-date information on system copy and corrections to the

system copy documentation:

SAP Note 1490839 (System Copy for SAP NetWeaver Based on Kernel 7.3)

Make sure that you have the most recent version of the SAP Note, which you can find at

http://service.sap.com/notes.

■ This documentation describes only the export of the source system in detail. For the installation

of the target system, you also need the installation guide for your SAP application. Installation

guides are available at

http://service.sap.com/instguides.

NOTE

If you have problems during the system copy, create a customer message using the application

area BC-INS-MIG.

More Information

■ SAP System Copy and Migration at http://service.sap.com/systemcopy

■ SAP OS/DB Migration Check at http://service.sap.com/osdbmigration

In addition to the information contained on this page, check the SAP OS/DB Migration Planning

Guide that is available in the Media Library.

■ SAP system landscape copy:

● Best Practice document SAP System Landscape Copy for SAP NetWeaver and SAP Solutions at http://

service.sap.com/solutionmanagerbp

● SAP Note 885343 – SAP System Landscape Copy

■ SAP Note 82478 – R/3 OS/DB migration

1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver

1.2 Online Information from SAP

8/140 PUBLIC 2011-12-15

Page 9: System Copy NW 7.3

1.3 Accessing the SAP Library

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

on SAP Help Portal:

http://help.sap.com/nw73 Application Help SAP Library: English SAP NetWeaver

1.4 Constraints

■ As of SAP NetWeaver 7.0, when your system is a dual-stack system and you perform a system copy,

your source system is copied to the target system as a whole. This means that it is neither possible

to exclude a single stack from the system copy nor to copy a separate stack only.

■ 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.

■ 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 convert a non-Unicode system to a Unicode system or perform the system copy of

a Unicode system, see SAP Note 551344.

■ 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 System

Landscape Optimization at http://service.sap.com/slo.

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.

In all other cases, contact SAP SLO at http://service.sap.com/slo or

[email protected].

1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver

1.3 Accessing the SAP Library

2011-12-15 PUBLIC 9/140

Page 10: System Copy NW 7.3

■ When you perform a system copy, all software units in the source system are copied to the target

system. This means that none of the software units in the target system can be excluded from the

system copy, nor can you select software units.

■ 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 SystemID and SID (SAPSID = SID = system name)

▶ Host name

▶ 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.

1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver

1.4 Constraints

10/140 PUBLIC 2011-12-15

Page 11: System Copy NW 7.3

2 Planning

This section describes how to plan your system copy.

You can apply the system copy for the following:

■ Setting up system landscapes (where the SAP systems have different SAPSIDs).

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

NOTE

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

● You should perform upgrades in a test system first. This way you can identify customer-

specific problems that might result from modifications.

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.

■ 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:

■ Install all SAP systems, starting with the development system. Customize the development

system as described in the implementation documentation.

■ 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.

Creating A System Copy Plan

Create a plan to perform the system copy.

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

system copy.

2. 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:

2 Planning

2011-12-15 PUBLIC 11/140

Page 12: System Copy NW 7.3

■ 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

perform read/write actions only on local file systems.

3. Define a schedule for the test run and the final system copy.

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.

Miscellaneous

■ 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.

■ Decide which system copy procedure you want to use:

● The database-independent procedure [page 21] using SAP tools

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

NOTE

For a database-heterogeneous system copy and for unicode conversion, only the

database-independent method is available.

● The database-specific procedure [page 45] using tools provided by the database vendor

Some database vendors offer specific tools for copying a database. These tools let you:

◆ Restore a backup of one database (source database) in another one (target database)

(backup method)

◆ Unload the source database and load the data into the target database

● Copy single instances only

◆ Copy the primary application server instance only [page 83].

◆ Copy the database only (using SAPinst) [page 83]

◆ Copy the database only (using database refresh) [page 85]

CAUTION

You cannot copy single usage types or components!

■ Changing the system variant

2 Planning

12/140 PUBLIC 2011-12-15

Page 13: System Copy NW 7.3

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 29].

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

the system copy procedure [page 22].

■ 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.

■ 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 9] at:

SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management SAP Licenses .

For more information about SAP license keys, see http://service.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 SAP Library [page 9] at:

SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Data Archiving (CA-

ARC) .

Access to archive files is platform-independent.

■ Configuration analysis and hardware analysis

You need to determine the:

● Number of application servers

● Expected size of the database

● Additional disks or other hardware required

● Required memory

NOTE

See the section on hardware and software requirements in the SAP system installation

documentation to determine the system requirements.

Usage-Type-Specific Planning Steps

SAP Business Warehouse (BW) only

As of SAP NetWeaver 7.3 Support Package 5, you can migrate your database to SAP HANA database if

the following conditions are met:

2 Planning

2011-12-15 PUBLIC 13/140

Page 14: System Copy NW 7.3

■ Your SAP system must meet at least the hardware and software requirements listed in the following

table:

Requirement Values

Hardware Your operating system platform must be 64-bit.

Operating System Version For a comprehensive list of supported operating system releases, see the Product Availability Matrix (PAM) at: http://service.sap.com/

pam .

Database Software The following source database platforms are supported: ● Oracle 11.2 ● MS SQL Server 2008 ● IBM DB for Linux, UNIX, and Windows V9.7 ● MaxDB 7.8 ● IBM DB2 for i 6,1, 7.1 ● IBM DB2 for z/OS V9, V10

SAP Kernel SAP Kernel 7.20 EXT 64–bit is installed.

SAP Java Virtual Machine (SAP JVM)

SAP JVM 6 is installed.

R3ldctl $Id: //bas/720_REL/src/R3ld/R3loadctl/R3loadctl.c#8 $Compilation date: August 2 2011 22:22:02

R3load R7.20/V1.4 [UNICODE]Compilation date: August 2 2011 22:21:38

■ SAP HANA database is available for SAP NetWeaver 7.3 ABAP only. Note that if your system is

based on SAP NetWeaver 7.3 ABAP+Java, you can run SAPinst to export and import the database

copy only for the ABAP stack.

2 Planning

14/140 PUBLIC 2011-12-15

Page 15: System Copy NW 7.3

3 Preparations

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

3.1 General Technical Preparations

Procedure

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.

The following describes important preparations on the source system. For more information about

SAP system administration, see the SAP Online Documentation.

■ 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.

■ Before you start the export on your source system, check that your JAVA_HOME environment points

to a valid JDK version.

NOTE

In i5/OS, the installed JVMs available in QIBM/ProdData are queried and the best suited one is

chosen. If you want to use another JVM, you must set JAVA_HOME.

■ No canceled or pending update requests should be in the system. Check this by choosing Tools

Administration Monitor Update (transaction SM13).

If canceled or pending updates exist, you must update these again or delete them from all clients.

You can see whether canceled or pending updates exist by checking if table VBDATA contains any

entries.

Find the canceled or open updates as follows:

1. Call transaction SM13.

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

3. Choose all update requests.

If canceled or pending records exist, you must update these again or delete them. Check

whether this action was successful using transaction SE16 for table VBDATA.

■ Set all released jobs from Released to Scheduled:

Tools CCMS Background Processing Jobs - Overview and Administration (transaction SM37)

3 Preparations

3.1 General Technical Preparations

2011-12-15 PUBLIC 15/140

Page 16: System Copy NW 7.3

You also need to do this for jobs that must run periodically (see SAP Note 16083). Select all jobs

(include start after event) as follows:

Job Released Scheduled

■ Adapt the operation mode timetable to make sure that no switching of operating modes takes

place while a system is being copied as follows:

Call transaction SM63 or choose SAP Menu Tools CCMS Configuration Operation Mode

Calendar .

■ Write down the logical system names of all clients:

1. 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.

2. 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. If you are still planning your SAP NetWeaver Business

Warehouse system landscape, see SAP Note 184447.

3. 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).

Changes to logical system names are not required.

■ Before the export, delete QCM tables from your system as follows:

1. Before deleting you must always check 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

● 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.

■ 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) .

3 Preparations

3.1 General Technical Preparations

16/140 PUBLIC 2011-12-15

Page 17: System Copy NW 7.3

■ FI customers: 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:

● 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.

3.2 Usage-Type-Specific Preparations

This section includes the preparation steps that you have to perform for specific usage types.

3 Preparations

3.2 Usage-Type-Specific Preparations

2011-12-15 PUBLIC 17/140

Page 18: System Copy NW 7.3

Procedure

Business Warehouse (BW)

■ When planning the copy of an SAP NetWeaver system with BW, read SAP Notes 886102, 1333302,

and 543715.

■ Before you start the system copy export, delete the BIC/000APR* interim result tables in the source

system by running the report RSAN_UT_RESULT_DROP_RESULTS.

For more information, see SAP Note 1476120.

■ If you are planning to copy an SAP NetWeaver BW system with SAP HANA database, perform the

preparation steps described at:

● http://www.sdn.sap.com/irj/sdn/edw-ops Additional Information about the Lifecycle

Management with SAP NetWeaver BW 7.x SAP NetWeaver 7.0 – BW Systemcopy ABAP .

● http://www.sdn.sap.com/irj/sdn/edw-ops Additional Information about the Lifecycle

Management with SAP NetWeaver BW 7.x SAP NetWeaver 7.3 – BW Systemcopy ABAP .

■ If you are planning to migrate to SAP HANA database, perform the preparation steps described in

SAP Note 1600929.

3.3 Preparing the Installation Media

Procedure

1. Identify the required media as listed below.

NOTE

The media names listed in the following table are abbreviations.

You can find the full names of all media shipped with SAP NetWeaver 7.3 in the document

Media List – SAP NetWeaver 7.3 on SAP Service Marketplace at: http://service.sap.com/

installnw73 .

SAP Instance Required Folder of Software Packages from Media

Central services instance for ABAP (ASCS)

■ Installation master (folder <Product>_IM_<OS>_<DB>) ■ UC or NUC kernel (folder K_<N or U>_<Version>_<OS>)

where U means Unicode and N means non-Unicode.

Make sure that you have the appropriate installation kit version for your SAP kernel and that the

versions of the SAP systems and the installation media are the same on the target and source

systems. Exceptions are only allowed if they are described in an SAP Note.

NOTE

SAP NetWeaver 7.3 Business Warehouse powered by SAP HANA database only:

■ If you are planning to copy an SAP NetWeaver BW system with SAP HANA database, you

must use the installation master for SAP NetWeaver BW on HANA 1.0.

■ If you want to migrate to SAP HANA database, for the export, you must use the

installation master for SAP NetWeaver 7.3 that you used to install your source system.

3 Preparations

3.3 Preparing the Installation Media

18/140 PUBLIC 2011-12-15

Page 19: System Copy NW 7.3

For the import on the target system, you must use the installation master for SAP

NetWeaver BW on HANA 1.0.

CAUTION

The source system must be in a consistent state before you can copy it.

2. Make the required media available.

RECOMMENDATION

You can operate several SAP systems on a single host without encountering any problems.

Nevertheless, we recommend that you use a separate host for each system because an SAP

system upgrade might depend on an OS upgrade. If the SAP systems are on separate hosts,

you can upgrade them at different times.

3. If you want to perform a heterogeneous system copy you need a migration key. You can generate

it at http://service.sap.com/migrationkey.

3 Preparations

3.3 Preparing the Installation Media

2011-12-15 PUBLIC 19/140

Page 20: System Copy NW 7.3

This page is left blank for documents that are printed on both sides.

Page 21: System Copy NW 7.3

4 Database Independent System Copy

With the SAP installation tool SAPinst, you can export and import your ABAP database in a database-

independent format. SAPinst uses the R3load tool.

R3load generates a database export of all SAP objects that are defined in the ABAP Dictionary and

archives the configuration and components in the file system.

Constraints

R3load Restrictions

■ SAPinst generates a database dump of all SAP objects that are defined in the ABAP Dictionary

(R3load). Other objects are not exported by SAPinst.

■ 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.

Existing Target System

If the target system already exists and if you do not plan to perform an MCOD installation, delete

the database on the target system before the import. For more information, see Additional Information in

the installation documentation for your SAP component.

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 theSplit STR Files screen while running SAPinst to

4 Database Independent System Copy

2011-12-15 PUBLIC 21/140

Page 22: System Copy NW 7.3

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 SAPinst 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.

Procedure

Process Flow on the Source System (Export)

When performing the export you create a MIGRATION EXPORT CD image, which contains the data

of the exported system, and which you use to install the target system.

Follow the sequence of steps described in the process flows below for a:

■ Standard system

■ Distributed system or high-availability system

Standard 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 http://service.sap.com/

migrationkey. Enter 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 15].

2. Generate DDL statements [page 24].

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

4. If you want to run export processes in parallel to import processes,

run SAPinst on UNIX or Windows [page 29] or on IBM i [page 32] to prepare the source system

for the export.

In SAPinst, choose the system copy option Export Preparation.

5. Run SAPinst on UNIX or Windows [page 29] or on IBM i [page 32] to export the database instance.

In SAPinst, choose the system copy option Database Instance Export.

4 Database Independent System Copy

4.1 System Copy Procedure

22/140 PUBLIC 2011-12-15

Page 23: System Copy NW 7.3

NOTE

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

described in Restarting R3load Processes [page 39].

Only valid for: UNIX |

CAUTION

If your database instance is running on HP PA-Risc, you must proceed as described in

SAP Note 884452.

End of: UNIX |

Result

You have finished this part of the system copy. To complete the system copy, perform the steps in

Setting Up the Target System Using SAPinst [page 40].

Distributed System or High-Availability 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 http://service.sap.com/

migrationkey. Enter the installation number of your source system when prompted.

2. Perform the export on the database instance host:

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

Preparations [page 15].

2. Generate DDL statements [page 24].

3. If you want to run export processes in parallel to import processes,

run SAPinst on UNIX or Windows [page 29] or on IBM i [page 32] to prepare the source system

for the export.

In SAPinst, choose the system copy option Export Preparation.

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

5. Run SAPinst on UNIX or Windows [page 29] or on IBM i [page 32] to export the database instance.

In SAPinst, choose the system copy option Database Instance Export.

NOTE

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

described in Restarting R3load Processes [page 39].

Only valid for: UNIX |

CAUTION

If your database instance is running on HP PA-Risc, you need to proceed as described in

SAP Note 884452.

End of: UNIX |

Result

You finished this part of the system copy. To complete the system copy, perform the steps as described

in Setting Up the Target System Using SAPinst [page 40].

4 Database Independent System Copy

4.1 System Copy Procedure

2011-12-15 PUBLIC 23/140

Page 24: System Copy NW 7.3

Export Options

Figure 1: Overview on Export Options

4.2 Generating DDL Statements

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

SMIGR_CREATE_DDL.

You must perform this procedure before starting SAPinst.

CAUTION

BW only: You must ensure that no further changes (such as, activations, data loads to cubes, or

field changes) are executed in the SAP NetWeaver Business Warehouse system after you have

called the SMIGR_CREATE_DDL report and before you export the data.

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.

4 Database Independent System Copy

4.2 Generating DDL Statements

24/140 PUBLIC 2011-12-15

Page 25: System Copy NW 7.3

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.

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.

8. Before starting the export, the generated SQL files have to be copied from the specified directory

to the <instdir> directory of the export.

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

4.3 Preparation for Table Splitting

The tool R3ta processes large tables. Instead of exporting/importing one table with one R3load process,

the table is processed in, for example, 10 entities. 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.

Prerequisites

■ 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 95] or the Migration Monitor User Guide. You can find them in the

MIGMON.SAR archive contained in the folder <Product>_IM_<OS>_<DB> of the installation media.

■ For the following databases, we recommend that you create an index on the column listed in the

hints file for the table you want to split before starting R3ta:

● IBM DB2 for z/OS (Only create a temporary index if you want to perform an unsorted unload.)

● Oracle

For more information, see section Creating a Temporary Index.

Restrictions

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

■ The following tables cannot be split:

● DDNTF

● DDNTF_CONV_UC

● DDNTT

4 Database Independent System Copy

4.3 Preparation for Table Splitting

2011-12-15 PUBLIC 25/140

Page 26: System Copy NW 7.3

● DDNTT_CONV_UC

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

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 SAPinst.

3. On the Welcome screen, choose <Pour Product> System Copy Source System Based on <Technical

Stack> Table Splitting Preparation .

4. Specify SAPSID, <sapsid>adm password, the file that contains the split information, the export

directory, and the number of parallel R3ta jobs.

CAUTION

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

5. Continue with Next; 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.

6. If required, create the temporary index on the source system's tables to be split.

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.

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.

Using Hints

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 <Product>_IM_<OS>_<DB>). If you want to modify this file, copy it from the directory <IM_OS>/

4 Database Independent System Copy

4.3 Preparation for Table Splitting

26/140 PUBLIC 2011-12-15

Page 27: System Copy NW 7.3

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.

Creating a Temporary Index

Only valid for: IBM DB2 for z/OS |

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.End of: IBM DB2 for z/OS |

Only valid for: IBM DB2 for z/OS |

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.

End of: IBM DB2 for z/OS |

Only valid for: Oracle |

Oracle only: For further information and for alternatives, see SAP Note 960280.End of: Oracle |

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

index:

File Description

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

<table>_IDX.TSK Contains the task to create the temporary index.

<table>_IDX.cmd R3load command file for creating the temporary index.

DRP_<table>_IDX.TSK Contains the task to drop the temporary index.

DRP_<table>_IDX.cmd 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.

1. Only valid for: IBM DB2 for i5/OS;IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server |

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.End of: IBM DB2 for i5/OS;IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server |

2. Only valid for: Oracle |

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.

Edit the file DDLORA.TPL and add the highlighted key words to the creind statement:

creind: CREATE &unique&

4 Database Independent System Copy

4.3 Preparation for Table Splitting

2011-12-15 PUBLIC 27/140

Page 28: System Copy NW 7.3

INDEX &ind name&

ON &tab name&

( /{ &fld name& /-, /} )

TABLESPACE &tablespace&

STORAGE (INITIAL &init&

NEXT &next&

MINEXTENTS &minext&

MAXEXTENTS &maxext&

PCTINCREASE &pctinc& )

NOLOGGING

COMPUTE STATISTICS PARALLEL

ONLINE;End of: Oracle |

3. Call R3load as user <sapsid>adm with the following parameters:

R3load –dbcodepage <source system’s dbcodepage> –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.4 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. The preparation includes the following steps, that are required to set up the

target database:

■ Creating the export directory structure

■ Calculating the size of the target database

■ Creating database size file DBSIZE.XML

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 SAPinst to perform the Export Preparation.

For more information, see Exporting the Source System Using SAPinst [page 29].

2. As soon as the export preparation has finished successfully, the complete export directory with its

structure and the generated DBSIZE.XML file have to be transferred to the target host.

For more information, see Transferring the Export Files to the Target Host [page 41].

More Information

R3load Procedures Using the Migration Monitor [page 95]

4 Database Independent System Copy

4.4 Preparing Parallel Export and Import

28/140 PUBLIC 2011-12-15

Page 29: System Copy NW 7.3

4.5 Exporting the Source System Using SAPinst

Here you can find information about how to run SAPinst to perform the export on the source system:

■ Running SAPinst on UNIX or Windows to Perform the Export [page 29]

■ Running SAPinst on IBM i to Perform the Export [page 32]

4.5.1 Running SAPinst on UNIX or Windows to Perform the Export

This procedure tells you how to run SAPinst to export the database of your SAP system. SAPinst includes

SAPinst GUI and a GUI server, which both use Java.

This section describes a standard export where SAPinst, SAPinst GUI, and the GUI server are running

on the same host. If required, you can instead perform a remote system copy with SAPinst, where

SAPinst GUI is running on a separate host from SAPinst and the GUI server. For more information, see

Performing a Remote Installation with SAPinst [page 121].

For more information about SAPinst, see Useful Information About SAPinst [page 114].

Prerequisites

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.

You need at least 60 MB of free space in the installation directory for each ABAP installation option. In

addition, you need 60-200 MB free space for the SAPinst executables.

Only valid for: UNIX |

If you cannot provide 200 MB free space in the temporary directory, you can set one of the environment

variables TEMP,TMP, or TMPDIR to another directory with 200 MB free space for the SAPinst executables.End of: UNIX |

Procedure

1. Only valid for: UNIX |

Log on to your host as user root.End of: UNIX |

Only valid for: Windows |

Log on to your host as user with the required rights and privileges that authorize you to install

the SAP system with the SAPinst tool. For more information, see section Required User Authorization

for the Installation in your installation guide.End of: Windows |

4 Database Independent System Copy

4.5 Exporting the Source System Using SAPinst

2011-12-15 PUBLIC 29/140

Page 30: System Copy NW 7.3

CAUTION

■ Make sure that this user has not set any environment variables for a different SAP system

or database.

■ Do not use an existing <sapsid>adm user.

2. Make the medium for the installation master (folder <Product>_IM_<OS>_<DB>) available on your

host.

CAUTION

If you want to use a different installation directory than the default, make sure that you create

it locally. Otherwise, you might experience problems when starting the SAP Java tools.

3. Only valid for: UNIX |

Change to the directory <product>_IM_<your OS>_<your DB> and start SAPinst from the

installation media in one of the following ways:

■ Using the default installation directory (recommended)

Enter the following command:

./sapinst

SAPinst creates a directory called sapinst_instdir, which is the current working directory

for your installation, below the temporary directory of your operating system.

■ Using an alternative installation directory

If you want to use an alternative installation directory, set the environment variable TEMP,

TMP, or TMPDIR.

■ If you use virtual host names for the primary application server, or the database instance, or

both (for example, in a high availability environment), start the export with the property ./

sapinst SAPINST_USE_HOSTNAME=<virtual host>.

CAUTION

Make sure that the installation directory is not mounted with NFS, or there might be problems

when the Java Virtual Machine is started.

NOTE

Be aware of the following:

■ 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 your current working directory is not an IM_<OS> directory belonging

to another operating system.

EXAMPLE

For example, the following causes an error:

$ cd /sapcd2/IM_HPUX_IA64

$ /sapcd2/IM_HPUX_PARISC/sapinst

To correct this, enter the following:

4 Database Independent System Copy

4.5 Exporting the Source System Using SAPinst

30/140 PUBLIC 2011-12-15

Page 31: System Copy NW 7.3

$ cd /sapcd2/IM_HPUX_PARISC

$ /sapcd2/IM_HPUX_PARISC/sapinst

SAPinst GUI starts automatically by displaying the Welcome screen.End of: UNIX |

4. Only valid for: Windows |

Start SAPinst from the installation media by double-clicking sapinst.exe from the directory:

<drive>:\DATA_UNITS\<product>_IM_WINDOWS_<your platform>_<your DB>

SAPinst GUI starts automatically by displaying the Welcome screen.End of: Windows |

5. On the Welcome screen, choose System Copy Source System Based on <Technical Stack> .

6. 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 21].

CAUTION

Make sure you choose the system copy options exactly in the order they appear for each

system variant.

The following table provides an overview about the installation options available for the export:

Export Options

Export Option Remarks

Export Preparation Optional step that is required only if you want to perform export processes in parallel to import processes.SAPinst performs the following steps: ■ Creates the export directory structure ■ Calculates the size of the target database (DBSIZE.XML)

NOTE

In the case of a distributed system or a high-availability system, you need to perform this step on the database instance host.

Table Splitting Preparation Optional step.SAPinst performs the following steps: ■ Creates the export directory DATA ■ Creates database structure files (*.STR) for the tables to be split ■ Splits the generated STR files ■ Creates where-conditions for the tables to be split ■ Splits the generated WHR files ■ Copies the resulting WHR files to the export directory DATA

Database Instance Export Mandatory step.SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*.EXT, DBSIZE.XML) ■ Exports the database content

7. After you have selected the required option, choose Next.

4 Database Independent System Copy

4.5 Exporting the Source System Using SAPinst

2011-12-15 PUBLIC 31/140

Page 32: System Copy NW 7.3

8. If you generated SQL files with DDL statements (see Generating DDL Statements [page 24]) during the

database instance export, copy the generated files into the SAPinst installation directory as soon

as it has been created by SAPinst. The installation directory will have been created as soon as the

first input screen appears.

9. Follow the instructions in the SAPinst input dialogs and enter the required parameters.

CAUTION

You must choose parameter mode Typical when performing a system copy with database

tools.

NOTE

■ BW only: If you want to migrate to SAP HANA database, proceed as described in SAP

Note 1600929.

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

● You choose parameter mode Custom.

● You select the expert option Parallel Export and Import for the database instance export

on the SAP System > Database Export screen.

■ If table splitting for ABAP tables has been prepared before the data export via SAPinst,

the SAPinst 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.

NOTE

For more information about input parameters in SAPinst, position the cursor on the

parameter field and choose F1 .

After you have entered all required input parameters, SAPinst starts the export and displays the progress

during the processing phase.

Troubleshooting

See Useful Information About SAPinst [page 114].

Only valid for: IBM i5/OS |

4.5.2 Running SAPinst on IBM i to Perform the Export

4.5.2.1 Starting SAPinst on IBM i

CAUTION

Make sure that you shut down all SAP application servers before the export. Otherwise, the target

system might be inconsistent.

4 Database Independent System Copy

4.5 Exporting the Source System Using SAPinst

32/140 PUBLIC 2011-12-15

Page 33: System Copy NW 7.3

This procedure tells you how to run SAPinst to export the database of your SAP system. SAPinst includes

an SAPinst GUI and a GUI server, which both use Java.

This section describes an export where SAPinst and SAPinst GUI server runs on the host and the GUI

runs on a Windows 32-bit host.

NOTE

When you start SAPinst, the GUI server is also started. SAPinst GUI connects using a secure SSL

connection to the GUI server and the GUI server connects to SAPinst.

Procedure

1. Log on to your host as a user with similar authorization rights as QSECOFR. For more information,

see Preparing an IBM i User Profile [page 36].

CAUTION

Make sure that the installation user has not set any environment variables for a different SAP

system or database.

2. Make the medium for the installation master (folder <Product>_IM_<OS>_<DB>) available on your

host.

For more information about making the installation media available, see Copying the Installation Media

Manually Using the ROOTBIN Share [page 37].

3. Start SAPinst in one of the following ways:

■ Using the default installation directory (recommended)

Enter the following commands:

cd 'DATA_UNITS/<product>_IM_OS400_PPC64_DB4'

CALL PGM(QP2TERM) PARM('./sapinst')

NOTE

● As a default, there is no GUI on IBM i, so you cannot see an SAPinst Welcome screen.

You must start the SAPinst GUI separately on a Windows 32-bit platform. For more

information, see Starting SAPinst GUI Separately (Optional) [page 124].

● For advanced users only: PASE, which is similar to AIX allows you to set the

DISPLAY variable. If you already have a running and configured XWindows server

on Linux or Windows (for example, Humming Bird), you can try to direct the

graphical output of SAPinst to a XWindow by setting the DISPLAY variable. If this

works, you do not have to use the remote SAPinst GUI separately. We do not

recommend that you start the SAPinst using the DISPLAY variable as there is no

support available.

● Only valid for: HA (UNIX) |

If you are installing a high-availability system and you have not already set the

environment parameter SAPINST_USE_HOSTNAME to specify the virtual host name,

you can start SAPinst as follows:

4 Database Independent System Copy

4.5 Exporting the Source System Using SAPinst

2011-12-15 PUBLIC 33/140

Page 34: System Copy NW 7.3

CALL PGM(QP2TERM) PARM('./sapinst' 'SAPINST_USE_HOSTNAME=<virtual host

name>')

End of: HA (UNIX) |

CAUTION

● 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.

● Make sure that your current working directory is not an IM_<OS> directory belonging

to another operating system.

For example, the following commands are incorrect and cause an error:

$ CD DIR ('DATA_UNITS/<product>_IM_HPUX_IA64')

$ CALL PGM(QP2TERM) PARM('DATA_UNITS/<product>_IM_HPUX_PARISC/

sapinst')

The following commands are correct:

$ CD DIR('DATA_UNITS/<product>_IM_OS400_PPC64_DB4')

$ CALL PGM(QP2TERM) PARM('./sapinst')

■ Using an alternative installation directory

If you want to use an alternative installation directory, set the environment variable TEMP,

TMP, or TMPDIR.

NOTE

To receive a list of all available SAPinst properties, enter the following command:

CALL PGM(QP2TERM) PARM('./sapinst -p')

■ If you use virtual host names for the primary application server or the database instance or

both (for example, in a high availability environment), start the export with the property

SAPINST_USE_HOSTNAME=<virtual host>.

4. On the Welcome screen, choose System Copy Source System Based on <Technical Stack> .

5. 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 21].

CAUTION

Make sure that you choose the system copy options exactly in the order they appear for each

system variant.

6. The following table provides an overview about the system copy options available for the export

of a:

■ Standard system

■ Distributed system or high-availability system

4 Database Independent System Copy

4.5 Exporting the Source System Using SAPinst

34/140 PUBLIC 2011-12-15

Page 35: System Copy NW 7.3

Export Options

Export Option Remarks

Export Preparation Optional step that is required only if you want to perform export processes in parallel to import processes.SAPinst performs the following steps: ■ Creates the export directory structure ■ Calculates the size of the target database (DBSIZE.XML)

NOTE

In the case of a distributed system or a high-availability system, you need to perform this step on the database instance host.

Table Splitting Preparation Optional step.SAPinst performs the following steps: ■ Creates the export directory DATA ■ Creates database structure files (*.STR) for the tables to be split ■ Splits the generated STR files ■ Creates where-conditions for the tables to be split ■ Splits the generated WHR files ■ Copies the resulting WHR files to the export directory DATA

Database Instance Export Mandatory step.SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*.EXT, DBSIZE.XML) ■ Exports the database content

7. After you have selected the required installation option, choose Next.

8. If you generated SQL files with DDL statements (see Generating DLL Statements [page 24]) during the

database instance export, copy the generated files into the SAPinst installation directory as soon

as it has been created by SAPinst. The installation directory will have been created as soon as the

first input screen appears.

9. Follow the instructions in the SAPinst input dialogs and enter the required parameters.

CAUTION

You must choose parameter mode Typical when performing a system copy with database

tools.

NOTE

■ BW only: If you want to migrate to SAP HANA database, in the SAP System > Export for

Target System screen, select the same database platform as target database that you use in

the source system.

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

● You choose parameter mode Custom.

● You select the expert option Parallel Export and Import for the database instance export

on the SAP System > Database Export screen.

4 Database Independent System Copy

4.5 Exporting the Source System Using SAPinst

2011-12-15 PUBLIC 35/140

Page 36: System Copy NW 7.3

■ If table splitting for ABAP tables has been prepared before the data export via SAPinst,

the SAPinst 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.

NOTE

For more information about input parameters in SAPinst, position the cursor on the

parameter field and choose F1 .

After you have entered all required input parameters, SAPinst starts the installation and displays the

progress of the installation.

Troubleshooting

See Useful Information About SAPinst [page 114].

Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS;No Database |

4.5.2.2 Preparing an IBM i User Profile

For the installation you need to create a user account on the IBM i you want to install.

The following requirement applies:

■ The IBM i user profile must have user class *SECOFR and all special authorities that belong to user

QSECOFR.

Procedure

NOTE

The user name SAPIUSR and the password SAP are used in the procedures as examples.

IBM i:

Execute the following command:

CRTUSRPRF USRPRF(SAPIUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('Test User for SAP

Installation') SPCAUT(*USRCLS) LANGID(ENU) CNTRYID(US) CCSID(500) LOCALE(*NONE)

NOTE

In previous releases, we recommended that you create the user SAPINST to install the SAP system.

In the current release, a group SAPINST is created and used for the installation and SAP system. If

a user SAPINST already exists on your system, you must delete this user.

End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS;No Database |

4 Database Independent System Copy

4.5 Exporting the Source System Using SAPinst

36/140 PUBLIC 2011-12-15

Page 37: System Copy NW 7.3

Only valid for: IBM i5/OS | IBM DB2 for i5/OS |

4.5.2.3 Copying the Installation Media Manually to Your IBM i

This section describes a secure way to copy the required installation media from your Windows PC to

your IBM i. To copy the media, you have to use a binary share ROOTBIN. This guarantees that the content

of the media is copied correctly from the Windows PC to your IBM i. No copied content is corrupted,

and no copied files with longer file names are shortened by a converting share.

Procedure

Creating a Binary Share ROOTBIN on IBM i

If you do not already have a binary share ROOTBIN on your IBM i, and you want to copy manually media

from your Windows PC into the IFS of your IBM i, you have to create this share manually using the

IBM i System Director Navigator. To do so, proceed as follows:

1. Start the IBM i System Director Navigator on your Windows PC.

2. Connect to your IBM i using My Connections.

3. To create or change the share ROOTBIN, choose File Systems File Shares .

4. Right-click File Shares Open i5/OS Netserver .

A new screen i5/OS Netserver appears.

5. Click the folder Shared Objects to see the shares.

6. To check the already existing share ROOTBIN or create a new share ROOTBIN, right-click New

File .

NOTE

The share ROOTBIN must have the access permission Read/Write and the path name should

be /.

7. On the Text Conversion tab, do not select Allow file text conversion.

8. To save the share ROOTBIN, press OK.

Now you have created the share ROOTBIN on your IBM i.

Copying the Installation Media Manually Using the Binary Share ROOTBIN

1. To open the MS DOS screen on Windows, choose Start Run .

2. Enter cmd.exe.

3. Press OK.

The MS DOS screen appears.

4. In the command line of the MS DOS screen, enter net use.

All network connections to shared resources are displayed.

5. Check if you have a connection to your IBM i.

4 Database Independent System Copy

4.5 Exporting the Source System Using SAPinst

2011-12-15 PUBLIC 37/140

Page 38: System Copy NW 7.3

If you find \\<IBM_i_Hostname>\ROOTBIN in the Remote column and a drive directory letter in the

Local column, you have already established the required connection to your IBM i.

Otherwise, you have to establish this connection. To do this, enter:

net use X: \\<IBM_i_Hostname>\ROOTBIN SAP /USER:SAPIUSR

X: is now your new network drive to share \\<IBM_i_Hostname>\ROOTBIN to your IFS on the

IBM i. If X: is already in use, choose another drive letter that is free.

NOTE

We use the user name SAPIUSR and the password SAP as examples. For more information

about how to create the installation user SAPIUSER, see Preparing an IBM i User Profile [page 36].

6. To change to the new network drive, enter X: in the command line of your MS DOS screen.

7. Create the subdirectories in your IFS where you want to copy the required media.

For each media, enter:

mkdir \tmp\<sid>\<media_name>

NOTE

You must avoid blanks or commas in the media path name.

8. Copy the installation media from your Windows drive (for example D:\) to the IFS of your IBM i

host by inserting the required installation media and entering the following command:

xcopy D:\<media> X:\tmp\<sid>\<media_name> /E or

xcopy C:\tmp\download\<media_name> X:\tmp\<sid>\<media_name> /E

NOTE

You must copy the root directory of the media and all required media subdirectories to the

IFS of your IBM i.

9. For each required media, create a subdirectory and copy the required media.

NOTE

For advanced users only: Instead of copying the complete media you also can copy only dedicated

subdirectories. For IBM i the following directories have to be copied:

■ <product>_IM_OS400_PPC64

■ K_<version>_<U or N>_OS400_PPC64

■ EXP*

■ JAVA*

■ SL_CONTROLLER*

■ <product>_IM_SAPINSTGUI_WINDOWS_I386

■ <product>_IM_SAPINSTGUI_LINUX_I386

End of: IBM i5/OS | IBM DB2 for i5/OS |

End of: IBM i5/OS |

4 Database Independent System Copy

4.5 Exporting the Source System Using SAPinst

38/140 PUBLIC 2011-12-15

Page 39: System Copy NW 7.3

4.5.3 Restarting R3load Processes

You can restart failed or canceled R3load processes while the Migration Monitor is still running. The

state files export_state.properties and import_state.properties (see Output Files [page 111]) allow

package states to be manually updated to restart failed R3load processes.

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

■ To restart package processing, set the package state from “–” to “0”.

■ 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.)

■ 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

1. 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.

2. 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 in

the import_state.properties files to “–”.

4 Database Independent System Copy

4.5 Exporting the Source System Using SAPinst

2011-12-15 PUBLIC 39/140

Page 40: System Copy NW 7.3

EXAMPLE

Export TSK file Import TSK file

Table name Status Table name Status

TAB_1 ok TAB_1 ok

TAB_2 err TAB_2 ok

TAB_3 xeq TAB_3 err

TAB_4 xeq TAB_4 xeq

The first object with errors here is TAB_2 in the export TSK file. That 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”.

■ When the import was completed successfully, but the export was canceled with errors,

you can set the status in the export_state.properties from “–” to “+”.

3. Restart SAPinst or the Migration Monitor to proceed with the system copy.

More Information

R3load Processes Using the Migration Monitor [page 95].

4.6 Setting Up the Target System

Purpose

You use SAPinst to install the target system and import the database files that you have exported from

the source system.

Process Flow

Standard System

You perform the following steps on the standard system host:

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

installation guide for your SAP application.

2. If you have already prepared the export [page 28] 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 28] on the source system.

2. You install the target system [page 42].

If you did not prepare the export on the source system, you install the target system [page 42].

4 Database Independent System Copy

4.6 Setting Up the Target System

40/140 PUBLIC 2011-12-15

Page 41: System Copy NW 7.3

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 for your SAP

application.

Distributed System or High-Availability System

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

1. You prepare the host of the primary application server instance and the database instance

host for the installation of the corresponding instances of your target system as described in the

installation guide for your SAP application.

2. You perform the following steps on the database instance host:

■ If you have already prepared the export [page 28] 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 28] on

the source system.

2. You install the database instance of the target system [page 42].

■ If you did not prepare the export [page 28] on the source system, you install the database instance of the

target system [page 42]

3. On the host of the primary application server instance, you install the primary application

server instance of the target system.

4. 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 for your SAP

application.

4.6.1 Transferring the Export Files to the Target Host

This section describes how to transfer the complete export directory with its structure and the generated

DBSIZE.XML file to the target host.

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 master or export files).

4 Database Independent System Copy

4.6 Setting Up the Target System

2011-12-15 PUBLIC 41/140

Page 42: System Copy NW 7.3

Otherwise, SAPinst does not ask you to specify the export directory and automatically chooses

one that you may not want to use. In this case, SAPinst 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.

4.6.2 Installing the Target System

PrerequisitesThere is enough free space on the target system for the database load. To find out the size of the export

and the sizes of the tablespaces or dbspaces that will be created, look at the file DBSIZE.XML, which is

located in the following directory:

Windows: <DRIVE>:\<EXPDIR>\DB\<DATABASE>

UNIX: <EXPDIR>/DB/<DATABASE>

Only valid for: MaxDB |

If the database platform of your target system is MaxDB, you must reserve at least twice as much space

as specified in the DBSIZE.XML file. During the import, monitor the remaining free space in the database

using the MaxDB administration tools Database Manager or Database Studio, and increase it if required.End of: MaxDB |

NOTE

SAPinst automatically performs a reload. If the database software has already been unpacked or

installed, or if the database already exists, SAPinst recognizes this automatically and skips the

related steps.

Procedure1. Prepare the target system host as described in the installation guide for your SAP system.

2. Start SAPinst as described in the installation guide for your SAP 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 SAPinst to avoid performance

4 Database Independent System Copy

4.6 Setting Up the Target System

42/140 PUBLIC 2011-12-15

Page 43: System Copy NW 7.3

problems during the dialog phase. You can find the latest version of SAPinst at http://

service.sap.com.

3. On the Welcome screen, navigate to the following folder according to the requirements of your

target system: <Your Product> System Copy Target System <System Variant> Based on <Technical

Stack> .

4. Run the options required for your system copy in the sequence they are listed in the specific folder

and according to the process flow in Setting Up the Target System Using SAPinst [page 40].

5. To install the target system, follow the instructions in the SAPinst input dialogs and enter the

required parameters.

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:

● UNIX: /usr/sap/<SAPSID>

● UNIX: /sapmnt/<SAPSID>

● Windows: \usr\sap\<SAPSID>

● Windows: \sapmnt\<SAPSID>

■ If you want to perform export processes in parallel to import processes and you have prepared

the export, you must choose Custom on the Parameter Mode screen.

■ On the SAP System > Database screen, choose Standard System Copy/Migration (Load-Based).

The SAP data dump from the MIGRATION EXPORT CD image that you created during the export

is loaded in the newly installed SAP system database.

■ When SAPinst displays the Media Browser window and asks for the Export Migration CD, 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 want to perform export processes in parallel to import processes and you have prepared

the export, you must select Parallel Export and Import on the SAP System Database Import screen.

6. Complete the installation as described in the installation documentation for your SAP component.

NOTE

If you have to restart the import after an error, just restart SAPinst. 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 39].

4 Database Independent System Copy

4.6 Setting Up the Target System

2011-12-15 PUBLIC 43/140

Page 44: System Copy NW 7.3

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

in the medium for the installation master (folder <Product>_IM_<OS>_<DB>).

4 Database Independent System Copy

4.6 Setting Up the Target System

44/140 PUBLIC 2011-12-15

Page 45: System Copy NW 7.3

5 Database-Specific System Copy

The following sections describe the database-specific methods for the system copy. For more

information about SAP Notes describing the homogeneous system copy for your database system, see

http://service.sap.com/notes.

NOTE

A database-specific method for SAP HANA database is not available.

Process

Follow the sequence of steps described in the process flows below for a:

■ Standard system

■ Distributed system

■ High-availability system

Standard System

For performing the export for a standard system, you need to proceed as follows on the central system

host:

Process Flow on the Source System (Export)

1. You generate the control file structure for the target database [page 48].

2. If required, you create an offline backup of the source database [page 52].

Process Flow on the Target System

1. Only valid for: Windows |

You install the database software as described in the installation guide of your SAP solution.End of: Windows |

2. Only valid for: UNIX |

You prepare the target system [page 53]:

1. Follow the instructions on the SAPinst screens until SAPinst requests you to install the database

software and to perform the database backup/restore.

CAUTION

Make sure that you create the secure store of the target system using the same key phrase

as for the source system. Otherwise, the UME service cannot be started.

2. You create the database file system (if not yet existing).

3. You install the database software.End of: UNIX |

5 Database-Specific System Copy

2011-12-15 PUBLIC 45/140

Page 46: System Copy NW 7.3

3. Only valid for: Windows |

Follow the instructions on the SAPinst screens until you are requested to perform the database

backup/restore.

NOTE

If required, you have to restart SAPinst as described in the installation guide of your SAP

solution.

End of: Windows |

4. To complete the system copy, you have to perform the follow-up activities [page 87].

Distributed System or High Availability System

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

Process Flow on the Source System (Export)

1. On the database instance host of the source system, you generate the control file structure for the target

database [page 48].

2. If required, on the database instance host, you create an offline backup of the source database [page 52].

Process Flow on the Target System

1. Only valid for: Windows |

On the database instance host, you install the database software as described in the installation

guide of your SAP solution.

CAUTION

Make sure that you create the secure store of the target system using the same key phrase as

for the source system. Otherwise, the UME service cannot be started.

End of: Windows |

2. Only valid for: UNIX |

You prepare the target system [page 53]:

1. On the database instance host, follow the instructions on the SAPinst screens until SAPinst

requests you to install the database software and to perform the database backup/restore.

2. On the database instance host, you create the database file system (if not yet existing).

3. On the database instance host, you install the database software.End of: UNIX |

3. Only valid for: Windows |

On the database instance host, follow the instructions on the SAPinst screens until you are

requested to perform the database backup/restore.

NOTE

If required, you have to restart SAPinst as described in the installation guide of your SAP

solution.

End of: Windows |

4. To complete the system copy, you have to perform the follow-up activities [page 87].

5 Database-Specific System Copy

46/140 PUBLIC 2011-12-15

Page 47: System Copy NW 7.3

Only valid for: Oracle |

5.1 Oracle-Specific Procedure

Purpose

In an SAP system environment, you can create a homogeneous copy of an Oracle database by copying

database files. This method is suitable for creating an exact copy of an existing database. The source of

the copy can be an offline backup or the file system of your source host.

You use SAPinst for the installation on the target system host as described in the installation

documentation for your SAP component. Only the SAPinst steps for setting up and loading the database

steps are different.

Advantages

■ You can use existing offline backups (provided that redo logs were cleaned up with forced log

switches).

■ This method is faster than the R3load method.

Disadvantages

■ Offline backup/copy of database files in a heterogeneous environment is not possible because the

hardware of the source and target systems must be binary-compatible.

■ Source system host and target system host must be different.

■ You must shut down the SAP system and the database during offline backup/copy of database files.

■ You cannot change the database schema and the tablespace names.

Prerequisites

■ You must use the same Oracle release and patch level for your database in the source and target

system.

■ The classes12.jar must exist in the <ORACLE_HOME>/jdbc/lib directory (installed using a

standard Oracle installation).

■ If your source system is an ABAP only system, make sure that a JRE version 1.5 or higher is installed

on the database instance.

■ The JAVA_HOME environment variable must point the JRE directory.

■ The backup must be done offline.

■ The source and target systems must run on different hosts for security reasons.

■ The source and target systems must be binary compatible.

NOTE

You can also perform a system copy from 32-bit systems to 64-bit systems and the other way

around (same operating system assumed) even if source and target system are not binary

compatible.

5 Database-Specific System Copy

5.1 Oracle-Specific Procedure

2011-12-15 PUBLIC 47/140

Page 48: System Copy NW 7.3

If your source system uses the US7ASCII character set, you must choose this character set when

installing the target system. SAPinst prompts for the character set during the installation (key: Database

Character Set). The installation default is WE8DEC or UTF8 for Unicode systems. To find out the

character set used by the source system, connect to the source database as user sap<schemaid> or

sapr3 with sqlplus and enter: SELECT * FROM V$NLS_PARAMETERS;

5.1.1 Generating the Control File Structure

The OraBRCopy Java tool writes a file CONTROL.SQL to the current working directory, which can be used

without further adaptations on the target system.

For more information about the OraBRCopy tool, see the documentation ORABRCopy.pdf, which is part

of the OraBRCOPY.SAR archive.

Prerequisites

RECOMMENDATION

We recommend that you shut down the SAP system before you perform the following steps. The

database must still be running.

Procedure

1. Create an installation directory <INSTDIR> (UNIX: with permissions 777) on the source system.

2. Copy the ORABRCOPY.SAR archive from the medium for the installation master to the installation

directory and extract it using SAPCAR.

You can find the archive in the following directory:

UNIX: /DATA_UNITS/<Product>_IM_<your OS>_ORA/COMMON/INSTALL/ORA/ORABRCOPY.SAR

Windows: \DATA_UNITS\<Product>_IM_WINDOWS_ORA\COMMON\INSTALL\ORA\ORABRCOPY.SAR

3. Make sure that all redo log groups are archived.

4. Start the OraBRCopy tool as an OS user with Oracle DBA privileges:

Only valid for: UNIX |

■ Log on as one of the following users:

● ora<dbsid>

● <sapsid>adm

■ Enter the following commands:

./ora_br_copy.sh -generateFiles -forceLogSwitches -targetSid <TARGET_DBSID> -

password <system's password> -listenerPort <listener port>

End of: UNIX |

Only valid for: Windows |

■ Log on as <sapsid>adm

■ Enter the following commands:

5 Database-Specific System Copy

5.1 Oracle-Specific Procedure

48/140 PUBLIC 2011-12-15

Page 49: System Copy NW 7.3

ora_br_copy.bat -generateFiles -forceLogSwitches -targetSid <TARGET_DBSID> -

password <system's password> -listenerPort <listener port>

End of: Windows |

5. The tool creates the files CONTROL.SQL, CONTROL.TRC, and init<targetSID>.ora in your

installation directory, shuts down and restarts the database and performs the required log switches.

NOTE

If an error occurs, check the log file:

<INSTDIR>/ora.brcopy.log

6. Verify and, if necessary, update the CONTROL.SQL control file using the CONTROL.TRC trace file as

follows.

Example

In the following example, entries of CONTROL.SQL written in bold should be compared and changed

according to the trace file. This is a Windows example, however, the changes to be made are valid for

UNIX, too.

REM

====================================================================

REM CONTROL.SQL

REM

REM SAP AG Walldorf

REM Systeme, Anwendungen und Produkte in der Datenverarbeitung

REM

REM (C) Copyright SAP AG 2006

REM

====================================================================

REM Generated at:

REM Fri Sep 17 08:33:25 CEST 2006

REM for target system NEW

REM on

REM Windows 2000 5.0 x86

CONNECT / AS SYSDBA

STARTUP NOMOUNT

CREATE CONTROLFILE REUSE

SET DATABASE "NEW"

RESETLOGS

ARCHIVELOG

MAXLOGFILES 255

MAXLOGMEMBERS 3

MAXDATAFILES 1022

5 Database-Specific System Copy

5.1 Oracle-Specific Procedure

2011-12-15 PUBLIC 49/140

Page 50: System Copy NW 7.3

MAXINSTANCES 50

MAXLOGHISTORY 1134

LOGFILE

GROUP 1 (

'D:\ORACLE\NEW\ORIGLOGA\LOG_G11M1.DBF',

'D:\ORACLE\NEW\MIRRLOGA\LOG_G11M2.DBF'

) SIZE 50M,

GROUP 2 (

'D:\ORACLE\NEW\ORIGLOGB\LOG_G12M1.DBF',

'D:\ORACLE\NEW\MIRRLOGB\LOG_G12M2.DBF'

) SIZE 50M,

GROUP 3 (

'D:\ORACLE\NEW\ORIGLOGA\LOG_G13M1.DBF',

'D:\ORACLE\NEW\MIRRLOGA\LOG_G13M2.DBF'

) SIZE 50M,

GROUP 4 (

'D:\ORACLE\NEW\ORIGLOGB\LOG_G14M1.DBF',

'D:\ORACLE\NEW\MIRRLOGB\LOG_G14M2.DBF'

) SIZE 50M

DATAFILE

'D:\ORACLE\NEW\SAPDATA1\SYSTEM_1\SYSTEM.DATA1',

'D:\ORACLE\NEW\SAPDATA3\IMS_1\IMS.DATA1',

'D:\ORACLE\NEW\SAPDATA3\IMS_2\IMS.DATA2',

'D:\ORACLE\NEW\SAPDATA3\IMS_3\IMS.DATA3',

'D:\ORACLE\NEW\SAPDATA3\IMS_4\IMS.DATA4',

'D:\ORACLE\NEW\SAPDATA4\IMS_5\IMS.DATA5',

'D:\ORACLE\NEW\SAPDATA4\IMS_6\IMS.DATA6',

'D:\ORACLE\NEW\SAPDATA4\IMS_7\IMS.DATA7',

'D:\ORACLE\NEW\SAPDATA4\IMS_8\IMS.DATA8',

'D:\ORACLE\NEW\SAPDATA4\IMS_9\IMS.DATA9',

'D:\ORACLE\NEW\SAPDATA1\IMS700_1\IMS700.DATA1',

'D:\ORACLE\NEW\SAPDATA1\IMS700_2\IMS700.DATA2',

'D:\ORACLE\NEW\SAPDATA1\IMS700_3\IMS700.DATA3',

'D:\ORACLE\NEW\SAPDATA1\IMS700_4\IMS700.DATA4',

'D:\ORACLE\NEW\SAPDATA2\IMS700_5\IMS700.DATA5',

'D:\ORACLE\NEW\SAPDATA2\IMS700_6\IMS700.DATA6',

'D:\ORACLE\NEW\SAPDATA2\IMS700_7\IMS700.DATA7',

'D:\ORACLE\NEW\SAPDATA2\IMS700_8\IMS700.DATA8',

5 Database-Specific System Copy

5.1 Oracle-Specific Procedure

50/140 PUBLIC 2011-12-15

Page 51: System Copy NW 7.3

'D:\ORACLE\NEW\SAPDATA2\IMS700_9\IMS700.DATA9',

'D:\ORACLE\NEW\SAPDATA3\IMS700_10\IMS700.DATA10',

'D:\ORACLE\NEW\SAPDATA4\IMS700_11\IMS700.DATA11',

'D:\ORACLE\NEW\SAPDATA1\IMSUSR_1\IMSUSR.DATA1',

'D:\ORACLE\NEW\SAPDATA2\ROLL_1\ROLL.DATA1'

;

ALTER DATABASE OPEN RESETLOGS;

ALTER TABLESPACE PSAPTEMP ADD TEMPFILE

'D:\ORACLE\NEW\SAPDATA3\TEMP_1\TEMP.DATA1'

SIZE 350M REUSE AUTOEXTEND OFF;

Changes to Be Made

1. If you want to migrate your database from 32-bit to 64-bit or vice versa, add the following lines at

the bottom of the control.sql file:

shutdown immediate;

startup upgrade

spool utlirp.log

@?/rdbms/admin/utlirp.sql

spool off

shutdown immediate;

startup

exit

2. MAXLOGFILES 255

...

The numbers must be greater than or equal to the corresponding numbers in the trace file.

3. GROUP 1 (

'D:\ORACLE\NEW\ORIGLOGA\LOG_G11M1.DBF',

'D:\ORACLE\NEW\MIRRLOGA\LOG_G11M2.DBF'

) SIZE 50M,

Group 2 (

The sizes of the respective groups must be equal to the sizes of the corresponding groups in the

trace file.

4. 'D:\ORACLE\NEW\SAPDATA1\SYSTEM_1\SYSTEM.DATA1',

'D:\ORACLE\NEW\SAPDATA3\IMS_1\IMS.DATA1',

'D:\ORACLE\NEW\SAPDATA1\IMS700_1\IMS700.DATA1'

5 Database-Specific System Copy

5.1 Oracle-Specific Procedure

2011-12-15 PUBLIC 51/140

Page 52: System Copy NW 7.3

The count of the data files must be equal to the count of the corresponding data files in the trace

file.

5. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE

'D:\ORACLE\NEW\SAPDATA3\TEMP_1\TEMP.DATA1'

SIZE 350M REUSE AUTOEXTEND OFF;

The size must be equal to the corresponding size in the trace file.

6. The number of the rows with ALTER TABLESPACE must be equal to the number of the corresponding

rows in the trace file.

5.1.2 Creating a Backup

If required, create a backup. Choose between performing an offline backup manually or an online

backup with BR*Tools.

5.1.2.1 Creating an Offline Backup

Procedure

Create an offline backup, if required. There are different possibilities for preparing the actual transfer

of the database files:

■ If you have an up-to-date offline backup, you can use it (provided that redo logs were cleaned

up with forced log switches).

■ If you want to transport the database file (for example, on tape) or if you have to perform the

database shutdown at a certain time, stop the database (normal shutdown) and perform a complete

offline backup. You can use the trace file CONTROL.TRC created by OraBrCOPY to determine the file

system trees that have to be saved.

■ Stop the database (normal shutdown) and copy the database files when the actual transfer to the

target system takes place. You do not have to perform any preparations for the actual transfer

now. Proceed with the next steps.

5.1.2.2 Creating an Offline or Online Backup with BR*Tools

You can use any backup strategy supported by BR*Tools as the basis for a system copy: offline or online,

with or without BACKINT, with or without RMAN, complete or incremental, and so on. The backup

strategy must simply be valid for restore and recovery. This means that a complete restore and recovery

of the source database must be possible. In addition for BACKINT and RMAN, the external backup

tools must be configured so that a restore is possible on the target host.

5 Database-Specific System Copy

5.1 Oracle-Specific Procedure

52/140 PUBLIC 2011-12-15

Page 53: System Copy NW 7.3

Procedure

Proceed as described in the SAP Library [page 9] at:

SAP NetWeaver Library: Function-Oriented View Administration of Databases Database Administration for Oracle

SAP Database Guide: Oracle BR*Tools for Oracle DBA BR*Tools in Action Backup and Database Copy with

BR*Tools .

5.1.3 Preparing the Target System (Oracle)

Prerequisites

Make sure that sapdata<n> file systems on the target system host are large enough.

Procedure

1. Install the target SAP system with SAPinst as described in the installation documentation for your

SAP solution.

CAUTION

When you perform a system copy with the Oracle backup/restore method, you cannot

change the database schema and the tablespace names of the new target system. When

installing the target primary application server instance, the target database instance, or the

target additional application server instance make sure that you enter the correct database

schema names (which are the database schema names of the source system). The schema

names of the source and target system must be identical.

1. On the Welcome screen, choose <Your Product> System Copy Target System <System Variant>

<Technical Stack> .

2. When SAPinst prompts for the database copy method, choose Homogeneous System Copy (Backup/

Restore).

3. Proceed until SAPinst stops to restore the database files on the target system.

The following message is displayed:

SAPinst now stops the installation. Proceed as follows:...

2. Only valid for: UNIX |

If necessary, extract the Oracle stage archives manually and install the Oracle software as described

in the installation documentation for your SAP solution.End of: UNIX |

3. Restore the database files on the target system.

4. If they do not exist, create the following directories on the target system:

■ UNIX:

● /oracle/<TARGET_DBSID>/mirrlog<x>

● /oracle/<TARGET_DBSID>/origlog<x>

● /oracle/<TARGET_DBSID>/sapdata<x>

● /oracle/<TARGET_DBSID>/sapreorg

5 Database-Specific System Copy

5.1 Oracle-Specific Procedure

2011-12-15 PUBLIC 53/140

Page 54: System Copy NW 7.3

● /oracle/<TARGET_DBSID>/saparch

● /oracle/<TARGET_DBSID>/oraarch

● /oracle/<TARGET_DBSID>/saptrace

● /oracle/<TARGET_DBSID>/saptrace/background

● /oracle/<TARGET_DBSID>/saptrace/usertrace

● /oracle/<TARGET_DBSID>/origlogA/cntrl

● /oracle/<TARGET_DBSID>/sapdata1/cntrl

● /oracle/<TARGET_DBSID>/saparch/cntrl

● /oracle/<TARGET_DBSID>/sapcheck

■ Windows:

● <drive>:\oracle\<TARGET_DBSID>\mirrlog<x>

● <drive>:\oracle\<TARGET_DBSID>\origlog<x>

● <drive>:\oracle\<TARGET_DBSID>\sapdata<x>

● <drive>:\oracle\<TARGET_DBSID>\sapreorg

● <drive>:\oracle\<TARGET_DBSID>\saparch

● <drive>:\oracle\<TARGET_DBSID>\oraarch

● <drive>:\oracle\<TARGET_DBSID>\saptrace

● <drive>:\oracle\<TARGET_DBSID>\saptrace\background

● <drive>:\oracle\<TARGET_DBSID>\saptrace\usertrace

● <drive>:\oracle\<TARGET_DBSID>\origlogA\cntrl

● <drive>:\oracle\<TARGET_DBSID>\sapdata1\cntrl

● <drive>:\oracle\<TARGET_DBSID>\saparch\cntrl

● <drive>:\oracle\<TARGET_DBSID>\sapcheck

5. Make sure that the following directories are empty (except the subdirectory saparch/cntrl):

UNIX

■ /oracle/<TARGET_DBSID>/saparch

■ /oracle/<TARGET_DBSID>/oraarch

Windows

■ <drive>:\oracle\<TARGET_DBSID>\saparch

■ <drive>:\oracle\<TARGET_DBSID>\oraarch

6. UNIX only: All directories must be owned by the user ora<target_dbsid>.

To do this, enter the following command:

chown ora<target_dbsid>:dba<directory>

7. Windows only: Set the security settings for the built-in accounts and groups SYSTEM,

Administrators, SAP_<SAPSID>_GlobalAdmin (domain installation), and

SAP_<SAPSID>_LocalAdmin (local installation) for all directories as follows:

1. In the Windows Explorer, right-click the Oracle root directory and choose Properties.

5 Database-Specific System Copy

5.1 Oracle-Specific Procedure

54/140 PUBLIC 2011-12-15

Page 55: System Copy NW 7.3

2. Under Security, choose Advanced.

3. Deselect Inherit from parent the permission entries….

4. In the next dialog, choose Copy to copy the permission entries that were previously applied

from the parent to this object.

5. Choose OK.

6. Set the permissions for the above-mentioned accounts SYSTEM, Administrators,

SAP_<DBSID>_GlobalAdmin, or SAP_<DBSID>_LocalAdmin to Full Control.

7. Delete all other accounts.

5.1.4 Restoring the Database Files on the Target System

CAUTION

If you do not use an offline backup but copy the database files directly from the source to the

target system host, make sure that you shut down the database on the source system before you

copy the listed files from the source to the target directories.

Procedure

1. Copy the following files from the source to the target system host either by using an offline backup

or by copying the listed files from the source directories to the target directories.

Directories on UNIX

Source and Target Directory Files

/oracle/<DBSID>/sapdata<x> All files

/oracle/<DBSID>/origlog<x> All files

/oracle/<DBSID>/mirrlog<x> All files

Source: <INSTDIR> Target: <SAPINST_INSTDIR>

CONTROL.SQL

Source: <INSTDIR> Target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/dbs

init<TARGET_DBSID>.ora

Directories on Windows

Source and Target Directory Files

<drive>:\oracle\<DBSID>\sapdata<x> All files

<drive>:\oracle\<DBSID>\origlog<x> All files

<drive>:\oracle\<DBSID>\mirrlog<x> All files

Source: <INSTDIR>Target: <SAPINST_INSTDIR>

CONTROL.SQL

Source: <INSTDIR>Target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database

init<TARGET_DBSID>.ora

5 Database-Specific System Copy

5.1 Oracle-Specific Procedure

2011-12-15 PUBLIC 55/140

Page 56: System Copy NW 7.3

Only valid for: Windows |

NOTE

If you use an existing offline backup, the source data files and log files are not located in the

directories shown in the table.

By default, the installation directory of the target system is located in the following directory:

%programfiles%\sapinst_instdir\<SAP_System_Name>\LM\ORA\COPY\ORA\SYSTEM\

<system_variant>\<technical stack>

End of: Windows |

2. After you have copied the database files, make sure that the files on the source and target system

are not located in different directories or drives. If required, make the corresponding changes in

the files control.sql and the init<DBSID>.ora.

3. Verify that the created directories and copied files have the owner ora<target_dbsid>, belong to

the group dba, and have the permissions 740.

4. Make sure that the control files are not restored. If necessary, remove them.

The file names are specified by the parameter control_files of the init<TARGET_DBSID>.ora file.

5.1.5 Restoring the Database Files on the Target System with BR*Tools

Procedure

1. Copy the following files from the source system host to the target system host by copying manually

the listed files from the source directories to the target directories.

■ On UNIX:

Source and Target Directory Files

Source: <INSTDIR> Target: <SAPINST_INSTDIR>

CONTROL.SQL

Source: <INSTDIR> Target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/dbs

init<TARGET_DBSID>.ora

■ On Windows:

Source and Target Directory Files

Source: <INSTDIR>Target: <SAPINST_INSTDIR>

CONTROL.SQL

Source: <INSTDIR>Target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database

init<TARGET_DBSID>.ora

2. Call the restore and recovery function of BR*Tools.

If you follow these instructions, the prerequisites are fulfilled. The main prerequisite is that the

corresponding BR*Tools logs (BRBACKUP detailed and summary log, BRARCHIVE summary log) are

copied from the source to the target system. In addition, the postprocessing steps mentioned in

the SAP Note 1003028 are covered during the standard system copy procedure.

5 Database-Specific System Copy

5.1 Oracle-Specific Procedure

56/140 PUBLIC 2011-12-15

Page 57: System Copy NW 7.3

For more information about the execution of restore and recovery under the control of

BRRECOVER and the exact syntax of BRRECOVER, see the section Homogeneous Database Copy in SAP

Note 1003028.

For more information about BR*Tools, see the SAP Library [page 9] at:

SAP NetWeaver Library: Function-Oriented View Administration of Databases Database Administration for

Oracle SAP Database Guide: Oracle BR*Tools for Oracle DBA .

3. Shut down the Oracle database instance as follows:

sqlplus /nolog

shutdown immediate

exit

End of: Oracle |

Only valid for: MaxDB |

5.2 SAP MaxDB-Specific Procedure

In an SAP system environment, you can create a homogeneous copy of an SAP MaxDB database by

using the backup and restore method. This method is suitable for creating an exact copy of an existing

database. The source of the copy is a complete data backup of your source database.

The SAPinst tool is used for installation on the target system host as described in the installation

documentation for your SAP solution. In SAPinst, you select the backup and restore method as the

database installation method.

This description is not valid for the liveCache system copy.

CAUTION

Make sure that you know the password of the database system administrator (SUPERDBA) from

the source system before you start the procedure below. Otherwise, you cannot access the

database contents on the target system.

You must also know the name of the SQL database schema on the source system, SAP<SAPSID> –

for example, SAPR3.

You can perform this procedure in the following ways:

■ Manual restore

SAPinst stops before the database instance initialization and asks you to perform the restore on the

target database. After you have performed restore and post-restore activities, you can continue the

installation in SAPinst.

■ Automatic restore

SAPinst performs the restore to import the data into the target system.

In this scenario, you have to use a single file as the backup medium for the whole backup. The

restore can use any SAP MaxDB backup, as long as it is a single file.

5 Database-Specific System Copy

5.2 SAP MaxDB-Specific Procedure

2011-12-15 PUBLIC 57/140

Page 58: System Copy NW 7.3

NOTE

The minimum size of the database is calculated from the size of the backup file.

Advantages

■ You can use existing offline backups.

■ This method is faster than the database-independent method using R3load or Jload [page 21].

Disadvantage

You can only copy between systems with the same byte order.

Prerequisites

■ Byte order – little-endian or big-endian

You can use the backup and restore method to copy systems with the same byte order. That is,

you can copy a system based on little-endian to another system based on little-endian. You can

also copy a system based on big-endian to another system based on big-endian. Check SAP Note

552464 to find out which processor and operating system combination uses which byte order.

■ Data backup

You perform the complete data backup of your source database.

■ Recovery tool (manual restore)

You are using the SAP MaxDB Database Manager (DBMGUI) version 7.5.0 Build 12 or above. For

more information, see:

http://maxdb.sap.com/doc/7_6/default.htm Tools Database Manager GUI

Alternatively, you can use Database Studio. For more information, see:

http://maxdb.sap.com/doc/7_7/default.htm Tools Database Studio

■ Database Software

The database software on the target host must have the same version as the software on the source

host. The build number of the software version on the target host must be greater than or equal

to the version on the source host.

■ Size of the data on the target system

The size of the target system must be greater than the used space on the source system. You can

find the size of the used pages on the source system as follows:

dbmcli —d <database_name> —u <dbm_user>,<password> —n <database_server> —u SQL

sap<sid>,<password> sql_execute 'SELECT USEDPERM FROM SERVERDBSTATISTICS'

The result of this query is the amount of used space, expressed as the number of 8 KB pages. To

get the used space in MB, divide this value by 128. When SAPinst prompts you, configure the

database data volumes according to this value.

■ JRE

You must have installed JRE version 1.5 or higher on your system.

The JAVA_HOME environment variable must point to the JRE directory.

5 Database-Specific System Copy

5.2 SAP MaxDB-Specific Procedure

58/140 PUBLIC 2011-12-15

Page 59: System Copy NW 7.3

Process

Steps to Perform on the Target System

1. To import the target system, start SAPinst as follows and then follow the prompts:

<Your Product> System Copy Target System <System Variant> <Technical Stack>

2. When SAPinst prompts for the database copy method, choose Homogeneous System Copy.

3. In the MaxDB Backup Template screen, choose one of the following, Manual Restore, or Restore by

SAPinst:

■ Manual restore

In the execution phase, you are prompted to do the following:

1. Start the data recovery wizard from DBMGUI

1. Register your database instance in the DBMGUI

2. Check the database instance in the admin state.

3. Choose Recovery Recovery with Initialization ...

4. In type of recovery, select Restore a medium.

5. Specify the backup medium.

6. Start the restore procedure.

NOTE

The recovery wizard does not start the recovery immediately. It initializes the

database instance first. It takes some time for the database server to format the

database volumes.

2. After the restore, check the state of the target database instance. Change the database state

to online if it is not already in online state.

3. Delete the entries from the following tables to make sure that information about the

backup history for update statistics in the Computing Center Management System

(CCMS) from the old system does not appear in the new system:

CNHIST, CNREPRT, CNMEDIA, DBSTATHADA, DBSTAIHADA, DBSTATIADA, DBSTATTADA,

SDBAADAUPD

4. Continue with SAPinst or restart it if you stopped it during the recovery.

■ Restore by SAPinst

Enter the following information:

● Template name

● Device/file

4. After installation is completed, maintain the database connection for CCMS.

For more information, see SAP Note 588515.End of: MaxDB |

5 Database-Specific System Copy

5.2 SAP MaxDB-Specific Procedure

2011-12-15 PUBLIC 59/140

Page 60: System Copy NW 7.3

Only valid for: Windows | MS SQL Server |

5.3 MS SQL Server-Specific Procedure

This section describes how to perform a homogeneous system copy of an MS SQL Server database by

using the backup/restore method, or the detach/attach method in an SAP environment. The SAPinst

installation tool supports both methods.

The backup/restore method and the detach/attach method have the following advantages compared

to the R3load method:

■ You can use an existing backup.

■ These methods are much faster than the database-independent method [page 21].

NOTE

● For more information about the system copy procedure, see also SAP Notes 193816 and

151603.

● With SQL Server, you can use backup images across the platforms x86, IA64, x64. That is,

you can make a backup on one type of platform and use it on another type.

● You can only attach SQL Server 2000 files to SQL Server 2005 but not the other way

around.

Process

1. Detach the database files from the source system database or create a backup and copy the files to

the target system.

2. Attach the database files or restore the backup of the source database on the target database server.

3. Run SAPinst to install the target system by choosing the following on the Welcome screen:

<Your Product> System Copy Target System <System Variant> Based on <Technical Stack> .

Choose the installation options exactly in the order they appear.

For more information, see the MS SQL Server installation guide for your SAP system at:

http://service.sap.com/instguides <Your SAP Product> Installation .

4. When SAPinst prompts for the database copy method, choose Homogeneous System Copy.End of: Windows | MS SQL Server |

Only valid for: IBM DB2 for Linux and UNIX and Windows |

5.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures

The database-specific procedure for the creation of a system copy is based on a restore of an existing

online or offline backup. Therefore, this method is also referred to as backup/restore procedure. Since you

can use a DB2 backup cross-platform within certain limitations (see below), this method is not limited

to the homogenous system copy only.

5 Database-Specific System Copy

5.3 MS SQL Server-Specific Procedure

60/140 PUBLIC 2011-12-15

Page 61: System Copy NW 7.3

NOTE

You can also create an SAP system copy with a DB2 database if more advanced techniques like file

system snapshots are available. The necessary procedure in this case is called database relocation. The

database relocation procedure differs significantly from the backup/restore procedure and is

not described in this guide.

For more information, see the Database Administration Guide: SAP on IBM DB2 for Linux, UNIX, and

Windows, section db2inidb Option: as snapshot.

SAPinst is used for the installation on the target system host as described in the installation

documentation for your SAP component. Before you start SAPinst on the target system make sure

that all prerequisites for the SAP system installation are met. Especially, make sure that the relevant

file systems are available. For more information, see the appropriate installation guide at http://

service.sap.com/instguidesnw <Your SAP NetWeaver Release> Installation Installation – SAP

NetWeaver Systems

In an ABAP system, only the SAPinst steps for setting up and loading the database are replaced by a

database restore.

Advantages of the Backup Method

■ You can use existing online and offline backups.

■ Using the backup method is faster than the database-independent method [page 21].

Disadvantages of the Backup Method

■ You cannot change the name of the database schema. The name of the database schema is the

same as that of the source system. This implies that the name of the database connect user does

not change either.

■ You cannot copy an individual MCOD component to another system. You can only copy the

complete system.

Prerequisites

■ It must be possible to restore the backup of the source system on the platform of the target system.

NOTE

With DB2, you can use backup images cross-platform within certain limitations. If you want

to use the backup/restore method between different platforms, you must follow the

additional instructions in SAP Note 628156.

For more information about cross-platform backups, also see Backup and restore operations between

different operating systems and hardware platforms in the IBM DB2 Information Center at http://

publib.boulder.ibm.com/infocenter/db2luw/v9r7/ index.jsp?topic=/

com.ibm.db2.luw.admin.ha.doc/doc/c0005960.html.

■ If errors occur when restoring the backup on the target system, the complete restore must be

repeated.

5 Database-Specific System Copy

5.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures

2011-12-15 PUBLIC 61/140

Page 62: System Copy NW 7.3

Process

1. You perform an online or offline backup.

If you use an online backup to copy your system, a rollforward of your database is required after

the database restore on the target system. As a prerequisite, the respective database logs must be

accessible. We, therefore, recommend that you include the necessary log files in the backup image.

As of DB2 V9.5, logs are included in the online backup image as long as the option EXCLUDE LOGS

is not specified.

2. To create a target system, run SAPinst on the target system host by choosing the following on the

Welcome screen:

<Your Product> System Copy Target System <System Variant> <Technical Stack>

Perform the installation options in the given sequence and follow the instructions on the SAPinst

dialogs. When SAPinst prompts for the database copy method, choose Homogeneous System Copy.

CAUTION

Be aware of the following constraints when using the backup method for a homogeneous

system copy:

■ Since you cannot change the name of the database schema, you can neither change the

connect user. During the dialog phase you have to make sure that you enter the name

of the connect user exactly as you did on your source system.

■ The tablespace names remain the same during the database restore. However, you can

change them after the installation.

■ If you want to change the name or the location of the DB2 container on the target system,

you have to adapt the DB2 container paths or names in the redirected restore script and

then perform a redirected restore. For more information, see the documentation Database

Administration Guide: SAP on IBM DB2 Universal Database for UNIX and Windows, section Usage of

Tool brdb6brt.

3. Multi-Partition Database Environments only: Add database partitions

If you copy a system with multiple database partitions, the target system must have the same

number of partitions as the source system. For more information, see Setting up partitioned database

environments in the IBM DB2 Information Center at:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/ index.jsp?topic=/

com.ibm.db2.luw.qb.server.doc/doc/t0023605.html

4. Restore your database.

To restore your database, you can choose between one of the following options:

■ Simple database restore

To perform a database restore, use the DB2 RESTORE command. For more information, see the

IBM manual DB2 Command Reference.

5 Database-Specific System Copy

5.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures

62/140 PUBLIC 2011-12-15

Page 63: System Copy NW 7.3

NOTE

With a simple restore, you can neither change the name nor the location of DB2

containers.

■ Redirected restore

This is the recommended method.

A redirected restore allows you to change the name or the location of the DB2 container. To

perform a redirected restore, you use the DB2 RESTORE DATABASE command with the REDIRECT

GENERATE SCRIPT option. For more information, see RESTORE DATABASE command in the IBM

DB2 Information Center at:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/

com.ibm.db2.luw.admin.cmd.doc/doc/r0001976.html.

Alternatively, you can use the tool brdb6brt that retrieves a database backup and creates a

CLP script to restore this backup image. Since brdb6brt needs to connect to the source system,

the source system must be available. For more information about how to use the tool

brdb6brt, see Redirected Restore Using brdb6brt in the Database Administration Guide: SAP on IBM DB2

Universal Database for UNIX and Windows.

If you have used an online backup, you have to make sure that you have access to the log files that

were created during the online backup. You also have to perform a rollforward operation to bring

the database into a consistent state.

You can now continue with the installation.

5. To adhere to the SAP standard naming conventions for tablespaces, we recommend that you

consider renaming the tablespaces after the installation to reflect the new system name. To rename

a single tablespace, enter the following command:

db2 rename tablespace <old name> to <new name>

EXAMPLE

db2 rename tablespace <SAPSID_SOURCE>#STABD to <SAPSID_TARGET>#STABD

If you use the deferred table creation function, you also have to execute the following command

for each renamed tablespace using the db6util tool:

db6util -rtvt <old tbs> <new tbs>

For more information, see SAP Note 1227165.

CAUTION

Make sure that you use an up-to-date version of the db6util tool. You require at least a

version that supports the option -rtvt. To check the command options of the db6util tool,

enter the following command:

db6util –h

5 Database-Specific System Copy

5.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures

2011-12-15 PUBLIC 63/140

Page 64: System Copy NW 7.3

In addition, you have to update the tablespace names in tables TSDB6, IADB6, and TADB6. To

rename all tablespaces in the respective tables according to the standard naming conventions, use

the following commands:

■ For table TSDB6, enter the following SQL command:

update <connect_user_name>.tsdb6 set tabspace = '<SAPSID_TARGET>#'||substr

(tabspace,5,length(tabspace)-4), indspace='<SAPSID_TARGET>#'||substr(indspace,

5,length(indspace)-4)

■ For table IADB6, enter the following SQL command:

update <connect_user_name>.iadb6 set tabspace = '<SAPSID_TARGET>#'||substr

(tabspace,5,length(tabspace)-4)

■ For table TADB6, enter the following SQL command:

update <connect_user_name>.tabdb6 set tabspace = '<SAPSID_TARGET>#'||substr

(tabspace,5,length(tabspace)-4)

Follow-up Activities

After the installation on the target system, you perform the following steps:

■ The tablespaces SYSTOOLSPACE and SYSTOOLSTMPSPACE are used by certain DB2 tools and SQL

administrative routines to store historical and configuration information. We recommend that

you drop and re-create these tablespaces in the target system as follows:

1. Log on to the database server of the target system as user db2<dbsid>.

2. Generate the DDL statements for the tablespaces of the system by entering the following

command on the DB2 command line:

db2look -d <DBSID> -l -o <filename>.sql

3. Drop both tablespaces by entering the following command:

db2 drop tablespace SYSTOOLSPACE, SYSTOOLTMPSPACE

4. Look up the CREATE TABLESPACE statements for SYSTOOLSPACE and SYSTOOLSTMPSPACE in

<filename>.sql.

5. Execute both statements on the DB2 command line.

For more information, see SYSTOOLSPACE and SYSTOOLSTMPSPACE tablespaces in the IBM DB2

V9.5 Information Center at http://publib.boulder.ibm.com/infocenter/db2luw/ v9r5/topic/

com.ibm.db2.luw.admin.gui.doc/doc/c0023713.html.

■ If you performed a redirected restore, check all settings of the database manager and database

configuration parameters. Specifically, make sure that the following configuration parameters

point to the correct path:

● DIAGPATH (DBM)

● JDK_PATH (DBM)

● DFTDBPATH (DBM)

● Path to log files (DB)

5 Database-Specific System Copy

5.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures

64/140 PUBLIC 2011-12-15

Page 65: System Copy NW 7.3

● If set, NEWLOGPATH (DB), OVERFLOWLOGPATH (DB), FAILARCHPATH (DB) and MIRRORLOGPATH (DB)

More Information

■ Database Administration Guide: SAP on IBM DB2 for Linux, UNIX, and Windows and Database Administration

Using the DBA Cockpit: IBM DB2 for Linux, UNIX, and Windows at:

http://service.sap.com/instguidesnw <Your SAP NetWeaver Release> Operations Database-

Specific Guides

■ IBM DB2 9.7 Information Center at:http://publib.boulder.ibm.com/infocenter/db2luw/v9r7

■ IBM Manuals for DB2 9.7 at:

http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg27015148

End of: IBM DB2 for Linux and UNIX and Windows |

Only valid for: IBM DB2 for i5/OS |

5.5 IBM DB2 for i Specific Procedure

In an SAP system environment, you can create a homogeneous system copy of a DB2 database using

theSAV/RSTLIB method.

A system copy consists of the export of the source system and the import of the target system. The

export is normally done by SAPinst. However, for the homogenous system on IBM DB2 for i using the

SAV/RSTLIB method you can only perform a SAVLIB of the library R3<SID>DATA. Finally, you have to

copy and transfer the saved database library to the IBM i host on which you want to create the target

system. The import will be performed similar to a normal installation.

You have to start the SAPinst by choosing <Your Product> System Copy Target System <System

Variant> Based on <Technical Stack> . When SAPinst prompts for the database copy method, you choose

Homogeneous System Copy for the database specific method. This method gives you the opportunity to

restore the saved library by using RSTLIB. SAPinst creates a restore command from your entered input

and restores the database library automatically.

Advantage of the Offline System Copy Method

This method is faster than the database-independent method [page 21].

For more information, see SAP Note 585277.End of: IBM DB2 for i5/OS |

Only valid for: IBM DB2 for z/OS |

5.6 IBM DB2 for z/OS Specific Procedures

In an SAP system environment, you can create a homogeneous system copy of a DB2 database using

the offline system copy method.

5 Database-Specific System Copy

5.5 IBM DB2 for i Specific Procedure

2011-12-15 PUBLIC 65/140

Page 66: System Copy NW 7.3

This document assumes that the database schema of your SAP system is SAPR3. If you employ a different

schema, adapt the references to SAPR3 in the following SQL statements and jobs to reflect the actual

schema name.

The following section describes an offline system copy method for SAP systems on IBM DB2 for z/

OS.

For this example system copy, the high level qualifier of the source system is assumed to be D8A0 of the

target system D8B0.

System Copy Mode

If you install a primary application server instance on the target system, make sure that you select

Custom Mode.

Advantage of the Offline System Copy Method

This method is faster than the database-independent method [page 21].

Restriction of the Offline System Copy Method

At the moment, you cannot copy an individual MCOD component to another system. You can only

copy the complete system.

NOTE

The offline system copy must be performed by an experienced database administrator.

You can find an adapted procedure for an online system copy in the IBM documentation High

Availability for SAP on zSeries Using Autonomic Computing Technologies.

Prerequisites

The following prerequisites must be fulfilled to use this method:

■ The permissions of the source and target systems must be completely separate. The source system

must not be able to use the resources of the target system, and the target system must not be able

to use the resources of the source system.

■ RACF authorization for the target DB2 subsystem is complete.

■ Source and target systems must work with DB2 managed objects.

■ Tablespaces are not partitioned.

■ The system copy is made from a nondata sharing system to a nondata sharing system.

■ Procedures of the source and the target system are defined in the DB2 PROCLIB.

■ Source and target systems have their appropriate entries in the APF list.

■ Volumes of the source and target systems are managed by SMS.

■ Source and target systems run with the same DB2 service level.

Variables Used in this Procedure

■ Source System = D8A0

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

66/140 PUBLIC 2011-12-15

Page 67: System Copy NW 7.3

■ Target System = D8B0

■ Storage Group = TEMPORA

■ High Level Qualifier = HLQ

■ Boot Strap Data Set = BSDS

Main Steps in this Procedure

The following sections contain the detailed steps involved in the homogeneous system copy procedure

for DB2 for z/OS.

In the following steps, storage groups must be modified to apply the new high level qualifier. This can

be achieved by dropping and recreating the storage groups with the new high level qualifier (and

volumes).

To prepare the DB2 catalog of the target system, you must run JCL jobs created by SQLs running in

the source system.

The offline system copy can be divided into the following steps:

1. Check the Source System for Consistency

2. Stop and Restart the Source System

3. Run SQLs in the Source System

4. Capture View Definitions (if you intend to change the schema name.)

5. Stop the Source System

6. Print the Bootstrap Data Sets

7. Make Copies of the Source Data Sets

8. Create the Target System

9. Post-process the Target System

10. Changing the VCAT of the Target System

11. Changing the Schema of the Target System (DB2 V9 only)

12. Adapting WLM Application Environments for DB2 Stored Procedures

JCL jobs and SQL Statements

The JCL jobs and SQL Statements are now located in a compressed file (.zip) that is attached to SAP

Note 680746.

The path for each file is given in the section that previously contained the code.

5.6.1 Step 1: Check Consistency

The following is a list to help you check the source system for consistency.

■ Check if there are threads.

■ Check for authorized utilities using the following:

DISPLAY DATABASE(*) UTIL(*) and press [ENTER]

Your output should be:

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

2011-12-15 PUBLIC 67/140

Page 68: System Copy NW 7.3

No authorized utility found.

If there are running utilities, you must shut them down properly before continuing.

■ Ensure that all DB2 objects of the source system are started RW mode.

This can be checked with

DISPLAY DATABASE(*) SPACENAM(*)

with keyword

RESTRICT.

For more information, see DB2 UDB for z/OS and OS/390 Command Reference (SC26-9932-05).

■ If there are no objects in pending status, the source system must be stopped.

5.6.2 Step 2: Stop and Restart the Source System

Now you must stop and restart the source system with the ACCESS (MAINT) command option to

prohibit any authorization IDs other than install SYSADM and install SYSOPR.

5.6.3 Step 3: Run SQL Statements in the Source System

Prerequisites

As described earlier in this section, you must stop and restart the source system with the ACCESS(MAINT)

command option to prevent changes and to obtain consistent data.

Information for IBM DB2 V9 for z/OS

If you are running your system with DB2 V9, note that SQL Statements 2 through 9, as well as Creating

a New Storage Group Using the HLQ of the Target System are not relevant tasks for this procedure.

Activities

Execute all the following SQL statements in the source system:

5.6.3.1 SQL Statement Number 01

This statement is located at

HSCProcedure\Step3\STMT01.SQL

in the .zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs and

SQL Statements.

With this statement, you identify user-defined indexes that you need to change in the DB2 catalog. For

more information, see Step 8e: Changing the User-Defined Indexes in the DB2 Catalog [page 79].

Output

The output of this statement is similar to the following:

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

68/140 PUBLIC 2011-12-15

Page 69: System Copy NW 7.3

EXAMPLE

---------+---------+---------+---------+---------+-----

NAME DBNAME INDEXSPACE

---------+---------+---------+---------+---------+-----

SYSTBLSP~0 DSNDB06 SYSTBLSP

SYSTABLE~0 DSNDB06 SYSTABLE

SYSIXPART~0 DSNDB06 SYSIXPAR

5.6.3.2 SQL Statement Number 02

This statement is located at

HSCProcedure\Step3\STMT02.SQL

in the .zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs and

SQL Statements.

With this statement, you identify all databases that you want to stop at a later point in time in the target

system:

NOTE

This task is not relevant for DB2 V9.

Output

The output of this statement is similar to the following:

EXAMPLE

-STOP DATABASE (A000XAAA)

-STOP DATABASE (A000XAAB)

-STOP DATABASE (A000XAAC)

-STOP DATABASE (A000XAAD)

-STOP DATABASE (A000XAAE)

-STOP DATABASE (A000XAAF)

-STOP DATABASE (A000XAAG)

-STOP DATABASE (A000XAAH)

-STOP DATABASE (A000XAAI)

-STOP DATABASE (A000XAAJ)

-STOP DATABASE (A000XAAK)

-STOP DATABASE (A000XAAL)

.

.

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

2011-12-15 PUBLIC 69/140

Page 70: System Copy NW 7.3

.

and so on

5.6.3.3 SQL Statement Number 03

This statement is located at

HSCProcedure\Step3\STMT03.SQL

in the .zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs and

SQL Statements.

With this statement, you identify all tablespaces to be connected at a later point in time to the temporary

storage group TEMPORA:

NOTE

This task is not relevant for DB2 V9.

Output

The output of this statement is similar to the following:

EXAMPLE

ALTER TABLESPACE A000XAAA.ABAPTREE USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ABAPTREE USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADIRACCE USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADOWNERR USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADRCOMCS USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADRDIFIN USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADRGS2 USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADR10 USING STOGROUP TEMPORA; COMMIT;

5.6.3.4 SQL Statement Number 04

This statement is located at

HSCProcedure\Step3\STMT04.SQL

in the .zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs and

SQL Statements.

With this statement, you identify all indexes to be connected with storage group TEMPORA.

NOTE

This task is not relevant for DB2 V9.

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

70/140 PUBLIC 2011-12-15

Page 71: System Copy NW 7.3

Output

The output of this statement is similar to the following:

EXAMPLE

ALTER INDEX "DSNACC"."UTLEX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTLSTX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTPEBX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTPETX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTPEX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTPRCX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTRESTARTX" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTRESTART2X" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTTMDX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTTMPX01" USING STOGROUP TEMPORA; COMMIT;

.

.

and so on

5.6.3.5 SQL Statement Number 05

This statement is located at

HSCProcedure\Step3\STMT05.SQL

in the .zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs and

SQL Statements.

Storage groups in the target system still contain the high level qualifier of the source system. With this

statement, you identify storage groups to be dropped at a later point in time with the following

statement:

NOTE

This task is not relevant for DB2 V9.

Output

The output of this statement is similar to the following:

EXAMPLE

DROP STOGROUP SYSDEFLT; COMMIT;

DROP STOGROUP SAPU1I; COMMIT;

DROP STOGROUP SAPU1D; COMMIT;

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

2011-12-15 PUBLIC 71/140

Page 72: System Copy NW 7.3

DROP STOGROUP SAPSOI; COMMIT;

DROP STOGROUP SAPSOD; COMMIT;

DROP STOGROUP SAPESI; COMMIT;

DROP STOGROUP SAPESD; COMMIT;

DROP STOGROUP SAPPRI; COMMIT;

DROP STOGROUP SAPPRD; COMMIT;

DROP STOGROUP SAPLOI; COMMIT;

.

.

and so on

5.6.3.6 SQL Statement Number 06

This statement is located at

HSCProcedure\Step3\STMT06.SQL

in the .zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs and

SQL Statements.

NOTE

This task is not relevant for DB2 V9.

With this statement, you identify storage groups to be created at a later point in time with the high

level qualifier of the target system. In this case, we assume that FR01 is the high level qualifier of the

target system.

Storage Group Naming Conventions

Some storage group names may have to be adapted for all storage groups for which the creator is your

SQLID and not SAPR3. The naming convention is as follows:

ABAP Storage Group Naming Convention

Schema Storage Group Name

SAPR3 SAP<SI><I|D>

other <SID><SI><I|D>

NOTE

<SI> signifies the two-character STORAGEID of the table type (TABART).

Java Storage Group Naming Convention

Schema Storage Group Name

<schema> <schema>

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

72/140 PUBLIC 2011-12-15

Page 73: System Copy NW 7.3

CAUTION

For Java, the schema name is also the name of the storage group. You must not change the name

of the storage group. Be aware that as of DB2 V9, you can use the CATMAINT utility to globally

switch a schema name.

Output

The output of this statement is similar to the following:

EXAMPLE

CREATE STOGROUP SYSDEFLT VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPU1I VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPU1D VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPSOI VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPSOD VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPESI VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPESD VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPPRI VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPPRD VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPLOI VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPLOI VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPLOD VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

.

.

and so on

5.6.3.7 SQL Statement Number 07

This statement is located at

HSCProcedure\Step3\STMT07.SQL

in the .zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs and

SQL Statements.

With this statement, you connect tablespaces with their previous storage groups, which now contain

the high level qualifier of the target system.

NOTE

This task is not relevant for DB2 V9.

Output

The output of this statement is similar to the following:

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

2011-12-15 PUBLIC 73/140

Page 74: System Copy NW 7.3

EXAMPLE

ALTER TABLESPACE "DSNRLST"."DSNRLS01" USING STOGROUP SYSDEFLT;COMMIT;

ALTER TABLESPACE "BCXXXC5E"."SYNCLOG" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXXC5E"."DDDBRTH" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXX3UT"."DDDBTAB" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXX3UT"."LDDDBT3U" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXX3UT"."DDDBRTX" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXXC5E"."JMSDMSG" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "CC390"."UTTEMPL" USING STOGROUP SYSDEFLT;COMMIT;

ALTER TABLESPACE "CC390"."UTPROC" USING STOGROUP SYSDEFLT;COMMIT;

ALTER TABLESPACE "CC390"."UTRSTRT" USING STOGROUP SYSDEFLT;COMMIT;

.

.

and so on

5.6.3.8 SQL Statement Number 08

This statement is located at

HSCProcedure\Step3\STMT08.SQL

in the .zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs and

SQL Statements.

With this statement, you connect indexes with their previous storage groups, which now contain the

high level qualifier of the target system.

NOTE

This task is not relevant for DB2 V9.

Output

The output of this statement is similar to the following:

EXAMPLE

ALTER INDEX "SAPD5Z"."SYSTBLSPß0" USING STOGROUP SYSDEFLT;COMMIT;

ALTER INDEX "SAPD5Z"."SYSTABLEß0" USING STOGROUP SYSDEFLT;COMMIT;

ALTER INDEX "SAPD5Z"."SYSIXPARTß0" USING STOGROUP SYSDEFLT;COMMIT;

ALTER INDEX "STEM"."DSNARL01" USING STOGROUP SYSDEFLT;COMMIT;

.

.

and so on

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

74/140 PUBLIC 2011-12-15

Page 75: System Copy NW 7.3

5.6.3.9 SQL Statement Number 09

This statement is located at

HSCProcedure\Step3\STMT09.SQL

in the .zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs and

SQL Statements.

With this statement, you identify all databases to be started after DB2 catalog manipulations.

NOTE

This task is not relevant for DB2 V9.

Output

The output of this statement is similar to the following:

EXAMPLE

-START DATABASE (A000XAAA)

-START DATABASE (A000XAAB)

-START DATABASE (A000XAAC)

-START DATABASE (A000XAAD)

-START DATABASE (A000XAAE)

-START DATABASE (A000XAAF)

-START DATABASE (A000XAAG)

-START DATABASE (A000XAAH)

-START DATABASE (A000XAAI)

-START DATABASE (A000XAAJ)

-START DATABASE (A000XAAK)

-START DATABASE (A000XAAL)

.

.

and so on

5.6.4 Step 4: Capturing View Definitions with DB2 V9 (if the Schema Name is to be Changed)

DB2 V9 adds the capability to change the VCAT name to the CATMAINT utility. This new capability

facilitates homogenous system copy. Moreover, the CATMAINT utility can change the schema and

creator of objects.

If you intend to also change the schema name as part of the homogeneous system copy, for example

for SAP Java systems, you need to capture the view definitions in this step. This is necessary since

renaming the schema using CATMAINT requires that no views exist on the tables for which a VCAT name

is changed. Therefore, the view definitions are exported in this step using R3ldctl.

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

2011-12-15 PUBLIC 75/140

Page 76: System Copy NW 7.3

As part of the post-processing steps that are performed in the target system, the saved view definitions

are later used to re-create the views in the target system. The views may also be saved and later re-

created in the target system using alternative tools.

Procedure

To export the view definitions using R3ldctl:

1. Run R3ldctl without parameters to create the DDLDB2.TPL file, the SAPVIEW.STR file, and others

2. Store these files

5.6.5 Step 5: Stop the Source System

Stop the source system with the following command option:

MODE (QUIESCE)

5.6.6 Step 6: Making Copies of Source Data Sets

With this step, you make copies of the source data sets, which includes:

■ DB2 bootstrap data sets

■ DB2 logcopy data sets

■ All DB2 VSAM data sets belonging to the source system

With these JCL jobs, you can make copies of the source data sets:

■ HSCProcedure\Step6\DUMPA0.JCL

■ HSCProcedure\Step6\DUMPA1.JCL

■ HSCProcedure\Step6\DUMPA2.JCL

■ HSCProcedure\Step6\DUMPLIB.JCL

■ HSCProcedure\Step6\DUMPLOG.JCL

■ HSCProcedure\Step6\DUMPREST.JCL

All scripts are located in the .zip file [page 65] attached to SAP Note 680746. For more information, see

the section JCL Jobs and SQL Statements.

NOTE

The source system can be restarted now. It is no longer needed for the following system copy

process.

5.6.7 Step 7: Creating the Target System

With the following JCL jobs, you create the target system.

In the first step, the dumps of the source system have to be restored. All data sets of the source system

have to be restored with the high level qualifier of the target system.

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

76/140 PUBLIC 2011-12-15

Page 77: System Copy NW 7.3

All statements are located in the .zip file [page 65] attached to SAP Note 680746. For more information,

see the section JCL Jobs and SQL Statements.

■ HSCProcedure\Step7\RSTOREA0.JCL

■ HSCProcedure\Step7\RSTOREA1.JCL

■ HSCProcedure\Step7\RSTOREA2.JCL

■ HSCProcedure\Step7\RSTORELI.JCL

■ HSCProcedure\Step7\RSTORELO.JCL

■ HSCProcedure\Step7\RSTORERE.JCL

5.6.8 Step 9a: Changing the Bootstrap Data Sets (BSDS)

Before starting the target system, the BSDS must be changed.

The JCL jobs listed here are located in the .zip file [page 65] attached to SAP Note 680746. For more

information, see the section JCL Jobs and SQL Statements.

1. Change the HLQ entry in the BSDS of the target system, using the HLQ D8B0.

The corresponding JCL job is located at

HSCProcedure\Step9a\CHGBSDS1.JCL

in the .zip file.

2. Change the log entries in the BSDS. The START and END RBA information as of utility DSNJU004

have to be used for the target system as follows:

The corresponding JCL job is located at

HSCProcedure\Step9a\CHGBSDS2.JCL

in the .zip file.

After changing the BSDS with these scripts, you can start the target system.

5.6.9 Step 9b: Start the Target System

When you start the DB2 target system for the first time, the system is still working with the work file

database of the source system. However, access fails with insufficient access authority, as seen in the

log.

Partial example of a LOG when you start the target system for the first time:

SYNTAX

.

.

.

. DSNR005I -D8B0 RESTART...COUNTS AFTER FORWARD 604 RECOVERY IN COMMIT=0, INDOUBT=0 DSNR006I -D8B0 RESTART...COUNTS AFTER BACKWARD 605 RECOVERY

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

2011-12-15 PUBLIC 77/140

Page 78: System Copy NW 7.3

INFLIGHT=0, IN ABORT=0, POSTPONED ABORT=0 DSNP012I -D8B0 DSNPCNP0 - ERROR IN VSAM CATALOG 606 LOCATE FUNCTION FOR D8A0.DSNDBC.DSNDB07.DSN4K01.I0001.A001 CTLGRC=AAAAAA08 CTLGRSN=AAAAAA08 CONNECTION-ID=D8E0, CORRELATION-ID=003.RCRSC 02, LUW-ID=* IKJ56228I DATA SET D8A0.DSNDBC.DSNDB07.DSN4K01.I0001.A001 NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED DSNB207I -D8B0 DYNAMIC ALLOCATION OF DATA SET 608 FAILED. REASON=17080002.DSNAME=D8A0.DSNDBC.DSNDB07.DSN4K01.I0001.A001 DSNT501I -D8B0 DSNITFFS RESOURCE UNAVAILABLE 609 CORRELATION-ID=D8E0 CONNECTION-ID=D8E0 LUW-ID=D8E0.D8E0.000000000000=0 REASON 00D70024....and so on

We strongly recommend that you maintain different RACF settings for different DB2 subsystems. If

not, the target system has access to the data sets of the source system and the data of the source system

could be changed by mistake.

The work file database data must be changed later in the clone process.

5.6.10 Step 9c: Creating a New STOGROUP Using the HLQ of the Target System

With this JCL job, you create a new STOGROUP using the HLQ of the target system (D8B0).

This JCL job is located at

HSCProcedure\Step9c\CRTMPSTO.JCL

.zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs and SQL

Statements.

NOTE

This task is not relevant for DB2 V9.

5.6.11 Step 9d: Stopping Index Spaces

With this JCL job, you stop the appropriate index spaces.

You find a list of index spaces in the output of SQL statement number 1 [page 68].

The JCL job is located at

HSCProcedure\Step9d\STOPIDXS.JCL

in the .zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs and

SQL Statements.

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

78/140 PUBLIC 2011-12-15

Page 79: System Copy NW 7.3

5.6.12 Step 9e: Changing the User-Defined Indexes in the DB2 Catalog

After starting the target system, the user-defined indexes (the output of SQL statement number 1 [page 68])

in the DB2 catalog must be changed, working with the new HLQ of the target system D8B0. The

following example script can be used to carry out this procedure.

Change the user-defined DB2 catalog indexes using the new storage group TEMPORA.

This JCL job is located at

HSCProcedure\Step9e\ALTERIDX.JCL

in the .zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs and

SQL Statements.

5.6.13 Step 9f: Restart the Index Spaces

At this point, you must restart the index spaces.

5.6.14 Step 9g: Creating the Temporary Files for the DB2 Target System

To create the temporary files for the DB2 target system:

1. Run part of DSNTIJTM to create temporary files for DB2. DSNTIJTM was generated by DSNTINST

(optional) or consists of a manually changed copy from another existing DB2 subsystem.

The JCL job is located in the .zip file atHSCProcedure\Step9g\CRTTMPFL.JCL.

The .zip file [page 65] attached to SAP Note 680746. For more information, see the section JCL Jobs

and SQL Statements.

2. Stop and restart the DB2 subsystem. The error as described in Step 6: Make Copies of the Sources Data

Sets [page 76] should not occur since DB2 is working with the new temporary files.

5.6.15 Step 9h: Implementing HLQ of the Target System in the Work File Database

In the next step, the work file database is changed to use the new HLQ D8B0.

Procedure

To change the work file database:

1. Drop work file database DSNDB07 in the target system, delete the clusters for 4K and 32K and create

them again.

2. Stop and restart the target system.

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

2011-12-15 PUBLIC 79/140

Page 80: System Copy NW 7.3

Error message IKJ56228I should not appear because DB2 is now working with its own work file

database.

5.6.16 Step 9i: Adjusting the DDF Location Name and Port Number

To allow communication with the SAP application servers of the DB2 target system, you must adjust

the DDF location name and port number.

Procedure

To adjust the DDF location name and port number, run the DB2 utility DSNJU003 with the option

DDF to specify the location name and port number.

5.6.17 Step 10 (DB2 V8 and Lower): Changing the VCAT of the Target System

The target system with the new HLQ D8B0 still works with storage groups using VCAT D8A0.

In the following steps, the DB2 catalog is manipulated by stopping the databases, altering tablespaces

and indexes, dropping and creating storage groups with the new VCAT D8B0, altering tablespaces and

indexes using the new storage groups, and starting all databases.

The objects to be manipulated are identified by the results of previously described SQL statements.

All SQL statements listed here are located in the.zip file [page 65] attached to SAP Note 680746. For more

information, see the section JCL Jobs and SQL Statements.

Procedure

1. Stop all databases

The corresponding JCL job is located at

HSCProcedure\Step10\STOPDBS.JCL.

2. Alter tablespaces using storage group TEMPORA

The corresponding JCL job is located at

HSCProcedure\Step10\ALTERTBS.JCL.

3. Alter indexes using storage group TEMPORA

The corresponding JCL job is located at

HSCProcedure\Step10\ALTERIDX.JCL.

4. Drop the storage groups

The corresponding JCL job is located at

HSCProcedure\Step10\DROPSTG.JCL.

5. Create the storage groups

The corresponding JCL job is located at

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

80/140 PUBLIC 2011-12-15

Page 81: System Copy NW 7.3

HSCProcedure\Step10\CREATSTG.JCL.

6. Alter tablespaces using their previous storage group

The corresponding JCL job is located at

HSCProcedure\Step10\ALTERTB2.JCL.

7. Alter indexes using their previous storage group

The corresponding JCL job is located at

HSCProcedure\Step10\ALTERID2.JCL.

8. Start all databases

This JCL job is located at

HSCProcedure\Step10\STARTDBS.JCL.

If necessary, change the user authorizations of the target system. The DB2 catalog still contains the

authorizations of the source system.

5.6.18 Step 10 (DB2 V9): Changing the VCAT of the Target System

To change the VCAT that is used for the storage groups of your SAP tables and indexes, proceed as

follows.

Procedure

1. Ensure that the DB2 EMD pool and DB2 EDM DBD cache have at least the following sizes:

■ EDMPOOL ≥ 200000 KB

■ EDMDBDC ≥ 300000 KB

2. Call the CATMAINT utility with the UPDATE VCAT option to switch the VCAT name

3. Reinstate the original sizes of EDMPOOL and EDMDBDC.

4. Start the DB2 subsystem in regular mode

If necessary, change the user authorizations of the target system. The DB2 catalog still contains the

authorizations of the source system.

5.6.19 Step 11 (DB2 V9): Changing the Schema of the Target System

To change the schema or creator name of your SAP tables and indexes, proceed as follows. This approach

requires that you have previously started R3ldctl on your source system to capture the view definitions

of the SAP system.

Procedure

1. If user-defined materialized query tables or triggers exist, save their definitions in a separate place.

2. Delete all views, materialized query tables, and triggers that exist on the SAP tables.

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

2011-12-15 PUBLIC 81/140

Page 82: System Copy NW 7.3

3. Ensure that the DB2 EMD pool and DB2 EDM DBD cache have at least the following sizes:

■ EDMPOOL ≥ 200000 KB

■ EDMDBDC ≥ 300000 KB

4. Call the CATMAINT utility with the SCHEMA SWITCH option to switch the schema name.

5. Reinstate the original sizes of EDMPOOL and EDMDBDC.

6. Start the DB2 subsystem in regular mode.

7. Recreate the views by implementing the following steps:

1. Generate the R3load task files by submitting the following command:

R3load -ctf I SAPVIEW.STR DDLDB2.TPL SAPVIEW.TSK DB2 -l SAPVIEW.log

2. Create an SAPVIEW.cmd file to prepare the recreation of the views. This file can contain the

following lines for example:

EXAMPLE

tsk: "SAPVIEW.TSK"

icf: "SAPVIEW.STR"

dcf: "DDLDB2.TPL"

dat: null

dir: null

ext: null

3. Call R3load with the option

-i SAPVIEW.cmd -dbcodepage <codepage> -l SAPVIEW.log

to re-create the views.

8. If user-defined materialized query tables or triggers exist, re-create them.

5.6.20 Step 12: Adapting WLM Application Environments for DB2 Stored Procedures

The WLM environments of the WLM-established stored procedures need to be changed if the target

system is running with other WLM environments.

Procedure

To change the WLM environments of the WLM-established stored procedures, carry out the following

steps:

1. Create WLM application environments for the DB2 stored procedures as described in the SAP DBA

Guide: DB2 for z/OS.

2. Use the ALTER PROCEDURE statement as described in the IBM documentation DB2 for z/OS SQL

Reference.End of: IBM DB2 for z/OS |

5 Database-Specific System Copy

5.6 IBM DB2 for z/OS Specific Procedures

82/140 PUBLIC 2011-12-15

Page 83: System Copy NW 7.3

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:

■ Copying the Primary Application Server [page 83]

■ Copying the Database Only – Move [page 83]

■ Copying the Database Only – Refresh [page 85]

CAUTION

You cannot copy single usage types.

6.1 Copying the Primary Application Server Instance Only

As of SAP NetWeaver based on kernel 7.1, you can copy a primary application server instance only.

With this procedure, you can move a primary application server instance to a different host within

your system.

Procedure

1. Shut down all application servers.

2. Uninstall the old primary application server instance.

3. On your target host, run SAPinst on UNIX or Windows [page 29] or run SAPinst on IBM i [page 32].

4. On the Welcome screen, choose <Your Product> 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

You can use this procedure to move a database instance to a different host within your system. The

move can be done using either database-specific methods or the SAP standard method based on R3load/

Jload.

CAUTION

■ The DBSID must not be changed.

6 Copying Single Instances Only

6.1 Copying the Primary Application Server Instance Only

2011-12-15 PUBLIC 83/140

Page 84: System Copy NW 7.3

■ 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 SAPinst based uninstall procedure.

This always deletes the current database of the system.

Procedure

1. On the source host, run SAPinst on UNIX or Windows [page 29] or run SAPinst on IBM i [page 32] to

perform the export.

2. If you perform the export using R3load/Jload, on the Welcome screen, choose <Your Product>

System Copy Source System Based on <Technical Stack> Database Instance Export to export the

database.

If you perform the export using database-specific tools, you must start them manually.

3. On the target host, stop all SAP instances.

4. On the target system, run SAPinst and choose <Your Product> System Copy Target System <System

Variant> Based on <Technical Stack> Database Refresh or Move to install the database.

NOTE

Since the target database instance is to replace the source database, do not change the DBSID.

5. When SAPinst has completed the installation of the database, restart your system including all

instance services.

6. Shut down the old database instance.

7. Only valid for: UNIX | MaxDB |

Set up the xuser entries from the home directory of the user <sapsid>adm on each application

server as follows:

xuser -U <key> -u <dbuser>,<password> -d <dbsid> -n <dbhost> -S SAPR3 -t 0 -I 0 set

The required keys and dbusers are as follows:

■ Key DEFAULT with dbuser SAP<SID>

■ Key c with dbuser control

■ Key w with dbuser superdbaEnd of: UNIX | MaxDB |

8. Only valid for: Windows | MaxDB |

Set up the xuser entries from the home directory of the users <sapsid>adm and

SAPService<SID> on each application server as follows:

xuser -c <os_user> -U <key> -u <dbuser>,<password> -d <dbsid> -n <dbhost> -S SAPR3

-t 0 -I 0 set

The required keys and dbusers are as follows:

■ Key DEFAULT with dbuser SAP<SID>

■ Key c with dbuser control

■ Key w with dbuser superdbaEnd of: Windows | MaxDB |

6 Copying Single Instances Only

6.2 Copying the Database Only – Move

84/140 PUBLIC 2011-12-15

Page 85: System Copy NW 7.3

6.3 Copying the Database Only – Refresh

With this procedure, you can refresh the content of an existing database without having to copy the

primary application server instance and to reinstall additional applications servers. The refresh can be

done using either database-specific methods or the SAP standard method based on R3load/Jload.

CAUTION

■ When copying the database only, you cannot change to another database but need to perform

a database-homogeneous copy.

Prerequisites

The source system and the target system already exist.

Procedure

1. On the source system, note down the IDs for each of the Java instances in the profile of the

application server.

The ID is stored in the instance as parameter j2ee/instance_id.

2. On the source system, run SAPinst on UNIX or Windows [page 29] or run SAPinst on IBM i [page 32] to

perform the export.

3. If you perform the export using R3load/Jload, on the Welcome screen, choose <Your Product>

System Copy Source System Based on <Technical Stack> Database Instance Export to export the

database.

If you perform the export using database-specific tools, you must start them manually.

4. On the target system, stop all SAP instances.

5. Run SAPinst and choose <Your Product> System Copy Target System <System Variant> Based on

<Technical Stack> Database Refresh or Move to install the database.

Only valid for: IBM i5/OS |

CAUTION

On IBM i, you have to delete your database libraries manually before you start the installation.

Make sure that these libraries are currently not added to any library list. To delete a library,

use the command DLTLIB.

For ABAP, delete the libraries: R3<SID>DATA and R3<SID>JRN.

For Java, delete the libraries: SAP<SID>DB and SAP<SID>JRN.

Use the command DSPJOBLOG to analyze any upcoming error. Finally choose Next to start the

installation.

End of: IBM i5/OS |

6. When SAPinst has completed the installation of the database, adapt the profiles in the application

server on the target system by reassigning the profile IDs of the Java instances. Make sure that they

are the same as on the source system.

6 Copying Single Instances Only

6.3 Copying the Database Only – Refresh

2011-12-15 PUBLIC 85/140

Page 86: System Copy NW 7.3

NOTE

If there are more application servers on the target system than on the source system, you

have to reinstall the ones that additionally exist on the target system.

EXAMPLE

Source System:

ABC_DVEBMGS88_<host1>:j2ee/instance_id = ID8873787

ABC_D00_<host1>:j2ee/instance_id = ID32225

ABC_D20_<host2>:j2ee/instance_id = ID2078823

Target System (before reassignment):

XYZ_DVEBMGS77_<host1>:j2ee/instance_id = ID7732291

XYZ_D00_<host2>:j2ee/instance_id = ID74637

XYZ_D01_<host1>:j2ee/instance_id = ID129016

Target System (after reassignment):

XYZ_DVEBMGS77_<host1>:j2ee/instance_id = ID8873787

XYZ_D00_<host2>:j2ee/instance_id = ID32225

XYZ_D01_<host1>:j2ee/instance_id = ID2078823

CAUTION

One application server (AS) is assigned to exactly one Java instance, and the other way around.

That means that, in the target system, you need to assign every Java instance in the database to

exactly one application server. You cannot assign the same Java instance to more than one

application server.

6 Copying Single Instances Only

6.3 Copying the Database Only – Refresh

86/140 PUBLIC 2011-12-15

Page 87: System Copy NW 7.3

7 Follow-Up Activities

To finish the system copy of your SAP system:

■ Perform follow-up activities in the source system [page 87]

■ Perform follow-up activities in the target system [page 87]

7.1 Performing Follow-Up Activities in the Source System

Procedure

1. Reschedule your canceled jobs as follows:

Call transaction SM37 or choose SAP Menu Tools CCMS Background Processing Jobs - Overview

and Administration .

2. Using CCMS, adapt your operation mode timetable to the original status as follows:

Call transaction SM63 or choose SAP Menu Tools CCMS Configuration Operation Mode

Calendar .

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.

7.2.1 Performing Follow-Up Activities for ABAP

7.2.1.1 Activities at Operating System Level

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.

7 Follow-Up Activities

7.1 Performing Follow-Up Activities in the Source System

2011-12-15 PUBLIC 87/140

Page 88: System Copy NW 7.3

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.

12. Oracle only: Adapt the database profiles init<SAPSID>.ora, init<SAPSID>.dba, and

init<SAPSID>.sap.

7.2.1.2 Activities at Database Level

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. Oracle only:

1. Delete all entries from the following tables:

DBSTATHORA, DBSTAIHORA, DBSTATIORA, DBSTATTORA.

2. Delete the user OPS$<SOURCE_SAPSID>ADM (if existing).

3. If you changed the <DBSID> during the system copy, we recommend that you adapt the

global_name parameter by using the following SQL command:

alter database rename global_name to <NEW_DBSID>;

If the parameter does not exist on your system, ignore this step.

6. MaxDB only: Run report RSSDBTICMCLEANUP in the following cases:

■ You copied a system using MaxDB in both the source system and the target system.

■ You copied a system and changed the database platform from MaxDB to a different database

platform.

For more information, see SAP Note 1179714.

7.2.1.3 Activities at SAP System Level

Procedure

1. Run an installation check (transaction SM28).

2. Import the system profiles into the database (transaction RZ10).

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.

7 Follow-Up Activities

7.2 Performing Follow-Up Activities in the Target System

88/140 PUBLIC 2011-12-15

Page 89: System Copy NW 7.3

Only valid for: IBM DB2 for i5/OS |

Use the commands CLRPFM R3<SID>DATA/TPFET and CLRPFM R3<SID>DATA/TPFHT.End of: IBM DB2 for i5/OS |

4. If you changed the SAPSID during the system copy, delete all entries from table TLOCK, which holds

the repair requests from your source system.

5. Maintain the operation modes.

1. Create new operation modes and instance definitions (transaction RZ04).

2. Maintain the time table using the new operation modes (transaction SM63).

3. Delete the old operation modes and old instance definitions.

6. Adapt other CCMS settings (for example, alert thresholds, reorganization parameters of CCMS

table MONI) if required.

7. 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.

8. Define or remove the SAP system users and revise the authorizations of the system users: Tools

Administration User maintenance Users (transaction SU01).

9. Synchronize the buffers as described in SAP Note 36283 and adapt the client information for the

logical system.

10. Configure the spool server.

1. 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)

2. Delete obsolete spool requests and spool inconsistencies while executing the ABAP program

RSPO0041 (transaction SE38).

3. Call transaction SP12 and run report RSPO1043 for a spool data consistency check.

For more information, see SAP Notes 98065 and 48400.

11. Configure batch jobs.

1. Delete canceled and finished batch jobs while executing the RSBTCDEL ABAP program, selecting

Delete with forced mode (transaction SE38).

2. Adapt all jobs needed in the target system.

12. If you have used the DBA Calendar in the source system, redefine database actions (backup, update

statistics, and so on) (transaction DB13).

13. Maintain the security configuration.

1. Call transaction STRUST.

2. Replace all existing PSE files in the target system with new ones, which contain the new system's

information.

7 Follow-Up Activities

7.2 Performing Follow-Up Activities in the Target System

2011-12-15 PUBLIC 89/140

Page 90: System Copy NW 7.3

For more information, see the SAP Library [page 9] at:

SAP NetWeaver by Key Capability Security System Security System Security for SAP NetWeaver AS

ABAP Only Trust Manager 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.

14. 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.

1. To check and adapt qRFC destination, call transaction SMQR.

2. To check and adapt tRFC destination, call transaction SM58.

3. To delete obsolete RFC destinations, call transaction SM59.

15. Migrate the ABAP secure store.

1. Call transaction SECSTORE to change the entries in the secure storage.

2. In case of entries with errors with message text System-dependent data for entry … changed, see SAP

Note 816861

16. Configure the Transport Management System (TMS).

1. 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.

2. 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 .

7 Follow-Up Activities

7.2 Performing Follow-Up Activities in the Target System

90/140 PUBLIC 2011-12-15

Page 91: System Copy NW 7.3

4. Configure the domain controller in the Transport Management System (TMS) by using

transaction STMS.

NOTE

If you did not change the SAPSID 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.

17. 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 9] and the SAP Library [page 9] at:

SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Data Archiving .

18. Check self-defined external commands (transaction SM69).

19. Check the logical system names. For more information, see Preparations [page 15]. 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, read SAP Note 325525.

20. 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).

21. Check if you can delete clients that are no longer used in the target system (transaction SCC5).

22. Check the contexts and segments of remote application servers for the SAP Monitoring

Infrastructure if required (transaction RZ21).

23. 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.

24. BW only: 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.

Only valid for: SAP HANA DB |

NOTE

If you changed the database management system to SAP HANA database, use variant

SAP&POSTMGRHDB.

End of: SAP HANA DB |

If you did not change the database management system when copying the system, you have to

start program RS_BW_POST_MIGRATION in the background by using variant SAP&POSTMGR.

7 Follow-Up Activities

7.2 Performing Follow-Up Activities in the Target System

2011-12-15 PUBLIC 91/140

Page 92: System Copy NW 7.3

Program RS_BW_POST_MIGRATION performs necessary modifications on database-specific objects

(mainly BI objects).

25. 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.

7.2.1.4 Usage Type or Software Unit-Specific Follow-Up Activities

You have to perform the following activities for specific usage types or software units of the copied SAP

system.

7.2.1.4.1 Business Warehouse (BW)

Procedure

1. Perform the BW-specific follow-up activities as described at: http://www.sdn.sap.com/irj/

sdn/edw-ops Additional Information about the Lifecycle Management with SAP NetWeaver BW 7.x SAP

NetWeaver 7.0 – BW Systemcopy ABAP .

2. 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 9] at: 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 .

7.2.1.4.2 Embedded Search

Prerequisites

You have applied SAP Note 1293026.

Procedure

1. To establish the connection between TREX and the ABAP target server, run the script

configureTrexRfcConnection.py on the host where TREX is installed.

7 Follow-Up Activities

7.2 Performing Follow-Up Activities in the Target System

92/140 PUBLIC 2011-12-15

Page 93: System Copy NW 7.3

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 9] at:

SAP NetWeaver Library: Function-Oriented View Search Search Services in SAP NetWeaver AS ABAP

Embedded Search Configuration Guide Performing the Post-Installation of Embedded Search Creating

Search Object Connectors and Starting Indexing .

7.2.1.5 Checking the Target System

The following actions are suitable 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.

7 Follow-Up Activities

7.2 Performing Follow-Up Activities in the Target System

2011-12-15 PUBLIC 93/140

Page 94: System Copy NW 7.3

Only valid for: z/OS |

7.2.2 Performing Jobhead Correction after Homogeneous System Copy

NOTE

This section is only relevant for customers using CCMS to monitor their SAP systems.

After copying your system, the CCMS jobhead still points to the former database SSID. To complete

the homogeneous system copy, the SSID needs to be set to the target system.

CAUTION

Only experienced users should use this utility.

Procedure

To set the SSID to the target system:

1. Call transaction DBACOCKPIT.

2. Choose Configuration Homogeneous System Copy: Jobhead Correction

3. Modify the necessary data.End of: z/OS |

7 Follow-Up Activities

7.2 Performing Follow-Up Activities in the Target System

94/140 PUBLIC 2011-12-15

Page 95: System Copy NW 7.3

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

Purpose

The Migration Monitor is a tool that helps you to perform and control the unload and load process

during the system copy procedure. As of SAP NetWeaver 04 SR1 the Migration Monitor is integrated

into the SAPinst system copy tool, but you can also use the Migration Monitor to copy previous releases

by starting it manually.

For more information about how to start the Migration Monitor manually, see Starting the Migration

Monitor [page 106].

The Migration Monitor does the following:

■ Creating R3load command files

■ Creating R3load task files if required

■ Starting the R3load processes to unload the data

■ Transferring packages from the source to the target host if required

■ Starting the R3load processes to load the data as soon as a package is available

■ Informing the person performing the system copy in case of errors

Tool

The tool is located in the MIGMON.SAR SAPCAR archive. The archive file contains the following:

■ User Guide

● MigrationMonitor.pdf

■ 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

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

2011-12-15 PUBLIC 95/140

Page 96: System Copy NW 7.3

● import_monitor_cmd.properties

Prerequisites

■ Java Runtime Environment (JRE) version 1.6.1 or higher is installed.

■ The JAVA_HOME environment variable must point to the JRE directory.

■ The correct directory structure for R3load dump files must exist on both the source and target

hosts.

8.1.1 Configuration

The following options can be provided via the property file or via 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.

Help

With the following command line option, the tool displays all parameters available:

■ -help

Version

With the following command line option, the tool displays version information:

■ -version

General Options

General Options

Name Description Comments

monitorTimeout Monitor timeout in seconds During a timeout, the monitor thread sleeps and does not analyze any files or analyze its processing state. The default timeout value is 30 seconds.

E-Mail Options

Name Description Comments

mailServer SMTP server Server name or IP address of the company SMTP server

mailFrom “From” e-mail address non

mailTo “To” e-mail address Can contain an address list separated by “;” or blanks.

Additional Options

Name Description Comments

bg Enables background mode Takes effect only as command line option.

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

96/140 PUBLIC 2011-12-15

Page 97: System Copy NW 7.3

Name Description CommentsIf the tool is running in background mode, the UNIX shell windows or Windows command prompt can be closed after startup.

secure Enables secure mode Takes effect only as command line option.If the tool is running in secure mode, command line parameters (for example, passwords) are hidden for Java processes. Secure mode implicitly enables background mode.

NOTE

You should use this mode if you have to specify passwords on the command line.

trace Trace level Possible values:all, off, 1 (error), 2 (warning), 3 (info), 4 (config, default), 5, 6, 7 (trace)

Export Monitor - Options

Export Options

Option Description Comments

installDir Installation directory Directory where the installation tool (SAPinst, R3SETUP) is started. If you run the Migration Monitor without using the installation tools, then the installation directory is the directory where the R3load TSK and log files will be written.

exportDirs List of export directories Separator on Windows: “;”Separator on UNIX: “:”The exportDirs parameter points to the directory where the R3load dump files will be written. In the exportDirs directory, the subdirectories DATA, DB, and DB/<TARGET_DBTYPE> (for example, DB/ORA must exist.

client Client operating mode Running in client mode means that the Migration Monitor runs parallel to standard SAPinst export process and transfers the exported dump files to the import server.

server Server operating mode Running in server mode means that the Migration Monitor creates R3load TSK files (if necessary), R3load cmd files, and starts the R3load processes.

All options below are for server mode. The import monitor always runs in the server mode. If you want to run the export monitor in the server mode, specify the server parameter in the export monitor's properties file.

orderBy Package order Can be the name or path of the file that contains package names. If the option value is omitted then package order is not determined.

ddlFile DDL control file Path or filename of DDL control fileThe default is DDL<DBTYPE>.TPL.If the filename is used without path, then the DDL control file from the export DB subdirectory is used.

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

2011-12-15 PUBLIC 97/140

Page 98: System Copy NW 7.3

Option Description Comments

ddlMap DDL mapping file File with mapping between DDL files and package names

r3loadExe Path of the R3load executable

Optional; default is R3load. If only the name of the R3load executable is available, then JVM looks for the R3load executable using OS-specific process 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, then the monitor will not overwrite them.

dataCodepage Code page for data files See SAP Note 552464. Possible values: 4102, 4103, 1100

taskArgs 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 Number of parallel export jobs, default:1

Any positive number; 0 for an unlimited number of jobs. The value can be changed dynamically at runtime.

Network Exchange Options

Option Description Comments

net Network operating mode Exported dump files must be visible on the import host to use this mode.

netExchangeDir Network exchange directory CAUTION

Clean up the netExchangeDir before 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 exchange directory as a signal to the import monitor that the package has been exported successfully and that the import can be started.

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

98/140 PUBLIC 2011-12-15

Page 99: System Copy NW 7.3

FTP Exchange Options

Option Description Comments

ftp FTP operating mode Exported dump files will be transferred automatically from the source host (directory exportDirs) to the target host (directory importDirs) using FTP.

ftpHost Remote FTP host Name or IP address of the import server.

ftpUser Name of the remote FTP user The FTP user specified here should be <sapsid>adm to make sure that the package files can be read by during the import (which is started as <sapsid>adm).

ftpPassword Password of the remote FTP user CAUTION

Security risk!

For more information, see the secure parameter in section Additional Options.

ftpExportDirs List of remote FTP directories for export dump

Both “;” and “:” separators are valid. This is the directory on the target host to which the dump will be transferred. The value will be the same as for importDirs in the import monitor's property file.

ftpExchangeDir Remote FTP exchange directory 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 exchange directory as a signal for the import monitor that the package is exported successfully and that the import can be started.

ftpJobNum Number of parallel FTP jobs; the default is 1.

Any positive number; 0 for an unlimited number of jobs. The value can be changed dynamically at runtime.

Export Socket Host

Option Description Comment

socket Socket operating mode R3load will not write dump files to the file system but the export and import work through the socket connection.

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

2011-12-15 PUBLIC 99/140

Page 100: System Copy NW 7.3

Option Description Comment

host Remote import host Name or IP address of the import host.

port Host port number Must be the same as the port number on the import host. Any free port on the import host from 1024 to 65535.

NOTE

Socket options are available for non-Unicode systems only.

FTP Copy Options

Option Description Command

ftpCopy 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 will be transferred from the source to the target host using FTP.

exportDirs List of export directories Separator on Windows: “;”Separator on UNIX: “:”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>.

ftpHost Remote FTP host Name or IP address of the import server

ftpUser 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).

ftpPassword Password of the remote FTP user

CAUTION

Security risk

ftpExportDirs List of remote FTP directories for export dump

Both “;” and “:” separators are valid. This is the directory on the target host to which the dump will be transferred. The value will be the same as for importDirs in the import monitor's property file.

Any other option is ignored by the export monitor.

Mandatory Options for 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:

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

100/140 PUBLIC 2011-12-15

Page 101: System Copy NW 7.3

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

Import Options

Option Description Comment

installDir Installation directory The installation directory is the directory in which the installation tools (SAPinst, R3SETUP) are started.When you run the Migration Monitor without using the installation tools, the installation directory is the directory where the R3load TSK and log files are created.

importDirs List of import directories Separator on Windows: “;”Separator on UNIX: “:”The importDirs parameter points to the directory where the R3load dump files are written. In the importDirs directory, the subdirectories DATA, DB, and DB/<TARGET_DBTYPE> (for example, DB/ORA) must exist.

orderBy Package order This option is used only if the import monitor works without the export monitor in standalone mode, that is, all export 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 ■ path of the file that contains package namesIf the option is omitted then package order is not defined.

ddlFile DDL control file Path or file name of DDL control fileThe default is DDL<DBTYPE>.TPL. If the file name is used without path, then the DDL control file from the export DB subdirectory is used.

ddlMap DDL mapping file File with mapping between DDL files and package names

r3loadExe Path of the R3load executable

Optional; default is R3load.If only the name of the R3load executable is available, then JVM looks for the R3load executable using OS-specific process 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, it must be set to yes. If the R3load task files *.TSK already exist, the monitor will not overwrite them.

extFiles yes to include EXT files; no to skip them

Add EXT file entries to cmd files.

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

2011-12-15 PUBLIC 101/140

Page 102: System Copy NW 7.3

Option Description CommentIf the EXT files cannot be found in the DB/<TARGET_DBTYPE> import dump subdirectory, the package processing is aborted.

dbCodepage Database code page for the target database

See SAP Note 552464. Possible values: 4102, 4103, 1100

migrationKey Migration key non

omit 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 options without blank (for example,-o TV).

taskArgs Additional R3load arguments for the TASK phase

Appended to the R3load command line.Options already set by the monitor:-ctf; -l; -o (if the omit argument is specified).

loadArgs Additional R3load arguments for the LOAD phase

Appended to the R3load command line.Options 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 Number of parallel import jobs; the default is 1.

Any positive number; 0 for an unlimited number of jobs.The value can be changed dynamically at runtime.

Import Exchange Options

Option Description Comment

exchangeDir Exchange directory 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 CDs 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 example, from a previous export run), remove this file.

Import Socket Options

Option Description Command

socket Socket operating mode non

port Server port number Any free port from 1024 to 65535.

Any other option is ignored by the import monitor.

Mandatory Options for Import Monitor

■ Server mode (default):

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

102/140 PUBLIC 2011-12-15

Page 103: System Copy NW 7.3

installDir, importDirs, tskFiles, extFiles,

one of the options exchangeDir or socket (and their related parameters)

■ Standalone mode:

installDir, importDirs, tskFiles, extFiles

■ Only valid for: IBM i5/OS |

IBM i-specific:

loadArgs= -nojournal

End of: IBM i5/OS |

NOTE

The value of the dbType option is determined automatically in the shell script or batch files from

the dbms_type environment variable.

8.1.2 Assigning DDL Files to Packages

ProcedureIt 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 Migration Monitor's properties file. 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 Additional Information

8.1 R3load Procedures Using the Migration Monitor

2011-12-15 PUBLIC 103/140

Page 104: System Copy NW 7.3

8.1.3 Defining Groups of Packages

The “package group” feature is an enhancement to defining a package order. By defining groups, you

can 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 Migration Monitor's properties file.

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.4 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 will automatically be 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

■ MS SQL

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

104/140 PUBLIC 2011-12-15

Page 105: System Copy NW 7.3

You can ensure this by using the Defining Groups of Packages [page 104] feature.

EXAMPLE

Target database does not support parallel data import

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.

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 will be 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.

Restart for all other database platforms:

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

2011-12-15 PUBLIC 105/140

Page 106: System Copy NW 7.3

1. Eliminate 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” (see Restarting R3load Processes [page 39]).

5. Restart the import.

8.1.5 Starting the Migration Monitor

The Migration Monitor has to be started on the source database host (export monitor) and on the

target database host (import monitor).

You can specify options in the command line or in the export or import property files (see

Configuration [page 96]). 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:

Directory Description

<export dump dir>/DATA Contains the STR files generated by R3ldctl

<export dump dir>/DB Contains the DDL<DBTYPE>.TPL files generated by R3ldctl

<export dump dir>/DB/<DBTYPE> 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 using one of the following ways:

■ Only valid for: UNIX |

UNIX shell scripts

export_monitor.sh / import_monitor.shEnd of: UNIX |

■ Only valid for: Windows |

Windows batch files

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

106/140 PUBLIC 2011-12-15

Page 107: System Copy NW 7.3

export_monitor.bat / import_monitor.batEnd of: Windows |

■ Only valid for: IBM i5/OS |

IBM i-specific

1. Run the command call qp2term.

2. export_monitor.sh / import_monitor.sh

3. Set the JAVA_HOME environment as follows:

export JAVA_HOME=/QIBM/ProdData/Java400/jdk14

4. Check that the environment variable PASE_THREAD_ATTACH is set to “Y”:

WRKENVVAR PASE_THREAD_ATTACH='Y'

End of: IBM i5/OS |

■ Automatically as part of the SAPinst export and import procedure

■ Manually within the SAPinst system copy tool:

1. On the Parameter Mode Default Settings SAPinst screen, choose Custom.

2. On the SAP System Export for Target System screen, select Start Migration Monitor Manually.

3. SAPinst will stop and ask you to start the Migration Monitor manually and to continue

with SAPinst as soon as the Migration Monitor finished successfully.

NOTE

If you use FTP access and security is required, start the Migration Monitor in secure mode to

prevent seeing FTP password in the command line parameter string or in the property file

(for example, on UNIX: ./export_monitor_secure.sh –ftpPassword <password>).

For more information about FTP, see FTP Exchange Options and FTP Copy Options in Configuration

[page 96].

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

Only valid for: UNIX |

EXAMPLE

Command line:

./export_monitor.sh –ftp

./export_monitor.sh –ftpCopy

./export_monitor.sh –socket –host <import server> –port 5000

End of: UNIX |

Only valid for: Windows |

EXAMPLE

Command line for Windows cmd.exe:

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

2011-12-15 PUBLIC 107/140

Page 108: System Copy NW 7.3

export_monitor.bat –net

export_monitor.bat –socket

End of: Windows |

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

#

# List of export directories, separator on Windows ; on UNIX :

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

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

108/140 PUBLIC 2011-12-15

Page 109: System Copy NW 7.3

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:

# Import Monitor options

#

# Common options

#

# List of import directories, separator on Windows ; on UNIX :

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

impJobNum=3

#

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

2011-12-15 PUBLIC 109/140

Page 110: System Copy NW 7.3

# E-mail options

#

# SMTP server

mailServer=sap-ag.de

# "From" email address

[email protected]

# "To" email address

[email protected] [email protected]

Only valid for: Oracle |

Processing Steps of a System Copy (Oracle only)

With the settings in the property file listed in the examples above and an Oracle database as source and

target database, the following prerequisites must be fulfilled:

■ The following directories must exist on the export host (parameter: exportDirs):

● c:\temp\export_dump\ABAP\DATA

● c:\temp\export_dump\ABAP\DB

● c:\temp\export_dump\ABAP\DB\ORA

The c:\temp\export_dump\ABAP\DATA directory must contain the STR files generated by R3ldctl.

The c:\temp\export_dump\ABAP\DB directory must contain the DDL<DBTYPE>.TPL files generated

by R3ldctl.

The c:\temp\export_dump\ABAP\DB\ORA directory must contain the EXT files generated by

R3szchk.

■ The following directories must exist on the import host (parameter: importDirs):

● /install_dir/export_dump/ABAP/DATA

● /install_dir/export_dump/ABAP/DB

● /install_dir/export_dump/ABAP/DB/ORA

The /install_dir/export_dump/ABAP/DATA directory must contain the STR files generated by

R3ldctl.

The /install_dir/export_dump/ABAP/DB directory must contain the DDL<DBTYPE>.TPL files

generated by R3ldctl.

The /install_dir/export_dump/ABAP/DB/ORA directory must contain the EXT files generated by

R3szchk.

The following steps are performed during a system copy:

1. The export monitor writes the R3load dump files and the TOC files to the directory c:\temp

\export_dump\ABAP\DATA.

2. The R3load log files, cmd files, and TSK files (if required) are located in the directory c:

\<install_dir>\start (installDir parameter). The export itself is not done by the export

monitor, as the monitor is running in client mode (server parameter is not set).

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

110/140 PUBLIC 2011-12-15

Page 111: System Copy NW 7.3

3. When a package has been exported successfully, the export monitor transfers all files belonging to

that package (TOC, STR, EXT, 001, and so on) to the target host (ftpHost parameter) to the

corresponding subdirectories of the directory /<install_dir>/export_dump

(ftpExportDirsparameter) as user <sapsid>adm (ftpUser parameter) with password

(ftpPassword parameter).

4. When the package files have been completely transferred to the server, the export monitor writes

a <package>.SGN signal file to the /<install_dir>/exchange directory (ftpExchangeDir

parameter) to notify the import monitor that it can start importing this package.

5. The import monitor starts to import a package as soon as the <package>.SGN file is found in the /

install_dir/exchange (exchangeDir parameter) directory.

6. The R3load log files, cmd files, and TSK files (if required) will be located in the directory /

<install_dir>/start (installDir parameter).

7. The DDLORA.TPL file must be copied to the /install_dir/start directory (installDir parameter)

before you start the import monitor.End of: Oracle |

8.1.6 Output Files

Export

■ export_monitor.log

■ export_state.properties

■ ExportMonitor.console.log

Import

■ import_monitor.log

■ import_state.properties

■ ImportMonitor.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:

0 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 may 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=++.

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

2011-12-15 PUBLIC 111/140

Page 112: System Copy NW 7.3

The format of state lines is <PACKAGE>=<STATE>. Possible values for state are listed in the following

table:

0 Package export not yet started.

? Package export in progress.

- Package export finished with errors.

+0 Package export finished successfully; package transfer not yet started.

+? Package transfer in progress.

+- Package transfer finished with errors.

++ Package transfer finished successfully.

8.1.7 Restarting R3load Processes

The state files export_state.properties and import_state.properties (see Output Files [page 111])

allow package states to be manually updated to restart failed R3load processes.

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.

Procedure

■ To restart package processing, set the package state from “–” to “0”.

■ 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.)

■ If the package is currently being processed (the package state is “?”), then any manual modifications

of the package state are ignored.

If you restart the Migration Monitor itself, the tool automatically recognizes which R3load packages

have not been finished successfully and starts R3load processes to complete the missing packages. It is

not necessary to modify the state file.

8.1.8 Installing the Target System Using the Migration Monitor

Prerequisites

Make sure there is enough free space on the target system for the database load. To find out the size of

the export and the sizes of the tablespaces or dbspaces that are created, look at the file DBSIZE.XML

located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE> (Windows) or <EXPDIR>/DB/

<DATABASE> (UNIX).

8 Additional Information

8.1 R3load Procedures Using the Migration Monitor

112/140 PUBLIC 2011-12-15

Page 113: System Copy NW 7.3

Procedure

1. If you want to start the installation of the target host using the Migration Monitor, make sure that

at least the dump directory with the following files is accessible on the target host and that it

contains the correct data before you start SAPinst:

■ <dump dir>/LABEL.ASC

■ <dump dir>/DB/<DBTYPE>/DBSIZE.XML

■ <dump dir>/DB/DDLORA.TPL

If the dump directory is not shared on the target host, copy the files from the source system to the

target system as soon as they have been created on the source host using the (export) Migration

Monitor's FTP copy options.

2. Start SAPinst as described in the installation documentation for your SAP component.

3. To install the target system, follow the instructions in the SAPinst input dialogs and enter the

required parameters as far as the ABAP System > Database screen. On this screen, choose Standard

System Copy/Migration (R3load-Based).

4. Select the Use Migration Monitor option.

NOTE

If you need more information about input parameters, position the cursor on the field of the

respective parameter and press F1 .

5. When SAPinst displays the CD browser window and asks for the Export Migration CD, enter the path

to the export directory <EXPDIR>.

6. Continue as described in the installation documentation for your SAP component until a dialog

box appears that states:

If the export has been started on the source system and the export monitor is

running, you can now start the data load by starting the import monitor.

7. Check that the prerequisites in the dialog box are fulfilled by your system. If so, start the Migration

Monitor.

8. Complete the installation as described in the installation documentation for your SAP solution.

CAUTION

If you have to restart the import after an error, just restart SAPinst. The import is continued

with the table that was not imported successfully.

8.2 Additional Information About SAPinst

The following sections provide additional information about SAPinst:

■ Useful Information About SAPinst [page 114]

■ Interrupted Installation with SAPinst [page 118]

■ Performing a Remote Installation with SAPinst [page 121]

■ Starting SAPinst GUI Separately [page 124].

8 Additional Information

8.2 Additional Information About SAPinst

2011-12-15 PUBLIC 113/140

Page 114: System Copy NW 7.3

■ Running SAPinst in Accessibility Mode [page 128]

■ Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle;SAP HANA DB |

Entries in the Services File Created by SAPinst [page 130]End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle;SAP HANA DB |

■ Troubleshooting with SAPinst [page 131]

■ Only valid for: IBM i5/OS | IBM DB2 for i5/OS |

Troubleshooting during the Database Load [page 132]End of: IBM i5/OS | IBM DB2 for i5/OS |

8.2.1 Useful Information About SAPinst

■ When you start SAPinst, SAPinst GUI, and the GUI server are also started. SAPinst GUI connects

using a secure SSL connection to the GUI server and the GUI server connects to SAPinst.

Only valid for: UNIX |

■ SAPinst normally creates the directory sapinst_instdir directly below the temporary directory.

SAPinst finds the temporary directory by checking the value of the environment variables TEMP,

TMP, or TMPDIR. If no value is set for these variables, SAPinst uses /tmp as default directory.

■ The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. These

executables are deleted again after SAPinst has stopped running. If required, you can terminate

SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C.End of: UNIX |

Only valid for: Windows |

■ SAPinst normally creates the installation directory sapinst_instdir, where it keeps its log files,

and which is located directly in the Program Files directory. If SAPinst is not able to create

sapinst_instdir directly below the Program Files directory, SAPinst tries to create

sapinst_instdir in the directory defined by the environment variable TEMP.

■ SAPinst creates a subdirectory for each installation option, called <sapinst_instdir>

\<installation_option>, which is located in %ProgramFiles%.

■ The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP, TMP,

TMPDIR, or SystemRoot). These executables are deleted after SAPinst 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 SAPinst Self-Extractor log file dev_selfex.out, which

might be useful if an error occurs.

If you want to terminate SAPinst and the SAPinst Self-Extractor, do one of the following:

● Right-click the icon for the SAPinst output window located in the Windows tray and choose

Exit.

8 Additional Information

8.2 Additional Information About SAPinst

114/140 PUBLIC 2011-12-15

Page 115: System Copy NW 7.3

● Click the icon for the SAPinst output window located in the Windows tray and choose File

Exit .End of: Windows |

CAUTION

■ If SAPinst cannot find a temporary directory, the installation terminates with the error

FCO-00058.

■ I you want to use a different installation directory than the default, make sure that you create

it locally. Otherwise, you might experience problems when starting the SAP Java tools.

Only valid for: UNIX |

■ Before starting the export, make sure that you have at least the same amount of disk space available

in /sapmnt/<SAPSID>/<InstanceName>/SMD/program as is used in /sapmnt/<SAPSID>/

<InstanceName>/SMD/root/origin.

During the export, some archives are written to the program subdirectories and SAPinst 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 SAPinst GUI is displayed.

■ Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime

Environment (JRE).

■ Only valid for: AIX |

If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE for AIX

64-bit.End of: AIX |

End of: UNIX |

Only valid for: Windows |

■ Before starting the export steps on the central instance of the source system, make sure that you

have at least the same amount of disk space available in \\SAPLOC\<SAPSID>\<InstanceName>\SMD

\program as is used in \\SAPLOC\<SAPSID>\<InstanceName>\SMD\root\origin. During the export

some archives are written to the program subdirectories and SAPinst aborts if there is not enough

space.End of: Windows |

Only valid for: IBM i5/OS |

■ Before you start the export of the existing SAP System, you have to download the current version

of R3szchk at http://service.sap.com/patches and copy it to directory /usr/sap/<>/SYS/exe/

run/.End of: IBM i5/OS |

NOTE

For a list of all available SAPinst properties, enter the following command: sapinst —p.

8 Additional Information

8.2 Additional Information About SAPinst

2011-12-15 PUBLIC 115/140

Page 116: System Copy NW 7.3

■ If you use virtual host names for the primary application server or the database instance both (for

example, in a high availability environment), start the export with the property

SAPINST_USE_HOSTNAME=<virtual host>.

Only valid for: Windows |

■ During the installation, the default ports 21200, 21212, and 4239 are used for communication

between SAPinst, GUI server, SAPinst GUI, and HTTP server, as follows:

● SAPinst uses port 21200 to communicate with the GUI server.

● The GUI server uses port 21212 to communicate with SAPinst GUI.

● 4239 is the port of the HTTP server, which is part of the GUI server.

If these ports are already in use, SAPinst automatically searches for free port numbers. If the search

fails, you see an error message and SAPinst exits.

In this case or if you want SAPinst to use specific ports, open a command prompt and change to

the required directory as follows:

cd /d <drive>:\DATA_UNITS\IM_WINDOWS_<platform>.

Execute sapinst.exe with the following commands:

● SAPINST_DIALOG_PORT=<port_number_sapinst_to_gui_server>

● GUISERVER_DIALOG_PORT=<port_number_gui_server_to_sapinst_gui>

● GUISERVER_HTTP_PORT=<port_number_http_server>

■ To see a list of all available SAPinst properties, go to the directory %TEMP%

\sapinst_exe.xxxxxx.xxxx after you have started SAPinst, and enter the following

command:sapinst —p.End of: Windows |

Only valid for: UNIX |

■ During the installation, the default ports 21200, 21212, and 4239 are used for communication

between SAPinst, GUI server, SAPinst GUI, and HTTP server, as follows:

● SAPinst uses port 21200 to communicate with the GUI server.

● The GUI server uses port 21212 to communicate with SAPinst GUI.

● 4239 is the port of the HTTP server, which is part of the GUI server.

If these ports are already in use, SAPinst automatically searches for free port numbers. If the search

fails, you see an error message and SAPinst exits.

In this case or if you want SAPinst to use specific ports, you can assign them by executing the sapinst

executable with the following parameters:

● SAPINST_DIALOG_PORT=<port_number_sapinst_to_gui_server>

● GUISERVER_DIALOG_PORT=<port_number_gui_server_to_sapinst_gui>

● GUISERVER_HTTP_PORT=<port_number_http_server>

■ To display a list of all available SAPinst properties, start SAPinst as described above with the option

-p:

8 Additional Information

8.2 Additional Information About SAPinst

116/140 PUBLIC 2011-12-15

Page 117: System Copy NW 7.3

./sapinst -p.End of: UNIX |

NOTE

For more information about input parameters in SAPinst, position the cursor on the parameter

field and choose F1 .

Troubleshooting

CAUTION

If an export process aborts due to a hardware failure (for example, file system full), you have to

repeat the export of the complete package. Remove the dump files <package>.<nnn>, the TOC

file <package>.TOC, the log file <package>.log and make sure that all tables in the TSK file

<package>.*TSK* have the status flag 'xeq' or 'err' set.

■ If there is not enough disk space in the export directory, the R3load database export fails. You can

then find error messages in the log files SAP*.log.

You can subsequently move the dump files that have been created from the file system in which

the export directory is located to a different file system during the export. Currently it is not possible

to automatically distribute the export over different file systems.

■ If an error occurs during the dialog phase, SAPinst:

● Stops the export.

● Displays a dialog that informs you about the error.

You can now directly view the log file by choosing View Logs.

Finally you must abort the export with OK and try to solve the problem.

■ If an error occurs during the processing phase, SAPinst:

● Stops the export.

● Displays a dialog that informs you about the error.

You can now:

● Directly view the log file by choosing View Logs.

● Try to solve the problem.

● Continue the export by choosing Retry.

● Abort the export by choosing OK.

■ System Copy - export on UNIX (especially for upgraded systems)

Symptom:

Processes started as <sapsid>adm or ora<sid> OS users cannot create or open files in the installation

directory.

Reason:

Only members of sapinst UNIX group can access the installation directory.

This group is created by SAPinst as of SAP NetWeaver 7.1.

8 Additional Information

8.2 Additional Information About SAPinst

2011-12-15 PUBLIC 117/140

Page 118: System Copy NW 7.3

Solution:

Associate <sapsid>adm and ora<sid> OS users with sapinst group manually if this association is

missing.

Verify /etc/group file and check if sapinst group exists and OS users are members of this group.

If sapinst group does not exist yet, start SAPinst. SAPinst creates this group during startup before

product catalog list is displayed.

Edit /etc/group file and associate OS users with sapinst group.

Continue with the export.

For more information, see Interrupted Installation with SAPinst [page 118].

8.2.2 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:

■ An error occurred during the Define Parameters or Execute phase:

SAPinst 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 SAPinst menu.

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.

The following table describes the options in the dialog box:

Option Definition

Retry SAPinst retries the installation from the point of failure without repeating any of the previous steps.This is possible because SAPinst 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, SAPinst displays the same dialog box again.

Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and the GUI server.SAPinst 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 SAPinst continues the installation from the current point.

View Log Access installation log files.

8 Additional Information

8.2 Additional Information About SAPinst

118/140 PUBLIC 2011-12-15

Page 119: System Copy NW 7.3

Procedure

This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to

continue an interrupted installation after an error situation.

1. Only valid for: Windows |

Log on to your remote host as a user who is a member of the local administrators group.End of: Windows |

2. Only valid for: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

Log on to your local UNIX host as user root.

CAUTION

Make sure that the root user has not set any environment variables for a different SAP system

or database.

End of: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

3. Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

Log on to your local IBM i host as your installation user with similar authorization rights as

QSECOFR. For more information about how to create the installation user SAPIUSR, see the section

Preparing an IBM i User Profile [page 36].End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

4. Only valid for: Windows |

Make available the installation master media.End of: Windows |

5. Only valid for: UNIX |

Make the medium for the installation master (folder <Product>_IM_<OS>_<DB>) available on the

installation host.

For more information, see Preparing the Installation Media [page 18].

Only valid for: UNIX |

RECOMMENDATION

Make installation media locally available. For example, if you use Network File System (NFS),

reading from media mounted with NFS might fail.

End of: UNIX |

Only valid for: Solaris |

NOTE

If you mount installation media, make sure that you do this with option nomaplcase.

End of: Solaris |

End of: UNIX |

6. Only valid for: IBM i5/OS |

Make available the installation master media.

NOTE

Make sure that the media is available locally. We do not recommend using Network File

System (NFS).

End of: IBM i5/OS |

8 Additional Information

8.2 Additional Information About SAPinst

2011-12-15 PUBLIC 119/140

Page 120: System Copy NW 7.3

7. Only valid for: Windows | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

Restart SAPinst by double-clicking sapinst.exe. You can also start SAPinst by entering the

following commands at the Windows command prompt:

cd /d <media_drive>:\IM_WINDOWS<platform>

sapinst.exe

End of: Windows | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

8. Only valid for: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

Change to the directory <product>_IM_<your OS>_<your DB> and start the sapinst executable

with the following command: ./sapinstEnd of: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

9. Only valid for: IBM i5/OS | IBM DB2 for i5/OS;No Database |

Enter the following commands:

CD DIR('<installation media>/DATA_UNITS/<product>_IM_OS400_PPC64_DB4')

CALL PGM(QP2TERM) PARM('./sapinst')

End of: IBM i5/OS | IBM DB2 for i5/OS;No Database |

10. From the tree structure in the Welcome screen, select the installation option that you want to

continue and choose Next.

The What do you want to do? screen appears.

11. In the What do you want to do? screen, decide between the following alternatives and continue with

Next:

Alternative Behavior

Run a new option SAPinst does not continue the interrupted installation option. Instead, it moves the content of the old installation directory and all installation-specific files to a backup directory. Afterwards, you can no longer continue the old installation option.

NOTE

All action taken by the installation before you stopped it (like creating directories, or users) will not be revoked.

For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds>.

EXAMPLE

log_01_Oct_2008_13_47_56

CAUTION

SAPinst 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.

Continue with the old option SAPinst continues the interrupted installation from the point of failure.

8 Additional Information

8.2 Additional Information About SAPinst

120/140 PUBLIC 2011-12-15

Page 121: System Copy NW 7.3

8.2.3 Performing a Remote Installation with SAPinst

You use this procedure to install your SAP system on a remote host. In this case, SAPinst and the GUI

server run on the remote host, and SAPinst GUI runs on the local host. The local host is the host from

which you control the installation with SAPinst GUI.

Only valid for: IBM i5/OS;UNIX |

If your security policy requires that the person performing the installation by running the SAPinst GUI

on the local host is not allowed to know root credentials 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.End of: IBM i5/OS;UNIX |

Only valid for: Windows |

If your security policy requires that the person performing the installation by running the SAPinst GUI

on the local host is not allowed to know administrator credentials 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 sapinst.exe from the command line.End of: Windows |

Only valid for: IBM i5/OS;UNIX |

Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote

access to SAPinst GUI on Windows workstations. For more information, see SAP Note 1170809.End of: IBM i5/OS;UNIX |

Only valid for: UNIX;Windows | Linux;Windows |

You can run the SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host.

For more information, see Starting SAPinst GUI Separately [page 124].End of: UNIX;Windows | Linux;Windows |

Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

CAUTION

In this section, “local host” refers to the Windows installation host, and“ remote host” refers to

the IBM i host where the SAP system is installed.

End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

Prerequisites

■ Both computers are in the same network and can ping each other.

To test this:

Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |

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>.End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |

8 Additional Information

8.2 Additional Information About SAPinst

2011-12-15 PUBLIC 121/140

Page 122: System Copy NW 7.3

Only valid for: IBM DB2 for i5/OS |

1. Log on to your remote host (IBM i) and enter the command PING RMTSYS('<local

host>').

2. Log on to the local host (Windows PC) and enter the command ping <remote host>.End of: IBM DB2 for i5/OS |

■ 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.

ProcedureOnly valid for: Windows |

1. Log on to your remote host as a user that is a member of the local administrators group.

2. Make the installation master media available on your remote host.

3. Open a command prompt and enter the following commands:

Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

cd \d <media drive>:\DATA_UNITS\<product>_IM_WINDOWS_<platform>_<DB>

End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

Run sapinst.exe -nogui

NOTE

If you need to specify another operating system user for authentication purposes, enter the

following command:

sapinst.exe -nogui SAPINST_REMOTE_ACCESS_USER=<specified OS user>

4. Execute the following command: sapinst.exe -nogui

SAPinst now starts and waits for the connection to the SAPinst 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

5. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 124].End of: Windows |

Only valid for: UNIX |

1. Log on to your remote host as user root.

CAUTION

Make sure that the root user has not set any environment variables for a different SAP system

or database.

2. Make the medium for the installation master (folder <Product>_IM_<OS>_<DB>) available on the

installation host.

For more information, see Preparing the Installation Media [page 18].

8 Additional Information

8.2 Additional Information About SAPinst

122/140 PUBLIC 2011-12-15

Page 123: System Copy NW 7.3

Only valid for: UNIX |

RECOMMENDATION

Make installation media locally available. For example, reading from media mounted with

Network File System (NFS) might fail.

End of: UNIX |

Only valid for: Solaris |

NOTE

If you mount installation media, make sure that you do this with option nomaplcase.

End of: Solaris |

3. Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

Change to the directory <product>_IM_<your OS>_<your DB> and start the sapinst executable

with the following command: ./sapinst -noguiEnd of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

NOTE

If you need to specify another operating system user for authentication purposes, enter the

following command:

./sapinst -nogui SAPINST_REMOTE_ACCESS_USER=<specified OS user>

SAPinst now starts and waits for the connection to the SAPinst 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

4. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 124].End of: UNIX |

Only valid for: IBM i5/OS |

1. Log on to your host as the installation user with similar authorization rights to QSECOFR. For more

information, see Preparing an IBM i User Profile [page 36].

CAUTION

Make sure that the installation user has not set any environment variables for a different SAP

system or database.

2. Make available the installation master media.

3. Start SAPinst from the installation master media by entering the following commands:

■ CD DIR ('<installation media>/DATA_UNITS/<product>_IM_OS400_PPC64_DB4')

■ CALL PGM(QP2TERM) PARM('./sapinst' '-nogui')

NOTE

If you need to specify another operating system user for authentication purposes, this

command is as follows:

CALL PGM(QP2TERM) PARM('./sapinst' '-nogui'

'SAPINST_REMOTE_ACCESS_USER=<specified OS user>')

8 Additional Information

8.2 Additional Information About SAPinst

2011-12-15 PUBLIC 123/140

Page 124: System Copy NW 7.3

SAPinst now starts and waits for the connection to the SAPinst 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

Only valid for: HA (UNIX) |

NOTE

If you are installing a high-availability system and you have not already set the environment

parameter SAPINST_USE_HOSTNAME to specify the virtual host name, you can start SAPinst as

follows:

CALL PGM(QP2TERM) PARM('./sapinst' '-nogui' 'SAPINST_USE_HOSTNAME=<virtual

host name>')

End of: HA (UNIX) |

4. There is no GUI on IBM i, so you do not see an SAPinst Welcome screen. As a default, you must start

the SAPinst GUI separately on a Windows 32-bit platform. For more information, see Starting SAPinst

GUI Separately [page 124].End of: IBM i5/OS |

8.2.4 Starting SAPinst GUI Separately

You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI separately

in the following cases:

■ Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

You are running IBM i and did not set a DISPLAY environment variable.End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

■ You closed SAPinst GUI using File Exit from the SAPinst menu while SAPinst is still running.

■ You want to perform a remote installation, where the SAPinst GUI runs on a different host from

SAPinst. For more information, see Performing a Remote Installation with SAPinst [page 121].

■ Only valid for: IBM i5/OS;UNIX |

You want to run SAPinst in accessibility mode. In this case, you have to start the SAPinst GUI

separately on a Windows host as described below with the additional command line parameter –

accessible.

For more information, see Running SAPinst in Accessibility Mode [page 128].End of: IBM i5/OS;UNIX |

Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

CAUTION

This is the default on IBM i. Since there is no GUI on IBM i, you must start the SAPinst GUI

separately.

End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

8 Additional Information

8.2 Additional Information About SAPinst

124/140 PUBLIC 2011-12-15

Page 125: System Copy NW 7.3

Prerequisites

The host on which you want to start the SAPinst GUI meets the prerequisites for starting SAPinst as

described in Exporting the Source System Using SAPinst [page 29]

Procedure

Starting SAPinst GUI on Windows

1. Make the medium for the installation master (folder <Product>_IM_<OS>_<DB>) available on the

host on which you want to start the SAPinst GUI.

For more information, see Preparing the Installation Media [page 18].

2. Change to the directory of the sapinstgui executable:

Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

<product>_IM_<your OS>_<your DB>

End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

NOTE

If you want to start SAPinst GUI on a Windows 32-bit operating system, change to the

following directory:

<product>_IM_SAPINSTGUI_WINDOWS_I386

End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

Only valid for: IBM DB2 for i5/OS |

NOTE

If you start the SAPinst GUI executable on Windows 7 or Windows 2008, you must use the

option Run as administrator. Typically, you first start a command prompt using Run as

administrator. Then in this command prompt, you enter the SAPinst GUI command.

End of: IBM DB2 for i5/OS |

Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |

NOTE

If you want to start SAPinst GUI on a Windows 32-bit operating system, you can use the

executable available in the IBM i media or change to the following directory:

DATA_UNITS\<product>\SAPINSTGUI_WINDOWS_I386

End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |

Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS;No Database |

NOTE

If you have a share ROOTBIN on your IBM i and you have mapped this share to the drive X,

you can start the SAPinst GUI using your copied installation master media:

X:\tmp\<SID>\<installation media>\DATA_UNITS

\<product>_SAPINSTGUI_WINDOWS_I386

8 Additional Information

8.2 Additional Information About SAPinst

2011-12-15 PUBLIC 125/140

Page 126: System Copy NW 7.3

For more information, see Copying the media Manually Using the ROOTBIN Share [page 37].

End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS;No Database |

3. Start the SAPinst GUI from a command prompt by executing sapinstgui.exe with the relevant

command line parameters:

■ If you want to perform a remote installation, execute the following command:

sapinstgui.exe -host <remote_host> -port

<port_number_gui_server_to_gui_client>

– where <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).

■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, proceed

as follows:

● If you are performing a local installation with SAPinst and SAPinst GUI running on the

same host, execute the following command:

sapinstgui.exe -standalone -port <port_number_gui_server_to_gui_client>

– where <port_number_gui_server_to_gui_client> is the port the GUI server uses to

communicate with the GUI client (21212 by default).

● If you are performing a remote installation with SAPinst and SAPinst GUI running on

different hosts, execute the following command:

sapinstgui.exe -host <remote_host> -port

<port_number_gui_server_to_gui_client>

– where <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).

The SAPinst GUI starts and connects to SAPinst.

Starting SAPinst GUI on UNIX

1. Make the medium for the installation master (folder <Product>_IM_<OS>_<DB>) available on the

host on which you want to start the SAPinst GUI.

For more information, see Preparing the Installation Media [page 18].

Only valid for: UNIX |

RECOMMENDATION

Make installation media locally available. For example, if you use Network File System (NFS),

reading from media mounted with NFS might fail.

End of: UNIX |

Only valid for: Solaris |

NOTE

If you mount installation media, make sure that you do this with option nomaplcase.

End of: Solaris |

8 Additional Information

8.2 Additional Information About SAPinst

126/140 PUBLIC 2011-12-15

Page 127: System Copy NW 7.3

2. Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;Oracle;SAP HANA DB |

Change to the directory <product>_IM_<your OS>_<your DB> and start the sapinstgui executable

with the following command: ./sapinstguiEnd of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;Oracle;SAP HANA DB |

■ If you want to start the SAPinst GUI on a Linux 32-bit platform, change to the directory

<product>_IM_SAPINSTGUI_LINUX_I386.

■ If you want to perform a remote installation, execute the following command:

./sapinstgui -host <remote_host> -port <port_number_gui_server_to_gui_client>

– where <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).

■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, proceed

as follows:

● If you are performing a local installation with SAPinst and SAPinst GUI running on the

same host, execute the following command:

./sapinstgui -port <port_number_gui_server_to_gui>

– where <port_number_gui_server_to_gui> is the port the GUI server uses to

communicate with the GUI client (21212 by default).

● If you are performing a remote installation with SAPinst and SAPinst GUI running on

different hosts, execute the following command:

./sapinstgui -host <remote_host> -port <port_number_gui_server_to_gui>

– where <remote_host> is the name of the remote host, and

<port_number_gui_server_to_gui> is the port the GUI server uses to communicate with

the GUI client (21212 by default).

The SAPinst GUI starts and connects to SAPinst.

3. Only valid for: z/OS |

Start the SAPinst GUI in one of the following ways:

■ If SAPinst GUI runs on the same host as SAPinst and the SAPinst GUI, enter the following

command without any additional parameters:

./startInstGui.sh

By default SAPinst GUI uses the local host.

■ If SAPinst runs on a different host from the SAPinst GUI (remote installation), enter the

following command with additional parameters:

./startInstGui.sh -host <host_name>

<host_name> is the host name of the installation host

NOTE

● If you enter the command without additional parameters, SAPinst GUI uses the

local host as default. SAPinst GUI starts and tries to connect to SAPinst. Since SAPinst

8 Additional Information

8.2 Additional Information About SAPinst

2011-12-15 PUBLIC 127/140

Page 128: System Copy NW 7.3

is running on another host, the SAPinst GUI cannot connect and the SAP Installation

GUI Connection dialog appears.

In this case, enter the name of the host on which SAPinst is running and choose Log

on.

The first dialog of the installation appears and you can perform the remote

installation from your local host.

● For a list of options to start SAPinst GUI, change to the same directory as your SAPinst

executable and enter the command:

./startInstGui.sh -h

End of: z/OS |

8.2.5 Running SAPinst in Accessibility Mode

You can also run SAPinst in accessibility mode. The following features are available:

■ Keyboard access:

This feature is available for all operating systems.

■ High-contrast color:

Only valid for: Windows |

This feature is derived from the Windows display properties. You can use it either for a local

installation or for a remote installation.End of: Windows |

Only valid for: IBM i5/OS;UNIX |

This feature is derived from the Windows display properties. Therefore, to enable this feature, you

must perform a remote installation with the SAPinst GUI running on a Windows host.End of: IBM i5/OS;UNIX |

■ Custom font setting:

Only valid for: Windows |

This feature is derived from the Windows display properties. You can use it either for a local

installation or for a remote installation.End of: Windows |

Only valid for: IBM i5/OS;UNIX |

This feature is derived from the Windows display properties. Therefore, to enable this feature, you

must perform a remote installation with the SAPinst GUI running on a Windows host.End of: IBM i5/OS;UNIX |

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 SAPinst or the SAPinst GUI.

8 Additional Information

8.2 Additional Information About SAPinst

128/140 PUBLIC 2011-12-15

Page 129: System Copy NW 7.3

NOTE

The following procedure applies for Windows Server 2008 and might be different when using

another Windows operating system.

1. Right click on your Windows desktop and choose Personalize.

2. Choose Adjust font size (DPI) and choose Larger scale (120 DPI).

To define other font size schemes, choose Custom DPI.

3. In the right-hand pane, select Window Color and Appearance.

Select a color scheme from the Color scheme dropdown box.

To define your own color schemes, choose Advanced.

Running SAPinst in Accessibility Mode

Only valid for: Windows |

You can either perform a local installation, where SAPinst and SAPinst GUI are running on the same

host, or a remote installation, where SAPinst and SAPinst GUI are running on different hosts.

■ Local installation:

Start SAPinst as described in Running SAPinst on UNIX or Windows to Perform the Export [page 29] by

executing the following command:

sapinst.exe –accessible

■ Remote installation:

1. Start SAPinst on the remote host by executing the following command from the command

line as described in Performing a Remote Installation with SAPinst [page 121]:

sapinst.exe –nogui

2. Start SAPinst GUI on the local host by executing the following command from the command

line as described in Starting the SAPinst GUI Separately for a Remote Installation [page 124]:

sapinstgui.exe -accessible –host <remote_host> -port

<port_number_gui_server_to_gui_client>

End of: Windows |

Only valid for: IBM i5/OS;UNIX |

You perform a remote installation as follows:

1. Start SAPinst on the remote host by executing the following command from the command line

as described in Performing a Remote Installation with SAPinst [page 121]:

./sapinst –nogui

2. Start SAPinst GUI on a local Windows host by executing the following command from the

command line as described in Starting the SAPinst GUI Separately for a Remote Installation [page 124]:

sapinstgui.exe -accessible –host <remote_host> -port

<port_number_gui_server_to_gui_client>

End of: IBM i5/OS;UNIX |

8 Additional Information

8.2 Additional Information About SAPinst

2011-12-15 PUBLIC 129/140

Page 130: System Copy NW 7.3

8.2.6 Entries in the Services File Created by SAPinstOnly valid for: UNIX |

After the installation has completed, SAPinst has created the following entries in /etc/services:End of: UNIX |

Only valid for: Windows |

After the installation has finished successfully, SAPinst has created the following entries for port names

in <drive:>\WINDOWS\system32\drivers\etc\services:End of: Windows |

Only valid for: UNIX;Windows |

sapdp<nn> = 32<nn>/tcp

End of: UNIX;Windows |

Only valid for: UNIX;Windows |

sapdp<nn>s = 47<nn>/tcp

End of: UNIX;Windows |

Only valid for: UNIX;Windows |

sapgw<nn> = 33<nn>/tcp

End of: UNIX;Windows |

Only valid for: UNIX;Windows |

sapgw<nn>s = 48<nn>/tcp

End of: UNIX;Windows |

Only valid for: UNIX;Windows |

sapms<SAPSID> = 36<nn>/tcp (unless you specified another value during the installation)End of: UNIX;Windows |

Only valid for: IBM i5/OS |

After the installation has finished successfully, SAPinst has created the following entries in the service

table:End of: IBM i5/OS |

Only valid for: IBM i5/OS |

To review the entries, use the command WRKSRVTBLE.End of: IBM i5/OS |

Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

Service Table

Service Port Protocol

sapdp<nn> 32<nn> tcp

sapdp<nn>s 47<nn> tcp

sapgw<nn> 33<nn> tcp

sapgw<nn>s 48<nn> tcp

sapms<SAPSID> 36<nn>

(unless you specified another value during the installation)

tcp

End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

8 Additional Information

8.2 Additional Information About SAPinst

130/140 PUBLIC 2011-12-15

Page 131: System Copy NW 7.3

NOTE

■ <nn> is the instance number. There is a port created for every possible instance number,

regardless of which instance number you specified during the installation. For example, for

sapgw<nn> = 33<nn>/tcp the following range of entries is created:

sapgw00 = 3300/tcp

sapgw01 = 3301/tcp

sapgw02 = 3302/tcp

[...]

sapgw98 = 3398/tcp

sapgw99 = 3399/tcp

■ If there is more than one entry for the same port number, this is not an error.

8.2.7 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.

If an error occurs, SAPinst:

■ Stops the installation

■ Displays a dialog informing you about the error

Procedure

1. Check SAP Note 1548438 for known SAPinst issues.

2. To view the log file, choose View Logs.

3. If an error occurs during the dialog or processing phase, do one of the following:

■ Try to solve the problem.

■ Abort the installation with Exit.

For more information, see Interrupted Installation with SAPinst [page 118].

■ Continue the installation by choosing Retry.

4. Only valid for: Windows |

Check the log and trace files of the GUI server and SAPinst GUI in the directory %userprofile%

\.sdtgui\ for errors.End of: Windows |

Only valid for: IBM i5/OS;UNIX |

Check the log and trace files of the GUI server and SAPinst GUI in the directory

<user_home>/.sdtgui/ for errors.End of: IBM i5/OS;UNIX |

■ Only valid for: IBM i5/OS;UNIX |

If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current

<user_home> directory.End of: IBM i5/OS;UNIX |

8 Additional Information

8.2 Additional Information About SAPinst

2011-12-15 PUBLIC 131/140

Page 132: System Copy NW 7.3

■ Only valid for: Windows |

If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current %

userprofile% directory.End of: Windows |

■ If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI

as described in Starting SAPinst GUI Separately [page 124].

■ Only valid for: IBM i5/OS;UNIX |

If you use an X Server for Microsoft Windows or other remote desktop tools for the Remote

Access of SAPinst 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 Swing-based GUIs and also tell you

about further requirements and restrictions. See also SAP Note 1170809.End of: IBM i5/OS;UNIX |

■ Only valid for: Windows | HA (MSCS) |

If you experience network connection problems, check IPv4 Host name resolution as described

in SAP Note 1365796.End of: Windows | HA (MSCS) |

5. If you cannot resolve the problem, create a customer message using component BC-INS.

Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

8.2.8 Troubleshooting During the Database Load

The database load is divided into several sections, which are performed in parallel. Each section writes

a log file to your installation directory. The names of these files are as follows:

■ SAP0000.log

■ SAPUSER.log

■ SAPSSRC.log

■ SAPSSEXC.log

■ SAPSPROT.log

■ SAPSLOAD.log

■ SAPSLEXC.log

■ SAPSDIC.log

■ SAPSDOCU.log

■ SAPPOOL.log

■ SAPCLUST.log

■ SAPAPPL2.log

■ SAPAPPL1.log

■ SAPAPPL0.log

■ SAPVIEW.log

8 Additional Information

8.2 Additional Information About SAPinst

132/140 PUBLIC 2011-12-15

Page 133: System Copy NW 7.3

■ SAPDDIM.log

■ SAPDFACT.log

■ SAPDODS.log

Procedure

1. If errors occur during database load find out which load process failed by checking the log files.

You can do this by entering:

EDTF '/tmp/sapinst_instdir/<INSTDIR>/<log_file>.log'

EXAMPLE

EDTF '/tmp/sapinst_instdir/<INSTDIR>/SAPSDIC.log'

The log file contains additional information about the status of the job and the corresponding IBM

i job.

2. Scroll to the bottom of this file and check the error message.

The start of each import attempt is logged to this file and looks like this:

TS61CEO34/R3LOADDB4: START OF LOG: 20010926170456

TS61CEO34/R3LOADDB4: sccsid @(#) $Id:

//bas/620_COR/src/R3ld/R3load/R3ldmain.c#4 $ SAP

TS61CEO34/R3LOADDB4: version R6.10/V1.

TS61CEO34/R3LOADDB4 -i SAPSDIC.cmd -p SAPSDIC.log -nojournal

-datacodepage 1100 -dbcodepage 0120

...

No Journaling During the Database Load

You should keep in mind that the new tables are not journaled during the database load. Therefore,

you receive the following message:

SQL7905 Information 20 10/21/01 17:18:38 QSQCRTT QSYS 1013 QSQCRTT

Message . . . . : Table <table_name> in R3<SID>DATA created but could not be journaled.

You can ignore this message. Journaling is switched on later.End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

8 Additional Information

8.2 Additional Information About SAPinst

2011-12-15 PUBLIC 133/140

Page 134: System Copy NW 7.3

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

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

EXAMPLE Keys on the keyboard

134/140 PUBLIC 2011-12-15

Page 135: System Copy NW 7.3

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle and Java are registered trademarks of Oracle.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP companySybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Legal Software Terms

2011-12-15 PUBLIC 135/140

Page 136: System Copy NW 7.3

Terms for Included Open Source Software

This SAP software contains also the third party open source software products listed below. Note that for these third party products the following special terms and conditions shall apply.1. This software includes ANTLR, which is released under the following BSD license:

[The BSD License]Copyright (c) 2010 Terence ParrAll rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: ■ Redistributions of source code must retain the above copyright notice, this list of conditions and the following

disclaimer. ■ Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following

disclaimer in the documentation and/or other materials provided with the distribution. ■ Neither the name of the author nor the names of its contributors may be used to endorse or promote products

derived from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

2. SAP License Agreement for STLportSAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingDietmar-Hopp-Allee 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)1. Subject Matter of the Agreement

1. SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library (STLport) and its documentation without fee.

2. By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement.

3. The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions.

4. Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG

5. The Customer may distribute original or modified STLport sources, provided that: ■ The conditions indicated in the above permissions notice are met; ■ The following copyright notices are retained when present, and conditions provided in accompanying

permission notices are met:Copyright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company

136/140 PUBLIC 2011-12-15

Page 137: System Copy NW 7.3

makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications.

2. Support and MaintenanceSAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall be not included.All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract.

3. Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport is error-free, without material defects or suitable for a specific application under third-party rights. Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes.

4. Limited Liability1. Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this

(i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute.

2. If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances known to it at that point in time representing a typical transfer of the software.

3. In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a defect or lost profit.

4. SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5,000.

5. The Customer shall take adequate measures for the protection of data and programs, in particular by making backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing this obligation.

6. The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees or agents of SAP.

3. Adobe Document Services

2011-12-15 PUBLIC 137/140

Page 138: System Copy NW 7.3

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer, see SAP Note 854621.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

138/140 PUBLIC 2011-12-15

Page 139: System Copy NW 7.3
Page 140: System Copy NW 7.3

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2011 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.