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

0 SR3 ABAP
Target Audience ■ System administrators ■ Technology consultants

PUBLIC Document version: 1.5 – 2010-03-16

Document History

CAUTION

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

1.5 1.4 1.3 1.2 1.1

2010-03-16 2009-12-08 2009-09-09 2009-03-12 2009-01-09

Update in Database-Specific System Copy: example for distributed or high availability system corrected Update in Database-Specific System Copy Update in Oracle-Specific Procedure Update in Constraints and Preparation for Table Splitting DI-, EPC-, and EP-specific information updated

2/126

PUBLIC

2010-03-16

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 Chapter 5 5.1

Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 7 8 8 8 9

Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 General Technical Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Installing the Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 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 System i to Perform the Export . . . . . . . . . . . . . . . . . . . . Preparing the Windows Host for the SAP System Installation . . . . . . . . . . . . . Preparing a Windows User Account and System i User Profile . . . . . . . . . . . . . Installing TMKSVR and Creating an Installation Share . . . . . . . . . . . . . . . . . . Starting SAPinst on System i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting R3load Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 22 25 26 29 30 30 36 36 37 39 41 45 47 48

Database-Specific System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Oracle-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

2010-03-16

PUBLIC

3/126

. .2. . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . Step 9c: Creating a New STOGROUP Using the HLQ of the Target System . . . . . . . . . . . . . . . . Step 4: Capturing View Definitions with DB2 V9 (if the Schema Name is to be Changed) . . . . . . . . . . . . . . . . . . . .6. . . . . . .8 5. . . . . . . .6. . . . .3. . . . . .1. . . . . . . . . . . . . . . . . . .11 5. . . . . . . . . . . . . . . . . . . . . . . .4 5. Step 8: Printing the Bootstrap Data Sets . . . . .1 5. . . . . .7 5. . . .4 5. . . . . . Step 6: Making Copies of Source Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . . . . . . . and Windows Specific Procedures . .13 5. .5 5.1. . . . . . . . . . . . . . . . . .2 5. . . . . . .1. . SQL Statement Number 09 . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 5. . Step 5: Stop the Source System .6. . . . . . . . IBM DB2 for Linux.3. . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1: Check Consistency . . . . . . . .6. .8 5. . Step 9d: Stopping Index Spaces . SQL Statement Number 04 . . .6. . . Step 9b: Start the Target System . . . Step 9f: Restart the Index Spaces . . .2 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6. . SQL Statement Number 07 . . . . . . Step 7: Creating the Target System . . .4 5. . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 5. . . . . . . . . . . .5. . . . . . . . . . . . . .10 5. . . . . . . . . .3 5. . . . SAP MaxDB-Specific Procedure . . . . . . . . . .6. . . . . . Restoring the Database Files on the Target System with BR*Tools . . . . . .1 5. . . . . . . . .6. . . . . . . . .6 5. . . . . . . . . . . . . . . . . MS SQL Server-Specific Procedure . . . . . . . . . . . . . . . . . . . . 54 58 58 59 59 61 62 63 66 66 69 69 71 71 72 72 72 73 74 75 75 77 78 78 79 79 80 80 80 81 82 83 83 83 83 84 4/126 PUBLIC 2010-03-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 9g: Creating the Temporary Files for the DB2 Target System .3 5. . . . . . . . . . . . . . . . . . . . . .7 5. .1 5. . . . . . . . . . . . . Step 3: Run SQL Statements in the Source System . . . . . . .3. . .6. . . . . . . . . .1 5. . . . .6 5. . . . . . . . . . . .6. . . . . UNIX. . . . . . . . . . . . . . . SQL Statement Number 01 . . . . . . . . . .1. Step 9a: Changing the Bootstrap Data Sets (BSDS) . . . . .5 5.3 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . .9 5. . . . . . . . . . . . . . . . . . . . . SQL Statement Number 02 . . . . . IBM DB2 for z/OS Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 9e: Changing the User-Defined Indexes in the DB2 Catalog . . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . Creating an Offline or Online Backup with BR*Tools . . . . . . . . .3. . . . . . . SQL Statement Number 08 . . . . . . . SQL Statement Number 05 . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. .6. . . . . . . . . . .5 5.5 5. . . . . . . . . . . . Creating a Backup . . . . .6. . . . .6. . . . . . . . . .1. . . . . . . . . . . . . . . . . . . Preparing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . .6. .2 5. . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . . . Step 2: Stop and Restart the Source System . . . . .6 5. . . . . . . . . . . . . . . . . . . . . .12 5. . . . . . . . . . . . Creating an Offline Backup Manually . .9 5. . . . . . . .15 Generating the Control File Structure . . . . . . . . . . . SQL Statement Number 03 . . . . . . .6. . . . . .4 5. . . . . . . . . . . . . . .3. . . . .6. . . . . . . .3 5. . . . . . . IBM DB2 for i5/OS Procedure . . . . . . . . . . . . . .6. . . . . . SQL Statement Number 06 . . . . .14 5. . . . . . . . .3. . .6. . . . . . Restoring the Database Files on the Target System Manually . . . . . . . . . . . .

17 5. . .2 7. . . . . . . . . . . . .6. . . . . . . . . . 105 Output Files . . . . . . . . . . .3 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 7. . . . . . . . .2 6. . . . . . . . Follow-Up Activities . 110 Installing the Target System Using the Migration Monitor . . . . . . . . . . . . . . . . 103 Processing Split Tables . . . . . . . . . .2. . . . . . . . . .2 Chapter 7 7. . . . . . .5 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Jobhead Correction after Homogeneous System Copy . . .18 5. .6. . . . . . . .2. . . . .5. . . . . . . . . . . . Step 12: Adapting WLM Application Environments for DB2 Stored Procedures . . . . . . . . . . . . . . . . . .1 6. . . . . . . . . . . . . .1 7. . . Step 11 (DB2 V9): Changing the Schema of the Target System . . .7 7. .6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . . .2 Additional Information . . 95 Assigning DDL Files to Packages . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . 112 Performing a Remote Export Using SAPinst . . . . 95 R3load Procedures Using the Migration Monitor . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . Performing Follow-Up Activities in the Target System . . . . .19 5. . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . .4. . .1 6. . . . . . . . . . . . . .6. . . .6 7. . . . . . . . . . . . . . .6. . . . . . . . . . . Performing Follow-Up Activities for ABAP . . . . . . . .1. . . . . . . . . . .2 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 7. . . . . . . . . . .20 5. . . . . . . . . . .1 7. 102 Defining Groups of Packages . . . . . . .4 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 7. . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . 114 Performing a Remote Installation with SAPinst (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 9i: Adjusting the DDF Location Name and Port Number . . . . . . . . . . . . .1. . . . . . . . . . . . . 110 Using SAPinst GUI . . . . Step 10 (DB2 V9): Changing the VCAT of the Target System . . . . . . . . . 95 Configuration . . .21 Step 9h: Implementing HLQ of the Target System in the Work File Database . . .16 5. Step 10 (DB2 V8 and Lower): Changing the VCAT of the Target System . . . 103 Starting the Migration Monitor . . . . . . . . . . . . . 116 2010-03-16 PUBLIC 5/126 . . . . . . . . 115 Starting SAPinst GUI Separately (Optional) . . . . . .1. . . . . . . . . . . 84 84 84 86 86 88 89 89 89 89 94 Chapter 6 6. Performing Follow-Up Activities in the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

1 Terminology ■ Homogeneous System Copy During the system copy you use the same operating system and database platform as the original system. you change either the operating system or the database system. you can copy ABAP systems.0 SR3 Terminology 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. Heterogeneous system copy is a synonym for migration.1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. ■ Heterogeneous System Copy During the system copy.1 1.0 SR3 As of SAP NetWeaver 7. ■ System Copy Duplication of an SAP system. Their SAP system names are abbreviated to SOURCE_SAPSID and TARGET_SAPSID (System i: source_<SID> and target_<SID>). 1. ABAP+Java systems and Java systems in one run using either database-specific methods or database-independent methods. ■ Database Copy Database-dependent part of the system copy. They are used in the same way as in the SAP system installation documentation. The terms source database and target database are also used in this description. SAPinst installs all the instances again. but it uses a copy of the source system database to set up the database. You must replace them with the values valid for your site.0. or both. Certain SAP parameters might change in a copy. The following additional placeholders are used: Placeholder <SAPSID> <S_HOST> <T_HOST> Meaning How to find out SAP system ID System name of the source host System name of the target host Command hostname Command hostname 2010-03-16 PUBLIC 7/126 . ■ Placeholders Placeholders such as <SAPSID> are used in commands. ■ 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. When you perform a system copy.

■ SAP OS/DB Migration page at http://service.3 System Architecture 1. check the SAP OS/DB Migration Planning Guide that is available in the Media Library. 8/126 PUBLIC 2010-03-16 . Only perform a heterogeneous system copy if you are a certified system support consultant or a certified SAP Technical Consultant. ■ SAP Note 82478 CAUTION Only perform a system copy if you have experience in copying systems and good knowledge of the operating system. A refresh of the database means that only the database is loaded with the content of a database of a different system.1 1.2 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. As in this scenario no migration controller is invoked.4 Restrictions The target system installation consists of both the target database and target instances/application servers installations.2 Online Information from SAP More information about system copy is online available as follows: ■ SAP System Copy & Migration page at http://sdn. NOTE If you encounter problems during the system copy.sap. End of: IBM DB2 for Linux and UNIX and Windows | ■ Refresh of the database is not supported.0 SR3 Online Information from SAP Meaning How to find out <SAPSID> of the original system <SAPSID> of the target system Placeholder <S_SAPSID> <T_SAPSID> <S_DBSID> <T_DBSID> SAP system ID of the source system SAP system ID of the target system Database ID of the source system Database ID of the target system of the original system <DBSID> of the target system <DBSID> 1.com/irj/sdn/systemcopy. For the scenarios below.0 SR3. ■ Copying the database only is not supported. the database. this is not supported. create a customer message using the application area BC-INS-MIG.sap. and the ABAP Dictionary. the following holds: ■ Only valid for: IBM DB2 for Linux and UNIX and Windows | The option Deferred Table Creation is not supported for load-based system copies for SAP systems that are not based on SAP NetWeaver 7.com/osdbmigration. Additionally to the information contained on this page. 1.

■ If you have made modifications in your development system and want to copy your quality assurance or production system onto the development system. This documentation does not describe how to copy data from non-SAP systems to SAP systems. Transporting production clients is not supported at all. see SAP Note 153433 and System Landscape Optimization at http://service. Use the appropriate tools for database reorganization.com/slo. If you used Data Archiving in the source or in the target system. see SAP Note 551344. ■ If you want to convert a non-Unicode system to a Unicode system or perform the system copy of a Unicode system.sap. hardware migration). This documentation does not cover the client copy procedure. so the system is not complete any longer. ■ This documentation does not describe how to export and import a database with the installation tools for reorganization purposes. ■ Reinstalling the central instance without the database is not supported. ■ This documentation describes how to copy data from one SAP system to another SAP system based on SAP NetWeaver Application Server. ■ SAP does not generally support all Data Archiving operations after a system copy. or you arrange network access for appropriate archive file sharing. ■ For the development of Java applications. access to the created archive file (s) from the target system may not always be possible. and you do not store archive files using ArchiveLink/CMS. ● The system copy is done to replace a productive system by a new productive system (for example. 1. we strongly recommend that you follow the rules mentioned below.0 SR3 Constraints ■ Copying the central instance only is not supported. The migration controller deletes all dialog instances in the database. 2010-03-16 PUBLIC 9/126 . 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. You can either copy all archive files to file systems that are not shared between the source and the target system. see SAP Note 130906. 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.5 Constraints ■ SAP does not support client transport as a system copy method. so the system is not complete any longer. as SAP does not support this installation option. The migration controller deletes all dialog instances in the database. Otherwise. For more information. only read-access to the previously archived data is intended from the target system (no reloading).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. assuming that the target system did not exist before and the source system's operation is discontinued after the system copy.1 1.

0 SR3 Constraints You must not change the system ID during system copy. 10/126 PUBLIC 2010-03-16 . contact SAP SLO at http://service.5 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. If you absolutely need to save this data to the file system level.consulting@sap. ■ Dos and Don'ts for system copy: ● Do: ◆ Save configuration data and runtime data in the Java database only. you must use the Software Deployment Manager (SDM) to save the data. ■ When you perform a system copy. In all other cases. nor can you select usage types. ◆ Follow the Open SQL standard.com. ◆ Set up dependencies between Java and ABAP. This means that none of the usage types in the target system can be excluded from the system copy. ◆ Make sure that all communication runs through the database pool.sap. all software units or usage types in the source system are copied to the target system. Use a pointer to the central storage of such information. but arrange for file access and/or ArchiveLink/CMS connectivity. ● Don't: ◆ Save any system and infrastructure-specific data in business objects.1 1. 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.com/slo or slo.

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

sap. ■ Order the right version of the installation kit before starting the system copy. ■ Check that you have the appropriate tool versions for your SAP kernel. and Other Software Make sure that all required DVDs for the system copy are available: ■ Required DVDs ● Installation Master DVD NOTE The DVD names are abbreviated. you can upgrade them at different times. ■ For the installation of the target system.0 SR3) ■ The documentation System Copy for SAP Systems Based on SAP NetWeaver 7. NOTE You can operate several SAP systems on a single host without encountering any problems. SAP ERP 6.0 SR3 only describes the export of the source system in detail.0 SR3 ABAP on <OS> : <DB> at http:// service. we recommend that you use a separate host for each system because an SAP system upgrade might depend on an OS upgrade.0 SR3 ABAP on <OS> : <DB> at http:// service.0 Installation .com/crm-inst SAP CRM 2005 CRM Core and Standalone Components .sap. you also need the installation guide for your SAP application: SAP NetWeaver 7.0: Installation Guide – SAP NetWeaver 7.com/erp-inst SAP ERP 6. SAP CRM 5. Nevertheless. If the SAP systems are on separate hosts. You can find the full names of all media shipped with SAP NetWeaver 7.com/installnw70 Installation – SAP NetWeaver Systems . Required DVDs.0 .0: Installation Guide – SAP SCM 5.sap.0 at http://service.2 Planning SAP Note 1120872 (Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0: Installation Guide – SAP ERP 6. SAP SRM 5.0 SR3 ABAP on <OS> : <DB> at http:// service.com/srm-inst Using SAP SRM Server 5. Make sure that the versions of the SAP system and the installation tools are the same on the target and source systems.sap.0 SR3 ABAP on <OS> : <DB> at http:// service.sap.com/installNW70. Tools.com/instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP SCM 5. Exceptions are only allowed if they are described in an SAP Note.0 in Media Information for SAP NetWeaver 7.0 SR3 ABAP on <OS> : <DB> at http:// service. SAP SCM 5. CAUTION The source system must be in a consistent state before you can copy it.0 Server .0: Installation Guide – SAP SRM 5.0: Installation Guide – SAP CRM 5.sap. 12/126 PUBLIC 2010-03-16 .

a partial test run (export of the entire database or parts of it) can be sufficient to calculate the system downtime. 2. see. We recommend that you perform read/write actions only on local file systems. Choose the best data transfer method (for example. ■ Decide which system copy procedure you want to use: ● The database-independent procedure using SAP tools. transport. This means that the entire database is exported from the source system. new machine type.com/migrationkey. Perform a test run of the system copy. The source system is only down for the time of the export. new hard disk configuration. 1. see Database-Specific System Copy [page 51]. Define a schedule for the test migration and the final migration. Creating A System Copy Plan Create a plan to perform the system copy. These tools let you: ◆ Restore a backup of one database (source database) in another one (target database) (backup method) ◆ Unload the source database and load the data into the target database For more information. transferred to the target system and imported there. new file system type). 2010-03-16 PUBLIC 13/126 . NOTE For a heterogeneous system copy. Consider the downtime of the source system (for preparations and copying) when planning the system copy. try to perform a complete test run. 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. Use this method if database-specific methods are either not available or not suitable. ■ If you do not want to replace your source system. Database-Independent System Copy [page 21]. 3. Calculating the system downtime is particularly important for very large databases (VLDB) or when tapes are being used. time for export. You can use the time taken by the test run to calculate the system downtime: ■ If your target system will replace your source system. and import). consult your SAP-authorized hardware partner.2 Planning ■ For a heterogeneous system copy you need to get a migration key by generating it at http:// service. The test run is also to determine the amount of export data. only the database-independent method is available.sap. FTP or tape). For more information. System downtime is approximately equal to the total test time (that is.

you will require a new license key for the target system. see http://service. For more information about ordering and installing the SAP license. The license key of the source system is not valid for this system.sap.com/nw70 SAP NetWeaver 7.sap. see http://help.com/nw70 SAP NetWeaver 7. Access to archive files is platform-independent. For more information about SAP license keys.2 Planning ■ Choosing an SAP system ID You can choose the new SAP system ID <TARGET_SAPSID> freely during a new installation. ● System copy procedure for a homogeneous system copy only For more information. ■ 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.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management Data Archiving . ■ These methods are not supported for all database systems. see http:// help. ■ Configuration analysis and hardware analysis You need to determine the: ● Number of application servers ● Expected size of the database ● Additional disks or other hardware required ● Required memory NOTE See the section on hardware and software requirements in the SAP system installation documentation to determine the system requirements. See 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.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SAP Licenses . see SAP MaxDB-specific procedure [page 63].com/licensekey. For more information. CAUTION To meet the requirements of the Workbench Organizer. you must choose different SAP system IDs for different SAP systems.sap. Use one of the following: ● System copy procedure on Windows using R3load 14/126 PUBLIC 2010-03-16 . see System Copy Procedure [page 22]. ■ SAP license Once the installation is completed and the SAP system copy has been imported. Adapt the file residence information in the target system.

For more information. see SAP MaxDB-specific procedure [page 63]. and Windows Specific Procedures [page 66]. End of: UNIX | ● Only valid for: Windows | System copy procedure on Windows using R3load For more information. Use one of the following: ● System copy procedure on System i using R3load For more information. see IBM DB2 for I5/OS Procedure [page 69]. End of: UNIX | ● Only valid for: Windows | System copy procedure on Windows using R3load For more information. see System Copy Procedure [page 22]. see System Copy Procedure [page 22].2 Planning Database OS Platform Available Methods IBM DB2 for i5/OS IBM System i IBM DB2 for UNIX or Windows Linux. and Windows is supported for SAP systems based on SAP NetWeaver 7. For more information. DELETE with WHERE is not performed if import errors occur in the target system. see IBM DB2 for Linux. For more information.0 SR3. 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. see IBM DB2 for z/OS Specific Procedure [page 69]. see System Copy Procedure [page 22]. End of: Windows | IBM DB2 for z/OS IBM System z ● The backup method of IBM DB2 for Linux. UNIX. Use one of the following: ● Only valid for: UNIX | System copy procedure on UNIX using R3load For more information. 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. ● System i-specific procedure for a homogeneous system copy only For more information. see System Copy Procedure [page 22]. UNIX. and Windows For more information. see SAP Note 585277. ● System copy procedure for a homogeneous system copy only For more information. see System Copy Procedure [page 22]. Use one of the following: ● Only valid for: UNIX | System copy procedure on UNIX using R3load 2010-03-16 PUBLIC 15/126 . UNIX. see SAP Note 778729. see Starting SAPinst on System i [page 41].

