system copy solman 7.0 ehp1 forsr1

System Copy GuideSystem Copy for SAP Solution Manager 7.0 Including SAP Enhancement Package 1 SR 1Using SAPinst

Target Audience ■ System administrators ■ Technology consultants

PUBLICDocument version: 1.2 – 2012-03-14

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.2 2012-03-14 IBM i-specific updates

1.1 2011-03-07 IBM i-specific updates

1.0 2011-02-18 Initial Version

2/148 PUBLIC 2012-03-14

http://service.sap.com/instguides


Table of Contents

Chapter 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based

on SAP NetWeaver 7.0 Including Enhancement Package 1 Support

Package 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

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

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

1.3 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.4 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.5 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.1 General Technical Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.2 Installing the Java Development Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 4 Database Independent System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.1 System Copy Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4.2 Generating DDL Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.3 Preparation for Table Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4.4 Preparing the Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

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

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

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

4.5.2.1 Preparing the Windows Host for the SAP System Installation . . . . . . . . . . . . . 42

4.5.2.2 Preparing a Windows User Account and IBM i User Profile . . . . . . . . . . . . . . . 43

4.5.2.3 Installing TMKSVR and Creating an Installation Share . . . . . . . . . . . . . . . . . . 44

4.5.2.4 Starting SAPinst on IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.5.3 Restarting R3load Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4.6 Setting Up the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

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

4.6.2 Installing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

2012-03-14 PUBLIC 3/148

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

5.1 Oracle-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

5.1.1 Generating the Control File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.1.2 Creating a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.1.2.1 Creating an Offline Backup Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

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

5.1.3 Preparing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.1.4 Restoring Database Files on the Target System Manually . . . . . . . . . . . . . . . . 70

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

5.2 SAP MaxDB-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

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

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

5.5 IBM DB2 for i Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

5.6 IBM DB2 for z/OS Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Chapter 6 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

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

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

6.2.1 Installing the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

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

6.2.3 Performing Follow-Up Activities for Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

6.2.3.1 General Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

6.2.3.1.1 Configuration Steps for the SAP Java Connector . . . . . . . . . . . . . . . . . . . . . . . 89

6.2.3.1.2 Generating Public-Key Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

6.2.3.2 Usage Type or Software Unit-Specific Follow-Up Activities . . . . . . . . . . . . . . . 90

6.2.3.2.1 Application Server Java (AS-Java) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

6.2.3.2.1.1 AS Java: SAP Knowledge Warehouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

