system copy 73 java

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

Target Audience ■ System administrators ■ Technology consultants

PUBLICDocument version: 1.3 – 2011-11-07

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.3 2011-11-07 Updates in Transferring Export Files to the Target System, Advanced Adapter Engine Extended (AEX)

1.2 2011-01-18 Update in Installing the Target System

1.1 2011-12-02 Formal update

1.0 2010-11-29 Initial version

2/122 PUBLIC 2011-11-07

http://service.sap.com/instguides


Table of Contents

Chapter 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based

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

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

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

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

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

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

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

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

3.2 Usage-Type-Specific Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.3 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 4 Database Independent System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.1 System Copy Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.2 Preparing Parallel Export and Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.3 Exporting the Source System Using SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.3.1 Running SAPinst on UNIX or Windows to Perform the Export . . . . . . . . . . . . 20

4.3.2 Running SAPinst on IBM i to Perform the Export . . . . . . . . . . . . . . . . . . . . . . 23

4.3.2.1 Starting SAPinst on IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.3.2.2 Preparing an IBM i User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4.3.2.3 Copying the Installation Media Manually to Your IBM i . . . . . . . . . . . . . . . . . 27

4.4 Setting Up the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.4.1 Transferring the Export Files to the Target Host . . . . . . . . . . . . . . . . . . . . . . . 30

4.4.2 Installing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

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

5.1 Oracle-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

5.1.1 Generating the Control File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.1.2 Creating a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5.1.2.1 Creating an Offline Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

2011-11-07 PUBLIC 3/122

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

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

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

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

5.2 SAP MaxDB-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

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

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

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

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

5.6.1 Step 1: Check Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

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

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

5.6.3.1 SQL Statement Number 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56









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

Changed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

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

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

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

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

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

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

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

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

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

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

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

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

Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

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

4/122 PUBLIC 2011-11-07

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

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

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

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

5.6.20 Step 12: Adapting WLM Application Environments for DB2 Stored

Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Chapter 6 Copying Single Instances Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

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

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

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

Chapter 7 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

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

7.1.1 Installing the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

7.1.2 Performing Follow-Up Activities for Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

7.1.2.1 General Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

7.1.2.1.1 Generating Public-Key Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

7.1.2.2 Software Unit-Specific Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

7.1.2.2.1 AS Java: Adobe Document Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

7.1.2.2.2 EP Core – Application Portal (EPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

7.1.2.2.2.1 EPC: Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

7.1.2.2.3 Enterprise Portal (EP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

7.1.2.2.3.1 EP: Knowledge Management and Collaboration . . . . . . . . . . . . . . . . . . . . . . . 77

7.1.2.2.4 Business Intelligence Java Components (BI Java) . . . . . . . . . . . . . . . . . . . . . . . 80

7.1.2.2.4.1 Business Intelligence (BI Java) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

7.1.2.2.4.2 Basic Configuration for BI Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

7.1.2.2.5 Enterprise Services Repository: Connecting to the SLD . . . . . . . . . . . . . . . . . . 81

7.1.2.2.6 Partner Connectivity Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

7.1.2.2.7 Development Infrastructure (DI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

7.1.3 Performing Jobhead Correction after Homogeneous System Copy . . . . . . . . . 84

Chapter 8 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

8.1 Jload Procedures Using the Java Migration Monitor . . . . . . . . . . . . . . . . . . . . . 87

8.1.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

8.1.2 Starting the Java Migration Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

8.1.3 Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

8.1.4 Restarting Jload Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

2011-11-07 PUBLIC 5/122

8.2 Package and Table Splitting for Java Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

8.2.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

8.2.2 Starting the Table Splitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

8.2.3 Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

8.3 Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

8.3.1 Useful Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

8.3.2 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

8.3.3 Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . 105

8.3.4 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

8.3.5 Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

8.3.6 Entries in the Services File Created by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . 114

8.3.7 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

6/122 PUBLIC 2011-11-07

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

Purpose

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

methods or database-specific methods.

CAUTION

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

of the operating system, the database, and the Java Dictionary. Only perform a heterogeneous

system copy if you are a certified system support consultant or a certified SAP Technical

Consultant.

1.1 Terminology

■ System Copy

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

a system copy, SAPinst installs all the instances again, but it uses a copy of the source system database

to set up the database.

■ Source System and Target System

The SAP system containing the original database is called the source system and the system to

which the database copy is to be imported is called the target system. Their SAP system names

are abbreviated to SOURCE_SAPSID and TARGET_SAPSID. The terms source database and target

database are also used in this description.

■ Homogeneous System Copy

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

system.

■ Heterogeneous System Copy

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

Heterogeneous system copy is a synonym for migration.

■ Database Copy

Database-dependent part of the system copy.

■ Placeholders


1.1 Terminology

2011-11-07 PUBLIC 7/122

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

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

The following additional placeholders are used:

Placeholder Meaning How to find out

<SAPSID> SAP system ID —

<S_HOST> System name of the source host Command hostname

<T_HOST> System name of the target host Command hostname

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

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

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

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

1.2 Online Information from SAP

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

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

system copy documentation:

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

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

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

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

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

guides are available at

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

NOTE

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

area BC-INS-MIG.

More Information

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

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

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

Guide that is available in the Media Library.

■ SAP system landscape copy:

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

service.sap.com/solutionmanagerbp

● SAP Note 885343 – SAP System Landscape Copy

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


1.2 Online Information from SAP

8/122 PUBLIC 2011-11-07

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

http://service.sap.com/notes


http://service.sap.com/systemcopy

http://service.sap.com/osdbmigration

http://service.sap.com/solutionmanagerbp

http://service.sap.com/solutionmanagerbp



1.3 Accessing the SAP Library

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

on SAP Help Portal:

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

1.4 Constraints

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

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

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

■ SAP does not support client transport as a system copy method. Transporting production clients

is not supported at all. You can use client transport for the initial setup of an SAP system

infrastructure. This documentation does not cover the client copy procedure.

■ This documentation does not describe how to export and import a database with the installation

tools for reorganization purposes. Use the appropriate tools for database reorganization, as SAP

does not support this installation option.

■ If you have made modifications in your development system and want to copy your quality

assurance or production system onto the development system, see SAP Note 130906.

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

on SAP NetWeaver Application Server. This documentation does not describe how to copy data

from non-SAP systems to SAP systems.

■ If you want to convert a non-Unicode system to a Unicode system or perform the system copy of

a Unicode system, see SAP Note 551344.

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

mentioned below. Otherwise, we cannot guarantee that you will be able to 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 system, you might not always have access from the target

system to the archive files that were created. For more information, see SAP Note 153433 and System

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

Access from the target system to archived files in the source system without a dedicated archive

migration project is only supported as follows:

● You have copied a source system that uses external data archiving. The target system has read-

only access to this archive.

● You have copied a source system that uses data archiving locally. You can either arrange

network access for appropriate archive file sharing or copy all archive files to the file system

of the target system.


1.3 Accessing the SAP Library

2011-11-07 PUBLIC 9/122

http://help.sap.com/nw73




http://service.sap.com/slo

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 in the source system are copied to the target

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

system copy, nor can you select software units.

■ Dos and Don'ts for system copy:

● Do:

◆ Save configuration data and runtime data in the Java database only.

◆ Follow the Open SQL standard.

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

● Don't:

◆ Save any system and infrastructure-specific data in business objects. Use a pointer to the

central storage of such information, for example:

▶ SAP SystemID and SID (SAPSID = SID = system name)

▶ Host name

▶ IP addresses

▶ Services and Ports

▶ Logical destinations and logical system names

▶ Other technical infrastructure names

◆ Use file system persistency.

◆ Set up dependencies between Java and ABAP.

◆ Try to copy the Java part of an ABAP+Java system to a Java standalone system or the other

way around.

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

see SAP Note 1080080 before commencing with the system copy.


1.4 Constraints

10/122 PUBLIC 2011-11-07

http://service.sap.com/slo


2 Planning

This section describes how to plan your system copy.

You can apply the system copy for the following:

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

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

NOTE

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

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

specific problems that might result from modifications.

Depending on the purpose of the system, it might be advisable to use the same SAP system ID, even

though this prevents you from including the system in a system group for transports.

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

You can use different operating system releases or database releases for the source and target

systems, but the SAP system release of the source and target systems must be the same.

■ Changing the hardware.

Creating A System Copy Plan

Create a plan to perform the system copy.

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

system copy.

2. Consider a test run

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

system downtime:

■ If you want your target system to replace your source system, try to perform a complete test

run. This means that the entire database is exported from the source system, transferred to

the target system and imported there. System downtime is approximately equal to the total

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

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

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

down for the time of the export.

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

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

2 Planning

2011-11-07 PUBLIC 11/122

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

perform read/write actions only on local file systems.

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

When copying a system that contains production data, choose the moment for the copy carefully.

This could be a month-end or year-end closing.

Miscellaneous

■ In the event of a major change in hardware configuration (for example, new machine type,

new hard disk configuration, new file system type), consult your SAP-authorized hardware

partner.

■ Decide which system copy procedure you want to use:

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

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

NOTE

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

database-independent method is available.

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

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

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

(backup method)

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

● Copy single instances only

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

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

CAUTION

You cannot copy single usage types or components!

■ Changing the system variant

If you want to change your system variant (for example, if you want to make your standard system

a distributed or high-availability system), proceed as follows:

1. Perform the export [page 20].

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

the system copy procedure [page 18].

■ 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

2 Planning

12/122 PUBLIC 2011-11-07

Once the installation is completed and the SAP system copy has been imported, you require a new

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

For information about ordering and installing the SAP license, see the SAP Library [page 9] at:

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

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

Note 94998.

■ Archiving files

Data that has been archived in the source system (data that does not reside in the database but was

moved to a different storage location using SAP Archive Management) must be made accessible

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

information, see the SAP Library [page 9] at:

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

ARC) .

Access to archive files is platform-independent.

■ Configuration analysis and hardware analysis

You need to determine the:

● Number of application servers

● Expected size of the database

● Additional disks or other hardware required

● Required memory

NOTE

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

documentation to determine the system requirements.

Usage-Type-Specific Planning Steps

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),

Change Management Service (CMS), and CM Services do not support such a copy.

■ Move

“Move” is supported by all JDI components (DTR, CBS, CMS, and CM Services). After a move, the

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

performed.

2 Planning

2011-11-07 PUBLIC 13/122

http://service.sap.com/licensekey


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

3 Preparations

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

3.1 General Technical Preparations

Procedure

To make a consistent copy of the database, you need to prepare the source system and perform some

subsequent actions on the target system. This is not necessary when performing a test run.

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

SAP system administration, see the SAP Online Documentation.

■ Before you start a system copy, check the minimum kernel patch level required by the support

package level of the source system. It might be necessary to replace the SAP kernel delivered with

the installation kit and installed during the installation of the target system by a newer kernel

patch level before starting the target system. If you have to replace the delivered SAP kernel, you

can do this after the installation of the primary application server instance.

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

to a valid JDK version.

NOTE

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

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

3.2 Usage-Type-Specific Preparations

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

Procedure

Development Infrastructure (DI)

If your SAP system is of software unit 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. The target system will be

inactive after the copy. If you want to move an SAP system with software unit Development

Infrastructure (DI), perform the following preparatory steps:

3 Preparations

3.1 General Technical Preparations

2011-11-07 PUBLIC 15/122

1. Make sure that the users and passwords created in the source system are valid in the target system

(for example, they use the same UME).

2. 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. Remove all existing development configurations from the SAP NetWeaver Developer Studio.

4. Stop all applications of the Development Infrastructure (DI) on the source system.

3.3 Preparing the Installation Media

Procedure

1. Identify the required media as listed below.

NOTE

The media names listed in the following table are abbreviations.

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

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

installnw73 .

SAP Instance Required Folder of Software Packages from Media

Central services instance for Java (SCS) ■ Installation master (folder <Product>_IM_<OS>_<DB>) ■ UC or NUC kernel (folder K_<N or U>_<Version>_<OS>)

where U means Unicode and N means non-Unicode. ■ Database client software

NOTE

You can find the Software Component Archives (SCAs) for the installation of SAP NetWeaver usage types in the software packages for Java (folders JAVA_*).

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

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

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

CAUTION

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

2. Make the required media available.

RECOMMENDATION

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

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

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

you can upgrade them at different times.

3.

3 Preparations

3.3 Preparing the Installation Media

16/122 PUBLIC 2011-11-07

http://service.sap.com/installnw73

http://service.sap.com/installnw73

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

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.

Constraints

Jload Restrictions

■ SAPinst generates a database dump of all SAP objects that are defined in the Java Dictionary (Jload).

Other objects are not exported by SAPinst.

■ For a consistent database export, no transactions on export-relevant database objects are allowed

during the export. Otherwise, the export has to be restarted. Therefore, we recommend that you

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

running.

Existing Target System

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

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

the installation documentation for your SAP component.

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

up these configuration files before deleting the database.

Splitting STR Files

■ During the standard system copy process, all tables of the SAP system are grouped into packages,

whereby all tables with the same data class belong to the same package. The processing unit for

one unload/load process is a package. The packages differ in number and size of contained tables,

resulting in varying unload/load runtimes. The overall runtime can be reduced by creating

packages of the same size, that is, creating packages with a similar processing time. You can achieve

this by splitting the default packages (one package per data class) into more and smaller pieces.

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

F1 help about the parameters prompted on theSplit STR Files screen while running SAPinst to

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

tool – combined.


2011-11-07 PUBLIC 17/122

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

you select the splitting option (if you did not already perform some tests before), using the splitting

tool parameters selected by SAPinst is a good starting point.

CAUTION

If you want to split STR files, you must first create the EXT files for the target database system.

You can find the EXT files in your export dump directory, subdirectory DB/<DBTYPE>, for

example DB/ORA.

4.1 System Copy Procedure

This section describes the system copy procedure using 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:

■ Standard system

■ Distributed system or high-availability system

Standard System

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

1. Perform the export on the standard system host:

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

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

for the export.

In SAPinst, choose the system copy option Export Preparation.

2. Run SAPinst on UNIX or Windows [page 20] or on IBM i [page 23] to export the database instance.

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

Only valid for: UNIX |

CAUTION

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

SAP Note 884452.

End of: UNIX |

Result

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

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


4.1 System Copy Procedure

18/122 PUBLIC 2011-11-07


Distributed System or High-Availability System

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

1. Perform the export on the database instance host:

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

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

for the export.

In SAPinst, choose the system copy option Export Preparation.

2. Run SAPinst on UNIX or Windows [page 20] or on IBM i [page 23] to export the database instance.

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


CAUTION

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

SAP Note 884452.

End of: UNIX |

Result

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

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

4.2 Preparing Parallel Export and Import

If you want to perform export processes in parallel to import processes, you have to prepare the source

system for the export. The preparation includes the following steps, that are required to set up the

target database:

■ Creating the export directory structure

■ Calculating the size of the target database

■ Creating database size file DBSIZE.XML

If you do not prepare the export, you have to wait for the export results before you can start with the

target system setup.

Procedure

1. Run SAPinst to perform the Export Preparation.

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

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

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

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

More Information

Jload Procedures Using the Java Migration Monitor [page 87]


4.2 Preparing Parallel Export and Import

2011-11-07 PUBLIC 19/122


4.3 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 20]

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

4.3.1 Running SAPinst on UNIX or Windows to Perform the Export

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

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

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

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

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

Performing a Remote Installation with SAPinst [page 105].

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

Prerequisites

CAUTION

Make sure that you shut down all SAP application servers before the export. The database must

