System Copy Guide System Copy for SAP Systems Based on SAP NetWeaver 7.

0 Including Enhancement Package 1 SR 1 ABAP
Target Audience ■ System administrators ■ Technology consultants

PUBLIC Document version: 1.8 – 2011-03-07

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document. You can find the latest version on SAP Service Marketplace http://service.sap.com/ instguides. The following table provides an overview on the most important document changes:
Version Date Description

1.8 1.7 1.6 1.5 1.4 1.3 1.2 1.1 1.0

2011-03-07 2011-02-22 2011-02-18 2010-01-25 2009-12-08 2009-09-10 2009-07-16 2009-06-15 2009-05-04

IBM i-specific updates IBM i-specific updates Updates in Preparation for Table Splitting, IBM DB2 for Linux, UNIX, and Windows-Specific Procedures, and in the table “Import Options” in Configuration (Migration Monitor) Update in Oracle-Specific Procedure Update in Database-Specific System Copy Update in Oracle-Specific Procedure Update in Development Infrastructure (DI) Updated version Initial Version

2/116

PUBLIC

2011-03-07

Table of Contents

Chapter 1

1.1 1.2 1.3 1.4 1.5 Chapter 2 Chapter 3 3.1 3.2 Chapter 4 4.1 4.2 4.3 4.4 4.5 4.5.1 4.5.2 4.5.2.1 4.5.2.2 4.5.2.3 4.5.2.4 4.5.3 4.6 4.6.1

Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 Including Enhancement Package 1 Support Package 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 5 6 6 6 7

Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 General Technical Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Installing the Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Database Independent System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Copy Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating DDL Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation for Table Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting the Source System Using SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . Running SAPinst on UNIX or Windows to Perform the Export . . . . . . . . . . . . Running SAPinst on IBM i to Perform the Export . . . . . . . . . . . . . . . . . . . . . . Preparing the Windows Host for the SAP System Installation . . . . . . . . . . . . . Preparing a Windows User Account and IBM i User Profile . . . . . . . . . . . . . . . Installing TMKSVR and Creating an Installation Share . . . . . . . . . . . . . . . . . . Starting SAPinst on IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting R3load Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 22 25 26 30 31 31 37 37 38 40 43 47 48 50

2011-03-07

PUBLIC

3/116

. . . . . . . . . . . . . . . . . . . . . . . Oracle-Specific Procedure .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the Database Files on the Target System with BR*Tools . . . . . . .7 7. . . . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Defining Groups of Packages . . . . . .3 5. . . . . . . . . .1 7. . . . . . . . . . 97 Using SAPinst GUI . 96 Installing the Target System Using the Migration Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . .1. .5 5. . . . . . . .1. . . . .4 5. . . . . . . . . . . .2. . . . . . . . . . . . . . Creating an Offline or Online Backup with BR*Tools . Generating the Control File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . 81 R3load Procedures Using the Migration Monitor . . . . . . . . . . . . . .1. . . .1. . . . . . . . . . . . . . . . . . Performing Jobhead Correction after Homogeneous System Copy . . . . . .1 5. . . . . . . IBM DB2 for z/OS Specific Procedure . . .1 5. . . 81 Assigning DDL Files to Packages . . . . . . . . . . . . . .2 5. . . . . . . . . . . . . . . . . . . . . . . . .3 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. UNIX. . . . . . . . . . . 81 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . .2 Database-Specific System Copy . . . . . . . . . . . . . . . . . . .5 7. . . . . . . .1. . . . . . . . . . . . .4.4 7. . . . . . . . .5 5. . . . . . . . . . . . . . . . . .6 Chapter 6 6.1 5. . 53 54 56 60 60 61 61 63 64 65 68 68 73 73 75 75 75 75 80 Additional Information . . . . . . . Performing Follow-Up Activities in the Target System . . . . . . . . . . . . . 98 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . .2 6. IBM DB2 for Linux. . . . . . . . . . .Chapter 5 5. . MS SQL Server-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . 105 4/116 PUBLIC 2011-03-07 . . . .3 7. . . . . . . . .2 5. . . . . . . Performing Follow-Up Activities in the Source System .2. Restoring Database Files on the Target System Manually . .4 7. . . . . . 90 Starting the Migration Monitor . . . . . 99 Performing a Remote Export Using SAPinst . . . . . . . . . . . . . . . . . . . . Creating a Backup . . . . . . .1. . . . 102 Performing a Remote Installation with SAPinst . . . SAP MaxDB-Specific Procedure . . . . . . . . . . . . . . . .3 7. . . . . . . . . . . . . Performing Follow-Up Activities for ABAP . . . . . . . . . . Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . IBM DB2 for i Procedure . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . .2 7. . 91 Output Files . . . . .1. . . . . . . . . . .2 5. . . . . . . . . . . . . . . . . . . . . . . . . .2 7. . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an Offline Backup Manually . . . 102 Starting the SAPinst GUI Separately . . . . 89 Processing Split Tables . . .1 7. . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 7. . . . . . . . . . . . . .1 6. . . . .2 Chapter 7 7. . . . .1 7. . . . . . . . . . . . . . . . . . . . .1 6. . . . . . .4 5. . and Windows-Specific Procedures . . . . . . . .

■ Database Copy Database-dependent part of the system copy. They are used in the same way as in the SAP system installation documentation.1 Terminology ■ Homogeneous System Copy During the system copy you use the same operating system and database platform as the original system.1 1. When you perform a system copy. ■ System Copy Duplication of an SAP system. you can copy ABAP systems. Heterogeneous system copy is a synonym for migration.0 Including Enhancement Package 1 Support Package 1 As of SAP NetWeaver 7. or both.0. 2011-03-07 PUBLIC 5/116 . SAPinst installs all the instances again. This document explains how to perform a system copy for SAP systems based on SAP NetWeaver 7.0 including Enhancement Package 1 Support Package 1 (SAP NetWeaver 7. ■ Heterogeneous System Copy During the system copy. you change either the operating system or the database system. using either database-specific methods or database-independent methods. ■ Placeholders Placeholders such as <SAPSID> are used in commands. You must replace them with the values valid for your site. Certain SAP parameters might change in a copy.0 EHP 1 SR 1). The terms source database and target database are also used in this description. 1. but it uses a copy of the source system database to set up the database.1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. ■ Source System and Target System The SAP system containing the original database is called the source system and the system to which the database copy is to be imported is called the target system. Their SAP system names are abbreviated to SOURCE_SAPSID and TARGET_SAPSID (IBM i: source_<SID> and target_<SID>). ABAP+Java systems and Java systems in one run.0 Including Enhancement Package 1 Support Package 1 Terminology 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.

the following holds: 6/116 PUBLIC 2011-03-07 . check the SAP OS/DB Migration Planning Guide that is available in the Media Library.4 Restrictions The target system installation consists of both the target database and target instance/application server installations.2 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.sap.com/irj/sdn/systemcopy.3 System Architecture 1. In addition to the information contained on this page.1 1.com/osdbmigration. For the scenarios below. and the ABAP Dictionary.0 Including Enhancement Package 1 Support Package 1 Online Information from SAP The following additional placeholders are used: Placeholder <SAPSID> <S_HOST> <T_HOST> <S_SAPSID> <T_SAPSID> <S_DBSID> <T_DBSID> Meaning How to find out <OS> <DB> <Technology> SAP system ID System name of the source host Command hostname System name of the target host Command hostname SAP system ID of the source system <SAPSID> of the original system SAP system ID of the target system <SAPSID> of the target system Database ID of the source system <DBSID> of the original system Database ID of the target system <DBSID> of the target system Operating system name within a path Database name within a path ABAP.2 Online Information from SAP More information about system copying is available online as follows: ■ SAP System Copy & Migration page at http://sdn. ■ SAP Note 82478 SAP System OS/DB Migration CAUTION Only perform a system copy if you have experience in copying systems and thorough knowledge of the operating system. create a customer message using the application area BC-INS-MIG. NOTE If you encounter problems during the system copy. ■ SAP OS/DB Migration page at http://service. Java. 1. Only perform a heterogeneous system copy if you are a certified system support consultant or a certified SAP Technical Consultant.sap. or ABAP+Java 1. the database.

Transporting production clients is not supported at all. You can either copy all archive files to file systems that are not shared between the source and the target system. ■ If you have made modifications in your development system and want to copy your quality assurance or production system onto the development system. Otherwise. If required. your SAP Solution Manager 4. see SAP Note 130906. For more information. Use the appropriate tools for database reorganization. install a Java Add-In to your existing ABAP system before you start the export.0 EHP 1 SR 1. access to the created archive files from the target system may not always be possible. as SAP does not support this installation option.0 Including Enhancement Package 1 Support Package 1 Constraints 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. see SAP Note 153433 and System Landscape Optimization at http://service. ■ For the development of Java applications. ■ SAP does not support all data archiving operations after a system copy. 2011-03-07 PUBLIC 7/116 . End of: SAP Solution Manager | ■ SAP does not support client transport as a system copy method. and you do not store archive files using ArchiveLink/CMS. see SAP Note 551344. If you used data archiving in the source or target system. ■ This documentation does not describe how to export and import a database with the installation tools for reorganization purposes. 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. This documentation does not describe how to copy data from non-SAP systems to SAP systems.com/slo.5 Constraints ■ Only valid for: SAP Solution Manager | As of Support Release 4. for read-only access to the previously archived data from the target system (no reloading).sap.5 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. You can use client transport for the initial setup of an SAP system infrastructure. or you arrange network access for appropriate archive file sharing. End of: IBM DB2 for Linux and UNIX and Windows | 1. 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.0 system must be a dual stack system if you want to perform a system copy. This documentation does not cover the client copy procedure.1 1. we strongly recommend that you follow the rules mentioned below. ■ If you want to convert a non-Unicode system to a Unicode system or perform the system copy of a Unicode system. ■ This documentation describes how to copy data from one SAP system to another SAP system based on SAP NetWeaver Application Server.

