Systemcopy 731 Abja Pi

System Copy Guide SAP Systems Based on SAP NetWeaver 7.3 including EHP 1 ABAP +Java (for Process Integration)Target Audience System administrators Technology consultants

CUSTOMER Document version: 1.4 2012-06-25

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.4 1.3 1.2 1.1 1.0

2012-06-25 2012-03-09 2012-02-27 2012-01-16 2011-11-21

Minor changes Update for IBM i-specific information and removal of erroneously included Sybase ASE-specific information Minor changes Update for Sybase ASE Initial version

2/166

CUSTOMER

2012-06-25

Table of Contents

Chapter 1 1.1 1.2 1.3 1.4 Chapter 2 Chapter 3 3.1 3.2 3.3 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.3 4.6 4.6.1 4.6.2 Chapter 5 5.1

Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 7 8 9 9

Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Technical Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Usage-Type-Specific Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Independent System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Copy Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating DDL Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the Table Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing Parallel Export and Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting the Source System Using SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . Running SAPinst on UNIX or Windows to Perform the Export . . . . . . . . . . . . Running SAPinst on IBM i to Perform the Export . . . . . . . . . . . . . . . . . . . . . . Starting SAPinst on IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing an IBM i User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying the Installation Media Manually to Your IBM i . . . . . . . . . . . . . . . . . Restarting R3load Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transferring the Export Files to the Target Host . . . . . . . . . . . . . . . . . . . . . . . Installing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 15 17 18 21 22 24 25 28 29 29 33 33 37 38 40 41 42 43

Database-Specific System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Oracle-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

2012-06-25

CUSTOMER

3/166

5.1.1 5.1.2 5.1.2.1 5.1.2.2 5.1.3 5.1.4 5.1.5 5.2 5.3 5.4 5.5 5.6 5.6.1 5.6.2 5.6.3 5.6.3.1 5.6.3.2 5.6.3.3 5.6.3.4 5.6.3.5 5.6.3.6 5.6.3.7 5.6.3.8 5.6.3.9 5.6.4 5.6.5 5.6.6 5.6.7 5.6.8 5.6.9 5.6.10 5.6.11 5.6.12 5.6.13 5.6.14