End of: Windows | MS SQL Server Windows ● R3load method with Export/Import Monitors For more information. ● Homogeneous system copy only: Oracle backup/restore method For more information. see System Copy Procedure [page 22]. see R3load Procedures Using the Migration Monitor [page 95]. see MS SQL Server-Specific Procedure [page 66] and SAP Notes 193816 and 151603. see R3load Procedures Using the Migration Monitor [page 95]. Use one of the following: ● Only valid for: Windows | System copy procedure on Windows using R3load For more information. ● Homogeneous system copy only: Backup/Restore or Detach/Attach Method For more information. see Oracle-Specific Procedure [page 52]. see R3load Procedures Using the Migration Monitor [page 95]. 16/126 PUBLIC 2010-03-16 . see System Copy Procedure [page 22]. see System Copy Procedure [page 22]. ● Oracle-specific procedure for a homogeneous system copy only For more information. Use one of the following: ● Only valid for: Windows | System copy procedure on Windows using R3load For more information. see Oracle-Specific Procedure [page 52] and SAP Note 676468. End of: UNIX | Oracle Windows ● R3load method with Export/Import Monitors For more information.2 Planning Database OS Platform Available Methods For more information. End of: Windows | ● R3load method with Export/Import Monitors For more information.

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

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

In this case. If you want to perform a remote installation. see Performing 2010-03-16 PUBLIC 19/126 . controlling it with the SAPinst GUI from a local host. as well as after copying the target system. ■ Prepare the system for SAPinst. CAUTION Prerequisites for an export: Before performing an export. To do so. Defer the migration until the incremental conversion has finished. For more information. you have to finish the incremental conversion. This lets you perform the installation on a remote host. make sure that no incremental conversion is in progress. Try to finish the incremental conversion by performing the following steps: ● If the tables are in state For conversion or in state Done. If there are any table entries in table TICNV. 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.Windows | NOTE If required. run transaction ICNV. This includes the installation of a Java Runtime Environment (JRE).3 3. an incremental conversion is in progress. ● If the tables are in any other state. which is required both for SAPinst and the SAPinst GUI.2 Preparations Installing the Java Runtime Environment ■ CO customers: You can perform an additional consistency check by running the report group 1SIP before copying the source system. Make sure that no customer data is changed in the meantime. and then compare the results. delete the entries by choosing Control Delete Entry . 3. make sure that the tables TATGPC and TATGPCA are empty. To test if an incremental conversion is in progress. Choose Assistant and proceed according to the online documentation. If you do not delete the contents of these tables you will encounter problems while importing the data to your target system because of non NULL capable fields in these tables. see Installing the Java Runtime Environment [page 19]. Only valid for: UNIX. CAUTION Heterogeneous System Copy only: Before you start the export of your source system.2 Installing the Java Runtime Environment You need to prepare your system for SAPinst. you have the following options: 1. 2. you can perform a remote installation using a standalone SAPinst GUI on a separate Windows or UNIX host.

SAP SRM | 4. Check the JRE versions that are released for SAP systems in the Product Availability Matrix (PAM): 1. you need to download and install it. Go to http://service. For more information about the recommended JRE version for your operating system and about how to download it.3 3. If SAPINST_JRE_HOME is not found. End of: UNIX.Windows | Procedure 1. End of: SAP CRM. ■ If the JRE is already installed Check the installed version of the JRE by entering: java -version NOTE SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment.0 (2004S) .com/pam.security and replace entry securerandom. Make sure a valid JRE version is installed. Only valid for: SAP CRM.sap. End of: UNIX | Linux | 20/126 PUBLIC 2010-03-16 . Choose tabstrip JSE Platforms.SAP ERP.source=file:/dev/urandom. SAPinst also checks JAVA_HOME.SAP SCM. you need at least a JRE on the local host to start the SAPinst GUI there. choose SAP NetWeaver SAP NetWeaver 7. you have to perform the following: Edit the configuration file $JAVA_HOME/jre/lib/security/java.SAP SCM. NOTE 2. In this case. see SAP Note 723909. 2.SAP SRM | On the right-hand panel. End of: SAP NetWeaver | 3.SAP ERP.source=file:/dev/random with securerandom. Only valid for: UNIX | Linux | NOTE If you use a Sun Java VM. Only valid for: SAP NetWeaver | On the right-hand panel.2 Preparations Installing the Java Runtime Environment a Remote Installation with SAPinst [page 115]. as follows: ■ If the JRE is not already installed. choose SAP Application Components <your product> . you need to download and install it. The JRE is part of the JDK (Java Development Kit). ■ If the JRE is not already installed Since the JRE is not part of the SAP shipment.

are lost after the system copy. If the database configuration of your database is stored in the file system. such as the distribution of tables over several tablespaces or dbspaces. ■ R3load only: Changes to database objects that cannot be maintained in the ABAP Dictionary (transaction SE14). for example) must have its own separate installation directory whenever you start SAPinst. The overall runtime can be reduced by creating packages of the same size. resulting in varying unload/load runtimes. delete the database on the target system before the import according to the corresponding description in section Additional Information of the installation documentation for your SAP component. ■ For a consistent database the SAP system must be shutdown (excluding the database!). we recommend you to back up these configuration files before deleting the database. The database must still be running. SAPinst uses the R3load tool. Other objects are not exported by SAPinst. 2010-03-16 PUBLIC 21/126 . you can export and import your database in a databaseindependent format. all tables of the SAP system are grouped into packages. You can achieve this by splitting the default packages (one package per data class) into more and smaller pieces. 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. that is. Splitting STR Files ■ During the standard system copy process. whereby all tables with the same data class belong to the same package. The processing unit for one unload/load process is a package.4 Database Independent System Copy 4 Database Independent System Copy With the SAP installation tool SAPinst. ■ If the target system already exists and if you do not plan to perform an MCOD installation. Constraints R3load and Jload Restrictions ■ SAPinst generates a database dump of all SAP objects that are defined in the ABAP Dictionary (R3load). 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. creating packages with a similar processing time. The packages usually differ in number and size of contained tables.

For more information. Windows. Only valid for: UNIX.Windows | Make sure that the QCM tables are deleted from your system. End of: UNIX. 2. Process Flow For UNIX. for example DB/ORA. see the F1 help about the parameters prompted on the screen Split STR Files while running SAPinst to export the database. see Preparing the Windows Host for the SAP System Installation [page 36]. Heterogeneous system copy: Generate the migration key at http://service. Enter the installation number of your source system when prompted. subdirectory DB/<DBTYPE>. The options can be used separately or – when using the new Java based splitting tool – combined.sap.com/ migrationkey. see General Technical Preparations [page 17]. ■ “Splitting of STR Files” is part of the “Advanced Export Parameters” and is disabled by default. Procedure Process Flow on the Source System (Export) When performing the export you create a MIGRATION EXPORT CD image.1 Database Independent System Copy System Copy Procedure ■ There are several options of how to split packages. You can find the EXT files in your export dump directory.Windows | 2. For a detailed description of the options. see System Copy Procedure [page 22]. Follow the sequence of steps described in the process flows below for a: ■ Central System ■ Distributed System and High-Availability System Central System To perform the export for a central system. you must first create the EXT files for the target database system. using the splitting tool parameters selected by SAPinst is a good starting point.1 System Copy Procedure This section describes the system copy procedure using R3load. Perform the export on the central system host: 1. End of: IBM i5/OS | 22/126 PUBLIC 2010-03-16 . you need to proceed as follows on the central system host: 1. CAUTION If you want to split STR files. If you select the splitting option and unless you did not already perform some tests. which contains the data of the exported system. Only valid for: IBM i5/OS | Prepare the Windows host for the SAP system installation. For more information.4 4. 4. or System i. and which you use to install the target system.

you set up the target system using SAPinst. For more information. 7. Run SAPinst on UNIX. In SAPinst. Enter the installation number of your source system when prompted 2. see Setting Up the Target System Using SAPinst [page 47]. For more information.sap. Windows. Only valid for: IBM i5/OS | Prepare a Windows user account and a System i user profile. For more information. End of: IBM i5/OS | 4.1 Database Independent System Copy System Copy Procedure 3.com/ migrationkey. see Installing TMKSVR and Create an Installation Share [page 39]. see Preparation for Table Splitting [page 26]. 8. choose the installation service Export Preparation. see Restarting R3load Processes [page 45]. For more information. Result You have finished this part of the system copy. To complete the system copy. or System i to export the database instance and the central instance. For more information. Distributed System or High-Availability System To perform the export for a distributed system or a high-availability-system. solve the problem and perform a restart. 2010-03-16 PUBLIC 23/126 . For more information. see Running SAPinst on UNIX or Windows to Perform the Export [page 30] or Running SAPinst on System i to Perform the Export [page 36]. see Running SAPinst on UNIX or Windows to Perform the Export [page 30] or Running SAPinst on System i to Perform the Export [page 36]. see Preparing a Windows User Account and System i User Profile [page 37]. choose the installation service Database Instance Export. Only valid for: IBM i5/OS | Install TMKSVR and create an installation share. Run SAPinst on UNIX. End of: IBM i5/OS | 5. Generate DDL statements.4 4. In SAPinst. Windows. Heterogeneous system copy only: Generate the migration key at http://service.Windows | Make sure that the QCM tables are deleted from your system. NOTE If R3load processes fail due to an error. you need to proceed as follows: 1. For more information. Prepare the system for table splitting (optional). 6. Only valid for: UNIX. For more information. see Generating DDL Statements [page 25]. or System i to prepare the source system for parallel export or parallel import (optional). Perform the export on the database instance host: 1.

or System i to export the database instance. Run SAPinst on UNIX. choose the installation service Export Preparation. For more information. Windows. Prepare the system for table splitting (optional). 4. see Running SAPinst on UNIX or Windows to Perform the Export [page 30] or Running SAPinst on System i to Perform the Export [page 36]. For more information. To complete the system copy. see Preparation for Table Splitting [page 26]. End of: UNIX. or System i to prepare the source system for parallel export/ import (optional). For more information. see Generating DDL statements [page 25]. choose the installation service Database Instance Export. you must proceed as described in SAP Note 884452. 3. For more information. 24/126 PUBLIC 2010-03-16 . Windows. For more information. In SAPinst. see General Technical Preparations [page 17]. In SAPinst. see Restarting R3load Processes [page 45]. 5. CAUTION If your database instance is running on HP PA-Risc. see Running SAPinst on UNIX or Windows to Perform the Export [page 30] or Running SAPist on System i to Perform the Export [page 36].1 Database Independent System Copy System Copy Procedure For more information. Run SAPinst on UNIX. Result You finished this part of the system copy.4 4. NOTE If R3load processes fail due to an error. you set up the target system using SAPinst. solve the problem and perform a restart. Generate DDL statements. see Setting Up the Target System Using SAPinst [page 47]. For more information.Windows | 2.

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

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

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

28/126 PUBLIC 2010-03-16 . Afterwards.STR Description <table>_IDX.txt. With one line in the file R3ta_hints. copy it from the directory <IM_OS>/COMMON/INSTALL to the installation directory and adapt it according your requirements as soon as the Parameter Summary dialog appears and before starting the processing phase. This is the case when you use a DDLDB2. End of: Oracle | For each table to be split. separated by a blank. Contains the task to drop the temporary index. End of: IBM DB2 for z/OS | Only valid for: IBM DB2 for z/OS | EXAMPLE 1.txt.3 Database Independent System Copy Preparation for Table Splitting be configured in the way that the data import processes the packages are sequentially. These specifications are used by R3ta to create the WHERE condition. see SAP Note 960280. Use the DEFER YES parameter to create the index.TPL file with no ORDER_BY_PKEY and the R3load does not overrule this setting. the default index name is <table>~IMG. make sure you select the Split predefined tables checkbox and add the R3ta_hints. R3load command file for dropping the temporary index. R3ta creates the following files to facilitate the creation of the temporary index: File <table>_IDX. Which tables cannot be unloaded unsorted is described in SAP Note 954268.cmd Contains the description of the temporary index. Contains the task to create the temporary index. you can instruct R3ta to use specific columns of a table to create a WHERE condition. R3load command file for creating the temporary index.cmd DRP_<table>_IDX. If you want to modify this file. End of: IBM DB2 for z/OS | Only valid for: Oracle | Oracle only: For further information and for alternatives. 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. After the Table Splitting Preparation. The columns have to be part of the primary key of the table.txt file in the Split STR Files dialog box. A file R3ta_hints.txt with column hints for several tables is delivered with the Installation Master DVD. you specify the table name followed by one or more column names. 2. For more information. see Processing Split Tables.TSK <table>_IDX.TSK DRP_<table>_IDX. Only create a temporary index if you want to perform an unsorted unload.4 4. The file has to be located in the directory in which you start R3ta. use the REBUILD INDEX job to speed up the index creation process. Using Hints With the file R3ta_hints.

Depending on your database platform it might be necessary to modify the create index statement in the DDL<DBTYPE>.cmd –l <table>_IDX. For this purpose you need to create certain files. the dbcodepage is 1100.IBM DB2 for Linux and UNIX and Windows. Only valid for: Oracle | Make sure that you do not lock the table while creating the temporary index.TPL and add the highlighted key words to the creind statement: creind: CREATE &unique& INDEX &ind name& ON &tab name& ( /{ &fld name& /-.TPL file. Edit the file DDLORA.STR) ■ Updating database statistics (…) 2010-03-16 PUBLIC 29/126 .TPL file. Depending on your database platform it might be necessary to modify the create index statement in the DDL<DBTYPE>. the dbcodepage is 4102 (Big Endian) or 4103 (Little Endian). STR and TSK files created by R3ta to create the index. Call R3load as user <sapsid>adm with the following parameters: R3load –dbcodepage <source system’s dbcodepage> –i <table>_IDX.4 Preparing the Export Optionally you can prepare the source system for the export using R3load and Jload. If your source system is a Unicode system. Only valid for: IBM DB2 for i5/OS. The following steps are performed: ■ Creating the export directory structure ■ Creating database structure files (*.4 4.IBM DB2 for z/OS.IBM DB2 for z/OS.MS SQL Server | 2.IBM DB2 for Linux and UNIX and Windows. 4. 1.MS SQL Server | Make sure that you do not lock the table while creating the temporary index.MaxDB. End of: Oracle | 3.4 Database Independent System Copy Preparing the Export You can use the R3load cmd.MaxDB.log If your source system is a non-Unicode system. End of: IBM DB2 for i5/OS. /} ) TABLESPACE &tablespace& STORAGE (INITIAL &init& NEXT &next& MINEXTENTS &minext& MAXEXTENTS &maxext& PCTINCREASE &pctinc& ) NOLOGGING COMPUTE STATISTICS PARALLEL ONLINE. so as to enable parallel export/import.

EXT. For more information. NOTE For more information. SAPinst includes a SAPinst GUI and a GUI server. see the documentation Migration Monitor – User’s Guide in the MIGMON. This section describes a standard export where SAPinst. In any case make sure that the dump directory and its subdirectories and files are accessible for user <sapsid>adm of the target system. the complete export directory with its structure and the generated files. Procedure 1.4 4.SAR archive on the SAP Installation Master DVD.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. which both use Java. ■ The export dump directory can be shared and thus made accessible on the target host.5 Exporting the Source System Using SAPinst Here you can find information about how to run SAPinst to perform the export on the source system: ■ Running SAPinst on UNIX or Windows to Perform the Export [page 30] ■ Running SAPinst on System i to Perform the Export [page 41] 4. you can instead perform a remote system copy with SAPinst.DBSIZE. ■ Export and import processes should run in parallel during the system copy process. see Running SAPinst on UNIX or Windows to Perform the Export [page 30]. have to be transferred to the target host. As soon as the export preparations have finished successfully. SAPinst GUI. If required. 4. which are required for building up the target system.XML) These export preparations are required. where SAPinst GUI is running on a separate host from SAPinst and the GUI server. You run SAPinst to perform the service Export Preparation. 2. 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. For more information. and the GUI server are running on the same host. see Performing a Remote Installation with SAPinst [page 115]. ■ Copy the export dump directory manually to the target host.5 Database Independent System Copy Exporting the Source System Using SAPinst ■ Size calculation for the target database (*. if: ■ You want to build up the target system to the point where the database load starts.5. Note the following about SAPinst: 30/126 PUBLIC 2010-03-16 . before the export of the source system has finished.

SAPinst GUI and the GUI server are also started. SAPinst uses /tmp as default installation directory. ■ The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. ● Click the icon for the SAPinst output window located in the Windows tray and choose File Exit . You can safely delete them. ■ SAPinst creates a subdirectory for each installation service. TMP. SAPinst finds the temporary directory by checking the value of the environment variables TEMP.out. Directories with the name sapinst_exe. If no value is set for these variables. Only valid for: Windows | ■ If you want to terminate SAPinst and the SAPinst Self-Extractor. called <sapinst_instdir> \<installation_service> which is located below %ProgramFiles%\sapinst_instdir. you can terminate SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C . SAPinst tries to create sapinst_instdir in the directory defined by the environment variable TEMP. If required. or SystemRoot). TMPDIR. TMP. which might be useful if an error occurs. you can also find the SAPinst Self-Extractor log file dev_selfex.4 4. and which is located directly below the Program Files directory.xxxx sometimes remain in the temporary directory. 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 | 2010-03-16 PUBLIC 31/126 . These executables are deleted after SAPinst has stopped running. End of: Windows | CAUTION If SAPinst cannot find a temporary directory. ■ The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP. These executables are deleted again after SAPinst has stopped running.5 Database Independent System Copy Exporting the Source System Using SAPinst ■ When you start SAPinst. Only valid for: UNIX | ■ SAPinst normally creates the installation directory sapinst_instdir directly below the temporary directory. where it keeps its log files.xxxxxx. SAPinst GUI connects using a secure SSL connection to the GUI server and the GUI server connects to SAPinst. or TMPDIR. the installation terminates with the error FCO-00058. If SAPinst is not able to create sapinst_instdir directly below the Program Files directory. In the temporary directory. End of: UNIX | Only valid for: Windows | ■ SAPinst normally creates the installation directory sapinst_instdir.