● Don't: ◆ Save any system and infrastructure-specific data in business objects. You must not change the system ID during system copy. ◆ Set up dependencies between Java and ABAP.com/slo or slo. all software units or usage types in the source system are copied to the target system.com. contact SAP SLO at http://service. ◆ Make sure that all communication runs through the database pool.consulting@sap. but arrange for file access and/or ArchiveLink/CMS connectivity. assuming that the target system did not exist before and the source system's operation is discontinued after the system copy. 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. you must use the Software Deployment Manager (SDM) to save the data.sap. hardware migration). Use a pointer to the central storage of such information. nor can you select usage types.0 Including Enhancement Package 1 Support Package 1 Constraints ● The system copy is done to replace a productive system with a new productive system (for example.1 1. ◆ Follow the Open SQL standard. In all other cases.5 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. ■ When you perform a system copy. If saving this data to the file system level is unavoidable. ■ Dos and Don'ts for system copy: ● Do: ◆ Save configuration data and runtime data in the Java database only. This means that none of the usage types in the target system can be excluded from the system copy. 8/116 PUBLIC 2011-03-07 .

and production system) without making a system copy as follows: ■ Install all SAP systems. customize it. Only valid for: Oracle | NOTE You cannot create standby systems with a system copy.2 Planning 2 Planning This section describes how to plan your system copy. you can also install a system. End of: Oracle | NOTE You should perform upgrades in a test system first. Required Documentation ■ Read the following SAP Note for up-to-date information: 2011-03-07 PUBLIC 9/116 . Customize the development system as described in the implementation documentation. this allows you to identify customerspecific problems that might result from modifications. ■ Transport the client-dependent and client-independent data to the quality assurance and production systems. NOTE You can set up the SAP system infrastructure (development. CAUTION Do not use NFS-mounted file systems because writing to NFS-mounted file systems might cause corrupted dumps. You can use the system copy for: ■ Setting up system landscapes (where the SAP systems have different SAPSIDs). ■ Creating systems for testing. demonstration. When copying a system that contains production data choose the right time for the copy. and standby. Depending on the purpose of the system. starting with the development system. This could be a month-end or year-end closing. quality assurance. training. if you do not follow this concept. However. even though this prevents you from including the system in a system group for transports. it might be advisable to use the same SAP system ID. and then perform a system copy.

0 Including Enhancement Package 1 Support Release 1 only describes the export of the source system in detail. Perform a test run of the system copy.0 EhP 1 SR 11 at: http://service. Required DVDs. You can find the full names of all media shipped with SAP NetWeaver 7.sap.com/ installNW70 Installation Installation – SAP NetWeaver Systems Media List – SAP NetWeaver 7.com/migrationkey. ■ For the installation of the target system. 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. 2. You can use the time taken by the test run to calculate the system downtime: 10/116 PUBLIC 2011-03-07 .0 including Enhancement Package 1 Support Release 1) ■ The documentation System Copy for SAP Systems Based on SAP NetWeaver 7.2 Planning SAP Note 1317500 (Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. Creating A System Copy Plan Create a plan to perform the system copy. you can upgrade them at different times.0 EhP 1 SR 1 in the appropriate Media List for SAP NetWeaver 7. ■ For a heterogeneous system copy.com/instguides . NOTE You can operate several SAP systems on a single host without encountering any problems. we recommend that you use a separate host for each system because an SAP system upgrade might depend on an OS upgrade.sap. Tools. ■ Check that you have the appropriate tool versions for your SAP kernel. CAUTION The source system must be in a consistent state before you can copy it. Installation guides are available at http://service.0 EHP 1 Support Release 1 . you need to get a migration key by generating it at http:// service. ■ Order the right version of the installation kit before starting the system copy.sap. Consider the downtime of the source system (for preparations and copying) when planning the system copy. you also need the installation guide for your SAP application. Exceptions are only allowed if they are described in an SAP Note. If the SAP systems are on separate hosts. Nevertheless. Make sure that the versions of the SAP system and the installation tools are the same on the target and source systems. 1.

■ If you do not want to replace your source system. For more information. try to perform a complete test run. see System Copy Procedure [page 22]. Calculating the system downtime is particularly important for very large databases (VLDB) or when tapes are being used. transport. Use one of the following: ● System copy procedure on Windows using R3load For more information. time for export. transferred to the target system. Define a schedule for the test migration and the final migration. The test run is also to determine the amount of export data. new hard disk configuration. This means that the entire database is exported from the source system. new machine type. Use this method if database-specific methods are either not available or not suitable. Choose the best data transfer method (for example. ● System copy procedure for a homogeneous system copy only For more information. ■ Decide which system copy procedure you want to use: ● The database-independent procedure using SAP tools. see Database-Independent System Copy [page 21]. see System Copy Procedure [page 22]. ■ If your target system will replace your source system. FTP or tape). We recommend that you only perform read/write actions on local file systems. and imported there. System downtime is approximately equal to the total test time (that is. new file system type).2 Planning 3. 2011-03-07 PUBLIC 11/116 . Miscellaneous ■ In the event of a major change in hardware configuration (for example. ● The database-specific procedure using tools provided by the database vendor Some database vendors offer specific tools for copying a database. These tools allow you to: ◆ Restore a backup of one database (source database) in another one (target database) (backup method) ◆ Unload the source database and load the data into the target database For more information. The source system is only down for the time of the export. consult your SAP-authorized hardware partner. These methods are not supported for all database systems. Refer to the following table to check which copy methods are available for your database system: Database OS Platform Available Methods SAP MaxDB UNIX SAP MaxDB Windows Use one of the following: ● System copy procedure on UNIX using R3load For more information. see Database-Specific System Copy [page 53]. and import). see SAP MaxDB-specific procedure [page 65]. a partial test run (export of the entire database or parts of it) can be sufficient to calculate the system downtime.

12/116 PUBLIC 2011-03-07 . see System Copy Procedure [page 22].PDF attachment to SAP Note 680746. see System Copy Procedure [page 22]. Use one of the following: ● System copy procedure on IBM i using R3load For more information. End of: UNIX | ● Only valid for: Windows | System copy procedure on Windows using R3load For more information. ● The backup method of IBM DB2 for Linux. see SAP Note 585277. Use one of the following: ● Only valid for: UNIX | System copy procedure on UNIX using R3load For more information. see SAP Note 778729.0 EHP 1. see System Copy Procedure [page 22]. and Windows Specific Procedures [page 68]. see IBM DB2 i Procedure [page 73]. see IBM DB2 for Linux. see the . End of: UNIX | ● R3load method with Export/Import Monitors For more information. UNIX. see Oracle-Specific Procedure [page 54]. Use one of the following: ● Only valid for: UNIX | System copy procedure on UNIX using R3load For more information. ◆ When R3ta is used to split tables. Use one of the following: ● System copy procedure using R3load For more information. For more information. and Windows is supported for SAP systems based on SAP NetWeaver 7. see Starting SAPinst on IBM i [page 43]. ● IBM i-specific procedure for a homogeneous system copy only For more information. ● Oracle-specific procedure for a homogeneous system copy only For more information. see SAP MaxDB-specific procedure [page 65]. see System Copy Procedure [page 22]. and Windows IBM DB2 for z/OS IBM System z ● System copy procedure for a homogeneous system copy only For more information. UNIX.2 Planning Database OS Platform Available Methods IBM DB2 for i IBM i IBM DB2 for UNIX or Windows Linux. End of: Windows | Oracle UNIX ● Additional Information: ◆ For more information about the IBM DB2 for z/OS specific procedure for a homogeneous system copy only. UNIX. DELETE with WHERE is not performed if import errors occur in the target system. For more information. For more information. see R3load Procedures Using the Migration Monitor [page 81].

For more information about ordering and installing the SAP license. ■ SAP license Once the installation is completed and the SAP system copy has been imported. see R3load Procedures Using the Migration Monitor [page 81]. see the SAP Library at: http://help. see R3load Procedures Using the Migration Monitor [page 81]. ■ Choosing an SAP system ID You can choose the new SAP system ID <TARGET_SAPSID> freely during a new installation. you must choose different SAP system IDs for different SAP systems.com/nw70 SAP NetWeaver 7.2 Planning Database OS Platform Available Methods Oracle Windows Use one of the following: ● Only valid for: Windows | System copy procedure on Windows using R3load For more information.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SAP Licenses . Use one of the following: ● Only valid for: Windows | System copy procedure on Windows using R3load For more information. you will require a new license key for the target system. ● Homogeneous system copy only: Oracle backup/restore method For more information. ● Homogeneous system copy only: Backup/Restore or Detach/Attach Method For more information.sap. CAUTION To meet the requirements of the Workbench Organizer. For more information about SAP license keys. see Oracle-Specific Procedure [page 54] and SAP Note 676468.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. The license key of the source system is not valid for this system. see http://service. see System Copy Procedure [page 22]. see System Copy Procedure [page 22].sap. For more information. End of: Windows | ● R3load method with Export/Import Monitors For more information. End of: Windows | MS SQL Server Windows ● R3load method with Export/Import Monitors For more information. see MS SQL Server-Specific Procedure [page 68] and SAP Notes 193816 and 151603. see the SAP Library at: 2011-03-07 PUBLIC 13/116 .

0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management Data Archiving .2 Planning SAP NetWeaver 7.com/nw70 NOTE Refer to the section on hardware and software requirements in the SAP system installation documentation to determine the system requirements. 14/116 PUBLIC 2011-03-07 . ■ 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 http://help.sap. Access to archive files is platform-independent.

you must update these again or delete them. Check whether this action was successful using transaction SE16 for table VBDATA. you must update these again or delete them from all clients.Overview and Administration (transaction SM37) You also need to do this for jobs that must run periodically (see SAP Note 16083). ■ Before you start the export on your source system. Find the canceled or open updates as follows: 1. user. 3. Choose all update requests. ■ Set all released jobs from Released to Scheduled: Tools CCMS Background Processing Jobs . The following describes important preparations.1 General Technical Preparations Procedure To make a consistent copy of the database. you can do this after the installation of the central instance. check that your JAVA_HOME environment points to a valid JDK version. Call transaction SM13. 2. This is not necessary when performing a test run. It might be necessary to replace the SAP kernel delivered with the kernel DVD of the installation kit and installed during the installation of the target system with a newer kernel patch level before starting the target system. ■ No canceled or pending update requests should be in the system. you must perform the following preparation steps: 3. If canceled or pending updates exist.3 3. You can find out whether canceled or pending updates exist by checking if table VBDATA contains any entries. you need to prepare the source system and perform some subsequent actions on the target system. Check this by choosing Tools Administration Monitor Update (transaction SM13). For more information about SAP system administration. refer to the SAP Online Documentation. If you have to replace the delivered SAP kernel. ■ Before you start a system copy. Select all jobs (include start after event) as follows: Job Released Scheduled 2011-03-07 PUBLIC 15/116 . If canceled or pending records exist. Delete the default values for the client. check the minimum kernel patch level required by the support package level of the source system. and time.1 Preparations General Technical Preparations 3 Preparations Before you start the system copy.

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. 3. ■ Before the export. If your system copy is used to replace hardware for the DB server. 2. ■ FI customers: You can perform an additional consistency check by running the job SAPF190 before copying the source system. ● ● RFUMSV00 (tax on sales/purchases) RAGITT01 (asset history sheet) 16/116 PUBLIC 2011-03-07 . 2. source system for the copy is the same as the copy target). Make sure that no customer data is changed in the meantime. delete QCM tables from your system as follows: 1. 4. as well as after copying the target system. If you plan to overwrite an existing system with a system copy (for example. If you are still planning your BI (formerly BW) system landscape. make sure you write down the logical system names of all clients in the system that will be overwritten (transaction SCC4). Mark the tables and delete them. migrate to a different database system or operating system (that is.1 Preparations General Technical Preparations ■ 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. see SAP Note 184447. If you create a new system with a system copy (that is. create an upgrade test system). Call transaction SE14.3 3. no changes to logical system names are required. and then compare the results. as well as after copying the target system. As the logical system names will be overwritten. make sure that the logical naming strategy for this new system is consistent with your existing logical system naming convention. You can do this as follows: Accounting Financial Accounting General ledger Periodic Processing Closing Check/count Comparison ■ FI customers: You can further check consistency by running the jobs listed below before copying the source system. Before deleting you must always check ● That the tables are consistent – no restart log or conversion procedure termination must be displayed ● That the data of the original table can be read ● That application programs that use the affected original table run correctly. table All QCM tables that can be deleted are displayed. CAUTION Make sure that no customer data is changed in the meantime. the source and target systems will both exist after the system copy). and then compare the results. 3. Choose Extras Invalid temp.

2 Installing the Java Runtime Environment Only valid for: IBM DB2 for i5/OS | You need to prepare your Windows system for SAPinst. Defer the migration until the incremental conversion has finished. Choose Assistant and proceed according to the online documentation. CAUTION Prerequisites for an export: Before performing an export. ● If the tables are in any other state. For more information. End of: IBM DB2 for i5/OS | 2011-03-07 PUBLIC 17/116 . see Installing the Java Runtime Environment [page 17]. you have to finish the incremental conversion. 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. This includes the installation of a Java Runtime Environment (JRE). To do so. run transaction ICNV. as well as after copying the target system. If there are any table entries in table TICNV. If you do not delete the contents of these tables.2 Preparations Installing the Java Runtime Environment ● RAZUGA01 (asset acquisitions) ● RAABGA01 (fixed asset retirements) ■ CO customers: You can perform an additional consistency check by running the report group 1SIP before copying the source system. ■ Prepare the system for SAPinst. and then compare the results. CAUTION Heterogeneous System Copy only: Before you start the export of your source system. an incremental conversion is in progress.3 3. The JRE is part of the JDK (Java Development Kit) and not part of the SAP shipment. you will encounter problems while importing the data to your target system because of non NULL capable fields in these tables. which is required for SAPinst on Windows. To test if an incremental conversion is in progress. make sure that the tables TATGPC and TATGPCA are empty. In this case. make sure that no incremental conversion is in progress. Make sure that no customer data is changed in the meantime. 2. 3. you have the following options: 1. 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 .

3 3. Choose Start PAM with navigation by category. Only valid for: SAP NetWeaver | On the right-hand panel.MS SQL Server. 18/116 PUBLIC 2011-03-07 . The JRE is part of the JDK (Java Development Kit) and not part of the SAP shipment. End of: UNIX. End of: SAP CRM.IBM DB2 for z/OS. the SAPinst executable is running on the Windows installation host. see Performing a Remote Installation with SAPinst [page 102].MaxDB. which is required for SAPinst.MS SQL Server.MaxDB.IBM DB2 for z/OS. If you want to perform a remote installation. End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | Only valid for: UNIX. The J2EE engine of the SAP system uses the IBM JDK as mentioned in the section Hardware and Software Requirements in the installation documentation. 3. This lets you perform the installation on a remote host.Oracle | You need to prepare your system for SAPinst.MS SQL Server.Windows | NOTE If required. End of: SAP NetWeaver | 4.Oracle | Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | NOTE Since IBM i has no graphical user interface.com/pam. Only valid for: SAP CRM. You need to install a valid JDK on Windows only for installation purposes.MaxDB. End of: IBM DB2 for i5/OS (Linux/Windows).SAP ERP.SAP SCM.SAP SRM | 5.sap.Windows | Procedure 1.2 Preparations Installing the Java Runtime Environment Only valid for: IBM DB2 for i5/OS (Linux/Windows).0 . choose SAP NetWeaver SAP EHP1 FOR SAP NETWEAVER 7.IBM DB2 for Linux and UNIX and Windows.IBM DB2 for Linux and UNIX and Windows.MaxDB.MS SQL Server. Go to http://service. This includes the installation of a Java Runtime Environment (JRE). choose SAP Application Components <your product> .IBM DB2 for Linux and UNIX and Windows.SAP ERP.SAP SRM | On the right-hand panel.Oracle | Only valid for: IBM DB2 for i5/OS | Check the JRE Windows versions that are released for SAP systems in the Product Availability Matrix (PAM): End of: IBM DB2 for i5/OS | 1.IBM DB2 for z/OS. controlling it with the SAPinst GUI from a local host.Oracle | Check the JRE versions that are released for SAP systems in the Product Availability Matrix (PAM): End of: IBM DB2 for i5/OS (Linux/Windows).IBM DB2 for Linux and UNIX and Windows. Only valid for: IBM DB2 for i5/OS (Linux/Windows). Choose tabstrip JSE Platforms.SAP SCM. 2.IBM DB2 for z/OS. you can perform a remote installation using a standalone SAPinst GUI on a separate Windows or UNIX host.

End of: IBM DB2 for i5/OS | Only valid for: IBM DB2 for i5/OS (Linux/Windows).MaxDB. SAPinst also checks JAVA_HOME.MS SQL Server. which is referenced near the beginning of SAP Note 723909.MS SQL Server. you need to download and install it. as follows: ■ If the JRE is not already installed.source=file:/dev/urandom. If SAPINST_JRE_HOME is not found.IBM DB2 for Linux and UNIX and Windows. see the relevant SAP Note for your Windows operating system. End of: UNIX | Linux | 2011-03-07 PUBLIC 19/116 . End of: IBM DB2 for i5/OS (Linux/Windows).3 3.Oracle | NOTE For more information about how to download it.2 Preparations Installing the Java Runtime Environment Only valid for: IBM DB2 for i5/OS (Linux/Windows). ■ If the JRE is already installed Check the installed version of the JRE by entering: java -version Only valid for: IBM DB2 for i5/OS | NOTE SAPinst checks on Windows environment variable SAPINST_JRE_HOME for a valid Java runtime environment.MS SQL Server.MaxDB.security and replace entry securerandom.IBM DB2 for Linux and UNIX and Windows. If SAPINST_JRE_HOME is not found.MaxDB.MaxDB. End of: IBM DB2 for i5/OS (Linux/Windows).Oracle | NOTE SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment.IBM DB2 for z/OS.MS SQL Server.IBM DB2 for z/OS. Make sure a valid JRE version is installed.IBM DB2 for Linux and UNIX and Windows. which is referenced near the beginning of SAP Note 723909.Oracle | Only valid for: IBM DB2 for i5/OS | NOTE For more information about how to download it. you have to perform the following: Edit the configuration file $JAVA_HOME/jre/lib/security/java.source=file:/dev/random with securerandom. see the relevant SAP Note for your operating system.IBM DB2 for z/OS. End of: IBM DB2 for i5/OS | 2.IBM DB2 for Linux and UNIX and Windows.Oracle | Only valid for: UNIX | Linux | NOTE If you use a Sun Java VM.IBM DB2 for z/OS. SAPinst also checks JAVA_HOME.

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

delete the database on the target system before the import according to the corresponding description in the Additional Information section of the installation documentation for your SAP component. ■ R3load only: Changes to database objects that cannot be maintained in the ABAP Dictionary (transaction SE14). The processing unit for 2011-03-07 PUBLIC 21/116 . all tables of the SAP system are grouped into packages. are lost after the system copy. SAPinst uses the R3load tool. for example) must have its own separate installation directory whenever you start SAPinst. Although. 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. The database must still be running. Splitting STR Files ■ During the standard system copy process. you can export and import your database in a databaseindependent format. Other objects are not exported by SAPinst. whereby all tables with the same data class belong to the same package. System Copy Tools ■ Every installation service (dialog instance installation. ■ R3load only: Indexes longer than 18 characters are not allowed on the database to be exported. If the database configuration of your database is stored in the file system. End of: IBM i5/OS | Constraints R3load and Jload Restrictions ■ SAPinst generates a database dump of all SAP objects that are defined in the ABAP Dictionary (R3load).4 Database Independent System Copy 4 Database Independent System Copy With the SAP installation tool SAPinst. NOTE Only valid for: IBM i5/OS | On IBM i the database tools only export into the integrated file system (IFS). the SAPinst for IBM i runs on Windows it is not possible to export into the file system on Windows. ■ If the target system already exists and you do not plan to perform an MCOD installation. we recommend that you back these configuration files up before deleting the database. ■ For a consistent database the SAP system must be shut down (excluding the database!). such as the distribution of tables over several tablespaces or dbspaces.

If you do not have EXT files. You can find the EXT files in your export dump directory.1 Database Independent System Copy System Copy Procedure one unload/load process is a package. creating packages with a similar processing time. 2. You can achieve this by splitting the default packages (one package per data class) into more smaller pieces. that is. ■ “Splitting of STR Files” is part of the “Advanced Export Parameters” and is disabled by default.1 System Copy Procedure This section describes the system copy procedure using R3load. For a detailed description of the options. resulting in varying unload/load runtimes. and which you use to install the target system. refer to the F1 help about the parameters prompted on the Split STR Files screen while running SAPinst to export the database. you must first create the EXT files for the target database system.4 4. subdirectory DB/<DBTYPE>. The packages usually differ in the number and size of contained tables. 4. for example DB/ORA. Perform the export on the central system host: 22/116 PUBLIC 2011-03-07 . you need to proceed as follows on the central system host: 1. Procedure Process Flow on the Source System (Export) When performing the export. ■ There are several ways to split packages. which contains the data of the exported system.sap. Enter the installation number of your source system when prompted. or IBM i. Using the splitting tool parameters selected by SAPinst is a good starting point if you select the splitting option and you have not performed any tests yet. Heterogeneous system copy: Generate the migration key at http://service. 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. refer to System Copy Procedure [page 22]. then you can only split by providing tables via input file. The overall runtime can be reduced by creating packages of the same size. The options can be used separately or – when using the new Java based splitting tool – together. Process Flow For UNIX. you create a MIGRATION EXPORT CD image.com/ migrationkey. CAUTION If you want to split STR files by the size based option. Windows.

To complete the system copy. Only valid for: UNIX. 8. Only valid for: IBM i5/OS | Prepare the Windows host for the SAP system installation. Prepare the system for table splitting (optional). 6. choose the installation service Database Instance Export. see Generating DDL Statements [page 25]. Only valid for: IBM i5/OS | Install TMKSVR and create an installation share. Only valid for: IBM i5/OS | Prepare a Windows user account and an IBM i user profile. In SAPinst. or IBM i to prepare the source system for parallel export or parallel import (optional). Windows. For more information. see Running SAPinst on UNIX or Windows to Perform the Export [page 31] or Running SAPinst on IBM i to Perform the Export [page 37]. In SAPinst. NOTE If R3load processes fail due to an error. For more information. see Installing TMKSVR and Creating an Installation Share [page 40]. see Preparation for Table Splitting [page 26]. choose the installation service Export Preparation. For more information. For more information. End of: UNIX. you set up the target system using SAPinst. For more information. see Setting Up the Target System Using SAPinst [page 48]. see Restarting R3load Processes [page 47]. solve the problem and perform a restart. For more information. For more information. End of: IBM i5/OS | 5. 2011-03-07 PUBLIC 23/116 . or IBM i to export the database instance and the central instance. 7. Generate DDL statements. Run SAPinst on UNIX. see Preparing the Windows Host for the SAP System Installation [page 37].Windows | Make sure that the QCM tables are deleted from your system. For more information. Run SAPinst on UNIX. see Preparing a Windows User Account and IBM i User Profile [page 38]. see General Technical Preparations [page 15]. End of: IBM i5/OS | 3. For more information.1 Database Independent System Copy System Copy Procedure 1. End of: IBM i5/OS | 4.4 4. Windows. see Running SAPinst on UNIX or Windows to Perform the Export [page 31] or Running SAPinst on IBM i to Perform the Export [page 37].Windows | 2. Result You have finished this part of the system copy. For more information.

Windows. see Setting Up the Target System Using SAPinst [page 48]. Enter the installation number of your source system when prompted 2.Windows | Make sure that the QCM tables are deleted from your system. Result You have finished this part of the system copy. 3. Windows. 5. see General Technical Preparations [page 15].sap. set up the target system using SAPinst. For more information.Windows | 2. choose the installation service Database Instance Export. Generate DDL statements. you must proceed as described in SAP Note 884452. NOTE If R3load processes fail due to an error. In SAPinst. or IBM i to export the database instance. 4. For more information.com/ migrationkey. Prepare the system for table splitting (optional). For more information. For more information. End of: UNIX. For more information. 24/116 PUBLIC 2011-03-07 . choose the installation service Export Preparation. Perform the export on the database instance host: 1. see Generating DDL statements [page 25]. solve the problem and perform a restart. Only valid for: UNIX. Heterogeneous system copy only: Generate the migration key at http://service. To complete the system copy.4 4. see Restarting R3load Processes [page 47]. you need to proceed as follows: 1. see Preparation for Table Splitting [page 26].1 Database Independent System Copy System Copy Procedure Distributed System or High-Availability System To perform the export for a distributed system or a high-availability-system. In SAPinst. CAUTION If your database instance is running on HP PA-Risc. For more information. see Running SAPinst on UNIX or Windows to Perform the Export [page 31] or Running SAPinst on IBM i to Perform the Export [page 37]. see Running SAPinst on UNIX or Windows to Perform the Export [page 31] or Running SAPist on IBM i to Perform the Export [page 37]. For more information. or IBM i to prepare the source system for parallel export/ import (optional). Run SAPinst on UNIX. Run SAPinst on UNIX.

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). You must perform this procedure before starting SAPinst. Depending on the database manufacturer. If required. Log on to the system as a system administrator in a productive client. you might need to select the database version. you need to generate DDL statements using the ABAP report SMIGR_CREATE_DDL. The DDL statements are generated and are written to the specified directory. Specify an empty working directory to which the files generated by the report are to be written. 5. Select the target database.2 Database Independent System Copy Generating DDL Statements Overview of Export Options Figure 1: 4. The value help supports you in selecting the database version. Call transaction SE38 and run the program SMIGR_CREATE_DDL. You should only enter a database version that is available in the value help. Execute the program. Procedure 1. 7. 6. 4. 3. you can restrict the generation of DDL statements to specific table types or individual tables. 2.4 4.2 Generating DDL Statements To migrate nonstandard database objects. 2011-03-07 PUBLIC 25/116 .

) ● Oracle For more information. see SAP Note 888210.4 4. this is not an error. the table is processed in. Instead of exporting/importing one table with one R3load process. only the processing of the package where the error occurred has to be repeated and not for the complete table.3 Database Independent System Copy Preparation for Table Splitting CAUTION If no database-specific objects exist in the database. If the export or import of a table aborts with an error. Each entity can be processed by different R3load processes. but created empty in the target system) 26/116 PUBLIC 2011-03-07 . Prerequisites ■ The export and import have to be performed with the migration monitor when the table splitting feature is used. As long as the report terminates with status successfully. no SQL files will be generated. The advantages of splitting the tables are: ■ Large tables are processed in smaller packages. For additional database-specific information.3 Preparation for Table Splitting The R3ta tool processes large tables. see the paragraph Creating a Temporary Index. Restrictions ■ Only tables that are described in the SAP dictionary can be split. Before starting the export. ■ For the following databases. 4. ■ The export and import of one table can be performed in parallel by starting several R3load processes to work on some packages in parallel. 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. 8. 10 entities. ■ The following tables cannot be split: ● DDNTF ● DDNTF_CONV_UC ● DDNTT ● DDNTT_CONV_UC ● DDLOG (is never copied. the generated SQL files have to be copied from the specified directory to the <instdir> directory of the export. for example.

If no *. 2. End of: Oracle | or column>. Create a new. CAUTION 6. 4. Define a new.* in the kernel directory. When doing a code page conversion (non-Unicode → Unicode. 8. empty installation directory.WHR files could be produced for some of these tables. Choose SAP NetWeaver System Copy Source System ABAP System <Database> <Unicode or NonUnicode> Table Splitting Preparation . Copy the *. For CAUTION 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.txt. 3. CAUTION 7.3 Database Independent System Copy Preparation for Table Splitting Procedure 1. If the *. and the db<dbtype>slib. make sure not to use a WHERE condition with the PAGENO column included.WHR files have been created for the missing tables. The specified path to the export directory must not contain blanks! Continue with Next. 2.txt to <export dump directory>/ABAP/DATA/whr. 2011-03-07 PUBLIC 27/116 . Only valid for: Oracle | Oracle PL/SQL splitter only: Use the form <table>%<nr of splits>.WHR files have been created for all tables that are to be split. 2.WHR files from <temporary dump directory>/ABAP/DATA to <export dump directory>/ABAP/DATA. Specify SAPSID. If required.<rowid more information about the Oracle PL/SQL splitter. Add the lines from <temporary dump directory>/ABAP/DATA/whr. create fewer packages for these tables: 1. the export directory.txt. The tables listed in this file have to appear in alphabetical order! Start SAPinst.4 4. R3ldctld. the file that contains the split information. empty export dump directory <temporary dump directory>. and the number of parallel R3ta jobs. 5. see SAP Note 1043380. Create a file that contains lines of the form <table>%<nr of splits> for all tables to be split. You can find a version of these files on the Installation Master DVD in the directory IM_<OS>/<DBTYPE>/{UC/ NUC}. repeat the table splitting . If the PAGENO column is included in the WHERE condition.either with different splitting parameters or by defining a suitable column for this table using the R3ta_hints. create the temporary index on the source system's tables to be split. Update the R3ta. merge these results with the results from the first Prepare Table Splitting run: 1. Check in the export directory <export dump directory>/ABAP/DATA if *. 4102 ↔ 4103). <sidadm> password.

make sure you select the Split predefined tables checkbox and add the R3ta_hints. With one line in the file R3ta_hints.txt with column hints for several tables is delivered with the Installation Master DVD.STR Description Contains the description of the temporary index. These specifications are used by R3ta to create the WHERE condition. see the paragraph Creating a Temporary Index. Using Hints With the file R3ta_hints. End of: IBM DB2 for z/OS | For each table to be split.txt. separated by a blank. 2. you can instruct R3ta to use specific columns of a table to create a WHERE condition. After the Table Splitting Preparation. This is the case when you use a DDLDB2. End of: Oracle | For more information. R3ta creates the following files to facilitate the creation of the temporary index: File <table>_IDX. 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. For more information. see Processing Split Tables. A file R3ta_hints. 28/116 PUBLIC 2011-03-07 . Afterwards.txt. If the target database platform does not support the parallel data import. the default index name is <table>~IMG.TPL file with no ORDER_BY_PKEY and the R3load does not overrule this setting. If you want to modify this file. End of: IBM DB2 for z/OS | Only valid for: IBM DB2 for z/OS | EXAMPLE 1.4 4. The file has to be located in the directory in which you start R3ta. Only create a temporary index if you want to perform an unsorted unload. Parallel data export of a table is supported by all database platforms but parallel data import is not.3 Database Independent System Copy Preparation for Table Splitting Only valid for: Oracle | This is not required if you perform a database export using the Oracle-specific method with the Oracle PL/SQL splitter. the migration monitor has to be configured so that the data import processes the packages sequentially. Use the DEFER YES parameter to create the index. use the REBUILD INDEX job to speed up the index creation process. The columns have to be part of the primary key of the table. you specify the table name followed by one or more column names. Which tables cannot be unloaded unsorted is described in SAP Note 954268.txt file in the Split STR Files dialog box. copy it from the directory <IM_OS>/COMMON/INSTALL to the installation directory and adapt it according to your requirements as soon as the Parameter Summary dialog appears.

the dbcodepage is 1100. Depending on your database platform.TSK <table>_IDX. End of: Oracle | 3.IBM DB2 for Linux and UNIX and Windows. Depending on your database platform.4 4. the dbcodepage is 4102 (big-endian) or 4103 (little-endian).log If your source system is a non-Unicode system. End of: IBM DB2 for i5/OS. Contains the task to drop the temporary index. 1. Only valid for: IBM DB2 for i5/OS. If your source system is a Unicode system.cmd –l <table>_IDX. and TSK files created by R3ta to create the index.TSK DRP_<table>_IDX. Call R3load as user <sapsid>adm with the following parameters: R3load –dbcodepage <source system’s dbcodepage> –i <table>_IDX. R3load command file for dropping the temporary index.TPL file.MS SQL Server | 2. it might be necessary to modify the create index statement in the DDL<DBTYPE>.IBM DB2 for z/OS.TPL and add the highlighted key words to the creind statement: creind: CREATE &unique& INDEX &ind name& ON &tab name& ( /{ &fld name& /-.3 File Database Independent System Copy Preparation for Table Splitting Description <table>_IDX.cmd DRP_<table>_IDX.MaxDB.IBM DB2 for Linux and UNIX and Windows.TPL file.cmd Contains the task to create the temporary index. Only valid for: Oracle | Make sure that you do not lock the table while creating the temporary index.IBM DB2 for z/OS. 2011-03-07 PUBLIC 29/116 . it might be necessary to modify the create index statement in the DDL<DBTYPE>. Edit the file DDLORA. /} ) TABLESPACE &tablespace& STORAGE (INITIAL &init& NEXT &next& MINEXTENTS &minext& MAXEXTENTS &maxext& PCTINCREASE &pctinc& ) NOLOGGING COMPUTE STATISTICS PARALLEL ONLINE. R3load command file for creating the temporary index. STR.MaxDB. You can use the R3load cmd.MS SQL Server | Make sure that you do not lock the table while creating the temporary index.

4 Database Independent System Copy Preparing the Export 4. so as to enable parallel export/ import. the Java DVD. NOTE For more information.EXT.SAR archive on the SAP Installation Master DVD. The following steps are performed: ■ Creating the export directory structure ■ Creating database structure files (*. have to be transferred to the target host. For this purpose you need to create certain files. ■ Copy the export dump directory manually to the target host. the complete export directory with its structure and the generated files. see the documentation Migration Monitor – User’s Guide in the MIGMON.XML) These export preparations are required. or other export files). 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. or another directory that contains installation information (such as the Installation Master DVD. For more information. SAPinst does not display the export directory and you cannot change it. ■ The export dump directory can be shared and thus made accessible on the target host. Procedure 1. In this case. SAPinst does not ask you to specify the export directory and automatically chooses one that you may not want to use. which are required for building up the target system. ■ Export and import processes should run in parallel during the system copy process. 2. In any case. As soon as the export preparations have finished successfully. 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. 30/116 PUBLIC 2011-03-07 .DBSIZE.STR) ■ Updating database statistics (…) ■ Size calculation for the target database (*. Run SAPinst to perform the Export Preparation service. see Running SAPinst on UNIX or Windows to Perform the Export [page 31].4 4.4 Preparing the Export You can prepare the source system for the export using R3load and Jload. make sure that the dump directory and its subdirectories and files are accessible for user <sapsid>adm of the target system. Otherwise. CAUTION Make sure that the dump directory is not under the installation directory.

and which is located directly below the Program Files directory. or SystemRoot). ■ SAPinst creates a subdirectory for each installation service.5. SAPinst GUI connects to the GUI server using a secure SSL connection and the GUI server connects to SAPinst.xxxx sometimes remain in the temporary directory. If no value is set for these variables. where it keeps its log files. see Performing a Remote Installation with SAPinst [page 102]. TMPDIR. or TMPDIR. Only valid for: UNIX | ■ SAPinst normally creates the installation directory sapinst_instdir directly below the temporary directory. SAPinst tries to create sapinst_instdir in the directory defined by the environment variable TEMP. If required. If SAPinst is not able to create sapinst_instdir directly below the Program Files directory. which is located below %ProgramFiles%\sapinst_instdir. Note the following about SAPinst: ■ When you start SAPinst. If required. For more information. Directories with the name sapinst_exe. ■ The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. This section describes a standard export where SAPinst. called <sapinst_instdir> \<installation_service>. These executables are deleted after SAPinst has stopped running. End of: UNIX | Only valid for: Windows | ■ SAPinst normally creates the installation directory sapinst_instdir.5 Database Independent System Copy Exporting the Source System Using SAPinst 4. These executables are deleted again after SAPinst has stopped running. you can terminate SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C . which both use Java.4 4. SAPinst uses /tmp as default installation directory. SAPinst includes a SAPinst GUI and a GUI server. 2011-03-07 PUBLIC 31/116 .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 GUI. SAPinst GUI and the GUI server are also started. TMP. where SAPinst GUI is running on a separate host from SAPinst and the GUI server. SAPinst finds the temporary directory by checking the value of the environment variables TEMP.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 31] ■ Running SAPinst on IBM i to Perform the Export [page 43] 4. TMP. You can safely delete them. ■ The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP.xxxxxx. and the GUI server are running on the same host. you can perform a remote system copy with SAPinst instead.

