System Copy Guide SAP Systems Based on SAP NetWeaver Application
Server ABAP +Java on WindowsUsing Software Provisioning Manager
1.0Valid for SAP Systems Based on: SAP NetWeaver Process
Integration 7.1 SAP NetWeaver Process Integration 7.1 including
Enhancement Package 1 SAP NetWeaver 7.3 SAP NetWeaver 7.3 including
Enhancement Package 1 SAP NetWeaver 7.4 Target Audience Rwikis
System administrators Rwikis Technology consultants
CUSTOMER RwiLMO)JK27i[ [ix"?l1 =MR%X[-(pC
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.0
2013-04-12
Initial version SL Toolset SPS07 Productspecific information has
been moved from the product-specific guides to this guide.
2/156
CUSTOMER
2013-04-12
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.6 4.6.1 4.6.2 Chapter 5
5.1 5.1.1 5.1.2 5.1.2.1 5.1.2.2
Homogeneous and Heterogeneous System Copy for SAP Systems Based
on SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 7 Terminology . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . 8 Online Information from SAP . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . 10 Constraints . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . 11 Planning . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . 13 Preparations . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . General
Technical Preparations . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . Product-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 the Installer . . .
. . . . . . . . . . . . . . . . . . . . Running the Installer to
Perform the Export . . . . . . . . . . . . . . . . . . . . . . . .
. . Restarting R3load Processes . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . Setting Up the Target
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . Transferring the Export Files to the Target Host .
. . . . . . . . . . . . . . . . . . . . . . Installing the Target
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . Database-Specific System Copy . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . Oracle-Specific
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . Generating the Control File Structure . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a
Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . Creating an Offline Backup . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. Creating an Offline or Online Backup with BR*Tools . . . . . . .
. . . . . . . . . . . . 17 17 18 20 25 26 28 29 32 32 33 35 37 38
39 43 44 45 49 49 50
2013-04-12
CUSTOMER
3/156
5.1.3 5.1.4 5.1.5 5.2 5.3 5.4 5.5 5.5.1 5.5.2 5.5.3 5.5.3.1
5.5.3.2 5.5.3.3 5.5.3.4 5.5.3.5 5.5.3.6 5.5.3.7 5.5.3.8 5.5.3.9
5.5.4 5.5.5 5.5.6 5.5.7 5.5.8 5.5.9 5.5.10 5.5.11 5.5.12 5.5.13
5.5.14 5.5.15 5.5.16 5.5.17 5.5.18
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
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 . .
. . . . . . . . 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 . . . . . . . . .
. . . . .
50 52 53 53 56 57 61 63 64 64 64 65 66 66 67 68 69 70 70 71 72
72 72 73 73 74 74 75 75 75 75 76 76 77
4/156
CUSTOMER
2013-04-12
5.5.19 5.5.20 5.6 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.3
7.2.3.2.4 7.2.3.2.4.1 7.2.3.2.4.2 7.2.3.2.5 7.2.3.2.6 7.2.3.2.6.1
7.2.3.2.6.2 7.2.3.2.6.3
Step 11 (DB2 V9): Changing the Schema of the Target System . . .
. . . . . . . . . 77 Step 12: Adapting WLM Application Environments
for DB2 Stored Procedures . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Sybase ASE Server-Specific Procedure . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . 79 Copying Single Instances Only
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copying the Primary Application Server Instance Only . . . . . . .
. . . . . . . . . . . Copying the Database Only Move . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . Copying the
Database Only Refresh . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . 81 81 81 82
Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 85 Performing Follow-Up
Activities in the Source System . . . . . . . . . . . . . . . . . .
85 Performing Follow-Up Activities in the Target System . . . . . .
. . . . . . . . . . . . 85 Installing the License Key . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
85 Performing Follow-Up Activities for ABAP . . . . . . . . . . . .
. . . . . . . . . . . . . . . 86 Activities at Operating System
Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . 86 Activities at Database Level . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . 86 Activities at
SAP System Level . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . 87 Usage Type or Software Unit-Specific
Follow-Up Activities . . . . . . . . . . . . . . . 91 Embedded
Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . 91 Checking the Target System . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . 91 Performing Follow-Up Activities for Java . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . 92 General Follow-Up
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . 92 Configuration Steps for the SAP Java
Connector . . . . . . . . . . . . . . . . . . . . . . . 93
Generating Public-Key Certificates . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . 93 Software Unit-Specific
Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . .
. . . . 94 AS Java: Adobe Document Services . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 94 EP Core Application
Portal (EPC): Portal . . . . . . . . . . . . . . . . . . . . . . .
. . . . . 94 Enterprise Portal (EP): Knowledge Management and
Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . 95 Business
Intelligence Java Components (BI Java) . . . . . . . . . . . . . .
. . . . . . . . . 98 Business Intelligence (BI Java) . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Basic Configuration for BI Java . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . 99 Enterprise Services
Repository: Connecting to the SLD . . . . . . . . . . . . . . . . .
. 99 Process Integration (PI) . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . 99 PI: System
Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . 100 PI: Integration Server . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
100 PI: Changes in the Exchange Profile . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . 102
2013-04-12
CUSTOMER
5/156
7.2.3.2.6.4 7.2.3.2.6.5 7.2.3.2.6.6 7.2.3.2.7 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
PI: Refresh Caches . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . PI: Switching
Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . PI: Connection Checks . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Development Infrastructure (DI) . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . 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 the Installer . . . . . . . . . . . .
. . . . . . . . . . . . . . Useful Information About the Installer
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interrupted Installation . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . Performing a Remote
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . Starting the Installer GUI Separately . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . Running the Installer
in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . .
. . . Entries in the Services File Created by the Installer . . . .
. . . . . . . . . . . . . . . . . Troubleshooting with the
Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . .
104 104 107 107 111 111 112 119 119 120 121 126 127 128 129 130
131 133 134 134 135 137 138 138 139 141 142 143 146 147 148
6/156
CUSTOMER
2013-04-12
1
Homogeneous and Heterogeneous System Copy for SAP Systems Based
on SAP NetWeaver
1 Homogeneous and Heterogeneous System Copy for SAP Systems
Based on SAP NetWeaver
This document explains how to perform heterogeneous and
homogeneous system copy of SAP systems in one run using either
database-independent methods or database-specific methods. It
applies to the copy of SAP systems on Windows to SAP systems with
the following target databases: C8K IBM DB2 for i C8K IBM DB2 for
Linux and UNIX and Windows C8K IBM DB2 for z/OS C8K SAP MaxDB C8K
Oracle C8K MS SQL Server C8K Sybase ASE You perform the system copy
using the installation tool software provisioning manager 1.0
(installer for short).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. The
guide contains information needed for the copy of SAP systems based
on the ABAP+Java application server of the following SAP NetWeaver
releases:NOTE
SAP Sybase ASE is not supported on SAP NetWeaver Process
Integration systems. C8K C8K C8K C8K C8K SAP NetWeaver Process
Integration 7.1 SAP NetWeaver Process Integration 7.1 including
Enhancement Package 1 SAP NetWeaver 7.3 SAP NetWeaver 7.3 including
Enhancement Package 1 SAP NetWeaver 7.4
2013-04-12
CUSTOMER
7/156
1 1.1
Homogeneous and Heterogeneous System Copy for SAP Systems Based
on SAP NetWeaver Terminology NOTE
Not all SAP NetWeaver releases or SAP Business Suite
applications that are available in software provisioning manager
1.0 and are described in this guide might have been released
already. Always check SAP Note 1680045 to ensure that the
installation options you want to perform are already
supported.NOTE
Alternatively, you can copy your system with a completely
automated end-to-end framework available with the SAP NetWeaver
Landscape Virtualization Management 1.0, enterprise edition. For
more information, see http://help.sap.com/nwlvm.
1.1 TerminologyV Software Provisioning Manager Software
provisioning manager is the successor of the product- and
release-specific delivery of provisioning tools, such as SAPinst.
Before you perform an installation or system copy, we recommend
that you always download the latest version of the software
provisioning manager [page 20], which is part of the Software
Logistics Toolset (SL Toolset for short). This way, you
automatically get the latest SAPinst version including latest fixes
in the tool and supported processes. For more information about
software provisioning manager as well as products and releases
supported by it, see SAP Note 1680045. As a result, SAPinst has
been renamed to software provisioning manager (installer for short)
in this documentation. However, the term SAPinst is still used in:
V Texts and screen elements in the software provisioning manager
GUI V Naming of executables, for example sapinst V Naming of
Command line parameters, for example SAPINST_USE_HOSTNAME V
Operating system user groups, for example additional group sapinst
V System Copy Duplication of an SAP system. Certain SAP parameters
might change in a copy. When you perform a system copy, the
installer installs all the instances again, but it uses a copy of
the source system database to set up the database. V 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. V Homogeneous System Copy
8/156
CUSTOMER
2013-04-12
1 1.2
Homogeneous and Heterogeneous System Copy for SAP Systems Based
on SAP NetWeaver Online Information from SAP
During homogeneous system copy, you use the same operating
system and database platform as the original system. You can
perform this system copy using either Database Independent System
Copy [page 25] or DatabaseSpecific System Copy [page 43]. !Q
Heterogeneous System Copy During heterogeneous system copy, you
change either the operating system or the database system, or both.
Heterogeneous system copy is a synonym for migration. !Q Database
Copy Database-dependent part of the system copy. !Q Placeholders
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
NOTE
Database ID identifies the database instance. The installer
prompts you for the when you are installing the database instance.
The can be the same as the .
1.2 Online Information from SAPBefore you start the system copy,
you must read the documentation that is referenced in the
following: !Q Read the following SAP Note for up-to-date
information on system copy and corrections to the system copy
documentation: !> SAP Note 1680045 Release Note for Software
Provisioning Manager 1.0 !> SAP Note 1738258 System Copy of
Systems Based on SAP NetWeaver 7.1 and Higher Make sure that you
have the most recent version of the SAP Note, which you can find
at: http://service.sap.com/notes.
2013-04-12
CUSTOMER
9/156
1 1.3
Homogeneous and Heterogeneous System Copy for SAP Systems Based
on SAP NetWeaver Accessing the SAP Library
zV^ 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/sltoolset.NOTE
If you have problems during the system copy, create a customer
message using the application area BC-INS-MIG.More Information
zV^ SAP System Copy and Migration at
http://scn.sap.com/docs/DOC-8324 zV^ 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. zV^ SAP system
landscape copy: zV^o Best Practice document SAP System Landscape
Copy for SAP NetWeaver and SAP Solutions available
athttp://service.sap.com/solutionmanagerbp
zV^o SAP Note 885343 SAP System Landscape Copy zV^ SAP Note
82478 SAP system OS/DB migration
1.3 Accessing the SAP LibraryThe references to SAP NetWeaver
Library documentation in this guide always refer to the following
on SAP Help Portal: zV^ SAP systems based on SAP NetWeaver Process
Integration 7.1: http://help.sap.com/nwpi71/ Application Help SAP
Library: English SAP NetWeaver Process Integration Library zV^ SAP
systems based on SAP NetWeaver Process Integration 7.1 including
Enhancement Package 1: http://help.sap.com/nwpi711/ Application
Help SAP Library: English SAP NetWeaver Process Integration Library
zV^ SAP systems based on SAP NetWeaver 7.3:
http://help.sap.com/nw73 Application Help SAP Library: English zV^
SAP systems based on SAP NetWeaver 7.3 including Enhancement
Package 1: http://help.sap.com/nw731 Application Help SAP Library:
English zV^ SAP systems based on SAP NetWeaver 7.4:
http://help.sap.com/nw74 Application Help SAP Library: English
10/156
CUSTOMER
2013-04-12
1 1.4
Homogeneous and Heterogeneous System Copy for SAP Systems Based
on SAP NetWeaver Constraints
1.4 Constraints5 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. 5 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. 5 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. 5
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. 5 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. 5 If you want to perform a Unicode
Conversion, see one of the following SAP Notes: 5 SAP Note 551344
Unicode Conversion Documentation 5 SAP Note 1051576 Conversion of
Single Code Page Systems to Unicode 5 SAP Note 928729 Combined
Upgrade & Unicode Conversion (CU) 5 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 AS Java later with the SAP tools to change your
underlying operating system and/or database system. 5 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: 5
You have copied a source system that uses external data archiving.
The target system has readonly access to this archive. 5 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.NOTE
Only valid for SAP NetWeaver BW: If you use ADK-based archiving
of request administration data in SAP NetWeaver BW, you have to
copy all archive files related to archiving object BWREQARCH to the
file system of
2013-04-12
CUSTOMER
11/156
1 1.4
Homogeneous and Heterogeneous System Copy for SAP Systems Based
on SAP NetWeaver Constraints
the target system. Only then write access (like deletion of
requests, deletion of the complete data target content, further
upload of data to other targets, changing the quality status of
requests or InfoProvider rebuild) to requests with archived
administration data is possible in the target system of the copy.
In all other cases, contact SAP SLO at http://service.sap.com/slo
or [email protected]. y 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. y 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: o SAP system
ID and SID (SAPSID = SID = SAP system name) o Host name o IP
addresses o Services and ports o Logical destinations and logical
system names o 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. y If you have implemented a federated portal
network (FPN) across multiple SAP NetWeaver systems, see SAP Note
1080080 before commencing with the system copy.
12/156
CUSTOMER
2013-04-12
2
Planning
2 Planning
This section describes how to plan your system copy. You can use
the system copy for the following: Kd Setting up system landscapes
(where the SAP systems have different SAPSIDs). Kd Providing
systems for testing, demonstration, training, and standby.NOTE
K Oracle only: You cannot create standby systems with a system
copy. K You should perform system copy in a test system first. This
allows you to identify customer-specific 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. Kd 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. Kd
Changing the hardware.CAUTION
Do not use NFS-mounted file systems because writing to
NFS-mounted file systems might cause corrupted dumps.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: Kd 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). Kd 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.
2013-04-12
CUSTOMER
13/156
2
Planning
3.
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. 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
A5 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. A5
Decide which system copy procedure you want to use: A5 The
database-independent procedure [page 25] 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. A5
The database-specific procedure [page 43] using tools provided by
the database vendor Some database vendors offer specific tools for
copying a database. These tools allow you to: A5 Restore a backup
of one database (source database) in another one (target database)
(backup method) A5 Unload the source database and load the data
into the target database A5 Copy single instances only A5 Copy the
primary application server instance only [page 81]. A5 Copy the
database only (using database move) [page 81] A5 Copy the database
only (using database refresh) [page 82]CAUTION
You cannot copy single usage types or components! A5 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 32]. 2. For the import, choose the relevant system
copy options as described in the process flows of the system copy
procedure [page 26]. A5 Choosing an SAP system ID You can choose
the new SAP system ID freely during a new installation.
14/156
CUSTOMER
2013-04-12
2
Planning
CAUTION
To meet the requirements of the Workbench Organizer, you must
choose different SAP system IDs for different SAP systems. Make
sure that your SAP system ID: M Is unique throughout your
organization. Do not use an existing when installing a new SAP
system. M Consists of exactly three alphanumeric characters M
Contains only uppercase letters M Has a letter for the first
character M Has a letter for the first character M Does not include
any of the following, which are reserved IDs:ADD ADM ALL AMD AND
ANY ARE ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID IBM INT
KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW
REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR
M If you want to install an additional application server
instance, make sure that no gateway instance with the same SAP
System ID (SAPSID) exists in your SAP system landscape. M SAP
license 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 10] for your release at: M SAP
NetWeaver Process Integration 7.1 / 7.1 including Enhancement
Package 1: Administrator's Guide Configuration of SAP NetWeaver
General Configuration Tasks License Configuration M SAP NetWeaver
7.3 and higher: 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. M 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 10] for your release at: M
SAP NetWeaver Process Integration 7.1 / 7.1 including Enhancement
Package 1: Administrator's Guide Technical Operations for SAP
NetWeaver General Administration Tasks Data Archiving M SAP
NetWeaver 7.3 and higher: SAP NetWeaver Library: Function-Oriented
View Solution Life Cycle Management Data Archiving
2013-04-12
CUSTOMER
15/156
2
Planning
Access to archive files is platform-independent. P)
Configuration analysis and hardware analysis You need to determine
the: PF Number of application servers PF Expected size of the
database PF Additional disks or other hardware required PF Required
memoryNOTE
See the section on hardware and software requirements in the SAP
system installation documentation to determine the system
requirements.Development Infrastructure (DI) only:
For the migration of Java Development Infrastructure (JDI)
components you can apply either Copy or Move. P) Copy Copy is
supported only by Design Time Repository (DTR). After a copy, both
the source DTR and target DTR can be used productively in parallel.
However, Component Build Service (CBS), Change Management Service
(CMS), and CM Services do not support such a copy. P) Move Move is
supported by all JDI components (DTR, CBS, CMS, and CM Services).
After a move, the source system can no longer be used, that is,
only the target is active after the move has been performed.
16/156
CUSTOMER
2013-04-12
3 3.1
Preparations General Technical Preparations
3 Preparations
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 section describes
important preparations on the source system before you perform
homogeneous or heterogeneous system copy. For more information
about SAP System Administration, see the Administration Information
in the SAP Library [page 10] for your release.Procedure
1.
2.
3.
4. 5.
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. 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 using transaction
SM37. You also need to do this for jobs that must run periodically.
For more information, 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). Write down the logical system names of all
clients: Bw 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).
2013-04-12
CUSTOMER
17/156
3 3.2
Preparations Product-Specific Preparations
6.
7.
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. {%:"j 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. SAP Business Warehouse (BW) only: If you are still in
the process of planning your BW system landscape, see SAP Note
184447 for information about how to set up your system landscape,
especially for information about system naming. {%:"j 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: {%:"j The tables are consistent no
restart log or conversion procedure termination must be displayed.
{%:"j The data of the original table can be read. {%:"j 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. To avoid stopping the database due to a log directory
being full, make sure that the log backup is enabled during the
import
3.2 Product-Specific PreparationsProcedureFI Customers
{%:"j 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) .
18/156
CUSTOMER
2013-04-12
3 3.2
Preparations Product-Specific Preparations
Z.A 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. Z.A RFUMSV00 (tax
on sales/purchases) Z.A RAGITT01 (asset history sheet) Z.A RAZUGA01
(asset acquisitions) Z.A 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: Z.A If the tables are in state For
conversion or in state Done, delete the entries by choosing Control
Delete Entry . Z.A 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.Development Infrastructure (DI)
If your SAP system is of software unit Development
Infrastructure (DI) then this system can only be moved, but not be
copied. This means that it is possible to migrate such a system
from one host to
2013-04-12
CUSTOMER
19/156
3 3.3
Preparations Preparing the Installation Media
another but it is not possible to keep both systems active after
the migration. The target system will be inactive after the copy.
If you want to move an SAP system with software unit Development
Infrastructure (DI), make sure that the following prerequisites are
met: ^U The users and passwords created in the source system are
valid in the target system (for example, they use the same UME). ^U
Check in (or revert) all open activities (of all users) in the SAP
NetWeaver Developer Studio by using the Design Time Repository
perspective (DTR perspective). ^U Remove all existing development
configurations from the SAP NetWeaver Developer Studio. ^U Stop all
applications of the Development Infrastructure (DI) on the source
system.Process 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. For
more information, see the SAP Library [page 10] for your release
at: ^U SAP NetWeaver Process Integration 7.1 / 7.1 including
Enhancement Package 1: Administrators Guide Technical Operations
for SAP NetWeaver General Administration Tasks Data Archiving ^U
SAP NetWeaver 7.3 and higher: Function-Oriented View Process
Integration Administering PI (Process Integration) 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.Business Warehouse
(BW)
^U When planning the copy of an SAP NetWeaver system with BW,
read SAP Notes 886102 and 1553333.
3.3 Preparing the Installation MediaThis section describes how
to prepare the installation media. ^U The software provisioning
manager 1.0 archive containing the installer as such.
20/156
CUSTOMER
2013-04-12
3 3.3
Preparations Preparing the Installation Media
You always have to download the latest version of the software
provisioning manager 1.0 archive. n51I The media containing the
software to be installed, which are available as follows: n51&
You normally obtain the physical installation media as part of the
installation package. n51& You can also download the
installation media apart from the software provisioning manager 1.0
archive from SAP Service Marketplace, as described at the end of
this section. For more information about the required media, see
SAP Note 1680045.Prerequisites
Make sure the latest version of the SAPCAR archiving tool is
available on each installation host. You require the SAPCAR
archiving tool to be able to unpack software component archives
(*.SAR files), which is the format of software life-cycle media and
tools that you can download from the SAP software distribution
center. If required, you can download the latest version of SAPCAR
from: http://service.sap.com/swdc Support Packages and Patches A Z
Index S SAPCAR For more information about SAPCAR, see SAP Note
212876.Procedure
1.
Identify the required media as listed below.NOTE
The media names listed below are abbreviated. The full labels
and the material numbers of all media are listed in the
release-specific media list for your SAP NetWeaver application. You
can find the location of the media list in the Master Guide for
your SAP Business Suite application or SAP NetWeaver application
and release at http://service.sap.com/ instguides.SAP Instance
Required Folder of Software Packages from Media
Central services instance for ABAP (ASCS)
n51I Software provisioning manager 1.0 archiveSWPM10SP_.SAR
The software provisioning manager 1.0 archive containing the
installer as such. You always have to download the latest version
of the software provisioning manager 1.0 archive. n51I UC or NUC
Kernel (folder K___) where U means Unicode and N means
non-Unicode.NOTE
Every new installation of an SAP system is Unicode. You can only
use the non- Unicode kernel if you perform the system copy for a
non-Unicode SAP system that has been upgraded to the current
release. Central services instance for Java (SCS) n51I Software
provisioning manager 1.0 archiveSWPM10SP_.SAR
2013-04-12
CUSTOMER
21/156
3 3.3
Preparations Preparing the Installation Media SAP Instance
Required Folder of Software Packages from Media
Primary application server instance (PAS)
The software provisioning manager 1.0 archive containing the
installer as such. You always have to download the latest version
of the software provisioning manager 1.0 archive. x3u UC or NUC
Kernel (folder K___) where U means Unicode and N means non-Unicode.
x3u Software provisioning manager 1.0 archiveSWPM10SP_.SAR
x3u UC or NUC Kernel (folder K___) where U means Unicode and N
means non-Unicode.NOTE
Database instance
Every new installation of an SAP system is Unicode. You can only
use the non-Unicode kernel if you perform the system copy for a
non-Unicode SAP system that has been upgraded to the current
release. Java Component (folders JAVA_*) x3u x3u Database Software
x3u Software provisioning manager 1.0 archiveSWPM10SP_.SAR
x3u UC or NUC Kernel (folder K___) where U means Unicode and N
means non-Unicode.NOTE
Every new installation of an SAP system is Unicode. You can only
use the non-Unicode kernel if you perform the system copy for a
non-Unicode SAP system that has been upgraded to the current
release. x3u Database Software x3u Database Export x3u Java
Component (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.CAUTION
2.
The source system must be in a consistent state before you can
copy it. Make the required media available.RECOMMENDATION
Mount the media locally. We do not recommend to use Network File
System (NFS), because reading from media mounted with NFS might
fail. 1. Download the latest version of the software provisioning
manager 1.0 archive SWPM10SP_.SAR by choosing download from:
22/156
CUSTOMER
2013-04-12
3 3.3
Preparations Preparing the Installation Media
2.
Software Logistics Toolset 1.0 Software Provisioning Manager 1.0
SP in the Software Provisioning SL Area. Unpack the software
provisioning manager archive to a local directory using the
following command:http://service.sap.com/sltoolset SAPCAR xvf
//.SAR -R
3.
Make the media containing the software to be installed
available. You can do this in one of the following ways: b Copy the
required media folders directly to the installation hosts. b Mount
media on a central media server that can be accessed from the
installation hosts.CAUTION
b If you copy the media to disk, make sure that the paths to the
destination location of the copied media do not contain any blanks.
b If you perform a domain installation and do not want to copy the
media but use network drives for mapping the installation media,
make sure that the adm user has access to the UNC paths of the
network drives. If the user does not yet exist, you have to create
the user manually before you install the SAP
system.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.
2013-04-12
CUSTOMER
23/156
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 to export and import your
ABAP and Java database content, file system, and all configuration
in a database-independent format. The installer 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/swdc
.Constraints R3load and Jload Restrictions
Z\ The installer 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 the installer. Z\ 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. Z\ 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. Z\ R3load:
Indexes longer than 18 characters are not allowed on the database
to be exported.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 chapter
Installation of Multiple Components in One Database in the
installation documentation for your SAP component.Splitting STR
Files
Z\ 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
2013-04-12
CUSTOMER
25/156
4 4.1
Database Independent System Copy System Copy Procedure
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. (l@p 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
the installer to export the database. The options can be used
separately or when using the new Java based splitting tool
combined. (l@p 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 the
installer 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 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.
26/156
CUSTOMER
2013-04-12
4 4.1
Database Independent System Copy System Copy Procedure
~
vX+_nGSOverview on Export Options
Follow the sequence of steps described in the process flows
below for a: ~
v Standard system ~
v 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 17]. 2. Generate DDL
statements [page 28]. 3. Prepare the system for table splitting
[page 29] (optional). 4. If you want to run export processes in
parallel to import processes, run the installer [page 33] to
prepare the source system for the export. In the installer, choose
the system copy option Export Preparation. 5. Run the installer
[page 33] to export the database instance. In the installer, 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 35].
2013-04-12
CUSTOMER
27/156
4 4.2
Database Independent System Copy Generating DDL Statements
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 17]. 2. Generate DDL statements [page 28]. 3. If
you want to run export processes in parallel to import processes,
run the installer [page 33] to prepare the source system for the
export. In the installer, choose the system copy option Export
Preparation. 4. Prepare the system for table splitting [page 29]
(optional). 5. Run the installer [page 33] to export the database
instance. In the installer, 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 35].Result
You have finished this part of the system copy. To complete the
system copy, set up the target system using the installer. For more
information, see Setting Up the Target System Using the Installer
[page 37]
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
the installer.CAUTION
BW, database migration only: You must ensure that no further
changes (such as, activations, data loads to cubes, or field
changes) are executed in the SAP NetWeaver Business Warehouse
system after you have called the SMIGR_CREATE_DDL report and before
you export the data.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.
28/156
CUSTOMER
2013-04-12
4 4.3
Database Independent System Copy Preparing the Table Split
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, the installer 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: [U? 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.
[U? 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
[U? 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 111]. [U? 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: [U? IBM DB2 for z/OS (Only create a temporary index
if you want to perform an unsorted unload.) [U? Oracle For more
information, see section Creating a Temporary Index.
2013-04-12
CUSTOMER
29/156
4 4.3
Database Independent System Copy Preparing the Table Split
Restrictions
BRjM^ Only tables that are described in the SAP dictionary can
be split. BRjM^ The following tables cannot be split: BRjM1 DDNTF
BRjM1 DDNTF_CONV_UC BRjM1 DDNTT BRjM1 DDNTT_CONV_UC BRjM1 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. Oracle PL/SQL splitter only: Use the form %;. For more
information about the Oracle PL/SQL splitter, see SAP Note
1043380.CAUTION
2. 3. 4.
The tables listed in this file have to appear in alphabetical
order! Start the installer. On the Welcome screen, choose System
Copy Source System Based on Table Splitting Preparation . Specify
SAPSID, adm password, the file that contains the split information,
the export directory, and the number of parallel R3ta
jobs.CAUTION
5.
The specified path to the export directory must not contain
blanks! Continue with Next; now the *.WHR files and the whr.txt
file are created in the export directory.CAUTION
When doing a code page 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. Oracle
only: This is not required if you perform a database export using
the Oracle-specific method with the Oracle PL/SQL splitter. 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.
30/156
CUSTOMER
2013-04-12
4 4.3
Database Independent System Copy Preparing the Table Split
Using Hints
With the file R3ta_hints.txt, you can instruct R3ta to use
specific columns of a table to create a WHERE condition. The file
has to be located in the directory in which you start R3ta. With
one line in the file R3ta_hints.txt, you specify the table name
followed by one or more column names, separated by a blank. The
columns have to be part of the primary key of the table. These
specifications are used by R3ta to create the WHERE condition. A
file R3ta_hints.txt with column hints for several tables is
delivered with the installation media (folder IM_). If you want to
modify this file, copy it from the directory IM_/COMMON/INSTALL to
the installation directory and adapt it according your requirements
as soon as the Parameter Summary dialog appears and before starting
the processing phase.Creating a Temporary Index
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.EXAMPLE
1. 2.
Use the DEFER YES parameter to create the index. Afterwards, use
the REBUILD INDEX job to speed up the index creation process.
For each table to be split, R3ta creates the following files to
facilitate the creation of the temporary index:File_IDX.STR
Description
_IDX.TSK _IDX.cmd DRP__IDX.TSK DRP__IDX.cmd
Contains the description of the temporary index; the default
index name is ~IMG. Contains the task to create the temporary
index. R3load command file for creating the temporary index.
Contains the task to drop the temporary index. 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. IBM DB2 for IBM i; IBM DB2 for Linux, UNIX
and Windows; IBM DB2 for z/OS; SAP MaxDB; MS SQL Server, Oracle
only: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.
Oracle only: Edit the file DDLORA.TPL and add the highlighted key
words to the creind statement as follows:SYNTAX creind: CREATE
&unique& INDEX &ind name&
2013-04-12
CUSTOMER
31/156
4 4.4
Database Independent System Copy Preparing Parallel Export and
Import ON &tab name& ( /{ &fld name& /-, /} )
TABLESPACE &tablespace& STORAGE (INITIAL &init&
NEXT &next& MINEXTENTS &minext& MAXEXTENTS
&maxext& PCTINCREASE &pctinc& ) NOLOGGING COMPUTE
STATISTICS PARALLEL ONLINE;
2.
Call R3load as user adm with the following parameters:R3load
dbcodepage i _IDX.cmd l _IDX.log
If your source system is a non-Unicode system, the dbcodepage is
1100. If your source system is a Unicode system, the dbcodepage is
4102 (big-endian) or 4103 (little-endian).
4.4 Preparing Parallel Export and ImportIf you want to perform
export processes in parallel to import processes, you have to
prepare the source system for the export. The preparation includes
the following steps that are required to set up the target
database: ?Q Creating the export directory structure ?Q Calculating
the size of the target database ?Q Creating database size file
DBSIZE.XML If you do not prepare the export, you have to wait for
the export results before you can start with the target system
setup.Procedure
1. 2.
Run the installer to perform the Export Preparation. For more
information, see Exporting the Source System Using the Installer
[page 32]. As soon as the export preparation has finished
successfully, transfer the complete export directory with its
structure and the generated DBSIZE.XML file to the target host. For
more information, see Transferring the Export Files to the Target
Host [page 38].
More Information
?Q R3load Procedures Using the Migration Monitor [page 111] ?Q
Jload Procedures Using the Java Migration Monitor [page 129]
4.5 Exporting the Source System Using the InstallerHere you can
find information about how to run the installer to perform the
export on the source system.
32/156
CUSTOMER
2013-04-12
4 4.5
Database Independent System Copy Exporting the Source System
Using the Installer
4.5.1 Running the Installer to Perform the ExportThis procedure
tells you how to run the installer to export the database of your
SAP system. The installer includes the installer GUI and a GUI
server, which both use Java. This section describes a standard
export where the installer, the installer GUI, and the GUI server
are running on the same host. If required, you can instead perform
a remote system copy with the installer, where the installer GUI is
running on a separate host from the installer and the GUI server.
For more information, see Performing a Remote Installation [page
142]. For more information about the installer, see Useful
Information About the Installer [page 139].PrerequisitesCAUTION
Make sure that you shut down all SAP application servers before
the export. The database must still be running. Otherwise, the
target system might be inconsistent. 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 installer executables.Procedure
1.
Log on to your host as user with the required rights and
privileges that authorize you to install the SAP system with the
installer. For more information, see section Required User
Authorization for the Installation in your installation
guide.CAUTION
2.
10* Make sure that this user has not set any environment
variables for a different SAP system or database. 10* Do not use an
existing adm user. Make the installation media available on your
host. For more information, see Preparing the Installation Media
[page 20].CAUTION
3.
4. 5.
If 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. Start the
installer by double-clicking sapinst.exe from the directory to
which you unpacked the SWPM10SP_.SAR file. The installer GUI starts
automatically by displaying the Welcome screen. On the Welcome
screen, choose System Copy Source System Based on . 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 25].
2013-04-12
CUSTOMER
33/156
4 4.5
Database Independent System Copy Exporting the Source System
Using the Installer CAUTION
Make 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 installation options available for
the export:NOTE
Do not perform these steps if you use a database-specific
method.Export Options Export Option Remarks
Export Preparation
Optional step that is required only if you want to perform
export processes in parallel to import processes. The installer
performs the following steps: +:h Creates the export directory
structure +:h Calculates the size of the target database
(DBSIZE.XML)NOTE
Table Splitting Preparation
Database Instance Export
In the case of a distributed system or a high-availability
system, you need to perform this step on the database instance
host. Optional step. The installer performs the following steps:
+:h Creates the export directory DATA +:h Creates database
structure files (*.STR) for the tables to be split +:h Splits the
generated STR files +:h Creates where-conditions for the tables to
be split +:h Splits the generated WHR files +:h Copies the
resulting WHR files to the export directory DATA Mandatory step.
The installer performs the following steps: +:h Creates the export
directory structure +:h Creates database structure files (*.STR)
+:h Updates database statistics () +:h Calculates the size of the
target database (*.EXT, DBSIZE.XML) +:h Exports the database
content
6. 7.
8.
After you have selected the required option, choose Next. If you
generated SQL files with DDL statements (see Generating DDL
Statements [page 28]) during the database instance export, copy the
generated files into the installer installation directory as soon
as it has been created by the installer. The installation directory
will have been created as soon as the first input screen appears.
Follow the instructions in the installer input dialogs and enter
the required parameters.CAUTION
You must choose parameter mode Typical when performing a system
copy with database tools.NOTE
+:h If parallel export and import has been prepared, ensure the
following: +: You choose parameter mode Custom.
34/156
CUSTOMER
2013-04-12
4 4.5
Database Independent System Copy Exporting the Source System
Using the Installer
/Y5{ You select the expert option Parallel Export and Import for
the database instance export on the SAP System > Database Export
screen. /Y5 If table splitting for ABAP tables has been prepared
before the data export via the installer, the installer export
automatically does the following: /Y5{ It forces package splitting.
/Y5{ It forces the use of an input file for table splitting. /Y5{
It uses the existing whr.txt file from the dump directory as
default for the package splitter input file. /Y5 To split Java
packages and tables you can use the Java splitter tool as part of
the installer. For more information about the Java splitter tool,
see Package and Table Splitting for Java Tables [page 134]. /Y5 You
can perform several database load processes in parallel. For more
information, see Jload Procedures Using the Java Migration Monitor
[page 129].NOTE
For more information about input parameters in the installer,
position the cursor on the parameter field and choose F1 . After
you have entered all required input parameters, the installer
starts the export and displays the progress during the processing
phase.More Information
See Useful Information About the Installer [page 139].
4.5.2 Restarting R3load ProcessesYou can restart failed or
canceled R3load processes while the Migration Monitor is still
running. The state files export_state.properties and
import_state.properties (see Output Files [page 126]) allow package
states to be manually updated to restart failed R3load
processes.EXAMPLE
If package processing failed and the package state has the value
, the state can be set to 0 and processing of the package is
restarted. If you want to restart failed or canceled R3load
processes that are using the socket option, R3load processes that
process the same package must not be running.ProcedureRestarting
R3load Processes Without Using the Socket Option
/Y5 To restart package processing, set the package state from to
0.
2013-04-12
CUSTOMER
35/156
4 4.5
Database Independent System Copy Exporting the Source System
Using the Installer
Lh 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.) Lh If the package is currently
being processed (the package state is ?), then any manual
modifications to the package state are ignored.Restarting R3load
Processes Using the Socket Option
1.
2.
Make sure that no related R3load processes (export or import)
are running. For example, if you want to restart an R3load export
process and the corresponding import process that processes the
same package is still running, cancel it or wait until it has
finished. There are four possible situations where an R3load
restart may be required. Proceed as required: Lh If both the import
and the export are completed successfully, there is nothing to do.
Lh If the export was completed successfully, but the import is
canceled with errors, proceed as follows: Lh 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. Lh 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 and for the export TSK file
from ok to err. Lh If both the export and the import are canceled
with errors, proceed as follows: Lh If the errors in export and
import relate to the same table, there is nothing to do. Lh If the
errors relate to different tables, set the status of the first
object with errors in both the export and the import TSK file to
err and in the export_state.properties and in the
import_state.properties files to .EXAMPLE Export TSK file Import
TSK file
Table name TAB_1 TAB_2 TAB_3 TAB_4
Status ok err xeq xeq
Table name TAB_1 TAB_2 TAB_3 TAB_4
Status ok ok err xeq
3.
The first object with errors here is TAB_2 in the export TSK
file. That means that in the import TSK file the status for TAB_2
must be set from ok to err. The entry in the
export_state.properties and import_state.properties files also must
be set from + to 0. Lh 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 +. Restart the installer or the
Migration Monitor to proceed with the system copy.
36/156
CUSTOMER
2013-04-12
4 4.6
Database Independent System Copy Setting Up the Target
System
More Information
R3load Processes Using the Migration Monitor [page 111].
4.6 Setting Up the Target SystemYou use the installer to install
the target system and import the database files that you have
exported from the source system.Process Flow Standard System
You 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 32]
on the source system because you want to perform export processes
in parallel to import processes, you perform the following steps:
1. If you use the FTP Exchange option during the export (transfer
type FTP on the SAP System > Data Transfer Parameters for Export
screen and communication type Exchange Directory on the SAP System
> Communication Parameters for Export screen), you make sure
that you have transferred the files, which have been generated in
step Preparing Parallel Export and Import [page 32] on the source
system. 2. You transfer the Java export files to the standard
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 standard system target host [page 38]. 2. you install
the target system [page 39]. 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
System
Perform 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: [Y. If you have
already prepared the export [page 32] on the source system because
you want to perform export processes in parallel to import
processes, you perform the following steps:
2013-04-12
CUSTOMER
37/156
4 4.6
Database Independent System Copy Setting Up the Target
System
4. 5.
If you use the FTP Exchange option during the export (transfer
type FTP on the SAP System > Data Transfer Parameters for Export
screen and communication type Exchange Directory on the SAP System
> Communication Parameters for Export screen), make sure that
you have transferred the files, which have been generated in step
Preparing Parallel Export and Import [page 32] 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]. TH If you did not prepare
the export for parallel export and import [page 32] 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]. On
the host of the primary application server instance, you install
the primary application server instance of the target system. 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.
1.
4.6.1 Transferring the Export Files to the Target HostThis
section describes how to transfer the complete export directory
with its structure and the generated DBSIZE.XML file to the target
host.Procedure
1.
On the target host, create a directory with sufficient space for
the database export files available.CAUTION
2.
Do not create this directory under the installation directory or
another directory that contains installation information (such as
the installation media or export files). Otherwise, the installer
does not ask you to specify the export directory and automatically
chooses one that you may not want to use. In this case, the
installer does not display the export directory and you cannot
change it. Transfer 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. You can choose one of the
following methods: TH Use the migration monitor with the file
transfer protocol (FTP) copy option.NOTE
Make sure that you use binary mode for transferring the files.
TH Copy the export dump directory manually to the target host.
38/156
CUSTOMER
2013-04-12
4 4.6
Database Independent System Copy Setting Up the Target
System
3.
The export dump directory can be shared and thus made accessible
on the target host (network share). 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 SystemThis section describes how to
set up the target system using the installer.Prerequisites
There is enough free space on the target system for the database
load. To find out the size of the export and the sizes of the
tablespaces or dbspaces that will be created, look at the file
DBSIZE.XML, which is located in the following directory:
Windows::\\DB\
UNIX, IBM i:/DB/
SAP MaxDB only: If the database platform of your target system
is SAP MaxDB, you must reserve at least twice as much space as
specified in the DBSIZE.XML file. During the import, monitor the
remaining free space in the database using the SAP MaxDB
administration tools Database Manager or Database Studio, and
increase it if required.NOTE
The installer automatically performs a reload. If the database
software has already been unpacked or installed, or if the database
already exists, the installer recognizes this automatically and
skips the related steps.Procedure
1. 2.
Prepare the target system host as described in the installation
guide for your SAP system. Start the installer as described in the
installation guide for your SAP system. You can find the relevant
documentation at: http://service.sap.com/sltoolset Software
Logistics Toolset 1.0 Software Provisioning Manager 1.0CAUTION
If you plan to use Advanced Configuration options during the SAP
System Database Import, make sure you have installed the most
current version of the installer to avoid performance problems
during the dialog phase. You can find the latest version of the
software provisioning manager 1.0 tool at:
http://service.sap.com/sltoolset Software Logistics Toolset 1.0
2013-04-12
CUSTOMER
39/156
4 4.6
Database Independent System Copy Setting Up the Target
System
3.
4. 5.
On the Welcome screen, navigate to the following folder
according to the requirements of your target system: System Copy
Target System Based on . 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
the Installer [page 37]. To install the target system, follow the
instructions in the installer input dialogs and enter the required
parameters.CAUTION
!J Windows, UNIX only: 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 15 times larger than in the non-Unicode source system. !J
Do not create the installation directory (for example:
sapinst_instdir) in the following directories: !J UNIX, IBM i only:
/usr/sap/ !J UNIX, IBM i only: /sapmnt/ !J Windows only: \usr\sap\
!J Windows only: \sapmnt\ !J If you want to perform export
processes in parallel to import processes and you have prepared the
export, you must choose Custom on the Parameter Mode screen. !J On
the SAP System > Database screen, choose Standard System
Copy/Migration (Load-Based). The SAP data dump from the MIGRATION
EXPORT image that you created during the export is loaded in the
newly installed SAP system database. !J When the installer displays
the Media Browser window and asks for the Export Migration, enter
the path to the export directory . !J If you perform a
heterogeneous system copy, enter the Migration Key on the Database
Import screen. !J If you want to perform export processes in
parallel to import processes and you have prepared the export, you
must select Parallel Export and Import on the SAP System Database
Import screen. Complete the installation as described in the
installation documentation for your SAP component.NOTE
6.
If you have to restart the import after an error, just restart
the installer. 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 35]. You can use
the Migration Checker to ensure that the import has been performed
successfully. The Migration Checker automatically checks that the
import has started and that all objects have been imported. For
more information about additional checks with the
40/156
CUSTOMER
2013-04-12
4 4.6
Database Independent System Copy Setting Up the Target
System
Migration Checker, see the Migration Checker User Guide
contained in the MIGMON.SAR archive, which is available in the
following directory: UNIX, IBM i only: /COMMON/INSTALL/MIGMON.SAR
Windows only: \COMMON\INSTALL\MIGMON.SARNOTE
The AS Java is not started automatically. After the target
system has been installed and the followup activities [page 85]
have been performed, you have to start the AS Java manually.
2013-04-12
CUSTOMER
41/156
This page is left blank for documents that are printed on both
sides.
5
Database-Specific System Copy
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
Pi 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 prevents the server
from starting. Pi 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.Process
Follow the sequence of steps described in the process flows
below for a: Pi Standard system Pi Distributed system Pi
High-availability systemStandard System NOTE
When performing a system copy using a database-specific method,
it is no longer required to run the installer in the source system
to export it. You only have to run the installer on the target host
to install the target system. Proceed as follows on the standard
system host.Process Flow on the Source System (Export)
Oracle only: 1. You generate the control file structure for the
target database [page 45]. 2. If required, you create an offline
backup of the source database [page 49].Process Flow on the Target
System
1. 2.
You install the database software as described in the
installation guide of your SAP solution. Follow the instructions on
the installer screens until you are re