6.2.3.2.2 EP Core (EPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

6.2.3.2.2.1 EPC: Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

6.2.3.2.3 Enterprise Portal (EP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

6.2.3.2.3.1 EP: Knowledge Management and Collaboration . . . . . . . . . . . . . . . . . . . . . . . 90

6.2.3.2.4 Business Intelligence Java Components (BI Java) . . . . . . . . . . . . . . . . . . . . . . . 94

6.2.3.2.4.1 Business Intelligence (BI Java) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

6.2.3.2.4.2 Basic Configuration for Usage Type BI Java . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

6.2.3.2.5 Process Integration (PI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

6.2.3.2.5.1 PI: System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

6.2.3.2.5.2 PI: Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

4/148 PUBLIC 2012-03-14

6.2.3.2.5.3 PI: Changes in the Exchange Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

6.2.3.2.5.4 PI: Refresh Caches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

6.2.3.2.5.5 PI: Switching Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

6.2.3.2.5.6 PI: Connection Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

6.2.3.2.6 Development Infrastructure (DI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

6.2.3.2.7 Mobile Infrastructure (MI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

6.2.3.2.7.1 MI: Clean Up the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

6.2.3.2.8 Self Services (XSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

6.2.3.2.8.1 Re-Creating the JCo Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

6.2.3.2.8.2 ERP-XSS: SAP WebDynpro Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

6.2.3.2.9 CRM Java Components (JCRM) / Extended E-Selling Components

(XECO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

6.2.3.2.9.1 Sub-Component Workforce Deployment AS/CS . . . . . . . . . . . . . . . . . . . . . . 106

6.2.3.2.10 MapBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

6.2.3.2.11 SRM Live Auction Cockpit (SRMLAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

6.2.3.2.11.1 SRM Live Auction Cockpit (SRMLAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

6.2.3.2.12 SCM Forecasting & Replenishment Processor (SCM FRP) . . . . . . . . . . . . . . . 108

6.2.4 Performing Jobhead Correction after Homogeneous System Copy . . . . . . . . 108

Chapter 7 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

7.1 R3load Procedures Using the Migration Monitor . . . . . . . . . . . . . . . . . . . . . . 111

7.1.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

7.1.2 Assigning DDL Files to Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

7.1.3 Defining Groups of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

7.1.4 Processing Split Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

7.1.5 Starting the Migration Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

7.1.6 Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

7.1.7 Installing the Target System Using the Migration Monitor . . . . . . . . . . . . . . 127

7.2 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

7.3 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

7.4 Performing a Remote Export Using SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . 132

7.4.1 Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . 132

7.4.2 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

7.5 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

2012-03-14 PUBLIC 5/148

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

1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 Including Enhancement Package 1 Support Package 1

As of SAP NetWeaver 7.0, you can copy ABAP systems, ABAP+Java systems and Java systems in one run,

using either database-specific methods or database-independent methods. This document explains how

to perform a system copy for SAP systems based on SAP NetWeaver 7.0 including Enhancement Package

1 Support Package 1 (SAP NetWeaver 7.0 EHP 1 SR 1).

1.1 Terminology

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

■ 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 (IBM i: source_<SID> and target_<SID>).

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

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

■ Database Copy

Database-dependent part of the system copy.

■ Placeholders

Placeholders such as <SAPSID> are used in commands. They are used in the same way as in the SAP

system installation documentation. You must replace them with the values valid for your site.


1.1 Terminology

2012-03-14 PUBLIC 7/148

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

<OS> Operating system name within a path

<DB> Database name within a path

<Technology> ABAP, Java, or ABAP+Java

1.2 Online Information from SAP

More information about system copying is available online as follows:

■ SAP System Copy & Migration page at http://sdn.sap.com/irj/sdn/systemcopy.

■ SAP OS/DB Migration page 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 Note 82478 SAP System OS/DB Migration

CAUTION

Only perform a system copy if you have experience in copying systems and thorough

knowledge of the operating system, the database, the ABAP Dictionary, and the Java

Dictionary. Only perform a heterogeneous system copy if you are a certified system support

consultant or a certified SAP Technical Consultant.

NOTE

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

application area BC-INS-MIG.

1.3 System Architecture

The Java system persists data in both the database and the file system, for example the Software Delivery

Manager (SDM) is persisted in the file system. Each server instance has a unique ID and is stored in the

database.


1.2 Online Information from SAP

8/148 PUBLIC 2012-03-14

http://sdn.sap.com/irj/sdn/systemcopy

http://service.sap.com/osdbmigration

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=82478&_NLANG=en&_NVERS=0

1.4 Restrictions

NOTE

Refer to SAP Note 1317500 for Java components based on SAP NetWeaver 7.0 EHP 1 SR 1 that have

been released already for system copy.

The target system installation consists of both the target database and target instance/application server

installations. For the scenarios below, the following holds:

■ Refreshing the database is not supported. Refreshing the database means that only the database is

loaded with the content of a database of a different system. Since no migration controller is invoked

in this scenario, this is not supported.

■ Copying only the database is not supported.

■ Copying only the central instance is not supported. The migration controller deletes all dialog

instances in the database, so the system is not complete any longer.

■ Reinstalling the central instance without the database is not supported. The migration controller

deletes all dialog instances in the database, so the system is not complete any longer.

■ Only valid for: IBM DB2 for Linux and UNIX and Windows |

The option Deferred Table Creation is not supported for load-based system copies for SAP systems

that are not based on SAP NetWeaver 7.0 EHP 1 SR 1.End of: IBM DB2 for Linux and UNIX and Windows |

1.5 Constraints

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

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

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

■ Only valid for: SAP Solution Manager |

As of Support Release 4, your SAP Solution Manager 4.0 system must be a dual stack system if you

want to perform a system copy. If required, install a Java Add-In to your existing ABAP system

before you start the export.End of: SAP Solution Manager |

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


1.4 Restrictions

2012-03-14 PUBLIC 9/148



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

■ For the development of Java applications, we strongly recommend that you follow the rules

mentioned below. Otherwise, we cannot guarantee that you can copy your Java engine later with

the SAP tools to change your underlying operating system and/or database system.

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

If you used data archiving in the source or target system, access to the created archive files from

the target system may not always be possible. For more information, see SAP Note 153433 and

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

Access to archived files from the target system without a dedicated archive migration project is

only supported in the following cases:

● Your system copy clones a source system for nonproductive purposes, for read-only access to

the previously archived data from the target system (no reloading), and you do not store

archive files using ArchiveLink/CMS.

You can either copy all archive files to file systems that are not shared between the source and

the target system, or you arrange network access for appropriate archive file sharing.

● The system copy is done to replace a productive system with a new productive system (for

example, hardware migration), assuming that the target system did not exist before and the

source system's operation is discontinued after the system copy.

You must not change the system ID during system copy, but arrange for file access and/or

ArchiveLink/CMS connectivity.

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

[email protected].

■ When you perform a system copy, all software units or usage types in the source system are copied

to the target system. This means that none of the usage types in the target system can be excluded

from the system copy, nor can you select usage types.

■ Dos and Don'ts for system copy:

● Do:

◆ Save configuration data and runtime data in the Java database only. If saving this data to

the file system level is unavoidable, you must use the Software Deployment Manager

(SDM) to save the data.

◆ Follow the Open SQL standard.

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

● Don't:


1.5 Constraints

10/148 PUBLIC 2012-03-14



http://service.sap.com/slo

http://service.sap.com/slo

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

◆ Try to copy the Java part of an ABAP+Java system to a Java standalone system or vice versa.

■ If you have implemented a federated portal network (FPN) across multiple SAP NetWeaver systems,

refer to SAP Note 1080080 before commencing with the system copy.


1.5 Constraints

2012-03-14 PUBLIC 11/148


2 Planning

This section describes how to plan your system copy.

You can use the system copy for:

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

■ Creating systems for testing, demonstration, training, and standby. 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.

Only valid for: Oracle |

NOTE

You cannot create standby systems with a system copy.

End of: Oracle |

NOTE

You should perform upgrades in a test system first. This allows you to identify customer-

specific problems that might result from modifications.

When copying a system that contains production data choose the right time for the copy. This could

be a month-end or year-end closing.

CAUTION

Do not use NFS-mounted file systems because writing to NFS-mounted file systems might cause

corrupted dumps.

Required Documentation

■ Read the following SAP Note for up-to-date information:

SAP Note 1317500 (Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0

including Enhancement Package 1 Support Release 1)

■ The documentation System Copy for SAP Systems Based on SAP NetWeaver 7.0 Including Enhancement Package

1 Support Release 1 only describes 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 .

Required DVDs, Tools, and Other Software

Make sure that all required DVDs for the system copy are available:

■ Required DVDs

● Installation Master DVD

● Java DVD

2 Planning

2012-03-14 PUBLIC 13/148



NOTE

The DVD names are abbreviated.

You can find the full names of all media shipped with SAP NetWeaver 7.0 EhP 1 SR 1 in the

appropriate Media List for SAP NetWeaver 7.0 EhP 1 SR 11 at: http://service.sap.com/

installNW70 Installation Installation – SAP NetWeaver Systems Media List – SAP NetWeaver 7.0 EHP

1 Support Release 1 .

■ Order the right version of the installation kit before starting the system copy.

Make sure that the versions of the SAP system and the installation tools are the same on the target

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

NOTE

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.

CAUTION

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

■ Check that you have the appropriate tool versions for your SAP kernel.

■ For a heterogeneous system copy, you need to get a migration key by generating it at http://

service.sap.com/migrationkey.

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. Perform a test run of the system copy. You can use the time taken by the test run to calculate the

system downtime:

■ If your target system will replace your source system, try to perform a complete test run. This

means that the entire database is exported from the source system, transferred to the target

system, and imported there. System downtime is approximately equal to the total test time

(that is, time for export, transport, and import).

■ If you do not want to replace your source system, a partial test run (export of the entire database

or parts of it) can be sufficient to calculate the system downtime. The source system is only

down for the time of the export.

Calculating the system downtime is particularly important for very large databases (VLDB)

or when tapes are being used. The test run is also to determine the amount of export data.

Choose the best data transfer method (for example, FTP or tape). We recommend that you

only perform read/write actions on local file systems.

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

2 Planning

14/148 PUBLIC 2012-03-14

http://service.sap.com/installNW70


http://service.sap.com/migrationkey


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 using SAP tools.

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

information, see Database-Independent System Copy [page 25].

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

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

◆ 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

For more information, see Database-Specific System Copy [page 59].

These methods are not supported for all database systems. Refer to the following table to check

which copy methods are available for your database system:

Database OS Platform Available Methods

SAP MaxDB UNIX Use one of the following: ● System copy procedure on UNIX using R3load for the

ABAP part and Jload for the Java partFor more information, see System Copy Procedure [page 26].

● System copy procedure for a homogeneous system copy onlyFor more information, see SAP MaxDB-specific procedure [page 72].

SAP MaxDB Windows Use one of the following: ● System copy procedure on Windows using R3load for the

ABAP part and Jload for the Java partFor more information, see System Copy Procedure [page 26].

● System copy procedure for a homogeneous system copy onlyFor more information, see SAP MaxDB-specific procedure [page 72].

IBM DB2 for i IBM i Use one of the following: ● System copy procedure on IBM i using R3load for the ABAP

part and Jload for the Java partFor more information, see Starting SAPinst on IBM i [page 47].

● IBM i-specific procedure for a homogeneous system copy onlyFor more information, see IBM DB2 i Procedure [page 80].

For more information, see SAP Note 585277.

2 Planning

2012-03-14 PUBLIC 15/148



IBM DB2 for Linux, UNIX, and Windows

UNIX or Windows Use one of the following: ● System copy procedure using R3load for the ABAP part and

Jload for the Java partFor more information, see System Copy Procedure [page 26].

● The backup method of IBM DB2 for Linux, UNIX, and Windows is supported for SAP systems based on SAP NetWeaver 7.0 EHP 1.For more information, see IBM DB2 for Linux, UNIX, and Windows Specific Procedures [page 75].

IBM DB2 for z/OS IBM System z Use one of the following: ● Only valid for: UNIX |

System copy procedure on UNIX using R3load for the ABAP part and Jload for the Java partFor more information, see System Copy Procedure [page 26].End of: UNIX |

● Only valid for: Windows |

System copy procedure on Windows using R3load for the ABAP part and Jload for the Java partFor more information, see System Copy Procedure [page 26].End of: Windows |

● Additional Information: ◆ For more information about the IBM DB2 for z/OS

specific procedure for a homogeneous system copy only, see the .PDF attachment to SAP Note 680746.

◆ When R3ta is used to split tables, DELETE with WHERE is not performed if import errors occur in the target system.For more information, see SAP Note 778729.

Oracle UNIX Use one of the following: ● Only valid for: UNIX |

System copy procedure on UNIX using R3load for the ABAP part and Jload for the Java partFor more information, see System Copy Procedure [page 26].End of: UNIX |

● Oracle-specific procedure for a homogeneous system copy onlyFor more information, see Oracle-Specific Procedure [page 61].

Oracle Windows Use one of the following: ● Only valid for: Windows |


● Homogeneous system copy only: Oracle backup/restore methodFor more information, see Oracle-Specific Procedure [page 61] and SAP Note 676468.

MS SQL Server Windows Use one of the following:

2 Planning

16/148 PUBLIC 2012-03-14





● Only valid for: Windows |


● Homogeneous system copy only: Backup/Restore or Detach/Attach MethodFor more information, see MS SQL Server-Specific Procedure [page 74] and SAP Notes 193816 and 151603.

■ Only valid for: Development Infrastructure (DI) |

Software Unit Development Infrastructure (DI) only:

For the migration of Java Development Infrastructure (JDI) components you can apply either

“Copy” or “Move”.

● Copy

“Copy” is supported only by Design Time Repository (DTR). After a copy, both the source

DTR and target DTR can be used productively in parallel. However, Component Build Service

(CBS) and Change Management Service (CMS) do not support such a copy.

● Move

“Move” is supported by all JDI components ‒ DTR, CBS, and CMS. After a move, the source

system can no longer be used ‒ that is, only the target is active after the move has been

performed.End of: Development Infrastructure (DI) |

■ 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 will require

a new license key for the target system. The license key of the source system is not valid for this

system. For more information about ordering and installing the SAP license, see the SAP Library

at:

http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SAP

Licenses .

For more information about SAP license keys, see http://service.sap.com/licensekey.

■ 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

2 Planning

2012-03-14 PUBLIC 17/148



http://help.sap.com/nw70

http://service.sap.com/licensekey

in the target system. Adapt the file residence information in the target system. For more

information, see the SAP Library at:


SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management Data

Archiving .

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

Refer to the section on hardware and software requirements in the SAP system

installation documentation to determine the system requirements.

2 Planning

18/148 PUBLIC 2012-03-14


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. For more information about SAP system

administration, refer to 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 kernel DVD of the installation kit and installed during the installation of the target system

with 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 central instance.

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

points to a valid JDK version.

■ 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 find out 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)

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

3 Preparations


2012-03-14 PUBLIC 19/148


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

place while a system is being copied as follows:

Tools CCMS Configuration Operation mode calendar (transaction SM63)

■ Write down the logical system names of all clients:

1. If you plan to overwrite an existing system with a system copy (for example, the source and

target systems will both exist after the system copy), make sure you write down the logical

system names of all clients in the system that will be overwritten (transaction SCC4).

As 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 (that is, 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 BI (formerly BW) 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),

no changes to logical system names are required.

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

1. Before deleting you must always check

● That the tables are consistent ‒ no restart log or conversion procedure termination must

be displayed

● That the data of the original table can be read

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

■ Only valid for: Development Infrastructure (DI) |

Usage Type Development Infrastructure (DI) only:

If your SAP system is of usage type Development Infrastructure (DI) then this system can only be

moved, but not be copied. This means that it is possible to migrate such a system from one host to

another but it is not possible to keep both systems active after the migration. If you want to move

an SAP system with usage type Development Infrastructure (DI), make sure that the following

prerequisites are met:

● The users and passwords created in the source system are valid in the target system (for

example, they use the same UME).

● Check in (or revert) all open activities (of all users) in the SAP NetWeaver Developer Studio

by using the Design Time Repository perspective (DTR perspective).

3 Preparations


20/148 PUBLIC 2012-03-14


● Remove all existing development configurations from the SAP NetWeaver Development

Studio.

● Verify in the DTR Web UI that there are no pending entries in the NameReservation queue.

To check this, go to http://<dtrhost>:<port>/dtr/sysconfig/support/

NameReservationList and check that there are no entries with the state PRELIMINARY,

FINALIZE_PENDING or REVERT_PENDING in the queue.

If there are entries with the state FINALIZE_PENDING or REVERT_PENDING you have to wait for

the next run of the name reservation background task in the DTR server that ends these

entries. This background task runs normally every 15 minutes.

To check the frequency of this background task you can have a look at http://

<dtrhost>:<port>/dtr/sysconfig/scheduled_tasks.html and check the value Periodicity for

the task ProcessNameReservationsTask. Since precondition for a successful execution of this

background task, the name server must be configured in the DTR server (http://

<dtrhost>:<port>/dtr/system-tools/administration/NameServerConfiguration. There

should be no entries with the state PRELIMINARY in the name reservation queue since they

only occur if there are open activities (which should not be the case if you followed the previous

steps).

● Stop all applications of the Development Infrastructure (DI) on the source system.End of: Development Infrastructure (DI) |

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

Accounting Financial Accounting General ledger Periodic Processing Closing Check/count

Comparison

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

CAUTION

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

● RFUMSV00 (tax on sales/purchases)

● RAGITT01 (asset history sheet)

● RAZUGA01 (asset acquisitions)

● RAABGA01 (fixed asset retirements)

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

3 Preparations


2012-03-14 PUBLIC 21/148

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

Normally both tables are empty. If you do not delete the contents of these tables, you will

encounter problems while importing the data to your target system because of non NULL

capable fields in these tables.

■ Prepare the system for SAPinst. For more information, see Installing the Java Development Kit [page

22].

3.2 Installing the Java Development KitOnly valid for: 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 |

A vendor Java Development Kit (JDK) 1.4.2 is required for the installation of the SAP system.End of: 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 |

Only valid for: IBM DB2 for i5/OS |

A vendor Java Development Kit (JDK) 1.4.2 on your Windows installation host is required for the

installation of the SAP system on your IBM i host.End of: IBM DB2 for i5/OS |

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

NOTE

Since IBM i has no graphical user interface, the SAPinst executable is running on the Windows

installation host. You need to install a valid JDK on Windows only for installation purposes. The

3 Preparations

3.2 Installing the Java Development Kit

22/148 PUBLIC 2012-03-14

J2EE engine of the SAP system uses the IBM JDK as mentioned in the Hardware and Software

Requirements section of the installation documentation.

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

Procedure

1. Only valid for: 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 |

Check the Product Availability Matrix (PAM) for released JSE platforms at http://

service.sap.com/pam Quick links and additional information <your product> JSE Platforms .End of: 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 |

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

Check the Product Availability Matrix (PAM) for the Windows version you want to use for running

SAPinst on for released JSE platforms at http://service.sap.com/pam Quick links and additional

information <your product> JSE Platforms .End of: IBM DB2 for i5/OS |

3. Only valid for: 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 |

Make sure that the latest JDK 1.4.2 version is installed on every host on which you want to install

an SAP instance:

■ You can check the version of installed JDKs by entering the following command:

java -version

■ If the latest JDK 1.4.2 version is not already installed, you need to download and install it.

For more information about how to download it, see the relevant SAP Note for your operating

system, which is referenced near the beginning of SAP Note 723909.End of: 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 |

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

Make sure that the latest JDK 1.4.2 version is installed on the Windows installation host on which

you want to run the SAPinst.

■ You can check the version of installed JDKs by entering the following command on your

Windows installation host:

java -version

■ If the latest JDK 1.4.2 version is not already installed, you need to download and install it.

For more information about how to download it, see the relevant SAP Note for the Windows

operating system, which is referenced near the beginning of SAP Note 723909.End of: IBM DB2 for i5/OS |

3 Preparations

3.2 Installing the Java Development Kit

2012-03-14 PUBLIC 23/148

http://service.sap.com/pam





4 Database Independent System Copy

You can use the SAP installation tool SAPinst to export and import your Java database content, file

system, and all configuration in a database-independent format. SAPinst uses both the R3load tool

and the Jload 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.

Jload generates a database export of all SAP objects that are defined in the Java Dictionary and archives

the configuration and components in the file system.

Only valid for: IBM i5/OS |

NOTE

On IBM i the database tools only exports into the integrated file system (IFS). Although, the

SAPinst for IBM i runs on Windows it is not possible to export into the file system on Windows.

End of: IBM i5/OS |

Constraints

R3load and Jload Restrictions

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

(R3load) or Java Dictionary (Jload). Other objects are not exported by SAPinst.

■ For a consistent database the SAP system must be shut down (excluding the database!). The database

must still be running.

■ R3load only: 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.

■ R3load only: Indexes longer than 18 characters are not allowed on the database to be exported.

System Copy Tools

■ Every installation service (dialog instance installation, for example) must have its own separate

installation directory whenever you start SAPinst.

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

delete the database on the target system before the import according to the corresponding

description in the Additional Information section of the installation documentation for your SAP

component.

If the database configuration of your database is stored in the file system, we recommend that you

back these configuration files up before deleting the database.


2012-03-14 PUBLIC 25/148

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 usually differ in the 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 smaller

pieces.

■ There are several ways to split packages. For a detailed description of the options, refer to the F1

help about the parameters prompted on the Split STR Files screen while running SAPinst to export

the database. The options can be used separately or ‒ when using the new Java based splitting tool

‒ together.

■ “Splitting of STR Files” is part of the “Advanced Export Parameters” and is disabled by default.

Using the splitting tool parameters selected by SAPinst is a good starting point if you select the

splitting option and you have not performed any tests yet.

CAUTION

If you want to split STR files by the size based option, 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.

If you do not have EXT files, then you can only split by providing tables via input file.

Process Flow

For UNIX, Windows, or IBM i, refer to System Copy Procedure [page 26].

4.1 System Copy Procedure

This section describes the system copy procedure using R3load and Jload.

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:

■ Central System

■ Distributed System and High-Availability System

Central System

To perform the export for a central system, you need to proceed as follows on the central system host:



26/148 PUBLIC 2012-03-14

1. Heterogeneous system copy: 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 central system host:

1. Only valid for: UNIX;Windows |

Make sure that the QCM tables are deleted from your system.

For more information, see General Technical Preparations [page 19].End of: UNIX;Windows |

2. Only valid for: IBM i5/OS |

Prepare the Windows host for the SAP system installation.

For more information, see Preparing the Windows Host for the SAP System Installation [page 42].End of: IBM i5/OS |


Prepare a Windows user account and an IBM i user profile.

For more information, see Preparing a Windows User Account and IBM i User Profile [page 43].End of: IBM i5/OS |


Install TMKSVR and create an installation share.

For more information, see Installing TMKSVR and Creating an Installation Share [page 44].End of: IBM i5/OS |

5. Generate DDL statements.

For more information, see Generating DDL Statements [page 29].

6. Prepare the system for table splitting (optional).

For more information, see Preparation for Table Splitting [page 30].

7. Run SAPinst on UNIX, Windows, or IBM i to prepare the source system for parallel export or

parallel import (optional).

For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 35] or

Running SAPinst on IBM i to Perform the Export [page 42].

In SAPinst, choose the installation service Export Preparation.

8. Run SAPinst on UNIX, Windows, or IBM i to export the database instance and the central

instance.

In SAPinst, choose the installation service Database and Central Instance Export.



NOTE

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

For more information, see Restarting R3load Processes [page 52].



2012-03-14 PUBLIC 27/148



Only valid for: IBM i5/OS;UNIX |

CAUTION

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

SAP Note 884452.

End of: IBM i5/OS;UNIX |

Result

You have finished this part of the system copy. To complete the system copy, you set up the target

system using SAPinst.

For more information, see Setting Up the Target System Using SAPinst [page 53].

Distributed System or High-Availability System

To perform the export for a distributed system or a high-availability-system, you need to 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.

For more information, see General Technical Preparations [page 19].

2. Generate DDL statements.

For more information, see Generating DDL statements [page 29].

3. Prepare the system for table splitting (optional).

For more information, see Preparation for Table Splitting [page 30].

4. Run SAPinst on UNIX, Windows, or IBM i to prepare the source system for parallel export/

import (optional). In SAPinst, choose the installation service Export Preparation.


Running SAPist on IBM i to Perform the Export [page 42].

5. Run SAPinst on UNIX, Windows, or IBM i to export the database instance. In SAPinst, choose

the installation service Database Instance Export.



CAUTION

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

SAP Note 884452.

3. Perform the export on the central instance host:

You run SAPinst to export the central instance. For more information, see Exporting the Source System

Using SAPinst [page 35].

In SAPinst, choose the installation service Central Instance Export.



28/148 PUBLIC 2012-03-14





Result

You have finished this part of the system copy. To complete the system copy, set up the target system

using SAPinst.

For more information, see Setting Up the Target System Using SAPinst [page 53].

Overview of Export Options

Figure 1:

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.

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. You should only

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

4. 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.2 Generating DDL Statements

2012-03-14 PUBLIC 29/148

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 SAP Note 888210.

4.3 Preparation for Table Splitting

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

the table is processed in, for example, 10 entities. 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 have to be performed with the migration monitor when the table splitting

feature is used.

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

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

● Oracle

For more information, see the paragraph 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

● DDNTT_CONV_UC

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



30/148 PUBLIC 2012-03-14


Procedure


Update the file R3ta in the kernel directory. You can find a version of this file on the Installation

Master DVD in the directory IM_<OS>/<DBTYPE>/{UC/NUC}.End of: IBM i5/OS |


Update the R3ta, R3ldctld, and the db<dbtype>slib.* in the kernel directory. You can find a

version of these files on the Installation Master DVD in the directory IM_<OS>/<DBTYPE>/{UC/

NUC}.End of: UNIX;Windows |

3. 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.End of: Oracle |

CAUTION

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

4. Start SAPinst.

5. Choose SAP NetWeaver System Copy Source System ABAP System <Database> <Unicode or Non-

Unicode> Table Splitting Preparation .

6. Specify SAPSID, <sidadm> 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!

7. Continue with Next.

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.

8. Check in the export directory <export dump directory>/ABAP/DATA if *.WHR files have been

created for all tables that are to be split.

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

1. Create a new, empty installation directory.

2. Define a new, empty export dump directory <temporary dump directory>.

3. Run the Prepare Table Splitting service again and provide an input file that contains only the

missing tables with a lower number of packages for each defined table.

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

the first Prepare Table Splitting run:



2012-03-14 PUBLIC 31/148


1. Copy the *.WHR files from <temporary dump directory>/ABAP/DATA to <export dump

directory>/ABAP/DATA.

2. Add the lines from <temporary dump directory>/ABAP/DATA/whr.txt to <export dump

directory>/ABAP/DATA/whr.txt.

9. 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.End of: Oracle |

For more information, see the paragraph Creating a Temporary Index.

Parallel data export of a table is supported by all database platforms but parallel data import is not. If

the target database platform does not support the parallel data import, the migration monitor has to

be configured so that the data import processes the packages 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 Master

DVD. After the Table Splitting Preparation, make sure you select the Split predefined tables checkbox and add

the R3ta_hints.txt file in the Split STR Files dialog box. If you want to modify this file, copy it from the

directory <IM_OS>/COMMON/INSTALL to the installation directory and adapt it according to 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 |



32/148 PUBLIC 2012-03-14

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=954268.&_NLANG=en&_NVERS=0

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&

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



2012-03-14 PUBLIC 33/148

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 the Export

You can prepare the source system for the export using R3load and Jload, so as to enable parallel export/

import. For this purpose you need to create certain files.

The following steps are performed:

■ Creating the export directory structure

■ Creating database structure files (*.STR)

■ Updating database statistics (…)

■ Size calculation for the target database (*.EXT,DBSIZE.XML)

These export preparations are required, if:

■ You want to build up the target system to the point where the database load starts before the export

of the source system has finished.

■ Export and import processes should run in parallel during the system copy process.

Procedure

1. Run SAPinst to perform the Export Preparation service.

For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 35].

2. As soon as the export preparations have finished successfully, the complete export directory with

its structure and the generated files, which are required for building up the target system, have to

be transferred to the target host.

CAUTION

Make sure that the dump directory is not under the installation directory. or another

directory that contains installation information (such as the Installation Master DVD, the

Java DVD, or other export files).

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.

You can choose one of the following methods:

■ Use the migration monitor with the FTP Copy option to transfer the files to the target instance.

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

In any case, make sure that the dump directory and its subdirectories and files are accessible for

user <sapsid>adm of the target system.


4.4 Preparing the Export

34/148 PUBLIC 2012-03-14

NOTE

For more information, see the documentation Migration Monitor – User’s Guide in the

MIGMON.SAR archive on the SAP Installation Master DVD.

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 35]

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

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

a 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 perform a remote system copy with SAPinst instead, 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 132].

Note the following about SAPinst:

■ When you start SAPinst, SAPinst GUI and the GUI server are also started. SAPinst GUI connects

to the GUI server using a secure SSL connection and the GUI server connects to SAPinst.

Only valid for: UNIX |

■ SAPinst normally creates the installation 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

installation 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 below 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 service, called <sapinst_instdir>

\<installation_service>, which is located below %ProgramFiles%\sapinst_instdir.



2012-03-14 PUBLIC 35/148

■ 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 with the name sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary

directory. You can safely delete them.

In the temporary directory, you can also find the SAPinst Self-Extractor log file dev_selfex.out,

which might be useful if an error occurs.End of: Windows |

CAUTION

If SAPinst cannot find a temporary directory, the installation terminates with the error

FCO-00058.

CAUTION

If you would rather create an installation directory manually, make sure that you create it

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


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

● Click the icon for the SAPinst output window located in the Windows tray and choose File

Exit .End of: Windows |

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.

■ Only valid for: UNIX |

You are logged on to your host as user root.End of: UNIX |


You are logged on to your host as a user with the required rights and privileges that authorize you

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

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

■ Make the Master Installation DVD available.

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

and at least 130 MB of free space in the installation directory for each Java installation option. In

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



36/148 PUBLIC 2012-03-14


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 |

■ 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>\SDM

\program as is used in \\SAPLOC\<SAPSID>\<InstanceName>\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 |


■ Before starting the export, make sure that you have at least the same amount of disk space available

in /sapmnt/<SAPSID>/<InstanceName>/SDM/program as is used in /sapmnt/<SAPSID>/

<InstanceName>/SDM/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 |

For more information about SAPinst, see Using SAPinst GUI [page 128], Interrupted Installation with SAPinst

[page 129], and Performing a Remote Export Using SAPinst [page 132].

Procedure

1. Start SAPinst from the SAP Installation Master DVD as follows:


Choose one of the following ways:

■ Using the default installation directory (recommended)

Enter the following commands:

cd <Installation_Master_DVD>/IM_<OS> ./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.



2012-03-14 PUBLIC 37/148

CAUTION

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

to another operating system.

For example, the following causes an error:

$ cd /sapcd2/IM_HPUX_IA64

$ /sapcd2/IM_HPUX_PARISC/sapinst

To correct this, enter the following:

$ cd /sapcd2/IM_HPUX_PARISC

$ /sapcd2/IM_HPUX_PARISC/sapinst

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, for example, by using a crontab entry.

■ Using an alternative installation directory

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

TMP, or TMPDIR.End of: UNIX |


NOTE

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

■ During the installation, the default ports 21200 and 21212 are used for communication

between SAPinst, GUI server, and SAPinst GUI. SAPinst uses port 21200 to communicate

with the GUI server. The GUI server uses port 21212 to communicate with SAPinst GUI.

You get an error message if one of these ports is already in use by another service.

In this case, you must execute SAPinst using the following parameters:

SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server>

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>

■ To get a list of all available SAPinst properties, start SAPinst as described above with the

option –p: ./sapinst —p.

End of: UNIX |


■ Double-click sapinst.exe from the following path:

<DVD_drive>:\IM_WINDOWS_<platform>

SAPinst GUI normally starts automatically by displaying the Welcome screen.

However, if there is only one component to install, SAPinst directly displays the first input

dialog without presenting the Welcome screen.



38/148 PUBLIC 2012-03-14

NOTE

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

● During installation, the default ports 21200 and 21212 are used for communication

between SAPinst, GUI server, and SAPinst GUI. SAPinst uses port 21200 to

communicate with the GUI server. The GUI server uses port 21212 to communicate

with SAPinst GUI. You get an error message if one of these ports is already in use by

another service.

In this case, open a command prompt and change to the required directory as

follows:

<DVD drive>:\IM_WINDOWS_<platform>

Enter the following command in a single line:

sapinst.exe

SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server>

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>

● To get 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 |

2. On the Welcome screen, choose Software Life-Cycle Options System Copy <database> Source System

<Distribution option> Based on <technical stack> .

3. Select the corresponding system copy option from the tree structure, according to the sequence

of the process flow for the database-specific or the database-independent system copy procedure.

For more information, see Database-Specific System Copy procedure [page 59] or Database-Independent System

Copy [page 25].

CAUTION

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

system variant.

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

Export Services for a Central System

Export Service Remarks

Export Preparation

NOTE

Do not perform this step if you use the database-specific method.

Optional step for preparing the export.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)



2012-03-14 PUBLIC 39/148


Table Splitting Preparation

NOTE


Optional stepSAPinst 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 and Central Instance ExportIf you use the database-specific procedure, SAPinst only performs the following steps:

NOTE

■ Creates the export directory structure with label files

■ Archives the SDM ■ Archives application-specific file

system content.

Mandatory step for system copy procedure.SAPinst performs the following steps: ■ Creates the export directory structure with label

files ■ Creates database structure files (*STR) ■ Updates database statistics ■ Calculates the size of the target database

(*EXT,DBSIZE.XML) ■ Exports the database content ■ Archives the SDM ■ Archives application-specific file system content

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


CAUTION

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

Note 884452.

End of: UNIX |

NOTE

If you generated SQL files with DDL statements (see Generating DDL Statements [page 29]), copy

the generated files into the SAPinst installation directory as soon as it has been created by

SAPinst. The installation directory is as soon as the first input screen appears.

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

CAUTION

You must choose Typical when performing a system copy with database tools.

NOTE

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

parameter field and choose F1 .

6. Database-specific procedures only: On the SAP System > Database Export screen, choose System Copy

Method Use database specific tools .

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

during the processing phase.



40/148 PUBLIC 2012-03-14


Troubleshooting

If an export process aborts due to a hardware failure (for example, file system full, power outage,

operating system crash), 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 then 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. It is currently not possible to

distribute the export over different file systems automatically.

■ If an error occurs during the dialog phase, SAPinst:

● Stops the export.

● Displays a dialog that informs you about the error.

You can now view the log file directly by choosing View Logs.

Finally, you have to abort the export with OK and try to solve the problem.

■ If an error occurs during the processing phase, SAPinst:

● Stops the export.


You can now:

● View the log file directly 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 <sid>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 NW 7.0 SR1.

Solution:

Manually associate <sid>adm and ora<sid> OS users with sapinst group if this association is

missing.

Verify the /etc/group file and check if the sapinst group exists and OS users are members of this

group.

If the sapinst group does not exist yet, start SAPinst. SAPinst will create this group during startup

before the product catalog list is displayed.



2012-03-14 PUBLIC 41/148

Edit /etc/group file and associate OS users with sapinst group.

Continue with the export.End of: UNIX |

For more information, see Using SAPinst GUI [page 128], Interrupted Installation with SAPinst [page 129], and

Performing a Remote Export Using SAPinst [page 132].


4.5.2 Running SAPinst on IBM i to Perform the Export

4.5.2.1 Preparing the Windows Host for the SAP System Installation

The Java-based SAPinst graphical user interface (SAPinst GUI) requires a Java Development Kit (Java™

2 SDK, Standard Edition) with graphical capabilities (AWT, Swing). Since IBM i does not provide a

graphical user interface, you must install the JDK on a Windows host to perform the installation with

SAPinst.

Prerequisites

To prepare the system for SAPinst and SAPinst GUI you need to do the following:

■ Necessary operating system versions: Windows NT/2000/2003/XP/7/2008

■ Check your Java Runtime Environment (JRE) on the host where SAPinst GUI runs, because the

JRE cannot be integrated into the SAPinst GUI executable for all platforms due to licensing issues.

■ Set the system path if you install on Windows.

Procedure

The SAP J2EE Engine requires a Java Development Kit (Java™ 2 SDK, Standard Edition). Therefore,

make sure a valid JDK version is installed on every host on which you want to install an SAP instance

including the SAP J2EE Engine.

For more information about the JDK versions that are released for the SAP Web Application Server,

SAP components based on SAP Web AS and the SAP J2EE Engine, see http://service.sap.com/

platforms Product Availability Matrix SAP NetWeaver SAP NetWeaver '04 JSE Platforms

NOTE

■ JDK is not part of the SAP shipment. If necessary, you need to download and install it.

■ To check the version of an already installed JDK, enter:

java -version

■ If you have more than one Java Virtual Machine (JVM) installed on your system (for example,

you have two JDKs with different versions installed), make sure that the JAVA_HOME

environment variable is set to the valid <JAVA_HOME> directory. Make sure that %JAVA_HOME%

\bin is included in your system path.



42/148 PUBLIC 2012-03-14

http://service.sap.com/platforms

http://service.sap.com/platforms


4.5.2.2 Preparing a Windows User Account and IBM i User Profile

For the installation you need to create a user account on your Windows installation host and a user

profile on the IBM i you want to install.

The following requirements apply:

■ The IBM i user profile and the Windows user account must have the same name and password.

■ Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |

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

QSECOFR.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |

■ Only valid for: SAP SCM |

The IBM i user profile must be the user QSECOFR.

NOTE

This is different to other installations on IBM i. For other installations, we recommended that

you create user SAPINST or SAPIUSR. However for SCM, you need to use the user QSECOFR

because the liveCache client software has to be installed by this special user.

End of: SAP SCM |

■ The Windows user account must have administrator rights on the Windows installation host.

ProcedureOnly valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |

NOTE

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

installation documentation, we used the user SAPINST. However, in future releases SAP has

introduced a group called SAPINST on IBM i, which conflicts with the previously recommended

user SAPINST.

End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |

Windows:

1. Create a local user.

2. Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |

In the field User name, enter your installation user name, for example, SAPIUSR.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |

3. Only valid for: SAP SCM |

In the field User name, enter your installation user name QSECOFR.End of: SAP SCM |



2012-03-14 PUBLIC 43/148


In the fields Password and Confirm password, enter the password SAP.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |


In the fields Password and Confirm password, enter the password of the user QSECOFR on your IBM i.End of: SAP SCM |

6. Deselect User must change password at next logon.


Assign the new user SAPIUSR to the group Administrators.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |


Assign the new user QSECOFR to the group Administrators.End of: SAP SCM |

IBM i:

Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |

Enter the following command:End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |

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

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

Only valid for: SAP SCM |

To change the user QSECOFR, enter the following command:End of: SAP SCM |


CHGUSRPRF USRPRF(QSECOFR) LANGID(ENU) CNTRYID(US) CCSID(500) LOCALE(*NONE).End of: SAP SCM |


After the installation, you can revert the user profile QSECOFR back to the old values.End of: SAP SCM |

CAUTION

You should not set the system variable QIBM_PASE_CCSID. This could lead to codepage conversion

problems within the installation. Delete the environment variable QIBM_PASE_CCSID at least for

the time while you are installing your SAP system. To delete an environment variable use the

command WRKENVVAR.



4.5.2.3 Installing TMKSVR and Creating an Installation Share

The TMKSVR is the interface between IBM i and Windows for the installation with SAPinst. SAPinst is

running on Windows, but has to install the product on IBM i. This means that all actions required for



44/148 PUBLIC 2012-03-14

IBM i are initiated remotely on Windows but executed locally using the TMKSVR. The communication

is done using TCP/IP.

In addition, an installation share on the IBM i host needs to be created and mapped to the Windows

installation host, which is done automatically by the TMKSVR.

The TMKSVR has to be installed and an installation share has to be created on all IBM i hosts where

instances of an SAP system should be installed.

Prerequisites

■ An FTP server running on IBM i

■ Make sure the NetServer is configured correctly. For more information, see SAP Note 709024.

■ You must prepare a user. For more information about how users are prepared, see Preparing a Windows

User Account and IBM i User Profile [page 43].

■ The Installation Master DVD must be inserted in the DVD drive of your Windows installation host.

■ If you have downloaded the DVDs from SAP Service Marketplace, the downloaded Installation Master

DVD must be available on your Windows installation host.

■ Make sure there is no system variable LANG defining a LOCAL on your IBM i host where you want

to install your SAP system. To find out if this variable can be de-activated during the installation,

contact your IBM i administrator. Otherwise, code page problems might prevent TMKSVR processes

from starting. To remove the environment variable LANG from your environment on your IBM i

host you can use the command WRKENVVAR.

Procedure

1. Log on to your Windows installation host as the installation user. For more information, see Preparing

a Windows User Account and IBM i User Profile [page 43].

Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM |

NOTE

This user must have the same user ID and password as the user that you are using for the

installation on IBM i (a user with administrator rights similar to QSECOFR).

End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM |


NOTE

This user must have the same user ID and password as the user that you are using for the

installation on IBM i. For SCM, this user must be QSECOFR).

End of: SAP SCM |

2. Run SETUP.EXE from the directory IM_OS400_PPC64\TMKSVR on the DVD containing the

installation package. You can start the setup program by double-clicking on it in the Windows

Explorer.

The following dialog box appears:



2012-03-14 PUBLIC 45/148


Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |

Figure 2:

End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |


Figure 3:

End of: SAP SCM |

3. Enter the following values:

■ iSeries Hostname:

Enter the name of the IBM i host where you want to install TMKSVR.

■ Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM |

iSeries Administrator (QSECOFR or similar):

Enter the IBM i user. For more information, see Preparing a Windows User Account and IBM i User

Profile [page 43].End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM |



46/148 PUBLIC 2012-03-14

■ Only valid for: SAP SCM |

iSeries Administrator (QSECOFR):

Enter the IBM i user. For more information, see Preparing a Windows User Account and IBM i User

Profile [page 43].End of: SAP SCM |

■ TMKSVR instance number:

Leave the value at 0.

■ TMKSVR Instance Port (also referred to as the Dispatcher Port):

Leave the value at 59975, if possible. Only change this port number if you encounter problems

during installation because the port is in use.

Result

The installation uses FTP to install and starts the TMKSVR on IBM i. During installation, a library named

TMKSVR<nn> is created, with <nn> being the instance number (for example, TMKSVR00).

A NetServer share named ROOTBIN is created on the IBM i host. You can map the share now to your

Windows PC or let SAPinst map it during the installation.

For more information, see the documentation INSTALL.PDF on the DVD in directory

IM_OS400_PPC64\TMKSVR.

NOTE

For more information about how to delete the TMKSVR after a successful installation, see the

Removing the SAPinst Installation Files section of the installation documentation.

NOTE

For more information about how to start a stopped TMKSVR subsystem, see Interrupted Installation with

SAPinst [page 129].



4.5.2.4 Starting SAPinst on IBM i

CAUTION

This section refers to “installation of an instance”, which is a synonym for “export an SAP system”.

This procedure tells you how to run SAPinst to install one or more SAP instances. It describes an

installation where SAPinst GUI and SAPinst server are running on the same Windows host.

SAPinst creates the installation directory \usr\sap\sapinst on IBM i.



2012-03-14 PUBLIC 47/148

Prerequisites

CAUTION

Make sure that you shut down all SAP Application Servers before the export. Otherwise, the target

system might be inconsistent.

■ TMKSVR is up and running: WRKACTJOBSBS(TMKSVR00) (there must be a DISPATCH job). For more

information, see Installing TMKSVR and Creating an Installation Share [page 44].

■ The Windows host is set up. For more information, see Preparing the Windows Host for the SAP System

Installation [page 42].

■ The users required for the installation are prepared. For more information, see Preparing a Windows


■ Make sure that the JAVA_HOME environment variable is set correctly on your Windows host.

Procedure

1. Log on to the Windows host as the installation user. For more information, see Preparing a Windows


2. Start SAPinst from the SAP Installation Master DVD by using the default installation directory

(recommended):

1. Double-click sapinst.exe from the following path:<Mapped drive>:\<Copied

Installation Master DVD>\IM_OS400_PPC64

2. Enter the following command in a single line:

sapinst.exe

SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server>

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to sapinst_gui>

NOTE

■ For a list of all available SAPinst properties, enter the following command: 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>.

■ During the installation, the default ports SAPinst 21212 and 21213 are used for

communication between SAPinst, GUI server, and SAPinst GUI. SAPinst uses port 21200

to communicate with the GUI server. You get an error message if one of these ports is

already in use by another service. In this case, open a command prompt and change to

the required directory as follows:

<Mapped drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64

3. The SAPinst/TMKSVR – Session Parameters dialog box appears and prompts you for the target IBM i

parameters. Enter your values.



48/148 PUBLIC 2012-03-14

Figure 4:

The SAPinst GUI now starts automatically by displaying the Welcome screen.

4. In the Welcome screen, choose Software Life-Cycle Options System Copy <your database> Source System

<System Variant> Based on <AS ABAP and AS Java | AS Java | AS ABAP> .

5. Select the corresponding installation service from the tree structure, according to the sequence

of the process flow, for one of the following procedures:

■ Database-Specific System Copy [page 59]

■ Database-Independent System Copy [page 25]

CAUTION

Make sure that you choose the installation services in exactly the order they appear for each

system variant.

6. The following table provides an overview about the available installation services available for a:

■ Central system

■ Distributed system or high-availability system

Export Services for a Central System


Export Preparation

NOTE


Optional step for preparing the export.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)



2012-03-14 PUBLIC 49/148



NOTE



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 and Central Instance ExportIf you use the database-specific procedure, SAPinst only performs the following steps:

NOTE

■ Creates the export directory structure with label files

■ Archives the SDM ■ Archives application-specific file

system content.

Mandatory step for system copy procedure.SAPinst performs the following steps: ■ Creates the export directory structure with label

files ■ Creates database structure files (*STR) ■ Updates database statistics ■ Calculates the size of the target database

(*EXT,DBSIZE.XML) ■ Exports the database content ■ Archives the SDM ■ Archives application-specific file system content

Export Services for a Distributed System or a High-Availability System


Export Preparation

NOTE


Optional step for the database-independent system copy procedure to prepare the export.You need to perform this step on the database instance host.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)


NOTE



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

CAUTION

You must perform this step before you perform Central Instance Export.

Mandatory step for the database-independent system copy procedure.You need to perform this step on the database instance host.SAPinst performs the following steps:



50/148 PUBLIC 2012-03-14

Export Service RemarksNOTE


■ Creates the export directory structure with label files ■ Creates database structure files (*STR) ■ Updates database statistics ■ Calculates the size of the target database

(*EXT,DBSIZE.XML) ■ Exports the database content

Central Instance Export

CAUTION

Before you perform this step, you must have completed the Database Instance Export.

Mandatory step for database-independent system copy procedure.You need to perform this step on the central instance host.SAPinst performs the following steps: ■ Creates the export directory structure with label files. ■ Archives the SDM ■ Archives application-specific file system content

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

8. Choose Next

NOTE

If you generated SQL files with DDL statements (see Generating DLL Statements [page 29]), copy

the generated files into the SAPinst installation directory as soon as it has been created by

SAPinst:

1. Choose Database and Central Instance Export.

2. Choose Next.

3. The installation directory has 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 Typical when performing a system copy with database tools.

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.

When the installation has successfully completed, the screen Finished installation is displayed.

Troubleshooting

CAUTION

If an export process aborts due to a hardware failure (for example, file system full, power outage,

operating system crash), 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 an error occurs during the dialog phase, SAPinst:



2012-03-14 PUBLIC 51/148

● Stops the installation.


You can now directly view the log file by choosing View Logs.

Finally, you must abort the installation with OK and try to solve the problem.

■ If an error occurs during the processing phase, SAPinst:

● Stops the installation.


You can now directly view the log file by choosing View Logs.

● Try to solve the problem.

● Retry the installation by choosing Retry.

● Abort the installation by choosing OK.

For more information, see Interrupted Installation with SAPinst [page 129].End of: IBM i5/OS |

End of: IBM i5/OS |

4.5.3 Restarting R3load Processes

The state file allows package states to be manually updated to restart failed R3load processes.

EXAMPLE

For 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

to the package state are ignored.

■ Sockets only: You cannot restart processes.

Restarting R3load Processes Using the Socket Option

There are four possible situations where an R3load restart may be required.

First of all, you need to cancel the R3load process. If one of the corresponding R3load processes (export

or import) is still running, cancel it as well. Then restart SAPinst to continue with the system copy. To

continue with the system copy proceed as follows:

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



52/148 PUBLIC 2012-03-14

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

◆ for the TSK file of the export 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 (export as

well as import) in the TSK file and in the *state* file to 'err'.

EXAMPLE

Export Import

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 (export). That means that in the import TSK

file the status for TAB_2 must be set from 'ok' to 'err'. The entry in the *state* file also

must be set from '+' to '0'.

■ If the import is completed successfully, but the export was canceled with errors, you can set

the status in the export_state.properties from '-' to '+'.

More Information

R3load Processes Using the Migration Monitor [page 111].

4.6 Setting Up the Target System

Purpose

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

source system.

Process Flow

Central System

Perform the following steps on the central system host:

1. Prepare the central system host for the installation of your target system as described in the

installation guide for your SAP system solution.

2. If you have already prepared the export (for more information, see Preparing the Export [page 34]) on

the source system, perform the following steps:



2012-03-14 PUBLIC 53/148

1. If you use the FTP Exchange option during the export (transfer type FTP, 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 the Preparing the Export [page

34] step on the source system.

2. Transfer the Java export files to the central system target host. For more information, see

Transferring the Export Files to the Target Host [page 55].

3. Install the target system. For more information, see Installing the Target System [page 55].

If you did not prepare the export on the source system, perform the following steps:



2. Install the target system. For more information, see Installing the Target System [page 55].

3. If required install additional dialog instances on dialog instance hosts as described in the


Distributed System or High-Availability System

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

1. Prepare the central services instance host, the database instance host, and the central

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

in the installation guide for your SAP system solution.

2. Install the central services instance for the target system as described in the installation guide

for your SAP system solution.

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

■ If you have already prepared the export (for more information, see Preparing the Export [page

34]) on the source system, perform the following steps:

1. If you use the FTP Exchange option during the export (transfer type FTP, communication

type Exchange Directory, on the SAP System > Communication Parameters for Export screen),

make sure that you have transferred the files, which were generated in the Preparing the

Export [page 34] step on the source system.



3. Install the database instance of the target system. For more information, see Installing the

Target System [page 55].

■ If you did not prepare the export (see Preparing the Export [page 34]) on the source system, perform

the following steps:



2. Install the database instance of the target system. For more information, see Installing the

Target System [page 55].



54/148 PUBLIC 2012-03-14

4. On the central instance host, install the central instance of the target system.

5. If required, install additional dialog instances on the dialog instance hosts as described in the


4.6.1 Transferring the Export Files to the Target Host

Procedure1. 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 DVD, the Java DVD, or

other export files).

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

NOTE

If you transfer the files with file transfer protocol (ftp), make sure that you use binary mode

for transferring the files.

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.

NOTE

If your source system is a distributed system, the files created by the export of the central instance

and the files created by the export of the database instance have to be located in the same

<EXPDIR> directory for the installation of the target system.

If you have not exported into the same <EXPDIR> already, then you have to merge the two

<EXPDIR> directories from the central instance export and from the database instance export

before starting the target system installation.

4.6.2 Installing the Target System

PrerequisitesOnly valid for: Windows |

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 will be created, look at the file DBSIZE.XML

located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE>.End of: Windows |



2012-03-14 PUBLIC 55/148


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 will be created, look at the file DBSIZE.XML

located in the directory <EXPDIR>/DB/<DATABASE>.End of: UNIX |

NOTE

As of SAP NetWeaver 7.0, RELOAD is no longer available as an executable installation service, but

is performed automatically by SAPinst. 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.

Procedure

1. Prepare the target system host as described in the installation guide of your SAP solution based on

SAP NetWeaver 7.0 EHP 1 SR 1.

Only valid for: IBM DB2 for Linux and UNIX and Windows |

NOTE

Make sure that you read the information provided in section Setup of Database Layout in the

installation documentation.

End of: IBM DB2 for Linux and UNIX and Windows |

2. Start SAPinst as described in the installation documentation for your SAP solution based on SAP

NetWeaver 7.0 EHP 1.

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

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

service.sap.com.

3. On the Welcome screen of the SAP Installation Master DVD, navigate to the following folder

according to the requirements of your target system: Software Life-Cycle Options System Copy

<database> Target System <Distribution option: Central System / Distributed System / High-Availability

System> Based on <Stack option> AS ABAP and Java / AS Java / AS ABAP> .

4. Run the installation services required for your system copy in the sequence they are listed in the

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

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

required parameters.

NOTE

On the SAP System > General Parameters screen, as default, the Unicode System option is selected.

You can only deselect this option if you perform the system copy for a non-Unicode SAP

system that has been upgraded to SAP NetWeaver 7.0 EHP1.



56/148 PUBLIC 2012-03-14

http://service.sap.com

http://service.sap.com

On the Database - Select the Database Instance Installation Method screen, choose the option 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.


CAUTION

■ Make sure that you take the information about automatic storage that is provided in

the Running SAPinst section in the appropriate installation guide into consideration.

■ The option Deferred Table Creation is not supported for load-based system copies for SAP

systems that are not based on SAP NetWeaver 7.0 EHP 1 or higher.


CAUTION

■ Do not create the installation directory (for example, sapinst_instdir) under the

following directories:

● UNIX: /usr/sap/<SAPSID>

Windows: \usr\sap\<SAPSID>

● UNIX: /sapmnt/<SAPSID>

Windows: \sapmnt\<SAPSID>

■ 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 DYNPSOURCE table will be created in the target database.

The required size for the table will be fifteen times larger than in the non-Unicode source

system.

6. When SAPinst displays the DVD / CD browser window and asks for the Export Migration CD, enter

the path to the export directory <EXPDIR>.

7. If you perform a heterogeneous system copy, enter the migration key on the Database Import screen.

If you want to perform export and import in parallel, choose the Parallel Export / Import option.

NOTE

You must have run the service Prepare the Export on the source system [page 34] if you want to use

the parallel export/ import option for the installation of the target system.

8. 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 was not imported successfully.

For more information about restarting failed R3load processes, refer to Restarting R3load

Processes [page 52].



2012-03-14 PUBLIC 57/148

NOTE

The Java engine is not started automatically. After the target system has been installed and the

follow-up activities (refer to Follow-Up Activities [page 83]) have been performed, you have to start

the Java engine manually.



58/148 PUBLIC 2012-03-14

5 Database-Specific System Copy

The following sections describe database-specific methods for the homogeneous system copy. Database-

specific methods are not available for all database systems. For more information about methods

available for your database, see Planning [page 13] and to the SAP Notes describing the homogeneous

system copy for your database system.

Process

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

■ Central System

■ Distributed System

■ High Availability System

Central System

To perform the export for a central system, you need to proceed as follows on the central system host:


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

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

1. Run SAPinst on UNIX or Windows [page 35] to create the export directory structure with labels and

to archive SDM and application-specific file system content.

In SAPinst, choose the installation option that corresponds to your database, SAP system, and

technology, and then Database and Central Instance Export.

EXAMPLE

<your SAP version> Software Life-Cycle Options System Copy Oracle Source System Export

Central System Based on AS ABAP and AS Java Database and Central Instance Export

2. Generate the control file structure for the target database [page 62].

3. If required, create an offline backup of the source database [page 67].

Process Flow on the Target System

1. Only valid for: Windows |

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

2. Only valid for: UNIX |

Prepare the target system [page 68]:

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

software and to perform the database backup/restore.


2012-03-14 PUBLIC 59/148

CAUTION

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

as of the source system. Otherwise, the UME service can not be started.

2. Create the database file system (if it does not yet exist).

3. Install the database software.End of: UNIX |

3. Only valid for: IBM i5/OS;Windows |

Follow the instructions on the SAPinst screens until you are requested 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

of the source system. Otherwise, the UME service can not be started.

NOTE

If required, restart SAPinst as described in the installation guide of your SAP solution.

End of: IBM i5/OS;Windows |

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

Distributed System or High Availability System

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


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


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

database [page 62].

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

3. On the central instance host, run SAPinst on UNIX or Windows [page 35] to create the export

directory structure with labels and to archive SDM and application-specific file system content.

In SAPinst, choose the installation option that corresponds to your database, SAP system, and

technology, and then Database and Central Instance Export.

EXAMPLE

<your SAP version> Software Life-Cycle Options System Copy <your database> Source System

Export Distributed System Based on AS ABAP and AS Java Database and Central Instance Export

Process Flow on the Target System


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

of your SAP solution.End of: Windows |


Prepare the target system [page 68]:


60/148 PUBLIC 2012-03-14

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, create the database file system (if not yet existing).

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

3. Only valid for: IBM i5/OS;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, restart SAPinst as described in the installation guide of your SAP solution.

End of: IBM i5/OS;Windows |

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


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 is a complete data backup of your source database. You can use an offline backup, an online

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

content are different.

Advantages

■ You can use existing offline or online backups.

■ This method is faster than the R3load and Jload method.

Disadvantages

■ 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 when you create an offline backup manually

or an offline backup with BR*Tools.

■ You cannot change the database schema and the table space names.

Prerequisites

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

system.



2012-03-14 PUBLIC 61/148

■ You must have prepared your system for SAPinst [page 22].

■ 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 JRE version 1.4.1 or higher is installed

on the database instance.

■ The JAVA_HOME environment variable must point the JRE directory.

■ For security reasons, the source and target systems must run on different hosts.

■ The source and target systems must be binary compatible.

NOTE

Note that you can also perform a system copy from 32-bit systems to 64-bit systems and vice

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

compatible.

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 SAP Installation Master DVD to the installation directory

and extract it using SAPCAR.

You can find the archive in the following directory on the Installation Master DVD:


<DVD-DIR>:/COMMON/INSTALL/ORA/ORABRCOPY.SAR

End of: UNIX |



62/148 PUBLIC 2012-03-14


<DVD-DRIVE>:\COMMON\INSTALL\ORA\ORABRCOPY.SAR

End of: Windows |

3. Make sure that all redo log groups are archived

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

user ora<dbsid>

user <sapsid>adm

■ If you perform an offline manual copy, enter the following commands:

● On UNIX:

./ora_br_copy.sh –generateFiles –forceLogSwitches —targetSid

<TARGET_DBSID> —password <system's password> —listenerPort <listener port>

● On Windows:

ora_br_copy.bat –generateFiles –forceLogSwitches —targetSid <TARGET_DBSID>

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

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.

■ If you perform an offline or online backup using BR*Tools, enter the following commands:

● On UNIX:

./ora_br_copy.sh –generateFiles —targetSid <TARGET_DBSID> —password

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

● On Windows:

ora_br_copy.bat –generateFiles —targetSid <TARGET_DBSID> —password

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

NOTE

During the online backup, the database must be up and running. To ensure this, this

command must not contain the parameter —forceLogSwitches.

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

installation directory, and performs the required log switches.

NOTE

If an error occurs, check the log file:

<INSTDIR>/ora.brcopy.log

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

follows.

Example for Windows

In the following example for Windows, entries of CONTROL.SQL written in bold should be compared to

the trace file:

REM



2012-03-14 PUBLIC 63/148

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

REM CONTROL.SQL

REM

REM SAP AG Walldorf

REM Systeme, Anwendungen und Produkte in der Datenverarbeitung

REM

REM (C) Copyright SAP AG 2004

REM

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

REM Generated at:

REM Fri Sep 17 08:33:25 CEST 2005

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

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 (



) SIZE 50M,



64/148 PUBLIC 2012-03-14

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\SAPDATA1\IMS700_1\IMS700.DATA1',











'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;

NOTE

In the above example for Windows, entries and values of CONTROL.SQL written in bold should be

compared to the trace file. The changes to be made are valid for UNIX, too.



2012-03-14 PUBLIC 65/148

Changes to be made

1. If you want to upgrade your database from 32-bit to 64-bit, add the following lines at the bottom

of the CONTROL.SQL file:

shutdown immediate;

startup restrict

spool utlirp.log

@?/rdbms/admin/utlirp.sql

spool off

alter system disable restricted session;

2. MAXLOGFILES 255

...

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

3. GROUP 1 (



) 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\SAPDATA1\IMS700_1\IMS700.DATA1'

…

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 rows with ALTER TABLESPACE must be equal to the number of corresponding rows

in the trace file.



66/148 PUBLIC 2012-03-14

5.1.2 Creating a Backup

Create a backup if required. Choose between the following possibilities: Performing an offline backup

manually or an offline or online backup with BR*Tools.

■ Creating an Offline Backup Manually [page 67]

■ Creating an Offline or Online Backup with BR*Tools [page 67]

5.1.2.1 Creating an Offline Backup Manually

Procedure

There are different possibilities to prepare 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.

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

NOTE

If you choose this manual offline backup method, you also have to restore the database files

on the target system manually. For more information, see Restoring the Database Files on the Target

System Manually [page 71].

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.

Procedure

CAUTION

To ensure that no changes are made to the file system during backup, stop the Software

Deployment Manager (SDM).

Proceed as described in the SAP Library at:



2012-03-14 PUBLIC 67/148

help.sap.com/nw70 SAP NetWeaver 7.0 including Enhancement Package 1 SAP NetWeaver 7.0 Library

(including Enhancement Package 1) English SAP NetWeaver Library Administrator’s Guide Technical Operations for

SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle

BR*Tools for Oracle DBA BR*Tools in Action Backup and Database Copy with BR*Tools .

NOTE

If you choose a backup method with BR*Tools, you also have to restore the database files on the

target system with BR*Tools. For more information, see Restoring the Database Files on the Target System

with BR*Tools [page 71].

5.1.3 Preparing the Target System

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

On the Welcome screen, choose the required installation service:

SAP NetWeaver 7.0 including Enhancement Package 1 Software Life-Cycle Options System Copy Oracle

Target System <Central System | Distributed System | High-Availability System> .

CAUTION

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

the database schema and the table space names of the new target system. When installing the

target central instance, database instance, or dialog instance make sure that you enter the

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

The schema names of the source and target system must be identical.

■ When SAPinst prompts for the installation type, choose Homogeneous System Copy (Backup/

Restore).

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

The following message is displayed:

SAPinst now stops the installation. Please proceed as follows:...

2. If necessary, extract the Oracle stage archives manually and install the Oracle Software as described

in the installation documentation for your SAP solution.

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

■ UNIX:

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

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



68/148 PUBLIC 2012-03-14

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

● /oracle/<TARGET_DBSID>/sapreorg

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

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

/oracle/<TARGET_DBSID>/saparch and /oracle/<TARGET_DBSID>/oraarch

<drive>:\oracle\<TARGET_DBSID>\saparch and <drive>:\oracle\<TARGET_DBSID>\oraarch


All directories must be owned by the user ora<target_dbsid>.

To achieve this, enter the following command:

chown ora<target_dbsid>:dba <directory>

End of: UNIX |

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

2. Under Security, choose Advanced.



2012-03-14 PUBLIC 69/148

3. Uncheck Allow inheritable permissions from the parent....

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.

7. Restore the database files on the target system either manually (see Restoring Database Files on the Target

System Manually [page 70]) or with BR*Tools (see Restoring the Database Files on the Target System with

BR*Tools [page 71]), then proceed with SAPinst.

5.1.4 Restoring Database Files on the Target System Manually

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 by copying the listed files from

the source directories to the target directories. For more information, see Creating an Offline Backup

Manually [page 67]

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:


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

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

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


CONTROL.SQL



70/148 PUBLIC 2012-03-14


source: <INSTDIR> target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database


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.

The installation directory of the target system is normally located in the directory:

%programfiles%\sapinst_instdir\NW04S\LM\COPY\ORACLE\SYSTEM\<system_variant>

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 control_files parameter 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:



CONTROL.SQL

source: <INSTDIR> target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/dbs


■ On Windows:



CONTROL.SQL

source: <INSTDIR> target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database


2. Create an Oracle spfile from init<TARGET_DBSID>.ora profile as follows:

SYNTAX

sqlplus /nologconnect / as sysdbacreate spfile from pfile;exit



2012-03-14 PUBLIC 71/148

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

For more information about the required steps and prerequisites, see SAP Note 1003028.

The main prerequisite is that the corresponding BR*Tools logs (BRBACKUP detailed and summary

log, BRARCHIVE summary log) are copied manually from the source to the target system. In addition,

the postprocessing steps mentioned in this SAP Note are performed automatically by SAPinst.

SAP Note 1003028 also comprises information about executing restore and recovery under the

control of BRRECOVER and the exact syntax of BRRECOVER (see section Homogeneous Database Copy).

For more information about BR*Tools, see help.sap.com/nw70 SAP NetWeaver 7.0 Library English

SAP NetWeaver Library Administrator’s Guide Technical Operations Manual for SAP NetWeaver General

Administration Tasks Database Administration Database Administration for Oracle BR*Tools for Oracle

DBA .

4. Shut down the Oracle database instance as follows:

SYNTAX

sqlplus /nologconnect / as sysdbashutdown immediateexit

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 the 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. SAPinst stops before the database instance initialization and asks you to

perform the recovery on the target database. After you have performed recovery and post-recovery

activities you can continue the installation in SAPinst.

This description is not valid for the liveCache system copy.

Advantages

■ You can use existing offline backups.

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

Disadvantage

You can only copy between systems with the same byte order. For more information, see below.

Prerequisites

■ Byte order ‒ little-endian or big-endian



72/148 PUBLIC 2012-03-14



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

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

You can find more information on DBMGUI here:

http://maxdb.sap.com/currentdoc/default.htm Tools Database Manager GUI

■ 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

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

Process

1. Do the following on the source system:

1. If you do not already have a suitable recent complete SAP MaxDB backup, create a complete

data backup using the DBMGUI tool:

DBMGUI Backup Backup Wizard Complete

2. Make the backup medium available on the target host.

2. Do the following on the target system:

1. To install the new system you start SAPinst as follows:

<SAP Product> Software Life-Cycle Options System Copy SAP MaxDB Target System <Central

System | Distributed System | High-Availability System> .

During the installation of the database instance, SAPinst stops in the Perform Database Recovery

screen before database initialization and asks you to perform the data recovery.



2012-03-14 PUBLIC 73/148


http://maxdb.sap.com/currentdoc/default.htm

2. Start the data recovery wizard from DBMGUI

1. Register your database instance in the DBMGUI

2. Check that the database instance is 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.

3. After the restore, check the state of the target database instance and change the database state

to online if it is not already in online state.

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

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

6. After installation is complete, you maintain the database connection for CCMS. For more

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

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

NOTE

● For more information about the system copy procedure, see SAP Notes 193816 and

151603.

● With SQL Server, you can use backup images across the platforms I386, IA64, x64. That

is, you can make a backup on one type of platform and use it on another type.

● You can attach SQL Server 2000 files to SQL Server 2005 but not vice versa.


5.3 MS SQL Server-Specific Procedure

74/148 PUBLIC 2012-03-14




Process1. On the source system, run SAPinst to create an export of the Java central instance [page 35] by choosing the

following installation service on the Welcome screen:

<Your SAP system> Software Life-Cycle Options System Copy MS SQL Server Source System <system

variant> Based on <technical stack>

■ For a central system, choose Database and Central Instance Export.

NOTE

On the SAPinst screen SAP SystemDatabase Export, make sure that you select Use database-

specific tools for the system copy method.

■ For a distributed system, choose Central Instance Export.

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


2. Detach the database files from the source system database or create a backup and copy the files to

the target system.

3. Attach the database files or restore the backup of the source database on the target database server.

4. Run SAPinst to install the target system by choosing the following on the Welcome screen:

<Your SAP system> Software Life-Cycle Options System Copy MS SQL Server Target System <system

variant> <technical stack>

NOTE

■ The target system is installed using the exports from the source system.

■ Choose the installation services in exactly the order they appear. For more information,

see the MS SQL Server installation guide for your SAP system at http://

service.sap.com/installnw70.

■ On the SAPinst screen SAP SystemDatabase, make sure that you select Homogeneous System

Copy (MS SQL Server-specific: Detach/Attach or Backup).End of: Windows | MS SQL Server |


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

a DB2 backup can be used cross-platform within certain limitations (see below), this method is not

limited to the homogenous system copy only.

An SAP system copy with a DB2 database can be also created 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.



2012-03-14 PUBLIC 75/148

http://service.sap.com/installnw70


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 installation on the target system host as described in the installation documentation

for your SAP component. Before starting 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/

installnw70 Installation – SAP NetWeaver Systems

In a Java only or ABAP+Java system, you also have to run an export for the Java Engine to archive SDM

and application-specific file system content.

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

Disadvantages of the Backup Method

■ You cannot change the name of the database schema. The name of the database schema will be

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 V9.1Information Center at http://

publib.boulder.ibm.com/infocenter/db2luw/ v9/topic/com.ibm.db2.udb.admin.doc/

doc/c0005960.htm.

■ If errors occur when restoring the backup on the target system, the complete restore must be

repeated.

Process

1. You perform an online or offline backup.

NOTE

If you use an online backup to copy your system, a roll forward 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.



76/148 PUBLIC 2012-03-14




http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/c0005960.htm



To do so, use the INCLUDE LOGS option of the BACKUP DATABASE command. Note that as of DB2

V9.5, logs are by default included in an online backup.

NOTE

To export the database content for Java, you can also use the database-specific method

(backup/restore).

During the dialog phase, SAPinst asks you in the Database Export dialog box to specify the system

copy method. If you want to use the backup/restore method, choose Use database-specific tools.

2. To create the export directory structure with labels and to archive SDM and application-specific

file system content, you also have to run SAPinst.

On the Welcome screen, choose <Your SAP system> Software Life-Cycle Options System Copy IBM

DB2 for Linux, UNIX, and Windows Source System <system variant> <technical stack> .

Perform the installation options in the given sequence and follow the instructions on the SAPinst

dialogs.

3. To create a target system, run SAPinst on the target system host by choosing the following on the

Welcome screen:

<Your SAP system> Software Life-Cycle Options System Copy IBM DB2 for Linux, UNIX, and Windows

Target System Installation <system variant> <technical stack>

Perform the installation options in the given sequence and follow the instructions on the SAPinst

dialogs. SAPinst prompts you to perform the database restore during the installation phase.

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 cannot change the

connect user either. 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.

4. 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 Enabling database partitioning in

a database in the IBM DB2 V9.1 Information Center at http://publib.boulder.ibm.com/

infocenter/db2luw/v9 /topic/com.ibm.db2.udb.admin.doc/doc/t0004896.htm

5. Restore your database.



2012-03-14 PUBLIC 77/148

http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/t0004896.htm

http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/t0004896.htm

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 DB2 documentation DB2 Command Reference.

NOTE

With a simple restore, you cannot change the name or 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 V9.1 Information Center at https://publib.boulder.ibm.com/infocenter/db2luw/

v9/topic/com.ibm.db2.udb.admin.doc/doc/r0001976.htm.

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 roll forward operation to bring

the database into a consistent state.

You can now continue with the installation.

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


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



78/148 PUBLIC 2012-03-14

https://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/r0001976.htm

https://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/r0001976.htm


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>.tadb6 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.1 Information Center at http://publib.boulder.ibm.com/infocenter/db2luw/ v9/topic/

com.ibm.db2.udb.admin.doc/doc/c0023713.htm.

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



2012-03-14 PUBLIC 79/148



● 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 in the SAP Community

Network at: https://www.sdn.sap.com/irj/sdn/db6 SAP on DB2 for Linux, UNIX, and Windows

Knowledge Center Key Topics Administration

■ Database Administration Using the DBA Cockpit in the SAP Community Network at: https://

www.sdn.sap.com/irj/sdn/db6 SAP on DB2 for Linux, UNIX, and Windows Knowledge Center Key

Topics Administration

■ IBM DB2 V9.1 Information Center at:

http://www.ibm.com/software/data/db2/udb/support/manualsv9.html

■ IBM DB2 V9.5 Information Center at:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/

■ IBM Manuals for DB2 V9.1 at:


■ IBM Manuals for DB2 V9.5 at:

http://www-1.ibm.com/support/docview.wss?rs=71&uid=swg27009727



5.5 IBM DB2 for i Procedure

In an SAP system environment, you can create a homogeneous system copy of a DB2 database using

the SAV/RSTLIB system copy method.

Advantage of the Offline System Copy Method

This method is faster than the database-independent method [page 25].


CAUTION

You can only copy for IBM DB2 for i.

End of: IBM DB2 for i5/OS |

5.6 IBM DB2 for z/OS Specific Procedure

In an SAP system environment, you can create a homogeneous system copy of a DB2 database using

the offline system copy method.


5.5 IBM DB2 for i Procedure

80/148 PUBLIC 2012-03-14

https://www.sdn.sap.com/irj/sdn/db6




http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/


http://www-1.ibm.com/support/docview.wss?rs=71&uid=swg27009727


More Information

For more information about this system copy procedure, see the .PDF file that is attached to SAP

Note 680746. The guide contains all the information necessary to carry out a system copy with DB2

tools.


5.6 IBM DB2 for z/OS Specific Procedure

2012-03-14 PUBLIC 81/148


6 Follow-Up Activities

To finish the system copy of your SAP system:

■ Perform follow-up activities in the source system [page 83]

■ Perform follow-up activities in the target system [page 83]

NOTE

The Java engine is not started automatically. After the target system has been installed and the

follow-up activities have been performed, you have to start the Java engine manually.

6.1 Performing Follow-Up Activities in the Source System

Procedure1. Reschedule your canceled jobs: Tools CCMS Jobs Maintenance (SM37) .

2. Using CCMS, adapt your operation mode timetable to the original status: Tools CCMS

Configuration Operation mode calendar (SM63) .

6.2 Performing Follow-Up Activities in the Target System

NOTE

Before you start the Java engine after the system copy, apply SAP Note 831812 and if necessary,

change the Java VM parameters as described in SAP Note 723909.


NOTE

On IBM i the tool CONFIGJVM can help you to adjust the Java VM parameter of your SAP system.


End of: IBM i5/OS |

6.2.1 Installing the License Key

Once the installation of the target system is completed and the SAP system copy has been imported,

you have to install a new license key.

CAUTION

Before installing the license key, make sure that SAP Note 831812 is applied.


6.1 Performing Follow-Up Activities in the Source System

2012-03-14 PUBLIC 83/148





For more information about ordering and installing the SAP license, see the SAP Library at:

http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SAP Licenses .

6.2.2 Performing Follow-Up Activities for ABAP

Procedure

Actions at Operating System Level

1. Adapt the configuration files at operating system level to meet network and SAP requirements.

2. Adapt additional SAP software components (for example, RFC, CPIC, SAP ArchiveLink) if required.

3. Adapt additional non-SAP software components (for example, archiving systems, monitoring

tools, job schedulers) if required.

4. Adapt backup programs (for example BRBACKUP, BRARCHIVE, BACKINT) if required.

5. Adapt non-SAP directories, file systems, NFS mounts, and so on, if required.

6. Check the SAP parameters of the default and instance profiles.

7. Check your UNIX shell files for special entries.

8. Check crontab or AT jobs.

9. Check operating system files (for example, .netrc, .rhosts).

10. Check operating system printers.

11. Oracle: Adapt the database profiles init<SAPSID>.ora, init<SAPSID>.dba, and

init<SAPSID>.sap.

Actions at Database Level

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. Oracle: Delete all entries from the following tables:

DBSTATHORA, DBSTAIHORA, DBSTATIORA, DBSTATTORA.

4. Oracle: Delete the user OPS$<SOURCE_SAPSID>ADM.

5. Oracle: 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.

Actions at SAP System Level

1. Run an installation check: Administration System administration Administration Installation Check

(transaction SM28).



84/148 PUBLIC 2012-03-14


2. Configure the Transport Management System (transaction STMS). 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.

3. Adapt the transport parameters and transport routes in the Transport Management System (TMS):

a.

1. Choose transaction STMS Overview Systems .

2. Select the system and select the Transporttool tab page.

To adapt the transport routes:

Choose transaction STMS Overview Transport routes .

4. Delete all entries from the following tables: ALCONSEG, ALSYSTEMS, DBSNP, MONI, OSMON, PAHI,

SDBAD, SDBAH, SDBAP, SDBAR.

5. Delete canceled and finished jobs.

Execute ABAP program RSBTCDEL, marking the field delete with forced mode: Tools ABAP Workbench

ABAP Editor (transaction SE38).

6. Adapt all jobs needed in the target system:

1. Copy the old jobs.

2. Modify the new jobs.

3. Delete the old jobs.

7. Check the consistency of the Temporary Sequential Objects (TemSe) by searching for files of TemSe

objects for which no TemSe objects exist:

Administration CCMS Spool TemSe administration (transaction SP12). For more information,

see SAP Note 16875.

8. Adapt the definition of the printers to meet the new system requirements:

■ Device types and character set definitions

■ Spool servers

■ Output management systems (OMS)

9. Delete entries in table DDLOG for buffer synchronization.

10. Synchronize the buffers as described in SAP Note 36283 and adapt the client information for the

logical system.

11. Adapt the RFC destination: Tools Administration Administration Network RFC destinations

(transaction SM59).

12. If you have performed a system copy with R3load, you must set up the trusted and trusting RFC

relationships again.

13. Clean the transactional RFC: Tools Administration Monitor Transactional RFC (transaction

SM58). For more information, see the relevant description in the SAP Online Documentation.

14. Start transaction SECSTORE using Check Entries. If you find erroneous entries with message text System-

dependent data for entry … changed, see SAP Note 816861.

15. Create new operation modes and remove old ones:



2012-03-14 PUBLIC 85/148




1. Create new operation modes and instance definitions.

2. Maintain the time table using the new operation modes.

3. Delete the old operation modes and old instance definitions.

16. Adapt the operation mode time tables (CCMS): Administration CCMS Configuration Operation

mode calendar (transaction SM63).

17. Adapt the instances and profiles (CCMS): Administration CCMS Configuration OP modes/

instances (transaction RZ04).

18. Define or remove the SAP system users: Tools Administration User maintenance Users

(transaction SU01). Also revise the authorizations of the system users.

19. Run transaction SE14 to delete all entries from tables TPFET and TPFHT. These contain information

about changes made to the profile of your source system.

IBM DB2 i: Use the commands CLRPFM R3<SID>DATA/TPFET and CLRPFM R3<SID>DATA/TPFHT.

20. Adapt other CCMS settings (for example, alert thresholds, reorganization parameters of CCMS

table MONI) if required.

21. Delete all entries from table TLOCK, which holds the repair requests from your source system.

22. 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 the SAP

Online Documentation (SAP Web Application Server System Administration Application Data Archiving and

Reorganization) .

23. Redefine database actions (backup, update statistics, and so on) if you have used the DBA calendar

in the source system (transaction DB13).

24. Check logon groups and assignment of application servers to logon groups (transaction SMLG).

25. Check the connection to SAPNet - R/3 Frontend (transaction OSS1).

26. Check self-defined external commands (transaction SM69).

27. Check entries of the following tables in all relevant systems:

■ TXCOM (transaction SM54)

■ THOST (transaction SM55)

28. Check the logical system names. For more information, see Preparations [page 19]. 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.

BI customers: If you have copied a BI (formerly BW) system, read SAP Note 325525.

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

30. Check if you can delete clients that will no longer be used in the target system (transaction

SCC5).



86/148 PUBLIC 2012-03-14




31. Check the contexts and segments of remote application servers for the SAP Monitoring

Infrastructure if required (transaction RZ21).

32. Configure the domain controller in the Transport Management System (TMS) by using

transaction STMS.

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

34. ABAP Program Loads

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. This might,

however, reduce production system performance. To avoid this, you can use transaction SGEN to

generate the missing loads.

Load generation requires a large amount of system resources. Therefore, it makes sense to schedule

the generation job to run overnight.

For a detailed description of the features, see the online documentation in transaction SGEN by

choosing Information on the SAP Load Generator, or in the Job Monitor by choosing Job Monitor.

35. 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. 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. Program RS_BW_POST_MIGRATION performs necessary modifications on database-

specific objects (mainly BI objects).

NOTE

You are required to perform the step independent of whether your target system is a BI or

not.

Checking the Target System

The following actions are suitable for checking the consistency of the target system:

1. Perform initial consistency check (transaction SM28).

2. Check the system log on all application servers (transaction SM21).

3. Check the consistency of the database (transaction DB02).

4. Perform server check (transaction SM51).

5. Test transactions frequently used by the customer.



2012-03-14 PUBLIC 87/148

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

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

8. CO customers: Run the report group 1SIP and compare the results to those gained on the source

system before the system copy.

Replacing the PSEs in the Target System

Replace all existing PSEs in the target systems with new ones, which contain the new system's

information. Proceed as follows:

1. In your ABAP system, call transaction STRUST.

2. Proceed as described in the documentation Creating or Replacing a PSE in the SAP Library at:


SAP NetWeaver Library SAP NetWeaver by Key Capability Security System Security System Security for

SAP NetWeaver AS ABAP only Trust Manager .

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

6.2.3 Performing Follow-Up Activities for Java

Depending on the usage types or software units contained in your target system, you have to perform

general and usage type or software unit-specific configuration steps:

■ General Follow-Up Activities [page 89]

■ Usage Type or Software Unit-Specific Follow-Up Activities [page 90]



88/148 PUBLIC 2012-03-14


6.2.3.1 General Follow-Up Activities

You have to perform the following activities for all usage types or software units of the copied SAP

system.

CAUTION

Make sure you applied SAP Note 831812, before you use the GUI Config Tool to change Java

parameters.

6.2.3.1.1 Configuration Steps for the SAP Java Connector

You need to perform these post-installation steps for a copied Java system that includes a component

that has to connect to an ABAP back end using the SAP Java Connector (SAP JCo), for example SAP

Business Warehouse or SAP Enterprise Portal.

Procedure

1. Log on to the Visual Administrator as an administrator.

2. On the launch path on the left, choose Cluster Server <server name> Services JCo RFC

Provider .

3. On the right, choose Runtime and select the RFC destination that you use for the connection to the

back end.

4. Maintain the required parameters for the RFC destination and repository.

5. Remove the old JCo-destination that was copied from the source system.

6. Restart the Java server and the component.

6.2.3.1.2 Generating Public-Key Certificates

Reconfiguring the Public-Key Certificates

After system copy, the public key certificates are wrong on the target system. You need to reconfigure

them as described at the SAP Library at:

help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key

Capability Security User Authentication and Single Sign-On Authentication on the AS Java Configuring

Authentication Mechanisms Using Logon Tickets for Single Sign-On Configuring the Use of Logon Tickets Replacing

the Key Pair to Use for Logon Tickets .

Importing the Public-Key Certificates

You also need to import this public-key certificate on any systems that are to accept logon tickets from

the AS Java system. For more information, see the SAP Library at:

help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key

Capability Security User Authentication and Single Sign-On Authentication on the AS Java Configuring



2012-03-14 PUBLIC 89/148


Authentication Mechanisms Using Logon Tickets for Single Sign-On Configuring the Use of Logon Tickets Configuring

SAP Web AS ABAP to Accept Logon Tickets from the J2EE .

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

6.2.3.2.1 Application Server Java (AS-Java)

6.2.3.2.1.1 AS Java: SAP Knowledge Warehouse

After the system copy, you have to configure the Internet Knowledge Servlet (IKS) to connect to the

new ABAP back-end. For more information, see Configuring the Access to Knowledge Warehouse Content from

SAP Internet Knowledge Servlet in the documentation Installation Guide - SAP NetWeaver 7.0 Including Enhancement

Package 1 on <OS>:<database> at http://service.sap.com/installNW70 Enhancement Package

Installation on Existing SAP Systems .

Only valid for: EP Core (EPC) |

6.2.3.2.2 EP Core (EPC)

6.2.3.2.2.1 EPC: Portal

If trust between a portal and any other system is required, then you need to replace certificates and re-

establish trust with the newly copied system on which the portal is installed. For more information,

see Generating Public-Key Certificates [page 89].

If you have more than one portal in your landscape and the portals share content via a federated portal

network (FPN), refer to SAP Note 1080080 for more information about post-system copy configuration

steps.End of: EP Core (EPC) |

Only valid for: Enterprise Portal (EP) |

6.2.3.2.3 Enterprise Portal (EP)

6.2.3.2.3.1 EP: Knowledge Management and Collaboration

After the system copy, the Knowledge Management and Collaboration (KMC) target system still has

access to the same data as the original source system. If the source and target system have write access



90/148 PUBLIC 2012-03-14



to the same data, this results in serious inconsistencies in both systems. For this reason, it is essential to

prevent both systems from using the same data.

Critical items that are accessed by both systems are, for example:

■ Indexes for search and classification (TREX)

■ Data in external repositories, for example, on file system shares

■ Data on groupware servers

Procedure

To prevent source and target system from working with the same data, reconfigure the following

components on the target system:

■ TREX

■ Repository Managers

■ Services

■ Collaboration

The tables below summarize the configuration steps for each of the components and specify where

you can find more information.

TREX

After the system copy, the target system is still connected to the same TREX installation as the source

system. For this reason you need to install a new instance of TREX and connect it to the target system.

CAUTION

While KMC is still connected to the old TREX installation, do not delete any indexes, otherwise

they will also be deleted on the source system.

Task Detailed Information

For the target system, install a new instance of TREX. http://service.sap.com/installNW70 InstallationInstallation - Standalone Engines & Clients Installation -

Standalone Engine - NW 7.0 TREX Single Host

On the target system, set up the connection to the newly installed TREX system.

http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability

Information Integration Search and Classification (TREX)TREX Configuration Post-Installation Configuration

Client Side Java Application (HTTP Connection) Specifying the Address of the TREX Name Server

On the target system, delete old indexes that belong to the source system. Define and generate new indexes for the target system.

NOTE

The prerequisite for this step is that all repository managers are configured correctly for the target system.


Information Integration Knowledge Management Administration Guide System Administration System

Configuration ‘Index Administration’ iView



2012-03-14 PUBLIC 91/148




Repository Managers

Ensure that the target system does not have write access to the same repositories as the source system.


On the target system, check the configuration of all external and internal repository managers that have write access to the same data as the source system. Make sure that the source and target system do not have write access to the same data. For example, check the repository manager settings for: ■ CM FSDB or CM DBFS repositories ■ Simple File System repositories

http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Information Integration Knowledge Management

Administration Guide System Configuration Content Management Configuration Repositories and Repository Managers External Repositories

Services


Content Exchange If content exchange is in use, the configuration on the source and target system is identical. However, it does not make sense to have the same content exchange procedures configured twice. For this reason, delete the configuration on the target system and, if required, set up a new configuration. Run a cleanup file to remove the existing configuration on the target system: ■ Download the cleanup file attached to SAP

Note 1238351. Note that the cleanup procedure automatically creates a new ID for a syndicator and subscriber.

■ Import the cleanup file into the target portal. To do this, choose System Administration System Configuration Knowledge Management Content Management and then, on the right, choose

Actions Import . ■ If required, configure new content exchange

settings on the target system.


Information Integration Knowledge ManagementAdministration Guide System Configuration Content

Management Configuration Global Services Content Exchange Service

URL GeneratorOn the target system, check the settings for the Host and Alternative Host parameters.

http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Information Integration Knowledge Management Administration Guide System Configuration

Content Management Configuration Global Services URL Generator Service

System Landscape: On the target system, delete the old system IDs that belong to the source system.

Log on to the Portal and choose System AdministrationSystem Configuration Knowledge Management Content

Management Global Services System Landscape DefinitionsSystems Content Management Systems .

Scheduler Service: If the target system is an SAP Java cluster, then you must assign scheduler tasks to the new system IDs of the target system. After the system copy, tasks are still assigned to the IDs of the source system.

http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Information Integration Knowledge Management Administration Guide Minimal Configuration



92/148 PUBLIC 2012-03-14






Task Detailed Informationfor Knowledge Management Cluster Only: Assigning Tasks to Nodes

Collaboration


On the target system, adapt the room back-end properties server address, server port, and Web protocol.


People Integration Collaboration Administration GuideBasic Configuration Defining Back-end System Properties for

Room URLs

On the target system, generate a new index to enable search operations in the content of rooms.


People Integration Collaboration Administration GuideVirtual Rooms Configuration of Search Functions for Rooms Configuration of the Search for Room Content

On the target system, check the properties of the roomsearch object. Make sure that the parameter Use TREX is set.


People Integration Collaboration Administration GuideVirtual Rooms Configuration of Search Functions for Rooms Configuration of the Search for Rooms

On the target system, configure the connection to the required groupware server.


People Integration Collaboration Administration GuideBasic Configuration Configuring E-Mail Connectivity

If the e-mailing service is active on the source system, but is not required on the target system, you need to delete the e-mail transport. After deletion of the transport, e-mailing is disabled. E-mails will no longer be automatically sent, for example, when members are excluded from a room or documents are updated and deleted.


People Integration Collaboration Administration GuideGroupware Groupware Framework Installing and

Configuring E-Mail Connectivity Configuration StepsCreating an E-Mail Transport

On the target system, reconfigure the ServerName and ServerPort for the application sharing server.


People Integration Collaboration Administration GuideReal-Time Collaboration Configuring Real-Time

Collaboration Configuring the Application Sharing Server (RTC) Setting Application Sharing Server Parameters (RTC)

End of: Enterprise Portal (EP) |



2012-03-14 PUBLIC 93/148







Only valid for: BI Java |

6.2.3.2.4 Business Intelligence Java Components (BI Java)

You have to perform the following follow-up activities for usage type BI Java:

6.2.3.2.4.1 Business Intelligence (BI Java)

Follow the instructions in this section if the entries for source system connection have not been copied

to the services file of your target system.

Prerequisites

You have performed a system copy that includes SAP Business Warehouse (SAP BW).

Procedure

Adding Entries to the Services File

You have to do the following to add the entries to the services file:

If your target host runs on a UNIX platform

1. Log on to your target system as user root.

CAUTION

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

or database.

2. Edit the file /etc/services.

3. Add the entries for your source system connection, for example sapgw47 3347.

If your target host runs on a Windows platform or on IBM i

1. Log on to your target system as a member of the local administration group.

2. Edit the file <WindowsDirectory>\system32\drivers\etc\services.

3. Add the entries for your source system connection, for example sapgw47 3347.

6.2.3.2.4.2 Basic Configuration for Usage Type BI Java

Procedure

1. BI-Integrated Planning

Call transaction SPRO and choose SAP NetWeaver Business Intelligence BI-Integrated Planning .

Follow the instructions for the following step: Define JCo Destination.

2. Integration into the Portal



94/148 PUBLIC 2012-03-14

Call transaction SPRO and choose SAP NetWeaver Business Intelligence Settings for Reporting and

Analysis BEx Web Integration into the Portal .

Follow the instructions for the following steps:

1. Create RFC Destination in J2EE Engine

2. Import BI Certificate to the Portal

3. Maintain Portal Server Settings for the Portal

4. Create RFC Destination for the Portal

5. Import Portal Certificate to BI SystemEnd of: BI Java |

Only valid for: Process Integration (PI) |

6.2.3.2.5 Process Integration (PI)

You have to perform the following follow-up activities for usage type PI:

NOTE

The following changes reflect exactly the regular configuration steps for usage type PI. For more

detailed instructions about how to change the values, see the SAP Library at:


SAP NetWeaver Library Technology Consultant's Guide Business Process Management Configuration of

Usage Type Process Integration .

6.2.3.2.5.1 PI: System Landscape Directory

Procedure

NOTE

For more information about how to perform the individual tasks, see the documentation in the

SAP Library at:


SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key

Capability Software Life Cycle Management System Landscape Directory Configuring Systems to Connect to

SLD .

The respective sections are stated below.

■ Maintain the SLD connection parameters:

Call transaction SLDAPICUST and change the value for the host name as well as for the port number.

For more information, see the section Connection Between Web AS ABAP Systems and SLD SLD

Application Programming Interface for ABAP-Based Systems Creating an HTTP Destination for the SLD ABAP

API on the ABAP Side .



2012-03-14 PUBLIC 95/148



■ Maintain the ABAP connection:

Call transaction RZ70 and change the value for the host and the gateway service in the Transport

Information group box. This value should be predefined by the value entered before in transaction

SLDAPICUST.

For more information, see the section Connection Between Web AS ABAP Systems and SLD Configuring

the SLD Data Supplier: Default Settings .

■ Configure the SLD Data Supplier Service in the Visual Administrator:

Change the value for the host as well as for the HTTP port number.

For more information, see the section Connection Between Web AS Java Systems and SLD Setting Up the

SLD Data Supplier for J2EE-Based Systems .

NOTE

For information on how to perform the following tasks, see the Post-Installation Guide SLD of SAP

NetWeaver 7.0 at http://service.sap.com/installNW70 Configuration . The respective

sections are stated below.

■ Maintain server settings in the SLD:

Change the value for the object server.

For more information, see the section Configuring Server and Persistence Parameters.

■ Configure the SLD Bridge:

Change the value for the gateway server as well as for the gateway service.

For more information, see to the section Configuring the SLD Bridge.

6.2.3.2.5.2 PI: Integration Server

Procedure

1. Maintain the logical system:

Call transaction SCC4 to maintain the logical system information.

2. Maintain the technical system and the business system for the Integration Server:

In the SLD, maintain a product for the technical system. Create a business system for the Integration

Server and maintain the logical system information.

3. Create RFC destinations in the ABAP environment:

Call transaction SM59, navigate to destination INTEGRATION_DIRECTORY_HMI, and change the value

for the target host as well as for the HTTP port number.

4. Maintain RFC destination in the ABAP and Java environment:

For the following connections, change the value for the gateway host as well as for the gateway

service on the ABAP side and in the Visual Administrator. In the Visual Administrator, also change

the value for the application host name and the system number. Change the value for the gateway



96/148 PUBLIC 2012-03-14


host, as well as for the gateway service on the ABAP side, and the value for the PI host in the Visual

Administrator for the following connections:

Connection Description

AI_RUNTIME_JCOSERVER Used to connect the ABAP part to the Java part of the Integration Server

LCRSAPRFC Used to connect the Integration Server to the SLD.

SAPSLDAPI

5. Create HTTP destination pmistore in the Java environment:

Change the value for the host and port number in the destination URL.

6. Maintain the pipeline to the Integration Server:

Change the pipeline to the Integration Server by running transaction SXMB_ADM.

7. Maintain Prefix Numbers for Workflow and Organizational Management.

Call transaction SWF_XI_CUSTOMIZING, select Maintain Definition Environment Maintain Prefix

Numbers , and choose Perform Automatic Workflow Customizing (F9).

8. Maintain RFC Server Groups.

Call transaction RZ12 and change the instance name under Group assignment.

9. Maintain RFC destination AI_MONITORING_SERVER in the ABAP environment.

This destination only needs to be maintained if performance data collected by Process Monitoring

Infrastructure is displayed in the Runtime Workbench.

10. Refresh host name buffer.

After you have maintained the required RFC destinations, the host name buffer needs to be reset.

Call transaction SM51 and choose Goto Host Name Buffer Reset Entire System .

6.2.3.2.5.3 PI: Changes in the Exchange Profile

Procedure

1. Maintain server settings for the exchange profile connection:

Change the value for the host name as well as for the instance number.

CAUTION

Note that it is essential that you change the connection for the following steps of this section.

Without adjusting the connection parameters, all changes in this section affect the exchange

profile of the source system.

2. Change all parameters pointing to the source system:

The following parameters contain the host name for the connection of components. All

parameters pointing to the source system must be changed to reference the target system.

For more information about parameters, refer to Exchange Profile Parameters in the PI configuration

documentation in the SAP Library at:



2012-03-14 PUBLIC 97/148


SAP NetWeaver Library Technology Consultant's Guide Business Process Management Configuration of Usage

Type Process Integration .

Parameter Description

com.sap.aii.connect.cr.name Contains the host name of the component repository server.

com.sap.aii.connect.cr.httpport Contains the HTTP port number of the component repository server.

com.sap.aii.connect.directory.name Contains the host name of the directory server.

com.sap.aii.connect.directory.httpport Contains the HTTP port number of the directory server.

com.sap.aii.connect.directory.httpsport Contains the HTTPS port number of the directory server.

com.sap.aii.connect.directory.rmiport Contains the RMI port number of the directory server.

com.sap.aii.connect.integrationserver.name Contains the host name of the Integration Server.

com.sap.aii.connect.integrationserver.httpport Contains the HTTP port of the J2EE Engine of the Integration Server. Used by the XI integration directory to connect to the XI runtime.

com.sap.aii.connect.integrationserver.httpsport Contains the HTTPS port of the J2EE Engine of the Integration Server. Used by the XI integration directory to connect to the XI runtime.

com.sap.aii.connect.integrationserver.r3.sysnr R3 system number of the NetWeaver Application Server on which the Integration Server runs.

com.sap.aii.connect.integrationserver.r3.httpport Contains the HTTP port number of the Integration Server.

com.sap.aii.connect.landscape.name Contains the host name of the landscape directory server.

com.sap.aii.connect.landscape.httpport Contains the HTTP port number of the landscape directory server.

com.sap.aii.connect.landscape.httpsport Contains the HTTPS port number of the landscape directory server.

com.sap.aii.connect.repository.name Contains the host name of the repository server.

com.sap.aii.connect.repository.httpport Contains the HTTP port number of the repository server.

com.sap.aii.connect.repository.httpsport Contains the HTTPS port number of the repository server.

com.sap.aii.connect.repository.rmiport Contains the RMI port number of the repository server.



98/148 PUBLIC 2012-03-14


Parameter Description

com.sap.aii.connect.rwb.name Contains the host name of the Runtime Workbench (RWB).

com.sap.aii.connect.rwb.r3.sysnr R3 system number of the NetWeaver Application Server on which the Runtime Workbench runs.

com.sap.aii.connect.rwb.httpport Contains the HTTP port number of the Runtime Workbench.

com.sap.aii.connect.rwb.httpsport Contains the HTTP port number of the Runtime Workbench.

com.sap.aii.ib.server.connect.webas.r3.ashost Connection from Java stack to ABAP stack of the NetWeaver Application Server.

com.sap.aii.ib.server.connect.webas.r3.sysnr Connection from Java stack to ABAP stack of the NetWeaver Application Server.

com.sap.aii.rwb.server.centralmonitoring.r3.ashost Application server of the NetWeaver Application Server on which the central PMI, the central CCMS, and the central alert server run.

com.sap.aii.rwb.server.centralmonitoring.r3.sysnr System number of the NetWeaver Application Server on which the central PMI, the CCMS, and the alert server run.

com.sap.aii.rwb.server.centralmonitoring.httpport HTTP port of the NetWeaver Application Server (ABAP part) on which the central PMI, the CCMS, and the alert server run.

6.2.3.2.5.4 PI: Refresh Caches

Procedure

1. Restart the Java engine:

To initialize exchange profile caches and SLD caches, restart the Java engine.

2. Refresh the CPACache:

Since the restart of the Java server only leads to a delta cache refresh for the CPACache, a full

CPACache refresh must be enforced by executing the following URL:

http://<host>:<Java-Port>/CPACache/refresh?mode=full

NOTE

To call the CPACache refresh URL, you have to enter user PIDIRUSER and the corresponding

password you entered during the installation.

3. Refresh the XI Cache:

Refresh the XI Cache by running transaction SXI_CACHE.



2012-03-14 PUBLIC 99/148

6.2.3.2.5.5 PI: Switching Addresses

Procedure

The newly installed target IS 7.0 resides at a new network address. If you want to reconnect business

systems, you have to make address changes at several locations to account for this change.

The following actions are performed automatically:

■ Communication from the target IS 7.0 to business systems is set due to copying BI content, which

contains the communication channels for these business systems.

The following sections contain a detailed description of all necessary manual address changes.

Connecting Business Systems to the SLD of the Target System

Business systems with an Integration Engine require a connection to the SLD server of the target system

to obtain their name from the SLD. The business system name is used in the header of the message sent

to the Integration Server. The connection to the SLD is established by creating an RFC destination (as

described below) and calling a registered server program, which is defined on the J2EE JRFC engine of

the Integration Server. The server program is called with the HTTP address as a parameter that is

maintained with transaction SLDAPICUST.

NOTE

For more information about performing the individual tasks, see the configuration information

for PI at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1)

