systemcopy_pi_711(1).pdf

System Copy GuideSystem Copy for SAP Systems Based on SAP NetWeaver 7.1 Including Enhancement Package 1 ABAP+JavaSAP NetWeaver Process Integration 7.1 including Enhancement Package 1

Target Audience System administrators Technology consultants

PUBLICDocument version: 1.7 2010-12-02

Document History

CAUTIONBefore 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 Description1.7 2010-12-02 Updates in IBM DB2 for Linux, UNIX, and Windows Specific Procedure and follow-up

activities for Process Integration (PI)1.6 2009-09-14 Update in Starting SAPinst on IBM i, Oracle-Specific Procedure, and Performing Follow-Up

Activities for ABAP1.5 2009-07-17 Update in Additional Information About SAPinst1.4 2009-07-06 Update in Performing Jobhead Correction after Homogeneous System Copy1.3 2009-04-08 Update in Database-Specific System Copy1.2 2009-03-13 Updates in SAP MaxDB-Specific Procedure1.1 2009-01-13 Updated EPC-, EP-, and DI-specific information

Updates in Oracle-Specific Procedure1.0 2008-12-18 Initial Version

2/148 PUBLIC 2010-12-02

Table of Contents

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

1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Information on SAP Service Marketplace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

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

Chapter 3 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 General Technical Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2 Usage-Type-Specific Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 4 Database Independent System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.1 System Copy Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.2 Generating DDL Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.3 Preparation for Table Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.4 Preparing the Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.5 Exporting the Source System Using SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . 274.5.1 Running SAPinst on UNIX or Windows to Perform the Export . . . . . . . . . . . . 274.5.2 Running SAPinst on IBM i to Perform the Export . . . . . . . . . . . . . . . . . . . . . . 304.5.2.1 Starting SAPinst on IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.5.2.2 Preparing an IBM i User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.5.2.3 Copying the DVDs Manually Using the ROOTBIN Share . . . . . . . . . . . . . . . . 344.5.3 Restarting R3load Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.6 Setting Up the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.6.1 Transferring the Export Files to the Target Host . . . . . . . . . . . . . . . . . . . . . . . 384.6.2 Installing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 5 Database-Specific System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415.1 Oracle-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435.1.1 Generating the Control File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

2010-12-02 PUBLIC 3/148

