systemcopy_70_sr3_abap

System Copy GuideSystem Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 ABAP

Target Audience ■ System administrators ■ Technology consultants

PUBLICDocument version: 1.5 – 2010-03-16

Document History

CAUTION

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

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

instguides.

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

Version Date Description

1.5 2010-03-16 Update in Database-Specific System Copy: example for distributed or high availability system corrected

1.4 2009-12-08 Update in Database-Specific System Copy

1.3 2009-09-09 Update in Oracle-Specific Procedure

1.2 2009-03-12 Update in Constraints and Preparation for Table Splitting

1.1 2009-01-09 DI-, EPC-, and EP-specific information updated

2/126 PUBLIC 2010-03-16

http://service.sap.com/instguides


Table of Contents

Chapter 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based

on SAP NetWeaver 7.0 SR3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

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

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

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

1.4 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

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

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

Chapter 3 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.1 General Technical Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.2 Installing the Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

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

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

4.2 Generating DDL Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.3 Preparation for Table Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4.4 Preparing the Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

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

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

4.5.2 Running SAPinst on System i to Perform the Export . . . . . . . . . . . . . . . . . . . . 36

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

4.5.2.2 Preparing a Windows User Account and System i User Profile . . . . . . . . . . . . . 37

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

4.5.2.4 Starting SAPinst on System i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4.5.3 Restarting R3load Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.6 Setting Up the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.6.1 Installing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

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

5.1 Oracle-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

2010-03-16 PUBLIC 3/126

5.1.1 Generating the Control File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5.1.2 Creating a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5.1.2.1 Creating an Offline Backup Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

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

5.1.3 Preparing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

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

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

5.2 SAP MaxDB-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

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

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

5.5 IBM DB2 for i5/OS Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

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

5.6.1 Step 1: Check Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

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

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

5.6.3.1 SQL Statement Number 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72









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

Changed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

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

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

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

5.6.8 Step 8: Printing the Bootstrap Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

5.6.9 Step 9a: Changing the Bootstrap Data Sets (BSDS) . . . . . . . . . . . . . . . . . . . . . . 81

5.6.10 Step 9b: Start the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

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

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

5.6.12 Step 9d: Stopping Index Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

5.6.13 Step 9e: Changing the User-Defined Indexes in the DB2 Catalog . . . . . . . . . . . 83

5.6.14 Step 9f: Restart the Index Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

5.6.15 Step 9g: Creating the Temporary Files for the DB2 Target System . . . . . . . . . . 84

4/126 PUBLIC 2010-03-16

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

Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

5.6.17 Step 9i: Adjusting the DDF Location Name and Port Number . . . . . . . . . . . . . 84

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

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

5.6.19 Step 10 (DB2 V9): Changing the VCAT of the Target System . . . . . . . . . . . . . . 86

5.6.20 Step 11 (DB2 V9): Changing the Schema of the Target System . . . . . . . . . . . . 86

5.6.21 Step 12: Adapting WLM Application Environments for DB2 Stored

Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Chapter 6 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

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

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

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

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

Chapter 7 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

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

7.1.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.1.2 Assigning DDL Files to Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

7.1.3 Defining Groups of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

7.1.4 Processing Split Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

7.1.5 Starting the Migration Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

7.1.6 Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

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

7.2 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

7.3 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

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

7.4.1 Performing a Remote Installation with SAPinst (Optional) . . . . . . . . . . . . . . 115

7.4.2 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . 116

2010-03-16 PUBLIC 5/126

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

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

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

using either database-specific methods or database-independent methods.

1.1 Terminology

■ Homogeneous System Copy

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

system.

■ Heterogeneous System Copy

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

Heterogeneous system copy is a synonym for migration.

■ Source System and Target System

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

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

are abbreviated to SOURCE_SAPSID and TARGET_SAPSID (System i: source_<SID> and

target_<SID>). The terms source database and target database are also used in this description.

■ System Copy

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

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

to set up the database.

■ Database Copy

Database-dependent part of the system copy.

■ Placeholders

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

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

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


1.1 Terminology

2010-03-16 PUBLIC 7/126

Placeholder Meaning How to find out

<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

More information about system copy is online available as follows:

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

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

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

Guide that is available in the Media Library.

■ SAP Note 82478

CAUTION

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

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

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

Technical Consultant.

NOTE

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

application area BC-INS-MIG.

1.3 System Architecture

1.4 Restrictions

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

servers installations. For the scenarios below, the following holds:

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

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

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

■ Refresh of the database is not supported. A refresh of the database means that only the database is

loaded with the content of a database of a different system. As in this scenario no migration

controller is invoked, this is not supported.

■ Copying the database only is not supported.


1.2 Online Information from SAP

8/126 PUBLIC 2010-03-16

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

http://service.sap.com/osdbmigration

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

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

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

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

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

1.5 Constraints

■ 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 can copy your Java engine later with

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

■ SAP does not generally support all Data Archiving operations after a system copy.

If you used Data Archiving in the source or in the target system, access to the created archive file

(s) from the target system may not always be possible. For more information, see SAP Note

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

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

only supported in the following cases:

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

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

store archive files using ArchiveLink/CMS.

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

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

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

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

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


1.5 Constraints

2010-03-16 PUBLIC 9/126




http://service.sap.com/slo

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

ArchiveLink/CMS connectivity.

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

[email protected].

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

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

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

■ Dos and Don'ts for system copy:

● Do:

◆ Save configuration data and runtime data in the Java database only. If you absolutely need

to save this data to the file system level, you must use the Software Deployment Manager

(SDM) to save the data.

◆ Follow the Open SQL standard.

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

● Don't:

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

central storage of such information, for example:

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

▶ Host name

▶ IP addresses

▶ Services and Ports

▶ Logical destinations and logical system names

▶ Other technical infrastructure names

◆ Use file system persistency.

◆ Set up dependencies between Java and ABAP.


1.5 Constraints

10/126 PUBLIC 2010-03-16

http://service.sap.com/slo

2 Planning

This section describes how to plan your system copy.

You can apply the system copy for:

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

■ Creating systems for testing, demonstration, training, and standby. Depending on the purpose of

the system, it might be advisable to use the same SAP system ID, even though this prevents you

from including the system in a system group for transports.

Only valid for: Oracle |

NOTE

You cannot create standby systems with a system copy.

End of: Oracle |

NOTE

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

specific problems that might result from modifications.

NOTE

You can set up the SAP system infrastructure (development, quality assurance, and production

system) without making a system copy as follows:

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

system as described in the implementation documentation.

■ Transport the client-dependent and client-independent data to the quality assurance and

production systems.

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

perform a system copy.

When copying a system that contains production data it is important to choose the right moment for

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

CAUTION

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

corrupted dumps.

Required Documentation

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

2 Planning

2010-03-16 PUBLIC 11/126

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

SR3)

■ The documentation System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 only describes the

export of the source system in detail.

■ For the installation of the target system, you also need the installation guide for your SAP

application:

SAP NetWeaver 7.0: Installation Guide – SAP NetWeaver 7.0 SR3 ABAP on <OS> : <DB> at http://

service.sap.com/installnw70 Installation – SAP NetWeaver Systems .

SAP ERP 6.0: Installation Guide – SAP ERP 6.0 SR3 ABAP on <OS> : <DB> at http://

service.sap.com/erp-inst SAP ERP 6.0 Installation .

SAP CRM 5.0: Installation Guide – SAP CRM 5.0 SR3 ABAP on <OS> : <DB> at http://

service.sap.com/crm-inst SAP CRM 2005 CRM Core and Standalone Components .

SAP SRM 5.0: Installation Guide – SAP SRM 5.0 SR3 ABAP on <OS> : <DB> at http://

service.sap.com/srm-inst Using SAP SRM Server 5.0 .

SAP SCM 5.0: Installation Guide – SAP SCM 5.0 SR3 ABAP on <OS> : <DB> at http://

service.sap.com/instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using

SAP SCM 5.0 Server .

Required DVDs, Tools, and Other Software

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

■ Required DVDs

● Installation Master DVD

NOTE

The DVD names are abbreviated.

You can find the full names of all media shipped with SAP NetWeaver 7.0 in Media Information for

SAP NetWeaver 7.0 at http://service.sap.com/installNW70.

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

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

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

NOTE

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

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

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

you can upgrade them at different times.

CAUTION

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

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

2 Planning

12/126 PUBLIC 2010-03-16


http://service.sap.com/installnw70


http://service.sap.com/erp-inst

http://service.sap.com/erp-inst

http://service.sap.com/crm-inst

http://service.sap.com/crm-inst

http://service.sap.com/srm-inst

http://service.sap.com/srm-inst



http://service.sap.com/installNW70

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

service.sap.com/migrationkey.

Creating A System Copy Plan

Create a plan to perform the system copy.

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

system copy.

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

system downtime:

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

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

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

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

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

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

down for the time of the export.

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

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

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

perform read/write actions only on local file systems.

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

Miscellaneous

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

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

partner.

■ Decide which system copy procedure you want to use:

● The database-independent procedure using SAP tools.

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

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

NOTE

For a heterogeneous system copy, only the database-independent method is

available.

● The database-specific procedure 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

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

2 Planning

2010-03-16 PUBLIC 13/126

http://service.sap.com/migrationkey


■ Choosing an SAP system ID

You can choose the new SAP system ID <TARGET_SAPSID> freely during a new installation.

CAUTION

To meet the requirements of the Workbench Organizer, you must choose different SAP

system IDs for different SAP systems.

■ SAP license

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

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

system. For more information about ordering and installing the SAP license, see http://

help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by

Key Capability Solution Life Cycle Management SAP Licenses .

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

■ Archiving files

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

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

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

information, see http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver

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

Access to archive files is platform-independent.

■ Configuration analysis and hardware analysis

You need to determine the:

● Number of application servers

● Expected size of the database

● Additional disks or other hardware required

● Required memory

NOTE

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

documentation to determine the system requirements.

■ These methods are not supported for all database systems. See the following table to check which

copy methods are available for your database system:

Database OS Platform Available Methods

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

For more information, see System Copy Procedure [page 22]. ● System copy procedure for a homogeneous system copy

onlyFor more information, see SAP MaxDB-specific procedure [page 63].

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

2 Planning

14/126 PUBLIC 2010-03-16

http://help.sap.com/nw70


http://service.sap.com/licensekey


Database OS Platform Available MethodsFor more information, see System Copy Procedure [page 22].

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

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

For more information, see Starting SAPinst on System i [page 41].

● System i-specific procedure for a homogeneous system copy onlyFor more information, see IBM DB2 for I5/OS Procedure [page 69].

For more information, see SAP Note 585277.

IBM DB2 for Linux, UNIX, and Windows

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

System copy procedure on UNIX using R3loadFor more information, see System Copy Procedure [page 22].End of: UNIX |

● Only valid for: Windows |

System copy procedure on Windows using R3loadFor more information, see System Copy Procedure [page 22].End of: Windows |

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

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

System copy procedure on UNIX using R3loadFor more information, see System Copy Procedure [page 22].End of: UNIX |

● Only valid for: Windows |


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

specific procedure for a homogeneous system copy only, see IBM DB2 for z/OS Specific Procedure [page 69].

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

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

System copy procedure on UNIX using R3load

2 Planning

2010-03-16 PUBLIC 15/126



Database OS Platform Available MethodsFor more information, see System Copy Procedure [page 22].End of: UNIX |

● R3load method with Export/Import MonitorsFor more information, see R3load Procedures Using the Migration Monitor [page 95].

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

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



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

MS SQL Server Windows Use one of the following: ● Only valid for: Windows |



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

2 Planning

16/126 PUBLIC 2010-03-16




3 Preparations

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

3.1 General Technical Preparations

Procedure

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

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

The following describes important preparations. For more information about SAP system

administration, 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 kernel DVD of 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 central instance.

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

points to a valid JDK version.

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

Administration Monitor Update (transaction SM13).

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

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

entries.

Find the canceled or open updates as follows:

1. Call transaction SM13.

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

3. Choose all update requests.

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

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

■ Set all released jobs from Released to Scheduled:

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

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

(include start after event) as follows:

Job Released Scheduled

3 Preparations


2010-03-16 PUBLIC 17/126


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

place while a system is being copied as follows:

Tools CCMS Configuration Operation mode calendar (transaction SM63)

■ Write down the logical system names of all clients:

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

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

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

As the logical system names will be overwritten, in the event of differences, you must change

them back to their original names (as they existed in the system that is overwritten) in the

follow-on actions after the system copy.

2. If you create a new system with a system copy (that is, create an upgrade test system), make

sure that the logical naming strategy for this new system is consistent with your existing logical

system naming convention. If you are still planning your BI (formerly BW) system landscape,

see SAP Note 184447.

3. If your system copy is used to replace hardware for the DB server, migrate to a different database

system or operating system (that is, source system for the copy is the same as the copy target),

no changes to logical system names are required.

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

1. Before deleting you must always check

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

be displayed

● That the data of the original table can be read

● If application programs that use the affected original table do not run correctly, do not

delete the QCM table yet.

2. Call transaction SE14.

3. Choose Extras Invalid temp. table

All QCM tables that can be deleted are displayed.

4. Mark the tables and delete them.

■ FI customers: You can perform an additional consistency check by running the job SAPF190 before

copying the source system, as well as after copying the target system, and then compare the results.

Make sure that no customer data is changed in the meantime. You can do this as follows:

Accounting Financial Accounting General ledger Periodic Processing Closing Check/count

Comparison

■ FI customers: You can further check consistency by running the jobs RFUMSV00 (tax on sales/

purchases), RAGITT01 (asset history sheet), RAZUGA01 (asset acquisitions), RAABGA01 (fixed asset

retirements) before copying the source system, as well as after copying the target system, and then

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

3 Preparations


18/126 PUBLIC 2010-03-16


■ CO customers: You can perform an additional consistency check by running the report group