During the export some archives are written to the program subdirectories and SAPinst aborts if there is not enough space. and at least 130 MB of free space in the installation directory for each Java installation option.4 4. some archives are written to the program subdirectories and SAPinst aborts if there is not enough space. 32/126 PUBLIC 2010-03-16 . 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. End of: UNIX | Only valid for: Windows | You are logged on to your host as user with the required rights and privileges that authorize you to install the SAP system with the SAPinst tool. End of: Windows | ■ Make available the Master Installation DVD. End of: DB2 UDB for UNIX and Windows | Only valid for: UNIX | ■ Before starting the export. see section Required User Authorization for the Installation in your installation guide.TMP.sap.5 Database Independent System Copy Exporting the Source System Using SAPinst Prerequisites CAUTION Make sure that you shut down all SAP Application Servers before the export.com/patches and copy it to directory /usr/sap/<>/SYS/exe/ run/. or TMPDIR to another directory with 200 MB free space for the SAPinst executables. In addition. The database must still be running. ■ You need at least 60 MB of free space in the installation directory for each ABAP installation option. For more information. the target system might be inconsistent. you can set one of the environment variables TEMP. 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 need 60-200 MB free space for the SAPinst executables. Only valid for: UNIX | If you cannot provide 200 MB free space in the temporary directory. End of: Windows | Only valid for: DB2 UDB for UNIX and Windows | ■ Before you start the export of the existing SAP System. ■ Only valid for: UNIX | You are logged on to your host as user root. you have to download the current version of R3szchk at http://service. During the export. Otherwise. End of: UNIX | ■ Only valid for: Windows | Before starting the export steps on the central instance of the source system.

■ Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime Environment (JRE). the following causes an error: $ cd /sapcd2/IM_HPUX_IA64 $ /sapcd2/IM_HPUX_PARISC/sapinst To correct this. by using a crontab entry.4 4. set the environment variable TEMP./sapinst SAPinst creates a directory called sapinst_instdir. or TMPDIR point. make sure that the PATH variable points to a JDK/JRE for AIX 64-bit. or TMPDIR. EXAMPLE For example.5 Database Independent System Copy Exporting the Source System Using SAPinst ■ Make sure that the DISPLAY environment variable is set to <host_name>:0. TMP. ■ Using an alternative installation directory If you want to use an alternative installation directory. End of: AIX | End of: UNIX | For more information about SAPinst. ■ Only valid for: AIX | If the operating system is AIX 64-bit. and Performing a Remote Export Using SAPinst [page 114]. TMP. ■ Make sure that your current working directory is not an IM_<OS> directory belonging to another operating system. Interrupted Installation with SAPinst [page 112]. enter the following: $ cd /sapcd2/IM_HPUX_PARISC $ /sapcd2/IM_HPUX_PARISC/sapinst End of: UNIX | 2010-03-16 PUBLIC 33/126 . ■ 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. which is the current working directory for your installation.0. below the temporary directory of your operating system. for example. see Using SAPinst GUI [page 111]. Start SAPinst from the SAP Installation Master DVD as follows: Only valid for: UNIX | Choose one of the following ways: End of: UNIX | Only valid for: UNIX | ■ Using the default installation directory (recommended) Enter the following commands: cd <Installation_Master_DVD>/IM_<OS> . where <host_name> is the host where the SAPinst GUI is displayed. Procedure 1.