still be running. Otherwise, the target system might be inconsistent.

You need at least 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.


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

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

Procedure

1. Only valid for: UNIX |

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

Only valid for: Windows |

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

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

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



20/122 PUBLIC 2011-11-07

CAUTION

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

or database.

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

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

host.

CAUTION

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

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


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

installation media in one of the following ways:

■ Using the default installation directory (recommended)

Enter the following command:

./sapinst

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

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

■ Using an alternative installation directory

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

TMP, or TMPDIR.

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

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

sapinst SAPINST_USE_HOSTNAME=<virtual host>.

CAUTION

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

when the Java Virtual Machine is started.

NOTE

Be aware of the following:

■ Make sure that your operating system does not delete the contents of the temporary

directory /tmp or the contents of the directories to which the variables TEMP, TMP, or

TMPDIR point, for example, by using a crontab entry.

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

to another operating system.

EXAMPLE

For example, the following causes an error:

$ cd /sapcd2/IM_HPUX_IA64

$ /sapcd2/IM_HPUX_PARISC/sapinst

To correct this, enter the following:



2011-11-07 PUBLIC 21/122

$ cd /sapcd2/IM_HPUX_PARISC

$ /sapcd2/IM_HPUX_PARISC/sapinst

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

4. Only valid for: Windows |

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

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

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

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

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

of the process flow for the database-independent system copy procedure [page 17].

CAUTION

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

system variant.

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

Export Options

Export Option Remarks

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

NOTE

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

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

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


CAUTION

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

Note 884452.

End of: UNIX |

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



22/122 PUBLIC 2011-11-07


CAUTION

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

tools.

NOTE

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

● You choose parameter mode Custom.

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

on the SAP System > Database Export screen.

■ To split Java packages and tables you can use the Java splitter tool as part of SAPinst. For

more information about the Java splitter tool, see Package and Table Splitting for Java Tables

[page 92].

■ You can perform several database load processes in parallel. For more information, see

Jload Procedures Using the Java Migration Monitor [page 87].

NOTE

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

parameter field and choose F1 .

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

during the processing phase.

Troubleshooting

See Useful Information About SAPinst [page 98].

Only valid for: IBM i5/OS |

4.3.2 Running SAPinst on IBM i to Perform the Export

4.3.2.1 Starting SAPinst on IBM i

CAUTION

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

system might be inconsistent.

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

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

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

runs on a Windows 32-bit host.

NOTE

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

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



2011-11-07 PUBLIC 23/122

Procedure

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

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

CAUTION

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

system or database.

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

host.

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

Manually Using the ROOTBIN Share [page 27].

3. Start SAPinst in one of the following ways:

■ Using the default installation directory (recommended)

Enter the following commands:

cd 'DATA_UNITS/<product>_IM_OS400_PPC64_DB4'

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

NOTE

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

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

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

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

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

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

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

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

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

support available.

● Only valid for: HA (UNIX) |

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

environment parameter SAPINST_USE_HOSTNAME to specify the virtual host name,

you can start SAPinst as follows:

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

name>')

End of: HA (UNIX) |

CAUTION

● Make sure that your operating system does not delete the contents of the temporary

directory /tmp or the contents of the directories to which the variables TEMP, TMP, or

TMPDIR point.



24/122 PUBLIC 2011-11-07

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

to another operating system.

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

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

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

sapinst')

The following commands are correct:

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

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

■ Using an alternative installation directory

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

TMP, or TMPDIR.

NOTE

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

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

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

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

SAPINST_USE_HOSTNAME=<virtual host>.

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

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

of the process flow for the database-independent system copy procedure [page 17].

CAUTION

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

system variant.

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

of a:

■ Standard system

■ Distributed system or high-availability system

Export Options


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

NOTE

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

Database Instance Export Mandatory step.SAPinst performs the following steps:



2011-11-07 PUBLIC 25/122


■ Creates the export directory structure ■ Creates database structure files (*.STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*.EXT, DBSIZE.XML) ■ Exports the database content

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

CAUTION

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

Note 884452.

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

CAUTION

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

tools.

NOTE

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

● You choose parameter mode Custom.

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

on the SAP System > Database Export screen.

■ To split Java packages and tables you can use the Java splitter tool as part of SAPinst. For

more information about the Java splitter tool, see Package and Table Splitting for Java Tables

[page 92].

You can perform several database load processes in parallel. For more information, see

Jload Procedures Using the Java Migration Monitor [page 87].

NOTE

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

parameter field and choose F1 .

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

progress of the installation.

Troubleshooting

See Useful Information About SAPinst [page 98].

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

4.3.2.2 Preparing an IBM i User Profile

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

The following requirement applies:

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

QSECOFR.



26/122 PUBLIC 2011-11-07


Procedure

NOTE

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

IBM i:

Execute the following command:

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

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

NOTE

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

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

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

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

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

4.3.2.3 Copying the Installation Media Manually to Your IBM i

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

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

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

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

Procedure

Creating a Binary Share ROOTBIN on IBM i

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

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

System i Navigator (OpsNav). To do so, proceed as follows:

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

2. Connect to your IBM i using My Connections.

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

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

A new screen i5/OS Netserver appears.

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

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

File .



2011-11-07 PUBLIC 27/122

NOTE

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

be /.

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

8. To save the share ROOTBIN, press OK.

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

Copying the Installation Media Manually Using the Binary Share ROOTBIN

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

2. Enter cmd.exe.

3. Press OK.

The MS DOS screen appears.

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

All network connections to shared resources are displayed.

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

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

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

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

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

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

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

NOTE

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

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

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

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

For each media, enter:

mkdir \tmp\<sid>\<media_name>

NOTE

You must avoid spaces in the media path name.

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

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

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

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

NOTE

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

IFS of your IBM i.

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



28/122 PUBLIC 2011-11-07

NOTE

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

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

■ <product>_IM_OS400_PPC64

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

■ EXP*

■ JAVA*

■ SL_CONTROLLER*

■ <product>_SAPINSTGUI_WINDOWS_I386

■ <product>_IM_SAPINSTGUI_LINUX_I386

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

End of: IBM i5/OS |

4.4 Setting Up the Target System

Purpose

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

the source system.

Process Flow

Standard System

You perform the following steps on the standard system host:

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

installation guide for your SAP application.

2. You transfer the Java export files to the central system target host [page 30].

3. You install the target system [page 30].

4. If required, on the host or hosts of the application server instance, you install further

additional application server instances as described in the installation guide for your SAP

application.

Distributed System or High-Availability System

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

1. You prepare the central services instance host, the database instance host and the host of

the primary application server instance for the installation of the corresponding instances of

your target system as described in the installation guide for your SAP application.

2. You install the central services instance for the target system as described in the installation

guide for your SAP application.

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

1. You transfer the Java export files to the database instance target host [page 30].



2011-11-07 PUBLIC 29/122

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

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

server instance of the target system.

5. If required, on the host or hosts of the additional application server instance, you install

further additional application server instances as described in the installation guide for your SAP

application.

4.4.1 Transferring the Export Files to the Target Host

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

DBSIZE.XML file to the target host.

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 or 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. Transfer all files and directories (recursively) that are located on the source host in the migration

export directory <EXPDIR> from the source host to the target host.

You can choose one of the following methods:

■ Use the migration monitor with the file transfer protocol (FTP) copy option.

NOTE

Make sure that you use binary mode for transferring the files.

■ Copy the export dump directory manually to the target host.

■ The export dump directory can be shared and thus made accessible on the target host (network

share).

3. Check the permissions of the transferred files on the target host. All files have to be accessible for

user <sapsid>adm of the target system.

4.4.2 Installing the Target System

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

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

located in the following directory:



30/122 PUBLIC 2011-11-07

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

UNIX: <EXPDIR>/DB/<DATABASE>

Only valid for: MaxDB |

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

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

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

Procedure

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

2. Start SAPinst as described in the installation guide for your SAP system.

CAUTION

If you plan to use Advanced Configuration options during the SAP System Database Import,

make sure you have installed the most current version of SAPinst to avoid performance

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

service.sap.com.

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

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

Stack> .

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

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

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

required parameters.

CAUTION

■ If you perform a Unicode conversion, the data import into the target system might abort

because of missing space in the database tablespace or dbspace. Enlarge the database or

database container, in which the table DYNPSOURCE will be created in the target database.

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

system.

■ Do not create the installation directory (for example: sapinst_instdir) in the following

directories:

● UNIX: /usr/sap/<SAPSID>

● UNIX: /sapmnt/<SAPSID>

● Windows: \usr\sap\<SAPSID>

● Windows: \sapmnt\<SAPSID>

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

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

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



2011-11-07 PUBLIC 31/122

http://service.sap.com

http://service.sap.com

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

is loaded in the newly installed SAP system database.

■ When SAPinst displays the Media Browser window and asks for the Export Migration CD, enter

the path to the export directory <EXPDIR>.

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

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

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

NOTE

If you have to restart the import after an error, just restart SAPinst. The import continues

with the table that has not yet been successfully imported.

NOTE

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

follow-up activities [page 75] have been performed, you have to start the Java EE engine manually.



32/122 PUBLIC 2011-11-07

5 Database-Specific System Copy

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

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

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

CAUTION

■ You must not uninstall all application server instances of an SAP system if you want to

continue using the database instance of this SAP system. Otherwise, you delete configuration-

specific data in the database instance that is required for performing the homogeneous system

copy.

■ During the installation of the target system, the secure store must be created using the same

key phrase as the source system. Make sure that the key phrase is correct otherwise encrypted

content cannot be decrypted and that prevents the server from starting.

Process

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

■ Standard system

■ Distributed system

■ High-availability system

Standard System

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

host:


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

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

Process Flow on the Target System


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


You prepare the target system [page 41]:

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

software and to perform the database backup/restore.


2011-11-07 PUBLIC 33/122

http://service.sap.com/notes

CAUTION

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

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

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

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


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

backup/restore.

NOTE

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

solution.

End of: Windows |

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

Distributed System or High Availability System

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


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

database [page 36].

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

Process Flow on the Target System


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

guide of your SAP solution.

CAUTION

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

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

End of: Windows |


You prepare the target system [page 41]:

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

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

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

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


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

requested to perform the database backup/restore.


34/122 PUBLIC 2011-11-07

NOTE

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

solution.

End of: Windows |

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

Only valid for: Oracle |

5.1 Oracle-Specific Procedure

Purpose

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

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

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

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

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

steps are different.

Advantages

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

switches).

■ This method is faster than the Jload method.

Disadvantages

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

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

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

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

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

Prerequisites

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

system.

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

standard Oracle installation).

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

on the database instance.

■ The JAVA_HOME environment variable must point the JRE directory.

■ The backup must be done offline.



2011-11-07 PUBLIC 35/122

NOTE

The system copy procedure does not support the usage of an online backup to copy your

Java engine.

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

■ The source and target systems must be binary compatible.

NOTE

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

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

compatible.

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

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

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

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

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

5.1.1 Generating the Control File Structure

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

without further adaptations on the target system.

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

of the OraBRCOPY.SAR archive.

Prerequisites

RECOMMENDATION

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

database must still be running.

Procedure

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

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

directory and extract it using SAPCAR.

You can find the archive in the following directory:

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

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

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

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


■ Log on as one of the following users:



36/122 PUBLIC 2011-11-07

● ora<dbsid>

● <sapsid>adm

■ Enter the following commands:

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

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

End of: UNIX |


■ Log on as <sapsid>adm

■ Enter the following commands:

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

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

End of: Windows |

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

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

NOTE

If an error occurs, check the log file:

<INSTDIR>/ora.brcopy.log

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

follows.

Example

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

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

UNIX, too.

REM

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

REM CONTROL.SQL

REM

REM SAP AG Walldorf

REM Systeme, Anwendungen und Produkte in der Datenverarbeitung

REM

REM (C) Copyright SAP AG 2006

REM

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

REM Generated at:

REM Fri Sep 17 08:33:25 CEST 2006

REM for target system NEW

REM on

REM Windows 2000 5.0 x86



2011-11-07 PUBLIC 37/122

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,

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










38/122 PUBLIC 2011-11-07


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

Changes to Be Made

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

the bottom of the control.sql file:

shutdown immediate;

startup upgrade

spool utlirp.log

@?/rdbms/admin/utlirp.sql

spool off

shutdown immediate;

startup

exit

2. MAXLOGFILES 255

...

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

3. GROUP 1 (



) SIZE 50M,



2011-11-07 PUBLIC 39/122

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 the rows with ALTER TABLESPACE must be equal to the number of the corresponding

rows in the trace file.

5.1.2 Creating a Backup

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

backup with BR*Tools.

5.1.2.1 Creating an Offline Backup

Procedure

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

of the database files:

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

up with forced log switches).

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

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

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

system trees that have to be saved.

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

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

now. Proceed with the next steps.



40/122 PUBLIC 2011-11-07

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

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

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

BR*Tools .

5.1.3 Preparing the Target System (Oracle)

Prerequisites

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

Procedure

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

SAP solution.

CAUTION

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

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

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

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

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

names of the source and target system must be identical.

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

<Technical Stack> .

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

Restore).

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

The following message is displayed:



2011-11-07 PUBLIC 41/122

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


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

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

3. Restore the database files on the target system.

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

■ UNIX:

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

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

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

● /oracle/<TARGET_DBSID>/sapreorg

● /oracle/<TARGET_DBSID>/saparch

● /oracle/<TARGET_DBSID>/oraarch

● /oracle/<TARGET_DBSID>/saptrace

● /oracle/<TARGET_DBSID>/saptrace/background

● /oracle/<TARGET_DBSID>/saptrace/usertrace

● /oracle/<TARGET_DBSID>/origlogA/cntrl

● /oracle/<TARGET_DBSID>/sapdata1/cntrl

● /oracle/<TARGET_DBSID>/saparch/cntrl

● /oracle/<TARGET_DBSID>/sapcheck

■ Windows:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

UNIX

■ /oracle/<TARGET_DBSID>/saparch



42/122 PUBLIC 2011-11-07

■ /oracle/<TARGET_DBSID>/oraarch

Windows

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

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

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

To do this, enter the following command:

chown ora<target_dbsid>:dba<directory>

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

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

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

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

2. Under Security, choose Advanced.

3. Deselect Inherit from parent the permission entries….

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

from the parent to this object.

5. Choose OK.

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

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

7. Delete all other accounts.

5.1.4 Restoring the Database Files on the Target System

CAUTION

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

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

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

Procedure

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

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

Directories on UNIX

Source and Target Directory Files

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

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

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

Source: <INSTDIR> Target: <SAPINST_INSTDIR>

CONTROL.SQL

Source: <INSTDIR> init<TARGET_DBSID>.ora



2011-11-07 PUBLIC 43/122

Source and Target Directory FilesTarget: /oracle/<DBSID>/<DB_VERSION>_<BIT>/dbs

Directories on Windows


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

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

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

Source: <INSTDIR>Target: <SAPINST_INSTDIR>Target:%programfiles%\sapinst_instdir\<SAP_System_Name>\LM\ORA\COPY

\ORA

\SYSTEM\<system_variant>\<technical stack>

CONTROL.SQL

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

init<TARGET_DBSID>.ora


NOTE

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

directories shown in the table.

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

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

<system_variant>\<technical stack>

End of: Windows |

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

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

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

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

the group dba, and have the permissions 740.

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

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

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

Procedure

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

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

■ On UNIX:


Source: <INSTDIR> CONTROL.SQL



44/122 PUBLIC 2011-11-07