1SIP before copying the source system, as well as after copying the target system, and then compare

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

CAUTION

Prerequisites for an export:

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

To test if an incremental conversion is in progress, run transaction ICNV. If there are any table

entries in table TICNV, an incremental conversion is in progress. In this case, you have the

following options:

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

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

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

Delete Entry .

● If the tables are in any other state, you have to finish the incremental conversion. Choose

Assistant and proceed according to the online documentation.

CAUTION

Heterogeneous System Copy only:

Before you start the export of your source system, make sure that the tables TATGPC and

TATGPCA are empty. To do so, use your database utility and delete the contents of these tables

with the following statements:

DELETE from TATGPC

DELETE from TATGPCA

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

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

capable fields in these tables.

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

19].

3.2 Installing the Java Runtime Environment

You need to prepare your system for SAPinst. This includes the installation of a Java Runtime

Environment (JRE), which is required both for SAPinst and the SAPinst GUI.

Only valid for: UNIX;Windows |

NOTE

If required, you can perform a remote installation using a standalone SAPinst GUI on a separate

Windows or UNIX host. This lets you perform the installation on a remote host, controlling it

with the SAPinst GUI from a local host. If you want to perform a remote installation, see Performing

3 Preparations


2010-03-16 PUBLIC 19/126

a Remote Installation with SAPinst [page 115]. In this case, you need at least a JRE on the local host to

start the SAPinst GUI there.

End of: UNIX;Windows |

Procedure

1. Check the JRE versions that are released for SAP systems in the Product Availability Matrix (PAM):

1. Go to http://service.sap.com/pam.

2. Only valid for: SAP NetWeaver |

On the right-hand panel, choose SAP NetWeaver SAP NetWeaver 7.0 (2004S) .End of: SAP NetWeaver |

3. Only valid for: SAP CRM;SAP ERP;SAP SCM;SAP SRM |

On the right-hand panel, choose SAP Application Components <your product> .End of: SAP CRM;SAP ERP;SAP SCM;SAP SRM |

4. Choose tabstrip JSE Platforms.

NOTE

For more information about the recommended JRE version for your operating system and

about how to download it, see SAP Note 723909.

2. Make sure a valid JRE version is installed, as follows:

■ If the JRE is not already installed, you need to download and install it.

■ If the JRE is not already installed

Since the JRE is not part of the SAP shipment, you need to download and install it. The JRE is

part of the JDK (Java Development Kit).

■ If the JRE is already installed

Check the installed version of the JRE by entering:

java -version

NOTE

SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment.

If SAPINST_JRE_HOME is not found, SAPinst also checks JAVA_HOME.

Only valid for: UNIX | Linux |

NOTE

If you use a Sun Java VM, you have to perform the following:

Edit the configuration file $JAVA_HOME/jre/lib/security/java.security and replace entry

securerandom.source=file:/dev/random with securerandom.source=file:/dev/urandom.

End of: UNIX | Linux |

3 Preparations


20/126 PUBLIC 2010-03-16

http://service.sap.com/pam


4 Database Independent System Copy

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

independent format. SAPinst uses the R3load tool.

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

archives the configuration and components in the file system.

Constraints

R3load and Jload Restrictions

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

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

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

must still be running.

■ R3load only: Changes to database objects that cannot be maintained in the ABAP Dictionary

(transaction SE14), such as the distribution of tables over several tablespaces or dbspaces, are

lost after the system copy.

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

System Copy Tools

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

installation directory whenever you start SAPinst.

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

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

description in section Additional Information of 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 usually 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.


2010-03-16 PUBLIC 21/126

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

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

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

tool – combined.

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

you select the splitting option and unless you did not already perform some tests, 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.

Process Flow

For UNIX, Windows, or System i, see System Copy Procedure [page 22].

4.1 System Copy Procedure

This section describes the system copy procedure using R3load.

Procedure

Process Flow on the Source System (Export)

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

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

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

■ Central System

■ Distributed System and High-Availability System

Central System

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

1. Heterogeneous system copy: Generate the migration key at http://service.sap.com/

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

2. Perform the export on the central system host:

1. Only valid for: UNIX;Windows |

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

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

2. Only valid for: IBM i5/OS |

Prepare the Windows host for the SAP system installation.

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



22/126 PUBLIC 2010-03-16




Prepare a Windows user account and a System i user profile.

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


Install TMKSVR and create an installation share.

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

5. Generate DDL statements.

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

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

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

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

or parallel import (optional).

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

Running SAPinst on System i to Perform the Export [page 36].

In SAPinst, choose the installation service Export Preparation.

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

instance.

In SAPinst, choose the installation service Database Instance Export.



NOTE

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

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

Result

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

system using SAPinst.

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

Distributed System or High-Availability System

To perform the export for a distributed system or a high-availability-system, you need to proceed

as follows:

1. Heterogeneous system copy only: Generate the migration key at http://service.sap.com/

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

2. Perform the export on the database instance host:

1. Only valid for: UNIX;Windows |

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



2010-03-16 PUBLIC 23/126



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

2. Generate DDL statements.

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

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

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

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

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


Running SAPist on System i to Perform the Export [page 36].

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

choose the installation service Database Instance Export.



NOTE

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

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

CAUTION

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

SAP Note 884452.

Result

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

using SAPinst.

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



24/126 PUBLIC 2010-03-16


Overview on Export Options

Figure 1:

4.2 Generating DDL Statements

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

SMIGR_CREATE_DDL.

You must perform this procedure before starting SAPinst.

Procedure

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

2. Call transaction SE38 and run the program SMIGR_CREATE_DDL.

3. Select the target database. Depending on the database manufacturer, you might need to select the

database version. The value help supports you in selecting the database version. In general, you

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

4. You are able to select Unicode Migration if you also wish to perform a Unicode system copy (from

Unicode to Unicode) or a Unicode conversion (from non-Unicode to Unicode).

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

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

tables.

7. Execute the program.

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


4.2 Generating DDL Statements

2010-03-16 PUBLIC 25/126

CAUTION

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

the report terminates with status successfully, this is not an error.

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

to the <instdir> directory of the export.

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

4.3 Preparation for Table Splitting

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

the table is processed in, for example, 10 entities. Each entity can be processed by different R3load

processes. The advantages of splitting the tables are:

■ Large tables are processed in smaller packages. If the export or import of a table aborts with an

error, only the processing of the package where the error occurred has to be repeated and not for

the complete table.

■ The export and import of one table can be performed in parallel by starting several R3load processes

to work on some packages in parallel.

Prerequisites

■ The export and import has to be performed with the Migration Monitor when the table splitting

feature is used.

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

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

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

● Oracle

For more information, see paragraph Creating a Temporary Index.

Restrictions

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

■ The following tables cannot be split:

● DDNTF

● DDNTF_CONV_UC

● DDNTT

● DDNTT_CONV_UC

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



26/126 PUBLIC 2010-03-16


Procedure

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

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

NUC}.

2. Create a file that contains lines of the form <table>%<nr of splits> for all tables to be split.

CAUTION

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

3. Start SAPinst.

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

Unicode> Table Splitting Preparation .

5. Specify SAPSID, <sidadm> password, the file that contains the split information, the export

directory, and the number of parallel R3ta jobs.

CAUTION

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

6. Continue with Next.

CAUTION

When doing a code page conversion (non-Unicode → Unicode; 4102 ↔ 4103), make sure not

to use a WHERE condition with the column PAGENO included. If the column PAGENO is

included in the WHERE condition, repeat the table splitting - either with different splitting

parameters or by defining a suitable column for this table using the R3ta_hints.txt.

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

created for all tables that are to be split.

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

1. Create a new, empty installation directory.

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

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

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

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

the first Prepare Table Splitting run:

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

directory>/ABAP/DATA.

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

directory>/ABAP/DATA/whr.txt.

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

information, see paragraph Creating a Temporary Index.

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

the target database platform does not support the parallel data import, the Migration Monitor has to



2010-03-16 PUBLIC 27/126

be configured in the way that the data import processes the packages are sequentially. For more

information, see Processing Split Tables.

Using Hints

With the file R3ta_hints.txt, you can instruct R3ta to use specific columns of a table to create a WHERE

condition. The file has to be located in the directory in which you start R3ta.

With one line in the file R3ta_hints.txt, you specify the table name followed by one or more column

names, separated by a blank. The columns have to be part of the primary key of the table. These

specifications are used by R3ta to create the WHERE condition.

A file R3ta_hints.txt with column hints for several tables is delivered with the Installation Master

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

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

directory <IM_OS>/COMMON/INSTALL to the installation directory and adapt it according your

requirements as soon as the Parameter Summary dialog appears and before starting the processing phase.

Creating a Temporary Index

Only valid for: IBM DB2 for z/OS |

IBM DB2 z/OS only: Create the corresponding temporary index on the database with database tools.

Only create a temporary index if you want to perform an unsorted unload. This is the case when you

use a DDLDB2.TPL file with no ORDER_BY_PKEY and the R3load does not overrule this setting. Which

tables cannot be unloaded unsorted is described in SAP Note 954268.End of: IBM DB2 for z/OS |


EXAMPLE

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

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

End of: IBM DB2 for z/OS |


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

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

index:

File Description

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

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

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

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

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



28/126 PUBLIC 2010-03-16



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

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

Make sure that you do not lock the table while creating the temporary index. Depending on your

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

DDL<DBTYPE>.TPL file.End of: IBM DB2 for i5/OS;IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server |

2. Only valid for: Oracle |

Make sure that you do not lock the table while creating the temporary index. Depending on your

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

DDL<DBTYPE>.TPL file.

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

creind: CREATE &unique&

INDEX &ind name&

ON &tab name&

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

TABLESPACE &tablespace&

STORAGE (INITIAL &init&

NEXT &next&

MINEXTENTS &minext&

MAXEXTENTS &maxext&

PCTINCREASE &pctinc& )

NOLOGGING

COMPUTE STATISTICS PARALLEL

ONLINE;End of: Oracle |

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

R3load –dbcodepage <source system’s dbcodepage> –i

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

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

Unicode system, the dbcodepage is 4102 (Big Endian) or 4103 (Little Endian).

4.4 Preparing the Export

Optionally you can prepare the source system for the export using R3load and Jload, so as to enable

parallel export/import. For this purpose you need to create certain files.

The following steps are performed:

■ Creating the export directory structure

■ Creating database structure files (*.STR)

■ Updating database statistics (…)


4.4 Preparing the Export

2010-03-16 PUBLIC 29/126

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

These export preparations are required, if:

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

export of the source system has finished.

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

Procedure

1. You run SAPinst to perform the service Export Preparation.

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

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

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

be transferred to the target host. You can choose one of the following methods:

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

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

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

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

user <sapsid>adm of the target system.

NOTE

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

MIGMON.SAR archive on the SAP Installation Master DVD.

4.5 Exporting the Source System Using SAPinst

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

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

■ Running SAPinst on System i to Perform the Export [page 41]

4.5.1 Running SAPinst on UNIX or Windows to Perform the Export

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

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

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

on the same host. If required, you can 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 115].

Note the following about SAPinst:



30/126 PUBLIC 2010-03-16

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

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

Only valid for: UNIX |

■ SAPinst normally creates the installation directory sapinst_instdir directly below the temporary

directory. SAPinst finds the temporary directory by checking the value of the environment

variables TEMP, TMP, or TMPDIR. If no value is set for these variables, SAPinst uses /tmp as default

installation directory.

■ The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. These

executables are deleted again after SAPinst has stopped running. If required, you can terminate

SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C .End of: UNIX |

Only valid for: Windows |

■ SAPinst normally creates the installation directory sapinst_instdir, where it keeps its log files,

and which is located directly below the Program Files directory. If SAPinst is not able to create

sapinst_instdir directly below the Program Files directory, SAPinst tries to create

sapinst_instdir in the directory defined by the environment variable TEMP.

■ SAPinst creates a subdirectory for each installation service, called <sapinst_instdir>

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

■ The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP, TMP,

TMPDIR, or SystemRoot). These executables are deleted after SAPinst has stopped running.

Directories with the name sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary

directory. You can safely delete them.

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

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

CAUTION

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

FCO-00058.


■ If you want to terminate SAPinst and the SAPinst Self-Extractor, do one of the following:

● Right-click the icon for the SAPinst output window located in the Windows tray and choose

Exit.

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

Exit .End of: Windows |



2010-03-16 PUBLIC 31/126

Prerequisites

CAUTION

Make sure that you shut down all SAP Application Servers before the export. The database must

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

■ Only valid for: UNIX |

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


You are logged on to your host as 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 |

■ Make available the Master Installation DVD.

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

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

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


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

environment variables TEMP,TMP, or TMPDIR to another directory with 200 MB free space for the

SAPinst executables.End of: UNIX |

■ Only valid for: Windows |

Before starting the export steps on the central instance of the source system, make sure that you

have at least the same amount of disk space available in \\SAPLOC\<SAPSID>\<InstanceName>\SDM

\program as is used in \\SAPLOC\<SAPSID>\<InstanceName>\root\origin. During the export

some archives are written to the program subdirectories and SAPinst aborts if there is not enough

space.End of: Windows |

■ Only valid for: DB2 UDB for UNIX and 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: DB2 UDB for UNIX and Windows |


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

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

<InstanceName>/SDM/root/origin.

During the export, some archives are written to the program subdirectories and SAPinst aborts if

there is not enough space.



32/126 PUBLIC 2010-03-16

http://service.sap.com/patches

■ Make sure that the DISPLAY environment variable is set to <host_name>:0.0, where

<host_name> is the host where the SAPinst GUI is displayed.

■ Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime

Environment (JRE).

■ Only valid for: AIX |

If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE for AIX

64-bit.End of: AIX |

End of: UNIX |

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

[page 112], and Performing a Remote Export Using SAPinst [page 114].

Procedure

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


Choose one of the following ways:End of: UNIX |