You get an error message if one of these ports is already in use by another service.XML) Mandatory step for database-independent system copy procedure. the default ports 21200 and 21212 are used for communication between SAPinst.5 Database Independent System Copy Exporting the Source System Using SAPinst Only valid for: Windows | ■ Double-click sapinst. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*. End of: Windows | NOTE During the installation. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*. For more information. SAPinst uses port 21200 to communicate with the GUI server. CAUTION Make sure that you choose the system copy options exactly in the order they appear for each system variant. see Database-Specific System Copy procedure [page 51] or Database-Independent System Copy [page 21].exe from the following path: <DVD_drive>:\DATA_UNITS\IM_WINDOWS_<platform> SAPinst GUI normally starts automatically by displaying the Welcome screen.EXT. 3.STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*. enter the following command: sapinst —p.exe SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui> 2. The following table provides an overview about the available installation options available for the export: Export Services for a Central System Export Service Remarks Export Preparation NOTE You do not perform this step if you use the database-specific method. choose Software Life-Cycle Options System Copy <database> Source System <Distribution option> Based on <technical stack> .STR) 34/126 PUBLIC 2010-03-16 . For a list of all available SAPinst properties. Database Instance Export Optional step for preparing the export.4 4. GUI server. and SAPinst GUI. Enter the following command in a single line: sapinst. Select the corresponding system copy option from the tree structure according to the sequence of the process flow for the database-specific or the database-independent system copy procedure. open a command prompt and change to the required directory as follows: <DVD drive>:\IM_WINDOWS_<platform>. The GUI server uses port 21212 to communicate with SAPinst GUI.DBSIZE. On the Welcome screen. In this case.

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

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. This group is created first by SAPinst starting from NW 7. SAPinst will create this group during startup before product catalog list will be displayed.5.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. Verify /etc/group file and check if sapinst group exists and OS users are members of this group. ● Continue the export by choosing Retry. see Using SAPinst GUI [page 111].5 Database Independent System Copy Exporting the Source System Using SAPinst ● Displays a dialog that informs you about the error. Continue with the export. Reason: Only members of sapinst UNIX group can access the installation directory. Swing). Solution: Associate <sid>adm and ora<sid> OS users with sapinst group manually if this association is missing. If sapinst group does not exist yet. Prerequisites To prepare the system for SAPinst and SAPinst GUI you need to do the following: 36/126 PUBLIC 2010-03-16 . Only valid for: UNIX | ■ System Copy . ● Try to solve the problem.4 4. Edit /etc/group file and associate OS users with sapinst group.2 Running SAPinst on System i to Perform the Export 4.0 SR1.5. you must install the JDK on a Windows host to perform the installation with SAPinst. Interrupted Installation with SAPinst [page 112]. start SAPinst. and Performing a Remote Export Using SAPinst [page 114].2. Only valid for: IBM i5/OS | 4. ● Abort the export by choosing OK. You can now: ● Directly view the log file by choosing View Logs. End of: UNIX | For more information. Since System i does not provide a graphical user interface. Standard Edition) with graphical capabilities (AWT.

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

Only valid for: SAP CRM.SAP NetWeaver. End of: SAP CRM. 7.SAP SRM | 3.SAP NetWeaver.SAP SRM | Enter the command CRTUSRPRF USRPRF(SAPINSTUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('Test User for SAP Installation') SPCAUT(*USRCLS) LANGID(ENU) CNTRYID(US) CCSID(500). enter the password of the user QSECOFR on your System i. enter the password SAP.SAP ERP. Only valid for: SAP CRM.SAP SRM | NOTE The user name SAPINSTUSR and the password SAP are used as examples in the procedures. Procedure Only valid for: SAP CRM. End of: SAP CRM.5 Database Independent System Copy Exporting the Source System Using SAPinst NOTE This is different to other installations on System i. 2. In former installation documentation. End of: SAP SCM | System i: Only valid for: SAP CRM.SAP NetWeaver.SAP NetWeaver.4 4. End of: SAP SCM | 4.SAP ERP.SAP NetWeaver. Only valid for: SAP CRM. Only valid for: SAP SCM | Assign the new user QSECOFR to the group Administrators.SAP SRM | In the fields Password and Confirm password.SAP SRM | 38/126 PUBLIC 2010-03-16 . enter your installation user name QSECOFR. Only valid for: SAP SCM | In the field User name.SAP ERP. we used the user SAPINST.SAP ERP.SAP SRM | Assign the new user SAPINSTUSR to the group Administrators. End of: SAP CRM. Create a local user. in future releases SAP has introduced a group called SAPINST on System i which conflicts with the previously recommended user SAPINST.SAP NetWeaver. we recommended that you create user SAPINST or SAPINSTUSR.SAP NetWeaver. enter your installation user name.SAP ERP. For other installations.SAP ERP. End of: SAP SCM | ■ The Windows user account must have administrator rights on the Windows installation host.SAP SRM | 8. Only valid for: SAP SCM | In the fields Password and Confirm password. for example.SAP ERP.SAP ERP.SAP SRM | Windows: 1.SAP ERP.SAP NetWeaver.SAP SRM | 5.SAP SRM | In the field User name. Deselect User must change password at next logon.SAP NetWeaver. SAPINSTUSR.SAP NetWeaver. End of: SAP CRM. However. End of: SAP SCM | 6.SAP ERP. End of: SAP CRM. However for SCM. you need to use the user QSECOFR because the liveCache client software has to be installed by this special user.

For more information. For more information about how users are prepared. Procedure 1.SAP NetWeaver. code page problems might prevent TMKSVR processes from starting. but has to install the product on System i.5.4 4. After the installation. This means that all actions required for System i are initiated remotely on Windows but executed locally using the TMKSVR.SAP ERP. The TMKSVR has to be installed and an installation share has to be created on all System i hosts where instances of an SAP system should be installed. End of: SAP SCM | CAUTION You should not set the system variable QIBM_PASE_CCSID. Only valid for: SAP CRM. see Preparing a Windows User Account and System i User Profile [page 37]. In addition. ■ The Installation Master DVD must be inserted in the DVD drive of your Windows host. SAPinst is running on Windows.2.5 Database Independent System Copy Exporting the Source System Using SAPinst Only valid for: SAP SCM | To change the user QSECOFR. You should leave this variable empty! 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. ■ Make sure there is no system variable LANG defining a LOCAL.SAP SRM | 2010-03-16 PUBLIC 39/126 . End of: SAP CRM. The communication is done using TCP/IP. Otherwise. Prerequisites ■ An FTP server running on System i ■ You must prepare a user.3 Installing TMKSVR and Creating an Installation Share The TMKSVR is the interface between System i and Windows for the installation with SAPinst. Log on to your Windows host as the installation user. which is done automatically by the TMKSVR. an installation share on the System i host needs to be created and mapped to the Windows installation host. you can revert the user profile QSECOFR back to the old values.SAP ERP.SAP SRM | NOTE This user must have the same user ID and password as the user that you are using for the installation on System i (a user with administrator rights similar to QSECOFR).SAP NetWeaver. see Preparing a Windows User Account and System i User Profile [page 37]. enter the command CRTUSRPRF USRPRF(QSECOFR) LANGID(ENU) CNTRYID (US) CCSID(500).

this user must be QSECOFR). Run SETUP.SAP SRM | Figure 2: End of: SAP CRM. The following dialog box appears: Only valid for: SAP CRM. You can start the setup program by double-clicking on it in the Windows Explorer.EXE from the directory IM_OS400_PPC64\TMKSVR on the DVD containing the installation package.5 Database Independent System Copy Exporting the Source System Using SAPinst 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 System i. Enter the following values: 40/126 PUBLIC 2010-03-16 .SAP ERP.SAP SRM | Only valid for: SAP SCM | Figure 3: End of: SAP SCM | 3.4 4. End of: SAP SCM | 2.SAP NetWeaver.SAP ERP. For SCM.SAP NetWeaver.

■ TMKSVR Instance Port (also referred to as the Dispatcher Port): Leave the value at 59975.SAP NetWeaver.SAP NetWeaver. Otherwise. During installation. End of: SAP SCM | ■ TMKSVR instance number: Leave the value at 0. This procedure tells you how to run SAPinst to install one or more SAP instances. End of: SAP CRM. ■ Only valid for: SAP CRM.SAP SRM | System i Administrator (QSECOFR or similar): Enter the System i user. For more information. SAPinst creates the installation directory \usr\sap\sapinst on System i. For more information.5. For more information. see Preparing a Windows User Account and System i User Profile [page 37]. with <nn> being the instance number (for example. TMKSVR00). You can map the share now to your Windows PC or let SAPinst map it during the installation. see Preparing a Windows User Account and System i User Profile [page 37].4 4. Result The installation uses FTP to install and starts the TMKSVR on System i. a library named TMKSVR<nn> is created. It describes an installation where SAPinst GUI and SAPinst server are running on the same Windows host.SAP ERP. if possible.SAP SRM | Only valid for: SAP SCM | ■ System i Administrator (QSECOFR): Enter the System i user. which is a synonym for “export an SAP system”. Prerequisites CAUTION Make sure that you shut down all SAP Application Servers before the export.PDF on the DVD in directory IM_OS400_PPC64 \TMKSVR. 2010-03-16 PUBLIC 41/126 . see the documentation INSTALL.4 Starting SAPinst on System i CAUTION This section refers to “installation of an instance”. The database must still be running.5 Database Independent System Copy Exporting the Source System Using SAPinst ■ System i Hostname: Enter the name of the System i host where you want to install TMKSVR. Only change this port number if you encounter problems during installation because the port is in use. the target system might be inconsistent.SAP ERP. A NetServer share named ROOTBIN is created on the System i host.2. End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | Only valid for: IBM i5/OS | 4.

■ The Windows host is set up.. GUI server and SAPinst GUI. the default ports SAPinst 21212 and 21213 are used for communication between SAPinst. enter the following command: sapinst -p 3. ■ The users required for the installation are prepared.exe from the following path: <Mapped drive>:<copied . see Preparing a Windows User Account and System i User Profile [page 37]. For more ■ information. 42/126 PUBLIC 2010-03-16 .. Log on to the Windows host as the installation user.. Enter your values. open a command prompt and change to the required directory as follows: <Mapped drive>:<copied .5 Database Independent System Copy Exporting the Source System Using SAPinst TMKSVR is up and running: WRKACTJOB SBS (TMKSVR00) (there must be a DISPATCH job). For more information.4 4. The SAPinst/TMKSVR – Session Parameters dialog box appears and prompts you for the target System i parameters. DVD>\IM_OS400_PPC64 NOTE ● During the installation.. DVD>\IM_OS400_PPC64 Enter the following command in a single line: sapinst. For more information.exe SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to sapinst_gui> ● For a list of all available SAPinst properties. SAPinst uses port 21200 to communicate with the GUI server. Start SAPinst from the SAP Installation Master DVD in one of the following ways: ■ If using the default installation directory (recommended) by double-clicking sapinst. In this case. ■ Make sure that the JAVA_HOME environment variable is set correctly on your Windows host. see Preparing a Windows User Account and System i User Profile [page 37]. see Installing TMKSVR and Creating an Installation Share [page 39]. 2. see Preparing the Windows Host for the SAP System Installation [page 36]. Procedure 1. You get an error message if one of these ports is already in use by another service. For more information.

Select the corresponding installation service from the tree structure according to the sequence of the process flow for one of the following precedures: ■ Database-Specific System Copy [page 51] ■ Database-Independent System Copy [page 21] CAUTION 6. In the Welcome screen. Make sure that you choose the installation services exactly in the order they appear for each system variant.DBSIZE.XML) 2010-03-16 PUBLIC 43/126 . choose Software Life-Cycle Options System Copy <your database> Source System <System Variant> Based on <AS ABAP and AS Java | AS Java | AS ABAP> .4 4. 5. Optional step for preparing the export.STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*. The SAPinst GUI now starts automatically by displaying the Welcome screen.5 Database Independent System Copy Exporting the Source System Using SAPinst Figure 4: 4.EXT. 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 You do not perform this step if you use the database-specific method. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.

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.XML) Database Instance Export Mandatory step for the database-independent system copy procedure.STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*.DBSIZE. choose Next. 44/126 PUBLIC 2010-03-16 . Follow the instructions in the SAPinst input dialogs and enter the required parameters.XML) ■ Exports the database content Export Preparation 7.STR) ■ Updates database statistics(…) ■ Calculates the size of the target database (*. Choose Database and Central Instance Export 2. copy the generated files into the SAPinst installation directory as soon as it has been created by SAPinst: 1. The installation directory has been created as soon as the first input screen appears.DBSIZE.EXT. use the database-specific SAPinst performs the following steps: method.5 Database Independent System Copy Exporting the Source System Using SAPinst Export Service Remarks Database Instance Export NOTE You do not perform this step if you use the database-specific method. CAUTION You must choose Typical when performing a system copy with database tools. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*. ■ Creates the export directory structure with label files ■ Creates database structure files (*STR) ■ Updates database statistics ■ Calculates the size of the target database (*EXT. 3.EXT. Choose Next NOTE 9. Choose Next. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.DBSIZE. the database-specific method. After you have selected the required installation service. NOTE You need to perform this step on the database instance ■ You do not perform this step if you host. NOTE You do not perform this step if you use You need to perform this step on the database instance host. Mandatory step for database-independent system copy procedure. 8.4 4. If you generated SQL files with DDL statements (see Generating DLL Statements [page 25]).

SAPinst: ● Stops the installation. ■ If an error occurs during the dialog phase.log and make sure that all tables in the TSK file <package>. 2010-03-16 PUBLIC 45/126 . Troubleshooting CAUTION If an export process aborts due to a hardware failure (for example. After you have entered all required input parameters.TOC. Remove the dump files <package>. When the installation has successfully completed. ● Displays a dialog that informs you about the error. EXAMPLE For example. Finally you must abort the installation with OK and try to solve the problem. End of: IBM i5/OS | End of: IBM i5/OS | 4. SAPinst starts the installation and displays the progress of the installation. the TOC file <package>.5 Database Independent System Copy Exporting the Source System Using SAPinst NOTE For more information about input parameters in SAPinst. ■ If an error occurs during the processing phase. ● Try to solve the problem. ● Displays a dialog that informs you about the error. You can now directly view the log file by choosing View Logs. the screen Finished installation is displayed. position the cursor on the parameter field and choose F1 .3 Restarting R3load Processes The state file allows package states to be manually updated to restart failed R3load processes. if package processing failed and the package state has the value –. the state can be set to 0 and processing of the package is restarted. set the package state from – to 0. Procedure ■ To restart package processing. see Interrupted Installation with SAPinst [page 112].<nnn>. ● Retry the installation by choosing Retry. ● Abort the installation by choosing OK. file system full.4 4. operating system crash). you have to repeat the export of the complete package. the log file <package>. You can now directly view the log file by choosing View Logs. For more information. SAPinst: ● Stops the installation.*TSK* have the status flag 'xeq' or 'err' set.5. power outage.

4 4.5 Database Independent System Copy Exporting the Source System Using SAPinst ■ To skip package processing.properties from '+' to '0'. there is nothing to do. If one of the corresponding R3load processes (export or import) is still running. you can set the status in the export_state. there is nothing to do. ● If the export was completed successfully but the import was cancelled when loading the table content. First of all. To continue with the system copy proceed as follows: ■ If both the import and the export are completed successfully.) ■ If the package is currently being processed (the package state is ?). you need to cancel the R3load process. proceed as follows: ● If the errors in export and import relate to the same table.properties from '-' to '+'. because it can cause inconsistent data files or database content. 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'. set the status ◆ for export_state. Restarting R3load Processes Using the Socket Option There are four possible situations where an R3load restart may be required. ■ Sockets only: You cannot restart processes. (This is not recommended. but the export was cancelled with errors. ■ If the export was completed successfully. The entry in the *state* file also must be set from '+' to '0'. Then restart SAPinst to continue with the system copy. 46/126 PUBLIC 2010-03-16 . cancel it as well. ■ When the import was completed successfully.properties from '+' to '0' ◆ for the TSK file of the export from 'ok' to 'err' ■ If both the export and the import are cancelled with errors. then any manual modifications of the package state are ignored. but the import is cancelled with errors. That means that in the import TSK file the status for TAB_2 must be set from 'ok' to 'err'. set the status for export_state. More Information See also R3load Processes Using the Migration Monitor [page 95]. 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). set the package state from 0 or – to +. proceed as follows: ● If the export was successful but the import was cancelled when creating the index or the primary key. ● If the errors relate to different tables.

You prepare the central instance host and the database instance host for the installation of the corresponding instances of your target system as described in the installation guide for your SAP system solution. see Preparing the Export [page 29]) on the source system. you install the target systemInstalling the Target System [page 48].6 Database Independent System Copy Setting Up the Target System 4. Distributed System or High-Availability System Perform the following steps on the relevant installation hosts of your target system: 1. you 2010-03-16 PUBLIC 47/126 . For more information. You install the target system. If you use the FTP Exchange option during the export (transfer type FTP. You prepare the central system host for the installation of your target system as described in the installation guide for your SAP system solution. End of: High Availability | 3. 3. on (the) dialog instance host(s).6 Setting Up the Target System Purpose You use SAPinst to install the target system and import the database files that you have exported from the source system. If required. you perform the following steps: 1. 2. Process Flow Central System Perform the following steps on the central system host: 1. 2. Only valid for: High Availability | You install the central services instance for the target system as described in the installation guide for your SAP system solution. you make sure that you have transferred all files that have been generated in step Preparing the Export [page 29] on the source system. End of: High Availability | 2. You perform the following steps on the database instance host: ■ If you have already prepared the export (for more information. communication type Exchange Directory on the screen SAP SystemCommunication Parameters for Export). Only valid for: High Availability | You also prepare the central services instance host.4 4. you install additional dialog instance(s) as described in the installation guide for your SAP system solution. If you did not prepare the export on the source system. communication type Exchange Directory on the screen SAP SystemCommunication Parameters for Export). If you use the FTP Exchange option during the export (transfer type FTP. If you have already prepared the export (for more information. you perform the following steps: 1. see Preparing the Export [page 29]) on the source system because you want to perform the export and import in parallel. see Installing the Target System [page 48].

2. make sure that you have transferred the files. If required. see Installing the Target System [page 48]. You install the database instance of the target system. SAPinst recognizes this automatically and skips the related steps.0 SR3. On the central instance host. which have been generated in step Preparing the Export [page 29] on the source system. see Preparing the Export [page 29]) on the source system. End of: UNIX | NOTE As of SAP NetWeaver 7.6. look at the file DBSIZE. see Installing the Target System [page 48]. If the database software has already been unpacked or installed. End of: Windows | Only valid for: UNIX | Make sure there is enough free space on the target system for the database load.0.6 Database Independent System Copy Setting Up the Target System 4. 4.XML located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE>. 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. To find out the size of the export and the sizes of the tablespaces or dbspaces that will be created. RELOAD is no longer available as an executable installation service. For more information. you install the database instance of the target system. 5.XML located in the directory <EXPDIR>/DB/<DATABASE>. Procedure 1. To find out the size of the export and the sizes of the tablespaces or dbspaces that will be created. End of: IBM DB2 for Linux and UNIX and Windows | 48/126 PUBLIC 2010-03-16 . ■ If you did not prepare the export (for more information.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. For more information. you install the central instance of the target system. on (the) dialog instance host(s). look at the file DBSIZE. but is performed automatically by SAPinst.4 4. you install additional dialog instance(s) as described in the installation guide for your SAP system solution. You prepare the target system host as described in the installation guide of your SAP solution based on SAP NetWeaver 7.

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. 3. End of: IBM DB2 for Linux and UNIX and Windows | CAUTION 6. Enlarge the database or database container. ■ Do not create the installation directory (for example.0 SR3. the data import into the target system might abort because of missing space in the database tablespace or dbspace.4 4. in which the table DYNPSOURCE will be created in the target database. enter the path to the export directory <EXPDIR>. you choose the option Standard System Copy/Migration (load-based): The SAP data dump from the MIGRATION EXPORT CD image that you created during the export is loaded in the newly installed SAP system database. On the Welcome screen of the SAP Installation Master DVD. navigate to the following folder according to the requirements of your target system: Software Life-Cycle Options System Copy <database> Target System <Distribution option: Central System / Distributed System / High-Availability System> Based on <Stack option> AS ABAP and Java / AS Java / AS ABAP> . 2010-03-16 PUBLIC 49/126 . If you want to perform export and import in parallel. 4. The required size for the table will be fifteen times larger than in the non-Unicode source system. choose the option Parallel Export / Import. On this screen. you follow the instructions in the SAPinst input dialogs and enter the required parameters up to the screen Database . ■ The option Deferred Table Creation is not supported for load-based system copies for SAP systems that are not based on SAP NetWeaver 7.6 Database Independent System Copy Setting Up the Target System 2. You start SAPinst as described in the installation documentation for your SAP solution based on SAP NetWeaver 7. 7.Select the Database Instance Installation Method. To install the target system. 5. You run the installation service(s) required for your system copy in the sequence they are listed in the specific folder and according to process flow in Setting Up the Target System Using SAPinst [page 47].0 SR3 or higher. Only valid for: IBM DB2 for Linux and UNIX and Windows | CAUTION ■ Make sure that you take the information about automatic storage into consideration that is provided in section Running SAPinst in the appropriate installation guide. enter the Migration Key on the screen Database Import. If you perform a heterogeneous system copy. When SAPinst displays the DVD / CD browser window and asks for the Export Migration CD.

6 Database Independent System Copy Setting Up the Target System NOTE 8. For more information about restarting failed R3load processes. You must have run the service Prepare the Export on the source system [page 29]. NOTE If you have to restart the import after an error. just restart SAPinst. The import continues with the table that was not imported successfully. see Restarting R3load Processes [page 45]. Complete the installation as described in the installation documentation for your SAP component. 50/126 PUBLIC 2010-03-16 . if you want to use the option parallel export/ import for the installation of the target system.4 4.

Only valid for: Windows | Follow the instructions on the SAPinst screens until you are requested to perform the database backup/restore. If required. End of: Windows | 2. Process Follow the sequence of steps described in the process flows below for a: ■ Central System ■ Distributed System ■ High Availability System Central System For performing the export for a central system. Follow the instructions on the SAPinst screens until SAPinst requests you to install the database software and to perform the database backup/restore. You generate the control file structure for the target database [page 54].5 Database-Specific System Copy 5 Database-Specific System Copy The following sections describe system copy procedures that base on database-specific methods. You install the database software. you need to proceed as follows on the central system host: Process Flow on the Source System (Export) 1. Only valid for: Windows | Process Flow on the Target System You install the database software as described in the installation guide of your SAP solution. Only valid for: UNIX | You prepare the target system [page 59]: 1. 2. 3. 1. For more information about methods available for your database. You create the database file system (if not yet existing). you create a backup of the source database [page 58]. 2010-03-16 PUBLIC 51/126 . see Planning [page 11] and the SAP Notes describing the homogeneous system copy for your database system. 2. End of: UNIX | 3. Database-specific methods are not available for all database systems.

you create the database file system (if not yet existing). proceed as follows: Process Flow on the Source System (Export) 1. on the database instance host. you have to restart SAPinst as described in the installation guide of your SAP solution.1 Database-Specific System Copy Oracle-Specific Procedure NOTE If required. To complete the system copy. On the database instance host. End of: Windows | 4. you have to restart SAPinst as described in the installation guide of your SAP solution. follow the instructions on the SAPinst screens until SAPinst requests you to install the database software and to perform the database backup/restore. you can create a homogeneous copy of an Oracle database by copying database files. The source of 52/126 PUBLIC 2010-03-16 . To complete the system copy. 2. you install the database software. Only valid for: Windows | Process Flow on the Target System 1. follow the instructions on the SAPinst screens until you are requested to perform the database backup/restore. On the database instance host.1 Oracle-Specific Procedure Purpose In an SAP system environment. End of: Windows | 4. you have to perform the follow-up activities [page 89]. you create a backup of the source database [page 58]. you have to perform the follow-up activities [page 89]. End of: Windows | 2. you generate the control file structure for the target database [page 54]. 2. 3.5 5. NOTE If required. Only valid for: UNIX | You prepare the target system [page 59]: 1. This method is suitable for creating an exact copy of an existing database. Only valid for: Oracle | 5. Distributed System or High Availability System To perform the export for a distributed or high-availability system. you install the database software as described in the installation guide of your SAP solution. Only valid for: Windows | On the database instance host. On the database instance host. On the database instance host. End of: UNIX | 3. On the database instance host of the source system. If required.

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

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

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. The tool creates the files CONTROL. check the log file: <INSTDIR>/ora.1 Database-Specific System Copy Oracle-Specific Procedure . entries of CONTROL. Example for Windows In the following example for Windows.sh –generateFiles —targetSid <TARGET_DBSID> —password <system's password> —listenerPort <listener port> ● On Windows: ora_br_copy.brcopy.SQL written in bold should be compared to the trace file: REM ==================================================================== REM CONTROL. To ensure this. the database must be up and running.SQL control file using the CONTROL.5 5. CONTROL./ora_br_copy. this command must not contain the parameter —forceLogSwitches.0 x86 CONNECT / AS SYSDBA STARTUP NOMOUNT CREATE CONTROLFILE REUSE SET DATABASE "NEW" 2010-03-16 PUBLIC 55/126 . and performs the required log switches.TRC trace file as follows.log 5.ora in your installation directory.TRC and init<targetSID>.bat –generateFiles —targetSid <TARGET_DBSID> —password <system's password> —listenerPort <listener port> NOTE During the online backup. update the CONTROL.SQL.SQL REM REM SAP AG Walldorf REM Systeme. if necessary. Verify and. NOTE If an error occurs.

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

1 Database-Specific System Copy Oracle-Specific Procedure 'D:\ORACLE\NEW\SAPDATA1\IMS700_4\IMS700.sql file: shutdown immediate. The numbers must be greater than or equal to the corresponding numbers in the trace file. NOTE In the above example for Windows.DATA11'.DATA5'.DATA7'. add the following lines at the bottom of the control.DATA8'.. 'D:\ORACLE\NEW\SAPDATA4\IMS700_11\IMS700. Changes to be made 1. ALTER DATABASE OPEN RESETLOGS.DATA1' . too. 'D:\ORACLE\NEW\SAPDATA2\IMS700_7\IMS700.DATA9'.DATA1' SIZE 350M REUSE AUTOEXTEND OFF. If you want to upgrade your database from 32-bit to 64-bit.sql written in bold should be compared to the trace file.log @?/rdbms/admin/utlirp. 3. 'D:\ORACLE\NEW\SAPDATA2\IMS700_8\IMS700.5 5.DATA1'. 'D:\ORACLE\NEW\SAPDATA2\IMS700_5\IMS700. The changes to be made are valid for UNIX. 'D:\ORACLE\NEW\SAPDATA3\IMS700_10\IMS700. 2. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE 'D:\ORACLE\NEW\SAPDATA3\TEMP_1\TEMP. Group 2 ( … 2010-03-16 PUBLIC 57/126 . GROUP 1 ( 'D:\ORACLE\NEW\ORIGLOGA\LOG_G11M1. 'D:\ORACLE\NEW\SAPDATA2\ROLL_1\ROLL.DATA10'. 'D:\ORACLE\NEW\MIRRLOGA\LOG_G11M2.. MAXLOGFILES 255 . startup restrict spool utlirp.DBF'. entries and values of control. 'D:\ORACLE\NEW\SAPDATA2\IMS700_6\IMS700. 'D:\ORACLE\NEW\SAPDATA1\IMSUSR_1\IMSUSR. 'D:\ORACLE\NEW\SAPDATA2\IMS700_9\IMS700.DATA6'.DATA4'.sql spool off alter system disable restricted session.DBF' ) SIZE 50M.

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

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

2. choose the required installation service: SAP NetWeaver 7. If they do not exist. choose Homogeneous System Copy (Backup/ Restore). If necessary.5 5.. 2.0 Support Release 2 Software Life-Cycle Options System Copy Oracle Target System <Central System | Distributed System | High-Availability System> .. Proceed until SAPinst stops to restore the database files on the target system. 3. Please proceed as follows:. create the following directories on the target system: ■ UNIX: ● /oracle/<TARGET_DBSID>/mirrlog<x> ● /oracle/<TARGET_DBSID>/origlog<x> ● /oracle/<TARGET_DBSID>/sapdata<x> ● /oracle/<TARGET_DBSID>/sapreorg ● /oracle/<TARGET_DBSID>/saparch ● /oracle/<TARGET_DBSID>/oraarch ● /oracle/<TARGET_DBSID>/saptrace ● /oracle/<TARGET_DBSID>/saptrace/background ● /oracle/<TARGET_DBSID>/saptrace/usertrace ● /oracle/<TARGET_DBSID>/origlogA/cntrl ● /oracle/<TARGET_DBSID>/sapdata1/cntrl ● /oracle/<TARGET_DBSID>/saparch/cntrl ● /oracle/<TARGET_DBSID>/sapcheck ■ Windows: ● <drive>:\oracle\<TARGET_DBSID>\mirrlog<x> ● <drive>:\oracle\<TARGET_DBSID>\origlog<x> ● <drive>:\oracle\<TARGET_DBSID>\sapdata<x> ● <drive>:\oracle\<TARGET_DBSID>\sapreorg ● <drive>:\oracle\<TARGET_DBSID>\saparch ● <drive>:\oracle\<TARGET_DBSID>\oraarch ● <drive>:\oracle\<TARGET_DBSID>\saptrace ● <drive>:\oracle\<TARGET_DBSID>\saptrace\background ● <drive>:\oracle\<TARGET_DBSID>\saptrace\usertrace ● <drive>:\oracle\<TARGET_DBSID>\origlogA\cntrl ● <drive>:\oracle\<TARGET_DBSID>\sapdata1\cntrl ● <drive>:\oracle\<TARGET_DBSID>\saparch\cntrl 60/126 PUBLIC 2010-03-16 . On the Welcome screen. The following message is displayed: SAPinst now stops the installation. extract the Oracle stage archives manually and install the Oracle Software as described in the installation documentation for your SAP solution.1 Database-Specific System Copy Oracle-Specific Procedure 1. When SAPinst prompts for the installation type. 3.

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. enter the following command: chown ora<target_dbsid>:dba<directory> End of: UNIX | 6. Administrators. SAP_<DBSID>_GlobalAdmin. 4. 3. 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. right-click the Oracle root directory and choose Properties. or SAP_<DBSID>_LocalAdmin to Full Control. To achieve this. choose Copy to copy the permission entries that were previously applied from the parent to this object. 6.4 Restoring the Database Files on the Target System Manually CAUTION If you do not use a backup but copy the database files directly from the source to the target system host. Deselect Allow inheritable permissions from the parent. Set the security settings for the built-in accounts and groups SYSTEM. Choose OK. Restore the database files on the target system either manually (see Restoring the Database Files on the Target System Manually [page 61]) or with BR*Tools (see Restoring the Database Files on the Target System with BR*Tools [page 62]).. Directories on UNIX: 2010-03-16 PUBLIC 61/126 .1 Database-Specific System Copy Oracle-Specific Procedure 4. see Creating an Offline Backup Manually [page 58]. 7. Under Security. ● <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. 2. Set the permissions for the above-mentioned accounts SYSTEM.. then proceed with SAPinst. and SAP_<SAPSID>_LocalAdmin (local installation) for all directories as follows: 1. In the next dialog. 7.. Procedure 1.5 5. Delete all other accounts. choose Advanced. 5. SAP_<SAPSID>_GlobalAdmin (domain installation). All directories must be owned by the user ora<target_dbsid>. For more information. In the Windows Explorer. 5.1. Administrators.

5 5. ■ On UNIX: Source and Target Directory Files CONTROL.SQL source: <INSTDIR> target: <SAPINST_INSTDIR> 62/126 PUBLIC 2010-03-16 . After you have copied the database files.1. Verify that the created directories and copied files have the owner ora<target_dbsid>. If necessary. make the corresponding changes in the files control.ora.5 Restoring the Database Files on the Target System with BR*Tools Procedure 1. The file names are specified by the parameter control_files of the 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>/dbs init<TARGET_DBSID>. Copy the following files from the source system host to the target system host by copying the listed files from the source directories to the target directories manually. Make sure that the control files are not restored. 5.sql and the init<DBSID>. and have the permissions 740.SQL source: <INSTDIR> target: <SAPINST_INSTDIR> source: <INSTDIR> target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database Only valid for: Windows | init<TARGET_DBSID>.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.ora NOTE The installation directory of the target system is normally located in the directory: %programfiles%\sapinst_instdir\NW04S\LM\COPY\ORACLE\SYSTEM\<system_variant> End of: Windows | 2. If required.ora file. belong to the group dba. 3. 4. remove them. make sure that the files on the source and target system are not located in different directories or drives.

2 SAP MaxDB-Specific Procedure In an SAP system environment.ora 2. For more information about BR*Tools. 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. The main prerequisite is that the corresponding BR*Tools logs (BRBACKUP detailed and summary log. 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).ora profile as follows: SYNTAX sqlplus /nolog connect / as sysdba create spfile from pfile. the postprocessing steps mentioned in this SAP Note are performed automatically by SAPinst. 4. Call the restore and recovery function of BR*Tools. In SAPinst you select the backup and restore method as the 2010-03-16 PUBLIC 63/126 .sap.2 Database-Specific System Copy SAP MaxDB-Specific Procedure Source and Target Directory Files init<TARGET_DBSID>.com/nw70 SAP NetWeaver 7. For more information about the required steps and prerequisites.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 . see help.5 5. see SAP Note 1003028. The source of the copy is a complete data backup of your source database. Create an Oracle spfile from init<TARGET_DBSID>. This method is suitable for creating an exact copy of an existing database. you can create a homogeneous copy of a SAP MaxDB database by using the backup and restore method. The SAPinst tool is used for the installation on the target system host as described in the installation documentation for your SAP solution. BRARCHIVE summary log) are copied manually from the source to the target system. exit 3.ora source: <INSTDIR> target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/ dbs ■ On Windows: Source and Target Directory Files CONTROL. In addition.SQL source: <INSTDIR> target: <SAPINST_INSTDIR> source: <INSTDIR> target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database init<TARGET_DBSID>.

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