Source and Target Directory FilesTarget: <SAPINST_INSTDIR>

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


■ On Windows:


Source: <INSTDIR>Target: <SAPINST_INSTDIR>Target: %programfiles%\sapinst_instdir\NW04SR1\WEBAS_COPY\CENTRAL\ONE_HOST

or %programfiles%\sapinst_instdir\NW04SR1\WEBAS_COPY\DISTRIBUTED\DB

CONTROL.SQL

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


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

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

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

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

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

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

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

Note 1003028.

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

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

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

3. Shut down the Oracle database instance as follows:

sqlplus /nolog

shutdown immediate

exit

End of: Oracle |


5.2 SAP MaxDB-Specific Procedure

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

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

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

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

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

database installation method.



2011-11-07 PUBLIC 45/122



This description is not valid for the liveCache system copy.

CAUTION

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

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

database contents on the target system.

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

for example, SAPR3.

You can perform this procedure in the following ways:

■ Manual restore

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

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

installation in SAPinst.

■ Automatic restore

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

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

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

NOTE

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

Advantages

■ You can use existing offline backups.

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

Disadvantage

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

Prerequisites

■ Byte order – little-endian or big-endian

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

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

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

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

■ Data backup

You perform the complete data backup of your source database.

■ Recovery tool (manual restore)

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

more information, see:



46/122 PUBLIC 2011-11-07


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

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

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

■ Database Software

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

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

to the version on the source host.

■ Size of the data on the target system

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

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

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

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

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

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

database data volumes according to this value.

■ JRE

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

The JAVA_HOME environment variable must point to the JRE directory.

Process

Steps to Perform on the Target System

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

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

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

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

SAPinst:

■ Manual restore

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

1. Start the data recovery wizard from DBMGUI

1. Register your database instance in the DBMGUI

2. Check the database instance in the admin state.

3. Choose Recovery Recovery with Initialization ...

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

5. Specify the backup medium.

6. Start the restore procedure.



2011-11-07 PUBLIC 47/122

http://maxdb.sap.com/doc/7_6/default.htm

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

NOTE

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

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

database volumes.

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

to online if it is not already in online state.

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

backup history for update statistics in the Computing Center Management System

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

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

SDBAADAUPD

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

■ Restore by SAPinst

Enter the following information:

● Template name

● Device/file

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

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

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

NOTE

● For more information about the system copy procedure, see also SAP Notes 193816 and

151603.

● As of SAP NetWeaver 7.1 you do no longer have to perform an export of the source

system.

● With SQL Server, you can use backup images across the platforms x86, IA64, x64. That is,

you can make a backup on one type of platform and use it on another type.


5.3 MS SQL Server-Specific Procedure

48/122 PUBLIC 2011-11-07




● You can only attach SQL Server 2000 files to SQL Server 2005 but not the other way

around.

Process

1. Detach the database files from the source system database or create a backup and copy the files to

the target system.

2. Attach the database files or restore the backup of the source database on the target database server.

3. Run SAPinst to install the target system by choosing the following on the Welcome screen:

<Your Product> System Copy Target System <System Variant> Based on <Technical Stack> .

Choose the installation options exactly in the order they appear.

For more information, see the MS SQL Server installation guide for your SAP system at:

http://service.sap.com/instguides <Your SAP Product> Installation .

4. When SAPinst prompts for the database copy method, choose Homogeneous System Copy.End of: Windows | MS SQL Server |

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

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

The database-specific procedure for the creation of a system copy is based on a restore of an existing

online or offline backup. Therefore, this method is also referred to as backup/restore procedure. Since you

can use a DB2 backup cross-platform within certain limitations (see below), this method is not limited

to the homogenous system copy only.

NOTE

You can also create an SAP system copy with a DB2 database if more advanced techniques like file

system snapshots are available. The necessary procedure in this case is called database relocation. The

database relocation procedure differs significantly from the backup/restore procedure and is

not described in this guide.

For more information, see the Database Administration Guide: SAP on IBM DB2 for Linux, UNIX, and

Windows, section db2inidb Option: as snapshot.

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

documentation for your SAP component. Before you start SAPinst on the target system make sure

that all prerequisites for the SAP system installation are met. Especially, make sure that the relevant

file systems are available. For more information, see the appropriate installation guide at http://

service.sap.com/instguidesnw <Your SAP NetWeaver Release> Installation Installation – SAP

NetWeaver Systems



2011-11-07 PUBLIC 49/122


http://service.sap.com/instguidesnw


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

Disadvantages of the Backup Method

■ You cannot change the name of the database schema. The name of the database schema is the

same as that of the source system. This implies that the name of the database connect user does

not change either.

■ You cannot copy an individual MCOD component to another system. You can only copy the

complete system.

Prerequisites

■ It must be possible to restore the backup of the source system on the platform of the target system.

NOTE

With DB2, you can use backup images cross-platform within certain limitations. If you want

to use the backup/restore method between different platforms, you must follow the

additional instructions in SAP Note 628156.

For more information about cross-platform backups, also see Backup and restore operations between

different operating systems and hardware platforms in the IBM DB2 Information Center at http://

publib.boulder.ibm.com/infocenter/db2luw/v9r7/ index.jsp?topic=/

com.ibm.db2.luw.admin.ha.doc/doc/c0005960.html.

■ If errors occur when restoring the backup on the target system, the complete restore must be

repeated.

Process

1. You perform an online or offline backup.

If you use an online backup to copy your system, a rollforward of your database is required after

the database restore on the target system. As a prerequisite, the respective database logs must be

accessible. We, therefore, recommend that you include the necessary log files in the backup image.

As of DB2 V9.5, logs are included in the online backup image as long as the option EXCLUDE LOGS

is not specified.

NOTE

To export the database content for Java, you can also use the database-specific method

(backup/restore).

2. To create a target system, run SAPinst on the target system host by choosing the following on the

Welcome screen:

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

Perform the installation options in the given sequence and follow the instructions on the SAPinst

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



50/122 PUBLIC 2011-11-07


http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.ha.doc/doc/c0005960.html



CAUTION

Be aware of the following constraints when using the backup method for a homogeneous

system copy:

■ Since you cannot change the name of the database schema, you can neither change the

connect user. During the dialog phase you have to make sure that you enter the name

of the connect user exactly as you did on your source system.

■ The tablespace names remain the same during the database restore. However, you can

change them after the installation.

■ If you want to change the name or the location of the DB2 container on the target system,

you have to adapt the DB2 container paths or names in the redirected restore script and

then perform a redirected restore. For more information, see the documentation Database

Administration Guide: SAP on IBM DB2 Universal Database for UNIX and Windows, section Usage of

Tool brdb6brt.

3. Multi-Partition Database Environments only: Add database partitions

If you copy a system with multiple database partitions, the target system must have the same

number of partitions as the source system. For more information, see Setting up partitioned database

environments in the IBM DB2 Information Center at:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/ index.jsp?topic=/

com.ibm.db2.luw.qb.server.doc/doc/t0023605.html

4. Restore your database.

To restore your database, you can choose between one of the following options:

■ Simple database restore

To perform a database restore, use the DB2 RESTORE command. For more information, see the

IBM manual DB2 Command Reference.

NOTE

With a simple restore, you can neither change the name nor the location of DB2

containers.

■ Redirected restore

This is the recommended method.

A redirected restore allows you to change the name or the location of the DB2 container. To

perform a redirected restore, you use the DB2 RESTORE DATABASE command with the REDIRECT

GENERATE SCRIPT option. For more information, see RESTORE DATABASE command in the IBM

DB2 Information Center at:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/

com.ibm.db2.luw.admin.cmd.doc/doc/r0001976.html.

Alternatively, you can use the tool brdb6brt that retrieves a database backup and creates a

CLP script to restore this backup image. Since brdb6brt needs to connect to the source system,

the source system must be available. For more information about how to use the tool



2011-11-07 PUBLIC 51/122

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.qb.server.doc/doc/t0023605.html

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.qb.server.doc/doc/t0023605.html

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.cmd.doc/doc/r0001976.html

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.cmd.doc/doc/r0001976.html

brdb6brt, see Redirected Restore Using brdb6brt in the Database Administration Guide: SAP on IBM DB2

Universal Database for UNIX and Windows.

You cannot use the brdb6brt tool to perform a redirected restore. By default, the brdb6brt

tool is not available in a Java only system. If you want to use it, you have to download from

SAP Service Marketplace. brdb6brt is part of the ABAP kernel.

NOTE

You do not have to export the database content for backup/restore with Jload. During

the dialog phase, SAPinst asks if you want to export the database content using database

tools or using Jload. If you choose the database tools, Jload is not used.

For more information, see SAP Note 1238351.

If you have used an online backup, you have to make sure that you have access to the log files that

were created during the online backup. You also have to perform a rollforward operation to bring

the database into a consistent state.

You can now continue with the installation.

Follow-up Activities

After the installation on the target system, you perform the following steps:

■ The tablespaces SYSTOOLSPACE and SYSTOOLSTMPSPACE are used by certain DB2 tools and SQL

administrative routines to store historical and configuration information. We recommend that

you drop and re-create these tablespaces in the target system as follows:

1. Log on to the database server of the target system as user db2<dbsid>.

2. Generate the DDL statements for the tablespaces of the system by entering the following

command on the DB2 command line:

db2look -d <DBSID> -l -o <filename>.sql

3. Drop both tablespaces by entering the following command:

db2 drop tablespace SYSTOOLSPACE, SYSTOOLTMPSPACE

4. Look up the CREATE TABLESPACE statements for SYSTOOLSPACE and SYSTOOLSTMPSPACE in

<filename>.sql.

5. Execute both statements on the DB2 command line.

For more information, see SYSTOOLSPACE and SYSTOOLSTMPSPACE tablespaces in the IBM DB2

V9.5 Information Center at http://publib.boulder.ibm.com/infocenter/db2luw/ v9r5/topic/

com.ibm.db2.luw.admin.gui.doc/doc/c0023713.html.

■ If you performed a redirected restore, check all settings of the database manager and database

configuration parameters. Specifically, make sure that the following configuration parameters

point to the correct path:

● DIAGPATH (DBM)

● JDK_PATH (DBM)

● DFTDBPATH (DBM)



52/122 PUBLIC 2011-11-07


http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.gui.doc/doc/c0023713.html

http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.gui.doc/doc/c0023713.html

● Path to log files (DB)

● If set, NEWLOGPATH (DB), OVERFLOWLOGPATH (DB), FAILARCHPATH (DB) and MIRRORLOGPATH (DB)

More Information

■ Database Administration Guide: SAP on IBM DB2 for Linux, UNIX, and Windows and Database Administration

Using the DBA Cockpit: IBM DB2 for Linux, UNIX, and Windows at:

http://service.sap.com/instguidesnw <Your SAP NetWeaver Release> Operations Database-

Specific Guides

■ IBM DB2 9.7 Information Center at:http://publib.boulder.ibm.com/infocenter/db2luw/v9r7

■ IBM Manuals for DB2 9.7 at:

http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg27015148

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

Only valid for: IBM DB2 for i5/OS |

5.5 IBM DB2 for i Specific Procedure

In an SAP system environment, you can create a homogeneous system copy of a DB2 database using

theSAV/RSTLIB method.

A system copy consists of the export of the source system and the import of the target system. The

export is normally done by SAPinst. However, for the homogenous system on IBM DB2 for i using the

SAV/RSTLIB method you can only perform a SAVLIB of the library R3<SID>DATA. Finally, you have to

copy and transfer the saved database library to the IBM i host on which you want to create the target

system. The import will be performed similar to a normal installation.

You have to start the SAPinst by choosing <Your Product> System Copy Target System <System

Variant> Based on <Technical Stack> . When SAPinst prompts for the database copy method, you choose

Homogeneous System Copy for the database specific method. This method gives you the opportunity to

restore the saved library by using RSTLIB. SAPinst creates a restore command from your entered input

and restores the database library automatically.

Advantage of the Offline System Copy Method

This method is faster than the database-independent method [page 17].

For more information, see SAP Note 585277.End of: IBM DB2 for i5/OS |

Only valid for: IBM DB2 for z/OS |

5.6 IBM DB2 for z/OS Specific Procedures

In an SAP system environment, you can create a homogeneous system copy of a DB2 database using

the offline system copy method.


5.5 IBM DB2 for i Specific Procedure

2011-11-07 PUBLIC 53/122


http://publib.boulder.ibm.com/infocenter/db2luw/v9r7

http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg27015148


This document assumes that the database schema of your SAP system is SAPR3. If you employ a different

schema, adapt the references to SAPR3 in the following SQL statements and jobs to reflect the actual

schema name.

The following section describes an offline system copy method for SAP systems on IBM DB2 for z/

OS.

For this example system copy, the high level qualifier of the source system is assumed to be D8A0 of the

target system D8B0.

System Copy Mode

If you install a primary application server instance on the target system, make sure that you select

Custom Mode.

Advantage of the Offline System Copy Method

This method is faster than the database-independent method [page 17].

Restriction of the Offline System Copy Method

At the moment, you cannot copy an individual MCOD component to another system. You can only

copy the complete system.

NOTE

The offline system copy must be performed by an experienced database administrator.

You can find an adapted procedure for an online system copy in the IBM documentation High

Availability for SAP on zSeries Using Autonomic Computing Technologies.

Prerequisites

The following prerequisites must be fulfilled to use this method:

■ The permissions of the source and target systems must be completely separate. The source system

must not be able to use the resources of the target system, and the target system must not be able

to use the resources of the source system.

■ RACF authorization for the target DB2 subsystem is complete.

■ Source and target systems must work with DB2 managed objects.

■ Tablespaces are not partitioned.

■ The system copy is made from a nondata sharing system to a nondata sharing system.

■ Procedures of the source and the target system are defined in the DB2 PROCLIB.

■ Source and target systems have their appropriate entries in the APF list.

■ Volumes of the source and target systems are managed by SMS.

■ Source and target systems run with the same DB2 service level.

Variables Used in this Procedure

■ Source System = D8A0



54/122 PUBLIC 2011-11-07

■ Target System = D8B0

■ Storage Group = TEMPORA

■ High Level Qualifier = HLQ

■ Boot Strap Data Set = BSDS

Main Steps in this Procedure

The following sections contain the detailed steps involved in the homogeneous system copy procedure

for DB2 for z/OS.

In the following steps, storage groups must be modified to apply the new high level qualifier. This can

be achieved by dropping and recreating the storage groups with the new high level qualifier (and

volumes).

To prepare the DB2 catalog of the target system, you must run JCL jobs created by SQLs running in

the source system.

The offline system copy can be divided into the following steps:

1. Check the Source System for Consistency

2. Stop and Restart the Source System

3. Run SQLs in the Source System

4. Capture View Definitions (if you intend to change the schema name.)

5. Stop the Source System

6. Print the Bootstrap Data Sets

7. Make Copies of the Source Data Sets

8. Create the Target System

9. Post-process the Target System

10. Changing the VCAT of the Target System

11. Changing the Schema of the Target System (DB2 V9 only)

12. Adapting WLM Application Environments for DB2 Stored Procedures

JCL jobs and SQL Statements

The JCL jobs and SQL Statements are now located in a compressed file (.zip) that is attached to SAP

Note 680746.

The path for each file is given in the section that previously contained the code.

5.6.1 Step 1: Check Consistency

The following is a list to help you check the source system for consistency.

■ Check if there are threads.

■ Check for authorized utilities using the following:

DISPLAY DATABASE(*) UTIL(*) and press [ENTER]