Generating the Control File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an Offline Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an Offline or Online Backup with BR*Tools . . . . . . . . . . . . . . . . . . . Preparing the Target System (Oracle) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the Database Files on the Target System . . . . . . . . . . . . . . . . . . . . . Restoring the Database Files on the Target System with BR*Tools . . . . . . . . . SAP MaxDB-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS SQL Server-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBM DB2 for Linux, UNIX, and Windows-Specific Procedures . . . . . . . . . . . . . IBM DB2 for i Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBM DB2 for z/OS Specific Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1: Check Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2: Stop and Restart the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3: Run SQL Statements in the Source System . . . . . . . . . . . . . . . . . . . . . . SQL Statement Number 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Statement Number 02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Statement Number 03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Statement Number 04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Statement Number 05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Statement Number 06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Statement Number 07 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Statement Number 08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Statement Number 09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4: Capturing View Definitions with DB2 V9 (if the Schema Name is to be Changed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5: Stop the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6: Making Copies of Source Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7: Creating the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 9a: Changing the Bootstrap Data Sets (BSDS) . . . . . . . . . . . . . . . . . . . . . . Step 9b: Start the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 9c: Creating a New STOGROUP Using the HLQ of the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 9d: Stopping Index Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 9e: Changing the User-Defined Indexes in the DB2 Catalog . . . . . . . . . . . Step 9f: Restart the Index Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 9g: Creating the Temporary Files for the DB2 Target System . . . . . . . . . .

50 54 54 54 55 57 58 59 62 62 67 67 69 70 70 70 71 72 72 73 74 75 76 77 77 78 78 78 79 79 80 80 81 81 81

4/166

CUSTOMER

2012-06-25

5.6.15 5.6.16 5.6.17 5.6.18 5.6.19 5.6.20 5.7 5.8 Chapter 6 6.1 6.2 6.3 Chapter 7 7.1 7.2 7.2.1 7.2.2 7.2.2.1 7.2.2.2 7.2.2.3 7.2.2.4 7.2.2.4.1 7.2.2.5 7.2.3 7.2.3.1 7.2.3.1.1 7.2.3.1.2 7.2.3.2 7.2.3.2.1 7.2.3.2.2 7.2.3.2.2.1 7.2.3.2.2.2 7.2.3.2.2.3

Step 9h: Implementing HLQ of the Target System in the Work File Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 9i: Adjusting the DDF Location Name and Port Number . . . . . . . . . . . . . Step 10 (DB2 V8 and Lower): Changing the VCAT of the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 10 (DB2 V9): Changing the VCAT of the Target System . . . . . . . . . . . . . . Step 11 (DB2 V9): Changing the Schema of the Target System . . . . . . . . . . . . Step 12: Adapting WLM Application Environments for DB2 Stored Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sybase ASE Server-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP HANA Database-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying Single Instances Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying the Primary Application Server Instance Only . . . . . . . . . . . . . . . . . . Copying the Database Only Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying the Database Only Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

81 82 82 83 83 84 85 86 87 87 87 89

Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Performing Follow-Up Activities in the Source System . . . . . . . . . . . . . . . . . . 91 Performing Follow-Up Activities in the Target System . . . . . . . . . . . . . . . . . . 91 Installing the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Performing Follow-Up Activities for ABAP . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Activities at Operating System Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Activities at Database Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Activities at SAP System Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Usage Type or Software Unit-Specific Follow-Up Activities . . . . . . . . . . . . . . . 96 Embedded Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Checking the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Performing Follow-Up Activities for Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 General Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Configuration Steps for the SAP Java Connector . . . . . . . . . . . . . . . . . . . . . . . 98 Generating Public-Key Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Software Unit-Specific Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Enterprise Services Repository: Connecting to the SLD . . . . . . . . . . . . . . . . . . 99 Process Integration (PI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 PI: System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 PI: Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 PI: Changes in the Exchange Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

2012-06-25

CUSTOMER

5/166

7.2.3.2.2.4 7.2.3.2.2.5 7.2.3.2.2.6 7.2.4 Chapter 8 8.1 8.1.1 8.1.2 8.1.3 8.1.4 8.1.5 8.1.6 8.1.7 8.1.8 8.2 8.2.1 8.2.2 8.2.3 8.2.4 8.3 8.3.1 8.3.2 8.3.3 8.4 8.4.1 8.4.2 8.4.3 8.4.4 8.4.5 8.4.6 8.4.7 8.4.8

PI: Refresh Caches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Switching Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Connection Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Jobhead Correction after Homogeneous System Copy . . . . . . . . Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R3load Procedures Using the Migration Monitor . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning DDL Files to Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Groups of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processing Split Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Migration Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting R3load Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Target System Using the Migration Monitor . . . . . . . . . . . . . . Jload Procedures Using the Java Migration Monitor . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Java Migration Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting Jload Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Package and Table Splitting for Java Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Table Splitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Useful Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entries in the Services File Created by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting During the Database Load . . . . . . . . . . . . . . . . . . . . . . . . . .

103 104 106 106 107 107 108 115 115 116 117 122 123 124 125 126 127 130 130 131 131 134 135 136 136 140 143 146 151 153 154 155

6/166

CUSTOMER

2012-06-25

1 1.1

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

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

Purpose

This document explains how to copy SAP systems in one run using either database-independent methods or database-specific methods.CAUTION

Only perform a system copy if you have experience in copying systems and thorough knowledge of the operating system, the database, the ABAP Dictionary, and the Java Dictionary. Only perform a heterogeneous system copy if you are a certified system support consultant or a certified SAP Technical Consultant.

1.1 Terminology System Copy Duplication of an SAP system. Certain SAP parameters might change in a copy. When you perform a system copy, SAPinst installs all the instances again, but it uses a copy of the source system database to set up the database. Source System and Target System The SAP system containing the original database is called the source system and the system to which the database copy is to be imported is called the target system. Their SAP system names are abbreviated to SOURCE_SAPSID and TARGET_SAPSID. The terms source database and target database are also used in this description. Homogeneous System Copy During the system copy, you use the same operating system and database platform as the original system. Heterogeneous System Copy During the system copy, you change either the operating system or the database system, or both. Heterogeneous system copy is a synonym for migration. Database Copy Database-dependent part of the system copy. Placeholders

2012-06-25

CUSTOMER

7/166

1 1.2

Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver Online Information from SAP

Placeholders such as are used in commands. They are used in the same way as in the SAP system installation documentation. You must replace them with the values valid for your site. The following additional placeholders are used:Placeholder

Meaning

How to find out

SAP system ID System name of the source host System name of the target host 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

Command hostname Command hostname of the original system of the target system of the original system of the target system

1.2 Online Information from SAPBefore you start the system copy, you must read the documentation that is referenced in the following: Read the following SAP Note for up-to-date information on system copy and corrections to the system copy documentation: SAP Note 1620515 (System Copy for SAP Systems Based on SAP NetWeaver 7.3 EHP1) Make sure that you have the most recent version of the SAP Note, which you can find at http://service.sap.com/notes. This documentation describes only the export of the source system in detail. For the installation of the target system, you also need the installation guide for your SAP application. Installation guides are available at http://service.sap.com/instguides.NOTE

If you have problems during the system copy, create a customer message using the application area BC-INS-MIG.More Information

SAP System Copy and Migration at http://www.sdn.sap.com/irj/sdn/systemcopy SAP OS/DB Migration Check at http://service.sap.com/osdbmigration In addition to the information contained on this page, check the SAP OS/DB Migration Planning Guide that is available in the Media Library. SAP system landscape copy: Best Practice document SAP System Landscape Copy for SAP NetWeaver and SAP Solutions at http://service.sap.com/solutionmanagerbp

SAP Note 885343 SAP System Landscape Copy SAP Note 82478 R/3 OS/DB migration

8/166

CUSTOMER

2012-06-25

1 1.3

Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver Accessing the SAP Library

1.3 Accessing the SAP LibraryThe references to SAP NetWeaver Library documentation in this guide always refer to the following on SAP Help Portal: http://help.sap.com/nw731 Application Help SAP Library: English SAP NetWeaver

1.4 Constraints As of SAP NetWeaver 7.0, when your system is a dual-stack system and you perform a system copy, your source system is copied to the target system as a whole. This means that it is neither possible to exclude a single stack from the system copy nor to copy a separate stack only. SAP does not support client transport as a system copy method. Transporting production clients is not supported at all. You can use client transport for the initial setup of an SAP system infrastructure. This documentation does not cover the client copy procedure. This documentation does not describe how to export and import a database with the installation tools for reorganization purposes. Use the appropriate tools for database reorganization, as SAP does not support this installation option. If you have made modifications in your development system and want to copy your quality assurance or production system onto the development system, see SAP Note 130906. This documentation describes how to copy data from one SAP system to another SAP system based on SAP NetWeaver Application Server. This documentation does not describe how to copy data from non-SAP systems to SAP systems. If you want to convert a non-Unicode system to a Unicode system or perform the system copy of a Unicode system, see SAP Note 551344. For the development of Java applications, we strongly recommend that you follow the rules mentioned below. Otherwise, we cannot guarantee that you will be able to copy your Java Engine later with the SAP tools to change your underlying operating system and/or database system. SAP does not support all data archiving operations after a system copy. If you used data archiving in the source system, you might not always have access from the target system to the archive files that were created. For more information, see SAP Note 153433 and System Landscape Optimization at http://service.sap.com/slo. Access from the target system to archived files in the source system without a dedicated archive migration project is only supported as follows: You have copied a source system that uses external data archiving. The target system has readonly access to this archive. You have copied a source system that uses data archiving locally. You can either arrange network access for appropriate archive file sharing or copy all archive files to the file system of the target system.

2012-06-25

CUSTOMER

9/166

1 1.4

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

In all other cases, contact SAP SLO at http://service.sap.com/slo or [email protected]. When you perform a system copy, all software units in the source system are copied to the target system. This means that none of the software units in the target system can be excluded from the system copy, nor can you select software units. Dos and Don'ts for system copy: Do: Save configuration data and runtime data in the Java database only. Follow the Open SQL standard. Make sure that all communication runs through the database pool. Don't: Save any system and infrastructure-specific data in business objects. Use a pointer to the central storage of such information, for example: SAP system ID and SID (SAPSID = SID = SAP system name) Host name IP addresses Services and ports Logical destinations and logical system names Other technical infrastructure names Use file system persistency. Set up dependencies between Java and ABAP. Try to copy the Java part of an ABAP+Java system to a Java standalone system or the other way around. If you have implemented a federated portal network (FPN) across multiple SAP NetWeaver systems, see SAP Note 1080080 before commencing with the system copy.

10/166

CUSTOMER

2012-06-25

2

Planning

2 Planning

This section describes how to plan your system copy. You can use the system copy for the following: Setting up system landscapes (where the SAP systems have different SAPSIDs). Providing systems for testing, demonstration, training, and standby.NOTE

Oracle only: You cannot create standby systems with a system copy. You should perform upgrades in a test system first. This allows you to identify customerspecific problems that might result from modifications. Depending on the purpose of the system, it might be advisable to use the same SAP system ID, even though this prevents you from including the system in a system group for transports. Changing the operating system, the database, or both. You can use different operating system releases or database releases for the source and target systems, but the SAP system release of the source and target systems must be the same. Changing the hardware.Creating A System Copy Plan

Create a plan to perform the system copy. 1. Consider the downtime of the source system (for preparations and copying) when planning the system copy. 2. Perform a test run of the system copy. You can use the time taken by the test run to calculate the system downtime: If you want your target system to replace your source system, try to perform a complete test run. This means that the entire database is exported from the source system, transferred to the target system, and imported there. System downtime is approximately equal to the total test time (that is, time for export, transport, and import). If you do not want to replace your source system, a partial test run (export of the entire database or parts of it) can be sufficient to calculate the system downtime. The source system is only down for the time of the export. Calculating the system downtime is particularly important for very large databases (VLDB) or when tapes are being used. The test run is also to determine the amount of export data. Choose the best data transfer method (for example, FTP or tape). We recommend that you only perform read/write actions on local file systems.

2012-06-25

CUSTOMER

11/166

2

Planning

3.

Define a schedule for the test run and the final system copy. When copying a system that contains production data choose the right time for the copy. This could be a month-end or year-end closing.

Miscellaneous

In the event of a major change in hardware configuration (for example, new machine type, new hard disk configuration, new file system type), consult your SAP-authorized hardware partner. Decide which system copy procedure you want to use: The database-independent procedure [page 21] using SAP tools. Use this method if database-specific methods are either not available or not suitable.NOTE

For a database-heterogeneous system copy and for Unicode conversion, only the database-independent method is available. The database-specific procedure [page 47] using tools provided by the database vendor Some database vendors offer specific tools for copying a database. These tools allow you to: Restore a backup of one database (source database) in another one (target database) (backup method) Unload the source database and load the data into the target database Copy single instances only Copy the primary application server instance only [page 87]. Copy the database only (using SAPinst) [page 87] Copy the database only (using database refresh) [page 89]CAUTION

You cannot copy single usage types or components! Changing the system variant If you want to change your system variant (for example, if you want to make your standard system a distributed or high-availability system), proceed as follows: 1. Perform the export [page 29]. 2. For the import, choose the relevant system copy options as described in the process flows of the system copy procedure [page 22]. Choosing an SAP system ID You can choose the new SAP system ID freely during a new installation.CAUTION

To meet the requirements of the Workbench Organizer, you must choose different SAP system IDs for different SAP systems. SAP license

12/166

CUSTOMER

2012-06-25

2

Planning

Once the installation is completed and the SAP system copy has been imported, you require a new license key for the target system. The license key of the source system is not valid for this system. For information about ordering and installing the SAP license, see the SAP Library [page 9] at: SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management SAP Licenses . For more information about SAP license keys, see http://service.sap.com/licensekey or SAP Note 94998. Archiving files Data that has been archived in the source system (data that does not reside in the database but was moved to a different storage location using SAP Archive Management) must be made accessible in the target system. Adapt the file residence information in the target system. For more information, see the SAP Library [page 9] at: SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Data Archiving . Access to archive files is platform-independent. Configuration analysis and hardware analysis You need to determine the: Number of application servers Expected size of the database Additional disks or other hardware required Required memoryNOTE

See the section on hardware and software requirements in the SAP system installation documentation to determine the system requirements.Usage-Type-Specific Planning Steps

2012-06-25

CUSTOMER

13/166

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

3 3.1

Preparations General Technical Preparations

3 Preparations

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

3.1 General Technical PreparationsTo make a consistent copy of the database, you need to prepare the source system and perform some subsequent actions on the target system. This is not necessary when performing a test run. The following describes important preparations on the source system. For more information about SAP System Administration, see the Administration Information in the SAP Library [page 9].Procedure

1.

Before you start a system copy, check the minimum kernel patch level required by the support package level of the source system. It might be necessary to replace the SAP kernel delivered with the installation kit and installed during the installation of the target system by a newer kernel patch level before starting the target system. If you have to replace the delivered SAP kernel, you can do this after the installation of the primary application server instance.Only valid for: IBM DB2 for i5/OS |

2.

In i5/OS, the installed JVMs available in QIBM/ProdData are queried and the best suited one is chosen. If you want to use another JVM, you must set JAVA_HOME.End of: IBM DB2 for i5/OS |

3.

4.

5.

Check if canceled or pending update requests exist in the system. If canceled or pending updates exist, you must update these again or delete them from all clients. Proceed as follows: 1. Call transaction SM13. 2. Delete the default values for the client, user, and time. 3. Choose all update requests. 4. Check if table VBDATA contains any entries. If there are entries, update or delete the corresponding update requests. 5. To check whether this action was successful, call transaction SE16 for table VBDATA. Set all released jobs from Released to Scheduled (transaction SM37). You also need to do this for jobs that must run periodically (see SAP Note 16083). To select all jobs (include start after event), choose Job Released Scheduled Adapt the operation mode timetable to make sure that no switching of operating modes takes place while a system is being copied (transaction SM63).

2012-06-25

CUSTOMER

15/166

3 3.1

Preparations General Technical Preparations

6.

7.

8.

Write down the logical system names of all clients: If you plan to overwrite an existing system with a system copy, make sure you write down the logical system names of all clients in the system that will be overwritten (transaction SCC4). Since the logical system names will be overwritten, in the event of differences, you must change them back to their original names (as they existed in the system that is overwritten) in the follow-on actions after the system copy. If you create a new system with a system copy (for example, create an upgrade test system), make sure that the logical naming strategy for this new system is consistent with your existing logical system naming convention. If you are still planning your BI (formerly BW) system landscape, see SAP Note 184447. If your system copy is used to replace hardware for the DB server, migrate to a different database system or operating system (that is, source system for the copy is the same as the copy target), no changes to logical system names are required. Before you run the export and after you have performed several checks, delete QCM tables on the source system. Proceed as follows: 1. Before you delete the QCM tables, ensure the following The tables are consistent no restart log or conversion procedure termination must be displayed. The data of the original table can be read. Application programs that use the affected original table run correctly. 2. Call transaction SE14. 3. Choose Extras Invalid temp. table All QCM tables that can be deleted are displayed. 4. Mark the tables and delete them. FI customers: You can perform an additional consistency check by running the job SAPF190 before copying the source system, as well as after copying the target system, and then compare the results. Make sure that no customer data is changed in the meantime. You can do this as follows: In transaction SAPF190, for classic FI, choose Accounting Financial Accounting General ledger Periodic Processing Closing Check/count Reconciliation . For a new general ledger, choose Accounting Financial Accounting General ledger Periodic Processing Closing Check/count Reconciliation (New) . FI customers: You can further check consistency by running the jobs listed below before copying the source system, as well as after copying the target system, and then compare the results. RFUMSV00 (tax on sales/purchases) RAGITT01 (asset history sheet) RAZUGA01 (asset acquisitions)

16/166

CUSTOMER

2012-06-25

3 3.2

Preparations Usage-Type-Specific Preparations

9.

RAABGA01 (fixed asset retirements) Make sure that no customer data is changed in the meantime. CO customers: You can perform an additional consistency check by running the report group 1SIP before copying the source system, as well as after copying the target system, and then compare the results. Make sure that no customer data is changed in the meantime.CAUTION

Prerequisites for an export: Before performing an export, make sure that no incremental conversion is in progress. To test if an incremental conversion is in progress, run transaction ICNV. If there are any table entries in table TICNV, an incremental conversion is in progress. In this case, you have the following options: 1. Defer the migration until the incremental conversion has finished. 2. Try to finish the incremental conversion by performing the following steps: If the tables are in state For conversion or in state Done, delete the entries by choosing Control Delete Entry . If the tables are in any other state, you have to finish the incremental conversion. Choose Assistant and proceed according to the online documentation.CAUTION

Heterogeneous system copy only: Before you start the export of your source system, make sure that the tables TATGPC and TATGPCA are empty. To do so, use your database utility and delete the contents of these tables with the following statements:DELETE from TATGPC DELETE from TATGPCA

If the tables are not empty and you do not delete the contents of these tables you encounter problems while importing the data to your target system because of nonNULL capable fields in these tables.

3.2 Usage-Type-Specific PreparationsProcedureProcess Integration (PI)

After messages have been processed successfully, they are kept in the database for a certain period of time. The data volume of these messages significantly influences the time for export/import. Therefore we strongly recommend that you reduce the amount of data by archiving or deleting messages before starting the export.

2012-06-25

CUSTOMER

17/166

3 3.3

Preparations Preparing the Installation Media

For more information, see the SAP Library [page 9] at SAP NetWeaver Library: Function-Oriented View Process Integration Administering Process Integration (PI) Administering Process Integration (PI) Dual-Stack Management Data Archiving .CAUTION

In case you have configured business systems and the Integration Server in different clients of the same system, be aware that no adoption takes place for the business clients during system copy procedure. You will have to adapt the configuration for these clients afterwards as follows: 1. Adapt the logical system (SALE, SCC4). 2. Create a new business system in SLD after creating a technical system (RZ70). 3. Reconfigure scenarios related to these clients according to the configuration guide.

3.3 Preparing the Installation MediaThis section describes how to prepare the installation media, which you obtain as part of the installation package.Procedure

1.

Identify the required media as listed below.NOTE

The media names listed in the following table are abbreviated. The full labels and the material numbers of all media are listed in the media list of your SAP Business Suite Application or SAP NetWeaver component. You can find the location of the media list in the Master Guide for your SAP Business Suite Application or SAP NetWeaver component at: http://service.sap.com/instguides .SAP Instance Required Folder of Software Packages from Media

Installation Master (folder _IM__) UC or NUC Kernel (folder K___) where U means Unicode and N means non-Unicode. Central services instance for Java (SCS) Installation Master (folder _IM__) UC or NUC Kernel (folder K___) where U means Unicode and N means non-Unicode. Database Software Central services instance for ABAP (ASCS)NOTE

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

Make sure that you have the appropriate installation kit version for your SAP kernel and that the versions of the SAP systems and the installation media are the same on the target and source systems. Exceptions are only allowed if they are described in an SAP Note.

18/166

CUSTOMER

2012-06-25

3 3.3

Preparations Preparing the Installation Media CAUTION

2.

The source system must be in a consistent state before you can copy it. Make the required media available.RECOMMENDATION

3.

You can operate several SAP systems on a single host without encountering any problems. Nevertheless, we recommend that you use a separate host for each system because an SAP system upgrade might depend on an OS upgrade. If the SAP systems are on separate hosts, you can upgrade them at different times. If you want to perform a heterogeneous system copy you need a migration key. You can generate it at http://service.sap.com/migrationkey.

2012-06-25

CUSTOMER

19/166

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

4

Database Independent System Copy

4 Database Independent System Copy

You can use the SAP installation tool SAPinst to export and import your ABAP and Java database content, file system, and all configuration in a database-independent format. SAPinst uses both the R3load and the Jload tools. R3load generates a database export of all SAP objects that are defined in the ABAP Dictionary and archives the configuration and components in the file system. Jload generates a database export of all SAP objects that are defined in the Java Dictionary and archives the configuration and components in the file system.NOTE

Make sure that you have the most recent version of the R3load and Jload tools, which you can find at http://service.sap.com .Constraints R3load and Jload Restrictions

SAPinst generates a database dump of all SAP objects that are defined in the ABAP Dictionary (R3load) or Java Dictionary (Jload). Other objects are not exported by SAPinst. For a consistent database export, no transactions on export-relevant database objects are allowed during the export. Otherwise, the export has to be restarted. Therefore, we recommend that you shut down the SAP system (excluding the database!) for the export. The database must still be running. R3load: Changes to database objects that cannot be maintained in the ABAP Dictionary (transaction SE14), such as the distribution of tables over several tablespaces or dbspaces, are lost after the system copy. R3load: Indexes longer than 18 characters are not allowed on the database to be exported.Only valid for: UNIX;Windows |

Existing Target System

If the target system already exists and if you do not plan to perform an MCOD installation, delete the database on the target system before the import. For more information, see Additional Information in the installation documentation for your SAP component. If the database configuration of your database is stored in the file system, we recommend you to back up these configuration files before deleting the database.End of: UNIX;Windows |

2012-06-25

CUSTOMER

21/166

4 4.1

Database Independent System Copy System Copy Procedure

Splitting STR Files

During the standard system copy process, all tables of the SAP system are grouped into packages, whereby all tables with the same data class belong to the same package. The processing unit for one unload/load process is a package. The packages differ in number and size of contained tables, resulting in varying unload/load runtimes. The overall runtime can be reduced by creating packages of the same size, that is, creating packages with a similar processing time. You can achieve this by splitting the default packages (one package per data class) into more and smaller pieces. There are several options of how to split packages. For a detailed description of the options, see the F1 help about the parameters prompted on theSplit STR Files screen while running SAPinst to export the database. The options can be used separately or when using the new Java based splitting tool combined. Splitting of STR Files is part of the Advanced Export Parameters and is enabled by default. If you select the splitting option (if you did not already perform some tests before), using the splitting tool parameters selected by SAPinst is a good starting point.CAUTION

If you want to split STR files, you must first create the EXT files for the target database system. You can find the EXT files in your export dump directory, subdirectory DB/, for example DB/ORA.

4.1 System Copy ProcedureThis section describes the system copy procedure using R3load and Jload.ProcedureProcess Flow on the Source System (Export)

When performing the export you create a MIGRATION EXPORT CD image, which contains the data of the exported system, and which you use to install the target system. The following figure shows exemplary the export options and their resulting output files.

22/166

CUSTOMER

2012-06-25

4 4.1

Database Independent System Copy System Copy Procedure

Figure 1:

Overview on Export Options

Follow the sequence of steps described in the process flows below for a: Standard system Distributed system or high-availability systemStandard System

To perform the export for a standard system, proceed as follows on the standard system host: 1. Heterogeneous system copy only: Generate the migration key at http://service.sap.com/ migrationkey. Enter the installation number of your source system when prompted. 2. Perform the export on the standard system host: 1. Make sure that the QCM tables are deleted from your system as described in General Technical Preparations [page 15]. 2. Generate DDL statements [page 24]. 3. Prepare the system for table splitting [page 25] (optional). 4. If you want to run export processes in parallel to import processes, run SAPinst on UNIX or Windows [page 29] or on IBM i [page 33] to prepare the source system for the export. In SAPinst, choose the system copy option Export Preparation. 5. Run SAPinst on UNIX or Windows [page 29] or on IBM i [page 33] to export the database instance. In SAPinst, choose the system copy option Database Instance Export.NOTE

If R3load processes fail due to an error, solve the problem, and perform the restart as described in Restarting R3load Processes [page 40].

2012-06-25

CUSTOMER

23/166

4 4.2

Database Independent System Copy Generating DDL StatementsOnly valid for: UNIX |

CAUTION

If your database instance is running on HP PA-Risc, you must proceed as described in SAP Note 884452.End of: UNIX |

Distributed System or High-Availability System

To perform the export for a distributed system or a high-availability system, proceed as follows: 1. Heterogeneous system copy only: Generate the migration key at http://service.sap.com/ migrationkey. Enter the installation number of your source system when prompted. 2. Perform the export on the database instance host: 1. Make sure that the QCM tables are deleted from your system as described in General Technical Preparations [page 15]. 2. Generate DDL statements [page 24]. 3. If you want to run export processes in parallel to import processes, run SAPinst on UNIX or Windows [page 29] or on IBM i [page 33] to prepare the source system for the export. In SAPinst, choose the system copy option Export Preparation. 4. Prepare the system for table splitting [page 25] (optional). 5. Run SAPinst on UNIX or Windows [page 29] or on IBM i [page 33] to export the database instance. In SAPinst, choose the system copy option Database Instance Export.NOTE

If R3load processes fail due to an error, solve the problem, and perform the restart as described in Restarting R3load Processes [page 40].Only valid for: UNIX |

CAUTION

If your database instance is running on HP PA-Risc, you need to proceed as described in SAP Note 884452.End of: UNIX |

Result

You have finished this part of the system copy. To complete the system copy, set up the target system using SAPinst. For more information, see Setting Up the Target System Using SAPinst [page 41]

4.2 Generating DDL StatementsTo migrate nonstandard database objects, you need to generate DDL statements using the ABAP report SMIGR_CREATE_DDL. You must perform this procedure before starting SAPinst.

24/166

CUSTOMER

2012-06-25

4 4.3

Database Independent System Copy Preparing the Table Split

Procedure

1. 2. 3.

Log on to the system as a system administrator in a productive client. Call transaction SE38 and run the program SMIGR_CREATE_DDL. Select the target database. Depending on the database manufacturer, you might need to select the database version. The value help supports you in selecting the database version.NOTE

4. 5. 6. 7.

Only enter a database version that is available in the value help. 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). Specify an empty working directory to which the files generated by the report are to be written. If required, you can restrict the generation of DDL statements to specific table types or individual tables. Execute the program. The DDL statements are generated and are written to the specified directory.NOTE

Ensure that the user adm of the target system has read access to the generated SQL files. From there, SAPinst copies them to the /ABAP/DB export directory.

If no database-specific objects exist in the database, no SQL files will be generated. As long as the report terminates with status Successfully, this is not an error. For additional database-specific information, see also SAP Note 888210.

4.3 Preparing the Table SplitThe R3ta tool processes large tables. Instead of exporting/importing one table with one R3load process, the table is processed in, for example, 10 entities. Each entity can be processed by different R3load processes. The advantages of splitting the tables are: Large tables are processed in smaller packages. If the export or import of a table aborts with an error, only the processing of the package where the error occurred has to be repeated and not for the complete table. The export and import of one table can be performed in parallel by starting several R3load processes to work on some packages in parallel.Prerequisites

The export and import has to be performed with the Migration Monitor when the table splitting feature is used. For more information about the Migration Monitor, see R3load Procedures Using the Migration Monitor [page 107].

2012-06-25

CUSTOMER

25/166

4 4.3

Database Independent System Copy Preparing the Table Split

For the following databases, we recommend that you create an index on the column listed in the hints file for the table you want to split before starting R3ta: IBM DB2 for z/OS (Only create a temporary index if you want to perform an unsorted unload.) Oracle For more information, see section Creating a Temporary Index.Restrictions

Only tables that are described in the SAP dictionary can be split. The following tables cannot be split: DDNTF DDNTF_CONV_UC DDNTT DDNTT_CONV_UC DDLOG (is never copied, but created empty in the target system)Procedure

1.

Create a file that contains lines of the form % for all tables to be split. or column>. For

Oracle PL/SQL splitter only: Use the form %; -listenerPort End of: UNIX | Only valid for: Windows |

Log on as adm Enter the following commands:

50/166

CUSTOMER

2012-06-25

5 5.1

Database-Specific System Copy Oracle-Specific Procedure ora_br_copy.bat -generateFiles -forceLogSwitches -targetSid password Database screen. On this screen, choose Standard System Copy/Migration (R3load-Based). Select the Use Migration Monitor option.

2. 3.

4.

124/166

CUSTOMER

2012-06-25

8 8.2

Additional Information Jload Procedures Using the Java Migration Monitor NOTE

5. 6.

If you need more information about input parameters, position the cursor on the field of the respective parameter and press F1 . When SAPinst displays the CD browser window and asks for the Export Migration CD, enter the path to the export directory . Continue as described in the installation documentation for your SAP component until a dialog box appears that states:If the export has been started on the source system and the export monitor is running, you can now start the data load by starting the import monitor.

7. 8.

Check that the prerequisites in the dialog box are fulfilled by your system. If so, start the Migration Monitor. Complete the installation as described in the installation documentation for your SAP solution.CAUTION

If you have to restart the import after an error, just restart SAPinst. The import is continued with the table that was not imported successfully.

8.2 Jload Procedures Using the Java Migration MonitorPurpose

The Java Migration Monitor is a tool that helps you to perform and control the unload and load process for the Java stack during the system copy procedure. The Java Migration Monitor performs the following steps: Starting the Jload processes to load or unload the data according to users requirements Informing the person performing the system copy in case of errorsTool

The tool is part of the archives J2EEINSTALL.SDA (jar file) and CORETOOL*.SCA (guide, scripts, property files) and consists of the following files: User Guide JMigMonUserGuide.pdf Located: On Windows: :\usr\sap\\SYS\global\sltools On UNIX, IBM i: /sapmnt//global/sltools Scripts jmigmon_export.sh / jmigmon_export.bat jmigmon_import.sh / jmigmon_import.bat Located: On Windows::\usr\sap\\SYS\global\sltools

2012-06-25

CUSTOMER

125/166

8 8.2

Additional Information Jload Procedures Using the Java Migration Monitor

On UNIX, IBM i: /sapmnt//global/sltools jar archive sdt_jcopy_jmigmon.jar Located: On Windows::\usr\sap\\SYS\global\sltools\sharedlib On UNIX, IBM i: /sapmnt//global/sltools/sharedlib Property files export.jmigmon.properties import.jmigmon.properties Located: On Windows::\usr\sap\\SYS\global\sltools On UNIX, IBM i: /sapmnt//global/sltools

8.2.1 ConfigurationThe following options can be provided via the property file or via command line. Command line parameters take precedence over parameters specified in the property file.Help

With the following command line option, the tool displays all parameters available:-help Version

With the following command line option, the tool displays version information:-version General Options General Options Namemode

Description

Comments

sid dsn

Java Migration Monitor mode: import or export SAP system ID of the system Data Source Name

Only available as command line option Specifies the SAP system ID of the system Specifies the Data Source Name and is registered in the SecureStore; usually jdbc/pool/

ssProps

ssKey orderBy

Path to the SecureStore properties On Windows: local drive or UNC path file Path to SecureStore key file On Windows: local drive or UNC path Package order This can be the name or path of the file that contains package names. If the option value is omitted the package order is not determined.

126/166

CUSTOMER

2012-06-25

8 8.2 NamejobNum

Additional Information Jload Procedures Using the Java Migration Monitor Description Comments

monitorTimeout disableStatistics

Number of parallel export jobs Monitor time-out in seconds Disables statistics logging

Default: 3 Default: 30 seconds Disables statistics logging for each Jload process: Therefore Jload does not collect statistics data that could later be displayed by the time analyzer.

Mandatory General Options

The following options are mandatory: sid, dsn, ssProps, ssKeyExport Options NameexportDirs

Description

Comment

Export directories path

Specifies the path or paths for exported data and triggers the export functionality. Separator on Windows: ; Separator on UNIX, IBM i: :

Mandatory Export Options

The following export option is mandatory:exportDirs Import Options NameimportDirs

Description

Comment

Import directories path

Specifies the path or paths for imported data and triggers the import functionality. Separator on Windows: ; Separator on UNIX, IBM i: :

Mandatory Import Options

The following import option is mandatory:importDirs

8.2.2 Starting the Java Migration MonitorThe application allows you to specify options in the command line or in the export or import property files. The names of the property files are export.jmigmon.properties and import.jmigmon.properties. Any options specified in the command line take precedence over the corresponding options in the application property file. Options are case-sensitive; any options that are not recognized are ignored.

2012-06-25

CUSTOMER

127/166

8 8.2


PrerequisitesNOTE

We recommend to create a certain directory and start the tool from there, because the Java Migration Monitor produces log and trace files in the current working directory. Before you run the Java Migration Monitor, set the following environment variables: SLTOOLS_HOME

Set this variable to the following directory: On Windows::\usr\sap\\SYS\global\sltools\sharedlib or :\sapmnt \\SYS\global\sltools\sharedlib

On UNIX, IBM i:/sapmnt//global/sltools/sharedlib

SLTOOLS_SECURITY_HOME

Set this variable to the directory, which contains the iaik_jce.jar file. The default directory is: On Windows: :\usr\sap\\SYS\global\security\lib\tools or :\sapmnt\\SYS\global\security\lib\tools

On UNIX, IBM i: /sapmnt//global/security/lib/tools SLTOOLS_DBDRIVER_HOME

Set this variable to the directory, which contains the database driver.EXAMPLE

For MaxDB on Windows: :\sapdb\programs\runtime\jarProcedure

1.

2.

Start the Java Migration Monitor as user adm as follows: With UNIX and IBM i shell scripts jmigmon_export.sh or jmigmon_import.sh With Windows batch files jmigmon_export.bat or jmigmon_import.bat Specify options as required in one of the following ways: Command line: Specify an option in the format optionName optionValue. Property file: Add an option as a new line in the format optionName=optionValue.NOTE

To check the monitor processing state, use the monitor

*.log and *.console.log files.

128/166

CUSTOMER

2012-06-25

8 8.2


In case you use an invalid option or you enter -help, the available options for starting the tool are displayed.ExampleCommand line for UNIX, IBM i ./jmigmon_export.sh -sid CE3 -dsn jdbc/pool/CE3 -ssProps /sapmnt/global/security/data/ SecStore.properties -ssKey /sapmnt/global/security/data/SecStore.key -exportDirs D:/ JPKGCTL Command line for Windows jmigmon_export.bat -sid CE3 -dsn jdbc/pool/CE3 -ssProps D:\usr\sap\CE3\SYS\global \security\data\SecStore.properties -ssKey D:\usr\sap\CE3\SYS\global\security\data \SecStore.key -exportDirs D:\JPKGCTL export.jmigmon.properties file with export options # jmigmon mode: import or export mode = export # number of parallel export jobs, default is 3 jobNum = 1 # of the system sid = CE3 # name of datasource registered in system's SecureStore; usually jdbc/pool/ dsn = jdbc/pool/CE3 # path of the SecureStore properties file ssProps = D:\usr\sap\CE3\SYS\global\security\data\SecStore.properties # path of the SecureStore key file ssKey = D:\usr\sap\CE3\SYS\global\security\data\SecStore.key # list of export directories exportDirs = D:\JPKGCTL # monitor timeout in seconds, default is 30 monitorTimeout = 30 import_monitor.properties file with import options # jmigmon mode: import or export mode = export # number of parallel export jobs, default is 3 jobNum = 1 # of the system sid = CE3 # name of datasource registered in system's SecureStore; usually jdbc/pool/

2012-06-25

CUSTOMER

129/166

8 8.2


dsn = jdbc/pool/CE3 # path of the SecureStore properties file ssProps = D:\usr\sap\CE3\SYS\global\security\data\SecStore.properties # path of the SecureStore key file ssKey = D:\usr\sap\CE3\SYS\global\security\data\SecStore.key # list of import directories importDirs = D:\export\unpacked\JAVA\JDMP # monitor timeout in seconds, default is 30 monitorTimeout = 30

8.2.3 Output FilesExport

export.state.properties .xml.log

Import

import.state.properties .xml.log Both the export and import state files contain package state lines such as the following:SAPUSER=+

Format of lines is =. The following table shows the possible values for state:Value Description

0 ? +

Package export/import not yet started. Package export/import in progress. Package export/import finished with errors. Package export/import finished successfully.

8.2.4 Restarting Jload ProcessesThe state file allows package states to be manually updated to restart failed Jload processes.EXAMPLE

If package processing failed and the package state has the value , you can set the state to 0 to restart the package processing.Procedure

To restart package processing, set the package state from - to 0. To skip package processing, set the package state from 0 or - to +.

130/166

CUSTOMER

2012-06-25

8 8.3

Additional Information Package and Table Splitting for Java Tables CAUTION

This is not recommended because it can cause inconsistent data files or database content. If the package is currently being processed (package state is ?) then any manual modifications of the package state are ignored.

8.3 Package and Table Splitting for Java TablesPurpose

The Java Splitter offers the following possibilities: Splitting the default packages EXPORT.XML and IMPORT.XML into several smaller and equal sized packages: Extracting large tables into packages of their own Splitting large tables into several smaller and equal sized packages (table splitting) The tool provides the corresponding split packages for export and import. Package splitting and table splitting can be used combined or separately.Tool

The tool archive consists of the following: User Guide JSplitterUserGuide.pdf Located: On Windows: :\usr\sap\\SYS\global\sltools On UNIX, IBM i: /sapmnt//global/sltools Scripts for starting the tool standalone jsplitter.sh, jsplitter.bat Located: On Windows: :\usr\sap\\SYS\global\sltools On UNIX, IBM i: /sapmnt//global/sltools jar archive sdt_jcopy_jpkgctl.jar Located: On Windows::\usr\sap\\SYS\global\sltools\sharedlib On UNIX, IBM i: /sapmnt//global/sltools/sharedlib

8.3.1 ConfigurationThe following options can be provided via the property file or via command line. Command line parameters take precedence over parameters specified in the property file.

2012-06-25

CUSTOMER

131/166

8 8.3 Help

Additional Information Package and Table Splitting for Java Tables

With the following command line option, the tool displays all parameters available:-help General Options General Splitting Options Optionhelp

Description

Comment

sid dsn

Prints help options for the parameters and their usage SAP system ID of the system Data Source Name

none

ssProps ssKey dataDir

log

Specifies the SAP system ID of the system Specifies the Data Source Name and is registered in the SecureStore; usually jdbc/pool/ Path to the SecureStore properties file On Windows: local drive or UNC path Path to SecureStore key file On Windows: local drive or UNC path Output data directory If this option is missing, the split rules are taken from the command line arguments. Log file with program output messages Default log file name is JPkgClt.console.log. and errors The log file is created in the current working directory. In addition, the JPkgCtl.trc trace file with detailed process descriptions, errors, and messages is generated.

Mandatory General Options

The following splitting options are mandatory for both package and table splitting: sid, dsn, ssProps, ssKey, dataDirPackage Splitting Options Package Splitting Options Optionsplit

Description

Comment

Size of the split packages

Size can be specified without unit (bytes assumed), as kilobytes (K), megabytes (M), gigabytes (G), or terabytes (T), for example, 1048576, 200M, 8G, and so on.

Additional Mandatory Option for Package Splitting

Splitting option: splitTable Splitting Options Table Splitting Options Optionsplitrulesfile

Description

Comment

Files that describe, which tables shall be split and how

Syntax:::

132/166

CUSTOMER

2012-06-25

8 8.3 Option

Additional Information Package and Table Splitting for Java Tables Description Comment EXAMPLEJ2EE_CONFIG:2: J2EE_CONFIGENTRY:4:CID

tablesplit

Parameter for specifying rules for Syntax: table splitting on the command ::

checksplitrules

Checks the following: Syntax: Syntax of splitrulesfile :: If all database tables specified in the splitrulesfile withoutCOLUMN_TO_BE_USED_FOR_ SPLITTING have a primary key It expects a file as an argument.

CAUTION

When configuring table splitting for a table without primary key (such as J2EE_CONFIGENTRY), you have to provide a value for parameter . If the table to be split has a primary key, this parameter is optional.Additional Mandatory Options for Table Splitting

Splitting options: splitrulefile, tablesplitExampleJSplitter_cmd.properties: # # Table Splitting options # # Common options # # List of SAPSID, data source name[,SecureStore property file, SecureStore key file] [,SecureStore key phrase] -sec=CE1, jdbc/pool/CE1,D:\usr\sap\CE1\SYS\global\security\data\SecStore.properties, D:\usr\sap\CE1\SYS\global\security\data\SecStore.key # Size of the split package with tables -split=200M # Output data directory -dataDir=C:\jsplitter_export_dir # File that contains key fields for each table with the following syntax:

2012-06-25

CUSTOMER

133/166

8 8.3


:: -splitrulesfile=C:\jsplitter_export_dir\splitrulesfile.txt # Log file with program output messages and errors -log= # Check splitrulesfile syntax -checksplitrules=C:\jsplitter_export_dir\splitrulesfile.txt

8.3.2 Starting the Table SplitterRECOMMENDATION

We recommend to create a certain directory for splitting and start the tools from there, because the splitter produces log and trace files in the current working directory. The application allows you to specify options in the command line or in the application property file. The name of the property file is JSplitter_cmd.properties. Any options specified in the command line take precedence over the corresponding options in the application property file. Options are case-sensitive; any options that are not recognized are ignored.Prerequisites

Before you run the table splitter, set the following environment variables: SLTOOLS_HOME

Set this variable to the following directory: On Windows: :\usr\sap\\SYS\global\sltools\sharedlib or :\sapmnt\\SYS\global\sltools\sharedlib

On UNIX, IBM i: /sapmnt//global/sltools/sharedlib SLTOOLS_SECURITY_HOME

Set this variable to the directory, which contains the iaik_jce.jar file. The default directory is: On Windows: :\usr\sap\\SYS\global\security\lib\tools or :\sapmnt\\SYS\global\security\lib\tools

On UNIX, IBM i: /sapmnt//global/security/lib/tools SLTOOLS_DBDRIVER_HOME

Set this variable to the directory, which contains the database driver.EXAMPLE

For MaxDB on Windows: :\sapdb\programs\runtime\jarProcedure

1.

Start the table splitter as user adm in one of the following ways: With the UNIX or IBM i shell script jsplitter.sh

134/166

CUSTOMER

2012-06-25

8 8.3


2.

With the Windows batch file jsplitter.bat Specify options as required in one of the following ways-optionName optionValue. Command line: Specify the option in the format optionName optionValue Property file: Add an option as a new line in the format optionName=optionValueNOTE

In case you use an invalid option or you enter -help, the available options for starting the tool are displayed.NOTE

To check the splitting processing state, use the splitterExampleCommand line for Windows

*.trc and *.console.log files.

jsplitter.bat -tablesplit BC_COMPVERS:2 -tablesplit J2EE_CONFIG:4:CID;PATHHASH tablesplit J2EE_CONFIGENTRY:4:CID Command line for UNIX, IBM i ./jsplitter.sh -tablesplit BC_COMPVERS:2 -tablesplit J2EE_CONFIG:4:CID;PATHHASH tablesplit J2EE_CONFIGENTRY:4:CID

8.3.3 Output Files JPkgCtl.console.log

Default log file of splitter toolJPkgCtl.trc

Trace file with additional and more detailed informationIMPORT_.XML

Resulting xml files for import after package splittingEXPORT_.XML

Resulting xml files for export after package splittingIMPORT_PKG_METADATA.XML

Metadata for tablesEXPORT_PKG_METADATA.XML

Metadata for tablessizes.xml

File with list of the biggest tables with their expected package size in bytes

2012-06-25

CUSTOMER

135/166

8 8.4

Additional Information Additional Information About SAPinst

8.4 Additional Information About SAPinstThe following sections provide additional information about SAPinst: Useful Information About SAPinst [page 136] Interrupted Installation with SAPinst [page 140] Performing a Remote Installation with SAPinst [page 143] Starting SAPinst GUI Separately [page 146]. Running SAPinst in Accessibility Mode [page 151] Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle;SAP HANA DB;SAP HANA DB for i5/OS |

Entries in the Services File Created by SAPinst [page 153]End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/ OS;MaxDB;MS SQL Server;Oracle;SAP HANA DB;SAP HANA DB for i5/OS |

Troubleshooting with SAPinst [page 154] Only valid for: IBM i5/OS | IBM DB2 for i5/OS;SAP HANA DB for i5/OS | Troubleshooting during the Database Load [page 155]End of: IBM i5/OS | IBM DB2 for i5/OS;SAP HANA DB for i5/OS |

8.4.1 Useful Information About SAPinstThis section provides information to consider when performing the export with SAPinst.Integration

When you start SAPinst, SAPinst GUI, and the GUI server are also started. SAPinst GUI connects using a secure SSL connection to the GUI server and the GUI server connects to SAPinst.Only valid for: UNIX |

SAPinst normally creates the directory sapinst_instdir directly below the temporary directory. SAPinst finds the temporary directory by checking the value of the environment variables TEMP, TMP, or TMPDIR. If no value is set for these variables, SAPinst uses /tmp as default directory. The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. These executables are deleted again after SAPinst has stopped running. If required, you can terminate SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C.End of: UNIX | Only valid for: Windows |

SAPinst normally creates the installation directory sapinst_instdir, where it keeps its log files, and which is located directly in the Program Files directory. If SAPinst is not able to create sapinst_instdir directly below the Program Files directory, SAPinst tries to create sapinst_instdir in the directory defined by the environment variable TEMP. SAPinst creates a subdirectory for each installation option, called \, which is located in %ProgramFiles%.

136/166

CUSTOMER

2012-06-25

8 8.4


The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP, TMP, TMPDIR, or SystemRoot). These executables are deleted after SAPinst has stopped running. Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can safely delete them. The temporary directory also contains the SAPinst Self-Extractor log file dev_selfex.out, which might be useful if an error occurs. If you want to terminate SAPinst and the SAPinst Self-Extractor, do one of the following: Right-click the icon for the SAPinst output window located in the Windows tray and choose Exit. Click the icon for the SAPinst output window located in the Windows tray and choose File Exit .End of: Windows |