■ Using the default installation directory (recommended)

Enter the following commands:

cd <Installation_Master_DVD>/IM_<OS> ./sapinst

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

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

■ Using an alternative installation directory

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

TMP, or TMPDIR.

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

$ cd /sapcd2/IM_HPUX_PARISC

$ /sapcd2/IM_HPUX_PARISC/sapinst End of: UNIX |



2010-03-16 PUBLIC 33/126


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

<DVD_drive>:\DATA_UNITS\IM_WINDOWS_<platform>

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

NOTE

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

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

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

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

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

<DVD drive>:\IM_WINDOWS_<platform>.

Enter the following command in a single line:

sapinst.exe

SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server>

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>

For a list of all available SAPinst properties, enter the following command: sapinst —p.

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

<Distribution option> Based on <technical stack> .

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

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

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

Copy [page 21].

CAUTION

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

system variant.

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

export:

Export Services for a Central System

Export Service Remarks

Export Preparation

NOTE

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

Optional step for preparing the export.SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.STR) ■ Updates database statistics (…) ■ Calculates the size of the target database

(*.EXT,DBSIZE.XML)

Database Instance Export Mandatory step for database-independent system copy procedure. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.STR)



34/126 PUBLIC 2010-03-16

Export Service RemarksNOTE


■ Updates database statistics (…) ■ Calculates the size of the target database

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

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

NOTE

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

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

SAPinst. The installation directory will have been created as soon as the first input screen

appears.

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

CAUTION

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

NOTE

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

parameter field and choose F1 .

6. Database-specific procedures only: On the screen SAP SystemDatabase Export choose option System

Copy Method Use database specific tools .

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

during the processing phase.

Troubleshooting

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

operating system crash), you have to repeat the export of the complete package. Remove the dump

files <package>.<nnn>, the TOC file <package>.TOC, the log file <package>.log and make sure that

all tables in the TSK file <package>.*TSK* have the status flag 'xeq' or 'err' set.

■ If there is not enough disk space in the export directory, the R3load database export fails. You can

then find error messages in the log files SAP*.log.

You can 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 there is no

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



2010-03-16 PUBLIC 35/126


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 <sid>adm or ora<sid> OS users cannot create or open files in the installation

directory.

Reason:

Only members of sapinst UNIX group can access the installation directory.

This group is created first by SAPinst starting from NW 7.0 SR1.

Solution:

Associate <sid>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 will create this group during startup

before product catalog list will be displayed.

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

Continue with the export.End of: UNIX |

For more information, see Using SAPinst GUI [page 111], Interrupted Installation with SAPinst [page 112], and

Performing a Remote Export Using SAPinst [page 114].

Only valid for: IBM i5/OS |

4.5.2 Running SAPinst on System i to Perform the Export

4.5.2.1 Preparing the Windows Host for the SAP System Installation

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

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

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

SAPinst.

Prerequisites

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



36/126 PUBLIC 2010-03-16

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

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

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

■ Set the system path if you install on Windows.

Procedure

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

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

including the SAP J2EE Engine.

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

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

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

NOTE

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

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

java -version

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

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

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

\bin is included in your system path.

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

4.5.2.2 Preparing a Windows User Account and System i User Profile

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

profile on the System i you want to install.

The following requirements apply:

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

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

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

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

■ Only valid for: SAP SCM |

The System i user profile must be the user QSECOFR.



2010-03-16 PUBLIC 37/126

http://service.sap.com/platforms

http://service.sap.com/platforms

NOTE

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

that you create user SAPINST or SAPINSTUSR. However for SCM, you need to use the user

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

End of: SAP SCM |

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

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

NOTE

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

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

has introduced a group called SAPINST on System i which conflicts with the previously

recommended user SAPINST.

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

Windows:

1. Create a local user.

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

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

3. Only valid for: SAP SCM |

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


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


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

6. Deselect User must change password at next logon.


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


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

System i:

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

Enter the command CRTUSRPRF USRPRF(SAPINSTUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('Test

User for SAP Installation') SPCAUT(*USRCLS) LANGID(ENU) CNTRYID(US) CCSID(500).End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM |



38/126 PUBLIC 2010-03-16

Only valid for: SAP SCM |

To change the user QSECOFR, enter the command CRTUSRPRF USRPRF(QSECOFR) LANGID(ENU) CNTRYID

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

CAUTION

You should not set the system variable QIBM_PASE_CCSID. You should leave this variable empty!

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


4.5.2.3 Installing TMKSVR and Creating an Installation Share

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

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

for System i are initiated remotely on Windows but executed locally using the TMKSVR. The

communication is done using TCP/IP.

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

installation host, which is done automatically by the TMKSVR.

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

instances of an SAP system should be installed.

Prerequisites

■ An FTP server running on System i

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

User Account and System i User Profile [page 37].

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

■ Make sure there is no system variable LANG defining a LOCAL. Otherwise, code page problems might

prevent TMKSVR processes from starting.

Procedure

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



NOTE

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

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




2010-03-16 PUBLIC 39/126


NOTE

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

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

End of: SAP SCM |

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

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

Explorer.

The following dialog box appears:


Figure 2:



Figure 3:

End of: SAP SCM |

3. Enter the following values:



40/126 PUBLIC 2010-03-16

■ System i Hostname:

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

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

System i Administrator (QSECOFR or similar):

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

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

■ Only valid for: SAP SCM |

System i Administrator (QSECOFR):

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

User Profile [page 37].End of: SAP SCM |

■ TMKSVR instance number:

Leave the value at 0.

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

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

during installation because the port is in use.

ResultThe installation uses FTP to install and starts the TMKSVR on System i. During installation, a library

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

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

Windows PC or let SAPinst map it during the installation.

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

\TMKSVR.End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

Only valid for: IBM i5/OS |

4.5.2.4 Starting SAPinst on System i

CAUTION

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

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

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

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

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.



2010-03-16 PUBLIC 41/126

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

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

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

Installation [page 36].

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


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

Procedure

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


2. Start SAPinst from the SAP Installation Master DVD in one of the following ways:

■ If using the default installation directory (recommended) by double-clicking sapinst.exe from

the following path:

<Mapped drive>:<copied ... DVD>\IM_OS400_PPC64

NOTE

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

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

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

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

change to the required directory as follows:

<Mapped drive>:<copied ... DVD>\IM_OS400_PPC64

Enter the following command in a single line:

sapinst.exe

SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server>

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to sapinst_gui>

● For a list of all available SAPinst properties, enter the following command: sapinst

-p

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

i parameters. Enter your values.



42/126 PUBLIC 2010-03-16

Figure 4:

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

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

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

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

the process flow for one of the following precedures:

■ Database-Specific System Copy [page 51]

■ Database-Independent System Copy [page 21]

CAUTION

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

system variant.

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

■ Central system

■ Distributed system or high-availability system

Export Services for a Central System


Export Preparation

NOTE


Optional step for preparing the export.SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.STR) ■ Updates database statistics (…) ■ Calculates the size of the target database

(*.EXT,DBSIZE.XML)



2010-03-16 PUBLIC 43/126


Database Instance Export

NOTE


Mandatory step for database-independent system copy procedure. 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 ABAP database content

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


Export Preparation

NOTE


Optional step for the database-independent system copy procedure to prepare the export.You need to perform this step on the database instance host.SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.STR) ■ Updates database statistics(…) ■ Calculates the size of the target database

(*.EXT,DBSIZE.XML)

Database Instance Export

NOTE

■ You do not perform this step if you use the database-specific method.

Mandatory step for the database-independent system copy procedure.You need to perform this step on the database instance host.SAPinst performs the following steps: ■ Creates the export directory structure with label files ■ Creates database structure files (*STR) ■ Updates database statistics ■ Calculates the size of the target database

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

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

8. Choose Next

NOTE

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

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

SAPinst:

1. Choose Database and Central Instance Export

2. Choose Next.

3. The installation directory has been created as soon as the first input screen appears.

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

CAUTION

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



44/126 PUBLIC 2010-03-16

NOTE

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

parameter field and choose F1 .

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

the progress of the installation.

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

Troubleshooting

CAUTION

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

operating system crash), you have to repeat the export of the complete package. Remove the

dump files <package>.<nnn>, the TOC file <package>.TOC, the log file <package>.log and make

sure that all tables in the TSK file <package>.*TSK* have the status flag 'xeq' or 'err' set.

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

● Stops the installation.



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

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

● Stops the installation.



● Try to solve the problem.

● Retry the installation by choosing Retry.

● Abort the installation by choosing OK.

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

End of: IBM i5/OS |

4.5.3 Restarting R3load Processes

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

EXAMPLE

For example, if package processing failed and the package state has the value –, the state can be

set to 0 and processing of the package is restarted.

Procedure

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



2010-03-16 PUBLIC 45/126

■ To skip package processing, set the package state from 0 or – to +. (This is not recommended,

because it can cause inconsistent data files or database content.)

■ If the package is currently being processed (the package state is ?), then any manual modifications

of the package state are ignored.

■ Sockets only: You cannot restart processes.

Restarting R3load Processes Using the Socket Option

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

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

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

continue with the system copy proceed as follows:

■ If both the import and the export are completed successfully, there is nothing to do.

■ If the export was completed successfully, but the import is cancelled with errors, proceed as

follows:

● If the export was successful but the import was cancelled when creating the index or the

primary key, set the status for export_state.properties from '+' to '0'.

● If the export was completed successfully but the import was cancelled when loading the

table content, set the status

◆ for export_state.properties from '+' to '0'

◆ for the TSK file of the export from 'ok' to 'err'

■ If both the export and the import are cancelled with errors, proceed as follows:

● If the errors in export and import relate to the same table, there is nothing to do.

● If the errors relate to different tables, set the status of the first object with errors (export as

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

EXAMPLE

Export Import

Table name Status Table name Status

TAB_1 ok TAB_1 ok

TAB_2 err TAB_2 ok

TAB_3 xeq TAB_3 err

TAB_4 xeq TAB_4 xeq

The first object with errors here is TAB_2 (export). That means that in the import TSK

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

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

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

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

More Information

See also R3load Processes Using the Migration Monitor [page 95].



46/126 PUBLIC 2010-03-16

4.6 Setting Up the Target System

Purpose

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

the source system.

Process Flow

Central System

Perform the following steps on the central system host:

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

installation guide for your SAP system solution.

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

the source system because you want to perform the export and import in parallel, you perform

the following steps:

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

Exchange Directory on the screen SAP SystemCommunication Parameters for Export), you make sure

that you have transferred all files that have been generated in step Preparing the Export [page 29]

on the source system.

2. You install the target system. For more information, see Installing the Target System [page 48].

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

Target System [page 48].

3. If required, on (the) dialog instance host(s), you install additional dialog instance(s) as described

in the installation guide for your SAP system solution.

Distributed System or High-Availability System

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

1. You prepare the central instance host and the database instance host for the installation of

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

SAP system solution.

Only valid for: High Availability |

You also prepare the central services instance host.End of: High Availability |

2. Only valid for: High Availability |

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

guide for your SAP system solution.End of: High Availability |

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

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

29]) on the source system, you perform the following steps:

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

type Exchange Directory on the screen SAP SystemCommunication Parameters for Export), you



2010-03-16 PUBLIC 47/126

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

the Export [page 29] on the source system.

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

the Target System [page 48].

■ If you did not prepare the export (for more information, see Preparing the Export [page 29]) on

the source system, you install the database instance of the target system. For more information,

see Installing the Target System [page 48].

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

5. If required, on (the) dialog instance host(s), you install additional dialog instance(s) as described

in the installation guide for your SAP system solution.

4.6.1 Installing the Target System

PrerequisitesOnly valid for: Windows |

Make sure there is enough free space on the target system for the database load. To find out the size of

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

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


Make sure there is enough free space on the target system for the database load. To find out the size of

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

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

NOTE

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

is performed automatically by SAPinst. If the database software has already been unpacked or

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

related steps.

Procedure

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

on SAP NetWeaver 7.0 SR3.

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

NOTE

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

installation documentation.

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



48/126 PUBLIC 2010-03-16

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

SAP NetWeaver 7.0 SR3.

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

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

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

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

4. You run the installation service(s) required for your system copy in the sequence they are listed

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

47].

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

required parameters up to the screen Database - Select the Database Instance Installation Method.

On this screen, you choose the option Standard System Copy/Migration (load-based):

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

loaded in the newly installed SAP system database.


CAUTION

■ Make sure that you take the information about automatic storage into consideration

that is provided in section Running SAPinst in the appropriate installation guide.

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

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

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

CAUTION

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

following directories:

● UNIX: /usr/sap/<SAPSID>

Windows: \usr\sap\<SAPSID>

● UNIX: /sapmnt/<SAPSID>

Windows: \sapmnt\<SAPSID>

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

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

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

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

system.

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

the path to the export directory <EXPDIR>.

7. If you perform a heterogeneous system copy, enter the Migration Key on the screen Database

Import.

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



2010-03-16 PUBLIC 49/126

NOTE

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

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

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

NOTE

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

with the table that was not imported successfully.

For more information about restarting failed R3load processes, see Restarting R3load Processes

[page 45].



50/126 PUBLIC 2010-03-16

5 Database-Specific System Copy

The following sections describe system copy procedures that base on database-specific methods.

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

methods available for your database, see Planning [page 11] and the SAP Notes describing the

homogeneous system copy for your database system.

Process

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

■ Central System

■ Distributed System

■ High Availability System

Central System

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

host:


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

2. If required, you create a backup of the source database [page 58].

Process Flow on the Target System

1. Only valid for: Windows |

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

2. Only valid for: UNIX |

You prepare the target system [page 59]:

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

software and to perform the database backup/restore.

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.


2010-03-16 PUBLIC 51/126

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

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

2. If required, on the database instance host, you create a backup of the source database [page 58].

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


You prepare the target system [page 59]:

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.

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


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