Your output should be:



2011-11-07 PUBLIC 55/122


No authorized utility found.

If there are running utilities, you must shut them down properly before continuing.

■ Ensure that all DB2 objects of the source system are started RW mode.

This can be checked with

DISPLAY DATABASE(*) SPACENAM(*)

with keyword

RESTRICT.

For more information, see DB2 UDB for z/OS and OS/390 Command Reference (SC26-9932-05).

■ If there are no objects in pending status, the source system must be stopped.

5.6.2 Step 2: Stop and Restart the Source System

Now you must stop and restart the source system with the ACCESS (MAINT) command option to

prohibit any authorization IDs other than install SYSADM and install SYSOPR.

5.6.3 Step 3: Run SQL Statements in the Source System

Prerequisites

As described earlier in this section, you must stop and restart the source system with the ACCESS(MAINT)

command option to prevent changes and to obtain consistent data.

Information for IBM DB2 V9 for z/OS

If you are running your system with DB2 V9, note that SQL Statements 2 through 9, as well as Creating

a New Storage Group Using the HLQ of the Target System are not relevant tasks for this procedure.

Activities

Execute all the following SQL statements in the source system:

5.6.3.1 SQL Statement Number 01

This statement is located at

HSCProcedure\Step3\STMT01.SQL

in the .zip file [page 53] attached to SAP Note 680746. For more information, see the section JCL Jobs and

SQL Statements.

With this statement, you identify user-defined indexes that you need to change in the DB2 catalog. For

more information, see Step 8e: Changing the User-Defined Indexes in the DB2 Catalog [page 67].

Output

The output of this statement is similar to the following:



56/122 PUBLIC 2011-11-07


EXAMPLE

---------+---------+---------+---------+---------+-----

NAME DBNAME INDEXSPACE

---------+---------+---------+---------+---------+-----

SYSTBLSP~0 DSNDB06 SYSTBLSP

SYSTABLE~0 DSNDB06 SYSTABLE

SYSIXPART~0 DSNDB06 SYSIXPAR





SQL Statements.

With this statement, you identify all databases that you want to stop at a later point in time in the target

system:

NOTE

This task is not relevant for DB2 V9.

Output


EXAMPLE

-STOP DATABASE (A000XAAA)

-STOP DATABASE (A000XAAB)

-STOP DATABASE (A000XAAC)

-STOP DATABASE (A000XAAD)

-STOP DATABASE (A000XAAE)

-STOP DATABASE (A000XAAF)

-STOP DATABASE (A000XAAG)

-STOP DATABASE (A000XAAH)

-STOP DATABASE (A000XAAI)

-STOP DATABASE (A000XAAJ)

-STOP DATABASE (A000XAAK)

-STOP DATABASE (A000XAAL)

.

.



2011-11-07 PUBLIC 57/122


.

and so on





SQL Statements.

With this statement, you identify all tablespaces to be connected at a later point in time to the temporary

storage group TEMPORA:

NOTE


Output


EXAMPLE

ALTER TABLESPACE A000XAAA.ABAPTREE USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ABAPTREE USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADIRACCE USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADOWNERR USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADRCOMCS USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADRDIFIN USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADRGS2 USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADR10 USING STOGROUP TEMPORA; COMMIT;





SQL Statements.

With this statement, you identify all indexes to be connected with storage group TEMPORA.

NOTE




58/122 PUBLIC 2011-11-07



Output


EXAMPLE

ALTER INDEX "DSNACC"."UTLEX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTLSTX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTPEBX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTPETX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTPEX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTPRCX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTRESTARTX" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTRESTART2X" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTTMDX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTTMPX01" USING STOGROUP TEMPORA; COMMIT;

.

.

and so on





SQL Statements.

Storage groups in the target system still contain the high level qualifier of the source system. With this

statement, you identify storage groups to be dropped at a later point in time with the following

statement:

NOTE


Output


EXAMPLE

DROP STOGROUP SYSDEFLT; COMMIT;

DROP STOGROUP SAPU1I; COMMIT;

DROP STOGROUP SAPU1D; COMMIT;



2011-11-07 PUBLIC 59/122


DROP STOGROUP SAPSOI; COMMIT;

DROP STOGROUP SAPSOD; COMMIT;

DROP STOGROUP SAPESI; COMMIT;

DROP STOGROUP SAPESD; COMMIT;

DROP STOGROUP SAPPRI; COMMIT;

DROP STOGROUP SAPPRD; COMMIT;

DROP STOGROUP SAPLOI; COMMIT;

.

.

and so on





SQL Statements.

NOTE


With this statement, you identify storage groups to be created at a later point in time with the high

level qualifier of the target system. In this case, we assume that FR01 is the high level qualifier of the

target system.

Storage Group Naming Conventions

Some storage group names may have to be adapted for all storage groups for which the creator is your

SQLID and not SAPR3. The naming convention is as follows:

ABAP Storage Group Naming Convention

Schema Storage Group Name

SAPR3 SAP<SI><I|D>

other <SID><SI><I|D>

NOTE

<SI> signifies the two-character STORAGEID of the table type (TABART).

Java Storage Group Naming Convention

Schema Storage Group Name

<schema> <schema>



60/122 PUBLIC 2011-11-07


CAUTION

For Java, the schema name is also the name of the storage group. You must not change the name

of the storage group. Be aware that as of DB2 V9, you can use the CATMAINT utility to globally

switch a schema name.

Output


EXAMPLE

CREATE STOGROUP SYSDEFLT VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPU1I VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPU1D VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPSOI VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPSOD VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPESI VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPESD VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPPRI VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPPRD VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPLOI VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPLOI VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPLOD VOLUMES('*') VCAT FR01; COMMIT;; COMMIT;

.

.

and so on





SQL Statements.

With this statement, you connect tablespaces with their previous storage groups, which now contain

the high level qualifier of the target system.

NOTE


Output




2011-11-07 PUBLIC 61/122


EXAMPLE

ALTER TABLESPACE "DSNRLST"."DSNRLS01" USING STOGROUP SYSDEFLT;COMMIT;

ALTER TABLESPACE "BCXXXC5E"."SYNCLOG" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXXC5E"."DDDBRTH" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXX3UT"."DDDBTAB" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXX3UT"."LDDDBT3U" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXX3UT"."DDDBRTX" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXXC5E"."JMSDMSG" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "CC390"."UTTEMPL" USING STOGROUP SYSDEFLT;COMMIT;

ALTER TABLESPACE "CC390"."UTPROC" USING STOGROUP SYSDEFLT;COMMIT;

ALTER TABLESPACE "CC390"."UTRSTRT" USING STOGROUP SYSDEFLT;COMMIT;

.

.

and so on





SQL Statements.

With this statement, you connect indexes with their previous storage groups, which now contain the

high level qualifier of the target system.

NOTE


Output


EXAMPLE

ALTER INDEX "SAPD5Z"."SYSTBLSPß0" USING STOGROUP SYSDEFLT;COMMIT;

ALTER INDEX "SAPD5Z"."SYSTABLEß0" USING STOGROUP SYSDEFLT;COMMIT;

ALTER INDEX "SAPD5Z"."SYSIXPARTß0" USING STOGROUP SYSDEFLT;COMMIT;

ALTER INDEX "STEM"."DSNARL01" USING STOGROUP SYSDEFLT;COMMIT;

.

.

and so on



62/122 PUBLIC 2011-11-07






SQL Statements.

With this statement, you identify all databases to be started after DB2 catalog manipulations.

NOTE


Output


EXAMPLE

-START DATABASE (A000XAAA)

-START DATABASE (A000XAAB)

-START DATABASE (A000XAAC)

-START DATABASE (A000XAAD)

-START DATABASE (A000XAAE)

-START DATABASE (A000XAAF)

-START DATABASE (A000XAAG)

-START DATABASE (A000XAAH)

-START DATABASE (A000XAAI)

-START DATABASE (A000XAAJ)

-START DATABASE (A000XAAK)

-START DATABASE (A000XAAL)

.

.

and so on

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

DB2 V9 adds the capability to change the VCAT name to the CATMAINT utility. This new capability

facilitates homogenous system copy. Moreover, the CATMAINT utility can change the schema and

creator of objects.

If you intend to also change the schema name as part of the homogeneous system copy, for example

for SAP Java systems, you need to capture the view definitions in this step. This is necessary since

renaming the schema using CATMAINT requires that no views exist on the tables for which a VCAT name

is changed. Therefore, the view definitions are exported in this step using R3ldctl.



2011-11-07 PUBLIC 63/122


As part of the post-processing steps that are performed in the target system, the saved view definitions

are later used to re-create the views in the target system. The views may also be saved and later re-

created in the target system using alternative tools.

Procedure

To export the view definitions using R3ldctl:

1. Run R3ldctl without parameters to create the DDLDB2.TPL file, the SAPVIEW.STR file, and others

2. Store these files

5.6.5 Step 5: Stop the Source System

Stop the source system with the following command option:

MODE (QUIESCE)

5.6.6 Step 6: Making Copies of Source Data Sets

With this step, you make copies of the source data sets, which includes:

■ DB2 bootstrap data sets

■ DB2 logcopy data sets

■ All DB2 VSAM data sets belonging to the source system

With these JCL jobs, you can make copies of the source data sets:

■ HSCProcedure\Step6\DUMPA0.JCL



■ HSCProcedure\Step6\DUMPLIB.JCL

■ HSCProcedure\Step6\DUMPLOG.JCL

■ HSCProcedure\Step6\DUMPREST.JCL

All scripts are located in the .zip file [page 53] attached to SAP Note 680746. For more information, see

the section JCL Jobs and SQL Statements.

NOTE

The source system can be restarted now. It is no longer needed for the following system copy

process.

5.6.7 Step 7: Creating the Target System

With the following JCL jobs, you create the target system.

In the first step, the dumps of the source system have to be restored. All data sets of the source system

have to be restored with the high level qualifier of the target system.



64/122 PUBLIC 2011-11-07


All statements are located in the .zip file [page 53] attached to SAP Note 680746. For more information,

see the section JCL Jobs and SQL Statements.

■ HSCProcedure\Step7\RSTOREA0.JCL



■ HSCProcedure\Step7\RSTORELI.JCL

■ HSCProcedure\Step7\RSTORELO.JCL

■ HSCProcedure\Step7\RSTORERE.JCL

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

Before starting the target system, the BSDS must be changed.

The JCL jobs listed here are located in the .zip file [page 53] attached to SAP Note 680746. For more

information, see the section JCL Jobs and SQL Statements.

1. Change the HLQ entry in the BSDS of the target system, using the HLQ D8B0.

The corresponding JCL job is located at

HSCProcedure\Step9a\CHGBSDS1.JCL

in the .zip file.

2. Change the log entries in the BSDS. The START and END RBA information as of utility DSNJU004

have to be used for the target system as follows:


HSCProcedure\Step9a\CHGBSDS2.JCL

in the .zip file.

After changing the BSDS with these scripts, you can start the target system.

5.6.9 Step 9b: Start the Target System

When you start the DB2 target system for the first time, the system is still working with the work file

database of the source system. However, access fails with insufficient access authority, as seen in the

log.

Partial example of a LOG when you start the target system for the first time:

SYNTAX

.

.

.

. DSNR005I -D8B0 RESTART...COUNTS AFTER FORWARD 604 RECOVERY IN COMMIT=0, INDOUBT=0 DSNR006I -D8B0 RESTART...COUNTS AFTER BACKWARD 605 RECOVERY



2011-11-07 PUBLIC 65/122



INFLIGHT=0, IN ABORT=0, POSTPONED ABORT=0 DSNP012I -D8B0 DSNPCNP0 - ERROR IN VSAM CATALOG 606 LOCATE FUNCTION FOR D8A0.DSNDBC.DSNDB07.DSN4K01.I0001.A001 CTLGRC=AAAAAA08 CTLGRSN=AAAAAA08 CONNECTION-ID=D8E0, CORRELATION-ID=003.RCRSC 02, LUW-ID=* IKJ56228I DATA SET D8A0.DSNDBC.DSNDB07.DSN4K01.I0001.A001 NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED DSNB207I -D8B0 DYNAMIC ALLOCATION OF DATA SET 608 FAILED. REASON=17080002.DSNAME=D8A0.DSNDBC.DSNDB07.DSN4K01.I0001.A001 DSNT501I -D8B0 DSNITFFS RESOURCE UNAVAILABLE 609 CORRELATION-ID=D8E0 CONNECTION-ID=D8E0 LUW-ID=D8E0.D8E0.000000000000=0 REASON 00D70024....and so on

We strongly recommend that you maintain different RACF settings for different DB2 subsystems. If

not, the target system has access to the data sets of the source system and the data of the source system

could be changed by mistake.

The work file database data must be changed later in the clone process.

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

With this JCL job, you create a new STOGROUP using the HLQ of the target system (D8B0).

This JCL job is located at

HSCProcedure\Step9c\CRTMPSTO.JCL

.zip file [page 53] attached to SAP Note 680746. For more information, see the section JCL Jobs and SQL

Statements.

NOTE


5.6.11 Step 9d: Stopping Index Spaces

With this JCL job, you stop the appropriate index spaces.

You find a list of index spaces in the output of SQL statement number 1 [page 56].

The JCL job is located at

HSCProcedure\Step9d\STOPIDXS.JCL


SQL Statements.



66/122 PUBLIC 2011-11-07



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

After starting the target system, the user-defined indexes (the output of SQL statement number 1 [page 56])

in the DB2 catalog must be changed, working with the new HLQ of the target system D8B0. The

following example script can be used to carry out this procedure.

Change the user-defined DB2 catalog indexes using the new storage group TEMPORA.


HSCProcedure\Step9e\ALTERIDX.JCL


SQL Statements.

5.6.13 Step 9f: Restart the Index Spaces

At this point, you must restart the index spaces.

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

To create the temporary files for the DB2 target system:

1. Run part of DSNTIJTM to create temporary files for DB2. DSNTIJTM was generated by DSNTINST

(optional) or consists of a manually changed copy from another existing DB2 subsystem.

The JCL job is located in the .zip file atHSCProcedure\Step9g\CRTTMPFL.JCL.

The .zip file [page 53] attached to SAP Note 680746. For more information, see the section JCL Jobs

and SQL Statements.

2. Stop and restart the DB2 subsystem. The error as described in Step 6: Make Copies of the Sources Data

Sets [page 64] should not occur since DB2 is working with the new temporary files.

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

In the next step, the work file database is changed to use the new HLQ D8B0.

Procedure

To change the work file database:

1. Drop work file database DSNDB07 in the target system, delete the clusters for 4K and 32K and create

them again.

2. Stop and restart the target system.



2011-11-07 PUBLIC 67/122



Error message IKJ56228I should not appear because DB2 is now working with its own work file

database.

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

To allow communication with the SAP application servers of the DB2 target system, you must adjust

the DDF location name and port number.

Procedure

To adjust the DDF location name and port number, run the DB2 utility DSNJU003 with the option

DDF to specify the location name and port number.

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

The target system with the new HLQ D8B0 still works with storage groups using VCAT D8A0.

In the following steps, the DB2 catalog is manipulated by stopping the databases, altering tablespaces

and indexes, dropping and creating storage groups with the new VCAT D8B0, altering tablespaces and

indexes using the new storage groups, and starting all databases.

The objects to be manipulated are identified by the results of previously described SQL statements.

All SQL statements listed here are located in the.zip file [page 53] attached to SAP Note 680746. For more

information, see the section JCL Jobs and SQL Statements.