CAUTION

If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058. I you want to use a different installation directory than the default, make sure that you create it locally. Otherwise, you might experience problems when starting the SAP Java tools.Only valid for: UNIX |

Before starting the export, make sure that you have at least the same amount of disk space available in /sapmnt///SMD/program as is used in /sapmnt// /SMD/root/origin. During the export, some archives are written to the program subdirectories and SAPinst aborts if there is not enough space. Make sure that the DISPLAY environment variable is set to :0.0, where is the host where the SAPinst GUI is displayed.End of: UNIX | Only valid for: Windows |

Before starting the export steps on the primary application server instance of the source system, make sure that you have at least the same amount of disk space available in \\SAPLOC\ \\SMD\program as is used in \\SAPLOC\\\SMD\root \origin. During the export some archives are written to the program subdirectories and SAPinst aborts if there is not enough space.End of: Windows | Only valid for: IBM i5/OS |

Before you start the export of the existing SAP System, you have to download the current version of R3szchk at http://service.sap.com/patches and copy it to directory /usr/sap//SYS/exe/ run/.End of: IBM i5/OS |

2012-06-25

CUSTOMER

137/166

8 8.4

Additional Information Additional Information About SAPinst NOTE

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

p.

If you use virtual host names for the primary application server or the database instance both (for example, in a high availability environment), start the export with the property SAPINST_USE_HOSTNAME=.Only valid for: Windows |