■ You need at least 60 MB of free space in the installation directory for each ABAP installation option. you can also find the SAPinst Self-Extractor log file dev_selfex. Otherwise. For more information. Only valid for: Windows | ■ If you want to terminate SAPinst and the SAPinst Self-Extractor. make sure that you create it locally. End of: Windows | CAUTION If SAPinst cannot find a temporary directory. you need 60-200 MB free space for the SAPinst executables. In addition. Otherwise. The database must still be running. ● Click the icon for the SAPinst output window located in the Windows tray and choose File Exit . the target system might be inconsistent. CAUTION If you would rather create an installation directory manually. do one of the following: ● Right-click the icon for the SAPinst output window located in the Windows tray and choose Exit. End of: Windows | ■ Make the Master Installation DVD available. End of: Windows | Prerequisites CAUTION Make sure that you shut down all SAP Application Servers before the export. you might experience problems when starting the SAP Java tools. and at least 130 MB of free space in the installation directory for each Java installation option. End of: UNIX | Only valid for: Windows | You are logged on to your host as a user with the required rights and privileges that authorize you to install the SAP system with the SAPinst tool. the installation terminates with the error FCO-00058. 32/116 PUBLIC 2011-03-07 .4 4. ■ Only valid for: UNIX | You are logged on to your host as user root. which might be useful if an error occurs. see Required User Authorization for the Installation in your installation guide.out.5 Database Independent System Copy Exporting the Source System Using SAPinst In the temporary directory.

TMP. below the temporary directory of your operating system. During the export some archives are written to the program subdirectories and SAPinst aborts if there is not enough space./sapinst SAPinst creates a directory called sapinst_instdir. End of: Windows | Only valid for: UNIX | ■ Before starting the export. make sure that you have at least the same amount of disk space available in /sapmnt/<SAPSID>/<InstanceName>/SDM/program as is used in /sapmnt/<SAPSID>/ <InstanceName>/SDM/root/origin. you can set one of the environment variables TEMP. ■ Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime Environment (JRE). which is the current working directory for your installation. see Using SAPinst GUI [page 98]. ■ Make sure that the DISPLAY environment variable is set to <host_name>:0.4 4. where <host_name> is the host where the SAPinst GUI is displayed. make sure that the PATH variable points to a JDK/JRE for AIX 64-bit.5 Database Independent System Copy Exporting the Source System Using SAPinst Only valid for: UNIX | If you cannot provide 200 MB free space in the temporary directory. During the export. Interrupted Installation with SAPinst [page 99]. and Performing a Remote Export Using SAPinst [page 102]. Procedure 1.0. some archives are written to the program subdirectories and SAPinst aborts if there is not enough space. 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. ■ Only valid for: AIX | If the operating system is AIX 64-bit. End of: AIX | End of: UNIX | For more information about SAPinst. Start SAPinst from the SAP Installation Master DVD as follows: Only valid for: UNIX | Choose one of the following ways: ■ Using the default installation directory (recommended) Enter the following commands: cd <Installation_Master_DVD>/IM_<OS> . 2011-03-07 PUBLIC 33/116 . 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.

However. if there is only one component to install. you must execute SAPinst using the following parameters: SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui> ■ To get a list of all available SAPinst properties. The GUI server uses port 21212 to communicate with SAPinst GUI. and SAPinst GUI. TMP. for example. End of: UNIX | Only valid for: Windows | ■ Double-click sapinst. GUI server. You get an error message if one of these ports is already in use by another service.exe from the following path: <DVD_drive>:\IM_WINDOWS_<platform> SAPinst GUI normally starts automatically by displaying the Welcome screen./sapinst —p. SAPinst directly displays the first input dialog without presenting the Welcome screen. or TMPDIR. set the environment variable TEMP. the following causes an error: $ cd /sapcd2/IM_HPUX_IA64 $ /sapcd2/IM_HPUX_PARISC/sapinst To correct this. by using a crontab entry. start SAPinst as described above with the option –p: . or TMPDIR point. ■ During the installation. TMP.5 Database Independent System Copy Exporting the Source System Using SAPinst CAUTION Make sure that your current working directory is not an IM_<OS> directory belonging to another operating system. End of: UNIX | Only valid for: UNIX | NOTE ■ If you use virtual host names for the primary application server or the database instance or both (for example. start the export with the property SAPINST_USE_HOSTNAME=<virtual host>. 34/116 PUBLIC 2011-03-07 . ■ Using an alternative installation directory If you want to use an alternative installation directory. the default ports 21200 and 21212 are used for communication between SAPinst. For example. In this case. SAPinst uses port 21200 to communicate with the GUI server. in a high availability environment).4 4. enter the following: $ cd /sapcd2/IM_HPUX_PARISC $ /sapcd2/IM_HPUX_PARISC/sapinst CAUTION Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variables TEMP.

DBSIZE.XML) 2011-03-07 PUBLIC 35/116 . start the export with the property SAPINST_USE_HOSTNAME=<virtual host>. You get an error message if one of these ports is already in use by another service. after you have started SAPinst. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*. The following table provides an overview of the installation options available for the export: Export Services for a Central System Export Service Remarks Export Preparation NOTE Do not perform this step if you use the database-specific method. 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. In this case. go to the directory (%TEMP% \sapinst_exe. Optional step for preparing the export. 3.EXT. CAUTION Make sure that you choose the system copy options in exactly the order they appear for each system variant.xxxxxx. End of: Windows | 2. and enter the following command: sapinst —p. and SAPinst GUI. For more information. GUI server.5 Database Independent System Copy Exporting the Source System Using SAPinst NOTE ● If you use virtual host names for the primary application server or the database instance or both (for example. SAPinst uses port 21200 to communicate with the GUI server. choose Software Life-Cycle Options System Copy <database> Source System <Distribution option> Based on <technical stack> .4 4. see Database-Specific System Copy procedure [page 53] or Database-Independent System Copy [page 21]. ● During installation. in a high availability environment).STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*. The GUI server uses port 21212 to communicate with SAPinst GUI. Select the corresponding system copy option from the tree structure. On the Welcome screen. the default ports 21200 and 21212 are used for communication between SAPinst. according to the sequence of the process flow for the database-specific or the database-independent system copy procedure.xxxx).exe SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui> ● To get a list of all available SAPinst properties.

Mandatory step for database-independent system copy procedure. file system full. position the cursor on the parameter field and choose F1 .TOC. copy the generated files into the SAPinst installation directory as soon as it has been created by SAPinst. power outage. the log file <package>. ■ If there is not enough disk space in the export directory. the TOC file <package>. 6. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*. It is currently not possible to distribute the export over different file systems automatically.5 Database Independent System Copy Exporting the Source System Using SAPinst Export Service Remarks Database Instance Export NOTE Do not perform this step if you use the database-specific method. choose System Copy Method Use database specific tools . CAUTION You must choose Typical when performing a system copy with database tools. choose Next. SAPinst: ● Stops the export.log. After you have entered all required input parameters. You can now view the log file directly by choosing View Logs.EXT. operating system crash). Database-specific procedures only: On the SAP System > Database Export screen. The installation directory is as soon as the first input screen appears. ● Displays a dialog that informs you about the error. the R3load database export fails. ■ If an error occurs during the dialog phase. You can then move the dump files that have been created from the file system in which the export directory is located to a different file system during the export.4 4.DBSIZE.log and make sure that all tables in the TSK file <package>.XML) ■ Exports the ABAP database content 4. Remove the dump files <package>. you have to repeat the export of the complete package. After you have selected the required option. Follow the instructions in the SAPinst input dialogs and enter the required parameters.<nnn>. Troubleshooting If an export process aborts due to a hardware failure (for example. you have to abort the export with OK and try to solve the problem. You can then find error messages in the log files SAP*. SAPinst starts the export and displays the progress during the processing phase. If you generated SQL files with DDL statements (see Generating DDL Statements [page 25]). NOTE For more information about input parameters in SAPinst.*TSK* have the status flag 'xeq' or 'err' set. NOTE 5. 36/116 PUBLIC 2011-03-07 .STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*. Finally.

● Continue the export by choosing Retry. SAPinst: ● Stops the export. start SAPinst.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. Continue with the export. see Using SAPinst GUI [page 98].2 Running SAPinst on IBM i to Perform the Export 4. Reason: Only members of sapinst UNIX group can access the installation directory.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. ● Displays a dialog that informs you about the error. ● Try to solve the problem.5 Database Independent System Copy Exporting the Source System Using SAPinst ■ If an error occurs during the processing phase.5. You can now: ● View the log file directly by choosing View Logs. ● Abort the export by choosing OK. Interrupted Installation with SAPinst [page 99]. Standard Edition) with graphical capabilities (AWT. Verify the /etc/group file and check if the sapinst group exists and OS users are members of this group. and Performing a Remote Export Using SAPinst [page 102]. This group is created by SAPinst as of NW 7.5. Swing). If the sapinst group does not exist yet. SAPinst will create this group during startup before the product catalog list is displayed.0 SR1. Only valid for: IBM i5/OS | 4.2. Edit /etc/group file and associate OS users with sapinst group. Only valid for: UNIX | ■ System Copy . Since IBM i does not provide a graphical user interface. End of: UNIX | For more information. 2011-03-07 PUBLIC 37/116 . Solution: Manually associate <sid>adm and ora<sid> OS users with sapinst group if this association is missing.4 4. you must install the JDK on a Windows host to perform the installation with SAPinst.

■ Only valid for: SAP CRM.SAP NetWeaver. Procedure The SAP J2EE Engine requires a Java Development Kit (Java™ 2 SDK. If necessary. because the JRE cannot be integrated into the SAPinst GUI executable for all platforms due to licensing issues. The following requirements apply: ■ The IBM i user profile and the Windows user account must have the same name and password. End of: SAP CRM. see http://service.SAP ERP.SAP Solution Manager. SAP components based on SAP Web AS and the SAP J2EE Engine. Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | 4.4 4. you need to download and install it.SAP Solution Manager.2. Standard Edition). 38/116 PUBLIC 2011-03-07 .SAP NetWeaver. Make sure that %JAVA_HOME% \bin is included in your system path.2 Preparing a Windows User Account and IBM i User Profile For the installation you need to create a user account on your Windows installation host and a user profile on the IBM i you want to install. you have two JDKs with different versions installed). ■ To check the version of an already installed JDK.SAP ERP. enter: java -version ■ If you have more than one Java Virtual Machine (JVM) installed on your system (for example.SAP SRM | Only valid for: SAP SCM | ■ The IBM i user profile must be the user QSECOFR.sap.com/ platforms Product Availability Matrix SAP NetWeaver SAP NetWeaver '04 JSE Platforms NOTE ■ JDK is not part of the SAP shipment.5 Database Independent System Copy Exporting the Source System Using SAPinst Prerequisites To prepare the system for SAPinst and SAPinst GUI you need to do the following: ■ Necessary operating system versions: Windows NT/2000/2003/XP ■ Check your Java Runtime Environment (JRE) on the host where SAPinst GUI runs. Therefore.5. ■ Set the system path if you install on Windows. 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 SRM | The IBM i user profile must have user class *SECOFR and all special authorities that belong to user QSECOFR. make sure that the JAVA_HOME environment variable is set to the valid <JAVA_HOME> directory.

SAP SRM | Enter the following command: End of: SAP CRM. However. SAPIUSR.SAP SRM | Assign the new user SAPIUSR to the group Administrators. End of: SAP CRM. End of: SAP CRM.SAP Solution Manager.SAP NetWeaver.SAP SRM | 8.SAP NetWeaver. enter your installation user name.SAP NetWeaver. In former installation documentation.SAP SRM | In the field User name. 7.SAP NetWeaver. For other installations.SAP ERP. Only valid for: SAP SCM | In the field User name. Only valid for: SAP CRM.SAP NetWeaver.SAP SRM | 3.SAP ERP. However for SCM. which conflicts with the previously recommended user SAPINST.SAP Solution Manager.SAP ERP.SAP ERP.SAP Solution Manager. in future releases SAP has introduced a group called SAPINST on IBM i.SAP NetWeaver.SAP SRM | Windows: 1. Deselect User must change password at next logon. we used the user SAPINST. enter your installation user name QSECOFR. Procedure Only valid for: SAP CRM. End of: SAP CRM.SAP ERP.SAP Solution Manager.SAP ERP.4 4. Only valid for: SAP CRM.SAP SRM | 5. Only valid for: SAP SCM | Assign the new user QSECOFR to the group Administrators. Only valid for: SAP CRM.SAP Solution Manager.SAP ERP.SAP ERP. End of: SAP SCM | ■ The Windows user account must have administrator rights on the Windows installation host. Create a local user.SAP NetWeaver.5 Database Independent System Copy Exporting the Source System Using SAPinst NOTE This is different to other installations on IBM i.SAP SRM | 2011-03-07 PUBLIC 39/116 .SAP NetWeaver.SAP ERP.SAP NetWeaver.SAP NetWeaver. enter the password of the user QSECOFR on your IBM i. End of: SAP SCM | IBM i: Only valid for: SAP CRM.SAP SRM | NOTE The user name SAPIUSR and the password SAP are used as examples in the procedures. enter the password SAP.SAP Solution Manager. you need to use the user QSECOFR because the liveCache client software has to be installed by this special user. End of: SAP SCM | 6. 2.SAP Solution Manager.SAP Solution Manager.SAP Solution Manager.SAP Solution Manager.SAP SRM | In the fields Password and Confirm password. we recommended that you create user SAPINST or SAPIUSR. for example. Only valid for: SAP SCM | In the fields Password and Confirm password. End of: SAP CRM. End of: SAP SCM | 4.SAP ERP.

the downloaded Installation Master DVD must be available on your Windows installation host. ■ The Installation Master DVD must be inserted in the DVD drive of your Windows installation host. Prerequisites ■ An FTP server running on IBM i ■ You must prepare a user. but has to install the product on IBM i. ■ Make sure there is no system variable LANG defining a LOCAL on your IBM i host where you want to install your SAP system. For more information about how users are prepared. The communication is done using TCP/IP. This means that all actions required for IBM i are initiated remotely on Windows but executed locally using the TMKSVR. To find out if this variable can be de-activated during the installation. End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | 4. End of: SAP SCM | Only valid for: SAP SCM | After the installation. ■ If you have downloaded the DVDs from SAP Service Marketplace.4 4. To delete an environment variable use the command WRKENVVAR. SAPinst is running on Windows. In addition. Delete the environment variable QIBM_PASE_CCSID at least for the time while you are installing your SAP system. End of: SAP SCM | CAUTION You should not set the system variable QIBM_PASE_CCSID. which is done automatically by the TMKSVR. This could lead to codepage conversion problems within the installation. Only valid for: SAP SCM | To change the user QSECOFR. enter the following command: End of: SAP SCM | Only valid for: SAP SCM | CRTUSRPRF USRPRF(QSECOFR) LANGID(ENU) CNTRYID(US) CCSID(500). you can revert the user profile QSECOFR back to the old values.3 Installing TMKSVR and Creating an Installation Share The TMKSVR is the interface between IBM i and Windows for the installation with SAPinst.2.5.5 Database Independent System Copy Exporting the Source System Using SAPinst CRTUSRPRF USRPRF(SAPIUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('Test User for SAP Installation') SPCAUT(*USRCLS) LANGID(ENU) CNTRYID(US) CCSID(500). an installation share on the IBM i host needs to be created and mapped to the Windows installation host. see Preparing a Windows User Account and IBM i User Profile [page 38]. The TMKSVR has to be installed and an installation share has to be created on all IBM i hosts where instances of an SAP system should be installed. 40/116 PUBLIC 2011-03-07 .

SAP SRM | Figure 2: End of: SAP CRM.SAP ERP. To remove the environment variable LANG from your environment on your IBM i host you can use the command WRKENVVAR. For SCM. You can start the setup program by double-clicking on it in the Windows Explorer.5 Database Independent System Copy Exporting the Source System Using SAPinst contact your IBM i administrator.SAP ERP.SAP SRM | 2011-03-07 PUBLIC 41/116 . For more information.SAP SRM | NOTE This user must have the same user ID and password as the user that you are using for the installation on IBM i (a user with administrator rights similar to QSECOFR). Log on to your Windows installation host as the installation user.SAP ERP.SAP NetWeaver. code page problems might prevent TMKSVR processes from starting.SAP NetWeaver. see Preparing a Windows User Account and IBM i User Profile [page 38]. Run SETUP.SAP SRM | Only valid for: SAP SCM | NOTE This user must have the same user ID and password as the user that you are using for the installation on IBM i. this user must be QSECOFR).SAP Solution Manager. Procedure 1.SAP NetWeaver.EXE from the directory IM_OS400_PPC64\TMKSVR on the DVD containing the installation package.SAP NetWeaver.4 4. End of: SAP CRM. Only valid for: SAP CRM. End of: SAP SCM | 2.SAP Solution Manager.SAP ERP. Otherwise. The following dialog box appears: Only valid for: SAP CRM.

For more information.SAP NetWeaver. Enter the following values: ■ IBM i Hostname: Enter the name of the IBM i host where you want to install TMKSVR. TMKSVR00). Only change this port number if you encounter problems during installation because the port is in use. ■ Only valid for: SAP CRM.SAP SRM | IBM i Administrator (QSECOFR or similar): Enter the IBM i user.SAP ERP. During installation. see the documentation INSTALL. End of: SAP SCM | ■ TMKSVR instance number: Leave the value at 0.SAP NetWeaver. see Preparing a Windows User Account and IBM i User Profile [page 38].SAP ERP.4 4. For more information. see Preparing a Windows User Account and IBM i User Profile [page 38].SAP SRM | Only valid for: SAP SCM | ■ System i Administrator (QSECOFR): Enter the IBM i user.PDF on the DVD in directory IM_OS400_PPC64\TMKSVR. A NetServer share named ROOTBIN is created on the IBM i host. with <nn> being the instance number (for example. You can map the share now to your Windows PC or let SAPinst map it during the installation. if possible. For more information. Result The installation uses FTP to install and starts the TMKSVR on IBM i. End of: SAP CRM. ■ TMKSVR Instance Port (also referred to as the Dispatcher Port): Leave the value at 59975. a library named TMKSVR<nn> is created. 42/116 PUBLIC 2011-03-07 .5 Database Independent System Copy Exporting the Source System Using SAPinst Only valid for: SAP SCM | Figure 3: End of: SAP SCM | 3.

Procedure 1. which is a synonym for “export an SAP system”. see Preparing the Windows Host for the SAP System Installation [page 37]. Prerequisites CAUTION Make sure that you shut down all SAP Application Servers before the export. see the section Removing the SAPinst Installation Files in the installation documentation. ■ The Windows host is set up. see Installing TMKSVR and Creating an Installation Share [page 40].5. Start SAPinst from the SAP Installation Master DVD by using the default installation directory (recommended): 1. see the section Removing the SAPinst Installation Files in the installation documentation. For more information. the target system might be inconsistent. see Preparing a Windows User Account and IBM i User Profile [page 38]. Double-click sapinst. ■ The users required for the installation are prepared. This procedure tells you how to run SAPinst to install one or more SAP instances. ■ Make sure that the JAVA_HOME environment variable is set correctly on your Windows host.2. End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | Only valid for: IBM i5/OS | 4. SAPinst creates the installation directory \usr\sap\sapinst on IBM i. Log on to the Windows host as the installation user. NOTE For more information about how to delete the TMKSVR after a successful installation.4 Starting SAPinst on IBM i CAUTION This section refers to “installation of an instance”. Otherwise.4 4. Enter the following command in a single line: 2011-03-07 PUBLIC 43/116 .5 Database Independent System Copy Exporting the Source System Using SAPinst NOTE For more information about how to delete the TMKSVR after a successful installation.exe from the following path:<Mapped drive>:<Copied Installation Master DVD>\IM_OS400_PPC64 2. For more information. For more information. 2. It describes an installation where SAPinst GUI and SAPinst server are running on the same Windows host. For more information. ■ TMKSVR is up and running: WRKACTJOB SBS(TMKSVR00) (there must be a DISPATCH job). The database must still be running. see Preparing a Windows User Account and IBM i User Profile [page 38].

SAPinst uses port 21200 to communicate with the GUI server. 44/116 PUBLIC 2011-03-07 . enter the following command: sapinst -p ■ If you use virtual host names for the primary application server or the database instance or both (for example. ■ During the installation. The SAPinst/TMKSVR – Session Parameters dialog box appears and prompts you for the target IBM i parameters.5 Database Independent System Copy Exporting the Source System Using SAPinst sapinst. In the Welcome screen. Figure 4: 4. In this case. the default ports SAPinst 21212 and 21213 are used for communication between SAPinst.exe SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to sapinst_gui> NOTE ■ For a list of all available SAPinst properties. start the export with the property SAPINST_USE_HOSTNAME=<virtual host>. Enter your values. and SAPinst GUI. You get an error message if one of these ports is already in use by another service. choose Software Life-Cycle Options System Copy <your database> Source System <System Variant> Based on <AS ABAP and AS Java | AS Java | AS ABAP> . The SAPinst GUI now starts automatically by displaying the Welcome screen. in a high availability environment).4 4. open a command prompt and change to the required directory as follows: <Mapped drive>:<Copied Installation Master DVD>\IM_OS400_PPC64 3. GUI server.

DBSIZE. SAPinst performs the following steps: ■ Creates the export directory structure with label files Export Preparation 2011-03-07 PUBLIC 45/116 .EXT.5 Database Independent System Copy Exporting the Source System Using SAPinst 5.STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*. You need to perform this step on the database instance host.XML) ■ Exports the ABAP database content Remarks Export Services for a Distributed System or a High-Availability System Export Service Optional step for the database-independent system copy procedure to prepare the export.4 4.DBSIZE. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*. for one of the following procedures: ■ Database-Specific System Copy [page 53] ■ Database-Independent System Copy [page 21] CAUTION 6. NOTE Do not perform this step if you use the You need to perform this step on the database instance host.EXT. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*. Make sure that you choose the installation services in exactly the order they appear for each system variant. Optional step for preparing the export. 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 Service Remarks Export Preparation NOTE Do not perform this step if you use the database-specific method. Database Instance Export NOTE Do not perform this step if you use the database-specific method.STR) ■ Updates database statistics(…) ■ Calculates the size of the target database (*.DBSIZE. database-specific method.STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*. Select the corresponding installation service from the tree structure.EXT. according to the sequence of the process flow. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.XML) Mandatory step for database-independent system copy procedure.XML) Database Instance Export Mandatory step for the database-independent system copy procedure.