Procedure

1. Stop all databases


HSCProcedure\Step10\STOPDBS.JCL.

2. Alter tablespaces using storage group TEMPORA


HSCProcedure\Step10\ALTERTBS.JCL.

3. Alter indexes using storage group TEMPORA


HSCProcedure\Step10\ALTERIDX.JCL.

4. Drop the storage groups


HSCProcedure\Step10\DROPSTG.JCL.

5. Create the storage groups




68/122 PUBLIC 2011-11-07


HSCProcedure\Step10\CREATSTG.JCL.

6. Alter tablespaces using their previous storage group


HSCProcedure\Step10\ALTERTB2.JCL.

7. Alter indexes using their previous storage group


HSCProcedure\Step10\ALTERID2.JCL.

8. Start all databases


HSCProcedure\Step10\STARTDBS.JCL.

If necessary, change the user authorizations of the target system. The DB2 catalog still contains the

authorizations of the source system.

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

To change the VCAT that is used for the storage groups of your SAP tables and indexes, proceed as

follows.

Procedure

1. Ensure that the DB2 EMD pool and DB2 EDM DBD cache have at least the following sizes:

■ EDMPOOL ≥ 200000 KB

■ EDMDBDC ≥ 300000 KB

2. Call the CATMAINT utility with the UPDATE VCAT option to switch the VCAT name

3. Reinstate the original sizes of EDMPOOL and EDMDBDC.

4. Start the DB2 subsystem in regular mode

If necessary, change the user authorizations of the target system. The DB2 catalog still contains the

authorizations of the source system.

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

To change the schema or creator name of your SAP tables and indexes, proceed as follows. This approach

requires that you have previously started R3ldctl on your source system to capture the view definitions

of the SAP system.

Procedure

1. If user-defined materialized query tables or triggers exist, save their definitions in a separate place.

2. Delete all views, materialized query tables, and triggers that exist on the SAP tables.



2011-11-07 PUBLIC 69/122

3. Ensure that the DB2 EMD pool and DB2 EDM DBD cache have at least the following sizes:

■ EDMPOOL ≥ 200000 KB

■ EDMDBDC ≥ 300000 KB

4. Call the CATMAINT utility with the SCHEMA SWITCH option to switch the schema name.

5. Reinstate the original sizes of EDMPOOL and EDMDBDC.

6. Start the DB2 subsystem in regular mode.

7. Recreate the views by implementing the following steps:

1. Generate the R3load task files by submitting the following command:

R3load -ctf I SAPVIEW.STR DDLDB2.TPL SAPVIEW.TSK DB2 -l SAPVIEW.log

2. Create an SAPVIEW.cmd file to prepare the recreation of the views. This file can contain the

following lines for example:

EXAMPLE

tsk: "SAPVIEW.TSK"

icf: "SAPVIEW.STR"

dcf: "DDLDB2.TPL"

dat: null

dir: null

ext: null

3. Call R3load with the option

-i SAPVIEW.cmd -dbcodepage <codepage> -l SAPVIEW.log

to re-create the views.

8. If user-defined materialized query tables or triggers exist, re-create them.

5.6.20 Step 12: Adapting WLM Application Environments for DB2 Stored Procedures

The WLM environments of the WLM-established stored procedures need to be changed if the target

system is running with other WLM environments.

Procedure

To change the WLM environments of the WLM-established stored procedures, carry out the following

steps:

1. Create WLM application environments for the DB2 stored procedures as described in the SAP DBA

Guide: DB2 for z/OS.

2. Use the ALTER PROCEDURE statement as described in the IBM documentation DB2 for z/OS SQL

Reference.End of: IBM DB2 for z/OS |



70/122 PUBLIC 2011-11-07

6 Copying Single Instances Only

If you want to copy single instances of your SAP system only, you can use one of the following

procedures, depending on your use case:

■ Copying the Primary Application Server [page 71]

■ Copying the Database Only – Move [page 71]

■ Copying the Database Only – Refresh [page 73]

CAUTION

You cannot copy single usage types.

6.1 Copying the Primary Application Server Instance Only

As of SAP NetWeaver based on kernel 7.1, you can copy a primary application server instance only.

With this procedure, you can move a primary application server instance to a different host within

your system.

Procedure

1. Shut down all application servers.

2. Uninstall the old primary application server instance.

3. On your target host, run SAPinst on UNIX or Windows [page 20] or run SAPinst on IBM i [page 23].

4. On the Welcome screen, choose <Your Product> System Copy Target System Distributed System or High-

Availability System Based on <Technical Stack> Primary Application Server Instance .

5. After the installation has finished, restart all additional application server including the instance

services.

6.2 Copying the Database Only – Move

You can use this procedure to move a database instance to a different host within your system. The

move can be done using either database-specific methods or the SAP standard method based on R3load/

Jload.

CAUTION

■ The DBSID must not be changed.


6.1 Copying the Primary Application Server Instance Only

2011-11-07 PUBLIC 71/122

■ When copying the database only, you cannot change to another database but need to perform

a database-homogeneous copy.

■ The old database instance cannot be uninstalled using the SAPinst based uninstall procedure.

This always deletes the current database of the system.

Procedure

1. On the source host, run SAPinst on UNIX or Windows [page 20] or run SAPinst on IBM i [page 23] to

perform the export.

2. If you perform the export using R3load/Jload, on the Welcome screen, choose <Your Product>

System Copy Source System Based on <Technical Stack> Database Instance Export to export the

database.

If you perform the export using database-specific tools, you must start them manually.

3. On the target host, stop all SAP instances.

4. On the target system, run SAPinst and choose <Your Product> System Copy Target System <System

Variant> Based on <Technical Stack> Database Refresh or Move to install the database.

NOTE

Since the target database instance is to replace the source database, do not change the DBSID.

5. When SAPinst has completed the installation of the database, restart your system including all

instance services.

6. Shut down the old database instance.

7. Only valid for: UNIX | MaxDB |

Set up the xuser entries from the home directory of the user <sapsid>adm on each application

server as follows:

xuser -U <key> -u <dbuser>,<password> -d <dbsid> -n <dbhost> -S SAPR3 -t 0 -I 0 set

The required keys and dbusers are as follows:

■ Key DEFAULT with dbuser SAP<SID>

■ Key c with dbuser control

■ Key c_j2ee with dbuser control

■ Key w with dbuser superdbaEnd of: UNIX | MaxDB |

8. Only valid for: Windows | MaxDB |

Set up the xuser entries from the home directory of the users <sapsid>adm and

SAPService<SID> on each application server as follows:

xuser -c <os_user> -U <key> -u <dbuser>,<password> -d <dbsid> -n <dbhost> -S SAPR3

-t 0 -I 0 set

The required keys and dbusers are as follows:

■ Key DEFAULT with dbuser SAP<SID>

■ Key c with dbuser control

■ Key c_j2ee with dbuser control


6.2 Copying the Database Only – Move

72/122 PUBLIC 2011-11-07

■ Key w with dbuser superdbaEnd of: Windows | MaxDB |

6.3 Copying the Database Only – Refresh

With this procedure, you can refresh the content of an existing database without having to copy the

primary application server instance and to reinstall additional applications servers. The refresh can be

done using either database-specific methods or the SAP standard method based on R3load/Jload.

CAUTION

■ When copying the database only, you cannot change to another database but need to perform

a database-homogeneous copy.

Prerequisites

The source system and the target system already exist.

Procedure

1. On the source system, note down the IDs for each of the Java instances in the profile of the

application server.

The ID is stored in the instance as parameter j2ee/instance_id.

2. On the source system, run SAPinst on UNIX or Windows [page 20] or run SAPinst on IBM i [page 23] to

perform the export.

3. If you perform the export using R3load/Jload, on the Welcome screen, choose <Your Product>

System Copy Source System Based on <Technical Stack> Database Instance Export to export the

database.

If you perform the export using database-specific tools, you must start them manually.

4. On the target system, stop all SAP instances.

5. Run SAPinst and choose <Your Product> System Copy Target System <System Variant> Based on

<Technical Stack> Database Refresh or Move to install the database.


CAUTION

On IBM i, you have to delete your database libraries manually before you start the installation.

Make sure that these libraries are currently not added to any library list. To delete a library,

use the command DLTLIB.

For ABAP, delete the libraries: R3<SID>DATA and R3<SID>JRN.

For Java, delete the libraries: SAP<SID>DB and SAP<SID>JRN.

Use the command DSPJOBLOG to analyze any upcoming error. Finally choose Next to start the

installation.

End of: IBM i5/OS |



2011-11-07 PUBLIC 73/122

6. When SAPinst has completed the installation of the database, adapt the profiles in the application

server on the target system by reassigning the profile IDs of the Java instances. Make sure that they

are the same as on the source system.

NOTE

If there are more application servers on the target system than on the source system, you

have to reinstall the ones that additionally exist on the target system.

EXAMPLE

Source System:

ABC_DVEBMGS88_<host1>:j2ee/instance_id = ID8873787

ABC_D00_<host1>:j2ee/instance_id = ID32225

ABC_D20_<host2>:j2ee/instance_id = ID2078823

Target System (before reassignment):

XYZ_DVEBMGS77_<host1>:j2ee/instance_id = ID7732291

XYZ_D00_<host2>:j2ee/instance_id = ID74637


Target System (after reassignment):

XYZ_DVEBMGS77_<host1>:j2ee/instance_id = ID8873787



CAUTION

One application server (AS) is assigned to exactly one Java instance, and the other way around.

That means that, in the target system, you need to assign every Java instance in the database to

exactly one application server. You cannot assign the same Java instance to more than one

application server.



74/122 PUBLIC 2011-11-07

7 Follow-Up Activities

To finish the system copy of your SAP system:

■ Perform follow-up activities in the target system [page 75]

NOTE

The Java EE 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 EE engine manually.

7.1 Performing Follow-Up Activities in the Target System

To complete the system copy process, you need to perform several follow-up activities on the target

system.

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

For more information about ordering and installing the SAP license, see the SAP Library [page 9] at

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

7.1.2 Performing Follow-Up Activities for Java

Depending on the software units contained in your target system, you have to perform general and

software unit-specific configuration steps:

■ General follow-up activities [page 75]

■ Software Unit-specific follow-up activities [page 76]

7.1.2.1 General Follow-Up Activities

You have to perform the following activities for all software units of the copied SAP system.



2011-11-07 PUBLIC 75/122

7.1.2.1.1 Generating Public-Key Certificates

Reconfiguring the Public-Key Certificates

After the system copy, the public-key certificates are not correct on the target system. You need to

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

SAP NetWeaver Library: Function-Oriented View Security User Authentication and Single Sign-On Integration

in Single Sign-On (SSO) Environments Single Sign-On for Web-Based Access Using Logon Tickets Using Logon

Tickets with AS Java Configuring the AS Java to Issue 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 [page 9] at:

SAP NetWeaver Library: Function-Oriented View Security User Authentication and Single Sign-On Integration in

Single Sign-On (SSO) Environments Single Sign-On for Web-Based Access Using Logon Tickets Using Logon Tickets

with AS ABAP Configuring the AS ABAP to Accept Logon Tickets Accepting Logon Tickets Issued by the AS

Java .

7.1.2.2 Software Unit-Specific Follow-Up Activities

You have to perform the following activities for specific software units of the copied SAP system.

7.1.2.2.1 AS Java: Adobe Document Services

Procedure

Copying Files to the Target System

After performing a system copy, some additional files need to be copied manually from the original

ADS system to the target system.

1. Copy the following files and subdirectories:

■ DIR_GLOBAL\AdobeDocumentServices\TrustManagerService\trust\*.*

■ DIR_GLOBAL\AdobeDocumentServices\JobProfiles\Custom\*.*

■ DIR_GLOBAL\AdobeDocumentServices\FontManagerService\fonts\customer\*.*

■ DIR_GLOBAL\AdobeDocumentServices\lib\custom_*.*

2. If you have adjusted the threshold for error file logging in the ADS, or if you are not sure whether

you have adjusted it, copy the following file to your target system:

DIR_GLOBAL\AdobeDocumentServices\lib\renderErrorLog\renderErrorLogConfig.xml

3. If you have made modifications to any XDC files, copy all XDC files to your target system:

DIR_GLOBAL\AdobeDocumentServices\lib\*.xdc



76/122 PUBLIC 2011-11-07

NOTE

When copying the files to the new system, do not replace any existing files. Otherwise the

changes made the XDC files provided by Adobe will be overwritten on system restart.

4. Restart your target system.

Manual Configuration

1. Adjust the RFC connection ADS.

Make sure you change the server name, the port, and the authentication information to match

the target system.

2. Create the HTTP destination FP_ICF_DATA_<SAPSID of target system>.

7.1.2.2.2 EP Core – Application Portal (EPC)

7.1.2.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 76].

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.

7.1.2.2.3 Enterprise Portal (EP)

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

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



2011-11-07 PUBLIC 77/122


■ 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/instguidesnw SAP NetWeaverSAP NetWeaver <your release> Installation 3 – Installation -

Standalone Engines SAP NetWeaver Search and Classification TREX

On the target system, set up the connection to the newly installed TREX system.

See the SAP Library [page 9] at:SAP NetWeaver Library: Function-Oriented View Search Search and

Classification TREX Search and Classification (TREX) TREX Configuration TREX Basic Configuration Connecting TREX with an Application Connecting TREX with a 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.

See the SAP Library [page 9] at: SAP NetWeaver Library: Function-Oriented View Enterprise Portal Knowledge Management

Administration Guide System Administration System ConfigurationAdministering Indexes

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

See the SAP Library [page 9] at:SAP NetWeaver Library: Function-Oriented View Enterprise

Portal Knowledge Management Administration Guide System Administration System Configuration Knowledge

Management Configuration Repositories and Repository Managers



78/122 PUBLIC 2011-11-07


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, you delete the configuration on the target system and, if required, set up a new configuration. To remove the existing configuration on the target system, you run a cleanup file: ■ Download the cleanup file attached to SAP

Note 870863. 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.



Management Configuration Global Services Content Exchange Service

URL GeneratorOn the target system, check the settings for the Host and Alternative Host parameters.



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


Portal Knowledge Management Administration Guide Basic Configuration for Knowledge Management Additional

Manual Configuration Steps Cluster Only: Assigning Tasks to Nodes

Collaboration


On the target system, adapt the room backend properties server address, server port, and Web protocol.

See the SAP Library [page 9] at:SAP NetWeaver Library: Function-Oriented View Enterprise PortalCollaboration Administration Guide Collaboration ConfigurationWizard-Based Basic Configuration for Collaboration Defining the

Web Address and Automatic E-Mail Dispatch for Rooms

On the target system, generate a new index to enable search operations in the content of rooms.

See the SAP Library [page 9] at:



2011-11-07 PUBLIC 79/122


Task Detailed InformationSAP NetWeaver Library: Function-Oriented View Enterprise PortalCollaboration Administration Guide Making Rooms Available in

the Portal Preparing Rooms for Use Configuring 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.

See the SAP Library [page 9] at:SAP NetWeaver Library: Function-Oriented View Enterprise PortalCollaboration Administration Guide Making Rooms Available in

the Portal Preparing Rooms for Use Configuring the Search for Rooms

On the target system, configure the connection to the required groupware server.

See the SAP Library [page 9] at:SAP NetWeaver Library: Function-Oriented View Enterprise PortalCollaboration Administration Guide Collaboration ConfigurationWizard-Based Basic Configuration for Collaboration 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.