English SAP NetWeaver Library Technology Consultant's Guide Business Process Management Configuration

of Usage Type Process Integration Configuration of Business Systems with an Integration Engine Connecting to the

System Landscape Directory .

1. Use transaction SLDAPICUST in the business system to define the SLD access data. This data consists

of the host and port of the SLD as well as a user (PIAPPLUSER) and password. You can use the entries

that you maintained on your Integration Server.

2. Change all RFC destinations on your business system. They use the same registered server program,

which is defined as part of the JRFC engine settings of the Java engine on the SLD host. This means

that all business systems can use the same server program ID (SAPSLDAPI_UNICODE or

SAPSLDAPI_NONUNICODE) for their RFC destinations LCRSAPRFC and SAPSLDAPI.

3. You must also change the RFC destinations in:

■ all business systems (enter the new Integration Server and, if necessary, adjust the roles)

■ all technical adapters

■ file SLDaccessor.properties in directory /tech_adapter/BaseConfiguration

4. Enter the gateways in file etc/services.

5. For Unicode business systems (program ID SAPSLDAPI_UNICODE), the Unicode indicator is set in

the JRFC engine settings. For non-Unicode business systems (program ID

SAPSLDAPI_NONUNICODE), the Unicode indicator is not set.



100/148 PUBLIC 2012-03-14