CNMEDIA. In type of recovery you select Restore a medium. You make the backup medium available on the target host. End of: MaxDB | 2010-03-16 PUBLIC 65/126 . 2. 3. It takes some time for the database server to format the database volumes. After installation is completed you maintain the database connection for CCMS.5 5. You delete the entries from the following tables to make sure that information about the backup history for update statistics in the Computing Center Management System (CCMS) from the old system does not appear in the new system: CNHIST. 6. SAPinst stops before database initialization in the screen Perform Database Recovery and asks you to perform the data recovery. 6. If you do not already have a suitable recent complete SAP MaxDB backup. It initializes the database instance first. After the restore. Process 1. DBSTATHADA. You continue with SAPinst or restart it if you stopped it during the recovery.5 or higher on your system. You check the database instance in the admin state. SDBAADAUPD 5. You start the data recovery wizard from DBMGUI 1. The JAVA_HOME environment variable must point to the JRE directory. you check the state of the target database instance. DBSTATIADA..0 Lifecyle Management System Copy SAP MaxDB Target System <Central System | Distributed System | High-Availability System> . The recovery wizard does not start the recovery immediately. You do the following on the source system: 1. You specify the backup medium. Change the database state to online if it is not already in online state. 2. 4. To install the new system you start SAPinst as follows: SAP NetWeaver 7. DBSTAIHADA. 5. see SAP Note 588515. 4. You start the restore procedure. You do the following on the target system: 1.. DBSTATTADA. You choose Recovery Recovery with Initialization . you create a complete data backup using the DBMGUI tool: DBMGUI Backup Backup Wizard Complete 2. NOTE 3.2 Database-Specific System Copy SAP MaxDB-Specific Procedure You must have installed JRE version 1. For more information. You register your database instance in the DBMGUI 2. During the installation of the database instance. CNREPRT.

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

see the documentation Database Administration Guide: SAP on IBM DB2 Universal Database for UNIX and Windows.5 5. SAPinst is used for the installation on the target system host as described in the installation documentation for your SAP component. Prerequisites ■ The source and target database systems should be binary compatible. Process 1. Disadvantages of the Backup Method ■ You cannot change the database schema. ■ If errors occur when restoring the backup on the target system. To create a target system. During the installation phase SAPinst prompts you to perform the database restore. the complete restore must be repeated. In an ABAP system. For more information. UNIX. 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.4 Database-Specific System Copy IBM DB2 for Linux. Solaris and HP-UX. This section provides information on the backup method. CAUTION Be aware of the following constraints when using the backup method for a homogeneous system copy: ■ You cannot change the connect user. it is possible to use backup images cross platform for AIX. section The db2inidb Tool and the DB2 documentation. UNIX. and Windows Target System <system variant> <technical stack> Perform the installation options in the given sequence and follow the instructions on the SAPinst dialogs. You perform an offline backup or restore an existing backup copy. The database schema will be the same as of the source system. only the SAPinst steps for setting up and loading the database steps are replaced by a database restore. During the dialog phase you have to make sure that you enter the name of the connect user exactly as you did on your source system. 2010-03-16 PUBLIC 67/126 . and Windows Specific Procedures conjunction with split mirror. NOTE With DB2. 2. ■ You cannot copy an individual MCOD component to another system. Advantages of the Backup Method ■ You can use existing offline backups. ■ Using the backup method is faster than the database-independent method [page 21]. You can only copy the complete system.