5 Database Independent System Copy Exporting the Source System Using SAPinst Export Service NOTE Remarks ■ Creates database structure files (*STR) ■ Do not perform this step if you use ■ Updates database statistics ■ Calculates the size of the target database the database-specific method. Choose Database and Central Instance Export.*TSK* have the status flag 'xeq' or 'err' set. the TOC file <package>. the log file <package>. ■ If an error occurs during the dialog phase.TOC. SAPinst: ● Stops the installation. position the cursor on the parameter field and choose F1 . SAPinst: ● Stops the installation. Choose Next. ● Displays a dialog that informs you about the error. Follow the instructions in the SAPinst input dialogs and enter the required parameters. you have to repeat the export of the complete package. power outage. copy the generated files into the SAPinst installation directory as soon as it has been created by SAPinst: 1. CAUTION You must choose Typical when performing a system copy with database tools. NOTE For more information about input parameters in SAPinst.4 4. ● Displays a dialog that informs you about the error. ■ If an error occurs during the processing phase. Finally.log and make sure that all tables in the TSK file <package>. Choose Next NOTE 9. Remove the dump files <package>. choose Next.XML) ■ Exports the database content 7. After you have entered all required input parameters. 3. 8.<nnn>. You can now directly view the log file by choosing View Logs. you must abort the installation with OK and try to solve the problem. operating system crash). The installation directory has been created as soon as the first input screen appears. 46/116 PUBLIC 2011-03-07 . the screen Finished installation is displayed. (*EXT. file system full. SAPinst starts the installation and displays the progress of the installation. When the installation has successfully completed. 2. After you have selected the required installation service. If you generated SQL files with DDL statements (see Generating DLL Statements [page 25]).DBSIZE. Troubleshooting CAUTION If an export process aborts due to a hardware failure (for example.

First of all. ■ To skip package processing. because it can cause inconsistent data files or database content. ● Abort the installation by choosing OK. set the package state from – to 0. To continue with the system copy proceed as follows: ■ If both the import and the export are completed successfully. if package processing failed and the package state has the value –. ■ If the export was completed successfully. but the import is canceled with errors. ● If the export was completed successfully but the import was canceled when loading the table content.4 4. there is nothing to do.5 Database Independent System Copy Exporting the Source System Using SAPinst You can now directly view the log file by choosing View Logs. set the status for export_state. the state can be set to 0 and processing of the package is restarted. you need to cancel the R3load process. (This is not recommended.) ■ If the package is currently being processed (the package state is ?). ■ Sockets only: You cannot restart processes. see Interrupted Installation with SAPinst [page 99]. If one of the corresponding R3load processes (export or import) is still running.properties from '+' to '0' ◆ for the TSK file of the export from 'ok' to 'err' ■ If both the export and the import are canceled with errors. set the package state from 0 or – to +. set the status ◆ for export_state. Then restart SAPinst to continue with the system copy.5. then any manual modifications to the package state are ignored.properties from '+' to '0'. Procedure ■ To restart package processing. End of: IBM i5/OS | End of: IBM i5/OS | 4. For more information. Restarting R3load Processes Using the Socket Option There are four possible situations where an R3load restart may be required. cancel it as well.3 Restarting R3load Processes The state file allows package states to be manually updated to restart failed R3load processes. proceed as follows: ● If the export was successful but the import was canceled when creating the index or the primary key. ● Try to solve the problem. ● Retry the installation by choosing Retry. proceed as follows: 2011-03-07 PUBLIC 47/116 . EXAMPLE For example.

6 Setting Up the Target System Purpose Use SAPinst to install the target system and import the database files that you have exported from the source system. EXAMPLE Export Import Table name TAB_1 TAB_2 TAB_3 TAB_4 Status ok err xeq xeq Table name TAB_1 TAB_2 TAB_3 TAB_4 Status ok ok err xeq The first object with errors here is TAB_2 (export). communication type Exchange Directory. More Information R3load Processes Using the Migration Monitor [page 81]. If you have already prepared the export (for more information. For more information. 2. you can set the status in the export_state. see Installing the Target System [page 50]. Prepare the central system host for the installation of your target system as described in the installation guide for your SAP system solution. on the SAP System > Communication Parameters for Export screen). The entry in the *state* file also must be set from '+' to '0'. 2. That means that in the import TSK file the status for TAB_2 must be set from 'ok' to 'err'. 48/116 PUBLIC 2011-03-07 . see Preparing the Export [page 30]) on the source system because you want to perform the export and import in parallel.properties from '-' to '+'. perform the following steps: 1. If you use the FTP Exchange option during the export (transfer type FTP. make sure that you have transferred all files that have been generated in the Preparing the Export [page 30] step on the source system.4 4. there is nothing to do. but the export was canceled with errors. 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'. Install the target system. 4. Process Flow Central System Perform the following steps on the central system host: 1. ● If the errors relate to different tables.6 Database Independent System Copy Setting Up the Target System ● If the errors in export and import relate to the same table. ■ If the import is completed successfully.

install the database instance of the target system. If required install additional dialog instances on dialog instance hosts as described in the installation guide for your SAP system solution. see Installing the Target System [page 50]. 2011-03-07 PUBLIC 49/116 . install additional dialog instances on the dialog instance hosts as described in the installation guide for your SAP system solution. If required. For more information. ■ If you did not prepare the export (see Preparing the Export [page 30]) on the source system. 5. 4. see Installing the Target System [page 50]. On the central instance host. make sure that you have transferred the files. If you use the FTP Exchange option during the export (transfer type FTP. perform the following steps: 1. on the SAP System > Communication Parameters for Export screen). End of: High Availability | 3. Only valid for: High Availability | Also prepare the central services instance host.6 Database Independent System Copy Setting Up the Target System 3. communication type Exchange Directory. 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. which were generated in the Preparing the Export [page 30] step on the source system. End of: High Availability | 2. Distributed System or High-Availability System Perform the following steps on the relevant installation hosts of your target system: 1. 2.4 4. If you did not prepare the export on the source system. For more information. install the target system Installing the Target System [page 50]. Only valid for: High Availability | Install the central services instance for the target system as described in the installation guide for your SAP system solution. install the central instance of the target system. Perform the following steps on the database instance host: ■ If you have already prepared the export (see Preparing the Export [page 30]) on the source system. Install the database instance of the target system.

End of: IBM DB2 for Linux and UNIX and Windows | 2.1 Installing the Target System Prerequisites Only valid for: Windows | Make sure there is enough free space on the target system for the database load. RELOAD is no longer available as an executable installation service.6. 50/116 PUBLIC 2011-03-07 . or if the database already exists. 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. CAUTION 3. End of: UNIX | NOTE As of SAP NetWeaver 7.6 Database Independent System Copy Setting Up the Target System 4. Procedure 1.XML located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE>.0. On the Welcome screen of the SAP Installation Master DVD.0 EHP 1.com. 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. look at the file DBSIZE. End of: Windows | Only valid for: UNIX | Make sure there is enough free space on the target system for the database load.0 EHP 1 SR 1. SAPinst recognizes this automatically and skips the related steps.4 4. If you plan to use Advanced Configuration options during the SAP System Database Import. 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> . make sure you have installed the most current version of SAPinst to avoid performance problems during the dialog phase. 4. You can find the latest version of SAPinst at http:// service. Prepare the target system host as described in the installation guide of your SAP solution based on SAP NetWeaver 7. Start SAPinst as described in the installation documentation for your SAP solution based on SAP NetWeaver 7.sap. If the database software has already been unpacked or installed. To find out the size of the export and the sizes of the tablespaces or dbspaces that will be created. Run the installation services required for your system copy in the sequence they are listed in the specific folder and according to process flow in Setting Up the Target System Using SAPinst [page 48].XML located in the directory <EXPDIR>/DB/<DATABASE>. but is performed automatically by SAPinst.

as default. enter the migration key on the Database Import screen. If you want to perform export and import in parallel. If you perform a heterogeneous system copy. NOTE On the SAP System > General Parameters screen. The required size for the table will be fifteen times larger than in the non-Unicode source system. Enlarge the database or database container. ■ The option Deferred Table Creation is not supported for load-based system copies for SAP systems that are not based on SAP NetWeaver 7. End of: IBM DB2 for Linux and UNIX and Windows | CAUTION 6. You must have run the service Prepare the Export on the source system [page 30] if you want to use the parallel export/ import option for the installation of the target system.6 Database Independent System Copy Setting Up the Target System 5.Select the Database Instance Installation Method screen. Only valid for: IBM DB2 for Linux and UNIX and Windows | CAUTION ■ Make sure that you take the information about automatic storage that is provided in the Running SAPinst section in the appropriate installation guide into consideration. NOTE 8. ■ 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. 7. When SAPinst displays the DVD / CD browser window and asks for the Export Migration CD. To install the target system. Complete the installation as described in the installation documentation for your SAP component. the data import into the target system might abort because of missing space in the database tablespace or dbspace. follow the instructions in the SAPinst input dialogs and enter the required parameters. in which the DYNPSOURCE table will be created in the target database. 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. On the Database . 2011-03-07 PUBLIC 51/116 .4 4.0 EHP1. enter the path to the export directory <EXPDIR>. You can only deselect this option if you perform the system copy for a non-Unicode SAP system that has been upgraded to SAP NetWeaver 7. the Unicode System option is selected.0 EHP 1 or higher. choose the Parallel Export / Import option.

4 4. The import continues with the table that was not imported successfully.6 Database Independent System Copy Setting Up the Target System NOTE If you have to restart the import after an error. refer to Restarting R3load Processes [page 47]. 52/116 PUBLIC 2011-03-07 . just restart SAPinst. For more information about restarting failed R3load processes.

CAUTION 2. End of: UNIX | Only valid for: IBM i5/OS. the UME service can not be started. 3. Only valid for: UNIX | Prepare the target system [page 61]: 1.5 Database-Specific System Copy 5 Database-Specific System Copy The following sections describe database-specific methods for the homogeneous system copy. End of: Windows | 2. see Planning [page 9] and to the SAP Notes describing the homogeneous system copy for your database system. For more information about methods available for your database. Only valid for: Windows | Install the database software as described in the installation guide of your SAP solution. create an offline backup of the source database [page 60]. 2011-03-07 PUBLIC 53/116 .Windows | Follow the instructions on the SAPinst screens until you are requested to perform the database backup/restore. If required. 2. Process Flow on the Target System 1. Create the database file system (if it does not yet exist). Databasespecific methods are not available for all database systems. 3. Process Follow the sequence of steps described in the process flows below for a: ■ Central System ■ Distributed System ■ High Availability System Central System To perform the export for a central system. Install the database software. Make sure that you create the secure store of the target system using the same key phrase as of the source system. Otherwise. you need to proceed as follows on the central system host: Process Flow on the Source System (Export) 1. Follow the instructions on the SAPinst screens until SAPinst requests you to install the database software and to perform the database backup/restore. Generate the control file structure for the target database [page 56].

On the database instance host. End of: UNIX | 3. Only valid for: IBM i5/OS. proceed as follows: Process Flow on the Source System (Export) 1. restart SAPinst as described in the installation guide of your SAP solution. you have to perform the follow-up activities [page 75]. on the database instance host. the UME service can not be started. restart SAPinst as described in the installation guide of your SAP solution. The source of 54/116 PUBLIC 2011-03-07 . create the database file system (if not yet existing). Distributed System or High Availability System To perform the export for a distributed or high-availability system. install the database software. End of: IBM i5/OS.Windows | 4. Otherwise. follow the instructions on the SAPinst screens until SAPinst requests you to install the database software and to perform the database backup/restore. This method is suitable for creating an exact copy of an existing database. you can create a homogeneous copy of an Oracle database by copying database files. End of: Windows | 2. you have to perform the follow-up activities [page 75]. On the database instance host of the source system. NOTE If required. To complete the system copy.1 Oracle-Specific Procedure Purpose In an SAP system environment. To complete the system copy. On the database instance host.5 5.1 Database-Specific System Copy Oracle-Specific Procedure CAUTION Make sure that you create the secure store of the target system using the same key phrase as of the source system.Windows | On the database instance host. install the database software as described in the installation guide of your SAP solution. If required. create an offline backup of the source database [page 60]. Only valid for: Oracle | 5. On the database instance host. Only valid for: UNIX | Prepare the target system [page 61]: 1. follow the instructions on the SAPinst screens until you are requested to perform the database backup/restore. generate the control file structure for the target database [page 56].Windows | 4. Only valid for: Windows | Process Flow on the Target System On the database instance host. 3. 1. End of: IBM i5/OS. 2. NOTE If required. 2.

1 or higher is installed on the database instance. ■ The JAVA_HOME environment variable must point the JRE directory. ■ If your source system is an ABAP only system. ■ The classes12. ■ You must shut down the SAP system and the database when you create an offline backup manually or an offline backup with BR*Tools.jar must exist in the <ORACLE_HOME>/jdbc/lib directory (installed using a standard Oracle installation). an online backup. SAPinst prompts for the character set during the installation (key: Database Character Set). Prerequisites ■ You must use the same Oracle release and patch level for your database in the source and target system. ■ The source and target systems must be binary compatible. make sure that JRE version 1. you must choose this character set when installing the target system. 2011-03-07 PUBLIC 55/116 .5 5. The installation default is WE8DEC or UTF8 for Unicode systems. connect to the source database as user sap<schemaid> or sapr3 with sqlplus and enter: SELECT * FROM V$NLS_PARAMETERS. 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. You can use an offline backup. You use SAPinst for the installation on the target system host as described in the installation documentation for your SAP component.1 Database-Specific System Copy Oracle-Specific Procedure the copy is a complete data backup of your source database. Only the SAPinst steps for setting up and loading the database content are different. ■ This method is faster than the R3load and Jload method. If your source system uses the US7ASCII character set. ■ Source system host and target system host must be different. or the file system of your source host. To find out the character set used by the source system. Advantages ■ You can use existing offline or online backups.4. 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. ■ You must have prepared your system for SAPinst [page 17]. the source and target systems must run on different hosts. ■ For security reasons. ■ You cannot change the database schema and the table space names.

see the documentation ORABRCopy.1.SAR End of: Windows | 3. The database must still be running. which is part of the OraBRCOPY.SAR End of: UNIX | Only valid for: Windows | <DVD-DRIVE>:\COMMON\INSTALL\ORA\ORABRCOPY.pdf. Prerequisites RECOMMENDATION We recommend that you shut down the SAP system before you perform the following steps.SQL. which can be used without further adaptations on the target system.TRC and init<targetSID>./ora_br_copy. For more information about the OraBRCopy tool.ora in your installation directory. Copy the ORABRCOPY.5 5.1 Database-Specific System Copy Oracle-Specific Procedure 5. 4.SAR archive from the SAP Installation Master DVD to the installation directory and extract it using SAPCAR.SAR archive. Create an installation directory <INSTDIR> (UNIX: with permissions 777) on the source system. Procedure 1. shuts down and restarts the database and performs the required log switches. 2. enter the following commands: ● On UNIX: .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. You can find the archive in the following directory on the Installation Master DVD: Only valid for: UNIX | <DVD-DIR>:/COMMON/INSTALL/ORA/ORABRCOPY. enter the following commands: ● On UNIX: 56/116 PUBLIC 2011-03-07 . Make sure that all redo log groups are archived 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.SQL to the current working directory.1 Generating the Control File Structure The OraBRCopy Java tool writes a file CONTROL. ■ If you perform an offline or online backup using BR*Tools. CONTROL.

5 5.1

Database-Specific System Copy Oracle-Specific Procedure ./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"

2011-03-07

PUBLIC

57/116

5 5.1

Database-Specific System Copy Oracle-Specific Procedure

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 ( 'D:\ORACLE\NEW\ORIGLOGA\LOG_G13M1.DBF', 'D:\ORACLE\NEW\MIRRLOGA\LOG_G13M2.DBF' ) SIZE 50M, GROUP 4 ( 'D:\ORACLE\NEW\ORIGLOGB\LOG_G14M1.DBF', 'D:\ORACLE\NEW\MIRRLOGB\LOG_G14M2.DBF' ) SIZE 50M DATAFILE 'D:\ORACLE\NEW\SAPDATA1\SYSTEM_1\SYSTEM.DATA1', 'D:\ORACLE\NEW\SAPDATA3\IMS_1\IMS.DATA1', 'D:\ORACLE\NEW\SAPDATA3\IMS_2\IMS.DATA2', 'D:\ORACLE\NEW\SAPDATA3\IMS_3\IMS.DATA3', 'D:\ORACLE\NEW\SAPDATA3\IMS_4\IMS.DATA4', 'D:\ORACLE\NEW\SAPDATA4\IMS_5\IMS.DATA5', 'D:\ORACLE\NEW\SAPDATA4\IMS_6\IMS.DATA6', 'D:\ORACLE\NEW\SAPDATA4\IMS_7\IMS.DATA7', 'D:\ORACLE\NEW\SAPDATA4\IMS_8\IMS.DATA8', 'D:\ORACLE\NEW\SAPDATA4\IMS_9\IMS.DATA9', 'D:\ORACLE\NEW\SAPDATA1\IMS700_1\IMS700.DATA1', 'D:\ORACLE\NEW\SAPDATA1\IMS700_2\IMS700.DATA2', 'D:\ORACLE\NEW\SAPDATA1\IMS700_3\IMS700.DATA3',

58/116

PUBLIC

2011-03-07

5 5.1

Database-Specific System Copy Oracle-Specific Procedure

'D:\ORACLE\NEW\SAPDATA1\IMS700_4\IMS700.DATA4', 'D:\ORACLE\NEW\SAPDATA2\IMS700_5\IMS700.DATA5', 'D:\ORACLE\NEW\SAPDATA2\IMS700_6\IMS700.DATA6', 'D:\ORACLE\NEW\SAPDATA2\IMS700_7\IMS700.DATA7', 'D:\ORACLE\NEW\SAPDATA2\IMS700_8\IMS700.DATA8', 'D:\ORACLE\NEW\SAPDATA2\IMS700_9\IMS700.DATA9', 'D:\ORACLE\NEW\SAPDATA3\IMS700_10\IMS700.DATA10', 'D:\ORACLE\NEW\SAPDATA4\IMS700_11\IMS700.DATA11', 'D:\ORACLE\NEW\SAPDATA1\IMSUSR_1\IMSUSR.DATA1', 'D:\ORACLE\NEW\SAPDATA2\ROLL_1\ROLL.DATA1' ; ALTER DATABASE OPEN RESETLOGS; ALTER TABLESPACE PSAPTEMP ADD TEMPFILE 'D:\ORACLE\NEW\SAPDATA3\TEMP_1\TEMP.DATA1' SIZE 350M REUSE AUTOEXTEND OFF; 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 ( 'D:\ORACLE\NEW\ORIGLOGA\LOG_G11M1.DBF', 'D:\ORACLE\NEW\MIRRLOGA\LOG_G11M2.DBF' ) SIZE 50M, Group 2 (

2011-03-07

PUBLIC

59/116

DATA1' … The count of the data files must be equal to the count of the corresponding data files in the trace file. … The size must be equal to the corresponding size in the trace file. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE 'D:\ORACLE\NEW\SAPDATA3\TEMP_1\TEMP. 'D:\ORACLE\NEW\SAPDATA1\SYSTEM_1\SYSTEM. stop the database (normal shutdown) and perform a complete offline backup.1. 4. Choose between the following possibilities: Performing an offline backup manually or an offline or online backup with BR*Tools. The number of rows with ALTER TABLESPACE must be equal to the number of corresponding rows in the trace file. You can use the trace file CONTROL.TRC created by OraBrCOPY to determine the file system trees that have to be saved. 'D:\ORACLE\NEW\SAPDATA3\IMS_1\IMS.DATA1' SIZE 350M REUSE AUTOEXTEND OFF. ■ You stop the database (normal shutdown) and copy the database files when the actual transfer to the target system takes place. 5. on tape) or if you have to perform the database shutdown at a certain time. … 'D:\ORACLE\NEW\SAPDATA1\IMS700_1\IMS700. You do not have to perform any preparations for the actual transfer now. 60/116 PUBLIC 2011-03-07 . ■ Creating an Offline Backup Manually [page 60] ■ Creating an Offline or Online Backup with BR*Tools [page 61] 5.1 Database-Specific System Copy Oracle-Specific Procedure The sizes of the respective groups must be equal to the sizes of the corresponding groups in the trace file.DATA1'.2 Creating a Backup Create a backup if required. ■ If you want to transport the database file (for example.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.1. 5. 6. you can use it (provided that redo logs were cleaned up with forced log switches).5 5.2.DATA1'. Proceed with the next step.

the external backup tools must be configured so that a restore is possible on the target host. For more information.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. 5. see Restoring the Database Files on the Target System with BR*Tools [page 64]. with or without RMAN. see Restoring the Database Files on the Target System Manually [page 64].1 Database-Specific System Copy Oracle-Specific Procedure NOTE If you choose this manual offline backup method.2.sap. The backup strategy must simply be valid for restore and recovery. For more information. NOTE If you choose a backup method with BR*Tools. complete or incremental. you cannot change the database schema and the table space names of the new target system. In addition for BACKINT and RMAN.3 Preparing the Target System Prerequisites Make sure that sapdata<n> file systems on the target system host are large enough. you also have to restore the database files on the target system with BR*Tools. you also have to restore the database files on the target system manually. with or without BACKINT. This means that a complete restore and recovery of the source database must be possible.1. CAUTION When you perform a system copy with the Oracle backup/restore method.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Administrator’s Guide Technical Operations for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle BR*Tools for Oracle DBA BR*Tools in Action Backup and Database Copy with BR*Tools . Procedure 1.com/nw70 SAP NetWeaver 7. Install the target SAP system with SAPinst as described in the installation documentation for your SAP solution. choose the required installation service: SAP NetWeaver 7. When installing the 2011-03-07 PUBLIC 61/116 .0 including Enhancement Package 1 SAP NetWeaver 7.0 including Enhancement Package 1 Software Life-Cycle Options System Copy Oracle Target System <Central System | Distributed System | High-Availability System> . and so on. CAUTION On the Welcome screen.5 5. Procedure Proceed as described in the SAP Library at: help. 5.1.

Please proceed as follows:.5 5. If they do not exist. extract the Oracle stage archives manually and install the Oracle Software as described in the installation documentation for your SAP solution. 3. 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 62/116 PUBLIC 2011-03-07 . ■ Proceed until SAPinst stops to restore the database files on the target system. If necessary. The schema names of the source and target system must be identical. database instance.1 Database-Specific System Copy Oracle-Specific Procedure target central instance. or dialog instance make sure that you enter the correct database schema names (which are the database schema name of the source system).. ■ When SAPinst prompts for the installation type. choose Homogeneous System Copy (Backup/ Restore).. The following message is displayed: SAPinst now stops the installation. 2.

5 5.1

Database-Specific System Copy Oracle-Specific Procedure

4.

● <drive>:\oracle\<TARGET_DBSID>\sapcheck 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
Only valid for: UNIX |

5.

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.

7.

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. Uncheck Allow inheritable permissions from the parent.... 4. In the next dialog, choose Copy to copy the permission entries that were previously applied from the parent to this object. 5. Choose OK. 6. Set the permissions for the above-mentioned accounts SYSTEM, Administrators, SAP_<DBSID>_GlobalAdmin, or SAP_<DBSID>_LocalAdmin to Full Control. 7. Delete all other accounts. Restore the database files on the target system either manually (see Restoring Database Files on the Target System Manually [page 63]) or with BR*Tools (see Restoring the Database Files on the Target System with BR*Tools [page 64]), then proceed with SAPinst.

5.1.4 Restoring Database Files on the Target System Manually
CAUTION

If you do not use an offline backup, but copy the database files directly from the source to the target system host, make sure that you shut down the database on the source system before you copy the listed files from the source to the target directories.
Procedure

1.

Copy the following files from the source to the target system host by copying the listed files from the source directories to the target directories. For more information, see Creating an Offline Backup Manually [page 60] Directories on UNIX:

2011-03-07

PUBLIC

63/116

5 5.1

Database-Specific System Copy Oracle-Specific Procedure Source and Target Directory
/oracle/<DBSID>/sapdata<x> /oracle/<DBSID>/origlog<x> /oracle/<DBSID>/mirrlog<x>

Files

All files All files All files
CONTROL.SQL

source: <INSTDIR> target: <SAPINST_INSTDIR> source: <INSTDIR> target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/dbs

init<TARGET_DBSID>.ora

Directories on Windows:
Source and Target Directory
<drive>:\oracle\<DBSID>\sapdata<x> <drive>:\oracle\<DBSID>\origlog<x> <drive>:\oracle\<DBSID>\mirrlog<x>

Files

All files All files All files
CONTROL.SQL

source: <INSTDIR> target: <SAPINST_INSTDIR> source: <INSTDIR> target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database
NOTE

init<TARGET_DBSID>.ora

If you use an existing offline backup, the source data files and log files are not located in the directories shown in the table. The installation directory of the target system is normally located in the directory:
%programfiles%\sapinst_instdir\NW04S\LM\COPY\ORACLE\SYSTEM\<system_variant>

2.

3. 4.

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. Verify that the created directories and copied files have the owner ora<target_dbsid>, belong to the group dba, and have the permissions 740. Make sure that the control files are not restored. If necessary, remove them. The file names are specified by the control_files parameter of the init<TARGET_DBSID>.ora file.

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

1.

Copy the following files from the source system host to the target system host by copying manually the listed files from the source directories to the target directories. ■ On UNIX:
Source and Target Directory Files
CONTROL.SQL

source: <INSTDIR> target: <SAPINST_INSTDIR>

64/116

PUBLIC

2011-03-07

5 5.2

Database-Specific System Copy SAP MaxDB-Specific Procedure Source and Target Directory Files
init<TARGET_DBSID>.ora

source: <INSTDIR> target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/
dbs

■ On Windows:
Source and Target Directory Files
CONTROL.SQL

source: <INSTDIR> target: <SAPINST_INSTDIR> source: <INSTDIR> target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database

init<TARGET_DBSID>.ora

2.

Create an Oracle spfile from init<TARGET_DBSID>.ora profile as follows:
SYNTAX sqlplus /nolog connect / as sysdba create spfile from pfile; exit

3.

4.

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 . Shut down the Oracle database instance as follows:
SYNTAX sqlplus /nolog connect / as sysdba shutdown immediate exit

End of: Oracle | Only valid for: MaxDB |

5.2 SAP MaxDB-Specific Procedure
In an SAP system environment, you can create a homogeneous copy of an SAP MaxDB database by using the backup and restore method. This method is suitable for creating an exact copy of an existing database. The source of the copy is a complete data backup of your source database. The SAPinst tool is used for 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

2011-03-07

PUBLIC

65/116

This description is not valid for the liveCache system copy. see below. You can find more information on DBMGUI here: http://maxdb.2 Database-Specific System Copy SAP MaxDB-Specific Procedure database installation method. configure the database data volumes according to this value. Check SAP Note 552464 to find out which processor and operating system combination uses which byte order. divide this value by 128. That is.5 or higher on your system. ■ Data backup You perform the complete data backup of your source database. You can also copy a system based on big-endian to another system based on big-endian.sap. When SAPinst prompts you.5. After you have performed recovery and post-recovery activities you can continue the installation in SAPinst. 66/116 PUBLIC 2011-03-07 . Advantages ■ You can use existing offline backups. Prerequisites ■ Byte order – little-endian or big-endian You can use the backup and restore method to copy systems with the same byte order.htm Tools Database Manager GUI ■ Database Software The database software on the target host must have the same version as the software on the source host.5 5. SAPinst stops before the database instance initialization and asks you to perform the recovery on the target database.<password> sql_execute 'SELECT USEDPERM FROM SERVERDBSTATISTICS' The result of this query is the amount of used space.0 Build 12 or above. For more information. You can find the size of the used pages on the source system as follows: dbmcli —d <database_name> —u <dbm_user>. To calculate the used space in MB. The JAVA_HOME environment variable must point to the JRE directory.<password> —n <database_server> —u SQL sap<sid>.com/currentdoc/default. ■ JRE You must have installed JRE version 1. Disadvantage You can only copy between systems with the same byte order. The build number of the software version on the target host must be greater than or equal to the version on the source host. you can copy a system based on little-endian to another system based on little-endian. expressed as the number of 8 KB pages. ■ 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. ■ This method is faster than the database-independent method using R3load or Jload [page 21]. ■ Recovery tool You are using the SAP MaxDB Database Manager (DBMGUI) version 7.

To install the new system you start SAPinst as follows: <SAP Product> Software Life-Cycle Options System Copy SAP MaxDB Target System <Central System | Distributed System | High-Availability System> . DBSTATIADA. It takes some time for the database server to format the database volumes. 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.. End of: MaxDB | 2011-03-07 PUBLIC 67/116 . Start the data recovery wizard from DBMGUI 1. see SAP Note 588515. 2. If you do not already have a suitable recent complete SAP MaxDB backup. 3. 4. DBSTATHADA. CNMEDIA. Register your database instance in the DBMGUI 2. DBSTAIHADA. NOTE 3. It initializes the database instance first. Do the following on the source system: 1. After installation is complete. CNREPRT. Do the following on the target system: 1. Specify the backup medium. SAPinst stops in the Perform Database Recovery screen before database initialization and asks you to perform the data recovery. The recovery wizard does not start the recovery immediately. 6. select Restore a medium. Start the restore procedure. Continue with SAPinst or restart it if you stopped it during the recovery. Check that the database instance is in the admin state. 4.. Choose Recovery Recovery with Initialization . In type of recovery. Make the backup medium available on the target host. 2. 5. During the installation of the database instance. you maintain the database connection for CCMS. For more information. DBSTATTADA.2 Database-Specific System Copy SAP MaxDB-Specific Procedure Process 1. check the state of the target database instance and change the database state to online if it is not already in online state. 6. create a complete data backup using the DBMGUI tool: DBMGUI Backup Backup Wizard Complete 2.5 5. After the restore. SDBAADAUPD 5.

Attach the database files or restore the backup of the source database on the target database server. ■ Choose the installation services in exactly the order they appear. 3. End of: Windows | MS SQL Server | Only valid for: IBM DB2 for Linux and UNIX and Windows | 5. Since 68/116 PUBLIC 2011-03-07 . The backup/restore method and the detach/attach method have the following advantages compared to the R3load method: ■ You can use an existing backup. you can make a backup on one type of platform and use it on another type. ● With SQL Server. UNIX. or the detach/attach method in an SAP environment. The SAPinst installation tool supports both methods. this method is also referred to as backup/restore procedure. see the MS SQL Server installation guide for your SAP system at http:// service. NOTE ● For more information about the system copy procedure.3 Database-Specific System Copy MS SQL Server-Specific Procedure Only valid for: Windows | MS SQL Server | 5.com/installnw70. see SAP Notes 193816 and 151603. 2. ■ These methods are much faster than the database-independent method [page 21]. make sure that you select Homogeneous System Copy (MS SQL Server-specific: Detach/Attach or Backup). 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. That is.4 IBM DB2 for Linux. For more information. ■ On the SAPinst screen SAP SystemDatabase. you can use backup images across the platforms I386. Detach the database files from the source system database or create a backup and copy the files to the target system. and Windows-Specific Procedures The database-specific procedure for the creation of a system copy is based on a restore of an existing online or offline backup.5 5.sap.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. Process 1. Therefore. ● You can attach SQL Server 2000 files to SQL Server 2005 but not vice versa. x64. IA64.

see the Database Administration Guide: SAP on IBM DB2 for Linux. and Windows-Specific Procedures a DB2 backup can be used cross-platform within certain limitations (see below). ■ You cannot copy an individual MCOD component to another system. For more information. Prerequisites ■ It must be possible to restore the backup of the source system on the platform of the target system. you can use backup images cross-platform within certain limitations. make sure that the relevant file systems are available. UNIX.4 Database-Specific System Copy IBM DB2 for Linux. only the SAPinst steps for setting up and loading the database are replaced by a database restore. SAPinst is used for installation on the target system host as described in the installation documentation for your SAP component.doc/ doc/c0005960. ■ If errors occur when restoring the backup on the target system.db2.1Information Center at http:// publib. The necessary procedure in this case is called database relocation. Disadvantages of the Backup Method ■ You cannot change the name of the database schema.com/ installnw70 Installation – SAP NetWeaver Systems In an ABAP system. you must follow the additional instructions in SAP Note 628156. the complete restore must be repeated. Advantages of the Backup Method ■ You can use existing online and offline backups.ibm. Before starting SAPinst on the target system make sure that all prerequisites for the SAP system installation are met. If you want to use the backup/restore method between different platforms. The name of the database schema will be the same as that of the source system.htm. For more information about cross-platform backups. see the appropriate installation guide at http://service. UNIX. For more information. also see Backup and restore operations between different operating systems and hardware platforms in the IBM DB2 V9. 2011-03-07 PUBLIC 69/116 . Especially. and Windows. section db2inidb Option: as snapshot.sap.com/infocenter/db2luw/v9/topic/com.5 5. You can only copy the complete system. The database relocation procedure differs significantly from the backup/restore procedure and is not described in this guide. ■ Using the backup method is faster than the database-independent method [page 21]. An SAP system copy with a DB2 database can be also created if more advanced techniques like file system snapshots are available.ibm. NOTE With DB2. this method is not limited to the homogenous system copy only.udb.admin. This implies that the name of the database connect user does not change either.boulder.

admin. and Windows-Specific Procedures Process 1. Restore your database. As a prerequisite. a roll forward of your database is required after the database restore on the target system.db2.ibm.4 Database-Specific System Copy IBM DB2 for Linux. see Enabling database partitioning in a database in the IBM DB2 V9. For more information.5 5. If you use an online backup to copy your 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. You perform an online or offline backup. 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. see the IBM DB2 documentation DB2 Command Reference. Note that as of DB2 V9. ■ The tablespace names remain the same during the database restore. For more information. To restore your database. CAUTION 3. you have to adapt the DB2 container paths or names in the redirected restore script and then perform a redirected restore. use the DB2 RESTORE command.boulder.1 Information Center at http://publib. However. UNIX. To create a target system.5. the target system must have the same number of partitions as the source system. For more information.htm 4. the respective database logs must be accessible.ibm. To do so. use the INCLUDE LOGS option of the BACKUP DATABASE command. you can choose between one of the following options: ■ Simple database restore To perform a database restore. SAPinst prompts you to perform the database restore during the installation phase.com/ infocenter/db2luw/v9/topic/com. Multi-Partition Database Environments only: Add database partitions If you copy a system with multiple database partitions.udb. you can change them after the installation. section Usage of Tool brdb6brt. UNIX. We therefore recommend that you include the necessary log files in the backup image. you cannot change the connect user either. and Windows Target System Installation <system variant> <technical stack> Perform the installation options in the given sequence and follow the instructions on the SAPinst dialogs.doc/doc/t0004896. logs are by default included in an online backup. ■ If you want to change the name or the location of the DB2 container on the target system. 70/116 PUBLIC 2011-03-07 . see the documentation Database Administration Guide: SAP on IBM DB2 Universal Database for UNIX and Windows. Be aware of the following constraints when using the backup method for a homogeneous system copy: ■ Since you cannot change the name of the database schema. NOTE 2.

You also have to perform a roll forward operation to bring the database into a consistent state. you can use the tool brdb6brt that retrieves a database backup and creates a CLP script to restore this backup image. use the following commands: ■ For table TSDB6.ibm.htm. For more information. To rename all tablespaces in the respective tables according to the standard naming conventions. see RESTORE DATABASE command in the IBM DB2 V9. see Redirected Restore Using brdb6brt in the Database Administration Guide: SAP on IBM DB2 Universal Database for UNIX and Windows. A redirected restore allows you to change the name or the location of the DB2 container.admin. you have to update the tablespace names in tables TSDB6. Since brdb6brt needs to connect to the source system.doc/doc/r0001976. IADB6. we recommend that you consider renaming the tablespaces after the installation to reflect the new system name.udb.boulder. Alternatively. 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. To rename a single tablespace. ■ Redirected restore This is the recommended method.com/infocenter/db2luw/ v9/topic/com. You can now continue with the installation.ibm.1 Information Center at https://publib. you use the DB2 RESTORE DATABASE command with the REDIRECT GENERATE SCRIPT option. the source system must be available.db2.4 Database-Specific System Copy IBM DB2 for Linux. With a simple restore. For more information about how to use the tool brdb6brt. and TADB6.5 5. CAUTION Make sure that you use an up-to-date version of the db6util tool. you also have to execute the following command for each renamed tablespace using the db6util tool: db6util -rtvt <old tbs> <new tbs> For more information. you cannot change the name or the location of DB2 containers. To adhere to the SAP standard naming conventions for tablespaces. You require at least a version that supports the option -rtvt. UNIX. enter the following command: db6util –h In addition. To check the command options of the db6util tool. enter the following SQL command: 2011-03-07 PUBLIC 71/116 . see SAP Note 1227165. enter the following command: db2 rename tablespace <old name> to <new name> EXAMPLE db2 rename tablespace <SAPSID_SOURCE>#STABD to <SAPSID_TARGET>#STABD If you use the deferred table creation function. To perform a redirected restore. and Windows-Specific Procedures NOTE 5.

5. enter the following SQL command: update <connect_user_name>. Log on to the database server of the target system as user db2<dbsid>.5.sql 3. Generate the DDL statements for the tablespaces of the system by entering the following command on the DB2 command line: db2look -d <DBSID> -l -o <filename>.indspace='<SAPSID_TARGET>#'||substr(indspace. OVERFLOWLOGPATH (DB).length(tabspace)-4). see SYSTOOLSPACE and SYSTOOLSTMPSPACE tablespaces in the IBM DB2 V9.4 Database-Specific System Copy IBM DB2 for Linux. enter the following SQL command: update <connect_user_name>. Drop both tablespaces by entering the following command: db2 drop tablespace SYSTOOLSPACE. FAILARCHPATH (DB) and MIRRORLOGPATH (DB) 72/116 PUBLIC 2011-03-07 .sql.boulder.com/infocenter/db2luw/v9/topic/ com. Specifically. We recommend that you drop and re-create these tablespaces in the target system as follows: 1.tadb6 set tabspace = '<SAPSID_TARGET>#'||substr (tabspace.htm.5 5.admin.ibm. and Windows-Specific Procedures update <connect_user_name>. check all settings of the database manager and database configuration parameters.ibm.tsdb6 set tabspace = '<SAPSID_TARGET>#'||substr (tabspace. SYSTOOLTMPSPACE Look up the CREATE TABLESPACE statements for SYSTOOLSPACE and SYSTOOLSTMPSPACE in <filename>. For more information.5.length(indspace)-4) ■ For table IADB6. NEWLOGPATH (DB).5.1 Information Center at http://publib. Execute both statements on the DB2 command line.udb. ■ If you performed a redirected restore. 5.length(tabspace)-4) ■ For table TADB6.iadb6 set tabspace = '<SAPSID_TARGET>#'||substr (tabspace. 4.doc/doc/c0023713. UNIX.db2. 2. you perform the following steps: ■ The tablespaces SYSTOOLSPACE and SYSTOOLSTMPSPACE are used by certain DB2 tools and SQL administrative routines to store historical and configuration information. make sure that the following configuration parameters point to the correct path: ● DIAGPATH (DBM) ● JDK_PATH (DBM) ● DFTDBPATH (DBM) ● Path to log files (DB) ● If set.length(tabspace)-4) Follow-up Activities After the installation on the target system.

boulder.ibm.5 IBM DB2 for i Procedure In an SAP system environment. UNIX. UNIX. 2011-03-07 PUBLIC 73/116 .com/irj/sdn/db6 SAP on DB2 for Linux. and Windows in the SAP Community Network at: https://www. you can create a homogeneous system copy of a DB2 database using the offline system copy method.wss?rs=71&uid=swg27009727 End of: IBM DB2 for Linux and UNIX and Windows | Only valid for: IBM DB2 for i5/OS | 5. see SAP Note 585277.com/irj/sdn/db6 SAP on DB2 for Linux.html ■ IBM Manuals for DB2 V9. CAUTION You can only copy for IBM DB2 for i.com/infocenter/db2luw/v9r5/ ■ IBM Manuals for DB2 V9.com/software/data/db2/udb/support/manualsv9. End of: IBM DB2 for i5/OS | 5.ibm.sdn.5 5. you can create a homogeneous system copy of a DB2 database using the SAV/RSTLIB system copy method. and Windows Knowledge Center Key Topics Administration ■ IBM DB2 V9.6 IBM DB2 for z/OS Specific Procedure In an SAP system environment.ibm.5 Information Center at: http://publib.ibm.com/support/docview.5 Database-Specific System Copy IBM DB2 for i Procedure More Information ■ Database Administration Guide: SAP on IBM DB2 for Linux. and Windows Knowledge Center Key Topics Administration ■ Database Administration Using the DBA Cockpit in the SAP Community Network at: https:// www. For more information. UNIX.5 at: http://www-1.sdn.html ■ IBM DB2 V9.com/software/data/db2/udb/support/manualsv9.1 at: http://www. Advantage of the Offline System Copy Method This method is faster than the database-independent method [page 21].sap.sap.1 Information Center at: http://www.

5 5. see the . The guide contains all the information necessary to carry out a system copy with DB2 tools.PDF file that is attached to SAP Note 680746.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure More Information For more information about this system copy procedure. 74/116 PUBLIC 2011-03-07 .

rhosts). Check the SAP parameters of the default and instance profiles. 5. 4. Check your UNIX shell files for special entries.netrc. 10.dba. Adapt non-SAP directories. monitoring tools. 6. Check operating system printers. 6.2. SAP ArchiveLink) if required.1 Performing Follow-Up Activities in the Source System Procedure 1. . Check operating system files (for example. RFC.1 Follow-Up Activities Performing Follow-Up Activities in the Source System 6 Follow-Up Activities To finish the system copy of your SAP system: ■ Perform follow-up activities in the source system [page 75] ■ Perform follow-up activities in the target system [page 75] 6.ora. archiving systems. 3. Adapt backup programs (for example BRBACKUP. 2. Adapt additional SAP software components (for example. job schedulers) if required. file systems. 2011-03-07 PUBLIC 75/116 . CPIC. Check crontab or AT jobs. . Using CCMS. Reschedule your canceled jobs: Tools CCMS Jobs Maintenance (SM37) .6 6. 8. Adapt the configuration files at operating system level to meet network and SAP requirements. NFS mounts. 9. if required. 7. 2.1 Performing Follow-Up Activities for ABAP Procedure Actions at Operating System Level 1. Adapt additional non-SAP software components (for example.2 Performing Follow-Up Activities in the Target System 6. Oracle: Adapt the database profiles init<SAPSID>. init<SAPSID>. and init<SAPSID>. BACKINT) if required. and so on. BRARCHIVE. adapt your operation mode timetable to the original status: Tools CCMS Configuration Operation mode calendar (SM63) . 11.sap.

DBSTATTORA. PAHI. DBSTAIHORA. 3. marking the field delete with forced mode: Tools ABAP Workbench ABAP Editor (transaction SE38). Oracle: Delete all entries from the following tables: DBSTATHORA. ALSYSTEMS. DBSNP. 3. Choose transaction STMS Overview Systems . 1. Delete canceled and finished jobs. 2. Run an installation check: Administration System administration Administration Installation Check (transaction SM28). If the parameter does not exist on your system. 2. SDBAR. OSMON. Copy the old jobs. For more information. Execute ABAP program RSBTCDEL. Before starting the SAP system. 2. If you did not change the SAPSID during the system copy. we recommend that you adapt the global_name parameter by using the following SQL command: alter database rename global_name to <NEW_DBSID>. Adapt all jobs needed in the target system: 1.2 Follow-Up Activities Performing Follow-Up Activities in the Target System Actions at Database Level 1. 6. 5. 5. Check the parameters in the database profiles. Modify the new jobs. see SAP Note 16875. Adapt the transport parameters and transport routes in the Transport Management System (TMS): a.6 6. Configure the Transport Management System (transaction STMS). ignore this step. 3. 4. Oracle: If you changed the <DBSID> during the system copy. Select the system and select the Transporttool tab page. SDBAH. Delete all entries from the following tables: ALCONSEG. DBSTATIORA. 7. SDBAP. Actions at SAP System Level 1. To adapt the transport routes: Choose transaction STMS Overview Transport routes . 8. all open transport. 2. and customizing requests that have not been released in the source system will not be released automatically. MONI. Delete the old jobs. repair. Oracle: Delete the user OPS$<SOURCE_SAPSID>ADM. 4. Adapt the definition of the printers to meet the new system requirements: ■ Device types and character set definitions 76/116 PUBLIC 2011-03-07 . 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). make sure that the logging mechanism of the database is active. SDBAD.

Maintain the time table using the new operation modes. Run transaction SE14 to delete all entries from tables TPFET and TPFHT. see SAP Note 816861. 19. Adapt the RFC destination: Tools Administration Administration Network RFC destinations (transaction SM59). Also revise the authorizations of the system users. 10. 3. For more information. These contain information about changes made to the profile of your source system. ■ Spool servers ■ Output management systems (OMS) Delete entries in table DDLOG for buffer synchronization. Clean the transactional RFC: Tools Administration Monitor Transactional RFC (transaction SM58). IBM DB2 i: Use the commands CLRPFM R3<SID>DATA/TPFET and CLRPFM R3<SID>DATA/TPFHT. 18. Delete the old operation modes and old instance definitions. 17. Make data archived in the source system (data that does not reside in the database but was moved to a different storage location using SAP Archive Management) accessible in the target system. see the relevant description in the SAP Online Documentation. Adapt the instances and profiles (CCMS): Administration CCMS Configuration OP modes/ instances (transaction RZ04). 24. which holds the repair requests from your source system. 12. Check logon groups and assignment of application servers to logon groups (transaction SMLG). If you have performed a system copy with R3load. alert thresholds. Define or remove the SAP system users: Tools Administration User maintenance Users (transaction SU01). Create new operation modes and instance definitions. 23. 2011-03-07 PUBLIC 77/116 . Adapt the operation mode time tables (CCMS): Administration CCMS Configuration Operation mode calendar (transaction SM63). see the SAP Online Documentation (SAP Web Application Server System Administration Application Data Archiving and Reorganization) .2 Follow-Up Activities Performing Follow-Up Activities in the Target System 9. Delete all entries from table TLOCK. update statistics. Adapt the file residence information in the target system. Synchronize the buffers as described in SAP Note 36283 and adapt the client information for the logical system. 22. 13. 21. 11. For more information. reorganization parameters of CCMS table MONI) if required. Redefine database actions (backup. 25.6 6. 15. If you find erroneous entries with message text Systemdependent data for entry … changed. Start transaction SECSTORE using Check Entries. Create new operation modes and remove old ones: 1. Adapt other CCMS settings (for example. 16. Check the connection to SAPNet . and so on) if you have used the DBA calendar in the source system (transaction DB13). 2.R/3 Frontend (transaction OSS1). 14. you must set up the trusted and trusting RFC relationships again. 20.

Load generation requires a large amount of system resources. For more information. For a detailed description of the features. Follow your corporate naming strategy for logical systems when making this change. 33.6 6. you have to start program RS_BW_POST_MIGRATION in the background with variant SAP&POSTMGRDB. Post-processing for customer objects: If customer objects are not original in the new system. see Preparations [page 15]. 31. Check the logical system names. Therefore. you can use transaction SGEN to generate the missing loads. The ABAP loads are generated in the target system when they are first used. If you changed the database management system (for example. 30. Check the contexts and segments of remote application servers for the SAP Monitoring Infrastructure if required (transaction RZ21).2 Follow-Up Activities Performing Follow-Up Activities in the Target System 26. 32. read SAP Note 325525. To avoid this. 35. see the online documentation in transaction SGEN by choosing Information on the SAP Load Generator. however. If you need to change logical system names in the system that results from the copy. or in the Job Monitor by choosing Job Monitor. ABAP Program Loads The ABAP loads are platform-dependent programs that are generated during runtime and stored in database tables. Configure the domain controller in the Transport Management System (TMS) by using transaction STMS. For every client in your SAP system check the detail settings (client role. 34. If you encounter problems modifying a customer development class using transaction SMTS or SM31. changes for client-independent objects. you have to start program RS_BW_POST_MIGRATION in the background by using variant 78/116 PUBLIC 2011-03-07 . restrictions) (transaction SCC4). 27. Check self-defined external commands (transaction SM69). reduce production system performance. modify the corresponding entries in table TADIR. 29. change the logical system names at this time. This might. try using the option Validate (ENTER) instead of the option Save to save your changes. as described in SAP Notes 103228 and 544509. If you did not change the database management system when copying the system. BI customers: If you have copied a BI (formerly BW) system. it makes sense to schedule the generation job to run overnight. protection level. IBM i to MaxDB) when copying the system. Check if you can delete clients that will no longer be used in the target system (transaction SCC5). Check entries of the following tables in all relevant systems: ■ TXCOM (transaction SM54) ■ THOST (transaction SM55) 28. They are not exported when you use the R3load procedure to copy your SAP system. changes and transports for client-dependent objects.

NOTE You are required to perform the step independent of whether your target system is a BI or not. Proceed as follows: 1. 3. 2. Replacing the PSEs in the Target System Replace all existing PSEs in the target systems with new ones. The naming conventions are usually specified by the Certification Authority (CA) where you obtain the certificate. 2. ■ Note the naming conventions to use for each PSE. RAGITT01 (asset history sheet). Proceed as described in the documentation Creating or Replacing a PSE in the SAP Library at: http://help. 7. Checking the Target System The following actions are suitable for checking the consistency of the target system: 1. CO customers: Run the report group 1SIP and compare the results to those gained on the source system before the system copy. Check the system log on all application servers (transaction SM21). 8.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security System Security System Security for SAP NetWeaver AS ABAP only Trust Manager . 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 ). however. the type of PSE also has some restrictions. also import all necessary trusted certificates into the new PSE's certificate list. RAZUGA01 (asset acquisitions).com/nw70 SAP NetWeaver 7. FI customers: Run the jobs RFUMSV00 (tax on sales/purchases). for the SSL server PSE. call transaction STRUST. for example. (Check the old PSE's certificate list. Check the consistency of the database (transaction DB02). Test transactions frequently used by the customer.2 Follow-Up Activities Performing Follow-Up Activities in the Target System SAP&POSTMGR. NOTE ■ Since replacing a PSE will remove all of the previously used certificates. ■ Make sure the new PSE contains the new system ID.) Also distribute the new PSE's public-key certificate to the systems where it will be used.6 6.sap. 4. the CN 2011-03-07 PUBLIC 79/116 . Perform server check (transaction SM51). which contain the new system's information. Perform initial consistency check (transaction SM28). 6. 5. In your ABAP system. Program RS_BW_POST_MIGRATION performs necessary modifications on databasespecific objects (mainly BI objects). andRAABGA01 (fixed asset retirements) and compare the results to those gained on the source system before the system copy.

2 Follow-Up Activities Performing Follow-Up Activities in the Target System part of the Distinguished Name must be the host name used to access the server.6 6.40 | 1. For the system PSE. 2. Choose Checks/Settings Correct Jobheads Modify the necessary data. make sure that the Distinguished Name used for the PSE conforms with the naming convention that applies. In order to complete the homogeneous system copy.0 SP 12 or above to use this function. the CCMS jobhead still points to the former database SSID.2 Performing Jobhead Correction after Homogeneous System Copy NOTE This section is only relevant for customers using CCMS to monitor their SAP system(s). 2. the SSID needs to be set to the target system. End of: SAP Web AS 6.2.0.0.0 | Prerequisites You must have SAP NetWeaver 7. Choose Configuration Homogeneous System Copy: Jobhead Correction Modify the necessary data. 6. 3.0 | Procedure To set the SSID to the target system: Only valid for: SAP NetWeaver 7. 3. Call transaction DB2. Call transaction DBACOCKPIT. End of: SAP NetWeaver 7. Therefore. End of: SAP NetWeaver 7. Only valid for: SAP NetWeaver 7. After copying your system.SAP NetWeaver 7.40 | 80/116 PUBLIC 2011-03-07 . CAUTION Only experienced users should use this utility.1 | 1.1 | Only valid for: SAP Web AS 6. we recommend using the SID as the CN part.SAP NetWeaver 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.1 or higher ■ The JAVA_HOME environment variable must point to the JRE directory. The Migration Monitor ■ creates R3load command files. Prerequisites ■ JRE version 1. the Migration Monitor is integrated into the SAPinst system copy tool.7 7. For more information. ■ starts R3load processes to load the data as soon as a package is available. CAUTION If you want to convert a non-Unicode system to a Unicode using the socket option. see SAP Note 1238351. ■ creates R3load task files if required. ■ starts R3load processes to unload the data.1 Configuration Help The tool displays all parameters available if you call it with one of the following options: ■ ■ -help -? 2011-03-07 PUBLIC 81/116 . ■ The correct directory structure for R3load dump files must exist on both the source and target hosts. The Migration Monitor has to be started on the source database host (export monitor) and on the target database host (import monitor).1.1 Additional Information R3load Procedures Using the Migration Monitor 7 Additional Information 7. you need an R3load version with a specific patch level. but you can also use the Migration Monitor to copy previous releases by starting it manually.4. ■ transfers packages from the source to the target host if required. As of SAP NetWeaver 04 SR1. ■ informs the person performing the system copy in the case of errors. 7.

3 (info). off. 82/116 PUBLIC 2011-03-07 . 1 (error).6. You should use this mode if you have to specify passwords on the command line. default). If you run the Migration Monitor without using the installation tools. passwords) will be hidden for the Java process. 5. command line parameters (for example. the monitor thread sleeps and does not analyze any files or its processing state. The default timeout value is 30 seconds.”or blanks. If the tool is running in background mode. 2 (warning). Enables secure mode Takes effect only as command line option.1 Additional Information R3load Procedures Using the Migration Monitor Version The tool displays the version information (release branch and build date) if you call it with the following option: ■ -version General Options Name monitorTimeout Description Comments Monitor timeout in seconds During a timeout. 4 (config. mailFrom mailTo Additional Options Name bg Description Comments secure trace Enables background mode Takes effect only as command line option. Secure mode implicitly enables background mode. If the tool is running in secure mode. E-Mail Options Name mailServer Description Comments SMTP server “From” e-mail address “To” e-mail address Server name or IP address of the company SMTP server.7 7. then the installation directory is the directory where the R3load TSK and log files will be written. Can contain an address list separated by “. the UNIX shell window or Windows command prompt can be closed after startup. R3SETUP) is started. Trace level Possible values: all.7 (trace) Export Options Option installDir Description Comments Installation directory Directory where the installation tool (SAPinst.

4103. The value can be changed dynamically at runtime.7 7. Possible values: 4102. datacodepage. then the DDL control file from the export DB subdirectory is used. orderBy Package order Can be the name or path of the file that contains package names.1 Option Additional Information R3load Procedures Using the Migration Monitor Description Comments Separator on Windows: “. server Server operating Running in server mode means that the Migration mode Monitor creates R3load TSK files (if necessary). -p. Up to and including version 4. If you want to run the Export Monitor in the server mode. The default is DDL<DBTYPE>. dataCodepage Code page for data files See SAP Note 552464. -l. Appended to the R3load command line. as of version 4. tskFiles yes to create task files. -socket (if the socket option is specified) Any positive number.7 set to yes. DB.TSK already exist then the monitor will not overwrite them.TPL. ddlMap DDL mapping file File with mapping between DDL files and package names. Options already set by the monitor: -ctf. default is R3load. exportDirs 1100 taskArgs List of export directories loadArgs Additional R3load arguments for the TASK phase Additional R3load arguments for the LOAD phase Number of parallel export jobs. If only the name of the executable R3load executable is available. r3loadExe Path of the R3load Optional.6 . -l expJobNum Appended to the R3load command line. and DB/<TARGET_DBTYPE> (for example. Options already set by the monitor: -e. the subdirectories DATA. client Client operating Running in client mode means that the Migration mode Monitor runs parallel to the standard SAPinst export process and transfers the exported dump files to the import server.” Separator on UNIX: “:” The exportDirs parameter points to the directory to which the R3load dump files will be written. The Import Monitor always runs in the server mode. then JVM looks for the R3load executable using OS-specific process search rules. If the R3load task files *. 2011-03-07 PUBLIC 83/116 . In the exportDirs directory. the default is 1. If the file name is used without a path. If the option value is omitted then package order is not determined. specify the server parameter in the Export Monitor's properties file. ddlFile DDL control file Path or file name of DDL control file. All options below are for the server mode. R3load cmd files. DB/ORA) must exist. and starts the R3load processes. 0 for an unlimited number of jobs. -r. this must be set to no to skip no.

This is the directory on the target host to which the dump will be transferred. CAUTION ftpPassword Password of the remote FTP user Security risk! For more information.” and “:” separators are valid.1 Additional Information R3load Procedures Using the Migration Monitor Network Exchange Options Option net Description Comments Network operating mode Network exchange directory netExchangeDir Exported dump files must be visible on the import host to use this mode. The export monitor writes a file <package>. The value will be the same as for importDirs in the import monitors property file. Name or IP address of the import server. Used for communication between the export and import monitors. see the secure parameter in section Additional Options Both “. Must be writable for the export monitor and readable for the import monitor. Used for communication between the export and import monitors.7 7. Must be writable for the export ftpExportDirs List of remote FTP directories for export dump ftpExchangeDir Remote FTP exchange directory 84/116 PUBLIC 2011-03-07 . The FTP user specified here should be <sapsid>adm to make sure that the package files can be read during the import (which is started as <sapsid>adm).SGN to the network exchange directory as a signal to the import monitor that the package has been exported successfully and that the import can be started. CAUTION Clean up the netExchangeDir before starting a new export! FTP Exchange Options Option ftp Description Comments FTP operating mode ftpHost Remote FTP host Name of the remote FTP user ftpUser Exported dump files will be transferred automatically from the source host (directory exportDirs) to the target host (directory importDirs) using FTP.

The export monitor writes a file <package>. but the export and import work through the socket connection. The value can be changed dynamically at runtime.SGN to the FTP exchange directory as a signal to the import monitor that the package has been exported successfully and that the import can be started. Any positive number.1 Option Additional Information R3load Procedures Using the Migration Monitor Description Comments ftpJobNum Number of parallel FTP jobs.7 7. 0 for an unlimited number of jobs.TPL files in the subdirectory DB. DB/ ORA) must exist. Name or IP address of the import host.” Separator on UNIX: “:” In the exportDirs directory. 2011-03-07 PUBLIC 85/116 . Any free port on the import host from 1024 to 65535. All files produced by R3lctl and R3szchk will be transferred from the source to the target host using FTP. Must be the same as the port number on the import host. and the R3load EXT files (if required) in the subdirectory DB/<TARGET_DBTYPE>. the subdirectories DATA. the default is 1. FTP Copy Options Option ftpCopy Description Command FTP copy operating mode exportDirs List of export directories ftpHost Remote FTP host Used as a separate program call for migration with sockets if no share directory is used. Export Socket Host Option socket Description Comment Socket operating mode host Remote import host Host port number port R3load will not write dump files to the file system. and DB/ <TARGET_DBTYPE> (for example. The R3load STR files must exist in the subdirectory DATA. Separator on Windows: “. DB. monitor and readable for the import monitor. Name or IP address of the import server. the DDL*.

ftpExchangeDir NOTE The value of the dbType option is determined automatically in the shell script/batch files from the dbms_type environment variable. In the importDirs directory. one of the options ftp. the installation start directory is the directory where the R3load TSK and log files will be created.” Separator on UNIX: “:” The importDirs parameter points to the directory where the R3load dump files will be written.ftp net.ftpUser. When the Migration Monitor is used without the installation tools. exportDirs. exportDirs tskFiles. DB. CAUTION ftpPassword Password of the remote FTP user List of remote FTP directories for export dump ftpExportDirs Security risk! Both “. This is the directory on the target host to which the dump will be transferred. Any other option is ignored by the export monitor. one of the options . the subdirectories DATA.1 Option Additional Information R3load Procedures Using the Migration Monitor Description Command ftpUser Name of the remote FTP user The FTP user specified here must be <sapsid>adm to make sure that the package files can be read during the import (which is started as <sapsid>adm). ftpExportDirs. socket (and their related parameters) ■ FTP copy: exportDirs. The value will be the same as for importDirs in the import monitor's property file.” and “:” separators are valid. Mandatory Options for Export Monitor ■ Client mode: installDir. Import Options Option installDir Description Comment Installation directory importDirs The installation start directory is the directory in which the installation tools (SAPinst. R3SETUP) write their log files. 86/116 PUBLIC 2011-03-07 . ftpHost.7 7. List of import directories Separator on Windows: “. net (and their related parameters) ■ Server mode: installDir.

all export dump files are available on the import host before the import monitor is started. If only the name of the executable R3load executable is available. Values can be: name: load packages in alphabetical order. 4103. -o (if the omit argument is specified). arguments for the TASK Options already set by the monitor: phase -ctf. do not create indexes V: omit views. DB/ORA) must exist.7 7. list these options without blanks (for example. If the R3load task files *. Package order This option is used only if the import monitor works without the export monitor in stand-alone mode. or a path of the file that contains package names. Additional R3load Appended to the R3load command line. yes to include EXT files. Possible values: 4102. do not create primary keys I: omit indexes. this must be set to no to skip no. D: omit data. -socket (if the socket option is specified). it must be set to yes. The default is DDL<DBTYPE>. -l. yes to create task files. V. -r. default is R3load. do not create views If you want to combine several omit options. -o=TV). -l.1 Option Additional Information R3load Procedures Using the Migration Monitor Description Comment orderBy ddlFile ddlMap r3loadExe tskFiles extFiles dbCodepage migrationKey omit taskArgs loadArgs and DB/<TARGET_DBTYPE> (for example. Migration key R3load omit value Can contain only the letters D. the package processing is aborted. as of version 4.TPL. -o (if the omit argument is 2011-03-07 PUBLIC 87/116 .TSK already exist.6. do not load data T: omit tables. T. that is. I. DDL mapping file File with mapping between DDL files and package names. Up to and including version 4. then the DDL control file from the export DB subdirectory is used. If the option is omitted then package order is not defined. Path of the R3load Optional. DDL control file Path or file name of DDL control file. Database code page for See SAP Note 552464. do not create tables P: omit primary keys. -p. arguments for the LOAD Options already used by the monitor: phase -i. the target database 1100. If the EXT files cannot no to skip them be found in the DB/<TARGET_DBTYPE> import dump subdirectory. -dbcodepage. Add EXT file entries to cmd files. size: load packages starting with the largest one. Additional R3load Appended to the R3load command line. then JVM looks for the R3load executable using OS-specific process search rules. If the file name is used without path. -k. P. then the monitor will not overwrite them.7.

the default jobs. extFiles. Mandatory Options for Import Monitor ■ Server mode (default): installDir.1 Option Additional Information R3load Procedures Using the Migration Monitor Description Comment impJobNum specified and task files are not used. one of the options exchangeDir or socket (and their related parameters) ■ Stand-alone mode: installDir.2 Assigning DDL Files to Packages It is possible to use several different DDL*. from a previous export run). importDirs. importDirs. remove this file. Any other option is ignored by the import monitor. The assignment of a specific DDL file to a single package is done within a simple text file. If there is an old file export_statistics. the value of tskFiles option is no). is 1. Import Exchange Options Option exchangeDir Description Comment Exchange directory If this option is not set. The value can be changed dynamically at runtime. extFiles NOTE The value of the dbType option is determined automatically in the shell script/batch files from the dbms_type environment variable.7 7. 7. that is.1. in the properties file). without the export monitor. tskFiles. Number of parallel Any positive number. Import Socket Options Option socket port Description Command Socket operating mode Server port number Any free port from 1024 to 65535.TPL templates during the export or import. 0 for an unlimited number of import jobs. which then has to be specified 88/116 PUBLIC 2011-03-07 . tskFiles. that is. 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.properties (for example. then the monitor runs in stand-alone mode.

All packages without a package group will be assigned to a “default group” with the number of jobs that was defined in the Migration Monitor's properties file.7 7. you can specify different values for the parameters jobNum and taskArgs or loadArgs for each package. Package groups can be defined in the same text file in which the package order can be defined (see parameter orderBy). the maximum number of parallel R3load jobs is the sum of jobNum of all packages. By defining groups. Packages not listed in the DDL mapping file use the default DDL control file. Procedure Example of a DDL mapping file: # DDL mapping file ddl_mapping.txt # !!! line with [GROUP_NAME] can be skipped # used for documentation purposes only [ SORTED UNLOAD ] # DDL file for sorted unload ddlFile = /export_dump/ABAP/DB/ORA/DDLORA. In addition. you can prevent certain packages being executed in parallel and you can define how many large tables are exported or imported at the same time. The previous package order format is also fully supported. If package groups are defined.TPL # package names SAPAPPL0 SAPAPPL1 SAPSDIC [ UNSORTED UNLOAD ] DDL file for unsorted unload ddlFile = .TPL # table names TABLE_A TABLE_B TABLE_C 7. Procedure Example of a package order file with group: # custom package order 2011-03-07 PUBLIC 89/116 . A group starts with any arbitrary name in brackets and ends when the next group starts./DDLORA_LRG.3 Defining Groups of Packages The “package group” feature is an enhancement to defining a package order.1 Additional Information R3load Procedures Using the Migration Monitor using the ddlMap option within the migration monitor's properties file.1.

4 Processing Split Tables If tables have been split during the export.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 90/116 PUBLIC 2011-03-07 . These tasks will automatically be synchronized by the Migration Monitor. UNIX. You now want to run a maximum of 10 R3load processes for parallel data import. WHR files are part of the package and have to be copied to the DATA export subdirectory to make sure that the same WHR file is used for the export and import of the corresponding package. Procedure Example: Target Database Does Not Support Parallel Data Import During the export you have split the table MY_FIRST_TABLE into 3 packages and MY_SECOND_TABLE into 5 packages.1 Additional Information R3load Procedures Using the Migration Monitor # package names SAPAPPL0 SAPAPPL1 SAPAPPL2 # package group [ SEQUENTIAL GROUP ] jobNum = 1 # table names TABLE_A TABLE_B TABLE_C 7. Create the file inputFile. The following database platforms do not support parallel data import: ■ IBM DB2 for Linux.7 7. and Windows ■ MS SQL You can ensure this by using the Defining Groups of Packages [page 89] feature.1. ensure before the import starts that the table exists and that the primary key and the indexes are created before or after (as defined in the DDL template) the table data has been imported.

you can also define the processing order of packages or you can assign DDL files to packages.TSK). Manually delete all rows of the table for which the import of one or more packages failed.1.properties file has to be set to 8 to ensure that no more than 10 R3load processes run in parallel. Eliminate the reason for the failure of the import of the packages. the parameter jobNum in the import_monitor_cmd. 7.7 7. Adapt the file import_state. Restart the import. 5.properties in the installation directory. Do not remove the TSK files that create either the table or the indexes for this table. therefore it is faster to delete all rows of the corresponding table manually and reimport all packages instead.bat / End of: Windows | 2011-03-07 PUBLIC 91/116 .bat / import_monitor. Remove the TSK files of all packages that import data into this table (<table name><counter>__TPI. An R3load job is started for every group (MY_FIRST_TABLE and MY_SECOND_TABLE).txt file has to be specified as a value for the Migration Monitor parameter orderBy. The deletion with a WHERE clause can be very time consuming. Restart for all other database platforms: 1. Re-Starting the Import of a Split Table Package If the import of a package fails. 2.sh / End of: UNIX | ■ Only valid for: Windows | The Windows batch files export_monitor. 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. 4.1 Additional Information R3load Procedures Using the Migration Monitor MY_SECOND_TABLE-3 MY_SECOND_TABLE-4 MY_SECOND_TABLE-5 In this file. Replace the status “+” of all packages for the corresponding table that had been imported successfully and has to be reimported by “0” (see Restarting R3load Processes [page 47]).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. In this example. 3. the rows that belong to this package have to be deleted using the WHERE condition assigned to this package before the data import is started again. The inputFile.

bat –socket End of: Windows | If FTP access is used and security is required.bat –net export_monitor. 3. To specify an option: ■ In the command line: Enter -optionName optionValue./export_monitor.properties. The names of the property files are export_monitor_cmd. Check that the environment variable PASE_THREAD_ATTACH is set to “Y”: WRKENVVAR PASE_THREAD_ATTACH='Y' 2.sh –socket –host <import server> –port 5000 End of: UNIX | Only valid for: Windows | EXAMPLE export_monitor. Templates for these files are included in the application archive and must be located in the current user's working directory. ■ In the application property file: Insert the new line optionName=optionValue. 92/116 PUBLIC 2011-03-07 . Set the JAVA_HOME environment as follows: If you are using the IBM Classic JVM: export JAVA_HOME=/QIBM/ProdData/Java400/jdk14 or If you are using the JDK IBM Technology for Java (IT4J): export JAVA_HOME=/QOpenSys/QIBM/ProdData/JavaVM/jdk14/64bit 4. Options are case-sensitive: Any options that are not recognized are ignored.sh / import_monitor./export_monitor. Only valid for: UNIX | EXAMPLE ./export_monitor.1 Additional Information R3load Procedures Using the Migration Monitor Only valid for: IBM i5/OS | ■ IBM i-specific 1.sh –ftp .sh End of: IBM i5/OS | You can specify options in the command line or in the export or import property files. export_monitor.7 7. start the monitor in secure mode to prevent seeing the FTP password in the command line parameter string or in the property file. Run the command call qp2term.sh –ftpCopy .properties and import_monitor_cmd. Any options specified in the command line take precedence over the corresponding options in the application property file.

separator on Windows ./export_monitor_secure. The monitor process runs in the background. 2.log files to check the monitor processing state.console. 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.properties file with export options: # Export Monitor options # Operating mode: ftp | net #net ftp # # Common options # # List of export directories. ftpExportDirs=/install_dir/export_dump 2011-03-07 PUBLIC 93/116 .sh –ftpPassword <password> End of: UNIX | Procedure 1. EXAMPLE export_monitor_cmd.7 7. Use monitor *. Start the monitor and close the shell window or command processor. separator : or .1 Additional Information R3load Procedures Using the Migration Monitor Only valid for: UNIX | EXAMPLE .log and *.

de # "From" email address mailFrom=mail@sap.com EXAMPLE import_monitor_cmd.com mail@yahoo.1 Additional Information R3load Procedures Using the Migration Monitor # Remote FTP exchange directory ftpExchangeDir=/install_dir/exchange # Number of parallel FTP jobs ftpJobNum=3 # # E-mail options # # SMTP server mailServer=sap-ag.com # "To" email address mailTo=mail@sap. separator on Windows .properties file with import options: # Import Monitor options # # Common options # # List of import directories.7 7. 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 94/116 PUBLIC 2011-03-07 .

com mail@yahoo. and so on) to the target host (parameter: ftpHost) into the corresponding subdirectories of the directory /install_dir/export_dump (parameter: ftpExportDirs) as user <sapsid>adm (parameter: ftpUser). STR. the export monitor will write a <package>. identified by password (parameter: ftpPassword) to log on. ■ The R3load log files. and TSK files (if required) are located in the directory c:\install \start (parameter: installDir).1 Additional Information R3load Procedures Using the Migration Monitor 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. ■ If the package files have been completely transferred to the server. and the c:\temp \export_dump\DB\ORA directory the EXT files generated by R3szchk. as the monitor is started in client mode (parameter server is not set). The export itself is not done by the export monitor.de # "From" email address mailFrom=mail@sap. ■ The export monitor writes the R3load dump files and the TOC files to the directory c:\temp \export_dump\DATA.7 7. 001. 2011-03-07 PUBLIC 95/116 . EXT. ■ As soon as a package has been exported successfully. cmd files.TPL files generated by R3ldctl. the export monitor will transfer all files belonging to that package (TOC. the c: \temp\export_dump\DB directory the DDL<DBTYPE>.com What happens during export / import with the above listed property files during a system copy with Oracle as source and target database: ■ The following directories must exist on the export host (parameter: exportDirs): ● c:\temp\export_dump\DATA ● c:\temp\export_dump\DB ● c:\temp\export_dump\DB\ORA The c:\temp\export_dump\DATA directory must contain the STR files generated by R3ldctl.com # "To" email address mailTo=mail@sap.SGN signal file to the /install_dir/exchange (parameter: ftpExchangeDir) directory to notify the import monitor that it can start importing this package.

then the export state file may contain a second <STATE> column that refers to the state of the package transfer. Then the export state file contains package state lines such as SAPUSER=++. and TSK files (if required) will be located in the directory / install_dir/start (parameter: installDir). Possible values for state are: 0 ? Package export not yet started. 96/116 PUBLIC 2011-03-07 .SGN file is found in the /install_dir/exchange (parameter: exchangeDir) directory.log Import ■ import_monitor. If any ftp or net exchange options are used. cmd files. ■ The file DDLORA.log Both the export and import state files contain package state lines such as SAPUSER=+.console. ■ The R3load log files. Package export/import finished successfully.properties ExportMonitor.7 7. the /install_dir/export_dump/DB directory the files DDL<DBTYPE>.console.properties ■ ImportMonitor. Package export in progress.TPL also generated by R3ldctl.1. Package export/import finished with errors.log ■ import_state.1 Additional Information R3load Procedures Using the Migration Monitor ■ The following directories must exist on the import host (parameter: importDirs): ● /install_dir/export_dump/DATA ● /install_dir/export_dump/DB ● /install_dir/export_dump/DB/ORA The /install_dir/export_dump/DATA directory has to contain the STR files generated by R3ldctl. ■ The import monitor will start to import a package as soon as the <package>. Format of lines is <PACKAGE>=<STATE>.log export_state.TPL has to be copied to the directory /install_dir/start (parameter: installDir) before you start the import monitor.6 Output Files Export ■ ■ ■ export_monitor. Package export/import in progress. the /install_dir/export_dump/DB/ORA directory the EXT files generated by R3szchk. 7. Possible values for state are: 0 ? + Package export/import not yet started. Format of lines is <PACKAGE>=<STATE>.

7.7 7. When SAPinst displays the CD browser window and asks for the Export Migration CD. NOTE 5. Package transfer finished with errors.ASC ■ <dump dir>/DB/<DBTYPE>/DBSIZE. you can now start the data load by starting the import monitor.XML located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE> (Windows) or <EXPDIR>/DB/ <DATABASE> (UNIX). 2. copy the files from the source system to the target system as soon as they have been created on the source host using the (export) migration monitor's FTP copy options. To install the target system. 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.TPL If the dump directory is not shared on the target host. choose Standard System Copy/Migration (R3load-Based). Package transfer in progress. enter the path to the export directory <EXPDIR>. 6. 3.1 Additional Information R3load Procedures Using the Migration Monitor +0 +? +++ Package export finished with errors. Package transfer finished successfully. On this screen. Package export finished successfully.1. follow the instructions in the SAPinst input dialogs and enter the required parameters as far as the ABAP System > Database screen. Procedure 1. position the cursor on the field of the respective parameter and press F1. 2011-03-07 PUBLIC 97/116 . Select the Use Migration Monitor option.XML ■ <dump dir>/DB/DDLORA. Start SAPinst as described in the installation documentation for your SAP component. look at the file DBSIZE. If you need more information about input parameters. If you want to start the installation of the target host using the Migration Monitor. To find out the size of the export and the sizes of the tablespaces or dbspaces that are created. package transfer not yet started.7 Installing the Target System Using the Migration Monitor Prerequisites Make sure that there is enough free space on the target system for the database load. make sure that at least the dump directory with the following files is accessible on the target host and that it contains the correct data before you start SAPinst: ■ <dump dir>/LABEL. 4.

SAP Solution Manager.SAP SRM | NOTE If you need to log off during the installation from the host where you control the installation with SAPinst GUI.2 Additional Information Using SAPinst GUI 7. 7. but SAPinst and the GUI server continue running Only valid for: SAP CRM. the installation continues while you are logged off.2 Using SAPinst GUI The following table shows the most important functions that are available in SAPinst GUI: SAPinst GUI Functions Input Type Label F1 Description Function key Menu option File Exit Displays detailed information about each input parameter Stops the SAPinst GUI.SAP SCM.log) ■ Log files from the SAPinst GUI server Cancels the installation with the following options: ■ Stop Stops the installation (SAPinst GUI. If so.SAP NetWeaver. End of: SAP CRM. just restart SAPinst. For more information. and the GUI server) without further changing the installation files You can restart and continue the installation later from this point. The import is continued with the table that was not imported successfully. ■ Continue Continues the installation 98/116 PUBLIC 2011-03-07 .SAP Solution Manager. CAUTION If you have to restart the import after an error. SAPinst.SAP ERP.7 7.SAP SRM | Menu option SAPinst Log Browser Menu option SAPinst Cancel Displays the Log Viewer dialog This dialog enables you to access the following log files directly: ■ Installation log (sapinst_dev.SAP ERP. Check that the prerequisites in the dialog box are fulfilled by your system.SAP NetWeaver.SAP SCM. start the Migration Monitor. Complete the installation as described in the installation documentation for your SAP solution. see Starting SAPinst GUI Separately [page 105]. You can later reconnect to the same SAPinst installation from the same or another host. 8.

SAPinst continues the installation from the current point.3 Interrupted Installation with SAPinst The SAP system installation might be interrupted for one of the following reasons: ■ An error occurred during the Define Parameters or Execute phase: SAPinst does not abort the installation in error situations. Continues with the option you chose previously 7. try to solve the problem. The following table describes the options in the dialog box: Option Definition Retry Stop Continue View Log Only valid for: UNIX | SAPinst retries the installation from the point of failure without repeating any of the previous steps. SAPinst displays the same dialog box again. SAPinst stops the installation. Therefore. ■ You interrupted the installation by choosing Cancel in the SAPinst menu. SAPinst records the installation progress in the keydb. and the GUI server. and then choose Retry. the SAPinst GUI. This is possible because SAPinst records the installation progress in the keydb. we do not recommend that you use Ctrl + C . closing the dialog box. End of: UNIX | 2011-03-07 PUBLIC 99/116 . If an error occurs. Access installation log files. We recommend that you view the entries in the log files. If the same or a different error occurs. the installation pauses and a dialog box appears.xml file.xml file.7 7. because this kills the process immediately.3 Additional Information Interrupted Installation with SAPinst Label Description Input Type Message button Message button Retry Stop Message button Continue Performs the installation step again (if an error has occurred) Stops the installation without further changing the installation files You can continue the installation later from this point. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error. However. NOTE You can also terminate SAPinst by choosing Ctrl + C . you can continue the installation from the point of failure without repeating any of the previous steps (see the procedure below).

We do not recommend using Network File System (NFS). or any other number you have chosen for your TMKSVR instance). Only valid for: Unix | Mount your Installation Master DVD. Only valid for: Windows | Double-click sapinst. Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | Check the subsystem TMKSVR<nn> (nn=00. Only valid for: Windows | Insert the Installation Master DVD in your DVD drive. or to continue an interrupted installation after an error situation. End of: Windows | 4. End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | 100/116 PUBLIC 2011-03-07 .exe. you can continue with the step check if an SAPinst GUI Java process is still running. To do this. NOTE Mount the DVD locally.7 7. Only valid for: Windows | Change to the required directory using the following command: <DVD drive>:\IM_WINDOWS_<platform> End of: Windows | 6. Only valid for: UNIX | Log on to your local UNIX host as user root./sapinst End of: Unix | 8. CAUTION Make sure that the root user has not set any environment variables for a different SAP system or database. Only valid for: Windows | Log on as a user who is a member of the local administrators group. End of: Unix | 5. which you stopped by choosing Stop. Only valid for: IBM DB2 for i5/OS | 1. End of: Windows | 7. Only valid for: Unix | Start SAPinst using the following commands: cd <Installation_Master_DVD>/IM_<OS> . End of: UNIX | 3.3 Additional Information Interrupted Installation with SAPinst Procedure This procedure describes the steps to restart an installation. enter the following command: WRKACTJOB SBS(TMKSVR<nn>) NOTE If the TMKSVR<nn> subsystem is running. End of: Windows | 2.

even if these files and folders are owned by other users. log on as your installation user and enter the following commands: ■ ■ ADDLIBLE TMKSVR<nn> STRTMKSVR INSTNO<nn> NOTE Now the TMKSVR<nn> subsystem is running again and you can continue with the next step. 12. Afterwards. In the What do you want to do? screen. it moves the content of the old installation directory and all installationspecific files to a backup directory. To do this.3 Additional Information Interrupted Installation with SAPinst Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | 9.7 7. you must restart the subsystem manually.exe ■ If you used an alternative installation directory: cd <Mapped_Drive>:\<your installation directory> <Mapped_Drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64\sapinst.exe End of: IBM i5/OS | IBM DB2 for i5/OS | 11. If there are any 2011-03-07 PUBLIC 101/116 . Instead. End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | 10. The What do you want to do? screen appears. For the backup directory. From the tree structure in the Welcome screen. select the installation option that you want to continue and choose Next. If this subsystem is not running because for example of an IPL.exe under Processes in your Task Manager and kill it. decide between the following alternatives and confirm with OK: End of: IBM DB2 for i5/OS | Alternative Behavior Run a New Option SAPinst does not continue the interrupted installation option. NOTE If there is only 1 component to install. Only valid for: IBM i5/OS | IBM DB2 for i5/OS | Check if an SAPinst GUI Java process is still running. the Welcome screen does not appear. you can no longer continue the old installation option. ■ If you used the default installation directory (recommended): cd <Mapped_Drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64 sapinst. If a process is still running. look for javaw. the following naming convention is used: <log_day_month_year_hours_minutes_seconds>. EXAMPLE log_01_Oct_2008_13_47_56 CAUTION SAPinst moves all the files and folders to a new log directory.

and SAPinst GUI client runs on the local host. A remote installation 102/116 PUBLIC 2011-03-07 .1 Performing a Remote Installation with SAPinst You use this procedure to install your SAP system on a remote host. see: ■ Starting SAPinst on the Remote Host [page 102] ■ Starting SAPinst GUI Separately [page 105] 7. A local installation on IBM i means that the entire SAPinst (the SAPinst. In this case. 7. 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).7 7. they might no longer function properly. To test this: ● Log on to your remote host and enter the command ping <local host>. Start the SAPinst server on your remote host. 2.4 Performing a Remote Export Using SAPinst Purpose You can run the SAPinst GUI in standalone mode to perform a remote export. Prerequisites ■ You have performed the preparation activities for your local host (SAPinst GUI host) and your remote host as described in Prerequisites in Exporting the Source System Using SAPinst [page 31]. Only valid for: IBM i5/OS | NOTE For IBM i only in rare cases a remote installation is done. Perform the installation using the SAPinst GUI. Process Flow 1. For more information. Start the SAPinst GUI on your local host. SAPinst continues the interrupted installation option from the point of failure. 3. the SAPinst GUI server and SAPinst GUI client) is running on the same Windows PC to install an SAP system on IBM i using the TMKSVR. The GUI client connects using a secure SSL connection to the GUI server and the GUI server connects to SAPinst. ● Log on to the local host and enter the command ping <remote host>.4. The local host is the host from which you control the installation with the SAPinst GUI client. SAPinst and the SAPinst GUI server run on the remote host.4 Additional Information Performing a Remote Export Using SAPinst Behavior Alternative Continue with the Old Option processes currently running on these files and folders. ■ Both computers are in the same network and can ping each other.

2011-03-07 PUBLIC 103/116 . Log on to the local host (Windows PC) and enter the command ping <remote host>. which we use to validate installations with SAPinst. you only run the SAPinst GUI client.7 7. We recommend that you use the Hummingbird Exceed X Server. End of: UNIX. see SAP Note 1238121.Windows | Linux. Only valid for: IBM i5/OS | Log on to your remote host (IBM i) and enter the command PING RMTSYS('<local host>').Windows | Linux. On the local PC. SAP no longer delivers any JCE policy archives within the SAP Java Virtual Machine (SAP JVM). You have to download the required Java Cryptography Extension (JCE) policy zip file from SAP on the remote host. For more information.Windows | CAUTION The behavior of SAPinst.Windows | Only valid for: UNIX. End of: IBM i5/OS | 2.Windows | You can run the GUI client on a PC with 32-bit while SAPinst is running on a 64-bit installation host.Windows | 1. End of: IBM i5/OS | Only valid for: UNIX. Procedure Only valid for: IBM i5/OS. not the IBM i host. you are running the SAPinst and the SAPinst GUI server.4 Additional Information Performing a Remote Export Using SAPinst on IBM i means that two Windows PCs and one IBM i host are involved in the installation. GUI server and GUI client has changed compared to previous versions. To test this: 1. Log on to your remote host as a user that is a member of the local administrators group.Windows | Alternatively you can use an X server for Microsoft Windows or other remote desktop tools such as VNC Viewer or NX Server / NX Client – offered by various vendors or open source – for remote access to SAPinst GUI on Windows workstations. End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | Prerequisites ■ The remote host meets the prerequisites as described in Running SAPinst in your installation guide. located close to the IBM i host. ■ Both computers are in the same network and can ping each other. “local host” in this section refers to the Windows installation host. see SAP Note 1170809. Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | CAUTION If you install SAP instances on IBM i. On the remote PC. End of: UNIX. For more information.

Mount the Installation Master DVD. waiting for a connection on host <host_name>. 4.Oracle | cd <DVD drive>:\IM_WINDOWS_<platform> End of: IBM DB2 for Linux and UNIX and Windows. Make sure that the root user has not set any environment variables for a different SAP system or database. 3.No Database.7 7.No Database. You see the following at the command prompt: guiengine: no GUI connected.MaxDB.MS SQL Server. Change to the directory of the sapinst executable and start SAPinst without GUI using the following commands: 104/116 PUBLIC 2011-03-07 . Log on to your remote host as user root. Insert the Installation Master DVD in the DVD drive on your remote host. 4.MaxDB.MS SQL Server. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive as follows: Shell Used Command JCE_POLICY_ZIP=<policy zip archive> export JCE_POLICY_ZIP Bourne shell (sh) C shell (csh) Korn shell (ksh) setenv JCE_POLICY_ZIP <policy zip archive> export JCE_POLICY_ZIP=<policy zip archive> 5. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive by entering the following command: set JCE_POLICY_ZIP=<policy zip archive> 5. port <port_number> to continue with the installation 6.exe -nogui For more information about how to perform the export.Oracle | Only valid for: IBM i5/OS | IBM DB2 for i5/OS | cd <mapped drive>:\IM_OS400_PPC64 End of: IBM i5/OS | IBM DB2 for i5/OS | sapinst. Start the GUI client on your local host as described in Starting SAPinst GUI Separately [page 105].IBM DB2 for z/OS. CAUTION 2. Download the JCE policy zip file from SAP as described in SAP Note 1240081. SAPinst now starts and waits for the connection to the GUI client.4 Additional Information Performing a Remote Export Using SAPinst 2. see Exporting the Source System Using SAPinst [page 31]. Enter the following commands: Only valid for: IBM DB2 for Linux and UNIX and Windows. 3. Download the JCE policy zip file from SAP as described in SAP Note 1240081. End of: IBM i5/OS.Windows | Only valid for: UNIX | 1.IBM DB2 for z/OS.

Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 105]. For more information. 3. Log on as a member of the local administrators group.IBM DB2 for z/OS. You see the following at the command prompt: guiengine: no GUI connected. you can start SAPinst GUI separately. port <port_number> to continue with the installation.MaxDB. You have to download the required JCE policy zip file from SAP on the local host.7 7. If the GUI client runs on a different host from SAPinst and the GUI server. 5.Oracle | . ■ You want to perform a remote installation [page 102].4 Additional Information Performing a Remote Export Using SAPinst Only valid for: IBM DB2 for Linux and UNIX and Windows. see Exporting the Source System Using SAPinst [page 31]. SAPinst now starts and waits for the connection to the SAPinst GUI client. see SAP Note 1238121.MS SQL Server. waiting for a connection on host <host_name>.4. 6.2 Starting the SAPinst GUI Separately You use this procedure to start the SAPinst GUI client separately.No Database. Download the JCE policy zip file from SAP as described in SAP Note 1240081.MS SQL Server./sapinst -nogui For more information about how to perform the export.No Database. Insert the SAP Installation Master DVD into your DVD drive.Oracle | cd <mountpoint_of_Installation_Master_DVD>/IM_<OS> End of: IBM DB2 for Linux and UNIX and Windows.Windows | 7. If you logged off during the installation and you later want to reconnect to the installation while it is still running. End of: UNIX | Only valid for: IBM i5/OS. SAP no longer delivers any JCE policy archives within the SAP JVM. You might need to start the GUI client separately in the following cases: ■ You have logged off from SAPinst. CAUTION The behavior of SAPinst has changed compared to previous versions. Procedure Starting the GUI Client on Windows 1.MaxDB. you have to start the GUI client separately on the local host. Change to the directory of the sapinst executables: 2011-03-07 PUBLIC 105/116 . 2.IBM DB2 for z/OS.UNIX. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive by entering the following command: set JCE_POLICY_ZIP=<policy zip archive> 4.