Maintaining System Connections and Destinations

If the host name and port of your Integration Server have changed after the system copy, you have to

maintain the destinations and connections if you want to reconnect Integration Engines and adapters.

For information on how to perform the individual tasks, see the configuration information for PI in

the SAP Library at:


NetWeaver Library Technology Consultant's Guide Business Process Management Configuration of Usage Type Process

Integration .

The respective sections are stated below.

■ Update the HTTP destinations:

Update the HTTP destination that points from the Integration Engines (business systems) to the

PI Integration Server. For more information, see the section Configuration of Business Systems with an

Integration Engine in the configuration information.

■ Optional: Update the destinations to IS 7.0 for receiver preidentification:

In the Integration Engine, update RFC destination AI_INTEGRATION_SERVER. For more

information, see the section Configuration of Business Systems with an Integration Engine in the configuration

information.

■ Optional: Update the destinations to IS 7.0 for maintenance of value mapping table:

In the Integration Engine, update RFC destination AI_INTEGRATION_SERVER. For more

information, see the section Configuration of Business Systems with an Integration Engine in the configuration

information.

■ Reintegrate business systems using the IDoc adapter of the source system:

In the sending system, update the RFC destination to the Integration Server. For more information,

see the section Integration of Business Systems Integration Using the IDoc Adapter in the configuration