See the SAP Library [page 9] at:SAP NetWeaver Library: Function-Oriented View Enterprise PortalCollaboration Administration Guide Groupware Groupware

Framework Installing and Configuring E-Mail ConnectivityConfiguration Steps Creating an E-Mail Transport

On the target system, reconfigure the ServerName and ServerPort for the application sharing server.

See the SAP Library [page 9] at:SAP NetWeaver Library: Function-Oriented View Enterprise PortalCollaboration Administration Guide Real-Time CollaborationConfiguring Real-Time Collaboration Configuring the RTC

Application Sharing Server Setting RTC Application Sharing Server Parameters

7.1.2.2.4 Business Intelligence Java Components (BI Java)

You have to perform the following follow-up activities for BI Java:

7.1.2.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 usage type BI Java.

Procedure

You have to do the following to add the entries to the services file:



80/122 PUBLIC 2011-11-07

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.

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.

7.1.2.2.4.2 Basic Configuration for BI Java

Procedure

Integration into the Portal

1. Call transaction SPRO and choose SAP Reference IMG SAP NetWeaver Business Intelligence

Reporting-relevant Settings BEx Web Integration into the Portal .

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

7.1.2.2.5 Enterprise Services Repository: Connecting to the SLD

Procedure

Adapt the connection to the System Landscape Directory (SLD). For more information, see the SAP

Library [page 9] at:

SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Configuring, Working With, and

Administering System Landscape Directory Configuring Systems to Connect to the SLD .

7.1.2.2.6 Partner Connectivity Kit

Procedure

After copying your system, you must check the aii.properties manually.



2011-11-07 PUBLIC 81/122

For more information, see SAP Note 746328.

7.1.2.2.7 Development Infrastructure (DI)

You have to perform the following manual steps on the target system after the move of an SAP system

with software unit Development Infrastructure (DI). The assumption here is that all components

(DTR, CBS, CMS, SLD, CM Services, 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 J2EE engine configuration:

■ Set MaxHeapSize and other engine parameters to the recommended values.

For more information, see the corresponding section in your installation guide.

■ Only valid for: MaxDB |

If your database is 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, see SAP Note 889038.

3. Design Time Repository (DTR):

Perform Update Statistics (30%) on the database.


NOTE

If your database is 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

of your local SLD to point to the target host.

CAUTION

Do not change the ObjectServer attribute.

5. Component Build Service (CBS):



82/122 PUBLIC 2011-11-07



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.

For more information about these parameters, see the corresponding section in your installation

guide.

6. Change Management Service (CMS):

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 (choose Update CMS). You should see a status message that the CMS

update was successfully.

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 (see Domain Data tab).

3. For each track (in the Track Data tab):

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. CM Services:

The main steps in CM Services involve resetting fields that contain URLs to other components

(such as DTR, CBS, SLD). Proceed as follows:



2011-11-07 PUBLIC 83/122

1. On the System Landscape Directory tab, adapt the SLD URL and the CM Services URL to the target

host.

These data are valid for all development configurations on this server.

2. On the Local Settings tab, perform the following steps for each development configuration:

1. Development configurations of type Stand-Alone only: Copy the content of both the inbox

and outbox directories of CM Services in the source system to the corresponding

directories of CM Services in the target system.

2. Change the CBS and DTR URLs.

3. Save the development configuration.

8. IDE:

■ Change the SLD URL in the preference page of the SAP NetWeaver Development Studio (under

Preferences Development Infrastructure Landscape Directory ).

This should now point to the new SLD on the target system.

■ Import the development configuration you had earlier used for development.

Now you are ready to begin the development with you new (relocated) Development

Infrastructure (DI).

9. Verification Steps (optional)

The following steps can optionally be done to verify that the Development Infrastructure (DI) is

fully functional after the move:

1. Log on to the DTR (using the browser) for all defined users and browse the repository.

2. Using IDE, create a new Development Component (DC), checking and activate:

■ The activation should succeed.

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

Only valid for: z/OS |

7.1.3 Performing Jobhead Correction after Homogeneous System Copy

NOTE

This section is only relevant for customers using CCMS to monitor their SAP systems.

After copying your system, the CCMS jobhead still points to the former database SSID. To complete

the homogeneous system copy, the SSID needs to be set to the target system.



84/122 PUBLIC 2011-11-07

CAUTION

Only experienced users should use this utility.

Procedure

To set the SSID to the target system:

1. Call transaction DBACOCKPIT.

2. Choose Configuration Homogeneous System Copy: Jobhead Correction

3. Modify the necessary data.End of: z/OS |



2011-11-07 PUBLIC 85/122

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

8 Additional Information

8.1 Jload Procedures Using the Java Migration Monitor

Purpose

The Java Migration Monitor is a tool that helps you to perform and control the unload and load process

for the Java stack during the system copy procedure.

The Java Migration Monitor performs the following steps:

■ Starting the Jload processes to load or unload the data according to user’s requirements

■ Informing the person performing the system copy in case of errors

Tool

The tool is part of the archives J2EEINSTALL.SDA (jar file) and CORETOOL*.SCA (guide, scripts, property

files) and consists of the following files:

■ User Guide

● JMigMonUserGuide.pdf

● Located:

On Windows: <Drive:>:\usr\sap\<SAPSID>\SYS\global\sltools

On UNIX: /sapmnt/<SAPSID>/global/sltools

■ Scripts

● jmigmon_export.sh / jmigmon_export.bat

● jmigmon_import.sh / jmigmon_import.bat

● Located:

On Windows:<Drive:>:\usr\sap\<SAPSID>\SYS\global\sltools


■ jar archive

● sdt_jcopy_jmigmon.jar

● Located:

On Windows:<Drive:>:\usr\sap\<SAPSID>\SYS\global\sltools\sharedlib

On UNIX: /sapmnt/<SAPSID>/global/sltools/sharedlib

■ Property files

● export.jmigmon.properties

● import.jmigmon.properties

● Located:

On Windows:<Drive:>:\usr\sap\<SAPSID>\SYS\global\sltools



2011-11-07 PUBLIC 87/122


Prerequisites

■ The JRE version must be at least 1.6.1.

■ JAVA_HOME environment variable must point to the JRE directory.

8.1.1 Configuration

The following options can be provided via the property file or via command line. Command line

parameters take precedence over parameters specified in the property file.

Help

With the following command line option, the tool displays all parameters available:

-help

Version

With the following command line option, the tool displays version information:

-version

General Options

General Options

Name Description Comments

mode Java Migration Monitor mode: import or export

Only available as command line option

sid <SAPSID> of the system Specifies the <SAPSID> of the system

dsn Data Source Name Specifies the Data Source Name and is registered in the SecureStore; usually jdbc/pool/<SAPSID>

ssProps Path to the SecureStore properties file

On Windows: local drive or UNC path

ssKey Path to SecureStore key file On Windows: local drive or UNC path

orderBy Package order This can be the name or path of the file that contains package names.If the option value is omitted the package order is not determined.

jobNum Number of parallel export jobs Default is 3.

monitorTimeout Monitor time-out in seconds Default is 30 seconds.

disableStatistics Disables statistics logging Disables statistics logging for each Jload process: Therefore Jload does not collect statistics data that could later be displayed by the time analyzer.

Mandatory General Options

The following options are mandatory:



88/122 PUBLIC 2011-11-07

sid, dsn, ssProps, ssKey

Export Options

Name Description Comment

exportDirs Export directories path Specifies the path or paths for exported data and triggers the export functionality.Separator on Windows: “;”Separator on UNIX: “:”

Mandatory Export Options

The following export option is mandatory:

exportDirs

Import Options

Name Description Comment

importDirs Import directories path Specifies the path or paths for imported data and triggers the import functionality.Separator on Windows: “;”Separator on UNIX: “:”

Mandatory Import Options

The following import option is mandatory:

importDirs

8.1.2 Starting the Java Migration Monitor

The application allows you to specify options in the command line or in the export or import property

files. The names of the property files are export.jmigmon.properties and

import.jmigmon.properties.

Any options specified in the command line take precedence over the corresponding options in the

application property file. Options are case-sensitive; any options that are not recognized are ignored.

Prerequisites

NOTE

We recommend to create a certain directory and start the tool from there, because the Java

Migration Monitor produces log and trace files in the current working directory.

Before you run the Java Migration Monitor, set the following environment variables:

■ SLTOOLS_HOME

Set this variable to the following directory:



2011-11-07 PUBLIC 89/122

● On Windows:

<Drive>:\usr\sap\<SAPSID>\SYS\global\sltools\sharedlib or <Drive>:\sapmnt

\<SAPSID>\SYS\global\sltools\sharedlib

● On UNIX:

/sapmnt/<SAPSID>/global/sltools/sharedlib

■ SLTOOLS_SECURITY_HOME

Set this variable to the directory, which contains the iaik_jce.jar file.

The default directory is:

● On Windows: <Drive>:\usr\sap\<SAPSID>\SYS\global\security\lib\tools or <Drive>:

\sapmnt\<SAPSID>\SYS\global\security\lib\tools

● On UNIX: /sapmnt/<SAPSID>/global/security/lib/tools

■ SLTOOLS_DBDRIVER_HOME

Set this variable to the directory, which contains the database driver.

EXAMPLE

For MaxDB on Windows: <Drive>:\sapdb\programs\runtime\jar

Procedure

1. Start the Java Migration Monitor as user <sapsid>adm as follows:

■ With UNIX shell scripts

jmigmon_export.sh or jmigmon_import.sh

■ With Windows batch files

jmigmon_export.bat or jmigmon_import.bat

2. Specify options as required in one of the following ways:

■ Command line:

Specify an option in the format –optionName optionValue.

■ Property file:

Add an option as a new line in the format optionName=optionValue.

NOTE

■ To check the monitor processing state, use the monitor *.log and *.console.log files.

■ In case you use an invalid option or you enter -help, the available options for starting

the tool are displayed.

Example

Command line for UNIX

./jmigmon_export.sh -sid CE3 -dsn jdbc/pool/CE3 -ssProps /sapmnt/global/security/data/

SecStore.properties -ssKey /sapmnt/global/security/data/SecStore.key -exportDirs D:/

JPKGCTL



90/122 PUBLIC 2011-11-07

Command line for Windows

jmigmon_export.bat -sid CE3 -dsn jdbc/pool/CE3 -ssProps D:\usr\sap\CE3\SYS\global

\security\data\SecStore.properties -ssKey D:\usr\sap\CE3\SYS\global\security\data

\SecStore.key -exportDirs D:\JPKGCTL

export.jmigmon.properties file with export options

# jmigmon mode: import or export

mode = export

# number of parallel export jobs, default is 3

jobNum = 1

# <SAPSID> of the system

sid = CE3

# name of datasource registered in system's SecureStore; usually jdbc/pool/<SAPSID>

dsn = jdbc/pool/CE3

# path of the SecureStore properties file

ssProps = D:\usr\sap\CE3\SYS\global\security\data\SecStore.properties

# path of the SecureStore key file

ssKey = D:\usr\sap\CE3\SYS\global\security\data\SecStore.key

# list of export directories

exportDirs = D:\JPKGCTL

# monitor timeout in seconds, default is 30

monitorTimeout = 30

import_monitor.properties file with import options

# jmigmon mode: import or export

mode = export

# number of parallel export jobs, default is 3

jobNum = 1

# <SAPSID> of the system

sid = CE3

# name of datasource registered in system's SecureStore; usually jdbc/pool/<SAPSID>

dsn = jdbc/pool/CE3

# path of the SecureStore properties file

ssProps = D:\usr\sap\CE3\SYS\global\security\data\SecStore.properties

# path of the SecureStore key file

ssKey = D:\usr\sap\CE3\SYS\global\security\data\SecStore.key

# list of import directories

importDirs = D:\export\unpacked\JAVA\JDMP

# monitor timeout in seconds, default is 30



2011-11-07 PUBLIC 91/122

monitorTimeout = 30

8.1.3 Output Files

Export

■ export.state.properties

■ <PACKAGE>.xml.log

Import

■ import.state.properties

■ <PACKAGE>.xml.log

Both the export and import state files contain package state lines such as the following:

SAPUSER=+

Format of lines is <PACKAGE>=<STATE>. The following table shows the possible values for state:

Value Description

0 Package export/import not yet started.

? Package export/import in progress.

- Package export/import finished with errors.

+ Package export/import finished successfully.

8.1.4 Restarting Jload Processes

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

EXAMPLE

If package processing failed and the package state has the value “–”, you can set the state to “0” to

restart the package processing.

Procedure

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

■ To skip package processing, set the package state from “0” or “-” to “+”.

CAUTION

This is not recommended because it can cause inconsistent data files or database content.

■ If the package is currently being processed (package state is “?”) then any manual modifications of

the package state are ignored.

8.2 Package and Table Splitting for Java Tables

Purpose

The Java Splitter offers the following possibilities:



92/122 PUBLIC 2011-11-07

■ Splitting the default packages EXPORT.XML and IMPORT.XML into several smaller and equal sized

packages:

■ Extracting large tables into packages of their own

■ Splitting large tables into several smaller and equal sized packages (table splitting)

The tool provides the corresponding split packages for export and import. Package splitting and table

splitting can be used combined or separately.

Tool

The tool archive consists of the following:

■ User Guide

● JSplitterUserGuide.pdf

● Located:



■ Scripts for starting the tool standalone

● jsplitter.sh, jsplitter.bat

● Located:



■ jar archive

● sdt_jcopy_jpkgctl.jar

● Located:

On Windows:<Drive:>:\usr\sap\<SAPSID>\SYS\global\sltools\sharedlib

On UNIX: /sapmnt/<SAPSID>/global/sltools/sharedlib

Prerequisites

■ The JRE version must be at least 1.6.1.

■ JAVA_HOME environment variable must point to the JRE directory.

8.2.1 Configuration

The following options can be provided via the property file or via command line. Command line

parameters take precedence over parameters specified in the property file.

Help

With the following command line option, the tool displays all parameters available:

-help



2011-11-07 PUBLIC 93/122

General Options

General Splitting Options

Option Description Comment

help Prints help options for the parameters and their usage

none

sid <SAPSID> of the system Specifies the <SAPSID> of the system

dsn Data Source Name Specifies the Data Source Name and is registered in the SecureStore; usually jdbc/pool/<SAPSID>

ssProps Path to the SecureStore properties file On Windows: local drive or UNC path

ssKey Path to SecureStore key file On Windows: local drive or UNC path

dataDir Output data directory If this option is missing, the split rules are taken from the command line arguments.

log Log file with program output messages and errors

Default log file name is JPkgClt.console.log. The log file is created in the current working directory. In addition, the JPkgCtl.trc trace file with detailed process descriptions, errors, and messages is generated.

Mandatory General Options

The following splitting options are mandatory for both package and table splitting:

sid, dsn, ssProps, ssKey, dataDir

Package Splitting Options

Package Splitting Options


split Size of the split packages Size can be specified without unit (bytes assumed), as kilobytes (K), megabytes (M), gigabytes (G), or terabytes (T), for example, 1048576, 200M, 8G, and so on.

Additional Mandatory Option for Package Splitting

Splitting option: split

Table Splitting Options

Table Splitting Options


splitrulesfile Files that describe, which tables shall be split and how

Syntax:<TABLE_NAME>:<NUMBER_OF_PACKAGES_FOR

_SPLITTING>:<[COLUMN_TO_BE_USED_

FOR_SPLITTING]>

EXAMPLE

J2EE_CONFIG:2:

J2EE_CONFIGENTRY:4:CID



94/122 PUBLIC 2011-11-07


tablesplit Parameter for specifying rules for table splitting on the command line



FOR_SPLITTING]>