During the installation, the default ports 21200, 21212, and 4239 are used for communication between SAPinst, GUI server, SAPinst GUI, and HTTP server, as follows: SAPinst uses port 21200 to communicate with the GUI server. The GUI server uses port 21212 to communicate with SAPinst GUI. 4239 is the port of the HTTP server, which is part of the GUI server. If these ports are already in use, SAPinst automatically searches for free port numbers. If the search fails, you see an error message and SAPinst exits. In this case or if you want SAPinst to use specific ports, open a command prompt and change to the required directory as follows: cd /d :\DATA_UNITS\IM_WINDOWS_. Execute sapinst.exe with the following commands: SAPINST_DIALOG_PORT= GUISERVER_DIALOG_PORT= GUISERVER_HTTP_PORT= To see a list of all available SAPinst properties, go to the directory %TEMP% \sapinst_exe.xxxxxx.xxxx after you have started SAPinst, and enter the following command:sapinst p.End of: Windows | Only valid for: UNIX |

During the installation, the default ports 21200, 21212, and 4239 are used for communication between SAPinst, GUI server, SAPinst GUI, and HTTP server, as follows: SAPinst uses port 21200 to communicate with the GUI server. The GUI server uses port 21212 to communicate with SAPinst GUI. 4239 is the port of the HTTP server, which is part of the GUI server. If these ports are already in use, SAPinst automatically searches for free port numbers. If the search fails, you see an error message and SAPinst exits. In this case or if you want SAPinst to use specific ports, you can assign them by executing the SAPinst executable with the following parameters: SAPINST_DIALOG_PORT= GUISERVER_DIALOG_PORT= GUISERVER_HTTP_PORT=