information.

■ If you made the configuration settings Maintain Services for the Integration Server in transaction

SICF, make sure these settings are also maintained in the newly installed target system.

For the following steps, see the SAP Library at:


NetWeaver Library SAP NetWeaver by Key Capability Process Integration by Key Capability SAP NetWeaver

Exchange Infrastructure Runtime Connectivity and then the sections stated below:

■ Change the system connections for the RFC adapter:

In all application systems, change the program ID RFC destination in transaction SM59 to the new

program ID defined in your sender channels in the section RFC adapter. For more information,

see the section Adapters RFC Adapters .

■ Integrate business systems using the Plain J2SE Adapter Engine:

Update the URL of the HTTP destination to the Integration Server in the sender adapters. For more

information, see the section Adapter Engine Plain J2SE Adapter Engine .



2012-03-14 PUBLIC 101/148



6.2.3.2.5.6 PI: Connection Checks

Procedure

1. Checks in SLDCHECK:

Call transaction SLDCHECK on the Integration Server.

2. Checks in SPROXY:

Call transaction SPROXY, choose Goto Connection Test , and execute all checks.End of: Process Integration (PI) |

Only valid for: Development Infrastructure (DI) |

6.2.3.2.6 Development Infrastructure (DI)

You have to perform the following manual steps on the target system after moving an SAP system with