checksplitrules Checks the following: ■ Syntax of splitrulesfile ■ If the database tables specified

in the splitrulesfile exist ■ If all database tables specified

in the splitrulesfile without COLUMN_TO_BE_USED_FOR_

SPLITTING have a primary keyIt expects a file as an argument.



FOR_SPLITTING]>

CAUTION

When configuring table splitting for a table without primary key (such as J2EE_CONFIGENTRY),

you have to provide a value for parameter <COLUMN_TO_BE_USED_FOR_SPLITTING>. If the table to

be split has a primary key, this parameter is optional.

Additional Mandatory Options for Table Splitting

Splitting options: splitrulefile, tablesplit

Example

JSplitter_cmd.properties:

#

# Table Splitting options

#

# Common options

#

# List of SAPSID, data source name[,SecureStore property file, SecureStore key file]

[,SecureStore key phrase]

-sec=CE1, jdbc/pool/CE1,D:\usr\sap\CE1\SYS\global\security\data\SecStore.properties,

D:\usr\sap\CE1\SYS\global\security\data\SecStore.key

# Size of the split package with tables

-split=200M

# Output data directory

-dataDir=C:\jsplitter_export_dir

# File that contains key fields for each table with the following syntax:

<TABLE_NAME>:<NUMBER_OF_PACKAGES_FOR_SPLITTING>:<[TABLE_KEY_FOR_SPLITTING]>

-splitrulesfile=C:\jsplitter_export_dir\splitrulesfile.txt



2011-11-07 PUBLIC 95/122

# Log file with program output messages and errors

-log=

# Check splitrulesfile syntax

-checksplitrules=C:\jsplitter_export_dir\splitrulesfile.txt

8.2.2 Starting the Table Splitter

RECOMMENDATION

We recommend to create a certain directory for splitting and start the tools from there, because

the splitter produces log and trace files in the current working directory.

The application allows you to specify options in the command line or in the application property file.

The name of the property file is JSplitter_cmd.properties.

Any options specified in the command line take precedence over the corresponding options in the

application property file. Options are case-sensitive; any options that are not recognized are ignored.

Prerequisites

Before you run the table splitter, set the following environment variables:

■ SLTOOLS_HOME

Set this variable to the following directory:

● On Windows: <Drive>:\usr\sap\<SAPSID>\SYS\global\sltools\sharedlib or <Drive>:

\sapmnt\<SAPSID>\SYS\global\sltools\sharedlib

● On UNIX: /sapmnt/<SAPSID>/global/sltools/sharedlib

■ SLTOOLS_SECURITY_HOME

Set this variable to the directory, which contains the iaik_jce.jar file.

The default directory is:

● On Windows: <Drive>:\usr\sap\<SAPSID>\SYS\global\security\lib\tools or <Drive>:

\sapmnt\<SAPSID>\SYS\global\security\lib\tools

● On UNIX: /sapmnt/<SAPSID>/global/security/lib/tools

■ SLTOOLS_DBDRIVER_HOME

Set this variable to the directory, which contains the database driver.

EXAMPLE

For MaxDB on Windows: <Drive>:\sapdb\programs\runtime\jar

Procedure

1. Start the table splitter as user <sapsid>adm in one of the following ways:

■ With the UNIX shell script jsplitter.sh

■ With the Windows batch file jsplitter.bat

2. Specify options as required in one of the following ways-optionName optionValue.



96/122 PUBLIC 2011-11-07

■ Command line:

Specify the option in the format –optionName optionValue

■ Property file:

Add an option as a new line in the format optionName=optionValue

NOTE

In case you use an invalid option or you enter -help, the available options for starting the

tool are displayed.

NOTE

To check the splitting processing state, use the splitter *.trc and *.console.log files.

Example

Command line for Windows

jsplitter.bat -tablesplit BC_COMPVERS:2 -tablesplit J2EE_CONFIG:4:CID;PATHHASH -

tablesplit J2EE_CONFIGENTRY:4:CID

Command line for UNIX

./jsplitter.sh -tablesplit BC_COMPVERS:2 -tablesplit J2EE_CONFIG:4:CID;PATHHASH -

tablesplit J2EE_CONFIGENTRY:4:CID

8.2.3 Output Files

■ JPkgCtl.console.log

Default log file of splitter tool

■ JPkgCtl.trc

Trace file with additional and more detailed information

■ IMPORT_<PKG_NUMBER>.XML

Resulting xml files for import after package splitting

■ EXPORT_<PKG_NUMBER>.XML

Resulting xml files for export after package splitting

■ IMPORT_PKG_METADATA.XML

Metadata for tables

■ EXPORT_PKG_METADATA.XML

Metadata for tables

■ sizes.xml

File with list of the biggest tables with their expected package size in bytes

8.3 Additional Information About SAPinst

The following sections provide additional information about SAPinst:



2011-11-07 PUBLIC 97/122

■ Useful Information About SAPinst [page 98]

■ Interrupted Installation with SAPinst [page 102]

■ Performing a Remote Installation with SAPinst [page 105]

■ Starting SAPinst GUI Separately [page 108].

■ Running SAPinst in Accessibility Mode [page 112]

■ Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle;SAP HANA DB |

Entries in the Services File Created by SAPinst [page 114]End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle;SAP HANA DB |

■ Troubleshooting with SAPinst [page 115]

8.3.1 Useful Information About SAPinst

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

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


■ SAPinst normally creates the directory sapinst_instdir directly below the temporary directory.

SAPinst finds the temporary directory by checking the value of the environment variables TEMP,

TMP, or TMPDIR. If no value is set for these variables, SAPinst uses /tmp as default directory.

■ The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. These

executables are deleted again after SAPinst has stopped running. If required, you can terminate

SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C.End of: UNIX |


■ SAPinst normally creates the installation directory sapinst_instdir, where it keeps its log files,

and which is located directly in the Program Files directory. If SAPinst is not able to create

sapinst_instdir directly below the Program Files directory, SAPinst tries to create

sapinst_instdir in the directory defined by the environment variable TEMP.

■ SAPinst creates a subdirectory for each installation option, called <sapinst_instdir>

\<installation_option>, which is located in %ProgramFiles%.

■ The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP, TMP,

TMPDIR, or SystemRoot). These executables are deleted after SAPinst has stopped running.

Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You

can safely delete them.

The temporary directory also contains the SAPinst Self-Extractor log file dev_selfex.out, which

might be useful if an error occurs.

If you want to terminate SAPinst and the SAPinst Self-Extractor, do one of the following:



98/122 PUBLIC 2011-11-07

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

CAUTION

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

FCO-00058.

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

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


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

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

<InstanceName>/SMD/root/origin.

During the export, some archives are written to the program subdirectories and SAPinst aborts if

there is not enough space.

■ Make sure that the DISPLAY environment variable is set to <host_name>:0.0, where

<host_name> is the host where the SAPinst GUI is displayed.

■ Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime

Environment (JRE).

■ Only valid for: AIX |

If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE for AIX

64-bit.End of: AIX |

End of: UNIX |


■ Before starting the export steps on the central instance of the source system, make sure that you

have at least the same amount of disk space available in \\SAPLOC\<SAPSID>\<InstanceName>\SMD

\program as is used in \\SAPLOC\<SAPSID>\<InstanceName>\SMD\root\origin. During the export

some archives are written to the program subdirectories and SAPinst aborts if there is not enough

space.End of: Windows |


■ Before you start the export of the existing SAP System, you have to download the current version

of R3szchk at http://service.sap.com/patches and copy it to directory /usr/sap/<>/SYS/exe/

run/.End of: IBM i5/OS |

NOTE

For a list of all available SAPinst properties, enter the following command: sapinst —p.



2011-11-07 PUBLIC 99/122

http://service.sap.com/patches

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

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

SAPINST_USE_HOSTNAME=<virtual host>.


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

between SAPinst, GUI server, SAPinst GUI, and HTTP server, as follows:

● SAPinst uses port 21200 to communicate with the GUI server.

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

● 4239 is the port of the HTTP server, which is part of the GUI server.

If these ports are already in use, SAPinst automatically searches for free port numbers. If the search

fails, you see an error message and SAPinst exits.

In this case or if you want SAPinst to use specific ports, open a command prompt and change to

the required directory as follows:

cd /d <drive>:\DATA_UNITS\IM_WINDOWS_<platform>.

Execute sapinst.exe with the following commands:

● SAPINST_DIALOG_PORT=<port_number_sapinst_to_gui_server>

● GUISERVER_DIALOG_PORT=<port_number_gui_server_to_sapinst_gui>

● GUISERVER_HTTP_PORT=<port_number_http_server>

■ To see a list of all available SAPinst properties, go to the directory %TEMP%

\sapinst_exe.xxxxxx.xxxx after you have started SAPinst, and enter the following

command:sapinst —p.End of: Windows |


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

between SAPinst, GUI server, SAPinst GUI, and HTTP server, as follows:

● SAPinst uses port 21200 to communicate with the GUI server.

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

● 4239 is the port of the HTTP server, which is part of the GUI server.

If these ports are already in use, SAPinst automatically searches for free port numbers. If the search

fails, you see an error message and SAPinst exits.

In this case or if you want SAPinst to use specific ports, you can assign them by executing the sapinst

executable with the following parameters:

● SAPINST_DIALOG_PORT=<port_number_sapinst_to_gui_server>

● GUISERVER_DIALOG_PORT=<port_number_gui_server_to_sapinst_gui>

● GUISERVER_HTTP_PORT=<port_number_http_server>

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

-p:



100/122 PUBLIC 2011-11-07

./sapinst -p.End of: UNIX |

NOTE

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

field and choose F1 .

Troubleshooting

CAUTION

If an export process aborts due to a hardware failure (for example, file system full), you have to

repeat the export of the complete package. Remove the dump files <package>.<nnn>, the TOC

file <package>.TOC, the log file <package>.log and make sure that all tables in the TSK file

<package>.*TSK* have the status flag 'xeq' or 'err' set.

■ If there is not enough disk space in the export directory, the R3load database export fails. You can

then find error messages in the log files SAP*.log.

You can subsequently move the dump files that have been created from the file system in which

the export directory is located to a different file system during the export. Currently it is not possible

to automatically distribute the export over different file systems.

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

● Stops the export.

● Displays a dialog that informs you about the error.

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

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

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

● Stops the export.

● Displays a dialog that informs you about the error.

You can now:

● Directly view the log file by choosing View Logs.

● Try to solve the problem.

● Continue the export by choosing Retry.

● Abort the export by choosing OK.

■ System Copy - export on UNIX (especially for upgraded systems)

Symptom:

Processes started as <sapsid>adm or ora<sid> OS users cannot create or open files in the installation

directory.

Reason:

Only members of sapinst UNIX group can access the installation directory.

This group is created by SAPinst as of SAP NetWeaver 7.1.



2011-11-07 PUBLIC 101/122

Solution:

Associate <sapsid>adm and ora<sid> OS users with sapinst group manually if this association is

missing.

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

If sapinst group does not exist yet, start SAPinst. SAPinst creates this group during startup before

product catalog list is displayed.

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

Continue with the export.

For more information, see Interrupted Installation with SAPinst [page 102].

8.3.2 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:

■ An error occurred during the Define Parameters or Execute phase:

SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses

and a dialog box appears. The dialog box contains a short description of the choices listed in the

table below as well as a path to a log file that contains detailed information about the error.

■ You interrupted the installation by choosing Cancel in the SAPinst menu.

CAUTION

If you stop an option in the Execute phase, any system or component installed by this option

is incomplete and not ready to be used. Any system or component uninstalled by this option

is not completely uninstalled.

The following table describes the options in the dialog box:

Option Definition

Retry SAPinst retries the installation from the point of failure without repeating any of the previous steps.This is possible because SAPinst records the installation progress in the keydb.xml file.We recommend that you view the entries in the log files, try to solve the problem, and then choose Retry.If the same or a different error occurs, SAPinst displays the same dialog box again.

Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and the GUI server.SAPinst records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below.

Continue SAPinst continues the installation from the current point.

View Log Access installation log files.



102/122 PUBLIC 2011-11-07

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 to your remote host as a user who is a member of the local administrators group.End of: Windows |

2. Only valid for: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

Log on to your local UNIX host as user root.

CAUTION

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

or database.

End of: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

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

Log on to your local IBM i host as your installation user with similar authorization rights as

QSECOFR. For more information about how to create the installation user SAPIUSR, see the section

Preparing an IBM i User Profile [page 26].End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |


Make available the installation master media.End of: Windows |


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

installation host.

For more information, see Preparing the Installation Media [page 16].


RECOMMENDATION

Make installation media locally available. For example, if you use Network File System (NFS),

reading from media mounted with NFS might fail.

End of: UNIX |

Only valid for: Solaris |

NOTE

If you mount installation media, make sure that you do this with option nomaplcase.

End of: Solaris |

End of: UNIX |

6. Only valid for: IBM i5/OS |

Make available the installation master media.

NOTE

Make sure that the media is available locally. We do not recommend using Network File

System (NFS).

End of: IBM i5/OS |



2011-11-07 PUBLIC 103/122

7. Only valid for: Windows | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

Restart SAPinst by double-clicking sapinst.exe. You can also start SAPinst by entering the

following commands at the Windows command prompt:

cd /d <media_drive>:\IM_WINDOWS<platform>

sapinst.exe

End of: Windows | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

8. Only valid for: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

Change to the directory <product>_IM_<your OS>_<your DB> and start the sapinst executable

with the following command: ./sapinstEnd of: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

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

Enter the following commands:

cd '<installation media>/DATA_UNITS/<product>_IM_OS400_PPC64_DB4'

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

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

10. From the tree structure in the Welcome screen, select the installation option that you want to

continue and choose Next.

The What do you want to do? screen appears.

11. In the What do you want to do? screen, decide between the following alternatives and continue with

Next:

Alternative Behavior

Run a new option SAPinst does not continue the interrupted installation option. Instead, it moves the content of the old installation directory and all installation-specific files to a backup directory. Afterwards, you can no longer continue the old installation option.

NOTE

All action taken by the installation before you stopped it (like creating directories, or users) will not be revoked.

For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds>.

EXAMPLE

log_01_Oct_2008_13_47_56

CAUTION

SAPinst moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.

Continue with the old option SAPinst continues the interrupted installation from the point of failure.



104/122 PUBLIC 2011-11-07

8.3.3 Performing a Remote Installation with SAPinst

You use this procedure to install your SAP system on a remote host. In this case, SAPinst and the GUI

server run on the remote host, and SAPinst GUI runs on the local host. The local host is the host from

which you control the installation with SAPinst GUI.

Only valid for: IBM i5/OS;UNIX |

If your security policy requires that the person performing the installation by running the SAPinst GUI

on the local host is not allowed to know root credentials on the remote host, you can specify another

operating system user for authentication purposes. You do this using the

SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command

line.End of: IBM i5/OS;UNIX |


If your security policy requires that the person performing the installation by running the SAPinst GUI

on the local host is not allowed to know administrator credentials on the remote host, you can specify

another operating system user for authentication purposes. You do this using the

SAPINST_REMOTE_ACCESS_USER parameter when starting sapinst.exe from the command line.End of: Windows |


Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote

access to SAPinst GUI on Windows workstations. For more information, see SAP Note 1170809.End of: IBM i5/OS;UNIX |

Only valid for: UNIX;Windows | Linux;Windows |