138/166

CUSTOMER

2012-06-25

8 8.4


To display a list of all available SAPinst properties, start SAPinst as described above with the option -p: ./sapinst -p.End of: UNIX |

NOTE

For more information about input parameters in SAPinst, position the cursor on the parameter field and choose F1 .Troubleshooting during the Export Process Processing Phase

If the export process aborts during the processing phase (for example, due to a hardware failure, such as power outage, operating system crash, file system full), you have to repeat the export of the complete package. 1. Remove the . dump files, the .TOC file, and the .log file. 2. Make sure that all tables in the .*TSK* file have the status flag xeq or err set. 3. Repeat the export of the complete package.Dialog Phase

If an error occurs during the dialog phase, SAPinst stops and displays a dialog that informs you about the error. You can now: View the log file directly by choosing View Logs. Try to solve the problem. Stop the process by choosing Cancel in the SAPinst menu. For more information, see Interrupted Installation with SAPinst [page 140]. After resolving the problem, you can continue by choosing Retry.Only valid for: UNIX |

System Copy export on UNIX (especially for upgraded systems)

Symptom: Processes started as adm or ora OS users cannot create or open files in the installation directory. Reason: Only members of sapinst UNIX group can access the installation directory. This group is created by SAPinst as of SAP NetWeaver 7.1. Solution: 1. Manually associate adm and ora OS users with sapinst group if this association is missing.