52/126 PUBLIC 2010-03-16

the copy is a complete data backup of your source database. You can use an offline backup, an online

backup, or the file system of your source host.

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

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

content are different.

Advantages

■ You can use existing offline or online backups.

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

Disadvantages

■ Backup/copy of database files in a heterogeneous environment is not possible because the hardware

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

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

■ You must shut down the SAP system and the database when you create an offline backup manually

or an offline backup with BR*Tools.

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

Prerequisites

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

system.

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

■ The ojdbc14.jar must exist in the /ORACLE/client/10x_64/instantclient (installed using a

standard Oracle installation).

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

on the database instance.

■ The JAVA_HOME environment variable must point the JRE directory.

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

■ The source and target systems must be binary compatible.

NOTE

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

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

compatible.

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

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

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

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

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



2010-03-16 PUBLIC 53/126

5.1.1 Generating the Control File Structure

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

without further adaptations on the target system.

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

of the OraBRCOPY.SAR archive.

Prerequisites

RECOMMENDATION

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

database must still be running.

Procedure

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

2. Copy the ORABRCOPY.SAR archive from the SAP Installation Master DVD to the installation directory

and extract it using SAPCAR.

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


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

End of: UNIX |


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

End of: Windows |

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

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

user ora<dbsid>

user <sapsid>adm

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

● On UNIX:

./ora_br_copy.sh –generateFiles –forceLogSwitches —targetSid

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

● On Windows:

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

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

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

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

switches.

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

● On UNIX:



54/126 PUBLIC 2010-03-16

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

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

● On Windows:

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

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

NOTE

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

command must not contain the parameter —forceLogSwitches.

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

installation directory, and performs the required log switches.

NOTE

If an error occurs, check the log file:

<INSTDIR>/ora.brcopy.log

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

follows.

Example for Windows

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

the trace file:

REM

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

REM CONTROL.SQL

REM

REM SAP AG Walldorf

REM Systeme, Anwendungen und Produkte in der Datenverarbeitung

REM

REM (C) Copyright SAP AG 2004

REM

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

REM Generated at:

REM Fri Sep 17 08:33:25 CEST 2005

REM for target system NEW

REM on

REM Windows 2000 5.0 x86

CONNECT / AS SYSDBA

STARTUP NOMOUNT

CREATE CONTROLFILE REUSE

SET DATABASE "NEW"



2010-03-16 PUBLIC 55/126

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









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





56/126 PUBLIC 2010-03-16









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

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

;

ALTER DATABASE OPEN RESETLOGS;

ALTER TABLESPACE PSAPTEMP ADD TEMPFILE

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

SIZE 350M REUSE AUTOEXTEND OFF;

NOTE

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

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

Changes to be made

1. If you want to upgrade your database from 32-bit to 64-bit, add the following lines at the bottom

of the control.sql file:

shutdown immediate;

startup restrict

spool utlirp.log

@?/rdbms/admin/utlirp.sql

spool off

alter system disable restricted session;

2. MAXLOGFILES 255

...

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

3. GROUP 1 (



) SIZE 50M,

Group 2 (

…



2010-03-16 PUBLIC 57/126

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

Create a backup if required. Choose between the following possibilities: Performing an offline backup

manually or an offline or online backup with BR*Tools.

■ Creating an Offline Backup Manually [page 58]

■ Creating an Offline or Online Backup with BR*Tools [page 59]

5.1.2.1 Creating an Offline Backup Manually

Procedure

There are different possibilities to prepare the actual transfer of the database files:

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

up with forced log switches).

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

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

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

system trees that have to be saved.

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

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

now. Proceed with the next step.



58/126 PUBLIC 2010-03-16

NOTE

If you choose this manual offline backup method, you also have to restore the database files on

the target system manually. For more information, see Restoring the Database Files on the Target System

Manually [page 61].

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. For BACKINT and RMAN, the external backup tools must also

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

Procedure

Proceed as described in the SAP Library at:

help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library Administrator’s Guide

Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration

Database Administration for Oracle BR*Tools for Oracle DBA BR*Tools in Action Backup and Database Copy

with BR*Tools

NOTE

If you choose a backup method with BR*Tools, you also have to restore the database files on the

target system with BR*Tools. For more information, see Restoring the Database Files on the Target System

with BR*Tools [page 62].

5.1.3 Preparing the Target System

Prerequisites

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

Procedure

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

SAP solution.

CAUTION

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

the database schema and the table space names of the new target system. When installing the

target central instance, database instance, or dialog instance make sure that you enter the

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

The schema names of the source and target system must be identical.



2010-03-16 PUBLIC 59/126

1. On the Welcome screen, choose the required installation service:

SAP NetWeaver 7.0 Support Release 2 Software Life-Cycle Options System Copy Oracle Target

System <Central System | Distributed System | High-Availability System> .

2. When SAPinst prompts for the installation type, choose Homogeneous System Copy (Backup/

Restore).

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

The following message is displayed:

SAPinst now stops the installation. Please proceed as follows:...

2. If necessary, extract the Oracle stage archives manually and install the Oracle Software as described

in the installation documentation for your SAP solution.

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

■ UNIX:

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

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

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



60/126 PUBLIC 2010-03-16

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

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

/oracle/<TARGET_DBSID>/saparch and /oracle/<TARGET_DBSID>/oraarch

<drive>:\oracle\<TARGET_DBSID>\saparch and <drive>:\oracle\<TARGET_DBSID>\oraarch


All directories must be owned by the user ora<target_dbsid>.

To achieve this, enter the following command:

chown ora<target_dbsid>:dba<directory>

End of: UNIX |

6. Set the security settings for the built-in accounts and groups SYSTEM, Administrators,

SAP_<SAPSID>_GlobalAdmin (domain installation), and SAP_<SAPSID>_LocalAdmin (local

installation) for all directories as follows:

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

2. Under Security, choose Advanced.

3. Deselect Allow inheritable permissions from the parent....

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

from the parent to this object.

5. Choose OK.

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

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

7. Delete all other accounts.

7. Restore the database files on the target system either manually (see Restoring the Database Files on the

Target System Manually [page 61]) or with BR*Tools (see Restoring the Database Files on the Target System

with BR*Tools [page 62]), then proceed with SAPinst.

5.1.4 Restoring the Database Files on the Target System Manually

CAUTION

If you do not use a backup but copy the database files directly from the source to the target system

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

files from the source to the target directories.

Procedure

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

the source directories to the target directories. For more information, see Creating an Offline Backup

Manually [page 58].

Directories on UNIX:



2010-03-16 PUBLIC 61/126

Source and Target Directory Files

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

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

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

source: <INSTDIR> target: <SAPINST_INSTDIR>

CONTROL.SQL

source: <INSTDIR> target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/dbs

init<TARGET_DBSID>.ora

Directories on Windows:


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

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

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


CONTROL.SQL

source: <INSTDIR> target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database



NOTE

The installation directory of the target system is normally located in the directory:

%programfiles%\sapinst_instdir\NW04S\LM\COPY\ORACLE\SYSTEM\<system_variant>

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

files from the source directories to the target directories manually.

■ On UNIX:



CONTROL.SQL



62/126 PUBLIC 2010-03-16


source: <INSTDIR> target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/dbs


■ On Windows:



CONTROL.SQL

source: <INSTDIR> target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database


2. Create an Oracle spfile from init<TARGET_DBSID>.ora profile as follows:

SYNTAX

sqlplus /nologconnect / as sysdbacreate spfile from pfile;exit

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

For more information about the required steps and prerequisites, see SAP Note 1003028.

The main prerequisite is that the corresponding BR*Tools logs (BRBACKUP detailed and summary

log, BRARCHIVE summary log) are copied manually from the source to the target system. In addition,

the postprocessing steps mentioned in this SAP Note are performed automatically by SAPinst.

SAP Note 1003028 also comprises information about executing restore and recovery under the

control of BRRECOVER and the exact syntax of BRRECOVER (see section Homogeneous Database Copy).

For more information about BR*Tools, see help.sap.com/nw70 SAP NetWeaver 7.0 Library English

SAP NetWeaver Library Administrator’s Guide Technical Operations Manual for SAP NetWeaver General

Administration Tasks Database Administration Database Administration for Oracle BR*Tools for Oracle

DBA .

4. Shut down the Oracle database instance as follows:

SYNTAX

sqlplus /nologconnect / as sysdbashutdown immediateexit

End of: Oracle |

Only valid for: MaxDB |

5.2 SAP MaxDB-Specific Procedure

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

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

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

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

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



2010-03-16 PUBLIC 63/126



database installation method. SAPinst stops before the database instance initialization and asks you to

perform the recovery on the target database. After you have performed recovery and post-recovery

activities you can continue the installation in SAPinst.

This description is not valid for the liveCache system copy.

Advantage

■ You can use existing offline backups.

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

Disadvantage

You can only copy between systems with the same byte order. For more information, see below.

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

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

You can find more information on DBMGUI at either of the following:

● http://dev.mysql.com/doc SAP MaxDB by MySQL SAP MaxDB Online Library Tools

● http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Databases SAP MaxDB Tools Database Manager GUI

■ Database Software

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

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

to the version on the source host.

■ Size of the data on the target system

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

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

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

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

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

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



64/126 PUBLIC 2010-03-16


http://dev.mysql.com/doc


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

The JAVA_HOME environment variable must point to the JRE directory.

Process

1. You do the following on the source system:

1. If you do not already have a suitable recent complete SAP MaxDB backup, you create a

complete data backup using the DBMGUI tool:

DBMGUI Backup Backup Wizard Complete

2. You make the backup medium available on the target host.

2. You do the following on the target system:

1. To install the new system you start SAPinst as follows:

SAP NetWeaver 7.0 Lifecyle Management System Copy SAP MaxDB Target System <Central

System | Distributed System | High-Availability System> .

During the installation of the database instance, SAPinst stops before database initialization in

the screen Perform Database Recovery and asks you to perform the data recovery.

2. You start the data recovery wizard from DBMGUI

1. You register your database instance in the DBMGUI

2. You check the database instance in the admin state.

3. You choose Recovery Recovery with Initialization ...

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

5. You specify the backup medium.

6. You start the restore procedure.

NOTE

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

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

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

to online if it is not already in online state.

4. You delete the entries from the following tables to make sure that information about the

backup history for update statistics in the Computing Center Management System (CCMS)

from the old system does not appear in the new system:

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

SDBAADAUPD

5. You continue with SAPinst or restart it if you stopped it during the recovery.

6. After installation is completed you maintain the database connection for CCMS. For more

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



2010-03-16 PUBLIC 65/126


Only valid for: Windows | MS SQL Server |

5.3 MS SQL Server-Specific Procedure

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

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

installation tool supports both methods.

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

to the R3load method:

■ You can use an existing backup.

■ These methods are much faster than the database-independent method [page 21].

NOTE

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

151603.

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

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

● You can only attach SQL Server 2000 files to SQL Server 2005 but not vice versa.

Process1. 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 SAP system> Software Life-Cycle Options System Copy MS SQL Server Target System <system

variant> <technical stack>

NOTE

■ The target system is installed using the exports from the source system.

■ Choose the installation services 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/installnw70.

■ On the SAPinst screen SAP SystemDatabase make sure to select Homogeneous System Copy (MS

SQL Server-specific: Detach/Attach or Backup).End of: Windows | MS SQL Server |


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

In an SAP system environment, you can create a homogeneous system copy of a DB2 database using

the backup method or by relocating your database. The relocation of the database is usually used in


5.3 MS SQL Server-Specific Procedure

66/126 PUBLIC 2010-03-16





conjunction with split mirror. For more information, see the documentation Database Administration

Guide: SAP on IBM DB2 Universal Database for UNIX and Windows, section The db2inidb Tool and the DB2

documentation.

This section provides information on the backup method.

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

documentation for your SAP component.

In an ABAP system, only the SAPinst steps for setting up and loading the database steps are replaced by

a database restore.

Advantages of the Backup Method

■ You can use existing offline backups.

■ Using the backup method is faster than the database-independent method [page 21].

Disadvantages of the Backup Method

■ You cannot change the database schema. The database schema will be the same as of the source

system.

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

complete system.

Prerequisites

■ The source and target database systems should be binary compatible.

NOTE

With DB2, it is possible to use backup images cross platform for AIX, Solaris and HP-UX.

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

repeated.

Process

1. You perform an offline backup or restore an existing backup copy.

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

Welcome screen:

<Your SAP system> Software Life-Cycle Options System Copy IBM DB2 for Linux, UNIX, and Windows

Target System <system variant> <technical stack>

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

dialogs. During the installation phase SAPinst prompts you to perform the database restore.

CAUTION

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

system copy:

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



2010-03-16 PUBLIC 67/126

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

change them after the installation.

■ If you want to change the container names on the target system, you have to adapt the

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

For the restore of your database, you can choose between one of the following options:

■ Simple database restore

To perform a database restore, use the DB2 restore command. For more information see the

IBM DB2 documentation DB2 Command Reference.

■ Redirected restore

To perform a redirected restore, use the tool brdb6brt that retrieves a database backup and

creates a CLP script for the restore of this backup image. For more information about how to

use the tool brdb6brt, see the documentation Database Administration Guide: SAP on IBM DB2

Universal Database for UNIX and Windows section Usage of Tool brdb6brt and the IBM DB2

documentation DB2 Command Reference.

3. Perform the database restore.

If you have used an online backup, you have to make sure that you have access to the log files that

were created during the online backup. You also have to perform a roll forward operation to bring

the database into a consistent state.

You can now continue with the installation.

4. If required, you can modify the table space names after the installation using the following

command:

db2 rename tablespace <old name> to <new name>

EXAMPLE

db2 rename tablespace <SAPSID_SOURCE>#STABD to <SAPSID_TARGET>#STABD

In addition, you have to update the table space names in tables TSDB6, IADB6 and TADB6 using