usage type Development Infrastructure (DI). The assumption here is that all components (DTR, CBS,

CMS, SLD, and name server) were on a single host before the move and will remain on a single host

after the move.

Procedure

1. If you are using an LDAP server for user management, it should be running to ensure that all the

users that were created when the Development Infrastructure (DI) was on the source system will

still be valid after the move to the target system.

2. Check the Java Engine Configuration:

■ Set MaxHeapSize and other engine parameters to the recommended values.

Refer to Installation Guide for SAP NetWeaver 7.0 including Enhancement Package 1 Java on

<OS>:>Database> (including usage type DI) for details.

■ Only valid for: MaxDB |

If your database is SAP MaxDB:,

1. Upgrade it to at least version 29.

2. Set the JOIN_OPERATOR_IMPLEMENTATION parameter to IMPROVED (setting this value is only

possible using the DB-WebUI in SAPMMC).

3. Restart the database.End of: MaxDB |

■ For general recommendations for the configuration of the Development Infrastructure

Servers, refer to SAP Note 889038.

3. Design Time Repository (DTR):

■ Redeploy the database schema.

This is necessary to re-create the missing metadata for the database views in the dictionary.

Otherwise OpenSQL cannot see the database views.



102/148 PUBLIC 2012-03-14


The database schema of the DTR server is part of the NWDI SCA. This is the SCA that you

have downloaded from http://service.sap.com/swdc to deploy the NetWeaver

Development Infrastructure (NWDI).

To only deploy this database schema you have to extract the SCA file. You can do this by

appending .zip to the filename. Then you can use a normal archive tool like WinZip. Under

the subfolder DEPLOYARCHIVES, you can find the SDA sap.com~tc~dtr~dbschema.sda for the

database schema. This SDA must be deployed using the Software Deployment Manager (SDM).

NOTE

During deployment, use the option Update deployed SDAs/SCAs that have any version. This

option can be set in the Deployment tab on SDM.

■ Restart DTR server.

■ Change the URL of the name server (in name server configuration page in Web UI: http://

<dtrhost>:<port>/dtr/system-tools/administration/NameServerConfiguration) if you

intend to use a different name server for the moved DTR instance, or if the name server was

also moved.

■ Perform an Update Statistics (30%) on the database.

Only valid for: MaxDB |

NOTE

If your database is SAP MaxDB, you can use the database manager to update the database

statistics.

End of: MaxDB |

4. System Landscape Directory (SLD):

If you used the SLD on the source host as the name server, you need to change the CimomURL

to point to the target host. To do so, proceed as follows:

1. Log on to the SLD as administrator.

2. Choose Administrator Content Maintenance , then under Class, choose System Landscape Directory

<your local SLD> .

3. Under CimomURL, change the host to target host.

CAUTION

Do not change the ObjectServer attribute.

5. Component Build Service (CBS):

The service properties JDK_HOME_PATHS, BUILD_TOOL_JDK_HOME, rootFolder, and

threadPoolSize have to be adjusted according to the hardware and software configuration of the

new system.

Refer to Installation Guide for SAP NetWeaver 7.0 including Enhancement Package 1Java on <OS>:>Database>

(including usage type DI) for details about these parameters.

6. Change Management Service (CMS):



2012-03-14 PUBLIC 103/148

http://service.sap.com/swdc

The main steps in CMS involve resetting the fields containing URLs to other components (such

as DTR, CBS, SLD).

■ If CMS has not been configured yet, proceed as follows:

1. Copy the folder /usr/sap/trans/EPS/in/CMS<host><SID>, including its content, to the

target host.

2. Rename the folder to the new host value and new SAPSID (if changed).

3. Make sure that the engine user (<SID>adm) has write permissions in the copied folder.

■ If CMS has been configured and you have used it already, proceed as follows:

1. For the domain (in the Domain Data tab):