5.1.2 Creating a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.1.2.1 Creating an Offline Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.1.2.2 Creating an Offline or Online Backup with BR*Tools . . . . . . . . . . . . . . . . . . . 495.1.3 Preparing the Target System (Oracle) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.1.4 Restoring the Database Files on the Target System . . . . . . . . . . . . . . . . . . . . . 515.1.5 Restoring the Database Files on the Target System with BR*Tools . . . . . . . . . 535.2 SAP MaxDB-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545.3 MS SQL Server-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures . . . . . . . . . . . . . 585.5 IBM DB2 for i5/OS Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625.6 IBM DB2 for z/OS Specific Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635.6.1 Step 1: Check Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.6.2 Step 2: Stop and Restart the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.6.3 Step 3: Run SQL Statements in the Source System . . . . . . . . . . . . . . . . . . . . . . 655.6.3.1 SQL Statement Number 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665.6.3.2 SQL Statement Number 02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665.6.3.3 SQL Statement Number 03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.6.3.4 SQL Statement Number 04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.6.3.5 SQL Statement Number 05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.6.3.6 SQL Statement Number 06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.6.3.7 SQL Statement Number 07 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.6.3.8 SQL Statement Number 08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.6.3.9 SQL Statement Number 09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.6.4 Step 4: Capturing View Definitions with DB2 V9 (if the Schema Name is to be

Changed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.6.5 Step 5: Stop the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.6.6 Step 6: Making Copies of Source Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.6.7 Step 7: Creating the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745.6.8 Step 9a: Changing the Bootstrap Data Sets (BSDS) . . . . . . . . . . . . . . . . . . . . . . 745.6.9 Step 9b: Start the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.6.10 Step 9c: Creating a New STOGROUP Using the HLQ of the Target

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.6.11 Step 9d: Stopping Index Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.6.12 Step 9e: Changing the User-Defined Indexes in the DB2 Catalog . . . . . . . . . . . 765.6.13 Step 9f: Restart the Index Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.6.14 Step 9g: Creating the Temporary Files for the DB2 Target System . . . . . . . . . . 765.6.15 Step 9h: Implementing HLQ of the Target System in the Work File

Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

4/148 PUBLIC 2010-12-02

5.6.16 Step 9i: Adjusting the DDF Location Name and Port Number . . . . . . . . . . . . . 775.6.17 Step 10 (DB2 V8 and Lower): Changing the VCAT of the Target

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775.6.18 Step 10 (DB2 V9): Changing the VCAT of the Target System . . . . . . . . . . . . . . 785.6.19 Step 11 (DB2 V9): Changing the Schema of the Target System . . . . . . . . . . . . 795.6.20 Step 12: Adapting WLM Application Environments for DB2 Stored

Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Chapter 6 Copying Single Instances Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816.1 Copying the Primary Application Server Instance Only . . . . . . . . . . . . . . . . . . 816.2 Copying the Database Only Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826.3 Copying the Database Only Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Chapter 7 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877.1 Performing Follow-Up Activities in the Source System . . . . . . . . . . . . . . . . . . 877.2 Performing Follow-Up Activities in the Target System . . . . . . . . . . . . . . . . . . 877.2.1 Installing the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877.2.2 Performing Follow-Up Activities for ABAP . . . . . . . . . . . . . . . . . . . . . . . . . . . 887.2.3 Performing Follow-Up Activities for Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927.2.3.1 General Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927.2.3.1.1 Configuration Steps for the SAP Java Connector . . . . . . . . . . . . . . . . . . . . . . . 927.2.3.1.2 Generating Public-Key Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937.2.3.2 Software Unit-Specific Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . 937.2.3.2.1 AS Java: Adobe Document Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937.2.3.2.2 Process Integration (PI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947.2.3.2.2.1 PI: System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947.2.3.2.2.2 PI: Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967.2.3.2.2.3 PI: Changes in the Exchange Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977.2.3.2.2.4 PI: Refresh Caches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997.2.3.2.2.5 PI: Switching Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997.2.3.2.2.6 PI: Connection Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017.2.3.2.3 Partner Connectivity Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017.2.4 Performing Jobhead Correction after Homogeneous System Copy . . . . . . . . 102

Chapter 8 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038.1 R3load Procedures Using the Migration Monitor . . . . . . . . . . . . . . . . . . . . . . 1038.1.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048.1.2 Assigning DDL Files to Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

2010-12-02 PUBLIC 5/148

8.1.3 Defining Groups of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1118.1.4 Processing Split Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128.1.5 Starting the Migration Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138.1.6 Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1198.1.7 Installing the Target System Using the Migration Monitor . . . . . . . . . . . . . . 1208.2 Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1218.2.1 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1218.2.2 Useful Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1228.2.3 How to Avoid Automatic Logoff by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . 1268.2.4 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1278.2.5 Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . 1298.2.6 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1338.2.7 Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1378.2.8 Entries in the Services File Created by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . 1398.2.9 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418.3 Troubleshooting During the Database Load . . . . . . . . . . . . . . . . . . . . . . . . . . 142

6/148 PUBLIC 2010-12-02

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

PurposeWith SAP NetWeaver, you can copy SAP systems in one run using either database-independent methods or database-specific methods.

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 SystemThe 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 CopyDuring the system copy, you use the same operating system and database platform as the original system.

Heterogeneous System CopyDuring the system copy, you change either the operating system or the database system, or both. Heterogeneous system copy is a synonym for migration.

Database CopyDatabase-dependent part of the system copy.

PlaceholdersPlaceholders 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 Command hostname


1.1 Terminology

2010-12-02 PUBLIC 7/148

Placeholder Meaning How to find out System name of the target host Command hostname SAP system ID of the source system of the original system SAP system ID of the target system of the target system Database ID of the source system of the original system Database ID of the target system of the target system

1.2 Information on SAP Service MarketplaceFor more information about system copy, see the documentation on SAP Service Marketplace: SAP System Copy & Migration page at http://service.sap.com/systemcopy. SAP OS/DB Migration page 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 mySAP Solutions at http://

service.sap.com/solutionmanagerbp SAP Note 885343 SAP System Landscape Copy

SAP Note 82478 R/3 OS/DB migrationCAUTIONOnly perform a system copy if you have experience in copying systems and good 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.NOTEIf you have problems during the system copy, create a customer message using the application area BC-INS-MIG.

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/nwpi71 SAP NetWeaver Process Integration 7.1 including Enhancement Package 1

Knowledge Center SAP NetWeaver Process Integration Library (including Enhancement Package 1) English


1.2 Information on SAP Service Marketplace

8/148 PUBLIC 2010-12-02

1.4 Constraints As of SAP NetWeaver 7.0, when your system is a double-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 or database system or both.

SAP does not generally support all Data Archiving operations after a system copy.If you used Data Archiving in the source or in the target system, access to the created archive file from the target system may not always be possible. For more information, see SAP Note 153433 and System Landscape Optimization at http://service.sap.com/slo.Access to archived files from the target system without a dedicated archive migration project is only supported in the following cases: Your system copy clones a source system for nonproductive purposes, only read-access to the

previously archived data is intended from the target system (no reloading), and you do not store archive files using ArchiveLink/CMS.You can either copy all archive files to file systems that are not shared between the source and the target system, or you arrange network access for appropriate archive file sharing.

The system copy is done to replace a productive system by a new productive system (for example, hardware migration), assuming that the target system did not exist before and the source system's operation is discontinued after the system copy.You must not change the system ID during system copy, but arrange for file access and/or ArchiveLink/CMS connectivity.


1.4 Constraints

2010-12-02 PUBLIC 9/148

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

When you perform a system copy, all software units in the source system are copied to the target system. This means that none of the software units in the target system can be excluded from the system copy, nor can you select software units.

Dos and Don'ts for system copy: Do:

Save configuration data and runtime data in the Java database only. Follow the Open SQL standard. Make sure that all communication runs through the database pool.

Don't: Save any system and infrastructure-specific data in business objects. Use a pointer to the

central storage of such information, for example: SAP SystemID and SID (SAPSID = SID = system name) Host name IP addresses Services and Ports Logical destinations and logical system names Other technical infrastructure names

Use file system persistency. Set up dependencies between Java and ABAP. Try to copy the Java part of an ABAP+Java system to a Java standalone system or vice versa.


1.4 Constraints

10/148 PUBLIC 2010-12-02

2 Planning

This section describes how to plan your system copy.You can apply the system copy for: Setting up system landscapes (where the SAP systems have different SAPSIDs). Creating systems for testing, demonstration, training, and standby. Depending on the purpose of

the system, it might be advisable to use the same SAP system ID, even though this prevents you from including the system in a system group for transports.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.Only valid for: Oracle |

NOTEYou cannot create standby systems with a system copy.

End of: Oracle |NOTEYou should perform upgrades in a test system first. This way you can identify customer-specific problems that might result from modifications.

Only valid for: UNIX |

CAUTIONDo not use NFS-mounted file systems because writing to NFS-mounted file systems might cause corrupted dumps.

End of: UNIX |

When copying a system that contains production data, choose the moment for the copy carefully. This could be a month-end or year-end closing.

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

SAP Note 1259011 ( System Copy for SAP NetWeaver Based on Kernel 7.1 EHP1)Make sure that you have the most recent version of the SAP Notes, which you can find athttp://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 athttp://service.sap.com/instguides.

2 Planning

2010-12-02 PUBLIC 11/148

Required DVDs, Tools, and Other Software Required DVDs

Make sure that all required DVDs for the system copy are available: Installation Master DVD Java DVD

NOTEThe DVD names are abbreviated.You can find the full names of all media shipped with SAP NetWeaver Process Integration 7.1 in Media List - SAP NetWeaver Process Integration 7.1 including Enhancement Package 1" athttp://service.sap.com/instguidesNWPI71 Installation .

Order the right version of the installation kit before starting the system copy.Make sure that the versions of the SAP system and the installation tools are the same on the target and source systems. Exceptions are only allowed if they are described in an SAP Note.

NOTEYou can operate several SAP systems including their databases on a single host without encountering any problems. However, 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.CAUTIONThe source system must be in a consistent state before you can copy it.

Check that you have the appropriate tool versions for your SAP kernel. Check whether you have to download archives at http://service.sap.com/swdc. For a heterogeneous system copy you need a migration key. You can generate it at http://

service.sap.com/migrationkey.

Creating A System Copy PlanCreate a plan to perform the system copy.1. Consider the downtime of the source system (for preparations and copying) when planning the

system copy.2. Consider a test run

Perform a test run of the system copy. You can use the time taken by the test run to calculate the system downtime: If you want your target system to replace your source system, try to perform a complete test

run. This means that the entire database is exported from the source system, transferred to the target system and imported there. System downtime is approximately equal to the total test time (that is, time for export, transport, and import).

2 Planning

12/148 PUBLIC 2010-12-02

If you do not want to replace your source system, a partial test run (export of the entire database or parts of it) can be sufficient to calculate the system downtime. The source system is only down for the time of the export.Calculating the system downtime is particularly important for very large databases (VLDB) or when tapes are being used. The test run is also to determine the amount of export data. Choose the best data transfer method (for example, FTP or tape). We recommend that you perform read/write actions only on local file systems.

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

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

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

Decide which system copy procedure you want to use: The database-independent procedure [page 19] using SAP tools

Use this method if database-specific methods are either not available or not suitable.NOTEFor a database-heterogeneous system copy and for Unicode conversion, only the database-independent method is available.

The database-specific procedure [page 41] using tools provided by the database vendorSome database vendors offer specific tools for copying a database. These tools let you: Restore a backup of one database (source database) in another one (target database)

(backup method) Unload the source database and load the data into the target database

Copy single instances only Copy the primary application server instance only [page 81]. Copy the database only (using SAPinst) [page 82] Copy the database only (using database refresh) [page 83]

CAUTIONYou cannot copy single usage types or components!

Changing the system variantIf 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 27].2. For the import, choose the relevant system copy options as described in the process flows of

the system copy procedure [page 20]. Choosing an SAP system ID

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

2 Planning

2010-12-02 PUBLIC 13/148

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

SAP licenseOnce 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 8] at