2012-06-25

CUSTOMER

139/166

8 8.4


2. 3. 4. 5.

Verify the /etc/group file and check if the sapinst group exists and OS users are members of this group. If the sapinst group does not exist yet, start SAPinst. SAPinst creates this group during startup before the product catalog list is displayed. Edit /etc/group file and associate OS users with sapinst group. Continue with the export.

End of: UNIX |

More Information

Additional Information About SAPinst [page 136]

8.4.2 Interrupted Installation with SAPinstThe SAP system installation might be interrupted for one of the following reasons: An error occurred during the Define Parameters or Execute phase: SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error. You interrupted the installation by choosing Cancel in the SAPinst menu.CAUTION

If you stop an option in the Execute phase, any system or component installed by this option is incomplete and not ready to be used. Any system or component uninstalled by this option is not completely uninstalled. The following table describes the options in the dialog box:Option Definition

Retry

Stop

Continue View Log

SAPinst retries the installation from the point of failure without repeating any of the previous steps. This is possible because SAPinst records the installation progress in the keydb.xml file. We recommend that you view the entries in the log files, try to solve the problem, and then choose Retry. If the same or a different error occurs, SAPinst displays the same dialog box again. SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and the GUI server. SAPinst records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below. SAPinst continues the installation from the current point. Access installation log files.