1. Change the SLD URL to point to the target host.

2. Change the CMS URL to point to the target host.

3. Change the transport directory to the appropriate directory on the new CMS (target

host).

4. Save the domain. You should see a status message that the data was saved successfully.

5. Update CMS by choosing Update CMS. You should see a status message that the CMS

update was successful.

2. Copy the contents of the transport directory of the old CMS (source system) to the

transport directory of the new CMS (target system). The transport directory is configured

in the domain (refer to Domain Data tab page).

3. For each track (in the Track Data tab page):

1. Change the CBS and DTR URLs.

2. For each runtime system that is defined, change the runtime system configuration

to point to the appropriate host (of the target runtime system).

If this has not changed, leave the fields unchanged.

3. Save the track definition.

You should see a status message that the data was saved successfully.

4. Restore system state (of the DEV system). This will place the software components

(SCs) into the import queue of this system.

5. Import these SCs. After the import is finished, you should see a status for each SC.

7. IDE:

■ Change the SLD URL in the preference page of the SAP NetWeaver Development Studio (under

Java Development Infrastructure Development Configuration Pool ).

This should now point to the new SLD on the target system.

■ Import the development configuration that you used earlier for development.

Now you are ready to begin the development with you new (relocated) Development

Infrastructure (DI).

8. Verification Steps (optional)



104/148 PUBLIC 2012-03-14

The following steps are optional and verify that the Development Infrastructure (DI) is fully

functional after the move:

1. Log in to the DTR (using the browser) for all defined users and browse the repository.

2. Using IDE, create a new development component (DC), check it in and activate it:

■ The activation should be successful.

■ The name of the development component (DC) must be reserved on the name server.

3. Release the activity created above (from the transport view in the IDE):

The activity (change request) should appear in the import queue of the CONS system of the track.

4. Import the change request into the CONS system (from the CMS Transport Studio).

5. Assemble a new version of your software components (SCs) in one of the tracks.End of: Development Infrastructure (DI) |

6.2.3.2.7 Mobile Infrastructure (MI)

6.2.3.2.7.1 MI: Clean Up the Target System

After the system copy, the download links for the mobile component's installation files still point from

the target system's ABAP server component to the source system's J2EE server component.

ProcedureIn the SAP NetWeaver Mobile Administrator, under Deployment Configuration, choose Update deployed SDAs/

SCAs that have any version to redeploy all mobile components via the SDM.

Only valid for: SAP ERP | Self Services (XSS) |

6.2.3.2.8 Self Services (XSS)

6.2.3.2.8.1 Re-Creating the JCo Destinations

ProcedureYou must re-create the JCo destinations as described in the documentation Creating JCo Destinations in

the SAP Library at:


NetWeaver Library SAP NetWeaver by Key Capability Application Platform (SAP Web Application Server) Java

Technology in SAP Web Application Server Java Development Manual Developing User Interfaces Web Dynpro

Advanced Web Dynpro Technologies Web Dynpro Content Administrator .


Only valid for: SAP ERP |

6.2.3.2.8.2 ERP-XSS: SAP WebDynpro Applications

SAP WebDynpro applications that use “Adaptive RFC” (a Web Dynpro technology based on JCo and

AII), require that their “Destinations ”(back-end connections) are configured with the Web Dynpro



2012-03-14 PUBLIC 105/148



Content Administrator “Admin” (a tool specific to Web Dynpro). The configuration data is stored in

the System Landscape Directory (SLD) where it is associated with the Java Cluster that the Content

Admin runs on. Some additional data is stored in the secure storage of the Java Cluster itself. For both

reasons, the destinations have to be configured for each Java Cluster individually and currently cannot

be transported.

For more information, see the documentation in the SAP Library at:

http://help.sap.com/nw70 SAP NetWeaver Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Application Platform Java Technology Java Development

Manual Core Development Tasks Developing User Interfaces Web Dynpro.

NOTE

Make sure you use the correct host and port in the portal under System administration System

configuration Systems SAP_Webdynpro .

End of: SAP ERP |

End of: SAP ERP | Self Services (XSS) |

Only valid for: SAP CRM;SAP ERP | CRM Java Components (JCRM);Extended E-Selling Components (XECO) |

6.2.3.2.9 CRM Java Components (JCRM) / Extended E-Selling Components (XECO)

Only valid for: SAP CRM;SAP ERP | CRM Java Components (JCRM);Extended E-Selling Components (XECO) |

6.2.3.2.9.1 Sub-Component Workforce Deployment AS/CS

The XCM parameters for Workforce Deployment Application and Calculation Services (WFD AS/CS)

point to an SAP CRM or SAP ERP back-end system. The WFD Calculation Services also have an XCM

parameter cs.http.port that points to the HTTP port of the Java instance it was installed on.

If the system copy involves copying the SAP CRM back-end system, you need to adjust the

cs.jco.xxxxx XCM parameters (which point to the SAP CRM back-end system) in the target system.

If the system copy involves copying the Java engine, you need to adjust the cs.http.port XCM

parameter for WFD Calculation Services in the target system. It should point to the HTTP port of the

target Java engine.

Procedure

Configure XCM parameters for WFD Application Services:

http://<J2EEHOST>:<>//wfd/admin/xcm/init.do.

Configure XCM parameters for WFD Calculation Services:

http://<J2EEHOST>:<J2EEHTTPPORT>//wfdcs/admin/xcm/init.do

End of: SAP CRM;SAP ERP | CRM Java Components (JCRM);Extended E-Selling Components (XECO) |

End of: SAP CRM;SAP ERP | CRM Java Components (JCRM);Extended E-Selling Components (XECO) |



106/148 PUBLIC 2012-03-14


Only valid for: SAP CRM | MapBox (MBX) |

6.2.3.2.10 MapBox

You need to proceed as follows to restore the configuration of the CRM Java component MapBox on

the target system.

Procedure

1. Shut down the Java engine.

2. Copy the following files to the relevant directories:

1. Copy the files mapboxmeta.xml, mapboxmeta.xsl, and xmlprofiles.xml to the directory

<J2EE_root>/cluster/server/.mapboxmeta. You can find these files at the same location on

the source system.

2. Copy the file coordserver.cfg to the <J2EE_root>/cluster/server directory.

3. If you want to have the smoketest directory on the target system, then you need to copy the

smoketest directory too.

3. Start the Java engine and MapBox from the URL as described in Post-Installation Steps for MapBox in

the documentation Installation Guide — SAP CRM 5.0 on <OS> <ABAP+Java|Java> at http://

service.sap.com/crm-inst .

Result

You have restored the configuration for MapBox on the target system.End of: SAP CRM | MapBox (MBX) |

Only valid for: SAP SRM | SRM Live Auction Cockpit (SRMLAC) |

6.2.3.2.11 SRM Live Auction Cockpit (SRMLAC)Only valid for: SAP SRM | SRM Live Auction Cockpit (SRMLAC) |

6.2.3.2.11.1 SRM Live Auction Cockpit (SRMLAC)

To facilitate customization, the resource files for the Live Auction Cockpit applet are packaged

separately from the web application itself. In order for the applet to retrieve its resources, the web server

must make the resource files accessible using HTTP. This is achieved by creating a web alias for the

directory that contains the resources. Without this alias, the applet does not load properly.

Prerequisites

The J2EE Engine is running.



2012-03-14 PUBLIC 107/148

http://service.sap.com/crm-inst

http://service.sap.com/crm-inst

Procedure

1. Open the Java engine administration tool.

EXAMPLE

Windows (and IBM i), go to:

<T_INSTDIR>\usr\sap\<sapsid>\<instancenumber>\j2ee\admin\go.bat

UNIX, go to:

<T_INSTDIR>/usr/sap/<sapsid>/<instancenumber>/j2ee/admin/go.sh

Port: 5<instance number>04

2. Enter the Java engine administrator password and choose Connect.

3. In the navigation pane, choose Server Services HTTP Provider

4. Select the Runtime tab.

5. Select the Aliases tab.

6. In Alias enter srm/lib/resources.

7. Enter the Path.

EXAMPLE

Windows (and IBM i):

<T_INSTDIR>:\usr\sap\<SAPSID>\SYS\global\srmla\resources

UNIX:

<T_INSTDIR>:/usr/sap/<SAPSID>/SYS/global/srmla/resources

8. Choose Add.

9. Choose Save Properties.

10. Choose the Java administration tool.End of: SAP SRM | SRM Live Auction Cockpit (SRMLAC) |

End of: SAP SRM | SRM Live Auction Cockpit (SRMLAC) |


6.2.3.2.12 SCM Forecasting & Replenishment Processor (SCM FRP)

Procedure

After the system copy, you must perform follow-up activities as described in SAP Note 862955.End of: SAP SCM |

6.2.4 Performing Jobhead Correction after Homogeneous System Copy

NOTE

This section is only relevant for customers using CCMS to monitor their SAP system(s).



108/148 PUBLIC 2012-03-14


After copying your system, the CCMS jobhead still points to the former database SSID. In order to

complete the homogeneous system copy, the SSID needs to be set to the target system.

CAUTION

Only experienced users should use this utility.

Only valid for: Source Release = SAP NetWeaver 7.0 |

Prerequisites

You must have SAP NetWeaver 7.0 SP 12 or above to use this function.End of: Source Release = SAP NetWeaver 7.0 |

Procedure

To set the SSID to the target system:

Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.1 |

1. Call transaction DBACOCKPIT.

2. Choose Configuration Homogeneous System Copy: Jobhead Correction

3. Modify the necessary data.End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.1 |

Only valid for: Source Release = SAP Web AS 6.40 |

1. Call transaction DB2.

2. Choose Checks/Settings Correct Jobheads

3. Modify the necessary data.End of: Source Release = SAP Web AS 6.40 |



2012-03-14 PUBLIC 109/148

7 Additional Information

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

The Migration Monitor

■ creates R3load command files.

■ creates R3load task files if required.

■ starts R3load processes to unload the data.

■ transfers packages from the source to the target host if required.

■ starts R3load processes to load the data as soon as a package is available.

■ informs the person performing the system copy in the case of errors.

The Migration Monitor has to be started on the source database host (export monitor) and on the

target database host (import monitor).

CAUTION

If you want to convert a non-Unicode system to a Unicode using the socket option, you need an

R3load version with a specific patch level. For more information, see SAP Note

1238351.

Prerequisites

■ JRE version 1.4.1 or higher

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

7.1.1 Configuration

Help

The tool displays all parameters available if you call it with one of the following options:

■ -help

■ -?



2012-03-14 PUBLIC 111/148


Version

The tool displays the version information (release branch and build date) if you call it with the following

option:

■ -version

General Options

Name Description Comments

monitorTimeout Monitor timeout in seconds During a timeout, the monitor thread sleeps and does not analyze any files or its processing state. The default timeout value is 30 seconds.

E-Mail Options


mailServer SMTP server Server name or IP address of the company SMTP server.

mailFrom “From” e-mail address

mailTo “To” e-mail address Can contain an address list separated by “;”or blanks.

Additional Options


bg Enables background mode Takes effect only as command line option.If the tool is running in background mode, the UNIX shell window 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) will be hidden for the Java process. Secure mode implicitly enables background mode.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 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.



112/148 PUBLIC 2012-03-14


exportDirs List of export directories

Separator on Windows: “;”Separator on UNIX, IBM i: “:”The exportDirs parameter points to the directory to which 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 the 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 the 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 file name of DDL control file. The default is DDL<DBTYPE>.TPL. If the file name is used without a 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 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)

expJobNum Number of parallel export jobs, the default is 1.

Any positive number; 0 for an unlimited number of jobs. The value can be changed dynamically at runtime.



2012-03-14 PUBLIC 113/148


Network Exchange Options


net Network operating mode Exported dump files must be visible on the import host to use this mode.

netExchangeDir Network 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 file <package>.SGN 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.

CAUTION

Clean up the netExchangeDir before starting a new export!

FTP Exchange Options


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 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 monitors property file.

ftpExchangeDir Remote FTP exchange directory Used for communication between the export and import monitors. Must be writable for the export



114/148 PUBLIC 2012-03-14

Option Description Commentsmonitor and readable for the import monitor. The export monitor writes a file <package>.SGN to the FTP exchange directory as a signal to the import monitor that the package has been 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.

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.

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



2012-03-14 PUBLIC 115/148


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:

exportDirs, ftpHost,ftpUser, ftpExportDirs, ftpExchangeDir

NOTE

The value of the dbType option is determined automatically in the shell script/batch files from

the dbms_type environment variable.

Import Options


installDir Installation directory The installation start directory is the directory in which the installation tools (SAPinst, R3SETUP) write their log files. When the Migration Monitor is used without the installation tools, the installation start directory is the directory where the R3load TSK and log files will be created.

importDirs List of import directories Separator on Windows: “;”Separator on UNIX, IBM i: “:”The importDirs parameter points to the directory where the R3load dump files will be written. In the importDirs directory, the subdirectories DATA, DB,



116/148 PUBLIC 2012-03-14

Option Description Commentand 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 stand-alone 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,or a path of the file that contains package names.If the option is omitted then package order is not defined.

ddlFile DDL control file Path or file name of DDL control file. The default is DDL<DBTYPE>.TPL. If the file name is used without path, then the DDL control file from the exportDB 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, then the monitor will not overwrite them.

extFiles yes to include EXT files; no to skip them

Add EXT file entries to cmd files. If 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

omit R3load omit value Can contain only the letters D, T, P, I, V.D: omit data; do not load dataT: omit tables; do not create tablesP: omit primary keys; do not create primary keysI: omit indexes; do not create indexesV: omit views; do not create viewsIf you want to combine several omit options, list these options without blanks (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



2012-03-14 PUBLIC 117/148


Option Description Commentspecified and task files are not used, that is, the value of tskFiles option is no).

impJobNum 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


exchangeDir Exchange directory If this option is not set, then the monitor runs in stand-alone 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 parameter importDirs (for example, in the properties file). If there is an old file export_statistics.properties

(for example, from a previous export run), remove this file.

Import Socket Options


socket Socket operating mode

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

installDir, importDirs, tskFiles, extFiles,

one of the options exchangeDir or socket (and their related parameters)

■ Stand-alone mode:

installDir, importDirs, tskFiles, extFiles

NOTE

The value of the dbType option is determined automatically in the shell script/batch files from

the dbms_type environment variable.

7.1.2 Assigning DDL Files to Packages

It is possible to use several different DDL*.TPL templates during the export or import. The assignment

of a specific DDL file to a single package is done within a simple text file, which then has to be specified



118/148 PUBLIC 2012-03-14

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.

Procedure

Example of a 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

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

Procedure

Example of a package order file with group:

# custom package order



2012-03-14 PUBLIC 119/148

# package names

SAPAPPL0

SAPAPPL1

SAPAPPL2

# package group

[ SEQUENTIAL GROUP ]

jobNum = 1

# table names

TABLE_A

TABLE_B

TABLE_C

7.1.4 Processing Split Tables

If tables have been split during the export, ensure before the import starts that the table exists and that

the primary key and the indexes are created 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 for Linux, UNIX, and Windows

■ MS SQL

You can ensure this by using the Defining Groups of Packages [page 119] feature.

Procedure

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. You now 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



120/148 PUBLIC 2012-03-14

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.

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 reimport all packages instead.

Restart for all other database platforms:

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

reimported by “0” (see Restarting R3load Processes [page 52]).

5. Restart the import.

7.1.5 Starting the Migration Monitor

The tool can be started using one of the following:

■ Only valid for: UNIX |

The UNIX shell scripts

export_monitor.sh / import_monitor.sh /

End of: UNIX |

■ Only valid for: Windows |

The Windows batch files

export_monitor.bat / import_monitor.bat /

End of: Windows |



2012-03-14 PUBLIC 121/148

■ Only valid for: IBM i5/OS |

IBM i-specific

1. Check that the environment variable PASE_THREAD_ATTACH is set to “Y” using the command

WRKENVVAR.

If the variable does not exist create it using the following command:

ADDENVVAR PASE_THREAD_ATTACH Y

2. Run the command call qp2term.

3. Set the JAVA_HOME environment as follows:

If you are using the IBM Classic JVM:

export JAVA_HOME=/QIBM/ProdData/Java400/jdk14

or

If you are using the JDK IBM Technology for Java (IT4J):

export JAVA_HOME=/QOpenSys/QIBM/ProdData/JavaVM/jdk14/64bit

4. ./ export_monitor.sh / ./import_monitor.shEnd of: IBM i5/OS |

You can specify options in the command line or in the export or import property files. 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: Any options that are not recognized are ignored.

To specify an option:

■ In the command line:

Enter -optionName optionValue.

■ In the application property file:

Insert the new line optionName=optionValue.


EXAMPLE

./export_monitor.sh –ftp

./export_monitor.sh –ftpCopy

./export_monitor.sh –socket –host <import server> –port 5000

End of: UNIX |


EXAMPLE

export_monitor.bat –net

export_monitor.bat –socket

End of: Windows |



122/148 PUBLIC 2012-03-14

If FTP access is used and security is required, start the monitor in secure mode to prevent seeing the

FTP password in the command line parameter string or in the property file.


EXAMPLE

./export_monitor_secure.sh –ftpPassword <password>

End of: UNIX |

Procedure1. Start the monitor and close the shell window or command processor. The monitor process runs

in the background.

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



2012-03-14 PUBLIC 123/148

# List of remote FTP directories for export dump, separator : or ;

ftpExportDirs=/install_dir/export_dump

# Remote FTP exchange directory

ftpExchangeDir=/install_dir/exchange

# Number of parallel FTP jobs

ftpJobNum=3

#

# E-mail options

#

# SMTP server

mailServer=sap-ag.de

# "From" email address

[email protected]

# "To" email address

[email protected] [email protected]

EXAMPLE

import_monitor_cmd.properties file with import options:

# 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



124/148 PUBLIC 2012-03-14

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

#

# E-mail options

#

# SMTP server

mailServer=sap-ag.de

# "From" email address

[email protected]

# "To" email address

[email protected] [email protected]

What happens during export / import with the above listed property files during a system copy with Oracle as source and target database:

■ The following directories must exist on the export host (parameter: exportDirs):

● c:\temp\export_dump\DATA

● c:\temp\export_dump\DB

● c:\temp\export_dump\DB\ORA

The c:\temp\export_dump\DATA directory must contain the STR files generated by R3ldctl, the c:

\temp\export_dump\DB directory the DDL<DBTYPE>.TPL files generated by R3ldctl, and the c:\temp

\export_dump\DB\ORA directory the EXT files generated by R3szchk.

■ The export monitor writes the R3load dump files and the TOC files to the directory c:\temp