Linux.IBM DB2 for i5/OS (Linux/Windows) | Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | NOTE If you have a share ROOTBIN on your IBM i and you have mapped this share to the drive X.Linux.IBM DB2 for i5/OS (Linux/Windows).Oracle | Only valid for: IBM DB2 for i5/OS. where <nr> is the port number for the connection to the GUI server ■ -accessible enables accessibility mode Example: sapinstgui host=lsi1209 port=3000 -accessible ■ -h displays a list of all available parameters End of: AIX. you can use the executable available in the DVD or change to the following directory: <Installation_Master_DVD>\IM_WINDOWS_I386 End of: IBM DB2 for i5/OS.IBM i5/OS.4 Additional Information Performing a Remote Export Using SAPinst Only valid for: IBM DB2 for i5/OS. If SAPinst and the GUI server are running on another host. the GUI client cannot connect and the SAP Installation GUI Connection dialog appears.MS SQL Server.HP-UX. change to the following directory: <Installation_Master_DVD>\IM_WINDOWS_I386 End of: IBM DB2 for Linux and UNIX and Windows.IBM DB2 for i5/OS (Linux/Windows) | NOTE If you want to start the GUI client on a Windows 32-bit operating system.MaxDB.No Database.IBM DB2 for Linux and UNIX and Windows.7 7.IBM DB2 for z/OS. you can start the SAPinst GUI using your copied Installation Master DVD: X:\tmp\<SID>\<Installation_Master_DVD>\IM_OS400_PPC_64 End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | 6.MaxDB.IBM DB2 for z/OS.IBM DB2 for z/ OS.IBM i5/OS.HP-UX.exe with the following parameters: ■ host=<host name>. NOTE Optionally you can start sapinstgui.Windows | Start the GUI client by double-clicking sapinstgui. The first screen of the installation appears and you can perform the remote installation from your local host.IBM DB2 for z/OS.IBM DB2 for i5/OS (Linux/Windows).exe The GUI client starts and tries to connect to the GUI server and SAPinst.No Database.MS SQL Server.Oracle | Only valid for: IBM DB2 for Linux and UNIX and Windows. In this case.Oracle | <DVD drive>:\IM_WINDOWS_<platform> End of: IBM DB2 for i5/OS. where <host name> is the host name of the installation host ■ port=<nr>.IBM DB2 for Linux and UNIX and Windows.MS SQL Server.MaxDB. Only valid for: AIX. using the local host as default.Oracle | NOTE If you want to start the GUI client on a Windows 32-bit operating system.Windows | 106/116 PUBLIC 2011-03-07 .MaxDB.MS SQL Server. enter the name of the host on which SAPinst is running and choose Log on.Solaris.Solaris.