the following commands:

■ For table TSDB6, enter the following SQL command:

update <connect_user_name>.tsdb6 set tabspace = '<SAPSID_TARGET>#'||substr

(tabspace,5,length(tabspace)-4),indspace='<SAPSID_TARGET>#'||substr(indspace,

5,length(indspace)-4)

■ For table IADB6, enter the following SQL command:

update <connect_user_name>.iadb6 set tabspace = '<SAPSID_TARGET>#'||substr

(tabspace,5,length(tabspace)-4)

■ For table TADB6, enter the following SQL command:



68/126 PUBLIC 2010-03-16

update <connect_user_name>.tabdb6 set tabspace = '<SAPSID_TARGET>#'||substr

(tabspace,5,length(tabspace)-4)

More Information

IBM DB2 documentation DB2 Command ReferenceEnd of: IBM DB2 for Linux and UNIX and Windows |

Only valid for: IBM DB2 for i5/OS |

5.5 IBM DB2 for i5/OS Procedure


the SAV/RSTLIB system copy method.

Advantage of the Offline System Copy Method

This method is faster than the database-independent method [page 21].

For more information, see SAP Note 585277.

CAUTION

You can only copy for IBM DB2 for i5/OS.

End of: IBM DB2 for i5/OS |


5.6 IBM DB2 for z/OS Specific Procedure


the offline system copy method.

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.

Advantage of the Offline System Copy Method

This method is faster than the database-independent method [page 21].

Restriction of the Offline System Copy Method

At the moment, you cannot copy an individual MCOD component to another system. You can only

copy the complete system.


5.5 IBM DB2 for i5/OS Procedure

2010-03-16 PUBLIC 69/126


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.

■ Table spaces 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

■ 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 re-creating 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



70/126 PUBLIC 2010-03-16

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:

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.



2010-03-16 PUBLIC 71/126


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 69] 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 83].

Output

The output of this statement is similar to the following:

EXAMPLE

---------+---------+---------+---------+---------+-----

NAME DBNAME INDEXSPACE

---------+---------+---------+---------+---------+-----

SYSTBLSP~0 DSNDB06 SYSTBLSP

SYSTABLE~0 DSNDB06 SYSTABLE

SYSIXPART~0 DSNDB06 SYSIXPAR





SQL Statements.



72/126 PUBLIC 2010-03-16



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)

.

.

.

etc.





SQL Statements.

With this statement, you identify all table spaces to be connected at a later point in time to the temporary

storage group TEMPORA:

NOTE




2010-03-16 PUBLIC 73/126


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


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;



74/126 PUBLIC 2010-03-16


.

.

etc.





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;

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;

.

.

etc.





2010-03-16 PUBLIC 75/126




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 Storagegroup 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>

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;



76/126 PUBLIC 2010-03-16


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;

.

.

etc.





SQL Statements.

With this statement, you connect table spaces with their previous storage groups, which now contain

the high-level qualifier of the target system.

NOTE


Output


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;

.

.

etc.



2010-03-16 PUBLIC 77/126






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;

.

.

etc.





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)



78/126 PUBLIC 2010-03-16



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

.

.

etc.

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.

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)



2010-03-16 PUBLIC 79/126

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

All statements are located in the .zip file [page 69] 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 8: Printing the Bootstrap Data Sets

Prerequisites

The source system must be stopped at this point.



80/126 PUBLIC 2010-03-16



Statement

This JCL job is located at

HSCProcedure\Step8\PROLOGMAP.JCL


SQL Statements.

With this statement, you print the bootstrap data sets. You can use the output of this statement to

manipulate the bootstrap data sets in the target system.

Output


SYNTAX

. . . GROUP NAME: ........ BSDS COPY 1 DATA SET NAME: ............................................ BSDS COPY 2 DATA SET NAME: ............................................ ENFM START RBA/LRSN: 000000000000 ACTIVE LOG COPY 1 DATA SETS START RBA/TIME END RBA/TIME DATE LTIME DATA SET INFORMATION -------------------- -------------------- -------- ----- -------------------- 0034A0468000 0034AC7DFFFF 2003.106 12:12 DSN=D8A0.LOGCOPY1.DS01 2004.163 18:31:44.4 2004.163 20:14:45.7 PASSWORD=(NULL) STATUS=REUSABLE 0034AC7E0000 0034B8B57FFF 2003.106 12:12 DSN=D8A0.LOGCOPY1.DS02 2004.163 20:14:45.7 2004.163 20:37:23.1 PASSWORD=(NULL) STATUS=REUSABLE 0034B8B58000 0034C4ECFFFF 2003.106 12:12 DSN=D8A0.LOGCOPY1.DS03 2004.163 20:37:23.1 ........ .......... PASSWORD=(NULL) STATUS=REUSABLEARCHIVE LOG COPY 1 DATA SETS NO ARCHIVE DATA SETS DEFINED FOR THIS COPY ACTIVE LOG COPY 2 DATA SETS NO ACTIVE DATA SETS DEFINED FOR THIS COPY ARCHIVE LOG COPY 2 DATA SETSNO ARCHIVE DATA SETS DEFINED FOR THIS COPY . . . etc.

5.6.9 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 69] 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



2010-03-16 PUBLIC 81/126



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.10 Step 9b: Start the Target System

When you start the DB2 target system for the very 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 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 . . . . etc.

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.



82/126 PUBLIC 2010-03-16

The work file database data must be changed later in the clone process.

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


HSCProcedure\Step9c\CRTMPSTO.JCL

.zip file [page 69] attached to SAP Note 680746. For more information, see the section JCL Jobs and SQL

Statements.

NOTE


5.6.12 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 72].

The JCL job is located at

HSCProcedure\Step9d\STOPIDXS.JCL


SQL Statements.

5.6.13 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 72])

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.14 Step 9f: Restart the Index Spaces

At this point, you must restart the index spaces.



2010-03-16 PUBLIC 83/126




5.6.15 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 69] 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 80] should not occur since DB2 is working with the new temporary files.

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

Error message IKJ56228I should not appear because DB2 is now working with its own work file

database.

5.6.17 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.18 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.



84/126 PUBLIC 2010-03-16


In the following steps, the DB2 catalog is manipulated by stopping the databases, altering table-spaces

and indexes, dropping and creating storage groups with the new VCAT D8B0, altering table-spaces 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 69] 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 table spaces 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


HSCProcedure\Step10\CREATSTG.JCL.

6. Alter table spaces 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.



2010-03-16 PUBLIC 85/126


5.6.19 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

5. If the schema of the SAP source system is not SAPR3 and if you do not intend to change the schema

name, create a new DB2 stogroup for each existing stogroup. These new stogroups reflect the SAP

system ID of the new SAP system instead of the SAP system ID of the source SAP system.

To create the stogroups, submit the following statement:

CREATE STOGROUP <stogroup_name> VOLUMES (*) VCAT <vcat_name>

where <vcat_name> is the VCAT name of the new DB2 subsystem.

EXAMPLE

If an existing stogroup name is OLDDID and if the SAP system IDs of the source and target

systems are OLD and NEW, respectively, then a new stogroup needs to be created with the name

NEWDID.

The existing stogroups in the DB2 target system, which reflect the SAP system ID of the source system,

do not need to be changed and are still used by the existing database objects of the new SAP system. As

these names are only used internally in DB2, they do not interfere with the stogroups of the DB2 source

system.

For details on the SAP exploitation of DB2 stogroups, see the SAP DBA Guide: DB2 for z/OS, section

Additional Information.

If necessary, change the user authorizations of the target system. The DB2 catalog still contains the

authorizations of the source system.

5.6.20 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 invoked R3ldctl on your source system to capture the view

definitions of the SAP system.



86/126 PUBLIC 2010-03-16

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

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. Create a new DB2 stogroup for each existing stogroup. These new stogroups reflect the SAP system

ID of the new SAP system instead of the SAP system ID of the source SAP system.

To create the stogroups, submit the following statement:

CREATE STOGROUP <stogroup_name> VOLUMES (*) VCAT <vcat_name>

where <vcat_name> is the VCAT name of the new DB2 subsystem.

EXAMPLE

If an existing stogroup name is OLDDID and if the SAP system IDs of the source and target

systems are OLD and NEW, respectively, then a new stogroup needs to be created with the name

NEWDID.

8. Re-create 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.

9. If user-defined materialized query tables or triggers exist, re-create them.



2010-03-16 PUBLIC 87/126

5.6.21 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 |



88/126 PUBLIC 2010-03-16

6 Follow-Up Activities

To finish the system copy of your SAP system:

■ Perform follow-up activities in the source system [page 89]

■ Perform follow-up activities in the target system [page 89]

6.1 Performing Follow-Up Activities in the Source System

Procedure

1. Reschedule your canceled jobs: Tools CCMS Jobs Maintenance (SM37) .

2. Using CCMS, adapt your operation mode timetable to the original status: Tools CCMS

Configuration Operation mode calendar (SM63) .

6.2 Performing Follow-Up Activities in the Target System

6.2.1 Performing Follow-Up Activities for ABAP

Procedure

Actions at Operating System Level

1. Adapt the configuration files at operating system level to meet network and SAP requirements.

2. Adapt additional SAP software components (for example, RFC, CPIC, SAP ArchiveLink) if required.

3. Adapt additional non-SAP software components (for example, archiving systems, monitoring

tools, job schedulers) if required.

4. Adapt backup programs (for example BRBACKUP, BRARCHIVE, BACKINT) if required.

5. Adapt non-SAP directories, file systems, NFS mounts, and so on if required.

6. Check the SAP parameters of the default and instance profiles.

7. Check your UNIX shell files for special entries.

8. Check crontab or AT jobs.

9. Check operating system files (for example, .netrc, .rhosts).

10. Check operating system printers.

11. Oracle: Adapt the database profiles init<SAPSID>.ora, init<SAPSID>.dba and

init<SAPSID>.sap.


6.1 Performing Follow-Up Activities in the Source System

2010-03-16 PUBLIC 89/126

Actions at Database Level

1. Before starting the SAP system, make sure that the logging mechanism of the database is active.

2. Check the parameters in the database profiles.

3. Oracle: Delete all entries from the following tables:

DBSTATHORA, DBSTAIHORA, DBSTATIORA, DBSTATTORA.

4. Oracle: Delete the user OPS$<SOURCE_SAPSID>ADM.

5. Oracle: If you changed the <DBSID> during the system copy, we recommend that you adapt the

global_name parameter with the following SQL command:

alter database rename global_name to <NEW_DBSID>;

If the parameter does not exist on your system, ignore this step.

Actions at SAP System Level

1. Run an installation check: Administration System administration Administration Installation Check

(transaction SM28).

2. Configure the Transport Management System (transaction STMS). If you did not change the SAPSID

during the system copy, all open transport, repair and customizing requests that have not been

released in the source system, will not be released automatically.

3. Adapt the transport parameters and transport routes in the Transport Management System (TMS):

a.

1. Choose transaction STMS Overview Systems .

2. Select the system and select the tab Transporttool.

To adapt the transport routes:

Choose transaction STMS Overview Transport routes .

4. Delete all entries from the following tables: ALCONSEG, ALSYSTEMS, DBSNP, MONI, OSMON, PAHI,

SDBAD, SDBAH, SDBAP, SDBAR.

5. Delete canceled and finished jobs.

Execute ABAP program RSBTCDEL, marking the field delete with forced mode: Tools ABAP Workbench

ABAP Editor (transaction SE38).

6. Adapt all jobs needed in the target system:

1. Copy the old jobs.

2. Modify the new jobs.

3. Delete the old jobs.

7. Check the consistency of the Temporary Sequential Objects (TemSe) by searching for files of TemSe

objects for which no TemSe objects exist:

Administration CCMS Spool TemSe administration (transaction SP12). For more information,

see SAP Note 16875.

8. Adapt the definition of the printers to meet the new system requirements:

■ Device types and character set definitions



90/126 PUBLIC 2010-03-16


■ Spool servers

■ Output management systems (OMS)

9. Delete entries in table DDLOG for buffer synchronization.

10. Synchronize the buffers as described in SAP Note 36283 and adapt the client information for the

logical system.

11. Adapt the RFC destination: Tools Administration Administration Network RFC destinations

(transaction SM59).

12. If you have performed a system copy with R3load, you must set up the trusted and trusting RFC

relationships again.

13. Clean the transactional RFC: Tools Administration Monitor Transactional RFC (transaction

SM58). For more information, see the relevant description in the SAP Online Documentation.

14. Start transaction SECSTORE using Check Entries. If you find erroneous entries with message text System-

dependent data for entry … changed , see SAP Note 816861.

15. Create new operation modes and remove old ones:

1. Create new operation modes and instance definitions.

2. Maintain the timetable using the new operation modes.

3. Delete the old operation modes and old instance definitions.

16. Adapt the operation mode time tables (CCMS): Administration CCMS Configuration Operation

mode calendar (transaction SM63).

17. Adapt the instances and profiles (CCMS): Administration CCMS Configuration OP modes/

instances (transaction RZ04).

18. Define or remove the SAP system users: Tools Administration User maintenance Users

(transaction SU01). Also revise the authorizations of the system users.

19. Run transaction SE14 to delete all entries from tables TPFET and TPFHT. These contain information

about changes made to the profile of your source system.

IBM DB2 for i5/OS: Use the commands CLRPFM R3<SID>DATA/TPFET and CLRPFM R3<SID>DATA/

TPFHT.

20. Adapt other CCMS settings (for example, alert thresholds, reorganization parameters of CCMS

table MONI) if required.

21. Delete all entries from table TLOCK, which holds the repair requests from your source system.

22. Make data archived in the source system (data that does not reside in the database but was moved

to a different storage location using SAP Archive Management) accessible in the target system.

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

Online Documentation (SAP Web Application Server System Administration Application Data Archiving and

Reorganization) .