Administrator's Guide Technical Operations for SAP NetWeaver General Administration Tasks License Administration .For more information about SAP license keys, see http://service.sap.com/licensekey or SAP Note 94998.

Archiving filesData 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 8] at Administrator's Guide Technical Operations for SAP NetWeaver

General Administration Tasks Data Archiving .Access to archive files is platform-independent.

Configuration analysis and hardware analysisYou need to determine the: Number of application servers Expected size of the database Additional disks or other hardware required Required memory

NOTESee the section on hardware and software requirements in the SAP system installation documentation to determine the system requirements.

2 Planning

14/148 PUBLIC 2010-12-02

3 Preparations

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

3.1 General Technical PreparationsProcedureTo make a consistent copy of the database, you need to prepare the source system and perform some subsequent actions on the target system. This is not necessary when performing a test run.The following describes important preparations on the source system. For more information about SAP system administration, see the SAP Online Documentation. Before you start a system copy, check the minimum kernel patch level required by the support

package level of the source system. It might be necessary to replace the SAP kernel delivered with the kernel DVD of the installation kit and installed during the installation of the target system by a newer kernel patch level before starting the target system. If you have to replace the delivered SAP kernel, you can do this after the installation of the primary application server instance.

No canceled or pending update requests should be in the system. Check this by choosing ToolsAdministration Monitor Update (transaction SM13).

If canceled or pending updates exist, you must update these again or delete them from all clients. You can see whether canceled or pending updates exist by checking if table VBDATA contains any entries.Find the canceled or open updates as follows:1. Call transaction SM13.2. Delete the default values for the client, user, and time.3. Choose all update requests.

If canceled or pending records exist, you must update these again or delete them. Check whether this action was successful using transaction SE16 for table VBDATA.

Set all released jobs from Released to Scheduled:Tools CCMS Background Processing Jobs - Overview and Administration (transaction SM37)

You also need to do this for jobs that must run periodically (see SAP Note 16083). Select all jobs (include start after event) as follows:

Job Released Scheduled Adapt the operation mode timetable to make sure that no switching of operating modes takes

place while a system is being copied as follows:

3 Preparations3.1 General Technical Preparations

2010-12-02 PUBLIC 15/148

Call transaction SM63 or choose SAP Menu Tools CCMS Configuration Operation Mode Calendar .

Write down the logical system names of all clients:1. If you plan to overwrite an existing system with a system copy (for example, the source and

target systems will both exist after the system copy), make sure you write down the logical system names of all clients in the system that will be overwritten (transaction SCC4).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.

2. If you create a new system with a system copy (that is, create an upgrade test system), make sure that the logical naming strategy for this new system is consistent with your existing logical system naming convention. If you are still planning your BI (formerly BW) system landscape, see SAP Note 184447.

3. If your system copy is used to replace hardware for the DB server, migrate to a different database system or operating system (that is, source system for the copy is the same as the copy target), no changes to logical system names are required.

Before the export, delete QCM tables from your system as follows:1. Before deleting you must always check

That the tables are consistent no restart log or conversion procedure termination must be displayed

That the data of the original table can be read That 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)

3 Preparations3.1 General Technical Preparations

16/148 PUBLIC 2010-12-02

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.

CAUTIONPrerequisites 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 ControlDelete 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.CAUTIONHeterogeneous 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 TATGPCANormally both tables are empty. If you do not delete the contents of these tables you will encounter problems while importing the data to your target system because of non NULL capable fields in these tables.

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.

3 Preparations3.2 Usage-Type-Specific Preparations

2010-12-02 PUBLIC 17/148

For more information, see the SAP Library [page 8] at NetWeaver Administrator's Guide Technical Operations for SAP NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Management

Data Archiving .

CAUTIONIn 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 Preparations3.2 Usage-Type-Specific Preparations

18/148 PUBLIC 2010-12-02

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.

ConstraintsR3load 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.Existing Target SystemIf the target system already exists and if you do not plan to perform an MCOD installation, delete the database on the target system before the import according to the corresponding description in section Additional Information of the installation documentation for your SAP component.If the database configuration of your database is stored in the file system, we recommend you to back up these configuration files before deleting the database.

Splitting STR Files During the standard system copy process, all tables of the SAP system are grouped into packages,

whereby all tables with the same data class belong to the same package. The processing unit for one unload/load process is a package. The packages usually differ in number and size of contained tables, resulting in varying unload/load runtimes. The overall runtime can be reduced by creating

4 Database Independent System Copy

2010-12-02 PUBLIC 19/148

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

CAUTIONIf 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.Follow the sequence of steps described in the process flows below for a: Standard system Distributed system or high-availability systemStandard SystemTo 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 22].3. Run SAPinst on UNIX or Windows [page 27] or on IBM i [page 30] to prepare the source system

for parallel export/import (optional).In SAPinst, choose the system copy option Export Preparation.

4. Prepare the system for table splitting [page 23] (optional).

4 Database Independent System Copy4.1 System Copy Procedure

20/148 PUBLIC 2010-12-02