Since SAPinst and the GUI server are running on another host. Log on as user root. 2011-03-07 PUBLIC 107/116 . Mount your Installation Master DVD. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive as follows: Shell Used Command JCE_POLICY_ZIP=<policy zip archive> export JCE_POLICY_ZIP Bourne shell (sh) C shell (csh) Korn shell (ksh) setenv JCE_POLICY_ZIP <policy zip archive> export JCE_POLICY_ZIP=<policy zip archive> 4. ■ If SAPinst and the GUI server runs on a different host from the GUI client (remote installation). CAUTION 2.bat -h End of: z/OS | Starting the GUI Client on UNIX 1. Start the GUI client in one of the following ways: ■ If the GUI client runs on the same host as SAPinst and the GUI server. change to the same directory as your SAPinst executable and enter the command: startinstgui. ● For a list of options to start the GUI client. the GUI cannot connect and the SAP Installation GUI Connection dialog appears. 3.bat SAPinst GUI uses the local host as default.4 Additional Information Performing a Remote Export Using SAPinst Only valid for: z/OS | 7. enter the following command: startinstgui. Make sure that the root user has not set any environment variables for a different SAP system or database. Download the JCE policy zip file from SAP as described in SAP Note 1240081. The first dialog of the installation appears and you can perform the remote installation from your local host. the GUI client uses the local host as default.7 7. The GUI client starts and tries to connect to the GUI server and SAPinst. enter the name of the host on which SAPinst is running and choose Log on. NOTE ● If you enter the command without additional parameters. In this case.bat -host <host_name> <host_name> is the host name of the installation host. enter the following command: startinstgui.