23. Redefine database actions (backup, update statistics, and so on) if you have used the DBA calendar

in the source system (transaction DB13).

24. Check logon groups and assignment of application servers to logon groups (transaction SMLG).



2010-03-16 PUBLIC 91/126



25. Check the connection to SAPNet - R/3 Frontend (transaction OSS1).

26. Check self-defined external commands (transaction SM69).

27. Check entries of the following tables in all relevant systems:

■ TXCOM (transaction SM54)

■ THOST (transaction SM55)

28. Check the logical system names. For more information, see Preparations [page 17]. If you need to

change logical system names in the system that results from the copy, change the logical system

names at this time as described in SAP Notes 103228 and 544509. Follow your corporate naming

strategy for logical systems when making this change.

BI customers: If you have copied a BI (formerly BW) system, read SAP Note 325525.

29. For every client in your SAP system check the detail settings (client role, changes and transports

for client-dependent objects, changes for client-independent objects, protection level, restrictions)

(transaction SCC4).

30. Check if you can delete clients that will no longer be used in the target system (transaction

SCC5).

31. Check the contexts and segments of remote application servers for the SAP Monitoring

Infrastructure if required (transaction RZ21).

32. Configure the domain controller in the Transport Management System (TMS) by using

transaction STMS.

33. Post-processing for customer objects:

If customer objects are not original in the new system, modify the corresponding entries in table

TADIR.

If you encounter problems modifying a customer development class using transaction SMTS or

SM31, try to use the option Validate (ENTER) instead of the option Save to save your changes.

34. ABAP Program Loads

The ABAP loads are platform-dependent programs that are generated during runtime and stored

in database tables. They are not exported when you use the R3load procedure to copy your SAP

system. The ABAP loads are generated in the target system when they are first used. This might,

however, reduce production system performance. To avoid this, you can use transaction SGEN to

generate the missing loads.

Load generation requires a large amount of system resources. Therefore, it makes sense to schedule

the generation job to run overnight.

For a detailed description of the features, see the online documentation in transaction SGEN by

choosing Information on the SAP Load Generator, or in the Job Monitor by choosing Job Monitor.

35. If you did not change the database when copying the system, you have to start program

RS_BW_POST_MIGRATION in the background with variant SAP&POSTMGR. Otherwise, if you

changed the database when copying the system, you have to start program

RS_BW_POST_MIGRATION in the background with variant SAP&POSTMGRDB Program



92/126 PUBLIC 2010-03-16




RS_BW_POST_MIGRATION performs necessary modifications on database-specific objects (mainly BI

objects).

Checking the Target System

The following actions are suitable for checking the consistency of the target system:

1. Perform initial consistency check (transaction SM28).

2. Check the system log on all application servers (transaction SM21).

3. Check the consistency of the database (transaction DB02).

4. Perform server check (transaction SM51).

5. Test transactions frequently used by the customer.

6. FI customers: Run the job SAPF190 (accounting reconciliation) and compare the results to those

gained on the source system before the system copy ( Accounting Financial Accounting General ledger

Periodic Processing Closing Check/count Comparison ).

7. FI customers: Run the jobs RFUMSV00 (tax on sales/purchases), RAGITT01 (asset history sheet),

RAZUGA01 (asset acquisitions), RAABGA01 (fixed asset retirements) and compare the results to those

gained on the source system before the system copy.

8. CO customers: Run the report group 1SIP and compare the results to those gained on the source

system before the system copy.

Replacing the PSEs in the Target System

Replace all existing PSEs in the target systems with new ones, which contain the new system's

information. Proceed as follows:

1. In your ABAP system, call transaction STRUST.

2. Proceed as described in the documentation Creating or Replacing a PSE in the SAP Library at http://

help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by

Key Capability Security System Security System Security for SAP NetWeaver AS ABAP only Trust

Manager .

NOTE

■ Since replacing a PSE will remove all of the previously used certificates, also import all

necessary trusted certificates into the new PSE's certificate list. (Check the old PSE's

certificate list.) Also distribute the new PSE's public-key certificate to the systems where

it will be used.

■ Make sure the new PSE contains the new system ID.

■ Note the naming conventions to use for each PSE. The naming conventions are usually

specified by the Certification Authority (CA) where you obtain the certificate, however,

the type of PSE also has some restrictions, for example, for the SSL server PSE, the CN

part of the Distinguished Name must be the host name used to access the server. For the

system PSE, we recommend using the SID as the CN part.



2010-03-16 PUBLIC 93/126



Therefore, make sure that the Distinguished Name used for the PSE conforms with the

naming convention that applies.

6.2.2 Performing Jobhead Correction after Homogeneous System Copy

NOTE

This section is only relevant for customers using CCMS to monitor their SAP system(s).

After copying your system, the CCMS jobhead still points to the former database SSID. In order to

complete the homogeneous system copy, the SSID needs to be set to the target system.

CAUTION

Only experienced users should use this utility.

Only valid for: SAP NetWeaver 7.0 |

Prerequisites

You must have SAP NetWeaver 7.0 SP 12 or above to use this function.End of: SAP NetWeaver 7.0 |

Procedure

To set the SSID to the target system:

Only valid for: SAP NetWeaver 7.0;SAP NetWeaver 7.1 |

1. Call transaction DBACOCKPIT.

2. Choose Configuration Homogeneous System Copy: Jobhead Correction

3. Modify the necessary data.End of: SAP NetWeaver 7.0;SAP NetWeaver 7.1 |

Only valid for: SAP Web AS 6.40 |

1. Call transaction DB2.

2. Choose Checks/Settings Correct Jobheads

3. Modify the necessary data.End of: SAP Web AS 6.40 |



94/126 PUBLIC 2010-03-16

7 Additional Information

7.1 R3load Procedures Using the Migration Monitor

Purpose

The Migration Monitor is a tool that helps you to perform and control the unload and load process

during the system copy procedure. The Migration Monitor is integrated into the SAPinst system copy

tool, but you can also use the monitor for copying older releases by starting it manually.

The Migration Monitor will

■ create R3load command files

■ create R3load task files if required

■ start the R3load processes to unload the data

■ transfer packages from the source to the target host if required

■ start the R3load processes to load the data as soon as a package is available

■ inform the person performing the system copy in case of errors

The Migration Monitor has to be started on the source database host (Export Monitor) and on the

target database host (Import Monitor).

CAUTION

If you want to convert a non-Unicode system to Unicode using the Socket option, you need an

R3load version with at least patch level 73 (compile date: 12.01.2008).

Prerequisites

■ JRE version 1.5 or higher

■ The JAVA_HOME environment variable must point to the JRE directory.

■ The correct directory structure for R3load dump files must exist on both the source and target

hosts.

7.1.1 Configuration

Help

The tool will display the available parameters, if you call it with one of the following options:

■ -help

■ -?



2010-03-16 PUBLIC 95/126

Version

The tool will display the version information (release branch and build date), if you call it with the

following option:

■ -version

General Options

Name Description Comments

monitorTimeout Monitor timeout in seconds During a timeout, the monitor thread sleeps and does not analyze any files or analyze its processing state. The default timeout value is 30 seconds.

E-Mail Options


mailServer SMTP server Server name or IP address of the company SMTP server

mailFrom “From” e-mail address

mailTo “To” e-mail address Can contain an address list separated by ‘;’ or blanks.

Trace Option


trace Trace level Possible values:all, off,

1 (error), 2 (warning), 3 (info), 4 (config, default), 5,6,7 (trace)

Export Options

Option Description Comments

installDir Installation directory The installation start directory is the directory in which the installation tools (SAPinst, R3SETUP) write their log files. When the Migration Monitor is used without the installation tools, the installation start directory is the directory, where the R3load TSK and log files will be created.

exportDirs List of export directories Separator on Windows: ‘;’ Separator on UNIX: ‘:’ The ‘exportDirs’ parameter points to the directory where the R3load dump files will be written to. In the ‘exportDirs’ directory, the subdirectories DATA, DB and DB/<TARGET_DBTYPE>(for example, DB/ORA) have to exist.



96/126 PUBLIC 2010-03-16


client Client operating mode Running in client mode means, the Monitor will run parallel with standard SAPinst export process and transfer the exported dump files onto the import server.

server Server operating mode Running in server mode means, the Monitor will create R3load TSK files (if necessary). R3load cmd files and start the R3load processes.

All options below are for the server mode. The Import Monitor always runs in the server mode. If you want to run the Export Monitor in the server mode, specify the parameter ‘server’ in the Export Monitors properties file.

orderBy Package order Can be the ‘name’ or path of the file that contains package names. If the option value is omitted then package order is not determined.

r3loadExe Path of the R3load executable Optional; the default is R3load. If only the name of the R3load executable is available, then JVM looks for the R3load executable using OS-specific process search rules.

tskFiles 'yes' to create task files; 'no' to skip Before version 4.6 must be set to ‘no’; starting from version 4.7 ‘yes’. If the R3load task files ‘*.TSK’ already exist then the monitor will not overwrite them.

dataCodepage Code page for data files See SAP Note 552464. Possible values: 4102, 4103, 1100

taskArgs Additional R3load arguments for the TASK phase

Appended to the R3load command line. Options already set by the monitor: -ctf; -l; -o (if the omit argument is specified).

loadArgs Additional R3load arguments for the LOAD phase

Appended to the R3load command line. Options already set by the monitor: -e; -datacodepage; -l; -p; -r; -socket (if the socket option is specified); -o (if the omit argument is specified and task files are not used, that is, the value of the ‘tskFiles’ option is ‘no’).

expJobNum Number of parallel export jobs, the default is 1.

Any positive number; 0 for an unlimited number of jobs.

Network Exchange Options


net Network operating mode Exported dump files must be visible on the import host to use this mode.



2010-03-16 PUBLIC 97/126



netExchangeDir Network exchange directory Used for communication between the export and Import Monitors. Must be writable for Export Monitor and readable for Import Monitor. The Export Monitor will write a file <package>.SGN to the network exchange directory as a signal for the Import Monitor that the package is exported successfully and the import could be started.

FTP Exchange Options


ftp FTP operating mode Exported dump files will be transferred automatically from the source host (directory ‘exportDirs’) to the target host (directory ‘importDirs’) using FTP.

ftpHost Remote FTP host Name or IP address of the import server.

ftpUser Name of the remote FTP user The FTP user specified here should be the <sapsid>adm to make sure that the package files can be read by during the import (which is started as <sapsid>adm).

ftpPassword Password of the remote FTP user CAUTION

Security risk!

ftpExportDirs List of remote FTP directories for export dump

Both ‘;’ or ‘:’ separators are valid. This is the directory on the target host to which the dump will be transferred. The value will be the same as for ‘importDirs’ in the Import Monitors property file.

ftpExchangeDir Remote FTP exchange directory Used for communication between the export and Import Monitors. Must be writable for the Export Monitor and readable for the Import Monitor. The Export Monitor will write a file <package>.SGN to the FTP exchange directory as a signal for the Import Monitor that the package is exported successfully and the import could be started.

ftpJobNum Number of parallel FTP jobs; the default is 1.

Any positive number; 0 for an unlimited number of jobs.



98/126 PUBLIC 2010-03-16

Export Socket Host

Option Description Comment

socket Socket operating mode R3load will not write dump files to the file system but the export and import work through the socket connection.

host Remote import host Name or IP address of the import host.

port Host port number Must be the same as the port number on the import host. Any free port on the import host from 1024 to 65535.

FTP Copy Options

Option Description Command

ftpCopy FTP copy operating mode Used as a separate program call for migration with sockets. All files produced by R3lctl and R3szchk will be transferred from the source to the target host using FTP.

exportDirs List of export directories Separator on Windows: ‘;’ Separator on UNIX: ‘:’ In the ‘exportDirs’ directory, the subdirectories DATA, DB and DB/<TARGET_DBTYPE> (e.g. DB/ORA) have to exist. The R3load STR files have to exist in the subdirectory DATA, the DDL*.TPL files in the subdirectory DB, and the R3load EXT files (if required) in the subdirectory DB/<TARGET_DBTYPE>.

ftpHost Remote FTP host Name or IP address of the import server.

ftpUser Name of the remote FTP user The FTP user specified here should be the <sapsid>adm to make sure that the package files can be read by during the import (which is started as <sapsid>adm).

ftpPassword Password of the remote FTP user CAUTION: Security risk

ftpExportDirs List of remote FTP directories for export dump

Both ‘;’ or ‘:’ separators are valid. This is the directory on the target host to which the dump will be transferred. The value will be the same as for ‘importDirs’ in the Import Monitors property file.

Any other option is ignored by Import Monitor.



2010-03-16 PUBLIC 99/126

Mandatory Options for Export Monitor

■ Client mode:

installDir, exportDirs,

one of the options ftp, net (and their related parameters)

■ Server mode:

installDir, exportDirs, tskFiles,

one of the options ftp, net, socket (and their related parameters)

■ FTP copy:

exportDirs, ftpHost, ftpUser, ftpExportDirs, ftpExchangeDir

NOTE

The value of the dbType option is determined automatically in the shell script/batch files from

the dbms_type environment variable.

Import Options


installDir Installation directory The installation start directory is the directory in which the installation tools (SAPinst, R3SETUP) write their log files. When the Migration Monitor is used without the installation tools, the installation start directory is the directory, where the R3load TSK and log files will be created.

importDirs List of import directories Separator on Windows: ‘;’ Separator on UNIX: ‘:’ The ‘importDirs’ parameter points to the directory where the R3load dump files will be written to. In the ‘importDirs’ directory, the subdirectories DATA, DB and DB/<TARGET_DBTYPE> (for example, DB/ORA) have to exist.

orderBy Package order This option is used only if the Import Monitor works without the Export Monitor in stand-alone mode, that is, all export dump files are available on the import host before the Import Monitor is started. Values can be:name: load packages in alphabetical order,size: load packages starting with the largest one, or a path of the file that contains package names.If the option is omitted then package order is not defined.