section Usage of Tool brdb6brt. enter the following SQL command: update <connect_user_name>. For the restore of your database. You also have to perform a roll forward operation to bring the database into a consistent state. For more information. IADB6 and TADB6 using the following commands: ■ For table TSDB6. see the documentation Database Administration Guide: SAP on IBM DB2 Universal Database for UNIX and Windows.tsdb6 set tabspace = '<SAPSID_TARGET>#'||substr (tabspace. and Windows Specific Procedures ■ The table space names remain the same during the database restore. UNIX.4 Database-Specific System Copy IBM DB2 for Linux. you have to update the table space names in tables TSDB6. For more information see the IBM DB2 documentation DB2 Command Reference. In addition. ■ Redirected restore To perform a redirected restore. If required. You can now continue with the installation.iadb6 set tabspace = '<SAPSID_TARGET>#'||substr (tabspace. 4. use the tool brdb6brt that retrieves a database backup and creates a CLP script for the restore of this backup image.length(tabspace)-4) ■ For table TADB6. see the documentation Database Administration Guide: SAP on IBM DB2 Universal Database for UNIX and Windows section Usage of Tool brdb6brt and the IBM DB2 documentation DB2 Command Reference. enter the following SQL command: update <connect_user_name>.5. you have to make sure that you have access to the log files that were created during the online backup. use the DB2 restore command. enter the following SQL command: 68/126 PUBLIC 2010-03-16 . you have to adapt the container names in the redirected restore script and then perform a redirected restore. you can modify the table space names after the installation using the following command: db2 rename tablespace <old name> to <new name> EXAMPLE db2 rename tablespace <SAPSID_SOURCE>#STABD to <SAPSID_TARGET>#STABD 3. However. you can choose between one of the following options: ■ Simple database restore To perform a database restore.5. Perform the database restore.length(indspace)-4) ■ For table IADB6.5 5.length(tabspace)-4). 5.indspace='<SAPSID_TARGET>#'||substr(indspace. If you have used an online backup. you can change them after the installation. For more information about how to use the tool brdb6brt. ■ If you want to change the container names on the target system.

5 5. adapt the references to SAPR3 in the following SQL statements and jobs to reflect the actual schema name. You can only copy the complete system. For more information. you cannot copy an individual MCOD component to another system. 2010-03-16 PUBLIC 69/126 . Restriction of the Offline System Copy Method At the moment. see SAP Note 585277. End of: IBM DB2 for i5/OS | Only valid for: IBM DB2 for z/OS | 5. CAUTION You can only copy for IBM DB2 for i5/OS. If you employ a different schema. Advantage of the Offline System Copy Method This method is faster than the database-independent method [page 21].5 IBM DB2 for i5/OS Procedure In an SAP system environment. This document assumes that the database schema of your SAP system is SAPR3. you can create a homogeneous system copy of a DB2 database using the offline system copy method.6 IBM DB2 for z/OS Specific Procedure In an SAP system environment. The following section describes an offline system copy method for SAP systems on IBM DB2 for z/ OS.5 Database-Specific System Copy IBM DB2 for i5/OS Procedure update <connect_user_name>.tabdb6 set tabspace = '<SAPSID_TARGET>#'||substr (tabspace. you can create a homogeneous system copy of a DB2 database using the SAV/RSTLIB system copy method.length(tabspace)-4) More Information IBM DB2 documentation DB2 Command Reference End of: IBM DB2 for Linux and UNIX and Windows | Only valid for: IBM DB2 for i5/OS | 5. Advantage of the Offline System Copy Method This method is faster than the database-independent method [page 21].5. For this example system copy. the high-level qualifier of the source system is assumed to be D8A0 of the target system D8B0.

and the target system must not be able to use the resources of the source system. Run SQLs in the Source System 4. storage groups must be modified to apply the new high-level qualifier. ■ RACF authorization for the target DB2 subsystem is complete. ■ Table spaces are not partitioned. Check the Source System for Consistency 2. To prepare the DB2 catalog of the target system.5 5. you must run JCL jobs created by SQLs running in the source system. The source system must not be able to use the resources of the target system. ■ Volumes of the source and target systems are managed by SMS. ■ Source and target systems run with the same DB2 service level. Prerequisites The following prerequisites must be fulfilled to use this method: ■ The permissions of the source and target systems must be completely separate.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure NOTE The offline system copy must be performed by an experienced database administrator. The offline system copy can be divided into the following steps: 1. ■ Source and target systems must work with DB2 managed objects. ■ The system copy is made from a nondata sharing system to a nondata sharing system. In the following steps. This can be achieved by dropping and re-creating the storage groups with the new high-level qualifier (and volumes). Stop and Restart the Source System 3. ■ Source and target systems have their appropriate entries in the APF list. You can find an adapted procedure for an online system copy in the IBM documentation High Availability for SAP on zSeries Using Autonomic Computing Technologies. Capture View Definitions 70/126 PUBLIC 2010-03-16 . ■ Procedures of the source and the target system are defined in the DB2 PROCLIB. Variables Used in this Procedure ■ ■ ■ ■ ■ Source System = D8A0 Target System = D8B0 Storage Group = TEMPORA High-Level Qualifier = HLQ Boot Strap Data Set = BSDS Main Steps in this Procedure The following sections contain the detailed steps involved in the homogeneous system copy procedure for DB2 for z/OS.

5 5. the source system must be stopped. This can be checked with DISPLAY DATABASE(*) SPACENAM(*) with keyword RESTRICT. ■ Check if there are threads.2 Step 2: Stop and Restart the Source System Now you must stop and restart the source system with the ACCESS (MAINT) command option to prohibit any authorization IDs other than install SYSADM and install SYSOPR. If there are running utilities.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure 5.zip) that is attached to SAP Note 680746. 11. For more information.1 Step 1: Check Consistency The following is a list to help you check the source system for consistency. ■ If there are no objects in pending status. 8. you must shut them down properly before continuing. ■ Ensure that all DB2 objects of the source system are started RW mode. 2010-03-16 PUBLIC 71/126 . 10. see DB2 UDB for z/OS and OS/390 Command Reference (SC26-9932-05).6. 5. ■ Check for authorized utilities using the following: DISPLAY DATABASE(*) UTIL(*) and press [ENTER] Your output should be: No authorized utility found. Stop the Source System Print the Bootstrap Data Sets Make Copies of the Source Data Sets Create the Target System Post-process the Target System Changing the VCAT of the Target System Changing the Schema of the Target System (DB2 V9 only) Adapting WLM Application Environments for DB2 Stored Procedures JCL jobs and SQL Statements The JCL jobs and SQL Statements are now located in a compressed file (. 6.6. 7. 5. The path for each file is given in the section that previously contained the code. 12. 9.

1 SQL Statement Number 01 This statement is located at HSCProcedure\Step3\STMT01. you identify user-defined indexes that you need to change in the DB2 catalog. Activities Execute all the following SQL statements in the source system: 5. Information for IBM DB2 V9 for z/OS If you are running your system with DB2 V9. see the section JCL Jobs and SQL Statements.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure 5.zip file [page 69] attached to SAP Note 680746.3. Output The output of this statement is similar to the following: EXAMPLE ---------+---------+---------+---------+---------+----NAME DBNAME INDEXSPACE ---------+---------+---------+---------+---------+----SYSTBLSP~0 SYSTABLE~0 SYSIXPART~0 DSNDB06 DSNDB06 DSNDB06 SYSTBLSP SYSTABLE SYSIXPAR 5. For more information. note that SQL Statements 2 through 9.3 Step 3: Run SQL Statements in the Source System Prerequisites As described earlier in this section.6. With this statement. see the section JCL Jobs and SQL Statements.3.6. For more information.zip file [page 69] attached to SAP Note 680746. For more information.2 SQL Statement Number 02 This statement is located at HSCProcedure\Step3\STMT02.SQL in the .5 5. you must stop and restart the source system with the ACCESS(MAINT) command option to prevent changes and to obtain consistent data. 72/126 PUBLIC 2010-03-16 . as well as Creating a New Storage Group Using the HLQ of the Target System are not relevant tasks for this procedure.SQL in the . see Step 8e: Changing the User-Defined Indexes in the DB2 Catalog [page 83].6.

5.3 SQL Statement Number 03 This statement is located at HSCProcedure\Step3\STMT03.5 5. see the section JCL Jobs and SQL Statements.SQL in the . you identify all databases that you want to stop at a later point in time in the target system: NOTE This task is not relevant for DB2 V9. Output The output of this statement is similar to the following: EXAMPLE -STOP DATABASE (A000XAAA) -STOP DATABASE (A000XAAB) -STOP DATABASE (A000XAAC) -STOP DATABASE (A000XAAD) -STOP DATABASE (A000XAAE) -STOP DATABASE (A000XAAF) -STOP DATABASE (A000XAAG) -STOP DATABASE (A000XAAH) -STOP DATABASE (A000XAAI) -STOP DATABASE (A000XAAJ) -STOP DATABASE (A000XAAK) -STOP DATABASE (A000XAAL) . . etc.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure With this statement. 2010-03-16 PUBLIC 73/126 . With this statement.3.zip file [page 69] attached to SAP Note 680746. you identify all table spaces to be connected at a later point in time to the temporary storage group TEMPORA: NOTE This task is not relevant for DB2 V9.6. For more information. .

COMMIT. ALTER INDEX "DSNACC". COMMIT. ALTER INDEX "DSNACC"."UTRESTART2X" USING STOGROUP TEMPORA. COMMIT. COMMIT. With this statement. ALTER INDEX "DSNACC"."UTLEX01" USING STOGROUP TEMPORA.5 5."UTRESTARTX" USING STOGROUP TEMPORA. NOTE This task is not relevant for DB2 V9. COMMIT."UTPETX01" USING STOGROUP TEMPORA. COMMIT. ALTER INDEX "DSNACC". ALTER TABLESPACE A000XAAA. COMMIT. you identify all indexes to be connected with storage group TEMPORA. ALTER INDEX "DSNACC"."UTLSTX01" USING STOGROUP TEMPORA. ALTER TABLESPACE A000XAAA. COMMIT. COMMIT. COMMIT. ALTER TABLESPACE A000XAAA. COMMIT.ABAPTREE USING STOGROUP TEMPORA.SQL in the . ALTER TABLESPACE A000XAAA.zip file [page 69] attached to SAP Note 680746."UTPRCX01" USING STOGROUP TEMPORA.6. ALTER INDEX "DSNACC"."UTPEX01" USING STOGROUP TEMPORA.ADRGS2 USING STOGROUP TEMPORA. see the section JCL Jobs and SQL Statements. COMMIT. COMMIT.ADIRACCE USING STOGROUP TEMPORA."UTTMPX01" USING STOGROUP TEMPORA. ALTER TABLESPACE A000XAAA.ABAPTREE USING STOGROUP TEMPORA. COMMIT."UTTMDX01" USING STOGROUP TEMPORA. ALTER INDEX "DSNACC".ADRDIFIN USING STOGROUP TEMPORA. COMMIT. COMMIT. ALTER INDEX "DSNACC".ADOWNERR USING STOGROUP TEMPORA. ALTER TABLESPACE A000XAAA. 74/126 PUBLIC 2010-03-16 .ADR10 USING STOGROUP TEMPORA. 5. ALTER INDEX "DSNACC". ALTER TABLESPACE A000XAAA. Output The output of this statement is similar to the following: EXAMPLE ALTER INDEX "DSNACC".6 Output Database-Specific System Copy IBM DB2 for z/OS Specific Procedure The output of this statement is similar to the following: EXAMPLE ALTER TABLESPACE A000XAAA.ADRCOMCS USING STOGROUP TEMPORA. COMMIT."UTPEBX01" USING STOGROUP TEMPORA. COMMIT. For more information.3.4 SQL Statement Number 04 This statement is located at HSCProcedure\Step3\STMT04.

zip file [page 69] attached to SAP Note 680746.3. COMMIT. . Database-Specific System Copy IBM DB2 for z/OS Specific Procedure etc. COMMIT. .5 SQL Statement Number 05 This statement is located at HSCProcedure\Step3\STMT05.6 SQL Statement Number 06 This statement is located at 2010-03-16 PUBLIC 75/126 . DROP STOGROUP SAPSOI. COMMIT.5 5. DROP STOGROUP SAPU1D. COMMIT. COMMIT. COMMIT. DROP STOGROUP SAPU1I. COMMIT. COMMIT. 5.6. COMMIT. DROP STOGROUP SAPLOI. Output The output of this statement is similar to the following: EXAMPLE DROP STOGROUP SYSDEFLT. COMMIT.3. 5. DROP STOGROUP SAPPRD. etc. DROP STOGROUP SAPPRI.6 .6. DROP STOGROUP SAPESI. Storage groups in the target system still contain the high-level qualifier of the source system. . see the section JCL Jobs and SQL Statements. DROP STOGROUP SAPSOD.SQL in the . you identify storage groups to be dropped at a later point in time with the following statement: NOTE This task is not relevant for DB2 V9. With this statement. For more information. DROP STOGROUP SAPESD.

Storage Group Naming Conventions Some storage group names may have to be adapted for all storage groups for which the creator is your SQLID and not SAPR3. COMMIT. COMMIT. COMMIT. COMMIT. CREATE STOGROUP SAPESI VOLUMES('*') VCAT FR01. see the section JCL Jobs and SQL Statements. CREATE STOGROUP SAPSOD VOLUMES('*') VCAT FR01. the schema name is also the name of the storage group. NOTE This task is not relevant for DB2 V9.5 5. CREATE STOGROUP SAPSOI VOLUMES('*') VCAT FR01. COMMIT. For more information. COMMIT.. COMMIT.SQL in the . Java Storage Group Naming Convention Schema Storage Group Name <schema> CAUTION <schema> For Java.. you can use the CATMAINT utility to globally switch a schema name.zip file [page 69] attached to SAP Note 680746. You must not change the name of the storage group. Be aware that as of DB2 V9. Output The output of this statement is similar to the following: EXAMPLE CREATE STOGROUP SYSDEFLT VOLUMES('*') VCAT FR01.... COMMIT. CREATE STOGROUP SAPU1D VOLUMES('*') VCAT FR01. COMMIT. 76/126 PUBLIC 2010-03-16 . CREATE STOGROUP SAPU1I VOLUMES('*') VCAT FR01. COMMIT. CREATE STOGROUP SAPESD VOLUMES('*') VCAT FR01. The naming convention is as follows: ABAP Storage Group Naming Convention Schema SAPR3 Storagegroup Name SAP<SI><I|D> <SID><SI><I|D> other NOTE <SI> signifies the two-character STORAGEID of the table type (TABART).6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure HSCProcedure\Step3\STMT06. COMMIT. COMMIT. In this case.. With this statement. COMMIT. we assume that FR01 is the high-level qualifier of the target system. COMMIT. you identify storage groups to be created at a later point in time with the highlevel qualifier of the target system..

COMMIT.COMMIT. etc. ALTER TABLESPACE "CC390". CREATE STOGROUP SAPLOI VOLUMES('*') VCAT FR01.COMMIT. .5 5..COMMIT. COMMIT."DDDBRTX" USING STOGROUP SAPD7DDB. COMMIT. . COMMIT. which now contain the high-level qualifier of the target system. ALTER TABLESPACE "CC390". COMMIT. With this statement. ALTER TABLESPACE "BCXXXC5E".7 SQL Statement Number 07 This statement is located at HSCProcedure\Step3\STMT07..COMMIT.COMMIT. NOTE This task is not relevant for DB2 V9."UTPROC" USING STOGROUP SYSDEFLT.COMMIT."DSNRLS01" USING STOGROUP SYSDEFLT. COMMIT. COMMIT.. For more information.COMMIT.COMMIT. Output The output of this statement is similar to the following: EXAMPLE ALTER TABLESPACE "DSNRLST".COMMIT.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure CREATE STOGROUP SAPPRI VOLUMES('*') VCAT FR01. COMMIT. ALTER TABLESPACE "BCXXXC5E". 2010-03-16 PUBLIC 77/126 .COMMIT. . you connect table spaces with their previous storage groups. COMMIT."DDDBRTH" USING STOGROUP SAPD7DDB. 5. ALTER TABLESPACE "BCXXX3UT".. ALTER TABLESPACE "BCXXXC5E"."DDDBTAB" USING STOGROUP SAPD7DDB.."UTTEMPL" USING STOGROUP SYSDEFLT.SQL in the . ALTER TABLESPACE "BCXXX3UT". ALTER TABLESPACE "CC390".zip file [page 69] attached to SAP Note 680746. see the section JCL Jobs and SQL Statements."JMSDMSG" USING STOGROUP SAPD7DDB. COMMIT.6."UTRSTRT" USING STOGROUP SYSDEFLT. CREATE STOGROUP SAPLOD VOLUMES('*') VCAT FR01. CREATE STOGROUP SAPPRD VOLUMES('*') VCAT FR01. etc."SYNCLOG" USING STOGROUP SAPD7DDB. CREATE STOGROUP SAPLOI VOLUMES('*') VCAT FR01. . ALTER TABLESPACE "BCXXX3UT".3."LDDDBT3U" USING STOGROUP SAPD7DDB.

5 5.6

Database-Specific System Copy IBM DB2 for z/OS Specific Procedure

5.6.3.8 SQL Statement Number 08
This statement is located at
HSCProcedure\Step3\STMT08.SQL

in the .zip file [page 69] attached to SAP Note 680746. For more information, see the section JCL Jobs and SQL Statements. With this statement, you connect indexes with their previous storage groups, which now contain the high-level qualifier of the target system.
NOTE

This task is not relevant for DB2 V9.
Output

The output of this statement is similar to the following:
EXAMPLE ALTER INDEX "SAPD5Z"."SYSTBLSPß0" USING STOGROUP SYSDEFLT;COMMIT; ALTER INDEX "SAPD5Z"."SYSTABLEß0" USING STOGROUP SYSDEFLT;COMMIT; ALTER INDEX "SAPD5Z"."SYSIXPARTß0" USING STOGROUP SYSDEFLT;COMMIT; ALTER INDEX "STEM"."DSNARL01" USING STOGROUP SYSDEFLT;COMMIT; . . etc.

5.6.3.9 SQL Statement Number 09
This statement is located at
HSCProcedure\Step3\STMT09.SQL

in the .zip file [page 69] attached to SAP Note 680746. For more information, see the section JCL Jobs and SQL Statements. With this statement, you identify all databases to be started after DB2 catalog manipulations.
NOTE

This task is not relevant for DB2 V9.
Output

The output of this statement is similar to the following:
EXAMPLE -START DATABASE (A000XAAA) -START DATABASE (A000XAAB) -START DATABASE (A000XAAC)

78/126

PUBLIC

2010-03-16

5 5.6

Database-Specific System Copy IBM DB2 for z/OS Specific Procedure -START DATABASE (A000XAAD) -START DATABASE (A000XAAE) -START DATABASE (A000XAAF) -START DATABASE (A000XAAG) -START DATABASE (A000XAAH) -START DATABASE (A000XAAI) -START DATABASE (A000XAAJ) -START DATABASE (A000XAAK) -START DATABASE (A000XAAL) . . etc.

5.6.4 Step 4: Capturing View Definitions with DB2 V9 (if the Schema Name is to be Changed)
DB2 V9 adds the capability to change the VCAT name to the CATMAINT utility. This new capability facilitates homogenous system copy. Moreover, the CATMAINT utility can change the schema and creator of objects. If you intend to also change the schema name as part of the homogeneous system copy, for example for SAP Java systems, you need to capture the view definitions in this step. This is necessary since renaming the schema using CATMAINT requires that no views exist on the tables for which a VCAT name is changed. Therefore, the view definitions are exported in this step using R3ldctl. As part of the post-processing steps that are performed in the target system, the saved view definitions are later used to re-create the views in the target system. The views may also be saved and later recreated in the target system using alternative tools.
Procedure

To export the view definitions using R3ldctl: 1. Run R3ldctl without parameters to create the DDLDB2.TPL file, the SAPVIEW.STR file and others 2. Store these files

5.6.5 Step 5: Stop the Source System
Stop the source system with the following command option:
MODE (QUIESCE)

2010-03-16

PUBLIC

79/126

5 5.6

Database-Specific System Copy IBM DB2 for z/OS Specific Procedure

5.6.6 Step 6: Making Copies of Source Data Sets
With this step, you make copies of the source data sets, which includes: ■ DB2 bootstrap data sets ■ DB2 logcopy data sets ■ All DB2 VSAM data sets belonging to the source system With these JCL jobs, you can make copies of the source data sets: ■ HSCProcedure\Step6\DUMPA0.JCL ■ HSCProcedure\Step6\DUMPA1.JCL ■ HSCProcedure\Step6\DUMPA2.JCL ■ HSCProcedure\Step6\DUMPLIB.JCL ■ HSCProcedure\Step6\DUMPLOG.JCL ■ HSCProcedure\Step6\DUMPREST.JCL All scripts are located in the .zip file [page 69] attached to SAP Note 680746. For more information, see the section JCL Jobs and SQL Statements.
NOTE

The source system can be restarted now. It is no longer needed for the following system copy process.

5.6.7 Step 7: Creating the Target System
With the following JCL jobs, you create the target system. In the first step, the dumps of the source system have to be restored. All data sets of the source system have to be restored with the high-level qualifier of the target system. All statements are located in the .zip file [page 69] attached to SAP Note 680746. For more information, see the section JCL Jobs and SQL Statements. ■ ■ ■ ■ ■ ■
HSCProcedure\Step7\RSTOREA0.JCL HSCProcedure\Step7\RSTOREA1.JCL HSCProcedure\Step7\RSTOREA2.JCL HSCProcedure\Step7\RSTORELI.JCL HSCProcedure\Step7\RSTORELO.JCL HSCProcedure\Step7\RSTORERE.JCL

5.6.8 Step 8: Printing the Bootstrap Data Sets
Prerequisites

The source system must be stopped at this point.

80/126

PUBLIC

2010-03-16

For more information.......5 5..163 20:14:45..-------------------0034A0468000 0034AC7DFFFF 2003.. see the section JCL Jobs and SQL Statements. The JCL jobs listed here are located in the ...DS03 2004.....zip file [page 69] attached to SAP Note 680746..-------------------. . .106 12:12 DSN=D8A0......6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure Statement This JCL job is located at HSCProcedure\Step8\PROLOGMAP..LOGCOPY1....163 20:37:23... using the HLQ D8B0. ENFM START RBA/LRSN: 000000000000 ACTIVE LOG COPY 1 DATA SETS START RBA/TIME END RBA/TIME DATE LTIME DATA SET INFORMATION -------------------.----...106 12:12 DSN=D8A0.. You can use the output of this statement to manipulate the bootstrap data sets in the target system...163 18:31:44.... 1..1 PASSWORD=(NULL) STATUS=REUSABLE 0034B8B58000 0034C4ECFFFF 2003.6.163 20:14:45.1 ...9 Step 9a: Changing the Bootstrap Data Sets (BSDS) Before starting the target system.JCL in the ......DS01 2004.zip file [page 69] attached to SAP Note 680746.......7 PASSWORD=(NULL) STATUS=REUSABLE 0034AC7E0000 0034B8B57FFF 2003... the BSDS must be changed...4 2004.. Change the HLQ entry in the BSDS of the target system...... 5... see the section JCL Jobs and SQL Statements.... PASSWORD=(NULL) STATUS=REUSABLE ARCHIVE LOG COPY 1 DATA SETS NO ARCHIVE DATA SETS DEFINED FOR THIS COPY ACTIVE LOG COPY 2 DATA SETS NO ACTIVE DATA SETS DEFINED FOR THIS COPY ARCHIVE LOG COPY 2 DATA SETS NO ARCHIVE DATA SETS DEFINED FOR THIS COPY .-------. BSDS COPY 2 DATA SET NAME: ..7 2004........ ...... etc.. GROUP NAME: .... The corresponding JCL job is located at HSCProcedure\Step9a\CHGBSDS1. .... BSDS COPY 1 DATA SET NAME: .. For more information.JCL 2010-03-16 PUBLIC 81/126 ...163 20:37:23. With this statement.DS02 2004.. .....106 12:12 DSN=D8A0....... you print the bootstrap data sets...LOGCOPY1..LOGCOPY1.. Output The output of this statement is similar to the following: SYNTAX ........

LUW-ID=* IKJ56228I DATA SET D8A0. the target system has access to the data sets of the source system and the data of the source system could be changed by mistake.I0001.DSN4K01.A001 NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED DSNB207I -D8B0 DYNAMIC ALLOCATION OF DATA SET 608 FAILED. POSTPONED ABORT=0 DSNP012I -D8B0 DSNPCNP0 .D8E0.I0001. CORRELATION-ID=003. as seen in the log.DSN4K01. However.DSNDB07. INDOUBT=0 DSNR006I -D8B0 RESTART.A001 CTLGRC=AAAAAA08 CTLGRSN=AAAAAA08 CONNECTION-ID=D8E0. After changing the BSDS with these scripts. ..000000000000=0 REASON 00D70024 .RCRSC 02.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure 2.A001 DSNT501I -D8B0 DSNITFFS RESOURCE UNAVAILABLE 609 CORRELATION-ID=D8E0 CONNECTION-ID=D8E0 LUW-ID=D8E0.COUNTS AFTER BACKWARD 605 RECOVERY INFLIGHT=0.DSNDB07. 5. .I0001.DSNDBC.. We strongly recommend that you maintain different RACF settings for different DB2 subsystems..JCL in the . If not.6.zip file. -D8B0 RESTART. . IN ABORT=0.DSN4K01.COUNTS AFTER FORWARD 604 DSNR005I RECOVERY IN COMMIT=0. .10 Step 9b: Start the Target System When you start the DB2 target system for the very first time. you can start the target system..DSNDBC. etc. the system is still working with the work file database of the source system.DSNDB07. Change the log entries in the BSDS. .DSNDBC. DSNAME=D8A0. REASON=17080002.ERROR IN VSAM CATALOG 606 LOCATE FUNCTION FOR D8A0. The START and END RBA information as of utility DSNJU004 have to be used for the target system as follows: The corresponding JCL job is located at HSCProcedure\Step9a\CHGBSDS2. access fails with insufficient access authority. 82/126 PUBLIC 2010-03-16 . .5 5. Partial example of a LOG when you start the target system for the first time: SYNTAX .zip file. in the .

11 Step 9c: Creating a New STOGROUP Using the HLQ of the Target System With this JCL job.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure The work file database data must be changed later in the clone process.5 5. You find a list of index spaces in the output of SQL statement number 1 [page 72].6. Change the user-defined DB2 catalog indexes using the new storage group TEMPORA. For more information. For more information. NOTE This task is not relevant for DB2 V9. 5. you create a new STOGROUP using the HLQ of the target system (D8B0). see the section JCL Jobs and SQL Statements. see the section JCL Jobs and SQL Statements. 5. This JCL job is located at HSCProcedure\Step9e\ALTERIDX. the user-defined indexes (the output of SQL statement number 1 [page 72]) in the DB2 catalog must be changed.zip file [page 69] attached to SAP Note 680746.6.JCL in the .13 Step 9e: Changing the User-Defined Indexes in the DB2 Catalog After starting the target system.JCL in the .6. This JCL job is located at HSCProcedure\Step9c\CRTMPSTO. you must restart the index spaces. see the section JCL Jobs and SQL Statements. you stop the appropriate index spaces. 5.JCL .12 Step 9d: Stopping Index Spaces With this JCL job.zip file [page 69] attached to SAP Note 680746. 2010-03-16 PUBLIC 83/126 .zip file [page 69] attached to SAP Note 680746.14 Step 9f: Restart the Index Spaces At this point. For more information. 5. The JCL job is located at HSCProcedure\Step9d\STOPIDXS. The following example script can be used to carry out this procedure. working with the new HLQ of the target system D8B0.6.

delete the clusters for 4K and 32K and create them again.6. The . Error message IKJ56228I should not appear because DB2 is now working with its own work file database.zip file [page 69] attached to SAP Note 680746. see the section JCL Jobs and SQL Statements.JCL.18 Step 10 (DB2 V8 and Lower): Changing the VCAT of the Target System The target system with the new HLQ D8B0 still works with storage groups using VCAT D8A0. 2. The error as described in Step 6: Make Copies of the Sources Data Sets [page 80] should not occur since DB2 is working with the new temporary files.zip file atHSCProcedure\Step9g\CRTTMPFL.16 Step 9h: Implementing HLQ of the Target System in the Work File Database In the next step. For more information. To change the work file database: 1. Procedure To adjust the DDF location name and port number.6.6. The JCL job is located in the . 5. 5.5 5. 2. you must adjust the DDF location name and port number. Run part of DSNTIJTM to create temporary files for DB2.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure 5. 84/126 PUBLIC 2010-03-16 . Drop work file database DSNDB07 in the target system. Stop and restart the target system. run the DB2 utility DSNJU003 with the option DDF to specify the location name and port number. the work file database is changed to use the new HLQ Procedure D8B0.15 Step 9g: Creating the Temporary Files for the DB2 Target System To create the temporary files for the DB2 target system: 1. DSNTIJTM was generated by DSNTINST (optional) or consists of a manually changed copy from another existing DB2 subsystem.6. Stop and restart the DB2 subsystem.17 Step 9i: Adjusting the DDF Location Name and Port Number To allow communication with the SAP Application Servers of the DB2 target system. 5.

JCL. 4. Create the storage groups The corresponding JCL job is located at HSCProcedure\Step10\CREATSTG. Alter indexes using storage group TEMPORA The corresponding JCL job is located at HSCProcedure\Step10\ALTERIDX.5 5.JCL. Drop the storage groups The corresponding JCL job is located at HSCProcedure\Step10\DROPSTG. 3. 1. altering table-spaces and indexes using the new storage groups. Alter indexes using their previous storage group The corresponding JCL job is located at HSCProcedure\Step10\ALTERID2. 2.JCL. see the section JCL Jobs and SQL Statements. Start all databases This JCL job is located at HSCProcedure\Step10\STARTDBS. 6. and starting all databases. the DB2 catalog is manipulated by stopping the databases. 8. Alter table spaces using storage group TEMPORA The corresponding JCL job is located at HSCProcedure\Step10\ALTERTBS. Alter table spaces using their previous storage group The corresponding JCL job is located at HSCProcedure\Step10\ALTERTB2. change the user authorizations of the target system. 2010-03-16 PUBLIC 85/126 . The objects to be manipulated are identified by the results of previously described SQL statements.zip file [page 69] attached to SAP Note 680746.JCL. If necessary.JCL.JCL. The DB2 catalog still contains the authorizations of the source system. All SQL statements listed here are located in the. Procedure Stop all databases The corresponding JCL job is located at HSCProcedure\Step10\STOPDBS.JCL. For more information.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure In the following steps. altering table-spaces and indexes. dropping and creating storage groups with the new VCAT D8B0. 5.JCL. 7.

submit the following statement: CREATE STOGROUP <stogroup_name> VOLUMES (*) VCAT <vcat_name> where <vcat_name> is the VCAT name of the new DB2 subsystem.6. 3. These new stogroups reflect the SAP system ID of the new SAP system instead of the SAP system ID of the source SAP system. ■ EDMPOOL ≥ 200000 KB ■ EDMDBDC ≥ 300000 KB Call the CATMAINT utility with the UPDATE VCAT option to switch the VCAT name Reinstate the original sizes of EDMPOOL and EDMDBDC. To create the stogroups. If necessary. Ensure that the DB2 EMD pool and DB2 EDM DBD cache have at least the following sizes: 2.19 Step 10 (DB2 V9): Changing the VCAT of the Target System To change the VCAT that is used for the storage groups of your SAP tables and indexes.6. do not need to be changed and are still used by the existing database objects of the new SAP system. proceed as follows. This approach requires that you have previously invoked R3ldctl on your source system to capture the view definitions of the SAP system.5 5. The existing stogroups in the DB2 target system. change the user authorizations of the target system. 5. they do not interfere with the stogroups of the DB2 source system.20 Step 11 (DB2 V9): Changing the Schema of the Target System To change the schema or creator name of your SAP tables and indexes. 5. proceed as follows. Procedure 1. respectively. Start the DB2 subsystem in regular mode If the schema of the SAP source system is not SAPR3 and if you do not intend to change the schema name. The DB2 catalog still contains the authorizations of the source system. EXAMPLE If an existing stogroup name is OLDDID and if the SAP system IDs of the source and target systems are OLD and NEW. which reflect the SAP system ID of the source system. create a new DB2 stogroup for each existing stogroup. 4. see the SAP DBA Guide: DB2 for z/OS.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure 5. then a new stogroup needs to be created with the name NEWDID. section Additional Information. 86/126 PUBLIC 2010-03-16 . As these names are only used internally in DB2. For details on the SAP exploitation of DB2 stogroups.

where <vcat_name> is the VCAT name of the new DB2 subsystem. These new stogroups reflect the SAP system ID of the new SAP system instead of the SAP system ID of the source SAP system. EXAMPLE 8. save their definitions in a separate place Delete all views. If user-defined materialized query tables or triggers exist. Start the DB2 subsystem in regular mode Create a new DB2 stogroup for each existing stogroup. 6. materialized query tables and triggers that exist on the SAP tables Ensure that the DB2 EMD pool and DB2 EDM DBD cache have at least the following sizes: ■ EDMPOOL ≥ 200000 KB ■ EDMDBDC ≥ 300000 KB Call the CATMAINT utility with the SCHEMA SWITCH option to switch the schema name Reinstate the original sizes of EDMPOOL and EDMDBDC. 2010-03-16 PUBLIC 87/126 .STR" dcf: "DDLDB2.cmd -dbcodepage <codepage> -l SAPVIEW. 5. re-create them. If user-defined materialized query tables or triggers exist. Call R3load with the option -i SAPVIEW.cmd file to prepare the recreation of the views. 3.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure Procedure 1. then a new stogroup needs to be created with the name NEWDID. Generate the R3load task files by submitting the following command: R3load -ctf I SAPVIEW.TSK" icf: "SAPVIEW. This file can contain the following lines for example: EXAMPLE tsk: "SAPVIEW. Create an SAPVIEW. 7.TSK DB2 -l SAPVIEW.STR DDLDB2. Re-create the views by implementing the following steps: 1. to re-create the views. submit the following statement: CREATE STOGROUP <stogroup_name> VOLUMES (*) VCAT <vcat_name> 4. If an existing stogroup name is OLDDID and if the SAP system IDs of the source and target systems are OLD and NEW.5 5.TPL SAPVIEW.log 2.log 9. 2. respectively.TPL" dat: null dir: null ext: null 3. To create the stogroups.

Use the ALTER PROCEDURE statement as described in the IBM documentation DB2 for z/OS SQL Reference. Create WLM application environments for the DB2 stored procedures as described in the SAP DBA Guide: DB2 for z/OS. carry out the following steps: 1.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure 5. End of: IBM DB2 for z/OS | 88/126 PUBLIC 2010-03-16 .5 5.21 Step 12: Adapting WLM Application Environments for DB2 Stored Procedures The WLM environments of the WLM-established stored procedures need to be changed if the target system is running with other WLM environments. 2.6. Procedure To change the WLM environments of the WLM-established stored procedures.

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

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

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

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

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

make sure that the Distinguished Name used for the PSE conforms with the naming convention that applies.40 | 1. Choose Configuration Homogeneous System Copy: Jobhead Correction Modify the necessary data. the CCMS jobhead still points to the former database SSID. 3. 2. Call transaction DB2.0 SP 12 or above to use this function. the SSID needs to be set to the target system. After copying your system.1 | 1.0 | Procedure To set the SSID to the target system: Only valid for: SAP NetWeaver 7. 2.2.SAP NetWeaver 7. 3. Call transaction DBACOCKPIT.1 | Only valid for: SAP Web AS 6.2 Follow-Up Activities Performing Follow-Up Activities in the Target System Therefore. End of: SAP NetWeaver 7.0.0 | Prerequisites You must have SAP NetWeaver 7.2 Performing Jobhead Correction after Homogeneous System Copy NOTE This section is only relevant for customers using CCMS to monitor their SAP system(s). End of: SAP NetWeaver 7. End of: SAP Web AS 6. Choose Checks/Settings Correct Jobheads Modify the necessary data. CAUTION Only experienced users should use this utility.SAP NetWeaver 7.40 | 94/126 PUBLIC 2010-03-16 . 6. In order to complete the homogeneous system copy.0.6 6. Only valid for: SAP NetWeaver 7.

but you can also use the monitor for copying older releases by starting it manually. The Migration Monitor is integrated into the SAPinst system copy tool. if you call it with one of the following options: ■ ■ -help -? 2010-03-16 PUBLIC 95/126 .7 7. ■ The correct directory structure for R3load dump files must exist on both the source and target hosts.5 or higher ■ The JAVA_HOME environment variable must point to the JRE directory.01.2008). 7. you need an R3load version with at least patch level 73 (compile date: 12.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. CAUTION If you want to convert a non-Unicode system to Unicode using the Socket option.1 Configuration Help The tool will display the available parameters.1 Additional Information R3load Procedures Using the Migration Monitor 7 Additional Information 7. The Migration Monitor will ■ create R3load command files ■ create R3load task files if required ■ start the R3load processes to unload the data ■ transfer packages from the source to the target host if required ■ start the R3load processes to load the data as soon as a package is available ■ inform the person performing the system copy in case of errors The Migration Monitor has to be started on the source database host (Export Monitor) and on the target database host (Import Monitor).1. Prerequisites ■ JRE version 1.

Separator on Windows: ‘.1 Additional Information R3load Procedures Using the Migration Monitor Version The tool will display the version information (release branch and build date).6. default). where the R3load TSK and log files will be created. When the Migration Monitor is used without the installation tools. DB and DB/<TARGET_DBTYPE>(for example. if you call it with the following option: ■ -version General Options Name monitorTimeout Description Comments Monitor timeout in seconds During a timeout. the subdirectories DATA. DB/ORA) have to exist. R3SETUP) write their log files. 1 (error). mailFrom mailTo Trace Option Name trace Description Comments Trace level Possible values: all. 96/126 PUBLIC 2010-03-16 . 2 (warning). The default timeout value is 30 seconds. 3 (info).’ or blanks.7 (trace) Export Options Option installDir Description Comments Installation directory exportDirs List of export directories The installation start directory is the directory in which the installation tools (SAPinst.7 7. off. 4 (config. In the ‘exportDirs’ directory. 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 Can contain an address list separated by ‘.’ Separator on UNIX: ‘:’ The ‘exportDirs’ parameter points to the directory where the R3load dump files will be written to. 5. the monitor thread sleeps and does not analyze any files or analyze its processing state. the installation start directory is the directory.

tskFiles 'yes' to create task files. The Import Monitor always runs in the server mode. -o (if the omit argument is specified and task files are not used. specify the parameter ‘server’ in the Export Monitors properties file.7 7. Number of parallel export jobs. that is. the Monitor will create R3load TSK files (if necessary).1 Option client Additional Information R3load Procedures Using the Migration Monitor Description Comments Running in client mode means. -o (if the omit argument is specified). p. Options already set by the monitor: -ctf. the Monitor will run parallel with standard SAPinst export process and transfer the exported dump files onto the import server. -r. Possible values: 4102. Network Exchange Options Option net Description Comments Network operating mode Exported dump files must be visible on the import host to use this mode.7 ‘yes’.TSK’ already exist then the monitor will not overwrite them. 0 for an default is 1. If the R3load task files ‘*. 2010-03-16 PUBLIC 97/126 . R3load cmd files and start the R3load processes. starting from version 4. If the option value is omitted then package order is not determined. orderBy Package order Can be the ‘name’ or path of the file that contains package names.6 must be set to ‘no’. -l. Additional R3load arguments for the Appended to the R3load command LOAD phase line. -datacodepage. -l. 'no' to skip Before version 4. Options already set by the monitor: -e. 1100 taskArgs Client operating mode loadArgs expJobNum Additional R3load arguments for the Appended to the R3load command TASK phase line. the Any positive number. the value of the ‘tskFiles’ option is ‘no’). 4103. All options below are for the server mode. unlimited number of jobs. If only the name of the R3load executable is available. server Server operating mode Running in server mode means. the default is R3load. r3loadExe Path of the R3load executable Optional. If you want to run the Export Monitor in the server mode. -socket (if the socket option is specified). dataCodepage Code page for data files See SAP Note 552464. then JVM looks for the R3load executable using OS-specific process search rules.

Any positive number. The FTP user specified here should be the <sapsid>adm to make sure that the package files can be read by during the import (which is started as <sapsid>adm). The value will be the same as for ‘importDirs’ in the Import Monitors property file. Used for communication between the export and Import Monitors. Security risk! Both ‘.1 Option Additional Information R3load Procedures Using the Migration Monitor Description Comments netExchangeDir Network exchange directory Used for communication between the export and Import Monitors. 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. CAUTION ftpPassword Password of the remote FTP user List of remote FTP directories for export dump ftpExportDirs ftpExchangeDir Remote FTP exchange directory ftpJobNum Number of parallel FTP jobs. Must be writable for Export Monitor and readable for Import Monitor.SGN to the network exchange directory as a signal for the Import Monitor that the package is exported successfully and the import could be started. Name or IP address of the import server. the default is 1. The Export Monitor will write a file <package>. 98/126 PUBLIC 2010-03-16 . Must be writable for the Export Monitor and readable for the Import Monitor.’ or ‘:’ separators are valid. The Export Monitor will write a file <package>. This is the directory on the target host to which the dump will be transferred.SGN to the FTP exchange directory as a signal for the Import Monitor that the package is exported successfully and the import could be started.7 7. 0 for an unlimited number of jobs.

The value will be the same as for ‘importDirs’ in the Import Monitors property file. Separator on Windows: ‘. Any free port on the import host from 1024 to 65535. FTP Copy Options Option ftpCopy Description Command FTP copy operating mode exportDirs List of export directories ftpHost Remote FTP host Name of the remote FTP user ftpUser ftpPassword ftpExportDirs Password of the remote FTP user List of remote FTP directories for export dump Used as a separate program call for migration with sockets. Name or IP address of the import server.1 Additional Information R3load Procedures Using the Migration Monitor 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 but the export and import work through the socket connection. Must be the same as the port number on the import host.g. 2010-03-16 PUBLIC 99/126 . Name or IP address of the import host.TPL files in the subdirectory DB. DB/ ORA) have to exist. DB and DB/<TARGET_DBTYPE> (e. This is the directory on the target host to which the dump will be transferred. All files produced by R3lctl and R3szchk will be transferred from the source to the target host using FTP.’ or ‘:’ separators are valid. CAUTION: Security risk Both ‘. the DDL*. the subdirectories DATA.’ Separator on UNIX: ‘:’ In the ‘exportDirs’ directory. Any other option is ignored by Import Monitor. The FTP user specified here should be the <sapsid>adm to make sure that the package files can be read by during the import (which is started as <sapsid>adm). The R3load STR files have to exist in the subdirectory DATA. and the R3load EXT files (if required) in the subdirectory DB/<TARGET_DBTYPE>.7 7.

all export dump files are available on the import host before the Import Monitor is started. DB and DB/<TARGET_DBTYPE> (for example. ■ Server mode: net (and their related parameters) installDir.6 must be set to ‘no’. Path of the R3load Optional. DB/ORA) have to exist. starting from ‘no’ to skip version 4. that is. Import Options Option installDir Description Comment Installation directory importDirs orderBy r3loadExe tskFiles The installation start directory is the directory in which the installation tools (SAPinst. ftpExportDirs. Before version 4. R3SETUP) write their log files. the installation start directory is the directory. ftpUser.7 7. size: load packages starting with the largest one.’ Separator on UNIX: ‘:’ The ‘importDirs’ parameter points to the directory where the R3load dump files will be written to. ftpHost. 100/126 PUBLIC 2010-03-16 . exportDirs. net. In the ‘importDirs’ directory. If the R3load task files ‘*.1 Additional Information R3load Procedures Using the Migration Monitor Mandatory Options for Export Monitor ■ Client mode: installDir. When the Migration Monitor is used without the installation tools. or a path of the file that contains package names. Values can be: name: load packages in alphabetical order. If only the name of the executable R3load executable is available then JVM looks for the R3load executable using OS-specific process search rules. socket (and their related parameters) ■ FTP copy: exportDirs. one of the options ftp. ftpExchangeDir NOTE The value of the dbType option is determined automatically in the shell script/batch files from the dbms_type environment variable. ‘yes’ to create task files. tskFiles. List of import directories Separator on Windows: ‘. If the option is omitted then package order is not defined.7 ‘yes’. one of the options ftp. where the R3load TSK and log files will be created.TSK’ already exist then the monitor will not overwrite them. Package order This option is used only if the Import Monitor works without the Export Monitor in stand-alone mode. exportDirs. the default is R3load. the subdirectories DATA.

remove this file. -l. in the properties file). -o D : omit data. Import Exchange Options Option exchangeDir Description Comment Exchange directory If this option is not set. that is without the Export Monitor. -l. list these options without blank (for example. 2010-03-16 PUBLIC 101/126 . -dbcodepage. do not create views If you want to combine several omit options. 4103.properties (for example. from a previous export run). Import Socket Options Option socket port Description Command Socket operating mode Server port number Any free port from 1024 to 65535. arguments for the TASK Options already set by the monitor: phase -ctf. Database code page for See SAP Note 552464. Additional R3load Appended to the R3load command line. If the EXT files cannot ‘no’ to skip them be found in DB/<TARGET_DBTYPE> import dump subdirectory the package processing is aborted. 0 for an unlimited number of import jobs. the target database 1100 Migration key R3load omit value Can contain only 'DTPIV' letters. do not create indexes -o V: omit views. Number of parallel Any positive number. -p. do not create primary keys -o I: omit indexes. Additional R3load Appended to the R3load command line.1 Option Additional Information R3load Procedures Using the Migration Monitor Description Comment extFiles dbCodepage migrationKey omit taskArgs loadArgs impJobNum ‘yes’ to include EXT files. that is. -o (if the omit argument is specified and task files are not used. -socket (if the socket option is specified). do not create tables -o P: omit primary keys. the value of ‘tskFiles’ option is ‘no’). -r. -o (if the omit argument is specified). Add EXT file entries to cmd files. arguments for the LOAD Options already used by the monitor: phase -i. 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. Possible values: 4102. the default jobs is 1.7 7. ‘-o TV’). then the monitor runs in stand-alone mode. do not load data -o T: omit tables. -k. If there is an old file export_statistics.

1. 7. Procedure Example of a DDL mapping file: # DDL mapping file ddl_mapping.1 Additional Information R3load Procedures Using the Migration Monitor Any other option is ignored by Import Monitor. The assignment of a specific DDL file to a single package is done within a simple text file. importDirs. tskFiles.TPL # table names TABLE_A TABLE_B TABLE_C 102/126 PUBLIC 2010-03-16 . one of the options exchangeDir or socket (and their related parameters) ■ Stand-alone mode: installDir. extFiles NOTE The value of the dbType option is determined automatically in the shell script/batch files from the dbms_type environment variable.2 Assigning DDL Files to Packages It is possible to use several different DDL*.TPL # package names SAPAPPL0 SAPAPPL1 SAPSDIC [ UNSORTED UNLOAD ] DDL file for unsorted unload ddlFile = .7 7.TPL templates during the export respectively during the import. Packages not listed in the DDL mapping file will use the default DDL control file.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. which then has to be specified via the ddlMap option within the migration monitor's properties file. Mandatory Options for Import Monitor ■ Server mode (default): installDir./DDLORA_LRG. extFiles. importDirs. tskFiles.

2010-03-16 PUBLIC 103/126 .1 Additional Information R3load Procedures Using the Migration Monitor 7. If package groups are defined. In addition. it has to be ensured before the import starts that the table exists and that the primary key and the indexes are created before/after (as defined in the DDL template) the table data have been imported.1.1.4 Processing Split Tables If tables have been split during the export. the maximal number of parallel R3load jobs is the sum of jobNum of all packages. which was defined in the migration monitor's properties file. The old package order format is also fully supported. These tasks will be synchronized by the migration monitor automatically. you can specify different values for the parameter jobNum and taskArgs / loadArgs per package. Procedure Example of a package order file with group: # custom package order # package names SAPAPPL0 SAPAPPL1 SAPAPPL2 # package group [ SEQUENTIAL GROUP ] jobNum = 1 # table names TABLE_A TABLE_B TABLE_C 7. WHR files are part of the package and have to be copied to DATA export subdirectory to make sure that the same WHR file is used for the export and the import of the corresponding package. and Windows ■ MS SQL You can ensure this by using the feature Defining Groups of Packages [page 103]. The following database platforms to not support parallel data import: ■ IBM DB2 for Linux. Package groups can be defined in the same text file in which the package order can be defined (see parameter orderBy).3 Defining Groups of Packages The “package group” feature is an enhancement of defining a package order. By defining groups you can prevent parallel execution of certain packages and you can define how many large tables are exported or imported at the same time. All packages without package group will be assigned to a “default group” with the number of jobs. UNIX.7 7.

which belong to this package have to be deleted using the WHERE condition assigned to this package before starting the data import again. you can also define the processing order of packages or you can assign DDL files to packages.1 Additional Information R3load Procedures Using the Migration Monitor Procedure Example: Target database does not support parallel data import Use During the export you have split the table MY_FIRST_TABLE into 3 packages and MY_SECOND_TABLE into 5 packages.properties file has to be set to 8 to ensure that not more than 10 R3load processes will run in parallel. manually. For every group (MY_FIRST_TABLE and MY_SECOND_TABLE) a R3load job is started. Now you want to run a maximum of 10 R3load processes for parallel data import.txt with the following content: [ MY_FIRST_TABLE ] jobNum = 1 MY_FIRST_TABLE-1 MY_FIRST_TABLE-2 MY_FIRST_TABLE-3 [ MY_SECOND_TABLE ] jobNum = 1 MY_SECOND_TABLE-1 MY_SECOND_TABLE-2 MY_SECOND_TABLE-3 MY_SECOND_TABLE-4 MY_SECOND_TABLE-5 In this file. Procedure Create the file inputFile. defined by the parameter jobNum. for which the import one or more packages failed. The deletion with a WHERE clause can be very time consuming so it is faster to delete all rows of the corresponding table manually and reimport all packages instead. Delete all rows of the table. The number of parallel R3load jobs will be the total of the number of R3load jobs of each group plus the number of R3load jobs defined for the default group (which is made up of all packages without an explicit group name). the rows. The inputFile. Eliminate the reason for the failure of the import of the package(s). In this example the parameter jobNum in the import_monitor_cmd. Restart for all other database platforms: 1.7 7.txt file has to be specified as value for the Migration Monitor parameter orderBy. 2. 104/126 PUBLIC 2010-03-16 . Re-Starting the Import of a Split-table Package If the import of a package fails.

properties and import_monitor_cmd.properties in the installation directory.sh 3. Restart the import. Options are case-sensitive. Run the command call qp2term. Do not remove the TSK files. Templates for these files are included in the application archive and must be located in the current user's working directory.properties. 2.sh End of: UNIX | ■ Only valid for: Windows | The Windows batch files export_monitor.TSK). which had been imported successfully and have to be reimported by '0' (see Restarting R3load Processes [page 45]). enter -optionName optionValue 2010-03-16 PUBLIC 105/126 . The names of the property files are export_monitor_cmd. 5. 7. To specify an option: ■ in the command line.sh / import_monitor. which import data into this table (<table name><counter>__TPI.sh / export_monitor_secure. export_monitor.bat End of: Windows | ■ Only valid for: IBM i5/OS | IBM i5/OS specific 1. Replace the status '+' of all packages for the corresponding table. Adapt the file import_state. any options that are not recognized are ignored.bat / import_monitor.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. which create the table or which create the indexes for this table. Check that the environment variable PASE_THREAD_ATTACH is set to 'Y': WRKENVVAR PASE_THREAD_ATTACH='Y' End of: IBM i5/OS | You can specify options in the command line or in the export or import property files [page 95].7 7. Set the JAVA_HOME environment as follows: export JAVA_HOME=/QIBM/ProdData/Java400/jdk14 4.1.1 Additional Information R3load Procedures Using the Migration Monitor 3.bat / export_monitor_secure. 4.sh / import_monitor. Remove the TSK files of all packages. Any options specified in the command line take precedence over the corresponding options in the application property file.

7 7.1

Additional Information R3load Procedures Using the Migration Monitor

■ in the application property file, insert the new line optionName=optionValue
Only valid for: UNIX |

Example of a command line for a UNIX terminal:
End of: UNIX | Only valid for: UNIX |

./export_monitor.sh –ftp
End of: UNIX | Only valid for: UNIX |

./export_monitor.sh –ftpCopy
End of: UNIX | Only valid for: UNIX |

./export_monitor.sh –socket –host <import server> –port 5000
End of: UNIX | Only valid for: Windows |

Example of a command line for Windows cmd.exe:
End of: Windows | Only valid for: Windows |

export_monitor.bat –net
End of: Windows | Only valid for: Windows |

export_monitor.bat –socket
End of: Windows |

If FTP access is used and security is required, start the monitor using the secure version of the shell script/batch file to prevent seeing FTP password in the command line parameter string / property file.
Only valid for: UNIX |

Example of a command line for a UNIX terminal:
End of: UNIX | Only valid for: UNIX |

./export_monitor_secure.sh –ftpPassword <password>
End of: UNIX |

Procedure

1.

Start the monitor and close the shell window / command processor. The monitor process will run in background. 2. Use monitor *.log and *.console.log files to check monitor processing state. Example of an export_monitor_cmd.properties file with export options:
# Export Monitor options # Operating mode: ftp | net #net ftp

106/126

PUBLIC

2010-03-16

7 7.1 #

Additional Information R3load Procedures Using the Migration Monitor

# Common options #

# List of export directories, separator on Windows ; on UNIX : exportDirs=C:\TEMP\export_dump # SAPinst start directory installDir=C:\install\start # Monitor timeout in seconds monitorTimeout=30

# # FTP options # # Remote FTP host ftpHost=server # Name of remote FTP user ftpUser=sysadm # Password of remote FTP user ftpPassword=password # List of remote FTP directories for export dump, separator : or ; ftpExportDirs=/install_dir/export_dump # Remote FTP exchange directory ftpExchangeDir=/install_dir/exchange # Number of parallel FTP jobs ftpJobNum=3 # # E-mail options # # SMTP server mailServer=sap-ag.de # "From" email address mailFrom=mail@sap.com # "To" email address mailTo=mail@sap.com mail@yahoo.com

Example of an import_monitor_cmd.properties file with import options:
# Import Monitor options

2010-03-16

PUBLIC

107/126

7 7.1 #

Additional Information R3load Procedures Using the Migration Monitor

# Common options # # List of import directories, separator on Windows ; on UNIX : importDirs=/install_dir/export_dump # SAPinst start directory installDir=/install_dir/start # Exchange directory exchangeDir=/install_dir/exchange # Generation of task files: yes | no tskFiles=yes # Inclusion of extent files: yes | no extFiles=yes # Monitor timeout in seconds monitorTimeout=30 # # R3load options # # DB code page for the target database dbCodepage=1100 # Migration key migrationKey= # Additional R3load arguments for TASK phase taskArgs= # Additional R3load arguments for LOAD phase loadArgs= # Number of parallel import jobs impJobNum=3 # # E-mail options # # SMTP server mailServer=sap-ag.de # "From" email address mailFrom=mail@sap.com # "To" email address mailTo=mail@sap.com mail@yahoo.com

108/126

PUBLIC

2010-03-16

the directory /install_dir/export_dump/DB the files DDL<DBTYPE>. ■ If the package files have been transferred completely to the server. ■ The import monitor will start to import a package as soon as the file <package>. the directory c:\temp\export_dump\DB\ORA the EXT files generated by R3szchk. cmd files and TSK files (if required) are located in the directory c:\install \start (parameter: installDir). ■ The Export Monitor will write the R3load dump files and the TOC files to the directory c:\temp \export_dump\DATA.TPL generated by R3ldctl as well. STR. the following directories have to exist (see parameter importDirs): ● /install_dir/export_dump/DATA ● /install_dir/export_dump/DB ● /install_dir/export_dump/DB/ORA The directory /install_dir/export_dump/DATA has to contain the STR files generated by R3ldctl. ■ As soon as a package has been exported successfully.. The export itself is not done by the Export Monitor.. as the monitor is started in client mode (parameter ‘server’ is not set). ■ The R3load log files. ■ The R3load log files. EXT. the Export Monitor will write a signal file <package>. cmd files and TSK files (if required) will be located in the directory / install_dir/start (parameter: installDir). ■ The file DDLORA. . the Export Monitor will transfer all files belonging to that package (TOC. the directory c:\temp\export_dump\DB the files DDL<DBTYPE>. 2010-03-16 PUBLIC 109/126 .7 7. the directory /install_dir/export_dump/DB/ORA the EXT files generated by R3szchk.SGN to the directory /install_dir/exchange (parameter: ftpExchangeDir) to notify the Import Monitor that it could start the import of this package.TPL has to be copied to the directory /install_dir/start (parameter: installDir) before you can start the Import Monitor. ■ On the import host. the following directories have to exist (see parameter exportDirs): ● c:\temp\export_dump\DATA ● c:\temp\export_dump\DB ● c:\temp\export_dump\DB\ORA The directory c:\temp\export_dump\DATA has to contain the STR files generated by R3ldctl.1 Additional Information R3load Procedures Using the Migration Monitor What happens during export / import with the above listed property files during a system copy with source and target database Oracle: ■ On the export host.SGN is found in the directory /install_dir/exchange (parameter: exchangeDir). 001. too.TPL generated by R3ldctl.) to the target host (parameter: ftpHost) into the corresponding subdirectories of the directory /install_dir/export_dump (parameter: ftpExportDirs) as user <sapsid>adm (parameter: ftpUser) identified by password (parameter: ftpPassword) to logon.

Package export/import in progress. If any ftp/net exchange options are used. To find out the size of the export and the sizes of the tablespaces or dbspaces that are created.log Both the export and import state files contain package state lines such as the following: SAPUSER=+ Format of lines is <PACKAGE>=<STATE>. Then the export state file contains package state lines such as the following: SAPUSER=++ Format of lines is <PACKAGE>=<STATE>. look at the file DBSIZE. 7. Possible values for state are: 0 ? +0 +? +++ Package export not yet started. then the export state file may contain a second <STATE> column.XML located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE> (Windows) or <EXPDIR>/DB/ <DATABASE> (UNIX). Package transfer finished successfully.properties ExportMonitor.log export_state. Possible values for state are: 0 ? + Package export/import not yet started. Package export/import finished successfully. package transfer not yet started. Package transfer in progress. which refers to the state of the package transfer.7 7.properties ■ ImportMonitor.1 Additional Information R3load Procedures Using the Migration Monitor 7.log Import ■ import_monitor. Package transfer finished with errors.log ■ import_state.console.1.1.console. Package export finished with errors. 110/126 PUBLIC 2010-03-16 .7 Installing the Target System Using the Migration Monitor Prerequisites Make sure there is enough free space in the target system for the database load. Package export/import finished with errors. Package export finished successfully.6 Output Files Export ■ ■ ■ export_monitor. Package export in progress.

follow the instructions in the SAPinst input dialogs and enter the required parameters up to the screen ABAP System > Database. 2010-03-16 PUBLIC 111/126 . You start SAPinst as described in the installation documentation for your SAP component. Select the option Use Migration Monitor. choose Standard System Copy/Migration (R3load-Based). 3. make sure that at least the dump directory with the following files is accessible on the target host and contain correct data before you start SAPinst: ■ <dump dir>/LABEL. 2. 6.2 Additional Information Using SAPinst GUI Procedure 1. If you want to start the installation of the target host using the migration monitor.XML ■ <dump dir>/DB/DDLORA.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 Displays detailed information about each input parameter. 7. On this screen. CAUTION If you have to restart the import after an error. NOTE 5. If you need more information about input parameters. When SAPinst displays the CD browser-window and asks for the Export Migration CD. Check that the prerequisites in the dialog box are fulfilled by your system. enter the path to the export directory <EXPDIR>.7 7. you can now start the data load by starting the Import Monitor.ASC ■ <dump dir>/DB/<DBTYPE>/DBSIZE.TPL If the dump directory is not shared on the target host. Complete the installation as described in the installation documentation for your SAP solution. just restart SAPinst. 7. you can start the Migration Monitor. 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. The import is continues with the table that was not imported successfully. 4. To install the target system. position the cursor on the field of the respective parameter and press F1. If so. 8. you can copy the files as soon as they have been created on the source host with the (export) migration monitor's FTP Copy options from the source system to the target system.

NOTE Menu option Menu option File File View Log Exit Message button Message button Message button Retry View Log Stop Message button Continue If for some reason you need to log off during the installation from the host where you control the installation with SAPinst GUI. The dialog box contains a short description about the choices listed in the table below as well as a path to a log file that contains detailed information about the error. but SAPinst and the GUI server continue running. The following table describes the options in the dialog box: Option Definition Retry SAPinst retries the installation from the point of failure without repeating any of the previous steps. If the same or a different error occurs again. the installation pauses and a dialog box appears. the installation continues while you are logged off. SAPinst and the GUI server) without further changing the installation files. Continues with the option you have chosen before.log) Stops the installation (SAPinst GUI. You can later reconnect to the same SAPinst installation from the same or another host. ■ Continue For more information. 112/126 PUBLIC 2010-03-16 . see the description of the message button below.log) Cancels the installation with the following options: ■ Stop For more information.3 Interrupted Installation with SAPinst The SAP system installation might be interrupted for one of the following reasons: ■ An error occurred during the dialog or processing phase: SAPinst does not abort the installation in error situations.3 Additional Information Interrupted Installation with SAPinst Label Description Input Type Menu option File Log off Stops the SAPinst GUI. You can continue the installation later from this point. 7.xml file. see the description of the message button below. see Starting SAPinst GUI Separately [page 116]. ■ You interrupted the installation by choosing Exit in the SAPinst menu. For more information. Performs the installation step again (if an error has occurred). try to solve the problem and then choose Retry. This is possible because SAPinst records the installation progress in the keydb.7 7. We recommend that you view the entries in the log files. Displays the installation log (sapinst_dev. If an error occurs. Displays the installation log (sapinst_dev. SAPinst displays the same dialog box again.

exe End of: Windows | 6. Only valid for: Windows | Change to the required directory <DVD drive>:\IM_WINDOWS_<platform> Double-click sapinst. See the procedure below. Only valid for: Windows | Log on as a user who is a member of the local administrators group. or to continue an interrupted installation after an error situation. Only valid for: Unix | Mount your Installation Master DVD.xml file. NOTE You can also terminate SAPinst by choosing Ctrl + C . SAPinst continues the installation from the current point. We do not recommend using Network File System (NFS). we do not recommend that you use Ctrl + C . Only valid for: Unix | Enter the following commands: cd <Installation_Master_DVD>/IM_<OS> 2010-03-16 PUBLIC 113/126 .7 7. closing the dialog box. NOTE Mount the DVD locally.3 Option Additional Information Interrupted Installation with SAPinst Definition Stop Continue Only valid for: UNIX | SAPinst stops the installation. End of: Windows | 4. Therefore. End of: UNIX | Procedure This procedure describes the steps to restart an installation. the SAPinst GUI. and the GUI server. you can continue the installation from the point of failure without repeating any of the previous steps. because this kills the process immediately. 1. CAUTION Make sure that the root user has not set any environment variables for a different SAP system or database. End of: Windows | 2. However. SAPinst records the installation progress in the keydb. which you stopped by choosing Stop. End of: Unix | 5. End of: UNIX | 3. Only valid for: UNIX | Log on to your local UNIX host as user root. Only valid for: Windows | Insert the Installation Master DVD in your DVD drive.

exe ■ If you used an alternative installation directory: cd <Mapped_Drive>:\<your installation directory> <Mapped_Drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64\sapinst.7 7./sapinst End of: Unix | 7. ■ If you used the default installation directory (recommended): cd <Mapped_Drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64 sapinst.4 Performing a Remote Export Using SAPinst Purpose You can run the SAPinst GUI in standalone mode to perform a remote export. it moves the content of the old installation directory and all installation-specific files to the backup directory. 9.exe under Processes in your Task Manager and kill it. If a process is still running. In the What do you want to do? screen. For the backup directory. the following naming convention is used: <log_day_month_year_hours_minutes_seconds> (for example. you can no longer continue the old installation.exe End of: IBM i5/OS | 8. decide between the following alternatives and confirm with OK. Prerequisites ■ Make sure that you have performed the preparation activities for your local host (SAPinst GUI host) and your remote host as described in Prerequisites in Exporting the Source System Using SAPinst [page 30]. look for javaw.4 Additional Information Performing a Remote Export Using SAPinst . the Welcome screen does not appear. log_01_Oct_2003_13_47_56). NOTE If there is only one component to install. SAPinst continues the interrupted installation from the point of failure. select the installation service that you want to continue and choose Next. Only valid for: IBM i5/OS | Check if a SAPinst GUI Java process is still running. The What do you want to do? screen appears. 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. Instead. From the tree structure in the Welcome screen. 114/126 PUBLIC 2010-03-16 . Afterwards. Behavior Alternative Run a new Installation Continue old installation SAPinst does not continue the interrupted installation.

7 7.4

Additional Information Performing a Remote Export Using SAPinst

■ Both computers are in the same network and can ping each other. To test this: ● Log on to your remote host and enter the command ping <local host>. ● Log on to the local host and enter the command ping <remote host>.
Process Flow

1. You start the SAPinst server on your remote host. 2. You start the SAPinst GUI on your local host. 3. You perform the installation using the SAPinst GUI. For more information, see: ■ Starting SAPinst on the Remote Host [page 115] ■ Starting SAPinst GUI Separately [page 116]

7.4.1 Performing a Remote Installation with SAPinst (Optional)
You use this procedure to install your SAP system on a remote host. In this case, SAPinst and the GUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is the host from which you control the installation with SAPinst GUI.
Only valid for: SAP CRM;SAP SCM;SAP SRM | SAP CRM 5.2;SAP SCM 5.1;SAP SRM Server 6.0 |

You can run SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host.
End of: SAP CRM;SAP SCM;SAP SRM | SAP CRM 5.2;SAP SCM 5.1;SAP SRM Server 6.0 | Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

CAUTION

If you install SAP instances on System i, “local host” in this section refers to the Windows installation host, not the System i host.
End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

Prerequisites

■ Both computers are in the same network and can “ping” each other. To test this: ● Log on to your remote host and enter the command ping <local host>. ● Log on to the local host and enter the command ping <remote host>.
Procedure
Only valid for: IBM i5/OS;Windows |

1. 2. 3.

Log on to your remote host as a user who is a member of the local administrators group. Insert the Installation Master DVD in the DVD drive on your remote host. Open a command prompt and change to the required directory of the installation Master DVD.

2010-03-16

PUBLIC

115/126

7 7.4

Additional Information Performing a Remote Export Using SAPinst

Enter the following commands:
Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |

<DVD drive:\>cd <DVD drive>:\IM_WINDOWS_<platform>
End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle | Only valid for: IBM DB2 for i5/OS (Linux/Windows) |

cd <mapped drives>:\IM_OS400_PPC64
End of: IBM DB2 for i5/OS (Linux/Windows) |

sapinst.exe -nogui

For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 30]. SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the command prompt:
guiengine: no GUI connected; waiting for a connection on host <host_name>, port <port_number> to continue with the installation

4.

Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 116].