4 Additional Information Performing a Remote Export Using SAPinst NOTE 5. using the local host as default. Change to the directory of the sapinst executables: <mountpoint_of_Installation_Master_DVD>/IM_<OS> NOTE If you want to start the GUI client on a Linux 32–bit platform. NOTE Optionally.HP-UX. enter the following command with additional parameters: .IBM i5/OS.sh -host <host_name> <host_name> is the host name of the installation host NOTE ● If you enter the command without additional parameters.Linux. where <nr> is the port number for the connection to the GUI server ■ -accessible enables accessibility mode Example: . where <host name> is the host name of the installation host ■ port=<nr>. the GUI client uses the local host as default.IBM i5/OS./startInstGui. Only valid for: z/OS | Start the GUI client in one of the following ways: ■ If the GUI client runs on the same host as SAPinst and the GUI server./sapinstgui host=lsi1209 port=3000 -accessible ■ -h displays a list of all available parameters End of: AIX. The GUI client starts and tries to connect to the GUI server and 108/116 PUBLIC 2011-03-07 ./sapinstgui The GUI client starts and tries to connect to the GUI server and SAPinst.7 7./startInstGui.Solaris.Windows | 7. Mount the DVD locally. We do not recommend that you use Network File System (NFS). enter the name of the host on which SAPinst is running and choose Log on. If SAPinst and the GUI server are running on another host.Linux. In this case. you can start sapinstgui with the following parameters: ■ host=<host name>.sh By default. SAPinst GUI uses the local host.HP-UX. ■ If SAPinst and the GUI server run on a different host from the GUI client (remote installation). The first screen of the installation appears and you can perform the remote installation from your local host. enter the following command without additional parameters: .Solaris. Only valid for: AIX. change to the following directory: <mountpoint_of_Installation_Master_DVD>/IM_LINUX_I386 6.Windows | Start the GUI client by executing . SAPinst GUI cannot connect and the SAP Installation GUI Connection dialog appears.