5. Run SAPinst on UNIX or Windows [page 27] or on IBM i [page 30] to export the database instance.In SAPinst, choose the system copy option Database Instance Export.

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

Only valid for: IBM i5/OS;UNIX |CAUTIONIf your database instance is running on HP PA-Risc, you must proceed as described in SAP Note 884452.

End of: IBM i5/OS;UNIX |

ResultYou have finished this part of the system copy. To complete the system copy, perform the steps in Setting Up the Target System Using SAPinst [page 37].

Distributed System or High-Availability SystemTo 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 22].3. Run SAPinst on UNIX or Windows [page 27] or on IBM i [page 30] to prepare the source system

for parallel export/import (optional).In SAPinst, choose the system copy option Export Preparation.

4. Prepare the system for table splitting [page 23] (optional).5. Run SAPinst on UNIX or Windows [page 27] or on IBM i [page 30] to export the database instance.

In SAPinst, choose the system copy option Database Instance Export.NOTEIf R3load processes fail due to an error, solve the problem, and perform the restart as described in Restarting R3load Processes [page 36].

Only valid for: IBM i5/OS;UNIX |CAUTIONIf your database instance is running on HP PA-Risc, you need to proceed as described in SAP Note 884452.

End of: IBM i5/OS;UNIX |

ResultYou finished this part of the system copy. To complete the system copy, perform the steps as described in Setting Up the Target System Using SAPinst [page 37].

4 Database Independent System Copy4.1 System Copy Procedure

2010-12-02 PUBLIC 21/148

Export Options

Figure 1: Overview on Export Options

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.

Procedure1. Log on to the system as a system administrator in a productive client.2. Call transaction SE38 and run the program SMIGR_CREATE_DDL.3. Select the target database. Depending on the database manufacturer, you might need to select the

database version. The value help supports you in selecting the database version.NOTEOnly enter a database version that is available in the value help.

4. You are able to select Unicode Migration if you also wish to perform a Unicode system copy (from Unicode to Unicode) or a Unicode conversion (from non-Unicode to Unicode).

5. Specify an empty working directory to which the files generated by the report are to be written.6. If required, you can restrict the generation of DDL statements to specific table types or individual

tables.7. Execute the program.

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

4 Database Independent System Copy4.2 Generating DDL Statements

22/148 PUBLIC 2010-12-02

CAUTIONIf no database-specific objects exist in the database, no SQL files will be generated. As long as the report terminates with status Successfully, this is not an error.

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

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

4.3 Preparation for Table SplittingThe tool R3ta processes large tables. Instead of exporting/importing one table with one R3load process, the table is processed in, for example, 10 entities. Each entity can be processed by different R3load processes. The advantages of splitting the tables are: Large tables are processed in smaller packages. If the export or import of a table aborts with an

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

The export and import of one table can be performed in parallel by starting several R3load processes to work on some packages in parallel.

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

feature is used. For the following databases, we recommend that you create an index on the column listed in the

hints file for the table you want to split before starting R3ta: IBM DB2 for z/OS (Only create a temporary index if you want to perform an unsorted unload.) OracleFor more information, see paragraph Creating a Temporary Index.

Restrictions Only tables that are described in the SAP dictionary can be split. The following tables cannot be split:

DDNTF DDNTF_CONV_UC DDNTT DDNTT_CONV_UC DDLOG (is never copied, but created empty in the target system)

Procedure1. Create a file that contains lines of the form % for all tables to be split.

4 Database Independent System Copy4.3 Preparation for Table Splitting

2010-12-02 PUBLIC 23/148

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

2. Start SAPinst.3. On the Welcome screen, choose Software Life-Cycle Options System Copy Source

System Based on Table Splitting Preparation .4. Specify SAPSID, adm password, the file that contains the split information, the export

directory, and the number of parallel R3ta jobs.CAUTIONThe specified path to the export directory must not contain blanks!

5. Continue with Next; now the *.WHR files and the whr.txt file are created in the export directory.CAUTIONWhen doing a codepage conversion (non-Unicode Unicode; 4102 4103), make sure not to use a WHERE condition with the PAGENO column included. If the PAGENO column is included in the WHERE condition, repeat the table splitting - either with different splitting parameters or by defining a suitable column for this table, using the R3ta_hints.txt.

6. If required, create the temporary index on the source system's tables to be split. For more information, see paragraph Creating a Temporary Index.

Parallel data export of a table is supported by all database platforms but not parallel data import. When the target database platform does not support the parallel data import, the Migration Monitor has to be configured in the way that the data import processes the packages are sequentially. For more information, see Processing Split Tables.

Using HintsWith the file R3ta_hints.txt, you can instruct R3ta to use specific columns of a table to create a WHERE condition. The file has to be located in the directory in which you start R3ta.With one line in the file R3ta_hints.txt, you specify the table name followed by one or more column names, separated by a blank. The columns have to be part of the primary key of the table. These specifications are used by R3ta to create the WHERE condition.A file R3ta_hints.txt with column hints for several tables is delivered with the Installation Master DVD. If you want to modify this file, copy it from the directory /COMMON/INSTALL to the installation directory and adapt it according your requirements as soon as the Parameter Summary dialog appears and before starting the processing phase.

Creating a Temporary IndexOnly valid for: IBM DB2 for z/OS |IBM DB2 z/OS only: Create the corresponding temporary index on the database with database tools. Only create a temporary index if you want to perform an unsorted unload. This is the case when you use a DDLDB2.TPL file with no ORDER_BY_PKEY and the R3load does not overrule this setting. Which tables cannot be unloaded unsorted is described in SAP Note 954268.End of: IBM DB2 for z/OS |


24/148 PUBLIC 2010-12-02

Only valid for: IBM DB2 for z/OS |

EXAMPLE1. Use the DEFER YES parameter to create the index.2. Afterwards, use the REBUILD INDEX job to speed up the index creation process.

End of: IBM DB2 for z/OS |Only valid for: Oracle |Oracle only: For further information and for alternatives, see SAP Note 960280.End of: Oracle |

For each table to be split, R3ta creates the following files to facilitate the creation of the temporary index:File Description_IDX.STR Contains the description of the temporary index; the default index name is

~IMG._IDX.TSK Contains the task to create the temporary index._IDX.cmd R3load command file for creating the temporary index.DRP__IDX.TSK Contains the task to drop the temporary index.DRP__IDX.cmd R3load command file for dropping the temporary index.

You can use the R3load cmd, STR, and TSK files created by R3ta to create the index.1. Only valid for: IBM DB2 for i5/OS;IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server |