140/166

CUSTOMER

2012-06-25

8 8.4


Procedure

This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to continue an interrupted installation after an error situation. 1. Only valid for: Windows | Log on to your remote host as a user who is a member of the local administrators group.End of: Windows |

2.

Only valid for: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

Log on to your local UNIX host as user root.CAUTION

Make sure that the root user has not set any environment variables for a different SAP system or database.End of: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

3.

Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS;SAP HANA DB for i5/OS |

Log on to your local IBM i host as the installation user with similar authorization rights as QSECOFR.End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS;SAP HANA DB for i5/OS |

4.

Only valid for: Windows |

Make the medium for the installation master (folder _IM__) available on the installation host.End of: Windows |

5.

Only valid for: UNIX |

Make the medium for the installation master (folder _IM__) available on the installation host. For more information, see Preparing the Installation Media [page 18].Only valid for: UNIX |

RECOMMENDATION

Make installation media locally available. For example, if you use Network File System (NFS), reading from media mounted with NFS might fail.End of: UNIX | Only valid for: Solaris |

NOTE

If you mount installation media, make sure that you do this with option nomaplcase.End of: Solaris | End of: UNIX |

6.

Only valid for: IBM i5/OS |

Make available the installation master media.NOTE

Make sure that the media is available locally. We do not recommend using Network File System (NFS).End of: IBM i5/OS |