In this case. ● For a list of options to start the GUI client.7 7. The first screen of the installation appears and you can perform the remote installation from your local host. change to the same directory as your SAPinst executable and enter the command: .UNIX.4 Additional Information Performing a Remote Export Using SAPinst SAPinst. the GUI client cannot connect and the SAP Installation GUI Connection dialog appears./startInstGui.Windows | 2011-03-07 PUBLIC 109/116 . Since SAPinst and the GUI server are running on another host.sh -h End of: z/OS | End of: IBM i5/OS. enter the name of host on which SAPinst is running and choose Log on.

These include report names. database table names.Typographic Conventions Example <Example> Description Example Example Example Example Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system. and key concepts of a programming language when they are surrounded by body text. names of variables and parameters. for example.sap. for example. for example. Arrows separating the parts of a navigation path. and database tools Technical names of system objects.com /example 123456 Example Example EXAMPLE EXAMPLE 110/116 PUBLIC 2011-03-07 . SAP Note 123456 ■ Words or characters quoted from the screen. for example. program names. menu names. and menu options. transaction codes. “Enter your <User Name>”. These include field labels. for example. and names of installation. SELECT and INCLUDE Keys on the keyboard http://www. menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note. messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths. ■ Cross-references to other documentation or published works ■ Output on the screen following a user action. upgrade. screen titles. pushbutton labels.

XHTML and W3C are trademarks or registered trademarks of W3C®.S. Redbooks. z/VM. Business Objects and the Business Objects logo. World Wide Web Consortium. AIX. POWER5+. System p5. System i5. Massachusetts Institute of Technology. PowerPC. BladeCenter. Xcelsius. Java is a registered trademark of Sun Microsystems. POWER5. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only. ByDesign. Netfinity.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. RACF. XML. DB2. Disclaimer Some components of this product are based on Java™. Citrix. System z. Data contained in this document serves informational purposes only. Sybase is an SAP company. HTML. R/3. RETAIN. and PowerPoint are registered trademarks of Microsoft Corporation. Power Architecture. System z10. iAnywhere. OpenPower. Acrobat. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. 2011-03-07 PUBLIC 111/116 . Nothing herein should be construed as constituting an additional warranty. MetaFrame. DB2 Connect. 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. Crystal Reports. MVS/ESA. The information contained herein may be changed without prior notice. and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Parallel Sysplex.com © Copyright 2011 SAP AG. S/390 Parallel Enterprise Server. Crystal Decisions. Microsoft. VideoFrame. AS/400. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.sap. ICA. if any. the Adobe logo. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited. IBM. Inc. z10. PartnerEdge. System i. DB2 Universal Database. i5/OS. POWER6+. Duet. z9. pSeries. PowerVM. BatchPipes. All rights reserved. SAP BusinessObjects Explorer. All other product and service names mentioned are the trademarks of their respective companies. zSeries. OSF/1. Web Intelligence. and MultiWin are trademarks or registered trademarks of Citrix Systems. and other countries. Inc. X/Open. These materials are subject to change without notice. WebSphere. in the United States and in other countries. as is any decompilation of these components. SAP NetWeaver. Program Neighborhood. Intelligent Miner. SQL Anywhere. SAP. System Storage. Inc. POWER6. JavaScript is a registered trademark of Sun Microsystems. OS/2. eServer. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. and Motif are registered trademarks of the Open Group. System p. S/390. WinFrame. and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase. 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. System x. HACMP. Adobe. and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. OS/400. Sybase and Adaptive Server. Excel. Inc.. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Sybase 365. and SAP Group shall not be liable for errors or omissions with respect to the materials. POWER. Oracle is a registered trademark of Oracle Corporation. z/OS. Windows. without representation or warranty of any kind. Linux is the registered trademark of Linus Torvalds in the U. OS/390. National product specifications may vary. System z9. PostScript. used under license for technology invented and implemented by Netscape. GPFS. UNIX. xSeries. iSeries. BusinessObjects. Outlook.

Legal Software Terms Terms for Included Open Source Software This SAP software contains also the third party open source software products listed below. and conditions provided in accompanying permission notices are met: Copyright 1994 Hewlett-Packard Company Copyright 1996. 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. provided the above notices are retained. royalty-free license to use the STLport. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws. Copyright 1999. SAP License Agreement for STLport SAP License Agreement for STLPort between SAP Aktiengesellschaft Systems. distribute and sell this software and its documentation for any purpose is hereby granted without fee. Permission to modify the code and to distribute modified code is granted. using. By downloading. This software was developed using ANTLR. It is provided “as is” without express or implied warranty.97 Silicon Graphics Computer Systems Inc. Applications. 112/116 PUBLIC 2011-03-07 . The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. Permission to use. 1. provided that: ■ The conditions indicated in the above permissions notice are met. provided the above notices are retained on all copies. Permission to use or copy this software for any purpose is hereby granted without fee. Germany (hereinafter: SAP) and you (hereinafter: Customer) 1.org C++ library (STLport) and its documentation without fee. The Customer may distribute original or modified STLport sources. This material is provided "as is". provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. 2.2000 Boris Fomitchev Copyright 2001 SAP AG Permission to use. Silicon Graphics makes no representations about the suitability of this software for any purpose. and a notice that the code was modified is included with the above copyright notice. copy. SAP grants Customer a non-exclusive. modify. 2. Any use is at your own risk. Note that for these third party products the following special terms and conditions shall apply. distribute and sell this software and its documentation for any purposes is hereby granted without fee. Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG 5. copy. with absolutely no warranty expressed or implied. modify. Boris Fomitchev makes no representations about the suitability of this software for any purpose. Permission to use. ■ The following copyright notices are retained when present. Products in Data Processing Dietmar-Hopp-Allee 16 69190 Walldorf. Copyright 1997 Moscow Center for SPARC Technology. copy. modify. distribute and sell this software and its documentation for any purposes is hereby granted without fee. 4. Subject Matter of the Agreement 1. non-transferable. and to all of the terms and conditions of this Agreement. 3. It is provided “as is” without express or implied warranty.

Support and Maintenance SAP does not provide software maintenance for the STLport. 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.SAP CRM | 4. Acrobat. Technical data. PostScript. SAP makes no representations about the suitability of this software for any purpose. or (ii) ownership of fifty percent (50%) or more of the outstanding shares. distribute and sell this software and its documentation for any purposes is hereby granted without fee. If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP. 3. direct or indirect. Permission to use. 4. Irrespective of the legal reasons. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. due to the circumstances known to it at that point in time representing a typical transfer of the software. copy. see SAP Note 854621. 4 includes claims against employees or agents of SAP. and configuration files. including unauthorized operation. Adobe Document Services Adobe. 2011-03-07 PUBLIC 113/116 . 2. the Adobe logo. Definitions: ■ "License" shall mean the terms and conditions for use. Apache License. SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5.0 1. SAP shall not be liable for indirect damage. in particular by making backup copies at the minimum intervals recommended by SAP. and distribution as defined by Sections 1 through 9 of this document. whether by contract or otherwise. ■ "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. 5. 4 if this loss could have been avoided by observing this obligation. ■ "Source" form shall mean the preferred form for making modifications.000. reproduction. documentation source. advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes. SAP cannot guarantee that the STLport is error-free.3. SAP shall not be liable for the loss of data and its recovery. without material defects or suitable for a specific application under third-party rights. consequential damage caused by a defect or lost profit. SAP shall only be liable for damage. provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Limited Liability 1. or are under common control with that entity. The exclusion or the limitation of claims in accordance with the present Art. 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. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer. modify. ■ "Legal Entity" shall mean the union of the acting entity and all other entities that control. notwithstanding the other limitations of the present Art. to cause the direction or management of such entity. 3. and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. "control" means (i) the power. 4.2 above. Exclusion of warranty As the STLport is transferred to the Customer on a loan basis and free of charge. The Customer shall take adequate measures for the protection of data and programs. or (iii) beneficial ownership of such entity. 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. including but not limited to software source code. Only valid for: SAP ERP. ■ "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. sales brochures. In the case of Art. Version 2. 2. 6. are controlled by. 4. For the purposes of this definition. Software maintenance of the STLport therefore shall be not included.

each Contributor hereby grants to You a perpetual. 3. irrevocable (except as stated in this section) patent license to make. ■ "Derivative Works" shall mean any work. and in Source or Object form. provided that You meet the following conditions: 1. 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. offer to sell. Derivative Works shall not include works that remain separable from. Grant of Copyright License Subject to the terms and conditions of this License. 4. if and wherever such third-party notices normally appear. within the Source form or documentation. If the Work includes a "NOTICE" text file as part of its distribution. that is based on (or derived from) the Work and for which the editorial revisions. and distribute the Work and such Derivative Works in Source or Object form. including but not limited to communication on electronic mailing lists. irrevocable copyright license to reproduce. excluding those notices that do not pertain to any part of the Derivative Works. elaborations. excluding those notices that do not pertain to any part of the Derivative Works. ■ "Work" shall mean the work of authorship. You must give any other recipients of the Work or Derivative Works a copy of this License. royalty-free. alongside or as an addendum to the NOTICE text from the Work. no-charge. For the purposes of this License. made available under the License. prepare Derivative Works of. worldwide. non-exclusive. then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. Redistribution You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium. "submitted" means any form of electronic. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form. annotations. ■ "Contribution" shall mean any work of authorship. worldwide. within a display generated by the Derivative Works. or for any such Derivative Works ■ 114/116 PUBLIC 2011-03-07 . use. sublicense. whether in Source or Object form. trademark. or distribution of Your modifications. with or without modifications. then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file. publicly display. sell. reproduction. an original work of authorship. and conversions to other media types. 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. source code control systems. all copyright. You may add Your own attribution notices within Derivative Works that You distribute. or on behalf of. publicly perform. and attribution notices from the Source form of the Work. have made. and otherwise transfer the Work. and issue tracking systems that are managed by. the Work and Derivative Works thereof. or. generated documentation. import. including but not limited to compiled object code. including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof. or other modifications represent. each Contributor hereby grants to You a perpetual. You must cause any modified files to carry prominent notices stating that You changed the files. or written communication sent to the Licensor or its representatives." ■ "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. and 2. provided that such additional attribution notices cannot be construed as modifying the License. non-exclusive.2. or merely link (or bind by name) to the interfaces of. and 3. You must retain. as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). in the Source form of any Derivative Works that You distribute. verbal. if provided along with the Derivative Works. 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. Grant of Patent License Subject to the terms and conditions of this License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use. as a whole. The contents of the NOTICE file are for informational purposes only and do not modify the License. whether in Source or Object form. For the purposes of this definition. and 4. but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution. in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works. the Licensor for the purpose of discussing and improving the Work. patent. no-charge. royalty-free.

reproduction. or product names of the Licensor. as a whole. You may act only on Your own behalf and on Your sole responsibility. 9. any warranties or conditions of TITLE. or other liability obligations and/or rights consistent with this License. provided Your use. acceptance of support. nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License. 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. Trademarks This License does not grant permission to use the trade names. work stoppage. Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS. Submission of Contributions Unless You explicitly state otherwise. 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. You may choose to offer. computer failure or malfunction. Limitation of Liability In no event and under no legal theory. 8. without any additional terms or conditions.sap. or otherwise. not on behalf of any other Contributor. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND. either express or implied. in accepting such obligations. shall any Contributor be liable to You for damages. Disclaimer of Warranty Unless required by applicable law or agreed to in writing. incidental. including.com/instguides 2011-03-07 PUBLIC 115/116 . service marks. trademarks. warranty. Accepting Warranty or Additional Liability While redistributing the Work or Derivative Works thereof. indemnity. 7. without limitation. indirect. or any and all other commercial damages or losses). except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. and hold each Contributor harmless for any liability incurred by. whether in tort (including negligence). defend. End of: SAP ERP. such Contributor by reason of your accepting any such warranty or additional liability. or claims asserted against. contract. and charge a fee for. unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing.SAP CRM | Documentation in the SAP Service Marketplace You can find this document at the following address: http://service. NON-INFRINGEMENT. MERCHANTABILITY. even if such Contributor has been advised of the possibility of such damages. Notwithstanding the above. and distribution of the Work otherwise complies with the conditions stated in this License. and only if You agree to indemnify. 6. including any direct. special. However. or FITNESS FOR A PARTICULAR PURPOSE.5.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. All rights reserved. The information contained herein may be changed without prior notice.sap. .SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.com © Copyright 2011 SAP AG.

Sign up to vote on this title
UsefulNot useful