You can run the SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host.

For more information, see Starting SAPinst GUI Separately [page 108].End of: UNIX;Windows | Linux;Windows |

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

CAUTION

In this section, “local host” refers to the Windows installation host, and“ remote host” refers to

the IBM i host where the SAP system is installed.

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

Prerequisites

■ Both computers are in the same network and can ping each other.

To test this:

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

1. Log on to your remote host and enter the command ping <local host>.

2. Log on to the local host and enter the command ping <remote host>.End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |



2011-11-07 PUBLIC 105/122



1. Log on to your remote host (IBM i) and enter the command PING RMTSYS('<local

host>').

2. Log on to the local host (Windows PC) and enter the command ping <remote host>.End of: IBM DB2 for i5/OS |

■ If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER

command line parameter, make sure that this user exists on the remote host.

ProcedureOnly valid for: Windows |

1. Log on to your remote host as a user that is a member of the local administrators group.

2. Make the installation master media available on your remote host.

3. Open a command prompt and enter the following commands:

Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

cd \d <media drive>:\DATA_UNITS\<product>_IM_WINDOWS_<platform>_<DB>

End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

Run sapinst.exe -nogui

NOTE

If you need to specify another operating system user for authentication purposes, enter the

following command:

sapinst.exe -nogui SAPINST_REMOTE_ACCESS_USER=<specified OS user>

4. Execute the following command: sapinst.exe -nogui

SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the

command prompt:

guiengine: no GUI connected; waiting for a connection on host <host_name>, port

<port_number> to continue with the installation

5. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 108].End of: Windows |


1. Log on to your remote host as user root.

CAUTION

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

or database.

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

installation host.




106/122 PUBLIC 2011-11-07


RECOMMENDATION

Make installation media locally available. For example, reading from media mounted with

Network File System (NFS) might fail.

End of: UNIX |


NOTE


End of: Solaris |

3. Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

Change to the directory <product>_IM_<your OS>_<your DB> and start the sapinst executable

with the following command: ./sapinst -noguiEnd of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

NOTE

If you need to specify another operating system user for authentication purposes, enter the

following command:

./sapinst -nogui SAPINST_REMOTE_ACCESS_USER=<specified OS user>


command prompt:



4. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 108].End of: UNIX |


1. Log on to your host as the installation user with similar authorization rights to QSECOFR. For more

information, see Preparing an IBM i User Profile [page 26].

CAUTION

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

system or database.

2. Make available the installation master media.

3. Start SAPinst from the installation master media by entering the following commands:

■ CD DIR ('<installation media>/DATA_UNITS/<product>_IM_OS400_PPC64_DB4')

■ CALL PGM(QP2TERM) PARM('./sapinst' '-nogui')

NOTE

If you need to specify another operating system user for authentication purposes, this

command is as follows:

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

'SAPINST_REMOTE_ACCESS_USER=<specified OS user>')



2011-11-07 PUBLIC 107/122


command prompt:



Only valid for: HA (UNIX) |

NOTE

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

parameter SAPINST_USE_HOSTNAME to specify the virtual host name, you can start SAPinst as

follows:

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

host name>')

End of: HA (UNIX) |

4. There is no GUI on IBM i, so you do not see an SAPinst Welcome screen. As a default, you must start

the SAPinst GUI separately on a Windows 32-bit platform. For more information, see Starting SAPinst

GUI Separately [page 108].End of: IBM i5/OS |

8.3.4 Starting SAPinst GUI Separately

You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI separately

in the following cases:

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

You are running IBM i and did not set a DISPLAY environment variable.End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

■ You closed SAPinst GUI using File Exit from the SAPinst menu while SAPinst is still running.

■ You want to perform a remote installation, where the SAPinst GUI runs on a different host from

SAPinst. For more information, see Performing a Remote Installation with SAPinst [page 105].

■ Only valid for: IBM i5/OS;UNIX |

You want to run SAPinst in accessibility mode. In this case, you have to start the SAPinst GUI

separately on a Windows host as described below with the additional command line parameter –

accessible.

For more information, see Running SAPinst in Accessibility Mode [page 112].End of: IBM i5/OS;UNIX |


CAUTION

This is the default on IBM i. Since there is no GUI on IBM i, you must start the SAPinst GUI

separately.




108/122 PUBLIC 2011-11-07

Prerequisites

The host on which you want to start the SAPinst GUI meets the prerequisites for starting SAPinst as

described in Exporting the Source System Using SAPinst [page 20]

Procedure

Starting SAPinst GUI on Windows


host on which you want to start the SAPinst GUI.


2. Change to the directory of the sapinstgui executable:

Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

<product>_IM_<your OS>_<your DB>

End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

NOTE

If you want to start SAPinst GUI on a Windows 32-bit operating system, change to the

following directory:

<product>_IM_SAPINSTGUI_WINDOWS_I386

End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |


NOTE

If you start the SAPinst GUI executable on Windows 7 or Windows 2008, you must use the

option Run as administrator. Typically, you first start a command prompt using Run as

administrator. Then in this command prompt, you enter the SAPinst GUI command.

End of: IBM DB2 for i5/OS |

Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |

NOTE

If you want to start SAPinst GUI on a Windows 32-bit operating system, you can use the

executable available in the IBM i media or change to the following directory:

DATA_UNITS\<product>\SAPINSTGUI_WINDOWS_I386

End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |

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

NOTE

If you have a share ROOTBIN on your IBM i and you have mapped this share to the drive X,

you can start the SAPinst GUI using your copied installation master media:

X:\tmp\<SID>\<installation media>\DATA_UNITS

\<product>_SAPINSTGUI_WINDOWS_I386



2011-11-07 PUBLIC 109/122

For more information, see Copying the media Manually Using the ROOTBIN Share [page 27].

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

3. Start the SAPinst GUI from a command prompt by executing sapinstgui.exe with the relevant

command line parameters:

■ If you want to perform a remote installation, execute the following command:

sapinstgui.exe -host <remote_host> -port

<port_number_gui_server_to_gui_client>

– where <remote_host> is the name of the remote host, and

<port_number_gui_server_to_gui_client> is the port the GUI server uses to communicate

with the GUI client (21212 by default).

■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, proceed

as follows:

● If you are performing a local installation with SAPinst and SAPinst GUI running on the

same host, execute the following command:

sapinstgui.exe -standalone -port <port_number_gui_server_to_gui_client>

– where <port_number_gui_server_to_gui_client> is the port the GUI server uses to

communicate with the GUI client (21212 by default).

● If you are performing a remote installation with SAPinst and SAPinst GUI running on

different hosts, execute the following command:

sapinstgui.exe -host <remote_host> -port



<port_number_gui_server_to_gui_client> is the port the GUI server uses to


The SAPinst GUI starts and connects to SAPinst.

Starting SAPinst GUI on UNIX


host on which you want to start the SAPinst GUI.



RECOMMENDATION

Make installation media locally available. For example, if you use Network File System (NFS),

reading from media mounted with NFS might fail.

End of: UNIX |


NOTE


End of: Solaris |



110/122 PUBLIC 2011-11-07

2. Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;Oracle;SAP HANA DB |

Change to the directory <product>_IM_<your OS>_<your DB> and start the sapinstgui executable

with the following command: ./sapinstguiEnd of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;Oracle;SAP HANA DB |

■ If you want to start the SAPinst GUI on a Linux 32-bit platform, change to the directory

<product>_IM_SAPINSTGUI_LINUX_I386.

■ If you want to perform a remote installation, execute the following command:

./sapinstgui -host <remote_host> -port <port_number_gui_server_to_gui_client>


<port_number_gui_server_to_gui_client> is the port the GUI server uses to communicate

with the GUI client (21212 by default).

■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, proceed

as follows:

● If you are performing a local installation with SAPinst and SAPinst GUI running on the

same host, execute the following command:

./sapinstgui -port <port_number_gui_server_to_gui>

– where <port_number_gui_server_to_gui> is the port the GUI server uses to


● If you are performing a remote installation with SAPinst and SAPinst GUI running on

different hosts, execute the following command:

./sapinstgui -host <remote_host> -port <port_number_gui_server_to_gui>


<port_number_gui_server_to_gui> is the port the GUI server uses to communicate with

the GUI client (21212 by default).

The SAPinst GUI starts and connects to SAPinst.

3. Only valid for: z/OS |

Start the SAPinst GUI in one of the following ways:

■ If SAPinst GUI runs on the same host as SAPinst and the SAPinst GUI, enter the following

command without any additional parameters:

./startInstGui.sh

By default SAPinst GUI uses the local host.

■ If SAPinst runs on a different host from the SAPinst GUI (remote installation), enter the

following command with additional parameters:

./startInstGui.sh -host <host_name>

<host_name> is the host name of the installation host

NOTE

● If you enter the command without additional parameters, SAPinst GUI uses the

local host as default. SAPinst GUI starts and tries to connect to SAPinst. Since SAPinst



2011-11-07 PUBLIC 111/122

is running on another host, the SAPinst GUI cannot connect and the SAP Installation

GUI Connection dialog appears.

In this case, enter the name of the host on which SAPinst is running and choose Log

on.

The first dialog of the installation appears and you can perform the remote

installation from your local host.

● For a list of options to start SAPinst GUI, change to the same directory as your SAPinst

executable and enter the command:

./startInstGui.sh -h

End of: z/OS |

8.3.5 Running SAPinst in Accessibility Mode

You can also run SAPinst in accessibility mode. The following features are available:

■ Keyboard access:

This feature is available for all operating systems.

■ High-contrast color:


This feature is derived from the Windows display properties. You can use it either for a local

installation or for a remote installation.End of: Windows |


This feature is derived from the Windows display properties. Therefore, to enable this feature, you

must perform a remote installation with the SAPinst GUI running on a Windows host.End of: IBM i5/OS;UNIX |

■ Custom font setting:


This feature is derived from the Windows display properties. You can use it either for a local

installation or for a remote installation.End of: Windows |


This feature is derived from the Windows display properties. Therefore, to enable this feature, you

must perform a remote installation with the SAPinst GUI running on a Windows host.End of: IBM i5/OS;UNIX |

Procedure

Activating and Adjusting Accessibility Settings on Windows

You first have to activate and adjust the relevant settings for the font size and color schemes before

you start SAPinst or the SAPinst GUI.



112/122 PUBLIC 2011-11-07

NOTE

The following procedure applies for Windows Server 2008 and might be different when using

another Windows operating system.

1. Right click on your Windows desktop and choose Personalize.

2. Choose Adjust font size (DPI) and choose Larger scale (120 DPI).

To define other font size schemes, choose Custom DPI.

3. In the right-hand pane, select Window Color and Appearance.

Select a color scheme from the Color scheme dropdown box.

To define your own color schemes, choose Advanced.

Running SAPinst in Accessibility Mode


You can either perform a local installation, where SAPinst and SAPinst GUI are running on the same

host, or a remote installation, where SAPinst and SAPinst GUI are running on different hosts.

■ Local installation:

Start SAPinst as described in Running SAPinst on UNIX or Windows to Perform the Export [page 20] by

executing the following command:

sapinst.exe –accessible

■ Remote installation:

1. Start SAPinst on the remote host by executing the following command from the command

line as described in Performing a Remote Installation with SAPinst [page 105]:

sapinst.exe –nogui

2. Start SAPinst GUI on the local host by executing the following command from the command

line as described in Starting the SAPinst GUI Separately for a Remote Installation [page 108]:

sapinstgui.exe -accessible –host <remote_host> -port


End of: Windows |


You perform a remote installation as follows:

1. Start SAPinst on the remote host by executing the following command from the command line

as described in Performing a Remote Installation with SAPinst [page 105]:

./sapinst –nogui

2. Start SAPinst GUI on a local Windows host by executing the following command from the

command line as described in Starting the SAPinst GUI Separately for a Remote Installation [page 108]:

sapinstgui.exe -accessible –host <remote_host> -port


End of: IBM i5/OS;UNIX |



2011-11-07 PUBLIC 113/122

8.3.6 Entries in the Services File Created by SAPinstOnly valid for: UNIX |

After the installation has completed, SAPinst has created the following entries in /etc/services:End of: UNIX |


After the installation has finished successfully, SAPinst has created the following entries for port names

in <drive:>\WINDOWS\system32\drivers\etc\services:End of: Windows |

Only valid for: UNIX;Windows |

sapdp<nn> = 32<nn>/tcp

End of: UNIX;Windows |


sapdp<nn>s = 47<nn>/tcp



sapgw<nn> = 33<nn>/tcp



sapgw<nn>s = 48<nn>/tcp



After the installation has finished successfully, SAPinst has created the following entries in the service

table:End of: IBM i5/OS |


To review the entries, use the command WRKSRVTBLE.End of: IBM i5/OS |


Service Table

Service Port Protocol

sapdp<nn> 32<nn> tcp

sapdp<nn>s 47<nn> tcp

sapgw<nn> 33<nn> tcp

sapgw<nn>s 48<nn> tcp


NOTE

■ <nn> is the instance number. There is a port created for every possible instance number,

regardless of which instance number you specified during the installation. For example, for

sapgw<nn> = 33<nn>/tcp the following range of entries is created:

sapgw00 = 3300/tcp



114/122 PUBLIC 2011-11-07

sapgw01 = 3301/tcp

sapgw02 = 3302/tcp

[...]

sapgw98 = 3398/tcp

sapgw99 = 3399/tcp

■ If there is more than one entry for the same port number, this is not an error.

8.3.7 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.

If an error occurs, SAPinst:

■ Stops the installation

■ Displays a dialog informing you about the error

Procedure

1. Check SAP Note 1548438 for known SAPinst issues.

2. To view the log file, choose View Logs.

3. If an error occurs during the dialog or processing phase, do one of the following:

■ Try to solve the problem.

■ Abort the installation with Exit.

For more information, see Interrupted Installation with SAPinst [page 102].

■ Continue the installation by choosing Retry.


Check the log and trace files of the GUI server and SAPinst GUI in the directory %userprofile%

\.sdtgui\ for errors.End of: Windows |


Check the log and trace files of the GUI server and SAPinst GUI in the directory

<user_home>/.sdtgui/ for errors.End of: IBM i5/OS;UNIX |


If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current

<user_home> directory.End of: IBM i5/OS;UNIX |

■ Only valid for: Windows |

If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current %

userprofile% directory.End of: Windows |

■ If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI

as described in Starting SAPinst GUI Separately [page 108].



2011-11-07 PUBLIC 115/122



If you use an X Server for Microsoft Windows or other remote desktop tools for the Remote

Access of SAPinst GUI on Windows Workstations and you experience display problems such

as missing repaints or refreshes, contact your X Server vendor. The vendor can give you

information about whether this X Server supports Java Swing-based GUIs and also tell you

about further requirements and restrictions. See also SAP Note 1170809.End of: IBM i5/OS;UNIX |

■ Only valid for: Windows | HA (MSCS) |

If you experience network connection problems, check IPv4 Host name resolution as described

in SAP Note 1365796.End of: Windows | HA (MSCS) |

5. If you cannot resolve the problem, create a customer message using component BC-INS.



116/122 PUBLIC 2011-11-07



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

2011-11-07 PUBLIC 117/122

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 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle and Java are registered trademarks of Oracle.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP companySybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Legal Software Terms

118/122 PUBLIC 2011-11-07

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

2011-11-07 PUBLIC 119/122

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 ServicesAdobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer, see SAP Note 854621.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

120/122 PUBLIC 2011-11-07



SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2011 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

system copy 73 java

Documents