\export_dump\DATA.

■ The R3load log files, cmd files, and TSK files (if required) are located in the directory c:\install

\start (parameter: installDir). The export itself is not done by the export monitor, as the

monitor is started in client mode (parameter server is not set).

■ As soon as a package has been exported successfully, the export monitor will transfer all files

belonging to that package (TOC, STR, EXT, 001, and so on) to the target host (parameter:

ftpHost) into the corresponding subdirectories of the directory /install_dir/export_dump

(parameter: ftpExportDirs) as user <sapsid>adm (parameter: ftpUser), identified by password

(parameter: ftpPassword) to log on.



2012-03-14 PUBLIC 125/148

■ If the package files have been completely transferred to the server, the export monitor will write

a <package>.SGN signal file to the /install_dir/exchange (parameter: ftpExchangeDir) directory

to notify the import monitor that it can start importing this package.

■ The following directories must exist on the import host (parameter: importDirs):

● /install_dir/export_dump/DATA

● /install_dir/export_dump/DB

● /install_dir/export_dump/DB/ORA

The /install_dir/export_dump/DATA directory has to contain the STR files generated by R3ldctl,

the /install_dir/export_dump/DB directory the files DDL<DBTYPE>.TPL also generated by R3ldctl,

the /install_dir/export_dump/DB/ORA directory the EXT files generated by R3szchk.

■ The import monitor will start to import a package as soon as the <package>.SGN file is found in

the /install_dir/exchange (parameter: exchangeDir) directory.

■ The R3load log files, cmd files, and TSK files (if required) will be located in the directory /

install_dir/start (parameter: installDir).

■ The file DDLORA.TPL has to be copied to the directory /install_dir/start (parameter:

installDir) before you start the import monitor.

7.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=+.

Format of lines is <PACKAGE>=<STATE>. Possible values for state are:

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=++.

Format of lines is <PACKAGE>=<STATE>. Possible values for state are:



126/148 PUBLIC 2012-03-14

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.

7.1.7 Installing the Target System Using the Migration Monitor

Prerequisites

Make sure that 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).

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:



2012-03-14 PUBLIC 127/148

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.

7.2 Using SAPinst GUI

The following table shows the most important functions that are available in SAPinst GUI:

SAPinst GUI Functions

Input Type Label Description

Function key F1 Displays detailed information about each input parameter

Menu option File Exit Stops the SAPinst GUI, but SAPinst and the GUI server continue runningOnly valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SCM;SAP Solution Manager;SAP SRM |

NOTE

If you need to log off during the installation from the host where you control the installation with SAPinst GUI, the installation continues while you are logged off. You can later reconnect to the same SAPinst installation from the same or another host.For more information, see Starting SAPinst GUI Separately [page 136].

End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SCM;SAP Solution Manager;SAP SRM |

Menu option SAPinst Log Browser Displays the Log Viewer dialogThis dialog enables you to access the following log files directly: ■ Installation log (sapinst_dev.log) ■ Log files from the SAPinst GUI server

Menu option SAPinst Cancel Cancels the installation with the following options: ■ Stop

Stops the installation (SAPinst GUI, SAPinst, and the GUI server) without further changing the installation filesYou can restart and continue the installation later from this point.

■ Continue


7.2 Using SAPinst GUI

128/148 PUBLIC 2012-03-14

Input Type Label DescriptionContinues the installation

Message button Retry Performs the installation step again (if an error has occurred)

Message button Stop Stops the installation without further changing the installation filesYou can continue the installation later from this point.

Message button Continue Continues with the option you chose previously

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

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.


NOTE

You can also terminate SAPinst by choosing Ctrl + C . However, we do not recommend that

you use Ctrl + C , because this kills the process immediately.

End of: UNIX |



2012-03-14 PUBLIC 129/148

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.



Log on as a user who is a member of the local administrators group.End of: Windows |


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 |


Insert the Installation Master DVD in your DVD drive.End of: Windows |

4. Only valid for: Unix |

Mount your Installation Master DVD.

NOTE

Mount the DVD locally. We do not recommend using Network File System (NFS).

End of: Unix |


Change to the required directory using the following command:


End of: Windows |


Double-click sapinst.exe.End of: Windows |

7. Only valid for: Unix |

Start SAPinst using the following commands:

cd <Installation_Master_DVD>/IM_<OS>

./sapinst

End of: Unix |

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

Check the subsystem TMKSVR<nn> (nn=00, or any other number you have chosen for your

TMKSVR instance). To do this, enter the following command:

WRKACTJOB SBS(TMKSVR<nn>)

NOTE

If the TMKSVR<nn> subsystem is running, you can continue with the step check if an SAPinst GUI

Java process is still running.




130/148 PUBLIC 2012-03-14

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

If this subsystem is not running because for example of an IPL, you must restart the subsystem

manually.

To do this, log on as your installation user and enter the following commands:

■ ADDLIBLE TMKSVR<nn>

■ STRTMKSVR INSTNO<nn>

NOTE

Now the TMKSVR<nn> subsystem is running again and you can continue with the next step.


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

Check if an SAPinst GUI Java process is still running.

If a process is still running, look for javaw.exe under Processes in your Task Manager and kill it.

■ If you used the default installation directory (recommended):

cd <Mapped_Drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64

sapinst.exe

■ If you used an alternative installation directory:

cd <Mapped_Drive>:\<your installation directory>

<Mapped_Drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64\sapinst.exe

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

11. From the tree structure in the Welcome screen, select the installation option that you want to

continue and choose Next.

NOTE

If there is only 1 component to install, the Welcome screen does not appear.

The What do you want to do? screen appears.

12. In the What do you want to do? screen, decide between the following alternatives and confirm with

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

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



2012-03-14 PUBLIC 131/148

Alternative Behaviorprocesses currently running on these files and folders, they might no longer function properly.

Continue with the Old Option SAPinst continues the interrupted installation option from the point of failure.

7.4 Performing a Remote Export Using SAPinst

Purpose

You can run the SAPinst GUI in standalone mode to perform a remote export.

This enables you to perform the export on another host (the remote host) while monitoring the export

with the SAPinst GUI on your local Windows or UNIX computer (the local host).

Prerequisites

■ You have performed the preparation activities for your local host (SAPinst GUI host) and your

remote host as described in Prerequisites in Exporting the Source System Using SAPinst [page 35].

■ Both computers are in the same network and can ping each other.

To test this:

● Log on to your remote host and enter the command ping <local host>.

● Log on to the local host and enter the command ping <remote host>.

Process Flow

1. Start the SAPinst server on your remote host.

2. Start the SAPinst GUI on your local host.

3. Perform the installation using the SAPinst GUI.

For more information, see:

■ Starting SAPinst on the Remote Host [page 132]

■ Starting SAPinst GUI Separately [page 136]

7.4.1 Performing a Remote Installation with SAPinst

You use this procedure to install your SAP system on a remote host. In this case, SAPinst runs on the

remote host, and the SAPinst GUI runs on the local host. The local host is the host from which you

control the installation with the SAPinst GUI. The SAPinst GUI connects using a secure SSL connection

to SAPinst.


NOTE

For IBM i only in rare cases a remote installation is done. A local installation on IBM i means that

the entire SAPinst (the SAPinst and SAPinst GUI) is running on the same Windows PC to install

an SAP system on IBM i using the TMKSVR. A remote installation on IBM i means that two



132/148 PUBLIC 2012-03-14

Windows PCs and one IBM i host are involved in the installation. On the remote PC, located close

to the IBM i host, you are running the SAPinst. On the local PC, you only run the SAPinst GUI.

End of: IBM i5/OS |


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



on the local Windows host is not allowed to know administrator credentials on the remote Windows

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.exe from the command line.End of: IBM i5/OS |



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: UNIX;Windows |

As an alternative to remote installation you can use an X server for Microsoft Windows or other remote

desktop tools such as VNC Viewer or NX Server / NX Client ‒ offered by various vendors or open

source ‒ for remote access to SAPinst GUI on Windows workstations. We recommend that you use the

Hummingbird Exceed X Server, which we use to validate installations with SAPinst. For more

information, see SAP Note 1170809.End of: UNIX;Windows |

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 136]End of: UNIX;Windows | Linux;Windows |


CAUTION

The behavior of SAPinst and SAPinst GUI has changed compared to previous versions. SAP no

longer delivers any JCE policy archives within the SAP Java Virtual Machine (SAP JVM). You have



2012-03-14 PUBLIC 133/148


to download the required Java Cryptography Extension (JCE) policy zip file from SAP on the

remote host. For more information, see SAP Note 1238121.

End of: IBM DB2 for i5/OS |


CAUTION

If you install SAP instances on IBM i, “local host” in this section refers to the Windows installation

host, not the IBM i host.


Prerequisites

■ The remote host meets the prerequisites as described in Running SAPinst in your installation guide.

■ Both computers are in the same network and can ping each other.

To test this:


Log on to your remote host and enter the command ping <remote host>.End of: UNIX;Windows |


Log on to your remote host (IBM i) and enter the command PING RMTSYS('<local

host>').End of: IBM i5/OS |

3. Log on to the local host (Windows PC) and enter the command ping <remote host>.

■ If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER

command line parameter, make sure that this user exists on the remote host.

ProcedureOnly valid for: IBM i5/OS;Windows |

1. Log on to your remote host as a user that is a member of the local administrators group.

2. Insert the Installation Master DVD in the DVD drive on your remote host.


Download the JCE policy zip file from SAP as described in SAP Note 1240081.End of: IBM i5/OS | IBM DB2 for i5/OS |


Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive

by entering the following command:

set JCE_POLICY_ZIP=<policy zip archive>


5. Enter the following commands:



134/148 PUBLIC 2012-03-14



Only valid for: 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 |

cd <DVD drive>:\IM_WINDOWS_<platform>

End of: 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 |

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

cd <mapped drive>:\IM_OS400_PPC64


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>

For more information about how to perform the export, see Exporting the Source System Using SAPinst

[page 35].

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

6. Start the SAPinst GUI on your local host as described in Starting the SAPinst GUI Separately [page

136].End of: IBM i5/OS;Windows |


1. Log on to your remote host as user root.

CAUTION


or database.

2. Mount the Installation Master DVD.

3. Change to the directory of the sapinst executable and start SAPinst without GUI using 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 |

cd <mountpoint_of_Installation_Master_DVD>/IM_<OS>

End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle |

./sapinst -nogui

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>



2012-03-14 PUBLIC 135/148

For more information about how to perform the export, see Exporting the Source System Using SAPinst

[page 35].

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 136].End of: UNIX |

7.4.2 Starting SAPinst GUI Separately

You use this procedure to start the SAPinst GUI separately. You need to start the SAPinst GUI separately

in the following cases:

■ You closed the 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 132].

■ 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 in your installation guide.End of: IBM i5/OS;UNIX |

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

CAUTION

The behavior of SAPinst and SAPinst GUI has changed compared to previous versions. SAP no

longer delivers any JCE policy archives within the SAP JVM. You have to download the required

JCE policy zip file from SAP on the local host. For more information, see SAP Note 1238121.


Procedure

Starting the SAPinst GUI on Windows

1. Log on as a member of the local administrators group.





by entering the following command:



136/148 PUBLIC 2012-03-14



set JCE_POLICY_ZIP=<policy zip archive>


4. Insert the SAP Installation Master DVD into your DVD drive.

5. Change to the directory of the sapinst executables:

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 |


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 |

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

NOTE

If you want to start the SAPinst GUI on a Windows 32-bit operating system, change to the

following directory:

<Installation_Master_DVD>\IM_WINDOWS_I386

End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |

Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |

NOTE

If you want to start the SAPinst GUI on a Windows 32-bit operating system, you can use the

executable available in the DVD or change to the following directory:

<Installation_Master_DVD>\IM_OS400_PPC_64

End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |


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

X:\tmp\<SID>\<Installation_Master_DVD>\IM_OS400_PPC_64


6. Only valid for: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

Start the SAPinst GUI by double-clicking sapinstgui.exe

The SAPinst GUI starts and tries to connect to SAPinst, using the local host as default.

If the SAPinst GUI is running on another host, the 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 screen of the installation appears and you can perform the remote installation from your

local host.

NOTE

Optionally you can start sapinstgui.exe with the following parameters:

■ host=<host name>, where <host name> is the host name of the installation host

■ port=<nr>, where <nr> is the port number for the connection to the GUI server

■ -accessible enables accessibility mode



2012-03-14 PUBLIC 137/148

Example: sapinstgui host=lsi1209 port=3000 -accessible

■ -h displays a list of all available parameters

End of: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

7. Only valid for: z/OS |

Start the SAPinst GUI in one of the following ways:

■ If the SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following

command:

startinstgui.bat

SAPinst GUI uses the local host as default.

■ If SAPinst runs on a different host from the SAPinst GUI (remote installation), enter the

following command:

startinstgui.bat -host <host_name>

<host_name> is the host name of the installation host.

NOTE

● If you enter the command without additional parameters, the SAPinst GUI uses the

local host as default. The SAPinst GUI starts and tries to connect to SAPinst. Since

SAPinst 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 the SAPinst GUI, change to the same directory as your

SAPinst executable and enter the command:

startinstgui.bat -h

End of: z/OS |

Only valid for: 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 |

Starting the SAPinst GUI on UNIX

1. Log on as user root.

CAUTION


or database.





as follows:



138/148 PUBLIC 2012-03-14


Shell Used Command

Bourne shell (sh) JCE_POLICY_ZIP=<policy zip archive>

export JCE_POLICY_ZIP

C shell (csh) setenv JCE_POLICY_ZIP <policy zip archive>

Korn shell (ksh) export JCE_POLICY_ZIP=<policy zip archive>


4. Mount your Installation Master DVD.

NOTE

Mount the DVD locally. We do not recommend that you use Network File System (NFS).

5. Change to the directory of the sapinst executables:

<mountpoint_of_Installation_Master_DVD>/IM_<OS>

NOTE

If you want to start the SAPinst GUI on a Linux 32‒bit platform, change to the following

directory:

<mountpoint_of_Installation_Master_DVD>/IM_LINUX_I386

6. Only valid for: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

Start the SAPinst GUI by executing ./sapinstgui

The SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host as

default.

If SAPinst and the GUI server are running on another host, 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 screen of the installation appears and you can perform the remote installation from your

local host.

NOTE

Optionally, you can start sapinstgui with the following parameters:

■ host=<host name>, where <host name> is the host name of the installation host

■ port=<nr>, where <nr> is the port number for the connection to the GUI server

■ -accessible enables accessibility mode

Example: ./sapinstgui host=lsi1209 port=3000 -accessible

■ -h displays a list of all available parameters

End of: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

7. Only valid for: z/OS |

Start the SAPinst GUI in one of the following ways:

■ If the SAPinst GUI runs on the same host as SAPinst, enter the following command

without additional parameters:

./startInstGui.sh

By default, SAPinst GUI uses the local host.



2012-03-14 PUBLIC 139/148

■ 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, the SAPinst GUI uses the

local host as default. The SAPinst GUI starts and tries to connect to SAPinst. Since

SAPinst 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 host on which SAPinst is running and choose Log on.

The first screen of the installation appears and you can perform the remote

installation from your local host.

● For a list of options to start the SAPinst GUI, change to the same directory as your

SAPinst executable and enter the command:

./startInstGui.sh -h

End of: z/OS |

End of: 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 |

7.5 Troubleshooting with SAPinst

This section describes the steps that you need to perform manually if SAPinst fails.

Procedure

Processing Phase

If the export process aborts during the processing phase (for example, due to a hardware failure, such

as power outage, operating system crash, file system full), you have to repeat the export of the complete

package.

1. Remove the <package>.<nnn> dump files, the <package>.TOC file, and the <package>.log file.

2. Make sure that all tables in the <package>.*TSK* file have the status flag xeq or err set.

3. Repeat the export of the complete package.

Dialog Phase

If an error occurs during the dialog phase, SAPinst stops and displays a dialog that informs you about

the error.

You can now:

■ View the log file directly by choosing View Logs.

■ Try to solve the problem.

■ Stop the process by choosing Cancel in the SAPinst menu.



140/148 PUBLIC 2012-03-14

For more information, see Interrupted Installation with SAPinst [page 129].

■ After resolving the problem, you can continue by choosing Retry.


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.0 SR1.

Solution:

1. Manually associate <sapsid>adm and ora<sid> OS users with sapinst group if this association is

missing.

2. Verify the /etc/group file and check if the sapinst group exists and OS users are members of this

group.

3. If the sapinst group does not exist yet, start SAPinst. SAPinst will create this group during startup

before the product catalog list is displayed.

4. Edit /etc/group file and associate OS users with sapinst group.

5. Continue with the export.End of: UNIX |

More Information

■ Interrupted Installation with SAPinst [page 129]

■ Performing a Remote Export Using SAPinst [page 132]



2012-03-14 PUBLIC 141/148

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

142/148 PUBLIC 2012-03-14

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2012 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, PowerPoint, Silverlight, and Visual Studio 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, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the United States and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.Oracle and Java are registered trademarks of Oracle and its affiliates.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.Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.IOS is a registered trademark of Cisco Systems Inc.RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.INTERMEC is a registered trademark of Intermec Technologies Corporation.Wi-Fi is a registered trademark of Wi-Fi Alliance.Bluetooth is a registered trademark of Bluetooth SIG Inc.Motorola is a registered trademark of Motorola Trademark Holdings LLC.Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.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 company.Sybase 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.

2012-03-14 PUBLIC 143/148

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate 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

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 was developed using ANTLR.2. SAP License Agreement for STLport

SAP 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

144/148 PUBLIC 2012-03-14

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

2012-03-14 PUBLIC 145/148

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.

4. Only valid for: SAP ERP;SAP CRM |

Apache License, Version 2.01. Definitions:

■ "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

■ "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

■ "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

■ "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. ■ "Source" form shall mean the preferred form for making modifications, including but not limited to software

source code, documentation source, and configuration files. ■ "Object" form shall mean any form resulting from mechanical transformation or translation of a Source

form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

■ "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

■ "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

■ "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

■ "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright LicenseSubject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent LicenseSubject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution

146/148 PUBLIC 2012-03-14


You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:1. You must give any other recipients of the Work or Derivative Works a copy of this License; and2. You must cause any modified files to carry prominent notices stating that You changed the files; and3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,

trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of ContributionsUnless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. TrademarksThis License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of WarrantyUnless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of LiabilityIn no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional LiabilityWhile redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

End of: SAP ERP;SAP CRM |

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

2012-03-14 PUBLIC 147/148


SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2012 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.

system copy solman 7.0 ehp1 forsr1

Documents