r3loadExe Path of the R3load executable

Optional; the default is R3load. If only the name of the R3load executable is available then JVM looks for the R3load executable using OS-specific process search rules.

tskFiles ‘yes’ to create task files; ‘no’ to skip

Before version 4.6 must be set to ‘no’; starting from version 4.7 ‘yes’. If the R3load task files ‘*.TSK’ already exist then the monitor will not overwrite them.



100/126 PUBLIC 2010-03-16


extFiles ‘yes’ to include EXT files; ‘no’ to skip them

Add EXT file entries to cmd files; If the EXT files cannot be found in DB/<TARGET_DBTYPE> import dump subdirectory the package processing is aborted.

dbCodepage Database code page for the target database

See SAP Note 552464. Possible values: 4102, 4103, 1100

migrationKey Migration key

omit R3load omit value Can contain only 'DTPIV' letters.-o D : omit data; do not load data-o T: omit tables; do not create tables-o P: omit primary keys; do not create primary keys-o I: omit indexes; do not create indexes-o V: omit views; do not create views If you want to combine several omit options, list these options without blank (for example, ‘-o TV’).

taskArgs Additional R3load arguments for the TASK phase

Appended to the R3load command line.Options already set by the monitor:-ctf; -l; -o (if the omit argument is specified).

loadArgs Additional R3load arguments for the LOAD phase

Appended to the R3load command line.Options already used by the monitor:-i; -dbcodepage; -l; -p; -k; -r; -socket (if the socket option is specified); -o (if the omit argument is specified and task files are not used, that is, the value of ‘tskFiles’ option is ‘no’).

impJobNum Number of parallel import jobs; the default is 1.

Any positive number; 0 for an unlimited number of jobs

Import Exchange Options


exchangeDir Exchange directory If this option is not set, then the monitor runs in stand-alone mode, that is without the Export Monitor. All the export dump files or the SAP export CDs from the installation kit must be available on the import host and be specified with the parameter ‘importDirs’ (for example, in the properties file). If there is an old file export_statistics.properties

(for example, from a previous export run), remove this file.

Import Socket Options

Option Description Command

socket Socket operating mode

port Server port number Any free port from 1024 to 65535.



2010-03-16 PUBLIC 101/126


Any other option is ignored by Import Monitor.

Mandatory Options for Import Monitor

■ Server mode (default):

installDir, importDirs, tskFiles, extFiles,

one of the options exchangeDir or socket (and their related parameters)

■ Stand-alone mode:

installDir, importDirs, tskFiles, extFiles

NOTE

The value of the dbType option is determined automatically in the shell script/batch files from

the dbms_type environment variable.

7.1.2 Assigning DDL Files to Packages

It is possible to use several different DDL*.TPL templates during the export respectively during the

import. The assignment of a specific DDL file to a single package is done within a simple text file, which

then has to be specified via the ddlMap option within the migration monitor's properties file. Packages

not listed in the DDL mapping file will use the default DDL control file.

Procedure

Example of a DDL mapping file:

# DDL mapping file ddl_mapping.txt

# !!! line with [GROUP_NAME] can be skipped

# used for documentation purposes only

[ SORTED UNLOAD ]

# DDL file for sorted unload

ddlFile = /export_dump/ABAP/DB/ORA/DDLORA.TPL

# package names

SAPAPPL0

SAPAPPL1

SAPSDIC

[ UNSORTED UNLOAD ]

DDL file for unsorted unload

ddlFile = ./DDLORA_LRG.TPL

# table names

TABLE_A

TABLE_B

TABLE_C



102/126 PUBLIC 2010-03-16

7.1.3 Defining Groups of Packages

The “package group” feature is an enhancement of defining a package order. By defining groups you

can prevent parallel execution of certain packages and you can define how many large tables are

exported or imported at the same time. In addition, you can specify different values for the parameter

jobNum and taskArgs / loadArgs per package. Package groups can be defined in the same text file in

which the package order can be defined (see parameter orderBy). The old package order format is also

fully supported.

If package groups are defined, the maximal number of parallel R3load jobs is the sum of jobNum of all

packages. All packages without package group will be assigned to a “default group” with the number

of jobs, which was defined in the migration monitor's properties file.

Procedure

Example of a package order file with group:

# custom package order

# package names

SAPAPPL0

SAPAPPL1

SAPAPPL2

# package group

[ SEQUENTIAL GROUP ]

jobNum = 1

# table names

TABLE_A

TABLE_B

TABLE_C

7.1.4 Processing Split Tables

If tables have been split during the export, it has to be ensured before the import starts that the table

exists and that the primary key and the indexes are created before/after (as defined in the DDL template)

the table data have been imported. These tasks will be synchronized by the migration monitor

automatically. WHR files are part of the package and have to be copied to DATA export subdirectory to

make sure that the same WHR file is used for the export and the import of the corresponding package.

The following database platforms to not support parallel data import:

■ IBM DB2 for Linux, UNIX, and Windows

■ MS SQL

You can ensure this by using the feature Defining Groups of Packages [page 103].



2010-03-16 PUBLIC 103/126

Procedure

Example: Target database does not support parallel data import

Use

During the export you have split the table MY_FIRST_TABLE into 3 packages and MY_SECOND_TABLE into

5 packages. Now you want to run a maximum of 10 R3load processes for parallel data import.

Procedure

Create the file inputFile.txt with the following content:

[ MY_FIRST_TABLE ]

jobNum = 1

MY_FIRST_TABLE-1

MY_FIRST_TABLE-2

MY_FIRST_TABLE-3

[ MY_SECOND_TABLE ]

jobNum = 1

MY_SECOND_TABLE-1

MY_SECOND_TABLE-2

MY_SECOND_TABLE-3

MY_SECOND_TABLE-4

MY_SECOND_TABLE-5

In this file, you can also define the processing order of packages or you can assign DDL files to packages.

The inputFile.txt file has to be specified as value for the Migration Monitor parameter orderBy.

For every group (MY_FIRST_TABLE and MY_SECOND_TABLE) a R3load job is started. The number of parallel

R3load jobs will be the total of the number of R3load jobs of each group plus the number of R3load

jobs defined for the default group (which is made up of all packages without an explicit group name),

defined by the parameter jobNum.

In this example the parameter jobNum in the import_monitor_cmd.properties file has to be set to 8 to

ensure that not more than 10 R3load processes will run in parallel.

Re-Starting the Import of a Split-table Package

If the import of a package fails, the rows. which belong to this package have to be deleted using the

WHERE condition assigned to this package before starting the data import again. The deletion with a

WHERE clause can be very time consuming so it is faster to delete all rows of the corresponding table

manually and reimport all packages instead.

Restart for all other database platforms:

1. Eliminate the reason for the failure of the import of the package(s).

2. Delete all rows of the table, for which the import one or more packages failed, manually.



104/126 PUBLIC 2010-03-16

3. Remove the TSK files of all packages, which import data into this table (<table name>-

<counter>__TPI.TSK). Do not remove the TSK files, which create the table or which create the

indexes for this table.

4. Adapt the file import_state.properties in the installation directory. Replace the status '+' of all

packages for the corresponding table, which had been imported successfully and have to be

reimported by '0' (see Restarting R3load Processes [page 45]).

5. Restart the import.

7.1.5 Starting the Migration Monitor

The tool can be started using one of the following:

■ Only valid for: UNIX |

The UNIX shell scripts

export_monitor.sh / import_monitor.sh /

export_monitor_secure.sh

End of: UNIX |

■ Only valid for: Windows |

The Windows batch files

export_monitor.bat / import_monitor.bat /

export_monitor_secure.bat

End of: Windows |

■ Only valid for: IBM i5/OS |

IBM i5/OS specific

1. Run the command call qp2term.

2. export_monitor.sh / import_monitor.sh

3. Set the JAVA_HOME environment as follows:

export JAVA_HOME=/QIBM/ProdData/Java400/jdk14

4. Check that the environment variable PASE_THREAD_ATTACH is set to 'Y':

WRKENVVAR PASE_THREAD_ATTACH='Y'

End of: IBM i5/OS |

You can specify options in the command line or in the export or import property files [page 95]. The names

of the property files are export_monitor_cmd.properties and import_monitor_cmd.properties.

Templates for these files are included in the application archive and must be located in the current

user's working directory.

Any options specified in the command line take precedence over the corresponding options in the

application property file. Options are case-sensitive; any options that are not recognized are ignored.

To specify an option:

■ in the command line,

enter -optionName optionValue



2010-03-16 PUBLIC 105/126

■ in the application property file,

insert the new line optionName=optionValue


Example of a command line for a UNIX terminal:End of: UNIX |


./export_monitor.sh –ftp

End of: UNIX |


./export_monitor.sh –ftpCopy

End of: UNIX |


./export_monitor.sh –socket –host <import server> –port 5000

End of: UNIX |


Example of a command line for Windows cmd.exe:End of: Windows |


export_monitor.bat –net

End of: Windows |


export_monitor.bat –socket

End of: Windows |

If FTP access is used and security is required, start the monitor using the secure version of the shell

script/batch file to prevent seeing FTP password in the command line parameter string / property file.


Example of a command line for a UNIX terminal:End of: UNIX |


./export_monitor_secure.sh –ftpPassword <password>

End of: UNIX |

Procedure

1. Start the monitor and close the shell window / command processor. The monitor process will run

in background.

2. Use monitor *.log and *.console.log files to check monitor processing state.

Example of an export_monitor_cmd.properties file with export options:

# Export Monitor options

# Operating mode: ftp | net

#net

ftp



106/126 PUBLIC 2010-03-16

#

# Common options

#

# List of export directories, separator on Windows ; on UNIX :

exportDirs=C:\TEMP\export_dump

# SAPinst start directory

installDir=C:\install\start

# Monitor timeout in seconds

monitorTimeout=30

#

# FTP options

#

# Remote FTP host

ftpHost=server

# Name of remote FTP user

ftpUser=sysadm

# Password of remote FTP user

ftpPassword=password

# List of remote FTP directories for export dump, separator : or ;

ftpExportDirs=/install_dir/export_dump

# Remote FTP exchange directory

ftpExchangeDir=/install_dir/exchange

# Number of parallel FTP jobs

ftpJobNum=3

#

# E-mail options

#

# SMTP server

mailServer=sap-ag.de

# "From" email address

[email protected]

# "To" email address

[email protected] [email protected]

Example of an import_monitor_cmd.properties file with import options:

# Import Monitor options



2010-03-16 PUBLIC 107/126

#

# Common options

#

# List of import directories, separator on Windows ; on UNIX :

importDirs=/install_dir/export_dump

# SAPinst start directory

installDir=/install_dir/start

# Exchange directory

exchangeDir=/install_dir/exchange

# Generation of task files: yes | no

tskFiles=yes

# Inclusion of extent files: yes | no

extFiles=yes

# Monitor timeout in seconds

monitorTimeout=30

#

# R3load options

#

# DB code page for the target database

dbCodepage=1100

# Migration key

migrationKey=

# Additional R3load arguments for TASK phase

taskArgs=

# Additional R3load arguments for LOAD phase

loadArgs=

# Number of parallel import jobs

impJobNum=3

#

# E-mail options

#

# SMTP server

mailServer=sap-ag.de

# "From" email address

[email protected]

# "To" email address

[email protected] [email protected]



108/126 PUBLIC 2010-03-16

What happens during export / import with the above listed property files during a system copy with source and target database Oracle:

■ On the export host, the following directories have to exist (see parameter exportDirs):

● c:\temp\export_dump\DATA

● c:\temp\export_dump\DB

● c:\temp\export_dump\DB\ORA

The directory c:\temp\export_dump\DATA has to contain the STR files generated by R3ldctl, the

directory c:\temp\export_dump\DB the files DDL<DBTYPE>.TPL generated by R3ldctl as well, the

directory c:\temp\export_dump\DB\ORA the EXT files generated by R3szchk.

■ The Export Monitor will write the R3load dump files and the TOC files to the directory c:\temp

\export_dump\DATA.

■ The R3load log files, cmd files and TSK files (if required) are located in the directory c:\install

\start (parameter: installDir). The export itself is not done by the Export Monitor, as the

monitor is started in client mode (parameter ‘server’ is not set).

■ As soon as a package has been exported successfully, the Export Monitor will transfer all files

belonging to that package (TOC, STR, EXT, 001, ...) to the target host (parameter: ftpHost) into

the corresponding subdirectories of the directory /install_dir/export_dump (parameter:

ftpExportDirs) as user <sapsid>adm (parameter: ftpUser) identified by password (parameter:

ftpPassword) to logon.

■ If the package files have been transferred completely to the server, the Export Monitor will write

a signal file <package>.SGN to the directory /install_dir/exchange (parameter:

ftpExchangeDir) to notify the Import Monitor that it could start the import of this package.

■ On the import host, the following directories have to exist (see parameter importDirs):

● /install_dir/export_dump/DATA

● /install_dir/export_dump/DB

● /install_dir/export_dump/DB/ORA

The directory /install_dir/export_dump/DATA has to contain the STR files generated by R3ldctl,

the directory /install_dir/export_dump/DB the files DDL<DBTYPE>.TPL generated by R3ldctl, too,

the directory /install_dir/export_dump/DB/ORA the EXT files generated by R3szchk.

■ The import monitor will start to import a package as soon as the file <package>.SGN is found in

the directory /install_dir/exchange (parameter: exchangeDir).

■ The R3load log files, cmd files and TSK files (if required) will be located in the directory /

install_dir/start (parameter: installDir).

■ The file DDLORA.TPL has to be copied to the directory /install_dir/start (parameter:

installDir) before you can start the Import Monitor.



2010-03-16 PUBLIC 109/126

7.1.6 Output Files

Export

■ export_monitor.log

■ export_state.properties