Make sure that you do not lock the table while creating the temporary index. Depending on your database platform it might be necessary to modify the create index statement in the DDL.TPL file.End of: IBM DB2 for i5/OS;IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server |

2. Only valid for: Oracle |Make sure that you do not lock the table while creating the temporary index. Depending on your database platform it might be necessary to modify the create index statement in the DDL.TPL file.Edit the file DDLORA.TPL and add the highlighted key words to the creind statement:creind: CREATE &unique&INDEX &ind name&ON &tab name&( /{ &fld name& /-, /} )TABLESPACE &tablespace& STORAGE (INITIAL &init&NEXT &next&MINEXTENTS &minext&MAXEXTENTS &maxext&PCTINCREASE &pctinc& )


2010-12-02 PUBLIC 25/148

NOLOGGINGCOMPUTE STATISTICS PARALLELONLINE;End of: Oracle |

3. Call R3load as user adm with the following parameters:R3load dbcodepage i_IDX.cmd l _IDX.logIf your source system is a non-Unicode system, the dbcodepage is 1100. If your source system is a Unicode system, the dbcodepage is 4102 (big-endian) or 4103 (little-endian).

4.4 Preparing the ExportOptionally you can prepare the source system for the export using SAPinst, so as to enable parallel export/import. For this purpose you need to create certain files.The export preparations are required, if: You want to build up the target system to the point where the database load starts, before the

export of the source system has finished. Export and import processes should run in parallel during the system copy process.The following steps are performed: Creating the export directory structure Creating database structure files (*.STR) Updating database statistics () Size calculation for the target database (*.EXT,DBSIZE.XML)Procedure1. You run SAPinst [page 27] and choose Export Preparation.2. As soon as the export preparations have finished successfully, the complete export directory with

its structure and the generated files, which are required for building up the target system, have to be transferred to the target host. You can choose one of the following methods: Use the migration monitor with the FTP Copy Option to transfer the files to the target instance. Copy the export dump directory manually to the target host. The export dump directory can be shared and thus made accessible on the target host.In any case make sure that the dump directory and its subdirectories and files are accessible for user adm of the target system.

NOTEFor more information, see the documentation Migration Monitor Users Guide in the MIGMON.SAR archive on the SAP Installation Master DVD.

4 Database Independent System Copy4.4 Preparing the Export

26/148 PUBLIC 2010-12-02

4.5 Exporting the Source System Using SAPinstHere 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 27] Running SAPinst on IBM i to Perform the Export [page 30]

4.5.1 Running SAPinst on UNIX or Windows to Perform the Export

This procedure tells you how to run SAPinst to export the database of your SAP system. SAPinst includes an SAPinst GUI and a GUI server, which both use Java.This section describes a standard export where SAPinst, SAPinst GUI, and the GUI server are running on the same host. If required, you can instead perform a remote system copy with SAPinst, where SAPinst GUI is running on a separate host from SAPinst and the GUI server. For more information, see Performing a Remote Installation with SAPinst [page 129].

Prerequisites Only valid for: UNIX |

You are logged on to your host as user root.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. For more information, see section Required User Authorization for the Installation in your installation guide.End of: Windows |

CAUTIONMake sure that this user has not set any environment variables for a different SAP system or database.

Make available the Master Installation DVD. You need at least 60 MB of free space in the installation directory for each ABAP installation option,

and at least 130 MB of free space in the installation directory for each Java installation option. In addition, you need 60-200 MB free space for the SAPinst executables.Only valid for: UNIX |If you cannot provide 200 MB free space in the temporary directory, you can set one of the environment variables TEMP,TMP, or TMPDIR to another directory with 200 MB free space for the SAPinst executables.End of: UNIX |

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

4 Database Independent System Copy4.5 Exporting the Source System Using SAPinst

2010-12-02 PUBLIC 27/148

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

CAUTIONMake sure that you shut down all SAP Application Servers before the export. The database must still be running. Otherwise, the target system might be inconsistent.

Procedure1. Only valid for: UNIX |

Start SAPinst from the SAP Installation Master DVD in one of the following ways: Using the default installation directory (recommended)

Enter the following commands:cd /IM_ ./sapinst SAPinst creates a directory called sapinst_instdir, which is the current working directory for your installation, below the temporary directory of your operating system.

Using an alternative installation directoryIf you want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR.

If you use virtual host names for the primary application server or the database instance or both (for example, in a high availability environment), start the export with the property SAPINST_USE_HOSTNAME=.NOTEBe aware of the following: Make sure that your operating system does not delete the contents of the temporary

directory /tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example, by using a crontab entry.

Make sure that your current working directory is not an IM_ directory belonging to another operating system.

EXAMPLEFor example, the following causes an error:$ cd /sapcd2/IM_HPUX_IA64$ /sapcd2/IM_HPUX_PARISC/sapinstTo correct this, enter the following:$ cd /sapcd2/IM_HPUX_PARISC $ /sapcd2/IM_HPUX_PARISC/sapinst

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

2. Only valid for: Windows |Double-click sapinst.exe from the following path::\DATA_UNITS\IM_WINDOWS_


28/148 PUBLIC 2010-12-02

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

3. On the Welcome screen, choose Software Life-Cycle Options System Copy Source System Based on .

4. Select the corresponding system copy option from the tree structure according to the sequence of the process flow for the database-independent system copy procedure [page 19].

CAUTIONMake sure you choose the system copy options exactly in the order they appear for each system variant.

The following table provides an overview about the available installation options available for the export:Export OptionsExport Option RemarksExport Preparation Optional step.