2012-06-25

CUSTOMER

141/166

8 8.4

Additional Information Additional Information About SAPinstOnly valid for: Windows | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

7.

Restart SAPinst by double-clicking sapinst.exe. You can also start SAPinst by entering the following commands at the Windows command prompt:cd /d :\IM_WINDOWS sapinst.exeEnd of: Windows | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

8.

Only valid for: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

Change to the directory _IM__ and start the sapinst executable

End of: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

Enter the following commands:CD DIR('/DATA_UNITS/_IM_OS400_PPC64_DB4') CALL PGM(QP2TERM) PARM('./sapinst')End of: IBM i5/OS | IBM DB2 for i5/OS |

10. From the tree structure in the Welcome screen, select the installation option that you want to continue and choose Next. The What do you want to do? screen appears. 11. In the What do you want to do? screen, decide between the following alternatives and continue with Next:Alternative Behavior

Run a new option

SAPinst does not continue the interrupted installation option. Instead, it moves the content of the old installation directory and all installationspecific files to a backup directory. Afterwards, you can no longer continue the old installation option. For the backup directory, the following naming convention is used: .NOTE

All actions taken by the installation before you stopped it (like creating directories, or users) will not be revoked.EXAMPLElog_01_Oct_2008_13_47_56

CAUTION

Continue with the old option

SAPinst moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly. SAPinst continues the interrupted installation from the point of failure.

142/166

CUSTOMER

2012-06-25

8 8.4


8.4.3 Performing a Remote Installation with SAPinstYou use this procedure to install your SAP system on a remote host. In this case, SAPinst and the GUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is the host from which you control the installation with SAPinst GUI.Only valid for: IBM i5/OS;UNIX |

If your security policy requires that the person performing the installation by running the SAPinst GUI on the local host is not allowed to know root credentials on the remote host, you can specify another operating system user for authentication purposes. You do this using the SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line.End of: IBM i5/OS;UNIX | Only valid for: Windows |

If your security policy requires that the person performing the installation by running the SAPinst GUI on the local host is not allowed to know administrator credentials on the remote host, you can specify another operating system user for authentication purposes. You do this using the SAPINST_REMOTE_ACCESS_USER parameter when starting sapinst.exe from the command line.End of: Windows | Only valid for: IBM i5/OS;UNIX |

Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to SAPinst GUI on Windows workstations. For more information, see SAP Note 1170809.End of: IBM i5/OS;UNIX | Only valid for: UNIX;Windows | Linux;Windows |

You can run the SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host. For more information, see Starting SAPinst GUI Separately [page 146].End of: UNIX;Windows | Linux;Windows | Only valid for: IBM i5/OS |

CAUTION

In this section, local host refers to the Windows installation host, and remote host refers to the IBM i host where the SAP system is installed.End of: IBM i5/OS |

Prerequisites

Both computers are in the same network and can ping each other. To test this:Only valid for: UNIX;Windows |

1. 2.

Log on to your remote host and enter the command ping . Log on to the local host and enter the command ping .

End of: UNIX;Windows |

2012-06-25

CUSTOMER

143/166

8 8.4

Additional Information Additional Information About SAPinstOnly valid for: IBM i5/OS |

1. 2.

Log on to your remote host (IBM i) and enter the command PING RMTSYS(''). Log on to the local host (Windows PC) and enter the command ping .

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

Make sure that the sapinst executable on the remote host and the sapinstgui executable on the local host have exactly the same version. You can check this by using the option version as described in the procedure below and in the procedure in Starting SAPinst GUI Separately [page 146].End of: IBM i5/OS;UNIX | Only valid for: Windows |

Make sure that the sapinst.exe on the remote host and the sapinstgui.exe on the local host have exactly the same version. You can check this by using the option version as described in the procedure below and in the procedure in Starting SAPinst GUI Separately [page 146].End of: Windows |

If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER command line parameter, make sure that this user exists on the remote host.ProcedureOnly valid for: Windows |

1. 2. 3.

Log on to your remote host as a user that is a member of the local administrators group. Make the installation master media available on your remote host. Open a command prompt and enter the following commands:Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

cd \d :\DATA_UNITS\_IM_WINDOWS__End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |

Run sapinst.exeNOTE

-nogui

If you need to specify another operating system user for authentication purposes, enter the following command:sapinst.exe -nogui SAPINST_REMOTE_ACCESS_USER=

4.

Execute the following command: sapinst.exe -nogui SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the command prompt:guiengine: no GUI connected; waiting for a connection on host , port to continue with the installation

5.

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

End of: Windows |

144/166

CUSTOMER

2012-06-25

8 8.4


Only valid for: UNIX |

1.

Log on to your remote host as user root.CAUTION

2.

Make sure that the root user has not set any environment variables for a different SAP system or database. Make the medium for the installation master (folder _IM__) available on the remote host. For more information, see Preparing the Installation Media [page 18].Only valid for: UNIX |

RECOMMENDATION

Make installation media locally available. For example, reading from media mounted with Network File System (NFS) might fail.End of: UNIX | Only valid for: Solaris |

NOTE

If you mount installation media, make sure that you do this with option nomaplcase.End of: Solaris |

3.

Check the version of the sapinst executable by entering the following command:./sapinst version

The version of the sapinst executable must be exactly the same as the version of the sapinstgui executable on the local host (see also Starting SAPinst GUI Separately [page 146]). 4.Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |

Change to the directory _IM__ and start the s

Systemcopy 731 Abja Pi

Documents

Transcript of Systemcopy 731 Abja Pi