End of: IBM i5/OS;Windows | Only valid for: UNIX |

1.

Log on to your remote host as user root.
CAUTION

2. 3.

Make sure that the root user has not set any environment variables for a different SAP system or database. Mount the Installation Master DVD. Enter the following commands:
cd <Installation_Master_DVD>/IM_<OS> ./sapinst -nogui

For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 30]. SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the command prompt:
guiengine: no GUI connected; waiting for a connection on host <host_name>, port <port_number> to continue with the installation.

4.

Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 116].

End of: UNIX | Only valid for: IBM i5/OS;UNIX;Windows |

7.4.2 Starting SAPinst GUI Separately (Optional)
You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI separately in the following cases: ■ You have logged off from SAPinst.

116/126

PUBLIC

2010-03-16

7 7.4

Additional Information Performing a Remote Export Using SAPinst

If you logged off during the installation and you later want to reconnect to the installation while it is still running, you can start SAPinst GUI separately. ■ You want to perform a remote installation [page 115]. If you want to run SAPinst GUI on a different host from SAPinst and the GUI server, you have to start SAPinst GUI separately.
Only valid for: SAP CRM;SAP SCM;SAP SRM | SAP CRM 5.2;SAP SCM 5.1;SAP SRM Server 6.0 |

You can run SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host.
End of: SAP CRM;SAP SCM;SAP SRM | SAP CRM 5.2;SAP SCM 5.1;SAP SRM Server 6.0 | Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