SAPinst performs the following steps: Creates the export directory structure Creates database structure files (*.STR) Updates database statistics () Calculates the size of the target database (*.EXT,

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

Database Instance Export Mandatory step.SAPinst performs the following steps: Creates the export directory structure with label

files Creates database structure files (*STR) Updates database statistics Calculates the size of the target database (*EXT,

DBSIZE.XML) Exports the database content

5. After you have selected the required option, choose Next.Only valid for: UNIX |

CAUTIONIf your database instance is running on HP PA-Risc, you must proceed as described in SAP Note 884452.

End of: UNIX |NOTEIf you generated SQL files with DDL statements (see Generating DDL Statements [page 22]), copy the generated files into the SAPinst installation directory as soon as it has been created by


2010-12-02 PUBLIC 29/148

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

6. Follow the instructions in the SAPinst input dialogs and enter the required parameters.CAUTIONYou must choose Typical when performing a system copy with database tools.NOTENote that if table splitting has been prepared before the data export via SAPinst, the SAPinst export automatically does the following: It forces package splitting. It forces the use of an input file for table splitting. It uses the existing whr.txt file from the dump directory as default for the package splitter

input file.NOTEFor more information about input parameters in SAPinst, position the cursor on the parameter field and choose F1 .

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

TroubleshootingSee Useful Information About SAPinst [page 122].Only valid for: IBM i5/OS |

4.5.2 Running SAPinst on IBM i to Perform the Export4.5.2.1 Starting SAPinst on IBM i

CAUTIONMake sure that you shut down all SAP Application Servers before the export. Otherwise, the target system might be inconsistent.

This procedure tells you how to run SAPinst to export the database of your SAP system. SAPinst includes an SAPinst GUI and a GUI server, which both use Java.This section describes an export where SAPinst and SAPinst GUI server runs on the i5/OS host and the GUI runs on a Windows 32-bit host.

NOTEWhen you start SAPinst, the GUI server is also started. SAPinst GUI connects using a secure SSL connection to the GUI server and the GUI server connects to SAPinst.


30/148 PUBLIC 2010-12-02

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

Preparing an IBM i User Profile [page 33].CAUTIONMake sure that the installation user has not set any environment variables for a different SAP system or database.

2. Make available the Installation Master DVD.For more information about making the DVDs available, see Copying the DVDs Manually Using the ROOTBIN Share [page 34].

3. Start SAPinst from the SAP Installation Master DVD in one of the following ways: Using the default installation directory (recommended)

Enter the following commands:cd '/DATA_UNITS/IM_OS400_PPC64_DB4'CALL PGM(QP2TERM) PARM('./sapinst')

NOTEAs a default, there is no GUI on IBM i, so you will not see an SAPinst Welcome screen. You must start the SAPinst GUI separately on a Windows 32-bit platform. For more information, see Starting SAPinst GUI Separately (Optional) [page 133].NOTEFor advanced users only: PASE, which is similar to AIX allows you to set the DISPLAY variable. If you already have a running and configured XWindows Server on Linux or Windows (for example Humming Bird), you can try to direct the graphical output of SAPinst to a XWindow by setting the DISPLAY variable. If this works, you do not have to use the remote SAPinst GUI separately. We do not recommend that you start the SAPinst using the DISPLAY variable as there is no support available.

Only valid for: HA (UNIX) |NOTEIf you are installing a high-availability system and you have not already set the environment parameter SAPINST_USE_HOSTNAME to specify the virtual host name, you can start SAPinst as follows:CALL PGM(QP2TERM) PARM('./sapinst' 'SAPINST_USE_HOSTNAME=')

End of: HA (UNIX) |CAUTIONMake sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point.


2010-12-02 PUBLIC 31/148

CAUTIONMake sure that your current working directory is not an IM_ directory belonging to another operating system.For example, the following commands are incorrect and cause an error:$ CD DIR ('/sapcd2/IM_HPUX_IA64')$ CALL PGM(QP2TERM) PARM('/sapcd2/IM_HPUX_PARISC/sapinst')The following commands are correct:$ CD DIR('/sapcd2/IM_OS400_PPC64_DB4')$ CALL PGM(QP2TERM) PARM('./sapinst')

Using an alternative installation directoryIf you want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR.

NOTETo receive a list of all available SAPinst properties, enter the following command:CALL PGM(QP2TERM) PARM('./sapinst -p')

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

4. On the Welcome screen, choose Software Life-Cycle Options System Copy Source System Based on .

5. Select the corresponding system copy option from the tree structure according to the sequence of the process flow for the Database-independent system copy procedure [page 19]:

CAUTIONMake sure that you choose the system copy options exactly in the order they appear for each system variant.

6. The following table provides an overview about the available system copy options available for the export of a: Central system Distributed system or high-availability systemExport OptionsExport Option RemarksExport Preparation Optional step.

SAPinst performs the following steps: Creates the export directory structure Creates database structure files (*.STR) Updates database statistics () Calculates the size of the target database (*.EXT,

DBSIZE.XML)


32/148 PUBLIC 2010-12-02

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

Database Instance Export Mandatory step.SAPinst performs the following steps: Creates the export directory structure with label

files Creates database structure files (*STR) Updates database statistics Calculates the size of the target database (*EXT,

DBSIZE.XML) Exports the database content

7. After you have selected the required installation option, choose Next.CAUTIONIf your database instance is running on HP PA-Risc, you must proceed as described in SAP Note 884452.NOTEIf you generated SQL files with DDL statements (see Generating DLL Statements [page 22]), copy the generated files into the SAPinst installation directory as soon as it has been created by SAPinst. The installation directory will have been created as soon as the first input screen appears.

8. Follow the instructions in the SAPinst input dialogs and enter the required parameters.CAUTIONYou must choose Typical when performing a system copy with database tools.NOTEFor more information about input parameters in SAPinst, position the cursor on the parameter field and choose F1 .

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

TroubleshootingSee Useful Information About SAPinst [page 122].Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS;No Database |

4.5.2.2 Preparing an IBM i User ProfileFor the installation you need to create a user account on the IBM i you want to install.The following requirement applies:


2010-12-02 PUBLIC 33/148

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

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

IBM i:Execute the following command:CRTUSRPRF USRPRF(SAPIUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('Test User for SAP Installation') SPCAUT(*USRCLS) LANGID(ENU) CNTRYID(US) CCSID(500)

NOTEIn previous releases, we recommended that you create the user SAPINST to install the SAP system. In the current release, a group SAPINST is created and used for the installation and SAP system. If a user SAPINST already exists on your system, you must delete this user.

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

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

4.5.2.3 Copying the DVDs Manually Using the ROOTBIN ShareProcedure

NOTEWe use the user name SAPIUSR and the password SAP as examples.

NOTEThis is a secure way to copy DVDs manually into the IFS of your IBM i.

NOTEWhen you make the DVDs available locally, make sure that the content is copied correctly. For example, the content might become corrupted by copying using a converting share or long file names can be shortened.

1. If you do not already have a binary share ROOTBIN on your IBM i, you have to create this share manually using the System i Navigator (OpsNav).

CAUTIONThis is typically done by an IBM i administrator!


34/148 PUBLIC 2010-12-02

1. Start the System i Navigator on your Windows PC.2. Connect to your IBM i using My Connections.3. To create or change the share ROOTBIN choose File Systems File Shares .4. Right-click File Shares Open i5/OS Netserver .5. A new screen i5/OS Netserver appears. Click the folder Shared Objects to see the shares.6. To check the already existing share ROOTBIN or create a new share ROOTBIN, right-click New

File .7. The share ROOTBIN should have the access permission Read/Write and the path name should

be /.8. On the Text Conversion tab, do not select Allow file text conversion.9. To save the share ROOTBIN press OK.

Now you have created a share ROOTBIN on your IBM i.2. To open the MS DOS screen on Windows, choose Start Run .3. Enter cmd.exe.4. Press OK.

The MS DOS screen appears.5. In the command line of the MS DOS screen, enter net use.

All network connections to shared resources are displayed.6. Check if you have a connection to your IBM i.

If you find \\\ROOTBIN in the Remote column and a drive directory letter in the Local column, you have already established the required connection to your IBM i.Otherwise, you have to establish this connection. To do this, enter:net use X: \\\ROOTBIN SAP /USER:SAPIUSRX: is now your new network drive to share \\\ROOTBIN to your IFS on the IBM i. If X: is already in use, choose another drive letter that is free.For more information, see Preparing an IBM i User Profile [page 33].

7. To change to the new network drive, enter X: in the command line of your MS DOS screen.8. Create the subdirectories in your IFS where you want to copy the required DVDs.

For each DVD, enter:mkdir \tmp\\

NOTEYou should avoid spaces in the DVD path name.

9. Copy the installation DVDs from your Windows drive (for example D:\) to the IFS of your IBM i host. Insert the required installation DVDs and enter the following command:For each DVD, enter:xcopy D:\ X:\tmp\\ /E


2010-12-02 PUBLIC 35/148

NOTEYou have to copy the root directory of the DVD and all required DVD subdirectories to the IFS of your IBM i.

10. For each required DVD, create a subdirectory and copy the required DVDs.End of: IBM i5/OS | IBM DB2 for i5/OS;No Database |End of: IBM i5/OS |

4.5.3 Restarting R3load ProcessesThe state file allows package states to be manually updated to restart failed R3load processes.

EXAMPLEIf package processing failed and the package state has the value '', the state can be set to '0' and processing of the package is restarted.

Procedure To restart package processing, set the package state from '' to '0'. To skip package processing, set the package state from '0' or '' to '+'. (This is not recommended,

because it can cause inconsistent data files or database content.) If the package is currently being processed (the package state is '?'), then any manual modifications

of the package state are ignored.

Restarting R3load Processes Using the Socket OptionThere are four possible situations where an R3load restart may be required.First of all, you need to cancel the R3load process. If one of the corresponding R3load processes (export or import) is still running, cancel it as well. Then restart SAPinst to continue with the system copy. To continue with the system copy proceed as follows: If both the import and the export are completed successfully, there is nothing to do. If the export was completed successfully, but the import is canceled with errors, proceed as

follows: If the export was successful but the import was canceled when creating the index or the primary

key, set the status for export_state.properties from '+' to '0'. If the export was completed successfully but the import was canceled when loading the

table content, set the status for export_state.properties from '+' to '0' for the TSK file of the export from 'ok' to 'err'

If both the export and the import are canceled with errors, proceed as follows: If the errors in export and import relate to the same table, there is nothing to do. If the errors relate to different tables, set the status of the first object with errors (export as

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


36/148 PUBLIC 2010-12-02

EXAMPLEExport ImportTable name Status Table name StatusTAB_1 ok TAB_1 okTAB_2 err TAB_2 okTAB_3 xeq TAB_3 errTAB_4 xeq TAB_4 xeq

The first object with errors here is TAB_2 (export). That means that in the import TSK file the status for TAB_2 must be set from 'ok' to 'err'. The entry in the *state* file must be set from '+' to '0'.

When the import was completed successfully, but the export was canceled with errors, you can set the status in the export_state.properties from '-' to '+'.

More InformationSee also R3load Processes Using the Migration Monitor [page 103].

4.6 Setting Up the Target SystemPurposeYou use SAPinst to install the target system and import the database files that you have exported from the source system.

Process FlowStandard SystemYou perform the following steps on the standard system host:1. You prepare the standard system host for the installation of your target system as described in the

installation guide for your SAP application.2. If you have already prepared the export [page 26] on the source system, you perform the following steps:

1. If you use the FTP Exchange option during the export (transfer type FTP, communication type Exchange Directory on the Communication Parameters for Export screen), you make sure that you have transferred the files, which have been generated in step Preparing the Export [page 26] on the source system.

2. You transfer the Java export files to the central system target host [page 38].3. You install the target system [page 39].If you did not prepare the export on the source system, you perform the following steps:1. You transfer the Java export files to the central system target host [page 38].2. you install the target system [page 39].

4 Database Independent System Copy4.6 Setting Up the Target System

2010-12-02 PUBLIC 37/148

3. If required, on the host or hosts of the application server instance, you install further additional application server instances as described in the installation guide for your SAP application.

Distributed System or High-Availability SystemPerform the following steps on the relevant installation hosts of your target system:1. You prepare the central services instance host, the database instance host and the host of

the primary application server instance for the installation of the corresponding instances of your target system as described in the installation guide for your SAP application.

2. You install the central services instance for the target system as described in the installation guide for your SAP application.

3. You perform the following steps on the database instance host: If you have already prepared the export [page 26] on the source system, you perform the following

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

type Exchange Directory on the Communication Parameters for Export screen), make sure that you have transferred the files, which have been generated in step Preparing the Export [page 26] on the source system.

2. You transfer the Java export files to the database instance target host [page 38].3. You install the database instance of the target system [page 39].

If you did not prepare the export [page 26] on the source system, you perform the following steps:1. You transfer the Java export files to the database instance target host [page 38].2. you install the database instance of the target system [page 39].

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

5. If required, on the host or hosts of the additional application server instance, you install further additional application server instances as described in the installation guide for your SAP application.

4.6.1 Transferring the Export Files to the Target HostProcedure1. On the target host, create a directory with sufficient space for the database export files

available.2. Copy all files and directories (recursively) that are located on the source host in the migration

export directory from the source host to the target host.


38/148 PUBLIC 2010-12-02

NOTEIf you transfer the files with file transfer protocol (ftp), make sure that you use binary mode for transferring the files.

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

4.6.2 Installing the Target SystemPrerequisitesThere is enough free space on the target system for the database load.To find out the size of the export and the sizes of the tablespaces or dbspaces that will be created, look at the file DBSIZE.XML, which is located in the following directory:Only valid for: Windows |:\\DB\End of: Windows |Only valid for: UNIX |/DB/End of: UNIX |

NOTESAPinst automatically performs a reload. If the database software has already been unpacked or installed, or if the database already exists, SAPinst recognizes this automatically and skips the related steps.

Procedure1. Prepare the target system host as described in the installation guide for your SAP system.2. Start SAPinst as described in the installation guide for your SAP system.

CAUTIONIf you plan to use Advanced Configuration options during the SAP System Database Import, make sure you have installed the most current version of SAPinst to avoid performance problems during the dialog phase. You can find the latest version of SAPinst at http://service.sap.com.

3. On the Welcome screen 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 Target System Based on .4. Run the options required for your system copy in the sequence they are listed in the specific folder

and according to the process flow in Setting Up the Target System Using SAPinst [page 37].5. To install the target system, follow the instructions in the SAPinst input dialogs and enter the

required parameters on the SAP System Database - Select the Database Copy Method screen.On this screen, choose Standard System Copy/Migration (Load-Based).


2010-12-02 PUBLIC 39/148

The SAP data dump from the MIGRATION EXPORT CD image that you created during the export is loaded in the newly installed SAP system database.

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

directories: UNIX: /usr/sap/ UNIX: /sapmnt/ Windows: \usr\sap\ Windows: \sapmnt\

If you perform a Unicode conversion, the data import into the target system might abort because of missing space in the database tablespace or dbspace. Enlarge the database or database container, in which the table DYNPSOURCE will be created in the target database. The required size for the table will be fifteen times larger than in the non-Unicode source system.

6. When SAPinst displays the Media Browser window and asks for the Export Migration CD, enter the path to the export directory .

7. If you perform a heterogeneous system copy, enter the Migration Key on the Database Import screen.If you want to perform export and import in parallel, run the option Export Preparation [page 26]. On the SAP System Database Import screen, choose Parallel Export /Import.

8. Complete the installation as described in the installation documentation for your SAP component.NOTEIf you have to restart the import after an error, just restart SAPinst. The import continues with the table that has not yet been successfully imported.If you have to restart failed R3load processes, see Restarting R3load Processes [page 36].

NOTEThe Java EE engine is not started automatically. After the target system has been installed and the follow-up activities [page 87] have been performed, you have to start the Java EE engine manually.


40/148 PUBLIC 2010-12-02

5 Database-Specific System Copy

The following sections describe the database-specific methods for the system copy. For more information about SAP Notes describing the homogeneous system copy for your database system, see http://service.sap.com/notes.

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

key phrase as the source system. Make sure that the key phrase is correct otherwise encrypted content cannot be decrypted and that will prevent the server from starting.

You must not uninstall all application servers of an SAP system if you want to continue using the database instance of this SAP system. Otherwise, you delete configuration-specific data in the database instance that is required for performing the homogeneous system copy.

ProcessFollow the sequence of steps described in the process flows below for a: Central system Distributed system High-availability systemCentral SystemFor performing the export for a central system, you need to proceed as follows on the central system host:

Process Flow on the Source System (Export)1. You generate the control file structure for the target database [page 44].2. If required, you create an offline backup of the source database [page 48].

Process Flow on the Target System1. Only valid for: Windows |

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

2. Only valid for: UNIX |You prepare the target system [page 49]:1. Follow the instructions on the SAPinst screens until SAPinst requests you to install the database

software and to perform the database backup/restore.


2010-12-02 PUBLIC 41/148

CAUTIONMake sure that you create the secure store of the target system using the same key phrase as for the source system. Otherwise, the UME service cannot be started.

2. You create the database file system (if not yet existing).3. You install the database software.End of: UNIX |

3. Only valid for: Windows |Follow the instructions on the SAPinst screens until you are requested to perform the database backup/restore.

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

End of: Windows |4. To complete the system copy, you have to perform the follow-up activities [page 87].

Distributed System or High Availability SystemTo perform the export for a distributed or high-availability system, proceed as follows:

Process Flow on the Source System (Export)1. On the database instance host of the source system, you generate the control file structure for the target

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

Process Flow on the Target System1. Only valid for: Windows |

On the database instance host, you install the database software as described in the installation guide of your SAP solution.

CAUTIONMake sure that you create the secure store of the target system using the same key phrase as for the source system. Otherwise, the UME service cannot be started.

End of: Windows |2. Only valid for: UNIX |

You prepare the target system [page 49]:1. On the database instance host, follow the instructions on the SAPinst screens until SAPinst

requests you to install the database software and to perform the database backup/restore.2. On the database instance host, you create the database file system (if not yet existing).3. On the database instance host, you install the database software.End of: UNIX |

3. Only valid for: Windows |On the database instance host, follow the instructions on the SAPinst screens until you are requested to perform the database backup/restore.


42/148 PUBLIC 2010-12-02

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

End of: Windows |4. To complete the system copy, you have to perform the follow-up activities [page 87].Only valid for: Oracle |

5.1 Oracle-Specific ProcedurePurposeIn an SAP system environment, you can create a homogeneous copy of an Oracle database by copying database files. This method is suitable for creating an exact copy of an existing database. The source of the copy can be an offline backup or the file system of your source host.You use SAPinst for the installation on the target system host as described in the installation documentation for your SAP component. Only the SAPinst steps for setting up and loading the database steps are different.

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

switches) This method is faster than the R3load and Jload method.Disadvantages Offline backup/copy of database files in a heterogeneous environment is not possible because the

hardware of the source and target systems must be binary-compatible. Source system host and target system host must be different. You must shut down the SAP system and the database during offline backup/copy of database files. You cannot change the database schema and the tablespace names.Prerequisites You must use the same Oracle release and patch level for your database in the source and target

system. The classes12.jar must exist in the /jdbc/lib directory (installed using a

standard Oracle installation). If your source system is an ABAP only system, make sure that a JRE version 1.5 or higher is installed

on the database instance. The JAVA_HOME environment variable must point the JRE directory. The backup must be done offline.

5 Database-Specific System Copy5.1 Oracle-Specific Procedure

2010-12-02 PUBLIC 43/148

NOTEThe system copy procedure does not support the usage of an online backup to copy your Java engine.

The source and target systems must run on different hosts for security reasons. The source and target systems must be binary compatible.

NOTENote that you can also perform a system copy from 32-bit systems to 64-bit systems and vice versa (same operating system assumed) even if source and target system are not binary compatible.

If your source system

Date post:	30-Sep-2015
Category:	Documents
Upload:	rajbasis
View:	220 times
Download:	2 times

systemcopy_pi_711(1).pdf

Documents