■ ExportMonitor.console.log

Import

■ import_monitor.log

■ import_state.properties

■ ImportMonitor.console.log

Both the export and import state files contain package state lines such as the following: SAPUSER=+

Format of lines is <PACKAGE>=<STATE>. Possible values for state are:

0 Package export/import not yet started.

? Package export/import in progress.

- Package export/import finished with errors.

+ Package export/import finished successfully.

If any ftp/net exchange options are used, then the export state file may contain a second <STATE>

column, which refers to the state of the package transfer.

Then the export state file contains package state lines such as the following: SAPUSER=++

Format of lines is <PACKAGE>=<STATE>. Possible values for state are:

0 Package export not yet started.

? Package export in progress.

- Package export finished with errors.

+0 Package export finished successfully; package transfer not yet started.

+? Package transfer in progress.

+- Package transfer finished with errors.

++ Package transfer finished successfully.

7.1.7 Installing the Target System Using the Migration Monitor

Prerequisites

Make sure there is enough free space in the target system for the database load. To find out the size of

the export and the sizes of the tablespaces or dbspaces that are created, look at the file DBSIZE.XML

located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE> (Windows) or <EXPDIR>/DB/

<DATABASE> (UNIX).



110/126 PUBLIC 2010-03-16

Procedure

1. If you want to start the installation of the target host using the migration monitor, make sure that

at least the dump directory with the following files is accessible on the target host and contain

correct data before you start SAPinst:

■ <dump dir>/LABEL.ASC

■ <dump dir>/DB/<DBTYPE>/DBSIZE.XML

■ <dump dir>/DB/DDLORA.TPL

If the dump directory is not shared on the target host, you can copy the files as soon as they have

been created on the source host with the (export) migration monitor's FTP Copy options from

the source system to the target system.

2. You start SAPinst as described in the installation documentation for your SAP component.

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

required parameters up to the screen ABAP System > Database. On this screen, choose Standard System

Copy/Migration (R3load-Based).

4. Select the option Use Migration Monitor.

NOTE

If you need more information about input parameters, position the cursor on the field of the

respective parameter and press F1.

5. When SAPinst displays the CD browser-window and asks for the Export Migration CD, enter the path

to the export directory <EXPDIR>.

6. Continue as described in the installation documentation for your SAP component until a dialog

box appears that states:

If the export has been started on the source system and the Export Monitor is

running, you can now start the data load by starting the Import Monitor.

7. Check that the prerequisites in the dialog box are fulfilled by your system. If so, you can start the

Migration Monitor.

8. Complete the installation as described in the installation documentation for your SAP solution.

CAUTION

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

with the table that was not imported successfully.

7.2 Using SAPinst GUI

The following table shows the most important functions that are available in SAPinst GUI:

SAPinst GUI Functions

Input Type Label Description

Function key F1 Displays detailed information about each input parameter.


7.2 Using SAPinst GUI

2010-03-16 PUBLIC 111/126

Input Type Label Description

Menu option File Log off Stops the SAPinst GUI, but SAPinst and the GUI server continue running.

NOTE

If for some reason you need to log off during the installation from the host where you control the installation with SAPinst GUI, the installation continues while you are logged off. You can later reconnect to the same SAPinst installation from the same or another host. For more information, see Starting SAPinst GUI Separately [page 116].

Menu option File View Log Displays the installation log (sapinst_dev.log)

Menu option File Exit Cancels the installation with the following options: ■ Stop

For more information, see the description of the message button below.

■ ContinueFor more information, see the description of the message button below.

Message button Retry Performs the installation step again (if an error has occurred).

Message button View Log Displays the installation log (sapinst_dev.log)

Message button Stop Stops the installation (SAPinst GUI, SAPinst and the GUI server) without further changing the installation files. You can continue the installation later from this point.

Message button Continue Continues with the option you have chosen before.

7.3 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:

■ An error occurred during the dialog or processing 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 about 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 Exit in the SAPinst menu.

The following table describes the options in the dialog box:

Option Definition

Retry SAPinst retries the installation from the point of failure without repeating any of the previous steps.This is possible because SAPinst records the installation progress in the keydb.xml file.We recommend that you view the entries in the log files, try to solve the problem and then choose Retry.If the same or a different error occurs again, SAPinst displays the same dialog box again.



112/126 PUBLIC 2010-03-16

Option Definition

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.


NOTE

You can also terminate SAPinst by choosing Ctrl + C . However, we do not recommend that

you use Ctrl + C , because this kills the process immediately.

End of: UNIX |

Procedure

This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to

continue an interrupted installation after an error situation.


Log on as a user who is a member of the local administrators group.End of: Windows |


Log on to your local UNIX host as user root.

CAUTION

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

or database.

End of: UNIX |


Insert the Installation Master DVD in your DVD drive.End of: Windows |

4. Only valid for: Unix |

Mount your Installation Master DVD.

NOTE

Mount the DVD locally. We do not recommend using Network File System (NFS).

End of: Unix |


Change to the required directory

<DVD drive>:\IM_WINDOWS_<platform>

Double-click sapinst.exeEnd of: Windows |

6. Only valid for: Unix |


cd <Installation_Master_DVD>/IM_<OS>



2010-03-16 PUBLIC 113/126

./sapinst

End of: Unix |


Check if a SAPinst GUI Java process is still running.

If a process is still running, look for javaw.exe under Processes in your Task Manager and kill it.

■ If you used the default installation directory (recommended):

cd <Mapped_Drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64

sapinst.exe

■ If you used an alternative installation directory:

cd <Mapped_Drive>:\<your installation directory>

<Mapped_Drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64\sapinst.exe

End of: IBM i5/OS |

8. From the tree structure in the Welcome screen, select the installation service that you want to

continue and choose Next.

NOTE

If there is only one component to install, the Welcome screen does not appear.

The What do you want to do? screen appears.

9. In the What do you want to do? screen, decide between the following alternatives and confirm with

OK.

Alternative Behavior

Run a new Installation SAPinst does not continue the interrupted installation. Instead, it moves the content of the old installation directory and all installation-specific files to the backup directory. Afterwards, you can no longer continue the old installation.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds> (for example, log_01_Oct_2003_13_47_56).

Continue old installation SAPinst continues the interrupted installation from the point of failure.

7.4 Performing a Remote Export Using SAPinst

Purpose

You can run the SAPinst GUI in standalone mode to perform a remote export.

This enables you to perform the export on another host (the remote host) while monitoring the export

with the SAPinst GUI on your local Windows or UNIX computer (the local host).

Prerequisites

■ Make sure that you have performed the preparation activities for your local host (SAPinst GUI

host) and your remote host as described in Prerequisites in Exporting the Source System Using SAPinst [page

30].



114/126 PUBLIC 2010-03-16

■ Both computers are in the same network and can ping each other.

To test this:

● Log on to your remote host and enter the command ping <local host>.

● Log on to the local host and enter the command ping <remote host>.

Process Flow

1. You start the SAPinst server on your remote host.

2. You start the SAPinst GUI on your local host.

3. You perform the installation using the SAPinst GUI.

For more information, see:

■ Starting SAPinst on the Remote Host [page 115]

■ Starting SAPinst GUI Separately [page 116]

7.4.1 Performing a Remote Installation with SAPinst (Optional)

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: SAP CRM;SAP SCM;SAP SRM | SAP CRM 5.2;SAP SCM 5.1;SAP SRM Server 6.0 |

You can run SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host.End of: SAP CRM;SAP SCM;SAP SRM | SAP CRM 5.2;SAP SCM 5.1;SAP SRM Server 6.0 |


CAUTION

If you install SAP instances on System i, “local host” in this section refers to the Windows

installation host, not the System i host.


Prerequisites

■ Both computers are in the same network and can “ping” each other.

To test this:

● Log on to your remote host and enter the command ping <local host>.

● Log on to the local host and enter the command ping <remote host>.

ProcedureOnly valid for: IBM i5/OS;Windows |

1. Log on to your remote host as a user who is a member of the local administrators group.

2. Insert the Installation Master DVD in the DVD drive on your remote host.

3. Open a command prompt and change to the required directory of the installation Master DVD.



2010-03-16 PUBLIC 115/126


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

<DVD drive:\>cd <DVD drive>:\IM_WINDOWS_<platform>

End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |

Only valid for: IBM DB2 for i5/OS (Linux/Windows) |

cd <mapped drives>:\IM_OS400_PPC64

End of: IBM DB2 for i5/OS (Linux/Windows) |

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

4. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 116].End of: IBM i5/OS;Windows |


1. Log on to your remote host as user root.

CAUTION


or database.

2. Mount the Installation Master DVD.

3. Enter the following commands:


./sapinst -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.

4. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 116].End of: UNIX |

Only valid for: IBM i5/OS;UNIX;Windows |

7.4.2 Starting SAPinst GUI Separately (Optional)

You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI separately

in the following cases:

■ You have logged off from SAPinst.



116/126 PUBLIC 2010-03-16

If you logged off during the installation and you later want to reconnect to the installation while

it is still running, you can start SAPinst GUI separately.

■ You want to perform a remote installation [page 115].

If you want to run SAPinst GUI on a different host from SAPinst and the GUI server, you have to

start SAPinst GUI separately.

Only valid for: SAP CRM;SAP SCM;SAP SRM | SAP CRM 5.2;SAP SCM 5.1;SAP SRM Server 6.0 |

You can run SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host.End of: SAP CRM;SAP SCM;SAP SRM | SAP CRM 5.2;SAP SCM 5.1;SAP SRM Server 6.0 |


CAUTION

If you install SAP instances on System i, “local host” in this section means the Windows installation

host, not the System i host.


Prerequisites

You have installed the Java Runtime Environment [page 19] on the host on which you want to start SAPinst

without SAPinst GUI.

Procedure

Starting SAPinst GUI on a Windows Platform

1. Log on as a member of the local administrators group.

2. Insert the SAP Installation Master DVD into your DVD drive.

3. Open a command prompt and change to the relevant directory:

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

<DVD drive>:\IM_WINDOWS_<platform>

End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |

Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |

cd <mapped drives>:\IM_OS400_PPC64

End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |

4. Start SAPinst GUI in one of the following ways:

■ If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following

command:

startinstgui.bat

SAPinst GUI uses the local host as default.

■ If SAPinst and the GUI server runs on a different host from SAPinst GUI (remote installation),

enter the following command:

startinstgui.bat -host <host_name>

<host_name> is the host name of the installation host.



2010-03-16 PUBLIC 117/126

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 the GUI server and

SAPinst. Since SAPinst and the GUI server are running on another host, SAPinst GUI

cannot connect and the SAP Installation GUI Connection dialog appears.

In this case, enter the name of the host on which SAPinst is running and choose Log

on.

The first 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.bat -h.

Starting SAPinst GUI on a UNIX Platform

1. Log on as user root.

CAUTION


or database.

2. Mount your installation DVD.

NOTE

Mount the DVD locally. We do not recommend that you use Network File System (NFS).

3. To change to the mount directory enter the following command:


4. Start the SAPinst GUI in one of the following ways:

■ If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following

command without additional parameters:

./startInstGui.sh

SAPinst GUI uses as default the local host.

■ If SAPinst and the GUI server run on a different host from 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 the GUI server and

SAPinst. Since SAPinst and GUI server are running on another host, SAPinst GUI

cannot connect and the SAP Installation GUI Connection dialog appears.

In this case, enter the name of host on which SAPinst is running and choose Log on.



118/126 PUBLIC 2010-03-16

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: IBM i5/OS;UNIX;Windows |



2010-03-16 PUBLIC 119/126

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

120/126 PUBLIC 2010-03-16

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

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 is a registered trademark of Oracle Corporation.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.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 in several other countries all over the world. 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.

2010-03-16 PUBLIC 121/126

Legal Software Terms

Terms for Included Open Source Software

This SAP software contains also the third party open source software products listed below. Note that for these third party products the following special terms and conditions shall apply.1. This software was developed using ANTLR.2. SAP License Agreement for STLport

SAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingDietmar-Hopp-Allee 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)1. Subject Matter of the Agreement

1. SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library (STLport) and its documentation without fee.

2. By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement.

3. The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions.

4. Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG

5. The Customer may distribute original or modified STLport sources, provided that: ■ The conditions indicated in the above permissions notice are met; ■ The following copyright notices are retained when present, and conditions provided in accompanying

permission notices are met:Copyright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company 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.

122/126 PUBLIC 2010-03-16

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications.

2. Support and MaintenanceSAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall be not included.All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract.

3. Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport is error-free, without material defects or suitable for a specific application under third-party rights. Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes.

4. Limited Liability1. Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this

(i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute.

2. If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances known to it at that point in time representing a typical transfer of the software.

3. In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a defect or lost profit.

4. SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5,000.

5. The Customer shall take adequate measures for the protection of data and programs, in particular by making backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing this obligation.

6. The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees or agents of SAP.

3. Adobe Document 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.

4. Only valid for: SAP ERP;SAP CRM |

Apache License, Version 2.01. Definitions:

■ "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

■ "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

■ "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

■ "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. ■ "Source" form shall mean the preferred form for making modifications, including but not limited to software

source code, documentation source, and configuration files.

2010-03-16 PUBLIC 123/126


■ "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

■ "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

■ "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

■ "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

■ "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright LicenseSubject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent LicenseSubject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. RedistributionYou may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:1. You must give any other recipients of the Work or Derivative Works a copy of this License; and2. You must cause any modified files to carry prominent notices stating that You changed the files; and3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,

trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works

124/126 PUBLIC 2010-03-16

as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of ContributionsUnless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. TrademarksThis License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of WarrantyUnless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of LiabilityIn no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional LiabilityWhile redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

End of: SAP ERP;SAP CRM |

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

2010-03-16 PUBLIC 125/126


SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2010 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.

Documents

systemcopy_70_sr3_abap