CAUTION

If you install SAP instances on System i, “local host” in this section means the Windows installation host, not the System i host.
End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

Prerequisites

You have installed the Java Runtime Environment [page 19] on the host on which you want to start SAPinst without SAPinst GUI.
Procedure
Starting SAPinst GUI on a Windows Platform

1. 2. 3.

Log on as a member of the local administrators group. Insert the SAP Installation Master DVD into your DVD drive. Open a command prompt and change to the relevant directory:
Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |

<DVD drive>:\IM_WINDOWS_<platform>
End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle | Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |

cd <mapped drives>:\IM_OS400_PPC64
End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |

4.

Start SAPinst GUI in one of the following ways: ■ If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following command:
startinstgui.bat

SAPinst GUI uses the local host as default. ■ If SAPinst and the GUI server runs on a different host from SAPinst GUI (remote installation), enter the following command:
startinstgui.bat -host <host_name> <host_name> is the host name of the installation host.

2010-03-16

PUBLIC

117/126

We do not recommend that you use Network File System (NFS)./startInstGui. ■ If SAPinst and the GUI server run on a different host from SAPinst GUI (remote installation). change to the same directory as your SAPinst executable and enter the command startinstgui. SAPinst GUI uses the local host as default. To change to the mount directory enter the following command: cd <Installation_Master_DVD>/IM_<OS> Start the SAPinst GUI in one of the following ways: ■ If SAPinst GUI runs on the same host as SAPinst and the GUI server. enter the name of host on which SAPinst is running and choose Log on.7 7. Log on as user root. SAPinst GUI cannot connect and the SAP Installation GUI Connection dialog appears. 4.sh SAPinst GUI uses as default the local host. SAPinst GUI uses the local host as default.4 Additional Information Performing a Remote Export Using SAPinst NOTE ● If you enter the command without additional parameters. Mount the DVD locally./startInstGui. The first dialog of the installation appears and you can perform the remote installation from your local host.bat -h.sh -host <host_name> <host_name> is the host name of the installation host. Since SAPinst and the GUI server are running on another host. Starting SAPinst GUI on a UNIX Platform 1. 118/126 PUBLIC 2010-03-16 . Since SAPinst and GUI server are running on another host. enter the following command without additional parameters: . enter the name of the host on which SAPinst is running and choose Log on. NOTE 3. Make sure that the root user has not set any environment variables for a different SAP system or database. enter the following command with additional parameters: . SAPinst GUI starts and tries to connect to the GUI server and SAPinst. ● For a list of options to start SAPinst GUI. SAPinst GUI cannot connect and the SAP Installation GUI Connection dialog appears. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. CAUTION 2. NOTE ● If you enter the command without additional parameters. In this case. Mount your installation DVD. In this case.

sh -h.4 Additional Information Performing a Remote Export Using SAPinst The first dialog of the installation appears and you can perform the remote installation from your local host.Windows | 2010-03-16 PUBLIC 119/126 . End of: IBM i5/OS.7 7./startInstGui. change to the same directory as your SAPinst executable and enter the command .UNIX. ● For a list of options to start SAPinst GUI.

Arrows separating the parts of a navigation path. for example. names of variables and parameters. SELECT and INCLUDE Keys on the keyboard http://www.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. menu names. pushbutton labels. screen titles. program names. These include report names. SAP Note 123456 ■ Words or characters quoted from the screen. upgrade. and names of installation. 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. and database tools Technical names of system objects. database table names. ■ Cross-references to other documentation or published works ■ Output on the screen following a user action. for example. These include field labels.com /example 123456 Example Example EXAMPLE EXAMPLE 120/126 PUBLIC 2010-03-16 . for example. messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths.sap. and key concepts of a programming language when they are surrounded by body text. for example. transaction codes. “Enter your <User Name>”. for example. and menu options.

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

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

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

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

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

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

Sign up to vote on this title
UsefulNot useful