702 Guide
-
Upload
thiagobertonha -
Category
Documents
-
view
33 -
download
0
Transcript of 702 Guide
![Page 1: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/1.jpg)
System Copy GuideSystem Copy for SAP Systems Based on SAP NetWeaver 7.0 including Enhancement Package 2 ABAP
Target Audience ■ System administrators ■ Technology consultants
PUBLICDocument version: 1.9 – 2012-04-12
![Page 2: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/2.jpg)
Document History
The following table provides an overview of the most important document changes.
Version Date Description
1.9 2012-04-12 Minor changes
1.8 2012-03-14 Minor changes
1.7 2012-02-16 Updates for IBMi and in Exporting the Source System Using SAPinst and Generating DDL Statements
1.6 2012-01-16 Minor updates
1.5 2012-11-16 Update for Sybase ASE
1.4 2011-10-11 Updated version
1.3 2011-08-24 Update in IBM DB2 for i Procedure
1.2 2010-12-29 Update in IBM DB2 for i Procedure
1.1 2010-12-20 Update in Preparation for Table Splitting
1.0 2010-11-22 Initial version
2/120 PUBLIC 2012-04-12
![Page 3: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/3.jpg)
Table of Contents
Chapter 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based
on SAP NetWeaver 7.0 Including Enhancement Package 2 . . . . . . . . . . . . . 7
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 3 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1 General Technical Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2 Installing the Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 4 Database Independent System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.1 System Copy Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.2 Generating DDL Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.3 Preparation for Table Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.4 Preparing Parallel Export and Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.5 Exporting the Source System Using SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.5.1 Running SAPinst on UNIX or Windows to Perform the Export . . . . . . . . . . . . 32
4.5.2 Running SAPinst on IBM i to Perform the Export . . . . . . . . . . . . . . . . . . . . . . 39
4.5.2.1 Preparing a Windows User Account and IBM i Installation User
Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.5.2.2 Starting SAPinst on IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.5.3 Restarting R3load Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.6 Setting Up the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.6.1 Transferring the Export Files to the Target Host . . . . . . . . . . . . . . . . . . . . . . . 47
4.6.2 Installing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Chapter 5 Database-Specific System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.1 Oracle-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.1.1 Generating the Control File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2012-04-12 PUBLIC 3/120
![Page 4: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/4.jpg)
5.1.2 Creating a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.1.2.1 Creating an Offline Backup Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.1.2.2 Creating an Offline or Online Backup with BR*Tools . . . . . . . . . . . . . . . . . . . 59
5.1.3 Preparing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.1.4 Restoring Database Files on the Target System . . . . . . . . . . . . . . . . . . . . . . . . 62
5.1.5 Restoring the Database Files on the Target System with BR*Tools . . . . . . . . . 63
5.2 SAP MaxDB-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.3 MS SQL Server-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
5.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures . . . . . . . . . . . . . 68
5.5 IBM DB2 for i Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.6 IBM DB2 for z/OS Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.7 Sybase ASE Server-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Chapter 6 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.1 Performing Follow-Up Activities in the Source System . . . . . . . . . . . . . . . . . . 75
6.2 Performing Follow-Up Activities in the Target System . . . . . . . . . . . . . . . . . . 75
6.2.1 Installing the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.2.2 Maintaining the Connection to the System Landscape Directory . . . . . . . . . . 76
6.2.3 Performing Follow-Up Activities for ABAP . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.2.3.1 Activities at Operating System Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.2.3.2 Activities at Database Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.2.3.3 Activities at SAP System Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6.2.3.4 Usage Type or Software Unit-Specific Follow-Up Activities . . . . . . . . . . . . . . . 81
6.2.3.4.1 Embedded Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.2.3.5 Checking the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.2.4 Performing Jobhead Correction after Homogeneous System Copy . . . . . . . . . 82
Chapter 7 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1 R3load Procedures Using the Migration Monitor . . . . . . . . . . . . . . . . . . . . . . . 85
7.1.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
7.1.2 Assigning DDL Files to Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
7.1.3 Defining Groups of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7.1.4 Processing Split Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7.1.5 Starting the Migration Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
7.1.6 Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7.1.7 Installing the Target System Using the Migration Monitor . . . . . . . . . . . . . . 101
7.2 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
7.3 Performing a Remote Export Using SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4/120 PUBLIC 2012-04-12
![Page 5: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/5.jpg)
7.3.1 Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . 106
7.3.2 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
7.4 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Chapter A Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
2012-04-12 PUBLIC 5/120
![Page 6: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/6.jpg)
This page is left blank for documents that are printed on both sides.
![Page 7: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/7.jpg)
1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 Including Enhancement Package 2
As of SAP NetWeaver 7.0, you can copy ABAP systems, ABAP+Java systems and Java systems in one run,
using either database-specific methods or database-independent methods. This document explains how
to perform a system copy for SAP systems based on SAP NetWeaver 7.0 including Enhancement Package
2 (SAP NetWeaver 7.0 EHP 2).
CAUTION
Only perform a system copy if you have experience in copying systems and thorough knowledge
of the operating system, the database, and the ABAP Dictionary. Only perform a heterogeneous
system copy if you are a certified system support consultant or a certified SAP Technical
Consultant.
1.1 Terminology
■ Homogeneous System Copy
During the system copy you use the same operating system and database platform as the original
system.
■ Heterogeneous System Copy
During the system copy, you change either the operating system or the database system, or both.
Heterogeneous system copy is a synonym for migration.
■ Source System and Target System
The SAP system containing the original database is called the source system and the system to
which the database copy is to be imported is called the target system. Their SAP system names
are abbreviated to SOURCE_SAPSID and TARGET_SAPSID (IBM i: source_<SID> and target_<SID>).
The terms source database and target database are also used in this description.
■ System Copy
Duplication of an SAP system. The SAP system ID and certain other SAP parameters might be
changed 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.
■ Database Copy
1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 Including Enhancement Package 2
1.1 Terminology
2012-04-12 PUBLIC 7/120
![Page 8: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/8.jpg)
Database-dependent part of the system copy.
■ Placeholders
Placeholders such as <SAPSID> 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
<SAPSID> SAP system ID
<S_HOST> System name of the source host Command hostname
<T_HOST> System name of the target host Command hostname
<S_SAPSID> SAP system ID of the source system <SAPSID> of the original system
<T_SAPSID> SAP system ID of the target system <SAPSID> of the target system
<S_DBSID> Database ID of the source system <DBSID> of the original system
<T_DBSID> Database ID of the target system <DBSID> of the target system
<OS> Operating system name within a path
<DB> Database name within a path
<Technology> ABAP, Java, or ABAP+Java
1.2 Online Information from SAP
More information about system copying is available online as follows:
■ SAP System Copy & Migration page at http://sdn.sap.com/irj/sdn/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 Note 82478 SAP System OS/DB Migration
NOTE
If you encounter problems during the system copy, create a customer message using the
application area BC-INS-MIG.
1.3 Restrictions
The target system installation consists of both the target database and target instance/application server
installations. For the scenarios below, the following holds:
■ Only valid for: IBM DB2 for Linux and UNIX and Windows |
The option Deferred Table Creation is not supported for load-based system copies for SAP systems
that are not based on SAP NetWeaver 7.0 EHP 1 or higher.End of: IBM DB2 for Linux and UNIX and Windows |
1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 Including Enhancement Package 2
1.2 Online Information from SAP
8/120 PUBLIC 2012-04-12
![Page 9: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/9.jpg)
1.4 Constraints
■ Only valid for: SAP Solution Manager |
As of Support Release 4, your SAP Solution Manager 4.0 system must be a dual-stack system if you
want to perform a system copy. If required, install a Java Add-In to your existing ABAP system
before you start the export.End of: SAP Solution Manager |
■ 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.
■ SAP does not support all data archiving operations after a system copy.
If you used data archiving in the source system, you might not always have access from the target
system to the archive files that were created. For more information, see SAP Note 153433 and System
Landscape Optimization at http://service.sap.com/slo.
Access from the target system to archived files in the source system without a dedicated archive
migration project is only supported as follows:
● You have copied a source system that uses external data archiving. The target system has read–
only access to this archive.
● You have copied a source system that uses data archiving locally. You can either arrange
network access for appropriate archive file sharing or copy all archive files to the file system
of the target system.
In all other cases, contact SAP SLO at http://service.sap.com/slo or
■ When you perform a system copy, all software units or usage types in the source system are copied
to the target system. This means that none of the usage types in the target system can be excluded
from the system copy, nor can you select usage types.
■ Dos and Don'ts for system copy:
● Do:
◆ Follow the Open SQL standard.
1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 Including Enhancement Package 2
1.4 Constraints
2012-04-12 PUBLIC 9/120
![Page 10: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/10.jpg)
◆ 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.
1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 Including Enhancement Package 2
1.4 Constraints
10/120 PUBLIC 2012-04-12
![Page 11: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/11.jpg)
2 Planning
This section describes how to plan your system copy.
You can use 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.
Only valid for: Oracle |
NOTE
You cannot create standby systems with a system copy.
End of: Oracle |
NOTE
You should perform upgrades in a test system first. This allows you to identify customer-
specific problems that might result from modifications.
NOTE
You can set up the SAP system infrastructure (development, quality assurance, and production
system) without making a system copy as follows:
■ Install all SAP systems, starting with the development system. Customize the development
system as described in the implementation documentation.
■ Transport the client-dependent and client-independent data to the quality assurance and
production systems.
However, if you do not follow this concept, you can also install a system, customize it, and then
perform a 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.
CAUTION
Do not use NFS-mounted file systems because writing to NFS-mounted file systems might cause
corrupted dumps.
Required Documentation
■ Read the following SAP Note for up-to-date information:
2 Planning
2012-04-12 PUBLIC 11/120
![Page 12: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/12.jpg)
SAP Note 1339717 (Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0
including Enhancement Package 2)
■ The documentation System Copy for SAP Systems Based on SAP NetWeaver 7.0 Including Enhancement Package
2 only describes the export of the source system in detail. For the installation of the target system,
you also need the installation guide for your SAP application. Installation guides are available at
http://service.sap.com/instguides .
Required DVDs, Tools, and Other Software
■ Make sure that all required DVDs for the system copy are available:
● Installation Master DVD
NOTE
The DVD names are abbreviated.
You can find the full names of all media shipped with SAP NetWeaver 7.0 EhP 2 in the
appropriate Media List for SAP NetWeaver 7.0 EhP 2 at: http://service.sap.com/
installNW70 Installation Installation – SAP NetWeaver Systems Media List – SAP NetWeaver 7.0
EHP 2 .
■ 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.
CAUTION
The source system must be in a consistent state before you can copy it.
RECOMMENDATION
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.
■ Check that you have the appropriate tool versions for your SAP kernel.
■ For a heterogeneous system copy, you need to get a migration key by generating it at http://
service.sap.com/migrationkey.
Creating A System Copy Plan
Create a plan to perform the system copy.
1. Consider the downtime of the source system (for preparations and copying) when planning the
system copy.
2. Perform a test run of the system copy. You can use the time taken by the test run to calculate the
system downtime:
■ If your target system will 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
2 Planning
12/120 PUBLIC 2012-04-12
![Page 13: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/13.jpg)
system, and imported there. System downtime is approximately equal to the total test time
(that is, time for export, transport, and import).
■ If you do not want to replace your source system, a partial test run (export of the entire database
or parts of it) can be sufficient to calculate the system downtime. The source system is only
down for the time of the export.
Calculating the system downtime is particularly important for very large databases (VLDB)
or when tapes are being used. The test run is also to determine the amount of export data.
Choose the best data transfer method (for example, FTP or tape). We recommend that you
only perform read/write actions on local file systems.
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 using SAP tools.
Use this method if database-specific methods are either not available or not suitable. For more
information, see Database-Independent System Copy [page 23].
● The database-specific procedure using tools provided by the database vendor
Some database vendors offer specific tools for copying a database. These tools allow you to:
◆ Restore a backup of one database (source database) in another one (target database)
(backup method)
◆ Unload the source database and load the data into the target database
For more information, see Database-Specific System Copy [page 51].
These methods are not supported for all database systems. Refer to the following table to check
which copy methods are available for your database system:
Database OS Platform Available Methods
SAP MaxDB UNIX Use one of the following: ● System copy procedure on UNIX using R3load
For more information, see System Copy Procedure [page 24]. ● System copy procedure for a homogeneous system copy
onlyFor more information, see SAP MaxDB-specific procedure [page 64].
SAP MaxDB Windows Use one of the following: ● System copy procedure on Windows using R3load
For more information, see System Copy Procedure [page 24]. ● System copy procedure for a homogeneous system copy
only
2 Planning
2012-04-12 PUBLIC 13/120
![Page 14: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/14.jpg)
Database OS Platform Available MethodsFor more information, see SAP MaxDB-specific procedure [page 64].
IBM DB2 for i IBM i Use one of the following: ● System copy procedure on IBM i using R3load
For more information, see Starting SAPinst on IBM i [page 41].
● IBM i-specific procedure for a homogeneous system copy onlyFor more information, see IBM DB2 i Procedure [page 72].
For more information, see SAP Note 585277.
IBM DB2 for Linux, UNIX, and Windows
UNIX or Windows Use one of the following: ● System copy procedure using R3load
For more information, see System Copy Procedure [page 24]. ● The backup method of IBM DB2 for Linux, UNIX, and
Windows is supported for SAP systems based on SAP NetWeaver 7.0 EHP 2.For more information, see IBM DB2 for Linux, UNIX, and Windows Specific Procedures [page 68].
IBM DB2 for z/OS IBM System z Use one of the following: ● Only valid for: UNIX |
System copy procedure on UNIX using R3loadFor more information, see System Copy Procedure [page 24].End of: UNIX |
● Only valid for: Windows |
System copy procedure on Windows using R3loadFor more information, see System Copy Procedure [page 24].End of: Windows |
● Additional Information: ◆ For more information about the IBM DB2 for z/OS
specific procedure for a homogeneous system copy only, see the .PDF attachment to SAP Note 680746.
◆ When R3ta is used to split tables, DELETE with WHERE is not performed if import errors occur in the target system.For more information, see SAP Note 778729.
Oracle UNIX Use one of the following: ● Only valid for: UNIX |
System copy procedure on UNIX using R3loadFor more information, see System Copy Procedure [page 24].End of: UNIX |
● R3load method with Export/Import MonitorsFor more information, see R3load Procedures Using the Migration Monitor [page 85].
● Oracle-specific procedure for a homogeneous system copy onlyFor more information, see Oracle-Specific Procedure [page 52].
Windows Use one of the following:
2 Planning
14/120 PUBLIC 2012-04-12
![Page 15: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/15.jpg)
Database OS Platform Available Methods
● Only valid for: Windows |
System copy procedure on Windows using R3loadFor more information, see System Copy Procedure [page 24].End of: Windows |
● R3load method with Export/Import MonitorsFor more information, see R3load Procedures Using the Migration Monitor [page 85].
● Homogeneous system copy only: Oracle backup/restore methodFor more information, see Oracle-Specific Procedure [page 52] and SAP Note 676468.
MS SQL Server Windows Use one of the following: ● System copy procedure on Windows using R3load
For more information, see System Copy Procedure [page 24]. ● R3load method with Export/Import Monitors
For more information, see R3load Procedures Using the Migration Monitor [page 85].
● Homogeneous system copy only: Backup/Restore or Detach/Attach MethodFor more information, see MS SQL Server-Specific Procedure [page 67] and SAP Notes 193816 and 151603.
Sybase ASE UNIX Use one of the following: ● System copy procedure on UNIX using R3load
For more information, see System Copy Procedure [page 24]. ● R3load method with Export/Import Monitors
For more information, see R3load Procedures Using the Migration Monitor [page 85].
● Homogeneous system copy only: Backup/Restore or Detach/Attach methodFor more information, see Sybase ASE Server-Specific Procedure [page 72].
NOTE
Before you start the system copy procedure, implement SAP Note 1612437.
Windows Use one of the following: ● System copy procedure on Windows using R3load
For more information, see System Copy Procedure [page 24]. ● R3load method with Export/Import Monitors
For more information, see R3load Procedures Using the Migration Monitor [page 85].
● Homogeneous system copy only: Backup/Restore or Detach/Attach methodFor more information, see Sybase ASE Server-Specific Procedure [page 72].
NOTE
Before you start the system copy procedure, implement SAP Note 1612437.
2 Planning
2012-04-12 PUBLIC 15/120
![Page 16: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/16.jpg)
■ Choosing an SAP system ID
You can choose the new SAP system ID <TARGET_SAPSID> freely during a new installation.
CAUTION
To meet the requirements of the Workbench Organizer, you must choose different SAP
system IDs for different SAP systems.
■ SAP license
Once the installation is completed and the SAP system copy has been imported, you will require
a new license key for the target system. The license key of the source system is not valid for this
system. For more information about ordering and installing the SAP license, see the SAP Library
at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 2) English
SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability
SAP Licenses .
■ 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 at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 2) English
SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Managementby Key Capability
Data Archiving .
Access to archive files is platform-independent.
■ Configuration analysis and hardware analysis
You need to determine the:
● Number of application servers
● Expected size of the database
● Additional disks or other hardware required
● Required memory
NOTE
Refer to the section on hardware and software requirements in the SAP system
installation documentation to determine the system requirements.
2 Planning
16/120 PUBLIC 2012-04-12
![Page 17: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/17.jpg)
3 Preparations
Before you start the system copy, you must perform the following preparation steps:
3.1 General Technical Preparations
Procedure
To 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. For more information about SAP system
administration, refer to 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
with 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 central instance.
■ Only valid for: UNIX;Windows |
Before you start the export on your source system, check that your JAVA_HOME environment
points to a valid JDK version.End of: UNIX;Windows |
■ No canceled or pending update requests should be in the system. Check this by choosing Tools
Administration Monitor Update (transaction SM13).
If canceled or pending updates exist, you must update these again or delete them from all clients.
You can find out 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:
3 Preparations
3.1 General Technical Preparations
2012-04-12 PUBLIC 17/120
![Page 18: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/18.jpg)
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:
Tools CCMS Configuration Operation mode calendar (transaction SM63)
■ Write down the logical system names of all clients:
1. If you plan to overwrite an existing system with a system copy, make sure you write down the
logical system names of all clients in the system that will be overwritten (transaction SCC4).
Since the logical system names will be overwritten, in the event of differences, you must change
them back to their original names (as they existed in the system that is overwritten) in the
follow-on actions after the system copy.
2. If you create a new system with a system copy (for example, create an upgrade test system),
make sure that the logical naming strategy for this new system is consistent with your existing
logical system naming convention. If you are still planning your BI (formerly BW) system
landscape, see SAP Note 184447.
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.
■ Only valid for: UNIX |
If your source system is not a new installation but is an upgrade from an SAP system with a release
level earlier than SAP NetWeaver 2004s, you must adjust the directory structure before you start
the export. To do so, apply SAP Note 1104735.End of: UNIX |
■ 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:
Accounting Financial Accounting General ledger Periodic Processing Closing Check/count
Comparison
3 Preparations
3.1 General Technical Preparations
18/120 PUBLIC 2012-04-12
![Page 19: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/19.jpg)
● 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.
CAUTION
Make sure that no customer data is changed in the meantime.
◆ RFUMSV00 (tax on sales/purchases)
◆ RAGITT01 (asset history sheet)
◆ RAZUGA01 (asset acquisitions)
◆ RAABGA01 (fixed asset retirements)
■ BI customers: If you want to perform a system landscape copy for SAP NetWeaver BW, apply SAP
Note 886102.
■ CO customers: You can perform an additional consistency check by running the report group
1SIP before copying the source system, as well as after copying the target system, and then compare
the results. Make sure that no customer data is changed in the meantime.
CAUTION
Prerequisites for an export:
Before performing an export, make sure that no incremental conversion is in progress.
To test if an incremental conversion is in progress, run transaction ICNV. If there are any table
entries in table TICNV, an incremental conversion is in progress. In this case, you have the
following options:
1. Defer the migration until the incremental conversion has finished.
2. Try to finish the incremental conversion by performing the following steps:
● If the tables are in state For conversion or in state Done, delete the entries by choosing Control
Delete Entry .
● If the tables are in any other state, you have to finish the incremental conversion. Choose
Assistant and proceed according to the online documentation.
CAUTION
Heterogeneous System Copy only:
Before you start the export of your source system, make sure that the tables TATGPC and
TATGPCA are empty. To do so, use your database utility and delete the contents of these tables
with the following statements:
DELETE from TATGPC
DELETE from TATGPCA
Normally 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.
■ Prepare the system for SAPinst. For more information, see Installing the Java Runtime Environment [page
20].
3 Preparations
3.1 General Technical Preparations
2012-04-12 PUBLIC 19/120
![Page 20: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/20.jpg)
Only valid for: IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |
3.2 Installing the Java Runtime EnvironmentOnly valid for: IBM DB2 for i5/OS |
You need to prepare your Windows system for SAPinst. This includes the installation of a Java Runtime
Environment (JRE), which is required for SAPinst on Windows. The JRE is part of the JDK (Java
Development Kit) and not part of the SAP shipment.End of: IBM DB2 for i5/OS |
Only valid for: IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |
You need to prepare your system for SAPinst. This includes the installation of a Java Runtime
Environment (JRE), which is required for SAPinst. The JRE is part of the JDK (Java Development Kit)
and not part of the SAP shipment.End of: IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |
Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |
NOTE
Since IBM i has no graphical user interface, the SAPinst executable is running on the Windows
installation host. You need to install a valid JDK on Windows only for installation purposes. The
J2EE engine of the SAP system uses the IBM JDK as mentioned in the section Hardware and Software
Requirements [external document].
End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |
Only valid for: UNIX;Windows |
NOTE
If required, you can perform a remote installation using a standalone SAPinst GUI on a separate
Windows or UNIX host. This lets you perform the installation on a remote host, controlling it
with the SAPinst GUI from a local host. If you want to perform a remote installation, see Performing
a Remote Installation with SAPinst [page 106].
End of: UNIX;Windows |
Procedure
1. Only valid for: IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |
Check the JRE versions that are released for SAP systems in the Product Availability Matrix (PAM):End of: IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |
3 Preparations
3.2 Installing the Java Runtime Environment
20/120 PUBLIC 2012-04-12
![Page 21: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/21.jpg)
Only valid for: IBM DB2 for i5/OS |
Check the JRE Windows versions that are released for SAP systems in the Product Availability
Matrix (PAM):End of: IBM DB2 for i5/OS |
1. Go to http://service.sap.com/pam.
2. Choose Start PAM with navigation by category.
3. Only valid for: SAP NetWeaver |
On the right-hand panel, choose SAP NetWeaver SAP EHP2 FOR SAP NETWEAVER 7.0 .End of: SAP NetWeaver |
4. Only valid for: SAP CRM;SAP ERP;SAP SCM;SAP SRM |
On the right-hand panel, choose SAP Application Components <your product> .End of: SAP CRM;SAP ERP;SAP SCM;SAP SRM |
5. Choose tabstrip JSE Platforms.
Only valid for: IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |
NOTE
For more information about how to download it, see the relevant SAP Note for your operating
system, which is referenced near the beginning of SAP Note 723909.
End of: IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |
Only valid for: IBM DB2 for i5/OS |
NOTE
For more information about how to download it, see the relevant SAP Note for your Windows
operating system, which is referenced near the beginning of SAP Note 723909.
End of: IBM DB2 for i5/OS |
2. Make sure a valid JRE version is installed, as follows:
■ If the JRE is not already installed, download and install it.
■ If the JRE is already installed, check the installed version of the JRE by entering:
java -version
Only valid for: Linux |
NOTE
If you use a Sun Java VM, edit the configuration file $JAVA_HOME/jre/lib/security/
java.security and replace entry securerandom.source=file:/dev/random with
securerandom.source=file:/dev/urandom.
End of: Linux |
End of: IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |
3 Preparations
3.2 Installing the Java Runtime Environment
2012-04-12 PUBLIC 21/120
![Page 22: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/22.jpg)
This page is left blank for documents that are printed on both sides.
![Page 23: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/23.jpg)
4 Database Independent System Copy
With the SAP installation tool SAPinst, you can export and import your database in a database-
independent format. SAPinst uses the R3load tool.
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.
Constraints
R3load Restrictions
■ SAPinst generates a database dump of all SAP objects that are defined in the ABAP Dictionary
(R3load). 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.
■ 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.
■ Indexes longer than 18 characters are not allowed on the database to be exported.
System Copy Tools
Only valid for: IBM i5/OS;UNIX;Windows |
■ Every installation service (dialog instance installation, for example) must have its own separate
installation directory whenever you start SAPinst.
■ If the target system already exists and 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 the Additional Information section of the installation documentation for your SAP
component.
If the database configuration of your database is stored in the file system, we recommend that you
back these configuration files up before deleting the database.End of: IBM i5/OS;UNIX;Windows |
Only valid for: IBM i5/OS |
Every installation service (dialog instance installation, for example) must have its own separate
installation directory whenever you start SAPinst.End of: IBM i5/OS |
4 Database Independent System Copy
2012-04-12 PUBLIC 23/120
![Page 24: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/24.jpg)
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 the number and size of
contained tables, resulting in varying unload/load runtimes. The overall runtime can be reduced
by creating packages of the same size, that is, creating packages with a similar processing time. You
can achieve this by splitting the default packages (one package per data class) into more smaller
pieces.
■ There are several ways to split packages. For a detailed description of the options, refer to the
F1 help about the parameters prompted on the Split 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 – together.
■ “Splitting of STR Files” is part of the “Advanced Export Parameters” and is disabled by default.
Using the splitting tool parameters selected by SAPinst is a good starting point if you select the
splitting option and you have not performed any tests yet.
CAUTION
If you want to split STR files by the size based option, 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/<DBTYPE>, for example DB/ORA.
If you do not have EXT files, then you can only split by providing tables via input file.
Process Flow
For UNIX, Windows, or IBM i, see System Copy Procedure [page 24].
4.1 System Copy Procedure
This section describes the system copy procedure using R3load.
Procedure
Process 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:
■ Central system
■ Distributed system and high-availability system
Central System
To perform the export for a central system, you need to proceed as follows on the central system host:
4 Database Independent System Copy
4.1 System Copy Procedure
24/120 PUBLIC 2012-04-12
![Page 25: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/25.jpg)
1. Heterogeneous system copy: 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 central system host:
1. Make sure that the QCM tables are deleted from your system.
For more information, see General Technical Preparations [page 17].
2. Only valid for: IBM i5/OS |
Prepare a Windows user account and an IBM i user profile.
For more information, see Preparing a Windows User Account and IBM i User Profile [page 39].End of: IBM i5/OS |
3. Generate DDL statements.
For more information, see Generating DDL Statements [page 27].
4. Prepare the system for table splitting (optional).
For more information, see Preparation for Table Splitting [page 27].
5. If you want to run export processes in parallel to import processes, run SAPinst on UNIX or
Windows [page 32] or on IBM i [page 39] to prepare the source system for the export.
In SAPinst, choose the installation service Export Preparation.
6. Run SAPinst on UNIX, Windows, or IBM i to export the database instance and the central
instance.
In SAPinst, choose the installation service Database Instance Export.
For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 32] or
Running SAPinst on IBM i to Perform the Export [page 39].
NOTE
If R3load processes fail due to an error, solve the problem and perform a restart.
For more information, see Restarting R3load Processes [page 45].
Result
You have finished this part of the system copy. To complete the system copy, you set up the target
system using SAPinst.
For more information, see Setting Up the Target System Using SAPinst [page 46].
Distributed System or High-Availability System
To perform the export for a distributed system or a high-availability-system, you need to 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.
For more information, see General Technical Preparations [page 17].
2. Generate DDL statements.
4 Database Independent System Copy
4.1 System Copy Procedure
2012-04-12 PUBLIC 25/120
![Page 26: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/26.jpg)
For more information, see Generating DDL statements [page 27].
3. If you want to run export processes in parallel to import processes, run SAPinst on UNIX or
Windows [page 32] or on IBM i [page 39] to prepare the source system for the export.
In SAPinst, choose the system copy option Export Preparation.
4. Prepare the system for table splitting (optional).
For more information, see Preparation for Table Splitting [page 27].
5. Run SAPinst on UNIX, Windows, or IBM i to export the database instance. In SAPinst, choose
the installation service Database Instance Export.
For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 32] or
Running SAPinst on IBM i to Perform the Export [page 39].
NOTE
If R3load processes fail due to an error, solve the problem and perform a restart.
For more information, see Restarting R3load Processes [page 45].
Only valid for: UNIX |
CAUTION
If your database instance is running on HP PA-Risc, you must proceed as described in
SAP Note 884452.
End of: UNIX |
Result
You have finished this part of the system copy. To complete the system copy, set up the target system
using SAPinst.
For more information, see Setting Up the Target System Using SAPinst [page 46].
Figure 1: Overview of Export Options
4 Database Independent System Copy
4.1 System Copy Procedure
26/120 PUBLIC 2012-04-12
![Page 27: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/27.jpg)
4.2 Generating DDL Statements
To 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.
Only valid for: BI Java |
CAUTION
You must ensure that no further changes (such as, activations, data loads to cubes, or field changes)
are executed in the SAP NetWeaver Business Intelligence system after you have called the
SMIGR_CREATE_DDL report and before you export the data.
End of: BI Java |
Procedure
1. 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. You should only
enter a database version that is available in the value help.
4. 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 written to the specified directory. From there, SAPinst
copies them to the <export dump directory>/ABAP/DB export directory.
If you copy the SQL files directly to the export directory, make sure that they have read access.
CAUTION
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 SAP Note 888210.
4.3 Preparation for Table Splitting
The 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:
4 Database Independent System Copy
4.2 Generating DDL Statements
2012-04-12 PUBLIC 27/120
![Page 28: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/28.jpg)
■ 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 have 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 85].
■ 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:
● DB2 for z/OS (Only create a temporary index if you want to perform an unsorted unload.)
● Oracle
For more information, see the 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)
Procedure
1. Only valid for: IBM i5/OS |
Update the file R3ta in the kernel directory. You can find a version of this file on the Installation
Master DVD in the directory IM_<OS>/<DBTYPE>/{UC/NUC}.End of: IBM i5/OS |
2. Only valid for: UNIX;Windows |
Update the R3ta, R3ldctld, and the db<dbtype>slib.* in the kernel directory. You can find a
version of these files on the Installation Master DVD in the directory IM_<OS>/<DBTYPE>/{UC/
NUC}.End of: UNIX;Windows |
3. Create a file that contains lines of the form <table>%<nr of splits> for all tables to be split.
4 Database Independent System Copy
4.3 Preparation for Table Splitting
28/120 PUBLIC 2012-04-12
![Page 29: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/29.jpg)
Only valid for: Oracle |
Oracle PL/SQL splitter only: Use the form <table>%<nr of splits>;<rowid or column>. For
more information about the Oracle PL/SQL splitter, see SAP Note 1043380.End of: Oracle |
CAUTION
■ The tables listed in this file have to appear in alphabetical order!
■ This file must not contain empty lines.
4. Start SAPinst.
5. Choose <SAP Product> Software Life-Cycle Options System Copy <Database> Source System Export
<System Variant> Based on <Technical Stack> Table Splitting Preparation .
6. Specify SAPSID, <sidadm> password, the file that contains the split information, the export
directory, and the number of parallel R3ta jobs.
CAUTION
The specified path to the export directory must not contain blanks!
7. Continue with Next.
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.
8. Check in the export directory <export dump directory>/ABAP/DATA if *.WHR files have been
created for all tables that are to be split.
If no *.WHR files could be produced for some of these tables, create fewer packages for these tables:
1. Create a new, empty installation directory.
2. Define a new, empty export dump directory <temporary dump directory>.
3. Run the Prepare Table Splitting service again and provide an input file that contains only the
missing tables with a lower number of packages for each defined table.
If the *.WHR files have been created for the missing tables, merge these results with the results from
the first Prepare Table Splitting run:
1. Copy the *.WHR files from <temporary dump directory>/ABAP/DATA to <export dump
directory>/ABAP/DATA.
2. Add the lines from <temporary dump directory>/ABAP/DATA/whr.txt to <export dump
directory>/ABAP/DATA/whr.txt.
9. If required, create the temporary index on the source system's tables to be split.
Only valid for: Oracle |
This is not required if you export the database using the Oracle-specific method with the Oracle
PL/SQL splitter.End of: Oracle |
4 Database Independent System Copy
4.3 Preparation for Table Splitting
2012-04-12 PUBLIC 29/120
![Page 30: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/30.jpg)
For more information, see the paragraph Creating a Temporary Index.
Parallel data export of a table is supported by all database platforms but parallel data import is not. If
the target database platform does not support the parallel data import, the migration monitor has to
be configured so that the data import processes the packages sequentially. For more information, see
Processing Split Tables.
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 Master
DVD. After the Table Splitting Preparation, make sure you select the Split predefined tables checkbox and add
the R3ta_hints.txt file in the Split STR Files dialog box. If you want to modify this file, copy it from the
directory <IM_OS>/COMMON/INSTALL to the installation directory and adapt it according to your
requirements as soon as the Parameter Summary dialog appears, and before starting the processing phase.
Creating a Temporary Index
Only valid for: IBM DB2 for z/OS |
IBM DB2 z/OS only: Create the corresponding temporary index on the database with database tools.
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 |
Only valid for: IBM DB2 for z/OS |
EXAMPLE
1. 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 |
For each table to be split, R3ta creates the following files to facilitate the creation of the temporary
index:
File Description
<table>_IDX.STR Contains the description of the temporary index; the default index name is <table>~IMG.
<table>_IDX.TSK Contains the task to create the temporary index.
<table>_IDX.cmd R3load command file for creating the temporary index.
DRP_<table>_IDX.TSK Contains the task to drop the temporary index.
DRP_<table>_IDX.cmd R3load command file for dropping the temporary index.
4 Database Independent System Copy
4.3 Preparation for Table Splitting
30/120 PUBLIC 2012-04-12
![Page 31: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/31.jpg)
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<DBTYPE>.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<DBTYPE>.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& )
NOLOGGING
COMPUTE STATISTICS PARALLEL
ONLINE;End of: Oracle |
3. Call R3load as user <sapsid>adm with the following parameters:
R3load –dbcodepage <source system’s dbcodepage> –i
<table>_IDX.cmd –l <table>_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 Import
If 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:
■ Creating the export directory structure
■ Calculating the size of the target database
■ Creating database size file DBSIZE.XML
4 Database Independent System Copy
4.4 Preparing Parallel Export and Import
2012-04-12 PUBLIC 31/120
![Page 32: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/32.jpg)
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. Run SAPinst to perform the Export Preparation.
For more information, see Exporting the Source System Using SAPinst [page 32].
2. As soon as the export preparation has finished successfully, the complete export directory with its
structure and the generated DBSIZE.XML file have to be transferred to the target host.
For more information, see Transferring the Export Files to the Target Host [page 47].
More Information
R3load Procedures Using the Migration Monitor [page 85]
4.5 Exporting the Source System Using SAPinst
Here you can find information about how to run SAPinst to perform the export on the source system:
■ Running SAPinst on UNIX or Windows to Perform the Export [page 32]
■ Running SAPinst on IBM i to Perform the Export [page 41]
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
a GUI client and a GUI server, which both use Java.
This section describes a standard export where SAPinst, GUI client, and GUI server are running on the
same host. In the following, GUI client and GUI server are addressed as “SAPinst GUI”.
Only valid for: UNIX |
If you need to see the installation on a remote display, we recommend that you perform a remote
installation, where the SAPinst GUI is running on a separate host from SAPinst. For more information,
see Performing a Remote Installation with SAPinst [page 106].End of: UNIX |
Useful Information About SAPinst
■ When you start SAPinst, it automatically starts the SAPinst GUI.
Only valid for: UNIX |
UNIX
■ SAPinst creates the installation directory sapinst_instdir directly below the temporary directory.
SAPinst finds the temporary directory by checking the value of the following environment variables
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
32/120 PUBLIC 2012-04-12
![Page 33: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/33.jpg)
in the following sequence: TEMP, TMP, and TMPDIR. If no value is set for these variables, SAPinst
creates the installation directory sapinst_instdir directly below the /tmp directory by default.
If you want SAPinst to create the installation directory sapinst_instdir in another directory, set
the environment variable TEMP to this directory before you start SAPinst.
Shell Used Command
Bourne shell (sh) TEMP=<directory>
export TEMP
C shell (csh) setenv TEMP <directory>
Korn shell (ksh) export TEMP=<directory>
CAUTION
Make sure that the installation directory is not mounted with NFS, or there might be problems
when the Java Virtual Machine is started.
■ SAPinst creates a subdirectory for each installation service called sapinst_instdir/
<installation_option_directory>.
■ SAPinst extracts itself to a temporary directory called sapinst_exe.xxxxxx.xxxx, which is located
in the environment variables TEMP, TMP, or TMPDIR. These files are deleted after SAPinst has stopped
running.End of: UNIX |
Only valid for: Windows |
Windows
■ SAPinst creates the installation directory sapinst_instdir, where it keeps its log files, and which
is located directly in the %ProgramFiles% directory. If SAPinst is not able to create
sapinst_instdir there, it tries to create sapinst_instdir in the directory defined by the
environment variable TEMP
■ SAPinst creates a subdirectory for each installation service, called <sapinst_instdir>
\<installation_service>, which is located below %ProgramFiles%\sapinst_instdir.
■ SAPinst extracts itself to a temporary directory called sapinst_exe.xxxxxx.xxxx, which is located
in %TEMP%, %TMP%, %TMPDIR%, or %SystemRoot%. These files are deleted after SAPinst has stopped
running.End of: Windows |
■ The temporary directory sapinst_exe.xxxxxx.xxxx sometimes remains undeleted. You can safely
delete it.
The temporary directory also contains the log file dev_selfex.out from the extraction process,
which might be useful if an error occurs.
CAUTION
● If SAPinst cannot find a temporary directory, the installation terminates with the error
FCO-00058.
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
2012-04-12 PUBLIC 33/120
![Page 34: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/34.jpg)
● If you would rather create an installation directory manually, make sure that you create
it locally. Otherwise, you might experience problems when starting the SAP Java tools.
■ During the installation, the default ports 21200, 21212, and 4239 are used for communication
between SAPinst, GUI server, GUI, and HTTP server, as follows:
● SAPinst uses port 21200 to communicate with the GUI server.
● The GUI server uses port 21212 to communicate with the GUI client.
● 4239 is the port of the HTTP server, which is part of the GUI server.
If the ports for SAPinst and the GUI server are already in use, SAPinst automatically searches for
free port numbers. If the search fails, you see an error message and SAPinst exits. In this case or if
you want SAPinst to use specific ports, proceed as follows:
● UNIX: Assign ports by executing the sapinst executable with the following command line
parameters:
◆ SAPINST_DIALOG_PORT=<port_number_sapinst_to_gui_server>
◆ GUISERVER_DIALOG_PORT=<port_number_gui_server_to_gui_client>
◆ GUISERVER_HTTP_PORT=<port_number_http_server>
● Windows: Open a command prompt and change to the required directory as follows:
Only valid for: Windows | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |
cd /d <DVD drive>:\IM_WINDOWS_<platform>
End of: Windows | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |
Only valid for: Windows |
Execute sapinst.exe with the following command line parameters:End of: Windows |
◆ SAPINST_DIALOG_PORT=<port_number_sapinst_to_gui_server>
◆ GUISERVER_DIALOG_PORT=<port_number_gui_server_to_gui_client>
◆ GUISERVER_HTTP_PORT=<port_number_http_server>
■ To see a list of all available SAPinst properties, proceed as follows:
● UNIX: Start SAPinst as described above with command line parameter -p: ./sapinst -p
● Windows: Open a command prompt and start SAPinst with command line parameter -p:
sapinst.exe -p
■ If required, you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu.
NOTE
Only valid for: UNIX |
If you need to terminate SAPinst, you can do this by pressing Ctrl + C .End of: UNIX |
Only valid for: Windows |
If you need to terminate SAPinst you can do this by choosing File Exit in the menu of
the Program Starter window.End of: Windows |
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
34/120 PUBLIC 2012-04-12
![Page 35: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/35.jpg)
Prerequisites
CAUTION
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 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. Make sure that the temporary directory has the permissions 1777.End of: UNIX |
■ Only valid for: Windows |
Before starting the export steps on the central instance of the source system, make sure that you
have at least the same amount of disk space available in \\SAPLOC\<SAPSID>\<InstanceName>\SDM
\program as is used in \\SAPLOC\<SAPSID>\<InstanceName>\root\origin. During the export
some archives are written to the program subdirectories and SAPinst aborts if there is not enough
space.End of: Windows |
Only valid for: UNIX |
■ Before starting the export, make sure that you have at least the same amount of disk space available
in /sapmnt/<SAPSID>/<InstanceName>/SDM/program as is used in /sapmnt/<SAPSID>/
<InstanceName>/SDM/root/origin.
During the export, some archives are written to the program subdirectories and SAPinst aborts if
there is not enough space.
■ Make sure that the DISPLAY environment variable is set to <host_name>:0.0, where
<host_name> is the host where the SAPinst GUI is displayed.
■ Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime
Environment (JRE).
■ Only valid for: AIX |
If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE for AIX
64-bit.End of: AIX |
■ 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.End of: UNIX |
For more information about SAPinst, see Interrupted Installation with SAPinst [page 102] and Performing a Remote
Export Using SAPinst [page 105].
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
2012-04-12 PUBLIC 35/120
![Page 36: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/36.jpg)
Procedure
1. Only valid for: UNIX |
Log on to your host as user root.End of: UNIX |
Only valid for: Windows |
Log on to your host as a user with the user authorization to install the SAP system with the SAPinst
tool. For more information, see Required User Authorization for Running SAPinst in your installation guide.End of: Windows |
2. Only valid for: Windows |
Insert the Installation Master DVD into your DVD drive or mount it locally.End of: Windows |
Only valid for: UNIX |
Mount the Installation Master DVD locally. We do not recommend that you use Network File
System (NFS), because reading from DVDs mounted with NFS might fail.End of: UNIX |
3. Start SAPinst from the Installation Master DVD as follows:
Only valid for: Windows |
■ Double-click sapinst.exe from the following path:
<DVD_drive>:\IM_WINDOWS_<platform>
The GUI starts automatically by displaying the Welcome screen.
However, if there is only one component to install, SAPinst directly displays the first input
dialog without presenting the Welcome screen.End of: Windows |
Only valid for: UNIX |
Choose one of the following ways:
■ Using the default installation directory (recommended)
Enter the following commands:
cd <Mountpoint of Installation Master DVD>/IM_<OS> ./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.
CAUTION
Make sure that your current working directory is not an IM_<OS> directory belonging
to another operating system.
For example, the following commands are incorrect and cause an error:
$ cd /sapcd2/IM_HPUX_IA64
$ /sapcd2/IM_HPUX_PARISC/sapinst
The following commands are correct:
$ cd /sapcd2/IM_HPUX_PARISC
$ /sapcd2/IM_HPUX_PARISC/sapinst
■ Using an alternative installation directory
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
36/120 PUBLIC 2012-04-12
![Page 37: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/37.jpg)
If you want to use an alternative installation directory, set the environment variable TEMP,
TMP, or TMPDIR.End of: UNIX |
NOTE
If you want to use a virtual host name, start the export with the SAPinst property
SAPINST_USE_HOSTNAME as follows:
./sapinst SAPINST_USE_HOSTNAME=<virtual host name>.
4. On the Welcome screen, choose <SAP Product> Software Life-Cycle Options System Copy <Database>
Source System Export <Distribution Option> Based on <technical stack> .
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.
For more information, see Database-Independent System Copy [page 23].
CAUTION
Make sure that you choose the system copy options in exactly the order they appear for each
system variant.
The following tables provide an overview of the installation options available for the export:
Export Services for a Central System
Export Service Remarks
Export Preparation
NOTE
Do not perform this step if you use the database-specific method.
Optional step that is required only if you want to run export and import processes in parallel.SAPinst performs the following steps: ■ Creates the export directory structure ■ Calculates the size of the target database (DBSIZE.XML)
Table Splitting Preparation
NOTE
Do not perform this step if you use the database-specific method.
Optional stepSAPinst performs the following steps: ■ Creates the export directory DATA ■ Creates database structure files (*.STR) for the tables to be split ■ Splits the generated STR files ■ Creates where-conditions for the tables to be split ■ Splits the generated WHR files ■ Copies the resulting WHR files to the export directory DATA
Database Instance Export
NOTE
Do not perform this step if you use the database-specific method.
Mandatory step for database-independent system copy procedure.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) ■ Exports the ABAP database content
Export Services for a Distributed System or a High-Availability System
Export Service Remarks
Export Preparation Optional step that is required only if you want to run export and import processes in parallel.
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
2012-04-12 PUBLIC 37/120
![Page 38: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/38.jpg)
Export Service RemarksNOTE
Do not perform this step if you use the database-specific method.
You need to perform this step on the database instance host.SAPinst performs the following steps: ■ Creates the export directory structure ■ Calculates the size of the target database
(DBSIZE.XML)
Table Splitting Preparation
NOTE
Do not perform this step if you use the database-specific method.
Optional stepSAPinst performs the following steps: ■ Creates the export directory DATA ■ Creates database structure files (*.STR) for the tables
to be split ■ Splits the generated STR files ■ Creates where-conditions for the tables to be split ■ Splits the generated WHR files ■ Copies the resulting WHR files to the export directory
DATA
Database Instance Export
NOTE
Do not perform this step if you use the database-specific method.
Mandatory step for the system copy procedure.You need to perform this step on the database instance host.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
6. After you have selected the required option, choose Next.
7. If you generated SQL files with DDL statements (see Generating DDL Statements [page 27]) during the
database instance export, 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.
CAUTION
You must choose parameter mode Typical when performing a system copy with database
tools.
NOTE
■ If parallel export and import has been prepared, ensure the following:
● You choose parameter mode Custom.
● You select the expert option Parallel Export and Import for the database instance export
on the SAP System > Database Export screen.
■ If table splitting for ABAP tables has been prepared before the data export via SAPinst,
the SAPinst export automatically does the following:
● It forces package splitting.
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
38/120 PUBLIC 2012-04-12
![Page 39: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/39.jpg)
● 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.
NOTE
For 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.
Only valid for: IBM i5/OS |
4.5.2 Running SAPinst on IBM i to Perform the ExportOnly valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |
4.5.2.1 Preparing a Windows User Account and IBM i Installation User Profile
For the installation you need to create a user account on your Windows installation host and a user
profile on the IBM i you want to install.
The following requirements apply:
■ The IBM i user profile and the Windows user account must have the same name and password.
■ Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |
The IBM i user profile must have user class *SECOFR and all special authorities that belong to user
QSECOFR.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |
■ Only valid for: SAP SCM |
The IBM i user profile must be the user QSECOFR.
NOTE
This is different to other installations on IBM i. For other installations, we recommended that
you create user SAPIUSR. However for SCM, you need to use the user QSECOFR because the
liveCache client software has to be installed by this special user.
End of: SAP SCM |
ProcedureOnly valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |
NOTE
The user name SAPIUSR and the password SAP are used as examples in the procedures. In former
installation documentation, we used the user SAPINST. However, in future releases SAP has
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
2012-04-12 PUBLIC 39/120
![Page 40: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/40.jpg)
introduced a group called SAPINST on IBM i, which conflicts with the previously recommended
user SAPINST.
End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |
Windows:
1. Create a local user.
2. Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |
In the field User name, enter your installation user name, for example, SAPIUSR.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |
3. Only valid for: SAP SCM |
In the field User name, enter your installation user name QSECOFR.End of: SAP SCM |
4. Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |
In the fields Password and Confirm password, enter the password SAP.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |
5. Only valid for: SAP SCM |
In the fields Password and Confirm password, enter the password of the user QSECOFR on your IBM i.End of: SAP SCM |
6. Deselect User must change password at next logon.
7. Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |
Assign the new user SAPIUSR to the group Administrators.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |
8. Only valid for: SAP SCM |
Assign the new user QSECOFR to the group Administrators.End of: SAP SCM |
IBM i:
Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |
Enter the following command:CRTUSRPRF USRPRF(SAPIUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT
('Test User for SAP Installation') SPCAUT(*USRCLS) LANGID(ENU) CNTRYID(US) CCSID(500)
LOCALE(*NONE)
End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP Solution Manager;SAP SRM |
Only valid for: SAP SCM |
To change the user QSECOFR, enter the following command: CHGUSRPRF USRPRF(QSECOFR) LANGID
(ENU) CNTRYID(US) CCSID(500) LOCALE(*NONE)
End of: SAP SCM |
Only valid for: SAP SCM |
. After the installation, you can revert the user profile QSECOFR back to the old values.End of: SAP SCM |
CAUTION
You should not set the system variable QIBM_PASE_CCSID. Do not leave this variable empty. Make
sure that QIBM_PASE_CCSID is deleted at least for the time while you are installing your SAP
system using the following command:
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
40/120 PUBLIC 2012-04-12
![Page 41: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/41.jpg)
RMVENVVAR ENVVAR(QIBM_PASE_CCSID) LEVEL(*SYS)
End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |
Only valid for: IBM i5/OS |
4.5.2.2 Starting SAPinst on IBM i
CAUTION
This section refers to “installation of an instance”, which is a synonym for “export an SAP system”.
This procedure tells you how to run SAPinst to install one or more SAP instances. It describes an
installation where SAPinst GUI is running on the Windows host and the SAPinst Server is running on
the IBM i host.
SAPinst creates the installation directory /tmp/sapinst_instdir on IBM i.
Prerequisites
CAUTION
Make sure that you shut down all SAP Application Servers before the export. Otherwise, the target
system might be inconsistent.
The users required for the installation are prepared. For more information, see Preparing a Windows User
Account and IBM i User Profile [page 39].
Procedure
1. Log on to the IBM i host as the installation user. For more information, see Preparing a Windows User
Account and IBM i User Profile [page 39].
2. Start SAPinst from the Installation Master DVD by entering the following commands:
CD DIR('<Installation Master_DVD>/IM_OS400_PPC64')
CALL PGM(QP2TERM) PARM('./sapinst')
NOTE
As a default, there is no GUI on IBM i, so you do not see the Welcome screen for SAPinst. You
must start the SAPinst with the parameter '-nogui' and the SAPinst GUI separately on a
Windows 32-bit platform. For more information, see perform a remote installation with SAPinst [page
106].
NOTE
If you want to use a virtual host name, start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows:
CALL PGM(QP2TERM) PARM('./sapinst' 'SAPINST_USE_HOSTNAME=<virtual host name>')
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
2012-04-12 PUBLIC 41/120
![Page 42: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/42.jpg)
CAUTION
■ Make sure that the installation directory is not mounted with NFS, or there might be
problems when the Java Virtual Machine is started.
■ Make sure that your current working directory is not an IM_<OS>_<DB> 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_IA64/sapinst')
The following commands are correct:
$ CD DIR('/sapcd2/IM_OS400_PPC64')
$ CALL PGM(QP2TERM) PARM('./sapinst')
3. In the Welcome screen, choose <SAP Product> Software Life-Cycle Options System Copy <Database>
Source System Export <System Variant> Based on <technical stack> .
4. Select the corresponding installation service from the tree structure, according to the sequence
of the process flow for the database-independent system copy procedure.
For more information, see Database-Independent System Copy [page 23].
CAUTION
Make sure that you choose the installation services in exactly the order they appear for each
system variant.
5. The following tables provide an overview about the installation services available for the export:
Only valid for: IBM i5/OS |
NOTE
To export a database instance using the database-specific method, you must call SAVLIB. For
more information, see SAP Note 58277.
End of: IBM i5/OS |
Export Services for a Central System
Export Service Remarks
Export Preparation
NOTE
Do not perform this step if you use the database-specific method.
Optional step that is required only if you want to run export and import processes in parallel.SAPinst performs the following steps: ■ Creates the export directory structure ■ Calculates the size of the target database (DBSIZE.XML)
Table Splitting Preparation
NOTE
Do not perform this step if you use the database-specific method.
Optional stepSAPinst performs the following steps: ■ Creates the export directory DATA ■ Creates database structure files (*.STR) for the tables to be split ■ Splits the generated STR files ■ Creates where-conditions for the tables to be split ■ Splits the generated WHR files ■ Copies the resulting WHR files to the export directory DATA
Database Instance Export Mandatory step for database-independent system copy procedure.
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
42/120 PUBLIC 2012-04-12
![Page 43: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/43.jpg)
Export Service RemarksNOTE
Do not perform this step if you use the database-specific method.
SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*.EXT, DBSIZE.XML) ■ Exports the ABAP database content
Export Services for a Distributed System or a High-Availability System
Export Service Remarks
Export Preparation
NOTE
Do not perform this step if you use the database-specific method.
Optional step that is required only if you want to run export and import processes in parallel.You need to perform this step on the database instance host.SAPinst performs the following steps: ■ Creates the export directory structure ■ Calculates the size of the target database
(DBSIZE.XML)
Table Splitting Preparation
NOTE
Do not perform this step if you use the database-specific method.
Optional stepSAPinst performs the following steps: ■ Creates the export directory DATA ■ Creates database structure files (*.STR) for the tables
to be split ■ Splits the generated STR files ■ Creates where-conditions for the tables to be split ■ Splits the generated WHR files ■ Copies the resulting WHR files to the export directory
DATA
Database Instance Export
NOTE
Do not perform this step if you use the database-specific method.
Mandatory step for the system copy procedure.You need to perform this step on the database instance host.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
6. After you have selected the required installation service, choose Next.
7. If you generated SQL files with DDL statements (see Generating DLL Statements [page 27]), copy the
generated files into the SAPinst installation directory as soon as it has been created by SAPinst:
1. Choose Database and Central Instance Export
2. Choose Next.
3. The installation directory has been created as soon as the first input screen appears.
8. Follow the instructions in the SAPinst input dialogs and enter the required parameters.
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
2012-04-12 PUBLIC 43/120
![Page 44: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/44.jpg)
CAUTION
You must choose parameter mode Typical when performing a system copy with database
tools.
NOTE
■ If parallel export and import has been prepared, ensure the following:
● You choose parameter mode Custom.
● You select the expert option Parallel Export and Import for the database instance export
on the SAP System > Database Export screen.
■ If table splitting for ABAP tables 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.
NOTE
For 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 installation and displays the
progress of the installation.
When the installation has successfully completed, the screen Finished installation is displayed.
Troubleshooting
CAUTION
If an export process aborts due to a hardware failure (for example, file system full, power outage,
operating system crash), you have to repeat the export of the complete package. Remove the
dump files <package>.<nnn>, the TOC file <package>.TOC, the log file <package>.log and make
sure that all tables in the TSK file <package>.*TSK* have the status flag 'xeq' or 'err' set.
■ If an error occurs during the dialog phase, SAPinst:
● Stops the installation.
● Displays a dialog that informs you about the error.
You can now directly view the log file by choosing View Logs.
Finally, you must abort the installation with OK and try to solve the problem.
■ If an error occurs during the processing phase, SAPinst:
● Stops the installation.
● Displays a dialog that informs you about the error.
You can now directly view the log file by choosing View Logs.
● Try to solve the problem.
● Retry the installation by choosing Retry.
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
44/120 PUBLIC 2012-04-12
![Page 45: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/45.jpg)
● Abort the installation by choosing OK.
For more information, see Interrupted Installation with SAPinst [page 102].End of: IBM i5/OS |
End of: IBM i5/OS |
4.5.3 Restarting R3load Processes
You 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 100]) 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.
Procedure
Restarting R3load Processes Without Using the Socket Option
■ 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
to the package state are ignored.
Restarting R3load Processes Using the Socket Option
1. 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.
2. There are four possible situations where an R3load restart may be required. Proceed as required:
■ 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” and for the
export TSK file from “ok” to “err”.
4 Database Independent System Copy
4.5 Exporting the Source System Using SAPinst
2012-04-12 PUBLIC 45/120
![Page 46: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/46.jpg)
■ 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 in both
the export and the import TSK file to “err” and in the export_state.properties and
import_state.properties files to “–”.
EXAMPLE
Export Import
Table name Status Table name Status
TAB_1 ok TAB_1 ok
TAB_2 err TAB_2 ok
TAB_3 xeq TAB_3 err
TAB_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
export_state.properties and import_state.properties files also must be set
from “+” to “0”.
■ If the import is completed successfully, but the export was canceled with errors, you can
set the status in the export_state.properties from “–” to “+”.
3. Restart SAPinst or the Migration Monitor to proceed with the system copy.
More Information
R3load Processes Using the Migration Monitor [page 85].
4.6 Setting Up the Target System
Purpose
Use SAPinst to install the target system and import the database files that you have exported from the
source system.
Process Flow
Central System
Perform the following steps on the central system host:
1. Prepare the central system host for the installation of your target system as described in the
installation guide for your SAP system solution.
2. If you have already prepared the export (for more information, see Preparing Parallel Export and
Import [page 31]) on the source system because you want to perform export processes in parallel
to import processes, and 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
4 Database Independent System Copy
4.6 Setting Up the Target System
46/120 PUBLIC 2012-04-12
![Page 47: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/47.jpg)
transferred the files, which were generated in the preparation step for parallel export and import
on the source system.
3. Transfer the export files [page 47] to the central system target host.
4. Install the target system [page 48].
5. If required install additional dialog instances on dialog instance hosts as described in the
installation guide for your SAP system solution.
Distributed System or High-Availability System
Perform the following steps on the relevant installation hosts of your target system:
1. Prepare the central instance host and the database instance host for the installation of the
corresponding instances of your target system as described in the installation guide for your SAP
system solution.
Only valid for: High Availability |
Also prepare the central services instance host.End of: High Availability |
2. Only valid for: High Availability |
Install the central services instance for the target system as described in the installation guide
for your SAP system solution.End of: High Availability |
3. Perform the following steps on the database instance host:
■ If you have already prepared the export (for more information, see Preparing Parallel Export and
Import [page 31]) on the source system because you want to perform export processes in
parallel to import processes, and 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 were generated in the preparation
step for parallel export and import on the source system.
■ Transfer the export files [page 47] to the central instance target host.
■ Install the database instance of the target system. For more information, see Installing the Target
System [page 48].
4. On the central instance host, install the central instance of the target system.
5. If required, install additional dialog instances on the dialog instance hosts as described in the
installation guide for your SAP system solution.
4.6.1 Transferring the Export Files to the Target Host
Procedure
1. On the target host, create a directory <EXPDIR> with sufficient space for the database export files
available.
4 Database Independent System Copy
4.6 Setting Up the Target System
2012-04-12 PUBLIC 47/120
![Page 48: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/48.jpg)
CAUTION
Do not create this directory under the installation directory or another directory that
contains installation information (such as the Installation Master DVD, the Java DVD, or
other export files).
Otherwise, SAPinst does not ask you to specify the export directory and automatically chooses
one that you may not want to use. In this case, SAPinst does not display the export directory
and you cannot change it.
2. Transfer all files and directories (recursively) that are located on the source host in the migration
export directory <EXPDIR> from the source host to the target host.
You can choose one of the following methods:
■ Use the migration monitor with the file transfer protocol (FTP) copy option.
NOTE
Make sure that you use binary mode for transferring the files.
■ 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 (network
share).
3. Check the permissions of the transferred files on the target host. All files have to be accessible for
user <sapsid>adm of the target system.
NOTE
If your source system is a distributed system, the files created by the export of the central instance
and the files created by the export of the database instance have to be located in the same
<EXPDIR> directory for the installation of the target system.
If you have not exported into the same <EXPDIR> already, then you have to merge the two
<EXPDIR> directories from the central instance export and from the database instance export
before starting the target system installation.
Make sure you use the SOURCE.PROPERTIES file from the central instance export when merging
the two export folders.
4.6.2 Installing the Target System
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: <DRIVE>:\<EXPDIR>\DB\<DATABASE>
UNIX, IBM i: <EXPDIR>/DB/<DATABASE>
4 Database Independent System Copy
4.6 Setting Up the Target System
48/120 PUBLIC 2012-04-12
![Page 49: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/49.jpg)
NOTE
As of SAP NetWeaver 7.0, RELOAD is no longer available as an executable installation service, but is
performed automatically by SAPinst. 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.
Procedure
1. Prepare the target system host as described in the installation guide for your SAP system.
Only valid for: IBM DB2 for Linux and UNIX and Windows |
NOTE
Make sure that you read the information provided in section Setup of Database Layout in the
installation documentation.
End of: IBM DB2 for Linux and UNIX and Windows |
2. Start SAPinst as described in the installation guide for your SAP system.
CAUTION
If 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 on the SAP
Service Marketplace.
3. On the Welcome screen, navigate to the following folder according to the requirements of your
target system: <SAP Product> Software Life-Cycle Options System Copy <Database> Target System
Installation <System Variant> Based on <Technical Stack> .
4. Run the installation services required for your system copy in the sequence they are listed in the
specific folder and according to process flow in Setting Up the Target System Using SAPinst [page 46].
5. To install the target system, follow the instructions in the SAPinst input dialogs and enter the
required parameters.
■ 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 > Default Settings screen.
■ On the SAP System > General Parameters screen, as default, the Unicode System option is selected.
You can only deselect this option if you perform the system copy for a non-Unicode SAP
system that has been upgraded to SAP NetWeaver 7.0 EHP 2.
■ On the SAP System > Database screen, choose the option Standard System Copy/Migration (load-
based):
The SAP data dump from the MIGRATION EXPORT CD image that you created during the export
is loaded in the newly installed SAP system database.
■ When SAPinst displays the DVD / CD browser window and asks for the Export Migration CD,
enter the path to the export directory <EXPDIR>.
■ If you perform a heterogeneous system copy, enter the migration key on the SAP System >
Database Import screen.
4 Database Independent System Copy
4.6 Setting Up the Target System
2012-04-12 PUBLIC 49/120
![Page 50: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/50.jpg)
■ 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.
CAUTION
Only valid for: IBM DB2 for Linux and UNIX and Windows |
■ Make sure that you take the information about automatic storage that is provided in the
Running SAPinst section in the appropriate installation guide into consideration.
■ The option Deferred Table Creation is not supported for load-based system copies for SAP
systems that are not based on SAP NetWeaver 7.0 EHP 1 or higher.End of: IBM DB2 for Linux and UNIX and Windows |
■ Do not create the installation directory (for example, sapinst_instdir) under the
following directories:
● UNIX, IBM i: /usr/sap/<SAPSID>
Windows: \usr\sap\<SAPSID>
● UNIX, IBM i: /sapmnt/<SAPSID>
Windows: \sapmnt\<SAPSID>
■ 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 DYNPSOURCE table 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. Complete the installation as described in the installation documentation for your SAP component.
NOTE
If 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 45].
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
Migration Checker, see the Migration Checker User Guide contained in the MIGMON.SAR archive
on your Installation Master DVD.
4 Database Independent System Copy
4.6 Setting Up the Target System
50/120 PUBLIC 2012-04-12
![Page 51: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/51.jpg)
5 Database-Specific System Copy
The following sections describe database-specific methods for the homogeneous system copy. Database-
specific methods are not available for all database systems. For more information about methods
available for your database, see Planning [page 11] and the SAP Notes describing the homogeneous system
copy for your database system.
Process
Follow the sequence of steps described in the process flows below for a:
■ Central System
■ Distributed System
■ High Availability System
Central System
To perform the export for a central system, you need to proceed as follows on the central system host:
Process Flow on the Source System (Export)
1. Generate the control file structure for the target database [page 54].
2. If required, create an offline backup of the source database [page 58].
Process Flow on the Target System
1. Only valid for: Windows |
Install the database software as described in the installation guide of your SAP solution.End of: Windows |
2. Only valid for: UNIX |
Prepare the target system [page 59]:
1. Follow the instructions on the SAPinst screens until SAPinst requests you to install the database
software and to perform the database backup/restore.
CAUTION
Make sure that you create the secure store of the target system using the same key phrase
as of the source system. Otherwise, the UME service can not be started.
2. Create the database file system (if it does not yet exist).
3. 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.
5 Database-Specific System Copy
2012-04-12 PUBLIC 51/120
![Page 52: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/52.jpg)
CAUTION
Make sure that you create the secure store of the target system using the same key phrase as
of the source system. Otherwise, the UME service can not be started.
NOTE
If required, 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 75].
Distributed System or High Availability System
To 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, generate the control file structure for the target
database [page 54].
2. If required, on the database instance host, create an offline backup of the source database [page 58].
Process Flow on the Target System
1. Only valid for: Windows |
On the database instance host, install the database software as described in the installation guide
of your SAP solution.End of: Windows |
2. Only valid for: UNIX |
Prepare the target system [page 59]:
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, create the database file system (if not yet existing).
3. On the database instance host, 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.
NOTE
If required, 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 75].
Only valid for: Oracle |
5.1 Oracle-Specific Procedure
Purpose
In 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
5 Database-Specific System Copy
5.1 Oracle-Specific Procedure
52/120 PUBLIC 2012-04-12
![Page 53: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/53.jpg)
the copy is a complete data backup of your source database. You can use an offline backup, an online
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
content are different.
Advantages
■ You can use existing offline or online backups.
■ This method is faster than the R3load and Jload method.
Disadvantages
■ Backup/copy of database files in a heterogeneous environment is not possible because the hardware
of the source and target systems must be binary-compatible.
■ Source system host and target system host must be different.
■ You must shut down the SAP system and the database when you create an offline backup manually
or an offline backup with BR*Tools.
■ You cannot change the database schema and the table space names.
Prerequisites
■ You must use the same Oracle release and patch level for your database in the source and target
system.
■ You must have installed the Java Runtime Environment [page 20].
■ The classes12.jar must exist in the <ORACLE_HOME>/jdbc/lib directory (installed using a
standard Oracle installation).
■ If your source system is an ABAP only system, make sure that JRE version 1.4.1 or higher is installed
on the database instance.
■ The JAVA_HOME environment variable must point the JRE directory.
■ For security reasons, the source and target systems must run on different hosts.
■ The source and target systems must be binary compatible.
NOTE
Note that you can also perform a system copy from 32-bit systems to 64-bit systems and vice
versa (same operating system assumed) even if source and target system are not binary
compatible.
If your source system uses the US7ASCII character set, you must choose this character set when
installing the target system. SAPinst prompts for the character set during the installation (key: Database
Character Set). The installation default is WE8DEC or UTF8 for Unicode systems. To find out the
character set used by the source system, connect to the source database as user sap<schemaid> or
sapr3 with sqlplus and enter: SELECT * FROM V$NLS_PARAMETERS;
5 Database-Specific System Copy
5.1 Oracle-Specific Procedure
2012-04-12 PUBLIC 53/120
![Page 54: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/54.jpg)
5.1.1 Generating the Control File Structure
The OraBRCopy Java tool writes a file CONTROL.SQL to the current working directory, which can be used
without further adaptations on the target system.
For more information about the OraBRCopy tool, see the documentation ORABRCopy.pdf, which is part
of the OraBRCOPY.SAR archive.
Prerequisites
RECOMMENDATION
We recommend that you shut down the SAP system before you perform the following steps. The
database must still be running.
Procedure
1. Create an installation directory <INSTDIR> (UNIX: with permissions 777) on the source system.
2. Copy the ORABRCOPY.SAR archive from the SAP Installation Master DVD to the installation directory
and extract it using SAPCAR.
You can find the archive in the following directory on the Installation Master DVD:
Only valid for: UNIX |
<DVD-DIR>:/COMMON/INSTALL/ORA/ORABRCOPY.SAR
End of: UNIX |
Only valid for: Windows |
<DVD-DRIVE>:\COMMON\INSTALL\ORA\ORABRCOPY.SAR
End of: Windows |
3. Make sure that all redo log groups are archived
4. Start the OraBRCopy tool as an OS user with Oracle DBA privileges:
user ora<dbsid>
user <sapsid>adm
■ If you perform an offline manual copy, enter the following commands:
● On UNIX:
./ora_br_copy.sh –generateFiles –forceLogSwitches —targetSid
<TARGET_DBSID> —password <system's password> —listenerPort <listener port>
● On Windows:
ora_br_copy.bat –generateFiles –forceLogSwitches —targetSid <TARGET_DBSID>
—password <system's password> —listenerPort <listener port>
The tool creates the files CONTROL.SQL, CONTROL.TRC and init<targetSID>.ora in your
installation directory, shuts down and restarts the database and performs the required log
switches.
■ If you perform an offline or online backup using BR*Tools, enter the following commands:
● On UNIX:
5 Database-Specific System Copy
5.1 Oracle-Specific Procedure
54/120 PUBLIC 2012-04-12
![Page 55: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/55.jpg)
./ora_br_copy.sh –generateFiles —targetSid <TARGET_DBSID> —password
<system's password> —listenerPort <listener port>
● On Windows:
ora_br_copy.bat –generateFiles —targetSid <TARGET_DBSID> —password
<system's password> —listenerPort <listener port>
NOTE
During the online backup, the database must be up and running. To ensure this, this
command must not contain the parameter —forceLogSwitches.
The tool creates the files CONTROL.SQL, CONTROL.TRC and init<targetSID>.ora in your
installation directory, and performs the required log switches.
NOTE
If an error occurs, check the log file:
<INSTDIR>/ora.brcopy.log
5. Verify and, if necessary, update the CONTROL.SQL control file using the CONTROL.TRC trace file as
follows.
Example for Windows
In the following example for Windows, entries of CONTROL.SQL written in bold should be compared
and changed according to the trace file:
REM
====================================================================
REM CONTROL.SQL
REM
REM SAP AG Walldorf
REM Systeme, Anwendungen und Produkte in der Datenverarbeitung
REM
REM (C) Copyright SAP AG 2004
REM
====================================================================
REM Generated at:
REM Fri Sep 17 08:33:25 CEST 2005
REM for target system NEW
REM on
REM Windows 2000 5.0 x86
CONNECT / AS SYSDBA
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE
SET DATABASE "NEW"
5 Database-Specific System Copy
5.1 Oracle-Specific Procedure
2012-04-12 PUBLIC 55/120
![Page 56: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/56.jpg)
RESETLOGS
ARCHIVELOG
MAXLOGFILES 255
MAXLOGMEMBERS 3
MAXDATAFILES 1022
MAXINSTANCES 50
MAXLOGHISTORY 1134
LOGFILE
GROUP 1 (
'D:\ORACLE\NEW\ORIGLOGA\LOG_G11M1.DBF',
'D:\ORACLE\NEW\MIRRLOGA\LOG_G11M2.DBF'
) SIZE 50M,
GROUP 2 (
'D:\ORACLE\NEW\ORIGLOGB\LOG_G12M1.DBF',
'D:\ORACLE\NEW\MIRRLOGB\LOG_G12M2.DBF'
) SIZE 50M,
GROUP 3 (
'D:\ORACLE\NEW\ORIGLOGA\LOG_G13M1.DBF',
'D:\ORACLE\NEW\MIRRLOGA\LOG_G13M2.DBF'
) SIZE 50M,
GROUP 4 (
'D:\ORACLE\NEW\ORIGLOGB\LOG_G14M1.DBF',
'D:\ORACLE\NEW\MIRRLOGB\LOG_G14M2.DBF'
) SIZE 50M
DATAFILE
'D:\ORACLE\NEW\SAPDATA1\SYSTEM_1\SYSTEM.DATA1',
'D:\ORACLE\NEW\SAPDATA3\IMS_1\IMS.DATA1',
'D:\ORACLE\NEW\SAPDATA3\IMS_2\IMS.DATA2',
'D:\ORACLE\NEW\SAPDATA3\IMS_3\IMS.DATA3',
'D:\ORACLE\NEW\SAPDATA3\IMS_4\IMS.DATA4',
'D:\ORACLE\NEW\SAPDATA4\IMS_5\IMS.DATA5',
'D:\ORACLE\NEW\SAPDATA4\IMS_6\IMS.DATA6',
'D:\ORACLE\NEW\SAPDATA4\IMS_7\IMS.DATA7',
'D:\ORACLE\NEW\SAPDATA4\IMS_8\IMS.DATA8',
'D:\ORACLE\NEW\SAPDATA4\IMS_9\IMS.DATA9',
'D:\ORACLE\NEW\SAPDATA1\IMS700_1\IMS700.DATA1',
'D:\ORACLE\NEW\SAPDATA1\IMS700_2\IMS700.DATA2',
'D:\ORACLE\NEW\SAPDATA1\IMS700_3\IMS700.DATA3',
5 Database-Specific System Copy
5.1 Oracle-Specific Procedure
56/120 PUBLIC 2012-04-12
![Page 57: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/57.jpg)
'D:\ORACLE\NEW\SAPDATA1\IMS700_4\IMS700.DATA4',
'D:\ORACLE\NEW\SAPDATA2\IMS700_5\IMS700.DATA5',
'D:\ORACLE\NEW\SAPDATA2\IMS700_6\IMS700.DATA6',
'D:\ORACLE\NEW\SAPDATA2\IMS700_7\IMS700.DATA7',
'D:\ORACLE\NEW\SAPDATA2\IMS700_8\IMS700.DATA8',
'D:\ORACLE\NEW\SAPDATA2\IMS700_9\IMS700.DATA9',
'D:\ORACLE\NEW\SAPDATA3\IMS700_10\IMS700.DATA10',
'D:\ORACLE\NEW\SAPDATA4\IMS700_11\IMS700.DATA11',
'D:\ORACLE\NEW\SAPDATA1\IMSUSR_1\IMSUSR.DATA1',
'D:\ORACLE\NEW\SAPDATA2\ROLL_1\ROLL.DATA1'
;
ALTER DATABASE OPEN RESETLOGS;
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE
'D:\ORACLE\NEW\SAPDATA3\TEMP_1\TEMP.DATA1'
SIZE 350M REUSE AUTOEXTEND OFF;
NOTE
In the above example for Windows, entries and values of CONTROL.SQL written in bold should be
compared to the trace file. The changes to be made are valid for UNIX, too.
Changes to be made
1. If you want to migrate your database from 32-bit to 64-bit or vice versa, add the following lines at
the bottom of the CONTROL.SQL file:
shutdown immediate
startup upgrade
spool utlirp.log
@?/rdbms/admin/utlirp.sql
spool off
shutdown immediate
startup
spool utlrp.log
@?/rdbms/admin/utlrp.sql
spool off
exit
2. MAXLOGFILES 255
...
The numbers must be greater than or equal to the corresponding numbers in the trace file.
3. GROUP 1 (
'D:\ORACLE\NEW\ORIGLOGA\LOG_G11M1.DBF',
5 Database-Specific System Copy
5.1 Oracle-Specific Procedure
2012-04-12 PUBLIC 57/120
![Page 58: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/58.jpg)
'D:\ORACLE\NEW\MIRRLOGA\LOG_G11M2.DBF'
) SIZE 50M,
Group 2 (
…
The sizes of the respective groups must be equal to the sizes of the corresponding groups in the
trace file.
4. 'D:\ORACLE\NEW\SAPDATA1\SYSTEM_1\SYSTEM.DATA1',
'D:\ORACLE\NEW\SAPDATA3\IMS_1\IMS.DATA1',
…
'D:\ORACLE\NEW\SAPDATA1\IMS700_1\IMS700.DATA1'
…
The count of the data files must be equal to the count of the corresponding data files in the trace
file.
5. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE
'D:\ORACLE\NEW\SAPDATA3\TEMP_1\TEMP.DATA1'
SIZE 350M REUSE AUTOEXTEND OFF;
…
The size must be equal to the corresponding size in the trace file.
6. The number of rows with ALTER TABLESPACE must be equal to the number of corresponding rows
in the trace file.
5.1.2 Creating a Backup
Create a backup if required. Choose between the following possibilities: Performing an offline backup
manually or an offline or online backup with BR*Tools.
■ Creating an Offline Backup [page 58]
■ Creating an Offline or Online Backup with BR*Tools [page 59]
5.1.2.1 Creating an Offline Backup Manually
Procedure
There are different possibilities to prepare the actual transfer of the database files:
■ If you have an up-to-date offline backup, you can use it (provided that redo logs were cleaned
up with forced log switches).
■ If you want to transport the database file (for example, on tape) or if you have to perform the
database shutdown at a certain time, stop the database (normal shutdown) and perform a complete
offline backup. You can use the trace file CONTROL.TRC created by OraBrCOPY to determine the file
system trees that have to be saved.
5 Database-Specific System Copy
5.1 Oracle-Specific Procedure
58/120 PUBLIC 2012-04-12
![Page 59: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/59.jpg)
■ You stop the database (normal shutdown) and copy the database files when the actual transfer to
the target system takes place. You do not have to perform any preparations for the actual transfer
now. Proceed with the next step.
NOTE
If you choose this manual offline backup method, you also have to restore the database files on
the target system manually. For more information, see Restoring Database Files on the Target System
Manually [page 62].
5.1.2.2 Creating an Offline or Online Backup with BR*Tools
You can use any backup strategy supported by BR*Tools as the basis for a system copy: offline or online,
with or without BACKINT, with or without RMAN, complete or incremental, and so on. The backup
strategy must simply be valid for restore and recovery. This means that a complete restore and recovery
of the source database must be possible. In addition for BACKINT and RMAN, the external backup
tools must be configured so that a restore is possible on the target host.
ProcedureProceed as described in the SAP Library at:
help.sap.com/nw70 SAP NetWeaver 7.0 including Enhancement Package 2 SAP NetWeaver 7.0 Library
(including Enhancement Package 2) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution
Life Cycle Management by Key Capability General Administration Tasks Database Administration Database
Administration for Oracle SAP Database Guide: Oracle BR*Tools for Oracle DBA BR*Tools in Action Backup
and Database Copy with BR*Tools .
NOTE
If you choose a backup method with BR*Tools. you also have to restore the database files on the
target system with BR*Tools. For more information, see Restoring the Database Files on the Target System
with BR*Tools [page 63].
5.1.3 Preparing the Target System
PrerequisitesMake sure that sapdata<n> file systems on the target system host are large enough.
Procedure1. Install the target SAP system with SAPinst as described in the installation documentation for your
SAP solution.
CAUTION
When you perform a system copy with the Oracle backup/restore method, you cannot change
the database schema and the table space names of the new target system. When installing the
5 Database-Specific System Copy
5.1 Oracle-Specific Procedure
2012-04-12 PUBLIC 59/120
![Page 60: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/60.jpg)
target central instance, database instance, or dialog instance make sure that you enter the
correct database schema names (which are the database schema name of the source system).
The schema names of the source and target system must be identical.
1. On the Welcome screen, choose <SAP Product> Software Life-Cycle Options System Copy Target
System Installation <System Variant> .
2. When SAPinst prompts for the installation type, choose Homogeneous System Copy (Backup/
Restore).
3. Proceed until SAPinst stops to restore the database files on the target system.
The following message is displayed:
SAPinst now stops the installation. Please proceed as follows:...
2. Only valid for: UNIX |
If necessary, extract the Oracle stage archives manually and install the Oracle Software as described
in the installation documentation for your SAP solution.End of: UNIX |
3. If they do not exist, create the following directories on the target system:
■ Only valid for: UNIX |
UNIX:
● /oracle/<TARGET_DBSID>/mirrlog<x>
● /oracle/<TARGET_DBSID>/origlog<x>
● /oracle/<TARGET_DBSID>/sapdata<x>
● /oracle/<TARGET_DBSID>/sapreorg
● /oracle/<TARGET_DBSID>/saparch
● /oracle/<TARGET_DBSID>/oraarch
● /oracle/<TARGET_DBSID>/saptrace
● /oracle/<TARGET_DBSID>/saptrace/background
● /oracle/<TARGET_DBSID>/saptrace/usertrace
● /oracle/<TARGET_DBSID>/origlogA/cntrl
● /oracle/<TARGET_DBSID>/sapdata1/cntrl
● /oracle/<TARGET_DBSID>/saparch/cntrl
● /oracle/<TARGET_DBSID>/sapcheck
End of: UNIX |
■ Only valid for: Windows |
Windows:
● <drive>:\oracle\<TARGET_DBSID>\mirrlog<x>
● <drive>:\oracle\<TARGET_DBSID>\origlog<x>
● <drive>:\oracle\<TARGET_DBSID>\sapdata<x>
● <drive>:\oracle\<TARGET_DBSID>\sapreorg
● <drive>:\oracle\<TARGET_DBSID>\saparch
● <drive>:\oracle\<TARGET_DBSID>\oraarch
5 Database-Specific System Copy
5.1 Oracle-Specific Procedure
60/120 PUBLIC 2012-04-12
![Page 61: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/61.jpg)
● <drive>:\oracle\<TARGET_DBSID>\saptrace
● <drive>:\oracle\<TARGET_DBSID>\saptrace\background
● <drive>:\oracle\<TARGET_DBSID>\saptrace\usertrace
● <drive>:\oracle\<TARGET_DBSID>\origlogA\cntrl
● <drive>:\oracle\<TARGET_DBSID>\sapdata1\cntrl
● <drive>:\oracle\<TARGET_DBSID>\saparch\cntrl
● <drive>:\oracle\<TARGET_DBSID>\sapcheck
End of: Windows |
4. Make sure that the following directories are empty (except the subdirectory saparch/cntrl):
Only valid for: UNIX |
■ /oracle/<TARGET_DBSID>/saparch
■ /oracle/<TARGET_DBSID>/oraarch
End of: UNIX |
Only valid for: Windows |
■ <drive>:\oracle\<TARGET_DBSID>\saparch
■ <drive>:\oracle\<TARGET_DBSID>\oraarch
End of: Windows |
5. Only valid for: UNIX |
All directories must be owned by the user ora<target_dbsid>.
To achieve this, enter the following command:
chown ora<target_dbsid>:dba <directory>
End of: UNIX |
6. Only valid for: Windows |
Set the security settings for the built-in accounts and groups SYSTEM, Administrators,
SAP_<SAPSID>_GlobalAdmin (domain installation), and SAP_<SAPSID>_LocalAdmin (local
installation) for all directories as follows:
1. In the Windows Explorer, right-click the Oracle root directory and choose Properties.
2. Under Security, choose Advanced.
3. Deselect Allow inheritable permissions from the parent....
4. In the next dialog, choose Copy to copy the permission entries that were previously applied
from the parent to this object.
5. Choose OK.
6. Set the permissions for the above-mentioned accounts SYSTEM, Administrators,
SAP_<DBSID>_GlobalAdmin, or SAP_<DBSID>_LocalAdmin to Full Control.
7. Delete all other accounts.End of: Windows |
7. Restore the database files on the target system either manually (see Restoring Database Files on the Target
System Manually [page 62]) or with BR*Tools (see Restoring the Database Files on the Target System with
BR*Tools [page 63]), then proceed with SAPinst.
5 Database-Specific System Copy
5.1 Oracle-Specific Procedure
2012-04-12 PUBLIC 61/120
![Page 62: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/62.jpg)
5.1.4 Restoring Database Files on the Target System
CAUTION
If you do not use an offline backup, but copy the database files directly from the source to the
target system host, make sure that you shut down the database on the source system before you
copy the listed files from the source to the target directories.
Procedure
1. Copy the following files from the source to the target system host by copying the listed files from
the source directories to the target directories. For more information, see Creating an Offline Backup
Manually [page 58].
Only valid for: UNIX |
Directories on UNIX
Source and Target Directory Files
/oracle/<DBSID>/sapdata<x> All files
/oracle/<DBSID>/origlog<x> All files
/oracle/<DBSID>/mirrlog<x> All files
Source: <INSTDIR> Target: <SAPINST_INSTDIR>
CONTROL.SQL
Source: <INSTDIR> Target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/dbs
init<TARGET_DBSID>.ora
End of: UNIX |
Only valid for: Windows |
Source and Target Directory Files
<drive>:\oracle\<DBSID>\sapdata<x> All files
<drive>:\oracle\<DBSID>\origlog<x> All files
<drive>:\oracle\<DBSID>\mirrlog<x> All files
Source: <INSTDIR> Target: <SAPINST_INSTDIR>
CONTROL.SQL
Source: <INSTDIR> Target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database
init<TARGET_DBSID>.ora
End of: Windows |
Only valid for: Windows |
NOTE
If you use an existing offline backup, the source data files and log files are not located in the
directories shown in the table.
The installation directory of the target system is normally located in the directory:
%programfiles%\sapinst_instdir\NW04S\LM\COPY\ORACLE\SYSTEM\<system_variant>
End of: Windows |
5 Database-Specific System Copy
5.1 Oracle-Specific Procedure
62/120 PUBLIC 2012-04-12
![Page 63: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/63.jpg)
2. After you have copied the database files, make sure that the files on the source and target system
are not located in different directories or drives. If required, make the corresponding changes in
the files control.sql and the init<DBSID>.ora.
3. Verify that the created directories and copied files have the owner ora<target_dbsid>, belong to
the group dba, and have the permissions 740.
4. Make sure that the control files are not restored. If necessary, remove them.
The file names are specified by the control_files parameter of the init<TARGET_DBSID>.ora file.
5.1.5 Restoring the Database Files on the Target System with BR*Tools
Procedure
1. Copy the following files from the source system host to the target system host by copying manually
the listed files from the source directories to the target directories.
Only valid for: UNIX |
Source and Target Directories on UNIX
Source and Target Directory Files
Source: <INSTDIR> Target: <SAPINST_INSTDIR>
CONTROL.SQL
Source: <INSTDIR> Target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/dbs
init<TARGET_DBSID>.ora
End of: UNIX |
Only valid for: Windows |
Source and Target Directories on Windows
Source and Target Directory Files
Source: <INSTDIR> Target: <SAPINST_INSTDIR>
CONTROL.SQL
Source: <INSTDIR> Target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database
init<TARGET_DBSID>.ora
End of: Windows |
2. Create an Oracle spfile from init<TARGET_DBSID>.ora profile as follows:
SYNTAX
sqlplus /nologconnect / as sysdbacreate spfile from pfile;exit
3. Call the restore and recovery function of BR*Tools.
For more information about the required steps and prerequisites, see SAP Note 1003028.
5 Database-Specific System Copy
5.1 Oracle-Specific Procedure
2012-04-12 PUBLIC 63/120
![Page 64: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/64.jpg)
The main prerequisite is that the corresponding BR*Tools logs (BRBACKUP detailed and summary
log, BRARCHIVE summary log) are copied manually from the source to the target system. In addition,
the postprocessing steps mentioned in this SAP Note are performed automatically by SAPinst.
SAP Note 1003028 also comprises information about executing restore and recovery under the
control of BRRECOVER and the exact syntax of BRRECOVER (see section Homogeneous Database Copy).
For more information about BR*Tools, see the SAP Library at:
help.sap.com/nw70 SAP NetWeaver 7.0 including Enhancement Package 2 SAP NetWeaver 7.0 Library
(including Enhancement Package 2) Englishh SAP NetWeaver Library SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability General Administration Tasks Database Administration
Database Administration for Oracle BR*Tools for Oracle DBA .
4. Shut down the Oracle database instance as follows:
SYNTAX
sqlplus /nologconnect / as sysdbashutdown immediateexit
End of: Oracle |
Only valid for: MaxDB |
5.2 SAP MaxDB-Specific Procedure
In an SAP system environment, you can create a homogeneous copy of an SAP MaxDB database by
using the backup and restore method. This method is suitable for creating an exact copy of an existing
database. The source of the copy is a complete data backup of your source database.
The SAPinst tool is used for the installation on the target system host as described in the installation
documentation for your SAP solution. In SAPinst, you select the backup and restore method as the
database installation method.
This description is not valid for the liveCache system copy.
CAUTION
Make sure that you know the password of the database system administrator (SUPERDBA) from
the source system before you start the procedure below. Otherwise, you cannot access the
database contents on the target system.
You must also know the name of the SQL database schema on the source system, SAP<SAPSID>
— for example, SAPR3.
You can perform this procedure in the following ways:
■ Manual restore
5 Database-Specific System Copy
5.2 SAP MaxDB-Specific Procedure
64/120 PUBLIC 2012-04-12
![Page 65: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/65.jpg)
SAPinst stops before the database instance initialization and asks you to perform the restore on the
target database. After you have performed restore and post-restore activities, you can continue the
installation in SAPinst.
■ Automatic restore
SAPinst performs the restore to import the data into the target system.
In this scenario, you have to use a single file as the backup medium for the whole backup. The
restore can use any SAP MaxDB backup, as long as it is a single file.
NOTE
The minimum size of the database is calculated from the size of the backup file.
Advantages
■ You can use existing offline backups.
■ This method is faster than the database-independent method using R3load or Jload [page 23].
Disadvantage
You can only copy between systems with the same byte order.
Prerequisites
■ Byte order – little-endian or big-endian
You can use the backup and restore method to copy systems with the same byte order. That is,
you can copy a system based on little-endian to another system based on little-endian. You can
also copy a system based on big-endian to another system based on big-endian. Check SAP Note
552464 to find out which processor and operating system combination uses which byte order.
■ Data backup
You perform the complete data backup of your source database.
■ Recovery tool
You are using the SAP MaxDB Database Manager (DBMGUI) version 7.5.0 Build 12 or above. For
more information, see:
http://maxdb.sap.com/currentdoc/default.htm Tools Database Manager GUI
■ Database Software
The database software on the target host must have the same version as the software on the source
host. The build number of the software version on the target host must be greater than or equal
to the version on the source host.
■ Size of the data on the target system
The size of the target system must be greater than the used space on the source system. You can
find the size of the used pages on the source system as follows:
dbmcli —d <database_name> —u <dbm_user>,<password> —n <database_server> —u SQL
sap<sid>,<password> sql_execute 'SELECT USEDPERM FROM SERVERDBSTATISTICS'
5 Database-Specific System Copy
5.2 SAP MaxDB-Specific Procedure
2012-04-12 PUBLIC 65/120
![Page 66: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/66.jpg)
The result of this query is the amount of used space, expressed as the number of 8 KB pages. To
calculate the used space in MB, divide this value by 128. When SAPinst prompts you, configure the
database data volumes according to this value.
■ JRE
You must have installed JRE version 1.5 or higher on your system.
The JAVA_HOME environment variable must point to the JRE directory.
Process
Steps to Perform on the Target System
1. To import the target system, start SAPinst as follows and then follow the prompts:
<SAP Product> Software Life-Cyle Options System Copy Target System Installation <System
Variant>
2. In the Select the database copy method screen, select Homogeneous System Copy.
3. In the MaxDB Backup Template screen, choose one of the following, Manual Restore, or Restore by
SAPinst:
■ Manual restore
In the execution phase, you are prompted to do the following:
1. Start the data recovery wizard from DBMGUI
1. Register your database instance in the DBMGUI
2. Check the database instance in the admin state.
3. Choose Recovery Recovery with Initialization ...
4. In type of recovery, select Restore a medium.
5. Specify the backup medium.
6. Start the restore procedure.
NOTE
The recovery wizard does not start the recovery immediately. It initializes the
database instance first. It takes some time for the database server to format the
database volumes.
2. After the restore, check the state of the target database instance. Change the database state
to online if it is not already in online state.
3. Delete the entries from the following tables to make sure that information about the
backup history for update statistics in the Computing Center Management System
(CCMS) from the old system does not appear in the new system:
CNHIST, CNREPRT, CNMEDIA, DBSTATHADA, DBSTAIHADA, DBSTATIADA, DBSTATTADA,
SDBAADAUPD
4. Continue with SAPinst or restart it if you stopped it during the recovery.
■ Restore by SAPinst
Enter the following information:
5 Database-Specific System Copy
5.2 SAP MaxDB-Specific Procedure
66/120 PUBLIC 2012-04-12
![Page 67: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/67.jpg)
● Template name
● Device/file
● Wait for backup
4. After installation is completed, maintain the database connection for CCMS.
For more information, see SAP Note 588515.End of: MaxDB |
Only valid for: Windows | MS SQL Server |
5.3 MS SQL Server-Specific Procedure
This section describes how to perform a homogeneous system copy of an MS SQL Server database by
using the backup/restore method, or the detach/attach method in an SAP environment. The SAPinst
installation tool supports both methods.
The backup/restore method and the detach/attach method have the following advantages compared
to the R3load method:
■ You can use an existing backup.
■ These methods are much faster than the database-independent method [page 23].
NOTE
● For more information about the system copy procedure, see SAP Notes 193816 and
151603.
● With SQL Server, you can use backup images across the platforms I386, IA64, x64. That
is, you can make a backup on one type of platform and use it on another type.
● You can attach SQL Server 2000 files to SQL Server 2005 but not vice versa.
Process
1. Detach the database files from the source system database or create a backup and copy the files to
the target system.
2. Attach the database files or restore the backup of the source database on the target database server.
3. Run SAPinst to install the target system by choosing the following on the Welcome screen:
<SAP Product> Software Life-Cycle Options System Copy MS SQL Server Target System Installation
<System Variant> Based on <Technical Stack>
NOTE
■ The target system is installed using the exports from the source system.
■ Choose the installation services in exactly the order they appear. For more information,
see the MS SQL Server installation guide for your SAP system at http://
service.sap.com/installnw70.
■ On the SAPinst screen SAP SystemDatabase, make sure that you select Homogeneous System
Copy (MS SQL Server-specific: Detach/Attach or Backup).End of: Windows | MS SQL Server |
5 Database-Specific System Copy
5.3 MS SQL Server-Specific Procedure
2012-04-12 PUBLIC 67/120
![Page 68: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/68.jpg)
Only valid for: IBM DB2 for Linux and UNIX and Windows |
5.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures
The database-specific procedure for the creation of a system copy is based on a restore of an existing
online or offline backup. Therefore, this method is also referred to as backup/restore procedure. Since
a DB2 backup can be used cross-platform within certain limitations (see below), this method is not
limited to the homogenous system copy only.
An SAP system copy with a DB2 database can be also created if more advanced techniques like file system
snapshots are available. The necessary procedure in this case is called database relocation. The database
relocation procedure differs significantly from the backup/restore procedure and is not described in
this guide.
For more information, see the Database Administration Guide: SAP on IBM DB2 for Linux, UNIX, and Windows,
section db2inidb Option: as snapshot.
SAPinst is used for installation on the target system host as described in the installation documentation
for your SAP component. Before starting SAPinst on the target system make sure that all prerequisites
for the SAP system installation are met. Especially, make sure that the relevant file systems are available.
For more information, see the appropriate installation guide at http://service.sap.com/
installnw70 Installation – SAP NetWeaver Systems
In an ABAP system, only the SAPinst steps for setting up and loading the database are replaced by a
database restore.
Advantages of the Backup Method
■ You can use existing online and offline backups.
■ Using the backup method is faster than the database-independent method [page 23].
Disadvantages of the Backup Method
■ You cannot change the name of the database schema. The name of the database schema of the
target system is the same as that of the source system. This implies that the name of the database
connect user does not change either.
■ You cannot copy an individual MCOD component to another system. You can only copy the
complete system.
Prerequisites
■ It must be possible to restore the backup of the source system on the platform of the target system.
5 Database-Specific System Copy
5.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures
68/120 PUBLIC 2012-04-12
![Page 69: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/69.jpg)
NOTE
With DB2, you can use backup images cross-platform within certain limitations. If you want
to use the backup/restore method between different platforms, you must follow the
additional instructions in SAP Note 628156.
■ If errors occur when restoring the backup on the target system, the complete restore must be
repeated.
Process
1. You perform an online or offline backup.
NOTE
If you use an online backup to copy your system, a roll forward of your database is required
after the database restore on the target system. As a prerequisite, the respective database logs must
be accessible. We therefore recommend that you include the necessary log files in the backup image.
To do so, use the INCLUDE LOGS option of the BACKUP DATABASE command. Note that as of DB2
V9.5, logs are by default included in an online backup.
2. To create a target system, run SAPinst on the target system host by choosing the following on the
Welcome screen:
<SAP Product> Software Life-Cycle Options System Copy IBM DB2 for Linux, UNIX, and Windows
Target System Installation <System Variant> Based on <Technical Stack>
Perform the installation options in the given sequence and follow the instructions on the SAPinst
dialogs. SAPinst prompts you to perform the database restore during the installation phase.
CAUTION
Be aware of the following constraints when using the backup method for a homogeneous
system copy:
■ Since you cannot change the name of the database schema, you cannot change the
connect user either. During the dialog phase you have to make sure that you enter the
name of the connect user exactly as you did on your source system.
■ The tablespace names remain the same during the database restore. However, you can
change them after the installation.
■ If you want to change the name or the location of the DB2 container on the target system,
you have to adapt the DB2 container paths or names in the redirected restore script and
then perform a redirected restore. For more information, see the documentation Database
Administration Guide: SAP on IBM DB2 Universal Database for UNIX and Windows, section Usage of
Tool brdb6brt.
3. Multi-Partition Database Environments only: Add database partitions
If you copy a system with multiple database partitions, the target system must have the same
number of partitions as the source system.
4. Restore your database.
5 Database-Specific System Copy
5.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures
2012-04-12 PUBLIC 69/120
![Page 70: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/70.jpg)
To restore your database, you can choose between one of the following options:
■ Simple database restore
To perform a database restore, use the DB2 RESTORE command. For more information, see the
IBM DB2 documentation DB2 Command Reference.
NOTE
With a simple restore, you cannot change the name or the location of DB2 containers.
■ Redirected restore
This is the recommended method.
A redirected restore allows you to change the name or the location of the DB2 container. To
perform a redirected restore, you use the DB2 RESTORE DATABASE command with the REDIRECT
GENERATE SCRIPT option.
Alternatively, you can use the tool brdb6brt that retrieves a database backup and creates a
CLP script to restore this backup image. Since brdb6brt needs to connect to the source system,
the source system must be available. For more information about how to use the tool
brdb6brt, see Redirected Restore Using brdb6brt in the Database Administration Guide: SAP on IBM DB2
Universal Database for UNIX and Windows.
If you have used an online backup, you have to make sure that you have access to the log files that
were created during the online backup. You also have to perform a roll forward operation to bring
the database into a consistent state.
You can now continue with the installation.
5. To adhere to the SAP standard naming conventions for tablespaces, we recommend that you
consider renaming the tablespaces after the installation to reflect the new system name. To rename
a single tablespace, enter the following command:
db2 rename tablespace <old name> to <new name>
EXAMPLE
db2 rename tablespace <SAPSID_SOURCE>#STABD to <SAPSID_TARGET>#STABD
If you use the deferred table creation function, you also have to execute the following command
for each renamed tablespace using the db6util tool:
db6util -rtvt <old tbs> <new tbs>
For more information, see SAP Note 1227165.
CAUTION
Make sure that you use an up-to-date version of the db6util tool. You require at least a
version that supports the option -rtvt. To check the command options of the db6util tool,
enter the following command:
db6util –h
5 Database-Specific System Copy
5.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures
70/120 PUBLIC 2012-04-12
![Page 71: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/71.jpg)
In addition, you have to update the tablespace names in tables TSDB6, IADB6, and TADB6. To
rename all tablespaces in the respective tables according to the standard naming conventions, use
the following commands:
■ For table TSDB6, enter the following SQL command:
update <connect_user_name>.tsdb6 set tabspace = '<SAPSID_TARGET>#'||substr
(tabspace,5,length(tabspace)-4), indspace='<SAPSID_TARGET>#'||substr(indspace,
5,length(indspace)-4)
■ For table IADB6, enter the following SQL command:
update <connect_user_name>.iadb6 set tabspace = '<SAPSID_TARGET>#'||substr
(tabspace,5,length(tabspace)-4)
■ For table TADB6, enter the following SQL command:
update <connect_user_name>.tadb6 set tabspace = '<SAPSID_TARGET>#'||substr
(tabspace,5,length(tabspace)-4)
Follow-up Activities
After the installation on the target system, you perform the following steps:
■ The tablespaces SYSTOOLSPACE and SYSTOOLSTMPSPACE are used by certain DB2 tools and SQL
administrative routines to store historical and configuration information. We recommend that
you drop and re-create these tablespaces in the target system as follows:
1. Log on to the database server of the target system as user db2<dbsid>.
2. Generate the DDL statements for the tablespaces of the system by entering the following
command on the DB2 command line:
db2look -d <DBSID> -l -o <filename>.sql
3. Drop both tablespaces by entering the following command:
db2 drop tablespace SYSTOOLSPACE, SYSTOOLTMPSPACE
4. Look up the CREATE TABLESPACE statements for SYSTOOLSPACE and SYSTOOLSTMPSPACE in
<filename>.sql.
5. Execute both statements on the DB2 command line.
■ If you performed a redirected restore, check all settings of the database manager and database
configuration parameters. Specifically, make sure that the following configuration parameters
point to the correct path:
● DIAGPATH (DBM)
● JDK_PATH (DBM)
● DFTDBPATH (DBM)
● Path to log files (DB)
● If set, NEWLOGPATH (DB), OVERFLOWLOGPATH (DB), FAILARCHPATH (DB) and MIRRORLOGPATH (DB)End of: IBM DB2 for Linux and UNIX and Windows |
5 Database-Specific System Copy
5.4 IBM DB2 for Linux, UNIX, and Windows-Specific Procedures
2012-04-12 PUBLIC 71/120
![Page 72: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/72.jpg)
Only valid for: IBM DB2 for i5/OS |
5.5 IBM DB2 for i Procedure
In an SAP system environment, you can create a homogeneous system copy of a DB2 database using
the SAV/RSTLIB system copy method.
Advantage of the Offline System Copy Method
This method is faster than the database-independent method [page 23].
For more information, see SAP Note 585277.
CAUTION
You can only copy for IBM DB2 for i.
End of: IBM DB2 for i5/OS |
5.6 IBM DB2 for z/OS Specific Procedure
In an SAP system environment, you can create a homogeneous system copy of a DB2 database using
the offline system copy method.
More Information
For more information about this system copy procedure, see the PDF file that is attached to SAP
Note 680746. The guide contains all the information necessary to carry out a system copy with DB2
tools.
5.7 Sybase ASE Server-Specific Procedure
This section describes how to perform a homogeneous system copy of a Sybase ASE database by using
the backup/restore method, or the detach/attach method in an SAP environment. The SAPinst
installation tool supports both methods.
The backup/restore method and the detach/attach method have the following advantages compared
to the R3load method:
■ You can use an existing backup.
■ You can copy the complete database software and database devices (all files below <drive>:\sybase
\<DBSID> (Windows) or /sybase/<DBSID> (UNIX)) to the target system and use this copy to create
the target system.
■ These methods are faster than the database-independent method [page 23].
5 Database-Specific System Copy
5.5 IBM DB2 for i Procedure
72/120 PUBLIC 2012-04-12
![Page 73: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/73.jpg)
Procedure
1. Provide the database files required for the target system setup using one of the following ways:
■ Detach the database files from the source system database with a database manifest file (Sybase
ASE command quiesce database to manifest_file).
■ Create a backup (Sybase ASE command dump database).
2. Copy the files to the target system.
3. Run SAPinst to install the target system by choosing the following on the Welcome screen:
<SAP Product> Software Life-Cycle Options System Copy Sybase ASE Target System Installation
<System Variant> Based on <Technical Stack>
NOTE
■ Choose the installation services in exactly the order they appear. For more information,
see the Sybase ASE installation guide for your SAP system at: http://service.sap.com/
installnw70.
■ On the SAPinst screen SAP SystemDatabase, make sure that you select Homogeneous System
Copy (Sybase ASE-specific: Detach/Attach or Backup/Restore).
■ SAPinst asks you if you want to use either an already existing Sybase ASE installation on
the target system or the database software from the installation media.
■ Depending on the method chosen, you have to enter either the path to the database
dump files or the location of the database manifest file. SAPinst tries to find the database
devices mentioned in the manifest file automatically, otherwise it asks for the files during
the SAPinst execution phase.
5 Database-Specific System Copy
5.7 Sybase ASE Server-Specific Procedure
2012-04-12 PUBLIC 73/120
![Page 74: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/74.jpg)
This page is left blank for documents that are printed on both sides.
![Page 75: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/75.jpg)
6 Follow-Up Activities
Checklist
This section includes the follow-up activities that you have to perform to finish the system copy of
your SAP system:
1. You perform follow-up activities in the source system [page 75].
2. You perform follow-up activities in the target system:
1. You install the SAP license key [page 75].
2. You maintain the connection to the System Landscape Directory [page 76].
3. You perform follow-up activities for ABAP at operating system level [page 75].
4. You perform follow-up activities for ABAP at database level [page 77].
5. You perform follow-up activities for ABAP at SAP system level [page 78].
6. You check the target system [page 82].
6.1 Performing Follow-Up Activities in the Source System
Procedure
1. If you canceled or scheduled released jobs and jobs that must run periodically before you started
the copy procedure, reschedule these jobs: Tools CCMS Jobs Maintenance (SM37) .
2. Using CCMS, adapt your operation mode timetable to the original status: Tools CCMS
Configuration Operation mode calendar (SM63) .
6.2 Performing Follow-Up Activities in the Target System
6.2.1 Installing the License Key
Once the installation of the target system is completed and the SAP system copy has been imported,
you have to install a new license key.
CAUTION
Before installing the license key, make sure that SAP Note 831812 is applied.
For more information about ordering and installing the SAP license, see the SAP Library at:
6 Follow-Up Activities
6.1 Performing Follow-Up Activities in the Source System
2012-04-12 PUBLIC 75/120
![Page 76: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/76.jpg)
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 2) English SAP
NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SAP
Licenses .
6.2.2 Maintaining the Connection to the System Landscape Directory
Procedure
Check if both the source system and the target system are connected to the same System Landscape
Directory (SLD). If not, maintain the connection on the target system as described below.
NOTE
For more information about how to perform the individual tasks, see the documentation in the
SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 2) English
SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key
Capability Software Life Cycle Management System Landscape Directory Configuring Systems to Connect to
SLD .
The respective sections are stated below.
■ Maintain the SLD connection parameters:
Call transaction SLDAPICUST and change the value for the host name as well as for the port number.
For more information, see the section Connection Between Web AS ABAP Systems and SLD SLD
Application Programming Interface for ABAP-Based Systems Creating an HTTP Destination for the SLD ABAP
API on the ABAP Side .
■ Maintain the ABAP connection:
Call transaction RZ70 and change the value for the host and the gateway service in the Transport
Information group box. This value should be predefined by the value entered before in transaction
SLDAPICUST.
For more information, see the section Connection Between Web AS ABAP Systems and SLD Configuring
the SLD Data Supplier: Default Settings .
6.2.3 Performing Follow-Up Activities for ABAP
6.2.3.1 Activities at Operating System Level
Procedure
1. Adapt the configuration files at operating system level to meet network and SAP requirements.
2. Adapt additional SAP software components (for example, RFC, CPIC, SAP ArchiveLink) if required.
6 Follow-Up Activities
6.2 Performing Follow-Up Activities in the Target System
76/120 PUBLIC 2012-04-12
![Page 77: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/77.jpg)
3. Adapt additional non-SAP software components (for example, archiving systems, monitoring
tools, job schedulers) if required.
4. Adapt backup programs (for example, BRBACKUP, BRARCHIVE, BACKINT) if required.
5. Adapt non-SAP directories, file systems, NFS mounts, and so on, if required.
6. Check the SAP parameters of the default and instance profiles.
7. Check your UNIX shell files for special entries.
8. Check crontab or AT jobs.
9. Check operating system files (for example, .netrc, .rhosts).
10. Check operating system printers.
11. If the spool requests are stored at file system level, you must copy the subdirectories with the spool
files to the new global directory. For more information, see SAP Note 20176.
12. Only valid for: Oracle |
Adapt the database profiles init<SAPSID>.ora, init<SAPSID>.dba, and init<SAPSID>.sap.End of: Oracle |
6.2.3.2 Activities at Database Level
Procedure
1. Before starting the SAP system, make sure that the logging mechanism of the database is active.
2. Check the parameters in the database profiles.
3. Only valid for: Oracle |
Oracle only:
1. Delete all entries from the following tables:
DBSTATHORA, DBSTAIHORA, DBSTATIORA, DBSTATTORA.
2. Delete the user OPS$<SOURCE_SAPSID>ADM.
3. If you changed the <DBSID> during the system copy, we recommend that you adapt the
global_name parameter by using the following SQL command:
alter database rename global_name to <NEW_DBSID>;
If the parameter does not exist on your system, ignore this step.End of: Oracle |
4. Only valid for: MaxDB |
MaxDB only: Run report RSSDBTICMCLEANUP in the following cases:
■ You copied a system using MaxDB in both the source system and the target system.
■ You copied a system and changed the database platform from MaxDB to a different database
platform.
For more information, see SAP Note 1179714.End of: MaxDB |
6 Follow-Up Activities
6.2 Performing Follow-Up Activities in the Target System
2012-04-12 PUBLIC 77/120
![Page 78: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/78.jpg)
6.2.3.3 Activities at SAP System Level
Procedure
1. Run an installation check: Administration System administration Administration Installation Check
(transaction SM28).
2. Configure the Transport Management System (transaction STMS). If you did not change the SAPSID
during the system copy, all open transport, repair, and customizing requests that have not been
released in the source system will not be released automatically.
3. Adapt the transport parameters and transport routes in the Transport Management System (TMS):
1. Choose transaction STMS Overview Systems .
2. Select the system and select the Transporttool tab page.
To adapt the transport routes:
Choose transaction STMS Overview Transport routes .
4. Delete all entries from the following tables using transaction SE14: ALCONSEG, ALSYSTEMS, DBSNP,
MONI, OSMON, PAHI, SDBAD, SDBAH, SDBAP, SDBAR, DDLOG.
1. Call transaction SE14.
2. Enter <table name>.
3. Select Delete data.
4. Choose Activate and adjust database and then Yes.
5. Delete canceled and finished jobs.
Execute ABAP program RSBTCDEL, marking the field delete with forced mode: Tools ABAP Workbench
ABAP Editor (transaction SE38).
6. Adapt all jobs needed in the target system:
1. Copy the old jobs.
2. Modify the new jobs.
3. Delete the old jobs.
7. Check the consistency of the Temporary Sequential Objects (TemSe) and spool requests.
Call transaction SP12 or choose SAP Menu Tools CCMS Print TemSe Administration , and run
report RSPO1043. For more information, see SAP Notes 98065 and 48400.
8. Adapt the definition of the printers to meet the new system requirements:
■ Device types and character set definitions
■ Spool servers
■ Output management systems (OMS)
9. Synchronize the buffers as described in SAP Note 36283 and adapt the client information for the
logical system.
10. Adapt the RFC destination: Tools Administration Administration Network RFC destinations
(transaction SM59).
11. Check and adapt the trusted and trusting RFC relationships again.
6 Follow-Up Activities
6.2 Performing Follow-Up Activities in the Target System
78/120 PUBLIC 2012-04-12
![Page 79: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/79.jpg)
12. Clean the transactional RFC: Tools Administration Monitor Transactional RFC (transaction
SM58). For more information, see the relevant description in the SAP Online Documentation.
13. Start transaction SECSTORE using Check Entries. If you find erroneous entries with message text System-
dependent data for entry … changed, see SAP Note 816861.
14. Create new operation modes and remove old ones:
1. Create new operation modes and instance definitions.
2. Maintain the time table using the new operation modes.
3. Delete the old operation modes and old instance definitions.
15. Adapt the operation mode time tables (CCMS): Administration CCMS Configuration Operation
mode calendar (transaction SM63).
16. Adapt the instances and profiles (CCMS): Administration CCMS Configuration OP modes/
instances (transaction RZ04).
17. Define or remove the SAP system users and revise the authorizations of the system users: Tools
Administration User maintenance Users (transaction SU01).
18. Run transaction SE14 to delete all entries from tables TPFET and TPFHT. These contain information
about changes made to the profile of your source system.
IBM DB2 i: Use the commands CLRPFM R3<SID>DATA/TPFET and CLRPFM R3<SID>DATA/TPFHT.
19. Adapt other CCMS settings (for example, alert thresholds, reorganization parameters of CCMS
table MONI) if required.
20. Delete all entries from table TLOCK, which holds the repair requests from your source system.
21. Make data archived in the source system (data that does not reside in the database but was moved
to a different storage location using SAP Archive Management) accessible in the target system.
Adapt the file residence information in the target system. For more information, see the SAP
Online Documentation (SAP Web Application Server System Administration Application Data Archiving and
Reorganization) .
22. Redefine database actions (backup, update statistics, and so on) if you have used the DBA calendar
in the source system (transaction DB13).
23. Check the logon groups and the assignment of the application servers to the logon groups
(transaction SMLG). If required, create new logon groups and assign the new application servers to
these logon groups.
24. Check the connection to SAPNet - R/3 Frontend (transaction OSS1).
25. Check self-defined external commands (transaction SM69).
26. Check entries of the following tables in all relevant systems:
■ TXCOM (transaction SM54)
■ THOST (transaction SM55)
27. Check the logical system names. For more information, see Preparations [page 17]. If you need to
change logical system names in the system that results from the copy, change the logical system
6 Follow-Up Activities
6.2 Performing Follow-Up Activities in the Target System
2012-04-12 PUBLIC 79/120
![Page 80: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/80.jpg)
names at this time, as described in SAP Notes 103228 and 544509. Follow your corporate naming
strategy for logical systems when making this change.
BI customers: If you have copied an SAP BI (formerly BW) system, read SAP Note 325525.
28. For every client in your SAP system check the detail settings (client role, changes and transports
for client-dependent objects, changes for client-independent objects, protection level, restrictions)
(transaction SCC4).
29. Check if you can delete clients that are no longer used in the target system (transaction SCC5).
30. Check the contexts and segments of remote application servers for the SAP Monitoring
Infrastructure if required (transaction RZ21).
31. Configure the domain controller in the Transport Management System (TMS) by using
transaction STMS.
32. Post-processing for customer objects:
If customer objects are not original in the new system, modify the corresponding entries in table
TADIR.
If you encounter problems modifying a customer development class using transaction SMTS or
SM31, try using the option Validate (ENTER) instead of the option Save to save your changes.
33. Replace all existing PSEs in the target systems with new ones, which contain the new system's
information. Proceed as follows:
1. In your ABAP system, call transaction STRUST.
2. Proceed as described in the documentation Creating or Replacing a PSE in the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 2) English
SAP NetWeaver Library SAP NetWeaver by Key Capability Security System Security System Security
for SAP NetWeaver AS ABAP Only Trust Manager .
NOTE
■ Since replacing a PSE will remove all of the previously used certificates, also import
all necessary trusted certificates into the new PSE's certificate list. (Check the old
PSE's certificate list.) Distribute the new PSE's public-key certificate to the systems
where it will be used.
■ Make sure the new PSE contains the new system ID.
■ Note the naming conventions to use for each PSE. The naming conventions are
usually specified by the Certification Authority (CA) where you obtain the
certificate, however, the type of PSE also has some restrictions, for example, for the
SSL server PSE, the CN part of the Distinguished Name must be the host name used
to access the server. For the system PSE, we recommend using the SID as the CN
part.
Therefore, make sure that the Distinguished Name used for the PSE conforms with
the naming convention that applies.
34. ABAP Program Loads
6 Follow-Up Activities
6.2 Performing Follow-Up Activities in the Target System
80/120 PUBLIC 2012-04-12
![Page 81: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/81.jpg)
The ABAP loads are platform-dependent programs that are generated during runtime and stored
in database tables. They are not exported when you use the R3load procedure to copy your SAP
system. The ABAP loads are generated in the target system when they are first used. This might,
however, reduce production system performance. To avoid this, you can use transaction SGEN to
generate the missing loads.
Load generation requires a large amount of system resources. Therefore, it makes sense to schedule
the generation job to run overnight.
For a detailed description of the features, see the online documentation in transaction SGEN by
choosing Information on the SAP Load Generator, or in the Job Monitor by choosing Job Monitor.
35. BW only: If you changed the database management system (for example, IBM i to MaxDB) when
copying the system, you have to start program RS_BW_POST_MIGRATION in the background with
variant SAP&POSTMGRDB. If you did not change the database management system when copying the
system, you have to start program RS_BW_POST_MIGRATION in the background by using variant
SAP&POSTMGR. Program RS_BW_POST_MIGRATION performs necessary modifications on database-
specific objects (mainly BI objects).
6.2.3.4 Usage Type or Software Unit-Specific Follow-Up Activities
6.2.3.4.1 Embedded Search
PrerequisitesYou have applied SAP Note 1293026.
Procedure1. To establish the connection between TREX and the ABAP target server, run the script
configureTrexRfcConnection.py on the host where TREX is installed.
2. On the ABAP server, perform the following steps:
1. To delete copied search object connectors, call transaction SE38. Run the report
ESH_ADM_INDEX_ALL_SC with option Delete.
2. Call transaction SE16 to find out the TREX destination from table ESH_ADM_TREX.
3. Call transaction SM59 to delete the program ID of the TREX destination. TREX retrieves the
correct new program ID automatically.
NOTE
If you have applied SAP Note 1303185, program ESH_ADM_INDEX_ALL_SC automatically
deletes the program ID of the TREX destination.
4. Create new search object connectors.
For more information, see help.sap.com/nw70 SAP NetWeaver 7.0 Library (including
Enhancement Package 2) English SAP NetWeaver Library SAP NetWeaver by Key Capability Information
Integration by Key Capability Search Search Services in SAP NetWeaver AS ABAP Embedded Search
6 Follow-Up Activities
6.2 Performing Follow-Up Activities in the Target System
2012-04-12 PUBLIC 81/120
![Page 82: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/82.jpg)
Configuration Guide Performing the Post-Installation of Embedded Search Creating Search Object Connectors
and Starting Indexing .
6.2.3.5 Checking the Target System
ProcedureThe following actions are suitable for checking the consistency of the target system:
1. Perform an initial consistency check (transaction SM28).
2. Check the system log on all application servers (transaction SM21). In case of warnings, see SAP
Note 43434.
3. Check the consistency of the database (transaction DB02).
4. Perform a server check (transaction SM51).
5. FI customers: Run the job SAPF190 (accounting reconciliation) and compare the results to those
gained on the source system before the system copy ( Accounting Financial Accounting General ledger
Periodic Processing Closing Check/count Comparison ).
6. FI customers: Run the jobs RFUMSV00 (tax on sales/purchases), RAGITT01 (asset history sheet),
RAZUGA01 (asset acquisitions), andRAABGA01 (fixed asset retirements) and compare the results to
those gained on the source system before the system copy.
7. CO customers: Run the report group 1SIP and compare the results to those gained on the source
system before the system copy.
Only valid for: z/OS |
6.2.4 Performing Jobhead Correction after Homogeneous System Copy
NOTE
This section is only relevant for customers using CCMS to monitor their SAP system(s).
After copying your system, the CCMS jobhead still points to the former database SSID. In order to
complete the homogeneous system copy, the SSID needs to be set to the target system.
CAUTION
Only experienced users should use this utility.
Only valid for: Source Release = SAP NetWeaver 7.0 |
Prerequisites
You must have SAP NetWeaver 7.0 SP 12 or above to use this function.End of: Source Release = SAP NetWeaver 7.0 |
ProcedureTo set the SSID to the target system:
6 Follow-Up Activities
6.2 Performing Follow-Up Activities in the Target System
82/120 PUBLIC 2012-04-12
![Page 83: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/83.jpg)
Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.1 |
1. Call transaction DBACOCKPIT.
2. Choose Configuration Homogeneous System Copy: Jobhead Correction
3. Modify the necessary data.End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.1 |
Only valid for: Source Release = SAP Web AS 6.40 |
1. Call transaction DB2.
2. Choose Checks/Settings Correct Jobheads
3. Modify the necessary data.End of: Source Release = SAP Web AS 6.40 |
End of: z/OS |
6 Follow-Up Activities
6.2 Performing Follow-Up Activities in the Target System
2012-04-12 PUBLIC 83/120
![Page 84: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/84.jpg)
This page is left blank for documents that are printed on both sides.
![Page 85: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/85.jpg)
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
Purpose
The Migration Monitor is a tool that helps you to perform and control the unload and load process
for the ABAP stack during the system copy procedure. As of SAP NetWeaver 04 SR1 the Migration
Monitor is integrated into the SAPinst system copy tool, but you can also use the Migration Monitor
to copy previous releases by starting it manually.
For more information about how to start the Migration Monitor manually, see Starting the Migration
Monitor [page 95].
The Migration Monitor does the following:
■ Creating R3load command files
■ Creating R3load task files if required
■ Starting the R3load processes to unload the data
■ Transferring packages from the source to the target host if required
■ Starting the R3load processes to load the data as soon as a package is available
■ Informing the person performing the system copy in case of errors
Tool
The tool is located in the MIGMON.SAR SAPCAR archive. The archive file contains the following:
■ User Guide
● MigrationMonitor.pdf
■ Scripts
● export_monitor.sh / export_monitor.bat
● import_monitor.sh / import_monitor.bat
● res_check.sh / res_check.bat
● import_dirs.sh / import_dirs.bat
■ jar archives
● migmon.jar
● rescheck.jar
● activation.jar
● mail.jar
■ Property files
● export_monitor_cmd.properties
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
2012-04-12 PUBLIC 85/120
![Page 86: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/86.jpg)
● import_monitor_cmd.properties
Prerequisites
■ Java Runtime Environment (JRE) version 1.4.2 or higher is installed.
■ JAVA_HOME environment variable must point to the JRE directory.
■ The correct directory structure for R3load dump files must exist on both the source and target
hosts.
7.1.1 Configuration
The following options can be provided via the property file or via command line. Command line
parameters take precedence over parameters specified in the property file. Options are case sensitive,
that is, options that are not recognized are ignored.
Help
With the following command line option, the tool displays all parameters available:
■ -help
Version
With the following command line option, the tool displays version information:
■ -version
General Options
General Options
Name Description Comments
monitorTimeout Monitor timeout in seconds During a timeout, the monitor thread sleeps and does not analyze any files or its processing state. The default timeout value is 30 seconds.
E-Mail Options
Name Description Comments
mailServer SMTP server Server name or IP address of the company SMTP server
mailFrom “From” e-mail address non
mailTo “To” e-mail address Can contain an address list separated by “;”or blanks.
Additional Options
Name Description Comments
bg Enables background mode Takes effect only as command line option.If the tool is running in background mode, the UNIX shell window or Windows command prompt can be closed after startup.
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
86/120 PUBLIC 2012-04-12
![Page 87: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/87.jpg)
Name Description Comments
secure Enables secure mode Takes effect only as command line option.If the tool is running in secure mode, command line parameters (for example, passwords) are hidden for Java processes. Secure mode implicitly enables background mode.
NOTE
You should use this mode if you have to specify passwords on the command line.
trace Trace level Possible values:all, off, 1 (error), 2 (warning), 3 (info), 4 (config, default), 5, 6, 7 (trace)
Export Monitor – Options
Export Options
Option Description Comments
installDir Installation directory Directory where the installation tool (SAPinst, R3SETUP) is started. If you run the Migration Monitor without using the installation tools, then the installation directory is the directory where the R3load TSK and log files will be written.
exportDirs List of export directories Separator on Windows: “;”Separator on UNIX; IBM i: “:”The exportDirs parameter points to the directory to which the R3load dump files will be written. In the exportDirs directory, the subdirectories DATA, DB, and DB/<TARGET_DBTYPE> (for example, DB/ORA) must exist.
client Client operating mode Running in client mode means that the Migration Monitor runs parallel to the standard SAPinst export process and transfers the exported dump files to the import server.
server Server operating mode Running in server mode means that the Migration Monitor creates R3load TSK files (if necessary), R3load cmd files, and starts the R3load processes.
All options below are for server mode. The import monitor always runs in the server mode. If you want to run the export monitor in the server mode, specify the server parameter in the export monitor's properties file.
orderBy Package order Can be the name or path of the file that contains package names. If the option value is omitted then package order is not determined.
ddlFile DDL control file Path or file name of DDL control fileThe default is DDL<DBTYPE>.TPL. If the file name is used without a path, then the DDL control file from the export DB subdirectory is used.
ddlMap DDL mapping file File with mapping between DDL files and package names
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
2012-04-12 PUBLIC 87/120
![Page 88: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/88.jpg)
Option Description Comments
r3loadExe Path of the R3load executable
Optional; default is R3load. If only the name of the R3load executable is available, then JVM looks for the R3load executable using OS-specific process search rules.
tskFiles yes to create task files;no to skip
Up to and including version 4.6 , this must be set to no; as of version 4.7 set to yes. If the R3load task files *.TSK already exist, then the monitor will not overwrite them.
dataCodepage Code page for data files See SAP Note 552464. Possible values: 4102, 4103, 1100
taskArgs Additional R3load arguments for the TASK phase
Appended to the R3load command line.Options already set by the monitor: -ctf; -l
loadArgs Additional R3load arguments for the LOAD phase
Appended to the R3load command line.Options already set by the monitor: -e; -datacodepage; -l; -p; -r; -socket (if the socket option is specified)
expJobNum Number of parallel export jobs, default:1
Any positive number; 0 for an unlimited number of jobs. The value can be changed dynamically at runtime.
Network Exchange Options
Option Description Comments
net Network operating mode Exported dump files must be visible on the import host to use this mode.
netExchangeDir Network exchange directory
CAUTION
Clean up the netExchangeDir before starting a new export!
Used for communication between the export and import monitors. Must be writable for the export monitor and readable for the import monitor. The export monitor writes a <package>.SGN file to the network exchange directory as a signal to the import monitor that the package has been exported successfully and that the import can be started.
FTP Exchange Options
Option Description Comments
ftp FTP operating mode Exported dump files will be transferred automatically from the source host (directory exportDirs) to the target host (directory importDirs) using FTP.
ftpHost Remote FTP host Name or IP address of the import server.
ftpUser Name of the remote FTP user
The FTP user specified here should be <sapsid>adm to make sure that the package files can be read during the import (which is started as <sapsid>adm).
ftpPassword Password of the remote FTP user
CAUTION
Security risk!
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
88/120 PUBLIC 2012-04-12
![Page 89: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/89.jpg)
Option Description CommentsFor more information, see the secure parameter in section Additional Options
ftpExportDirs List of remote FTP directories for export dump
Both “;” and “:” separators are valid. This is the directory on the target host to which the dump will be transferred. The value will be the same as for importDirs in the import monitor's property file.
ftpExchangeDir Remote FTP exchange directory
Used for communication between the export and import monitors. Must be writable for the export monitor and readable for the import monitor. The export monitor writes a file <package>.SGN to the FTP exchange directory as a signal to the import monitor that the package has been exported successfully and that the import can be started.
ftpJobNum Number of parallel FTP jobs; the default is 1.
Any positive number; 0 for an unlimited number of jobs. The value can be changed dynamically at runtime.
Export Socket Host
Option Description Comment
socket Socket operating mode R3load will not write dump files to the file system, but the export and import work through the socket connection.
host Remote import host Name or IP address of the import host.
port Host port number Must be the same as the port number on the import host. Any free port on the import host from 1024 to 65535.
FTP Copy Options
Option Description Command
ftpCopy FTP copy operating mode Used as a separate program call for migration with sockets if no share directory is used. All files produced by R3lctl and R3szchk will be transferred from the source to the target host using FTP.
exportDirs List of export directories Separator on Windows: “;”Separator on UNIX: “:”In the exportDirs directory, the subdirectories DATA, DB, and DB/<TARGET_DBTYPE> (for example, DB/ORA) must exist. The R3load STR files must exist in the subdirectory DATA, the DDL*.TPL files in the subdirectory DB, and the R3load EXT files (if required) in the subdirectory DB/<TARGET_DBTYPE>.
ftpHost Remote FTP host Name or IP address of the import server
ftpUser Name of the remote FTP user
The FTP user specified here must be <sapsid>adm to make sure that the package files can be read during the import (which is started as <sapsid>adm).
ftpPassword Password of the remote FTP user
CAUTION
Security risk!
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
2012-04-12 PUBLIC 89/120
![Page 90: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/90.jpg)
Option Description Command
ftpExportDirs List of remote FTP directories for export dump
Both “;” and “:” separators are valid. This is the directory on the target host to which the dump will be transferred. The value will be the same as for importDirs in the import monitor's property file.
Any other option is ignored by the export monitor.
Mandatory Options for Export Monitor
■ Client mode:
installDir, exportDirs,
one of the options ftp, net (and their related parameters)
■ Server mode:
installDir, exportDirs, tskFiles,
one of the options ftp, net, socket (and their related parameters)
■ FTP copy:
exportDirs, ftpHost, ftpUser, ftpExportDirs, ftpExchangeDir
NOTE
The value of the dbType option is determined automatically in the shell script or batch files from
the dbms_type environment variable.
Import Options
Option Description Comment
installDir Installation directory The installation directory is the directory in which the installation tools (SAPinst, R3SETUP) are started.When you run the Migration Monitor without using the installation tools, the installation directory is the directory where the R3load TSK and log files are created.
importDirs List of import directories Separator on Windows: “;”Separator on UNIX, IBM i: “:”The importDirs parameter points to the directory where the R3load dump files are written. In the importDirs directory, the subdirectories DATA, DB, and DB/<TARGET_DBTYPE> (for example, DB/ORA) must exist.
orderBy Package order This option is used only if the import monitor works without the export monitor in standalone mode, that is, all export dump files are available on the import host before the import monitor is started.Values can be: ■ name: load packages in alphabetical order ■ size: load packages starting with the largest one ■ path of the file that contains package namesIf the option is omitted then package order is not defined.
ddlFile DDL control file Path or file name of DDL control file
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
90/120 PUBLIC 2012-04-12
![Page 91: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/91.jpg)
Option Description CommentThe default is DDL<DBTYPE>.TPL. If the file name is used without path, then the DDL control file from the export DB subdirectory is used.
ddlMap DDL mapping file File with mapping between DDL files and package names
r3loadExe Path of the R3load executable
Optional; default is R3load.If only the name of the R3load executable is available, then JVM looks for the R3load executable using OS-specific process search rules.
tskFiles yes to create task files; no to skip
Up to and including version 4.6, this must be set to no; as of version 4.7, it must be set to yes. If the R3load task files *.TSK already exist, the monitor will not overwrite them.
extFiles yes to include EXT files; no to skip them
Add EXT file entries to cmd files.If the EXT files cannot be found in the DB/<TARGET_DBTYPE> import dump subdirectory, the package processing is aborted.
dbCodepage Database code page for the target database
See SAP Note 552464. Possible values: 4102, 4103, 1100
migrationKey Migration key non
omit R3load omit value Can contain only the letters D, T, P, I, and V.D: omit data; do not load dataT: omit tables; do not create tablesP: omit primary keys; do not create primary keysI: omit indexes; do not create indexesV: omit views; do not create viewsIf you want to combine several omit options, list these options without blanks (for example, -o=TV).
taskArgs Additional R3load arguments for the TASK phase
Appended to the R3load command line.Options already set by the monitor:-ctf; -l; -o (if the omit argument is specified).
loadArgs Additional R3load arguments for the LOAD phase
Appended to the R3load command line.Options already used by the monitor:-i; -dbcodepage; -l; -p; -k; -r; -socket (if the socket option is specified); -o (if the omit argument is specified and task files are not used, that is, the value of tskFiles option is no).
impJobNum Number of parallel import jobs; the default is 1.
Any positive number; 0 for an unlimited number of jobs.The value can be changed dynamically at runtime.
Import Exchange Options
Option Description Comment
exchangeDir Exchange directory If this option is not set, the monitor runs in standalone mode, that is, without the export monitor. All the export dump files or the SAP export CDs from the installation kit must be available on the import host and
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
2012-04-12 PUBLIC 91/120
![Page 92: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/92.jpg)
Option Description Commentbe specified with the importDirs parameter (for example, in the properties file).If there is an old export_statistics.properties file (for example, from a previous export run), remove this file.
Import Socket Options
Option Description Command
socket Socket operating mode non
port Server port number Any free port from 1024 to 65535.
Any other option is ignored by the import monitor.
Mandatory Options for Import Monitor
■ Server mode (default):
installDir, importDirs, tskFiles, extFiles,
one of the options exchangeDir or socket (and their related parameters)
■ Standalone mode:
installDir, importDirs, tskFiles, extFiles
■ Only valid for: IBM i5/OS |
IBM i-specific:
loadArgs= -nojournal
End of: IBM i5/OS |
NOTE
The value of the dbType option is determined automatically in the shell script or batch files from
the dbms_type environment variable.
7.1.2 Assigning DDL Files to Packages
It is possible to use several different DDL*.TPL templates during the export or import. The assignment
of a specific DDL file to a single package is done within a simple text file, which then has to be specified
using the ddlMap option within the Migration Monitor's properties file. Packages not listed in the DDL
mapping file use the default DDL control file.
EXAMPLE
DDL mapping file:
# DDL mapping file ddl_mapping.txt
# !!! line with [GROUP_NAME] can be skipped
# used for documentation purposes only
[ SORTED UNLOAD ]
# DDL file for sorted unload
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
92/120 PUBLIC 2012-04-12
![Page 93: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/93.jpg)
ddlFile = /export_dump/ABAP/DB/ORA/DDLORA.TPL
# package names
SAPAPPL0
SAPAPPL1
SAPSDIC
[ UNSORTED UNLOAD ]
DDL file for unsorted unload
ddlFile = ./DDLORA_LRG.TPL
# table names
TABLE_A
TABLE_B
TABLE_C
7.1.3 Defining Groups of Packages
The “package group” feature is an enhancement to defining a package order. By defining groups, you
can prevent certain packages being executed in parallel and you can define how many large tables are
exported or imported at the same time. In addition, you can specify different values for the parameters
jobNum and taskArgs or loadArgs for each package. Package groups can be defined in the same text
file in which the package order can be defined (see parameter orderBy). The previous package order
format is also fully supported.
A group starts with any arbitrary name in brackets and ends when the next group starts.
If package groups are defined, the maximum number of parallel R3load jobs is the sum of jobNum of
all packages. All packages without a package group will be assigned to a “default group” with the number
of jobs that was defined in the Migration Monitor's properties file.
EXAMPLE
Package order file with group:
# custom package order
# package names
SAPAPPL0
SAPAPPL1
SAPAPPL2
# package group
[ SEQUENTIAL GROUP ]
jobNum = 1
# table names
TABLE_A
TABLE_B
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
2012-04-12 PUBLIC 93/120
![Page 94: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/94.jpg)
TABLE_C
7.1.4 Processing Split Tables
If tables have been split during the export, ensure before the import starts that the table exists (only
once) and that the primary key and the indexes are created (only once) before or after (as defined in
the DDL template) the table data has been imported. These tasks will automatically be synchronized
by the Migration Monitor.
WHR files are part of the package and have to be copied to the DATA export subdirectory to make sure
that the same WHR file is used for the export and import of the corresponding package.
The following database platforms do not support parallel data import:
■ IBM DB2 for Linux, UNIX, and Windows
■ MS SQL
You can ensure this by using the Defining Groups of Packages [page 93] feature.
Procedure
Re-Starting the Import of a Split Table Package
If the import of a package fails, the rows that belong to this package have to be deleted using the
WHERE condition assigned to this package before the data import is started again. The deletion with a
WHERE clause can be very time consuming, therefore it is faster to delete all rows of the corresponding
table manually and re-import all packages instead.
Restart for all other database platforms:
1. Eliminate the reason for the failure of the import of the packages.
2. Manually delete all rows of the table for which the import of one or more packages failed.
3. Remove the TSK files of all packages that import data into this table (<table name>-
<counter>__TPI.TSK). Do not remove the TSK files that create either the table or the indexes for
this table.
4. Adapt the file import_state.properties in the installation directory. Replace the status “+” of
all packages for the corresponding table that had been imported successfully and has to be re-
imported by “0” (see Restarting R3load Processes [page 45]).
5. Restart the import.
ExampleTarget database does not support parallel data import
During the export you have split the MY_FIRST_TABLE table into 3 packages and MY_SECOND_TABLE into
5 packages. You now want to run a maximum of 10 R3load processes for parallel data import.
Create the file inputFile.txt with the following content:
[ MY_FIRST_TABLE ]
jobNum = 1
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
94/120 PUBLIC 2012-04-12
![Page 95: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/95.jpg)
MY_FIRST_TABLE-1
MY_FIRST_TABLE-2
MY_FIRST_TABLE-3
[ MY_SECOND_TABLE ]
jobNum = 1
MY_SECOND_TABLE-1
MY_SECOND_TABLE-2
MY_SECOND_TABLE-3
MY_SECOND_TABLE-4
MY_SECOND_TABLE-5
In this file, you can also define the processing order of packages or you can assign DDL files to packages.
The inputFile.txt file has to be specified as a value for the Migration Monitor parameter orderBy.
An R3load job is started for every group (MY_FIRST_TABLE and MY_SECOND_TABLE). The number of
parallel R3load jobs will be the total of the number of R3load jobs of each group plus the number of
R3load jobs defined for the default group (which is made up of all packages without an explicit group
name) defined by the parameter jobNum.
In this example, the parameter jobNum in the import_monitor_cmd.properties file has to be set to 8
to ensure that no more than 10 R3load processes run in parallel.
7.1.5 Starting the Migration Monitor
The Migration Monitor has to be started on the source database host (export monitor) and on the
target database host (import monitor).
You can specify options in the command line or in the export or import property files (see
Configuration [page 86]). The names of the property files are export_monitor_cmd.properties and
import_monitor_cmd.properties. Templates for these files are included in the application archive and
must be located in the current user's working directory.
Any options specified in the command line take precedence over the corresponding options in the
application property file. Options are case sensitive, that is, options that are not recognized are ignored.
Prerequisites
■ Make sure that the export dump directory and its subdirectory exist as described in the following
table:
Directory Description
<export dump dir>/DATA Contains the STR files generated by R3ldctl
<export dump dir>/DB Contains the DDL<DBTYPE>.TPL files generated by R3ldctl
<export dump dir>/DB/<DBTYPE> Contains the EXT files generated by R3szchk (optional)
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
2012-04-12 PUBLIC 95/120
![Page 96: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/96.jpg)
■ Make sure that the export dump directory can be accessed from the target host, either using a
shared directory (local to the export host) or by using Migration Monitor's FTP feature.
Procedure
1. Start the tool using one of the following ways:
■ Only valid for: UNIX |
UNIX shell scripts
export_monitor.sh / import_monitor.shEnd of: UNIX |
■ Only valid for: Windows |
Windows batch files
export_monitor.bat / import_monitor.batEnd of: Windows |
■ Only valid for: IBM i5/OS |
IBM i-specific
1. Check that the environment variable PASE_THREAD_ATTACH is set to “Y” using the
command WRKENVVAR.
If PASE_THREAD_ATTACH is missing, use the following command to set it:
ADDENVVAR PASE_THREAD_ATTACH 'Y'
2. Run the command call qp2term.
3. export_monitor.sh / import_monitor.shEnd of: IBM i5/OS |
■ Automatically as part of the SAPinst export and import procedure
■ Manually within the SAPinst system copy tool:
1. On the Parameter Mode Default Settings SAPinst screen, choose Custom.
2. On the SAP System Export for Target System screen, select Start Migration Monitor Manually.
3. SAPinst will stop and ask you to start the Migration Monitor manually and to continue
with SAPinst as soon as the Migration Monitor finished successfully.
NOTE
If you use FTP access and security is required (see FTP Exchange Options and FTP Copy Options in
Configuration [page 86]), start the Migration Monitor in secure mode to prevent seeing FTP
password in the command line parameter string or in the property file (for example, on
UNIX: ./export_monitor_secure.sh –ftpPassword <password>).
2. Close the shell window or command processor. The monitor process runs in the background.
3. Specify options as required in one of the following ways:
■ In the command line:
Specify the option in the format: -optionName optionValue
■ In the application property file:
Add an option as a new line in the format: optionName=optionValue
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
96/120 PUBLIC 2012-04-12
![Page 97: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/97.jpg)
Only valid for: IBM i5/OS;UNIX |
EXAMPLE
Command line:
./export_monitor.sh –ftp
./export_monitor.sh –ftpCopy
./export_monitor.sh –socket –host <import server> –port 5000
End of: IBM i5/OS;UNIX |
Only valid for: Windows |
EXAMPLE
Command line for Windows cmd.exe:
export_monitor.bat –net
export_monitor.bat –socket
End of: Windows |
4. Use monitor*.log and *.console.log files to check the monitor processing state.
EXAMPLE
export_monitor_cmd.properties file with export options:
# Export Monitor options
# Operating mode: ftp | net
#net
ftp
#
# Common options
#
# List of export directories, separator on Windows ; on UNIX :
exportDirs=C:\TEMP\export_dump
# SAPinst start directory
installDir=C:\install\start
# Monitor timeout in seconds
monitorTimeout=30
#
# FTP options
#
# Remote FTP host
ftpHost=server
# Name of remote FTP user
ftpUser=sysadm
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
2012-04-12 PUBLIC 97/120
![Page 98: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/98.jpg)
# Password of remote FTP user
ftpPassword=password
# List of remote FTP directories for export dump, separator : or ;
ftpExportDirs=/install_dir/export_dump
# Remote FTP exchange directory
ftpExchangeDir=/install_dir/exchange
# Number of parallel FTP jobs
ftpJobNum=3
#
# E-mail options
#
# SMTP server
mailServer=sap-ag.de
# "From" email address
# "To" email address
[email protected] [email protected]
EXAMPLE
import_monitor_cmd.properties file with import options:
# Import Monitor options
#
# Common options
#
# List of import directories, separator on Windows ; on UNIX :
importDirs=/install_dir/export_dump
# SAPinst start directory
installDir=/install_dir/start
# Exchange directory
exchangeDir=/install_dir/exchange
# Generation of task files: yes | no
tskFiles=yes
# Inclusion of extent files: yes | no
extFiles=yes
# Monitor timeout in seconds
monitorTimeout=30
#
# R3load options
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
98/120 PUBLIC 2012-04-12
![Page 99: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/99.jpg)
#
# DB code page for the target database
dbCodepage=1100
# Migration key
migrationKey=
# Additional R3load arguments for TASK phase
taskArgs=
# Additional R3load arguments for LOAD phase
loadArgs=
# Number of parallel import jobs
impJobNum=3
#
# E-mail options
#
# SMTP server
mailServer=sap-ag.de
# "From" email address
# "To" email address
[email protected] [email protected]
Only valid for: Oracle |
Processing Steps of a System Copy (Oracle only)
With the settings in the property file listed in the examples above and an Oracle database as source and
target database, the following prerequisites must be fulfilled:
■ The following directories must exist on the export host (parameter: exportDirs):
● c:\temp\export_dump\ABAP\DATA
● c:\temp\export_dump\ABAP\DB
● c:\temp\export_dump\ABAP\DB\ORA
The c:\temp\export_dump\ABAP\DATA directory must contain the STR files generated by R3ldctl.
The c:\temp\export_dump\ABAP\DB directory must contain the DDL<DBTYPE>.TPL files generated
by R3ldctl.
The c:\temp\export_dump\ABAP\DB\ORA directory must contain the EXT files generated by
R3szchk.
■ The following directories must exist on the import host (parameter: importDirs):
● /install_dir/export_dump/ABAP/DATA
● /install_dir/export_dump/ABAP/DB
● /install_dir/export_dump/ABAP/DB/ORA
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
2012-04-12 PUBLIC 99/120
![Page 100: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/100.jpg)
The /install_dir/export_dump/ABAP/DATA directory must contain the STR files generated by
R3ldctl.
The /install_dir/export_dump/ABAP/DB directory must contain the DDL<DBTYPE>.TPL files
generated by R3ldctl.
The /install_dir/export_dump/ABAP/DB/ORA directory must contain the EXT files generated by
R3szchk.
The following steps are performed during a system copy:
1. The export monitor writes the R3load dump files and the TOC files to the directory c:\temp
\export_dump\ABAP\DATA.
2. The R3load log files, cmd files, and TSK files (if required) are located in the directory c:
\<install_dir>\start (installDir parameter). The export itself is not done by the export
monitor, as the monitor is started in client mode (server parameter is not set).
3. When a package has been exported successfully, the export monitor transfers all files belonging to
that package (TOC, STR, EXT, 001, and so on) to the target host (ftpHost parameter) to the
corresponding subdirectories of the directory /<install_dir>/export_dump
(ftpExportDirsparameter) as user <sapsid>adm (ftpUser parameter) with password
(ftpPassword parameter).
4. When the package files have been completely transferred to the server, the export monitor writes
a <package>.SGN signal file to the /<install_dir>/exchange directory (ftpExchangeDir
parameter) to notify the import monitor that it can start importing this package.
5. The import monitor starts to import a package as soon as the <package>.SGN file is found in the /
install_dir/exchange (exchangeDir parameter) directory.
6. The R3load log files, cmd files, and TSK files (if required) will be located in the directory /
<install_dir>/start (installDir parameter).
7. The DDLORA.TPL file must be copied to the /install_dir/start directory (installDir parameter)
before you start the import monitor.End of: Oracle |
7.1.6 Output Files
Export
■ export_monitor.log
■ export_state.properties
■ ExportMonitor.console.log
Import
■ import_monitor.log
■ import_state.properties
■ ImportMonitor.console.log
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
100/120 PUBLIC 2012-04-12
![Page 101: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/101.jpg)
Both the export and import state files contain package state lines such as SAPUSER=+.
The format of state lines is <PACKAGE>=<STATE>. Possible values for state are listed in the following
table:
0 Package export/import not yet started.
? Package export/import in progress.
- Package export/import finished with errors.
+ Package export/import finished successfully.
If any ftp or net exchange options are used, then the export state file may contain a second <STATE>
column that refers to the state of the package transfer.
Then the export state file contains package state lines such as SAPUSER=++.
Format of lines is <PACKAGE>=<STATE>. Possible values for state are:
0 Package export not yet started.
? Package export in progress.
- Package export finished with errors.
+0 Package export finished successfully; package transfer not yet started.
+? Package transfer in progress.
+- Package transfer finished with errors.
++ Package transfer finished successfully.
7.1.7 Installing the Target System Using the Migration Monitor
PrerequisitesOnly valid for: UNIX;Windows |
Make sure that 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 are created, look at the file
DBSIZE.XML located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE> (Windows) or <EXPDIR>/DB/
<DATABASE> (UNIX).End of: UNIX;Windows |
Only valid for: IBM i5/OS |
Make sure that there is enough free space on the target system for the database load.End of: IBM i5/OS |
Procedure
1. If you want to start the installation of the target host using the Migration Monitor, make sure that
at least the dump directory with the following files is accessible on the target host and that it
contains the correct data before you start SAPinst:
■ <dump dir>/LABEL.ASC
7 Additional Information
7.1 R3load Procedures Using the Migration Monitor
2012-04-12 PUBLIC 101/120
![Page 102: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/102.jpg)
■ <dump dir>/DB/<DBTYPE>/DBSIZE.XML
■ <dump dir>/DB/DDLORA.TPL
If the dump directory is not shared on the target host, copy the files from the source system to the
target system as soon as they have been created on the source host using the (export) Migration
Monitor's FTP copy options.
2. Start SAPinst as described in the installation documentation for your SAP component.
3. To install the target system, follow the instructions in the SAPinst input dialogs and enter the
required parameters as far as the ABAP System > Database screen. On this screen, choose Standard
System Copy/Migration (R3load-Based).
4. Select the Use Migration Monitor option.
NOTE
If you need more information about input parameters, position the cursor on the field of the
respective parameter and press F1 .
5. When SAPinst displays the CD browser window and asks for the Export Migration CD, enter the path
to the export directory <EXPDIR>.
6. Continue as described in the installation documentation for your SAP component until a dialog
box appears that states:
If the export has been started on the source system and the export monitor is
running, you can now start the data load by starting the import monitor.
7. Check that the prerequisites in the dialog box are fulfilled by your system. If so, start the Migration
Monitor.
8. Complete the installation as described in the installation documentation for your SAP solution.
CAUTION
If you have to restart the import after an error, just restart SAPinst. The import is continued
with the table that was not imported successfully.
7.2 Interrupted Installation with SAPinst
The SAP system installation might be interrupted for one of the following reasons:
■ An error occurred during the Define Parameters or Execute phase:
SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses
and a dialog box appears. The dialog box contains a short description of the choices listed in the
table below as well as a path to a log file that contains detailed information about the error.
■ You interrupted the installation by choosing Cancel in the SAPinst menu.
CAUTION
If you stop an option in the Execute phase, any system or component installed by this option
is incomplete and not ready to be used. Any system or component uninstalled by this option
is not completely uninstalled.
7 Additional Information
7.2 Interrupted Installation with SAPinst
102/120 PUBLIC 2012-04-12
![Page 103: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/103.jpg)
The following table describes the options in the dialog box:
Option Definition
Retry SAPinst retries the installation from the point of failure without repeating any of the previous steps.This is possible because SAPinst records the installation progress in the keydb.xml file.We recommend that you view the entries in the log files, try to solve the problem, and then choose Retry.If the same or a different error occurs, SAPinst displays the same dialog box again.
Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and the GUI server.SAPinst records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps (see the procedure below).
Continue SAPinst continues the installation from the current point.
View Log Access installation log files.
Only valid for: UNIX |
NOTE
You can also terminate SAPinst by choosing Ctrl + C . However, we do not recommend that
you use Ctrl + C , because this kills the process immediately.
End of: UNIX |
Procedure
This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to
continue an interrupted installation after an error situation.
1. Only valid for: Windows |
Log on as a user who is a member of the local administrators group.End of: Windows |
2. Only valid for: UNIX |
Log on to your local UNIX host as user root.
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database.
End of: UNIX |
3. Only valid for: Windows |
Insert the Installation Master DVD in your DVD drive.End of: Windows |
4. Only valid for: UNIX |
Mount your Installation Master DVD.
7 Additional Information
7.2 Interrupted Installation with SAPinst
2012-04-12 PUBLIC 103/120
![Page 104: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/104.jpg)
NOTE
Mount the DVD locally. We do not recommend using Network File System (NFS).
End of: UNIX |
5. Only valid for: Windows |
Change to the required directory:
<DVD drive>:\IM_WINDOWS_<platform>
End of: Windows |
6. Only valid for: Windows |
Double-click sapinst.exe.
NOTE
For more information about how to start SAPinst, see Running SAPinst [page 39] or Performing a
Remote Installation with SAPinst [page 106] and Starting SAPinst GUI Separately [page 109].
End of: Windows |
7. Only valid for: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle |
Change to the directory with the sapinst executable for your operating system by entering the
following command:End of: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle |
8. Only valid for: Unix |
Start SAPinst by executing the following command:
./sapinst
NOTE
For more information about how to start SAPinst, see Running SAPinst [page 39] or Performing a
Remote Installation with SAPinst [page 106] and Starting SAPinst GUI Separately [page 109].
End of: Unix |
9. Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS;No Database |
Log on to your local IBM i host as your installation user with similar authorization rights as
QSECOFR. For more information about how to create the installation user SAPIUSR, see the section
Preparing a Windows User Account and IBM i User Profile [page 39].End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS;No Database |
10. Only valid for: IBM i5/OS | IBM DB2 for i5/OS |
Enter the following commands:
CD DIR('<Installation_Master_DVD>/IM_OS400_PPC64')
CALL PGM(QP2TERM) PARM('./sapinst')
NOTE
For more information about how to start SAPinst on IBM i, see Running SAPinst [page 39] or
Performing a Remote Installation with SAPinst [page 106] and Starting SAPinst GUI Separately [page
109].
End of: IBM i5/OS | IBM DB2 for i5/OS |
11. From the tree structure in the Welcome screen, select the installation option that you want to
continue and choose Next.
The What do you want to do? screen appears.
7 Additional Information
7.2 Interrupted Installation with SAPinst
104/120 PUBLIC 2012-04-12
![Page 105: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/105.jpg)
12. In the What do you want to do? screen, decide between the following alternatives and continue with
Next:
Alternative Behavior
Run a new option SAPinst does not continue the interrupted installation option. Instead, it moves the content of the old installation directory and all installation-specific files to a backup directory. Afterwards, you can no longer continue the old installation option.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds>
EXAMPLE
log_01_Oct_2008_13_47_56
CAUTION
SAPinst moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.
Continue with the old option SAPinst continues the interrupted installation option from the point of failure.
7.3 Performing a Remote Export Using SAPinst
Purpose
You can run the SAPinst GUI in standalone mode to perform a remote export.
This enables you to perform the export on another host (the remote host) while monitoring the export
with the SAPinst GUI on your local Windows or UNIX computer (the local host).
Prerequisites
■ You have performed the preparation activities for your local host (SAPinst GUI host) and your
remote host as described in Prerequisites in Exporting the Source System Using SAPinst [page 32].
■ Both computers are in the same network and can ping each other.
To test this:
● Log on to your remote host and enter the command ping <local host>.
● Log on to the local host and enter the command ping <remote host>.
Process Flow
1. Start the SAPinst server on your remote host.
2. Start the SAPinst GUI on your local host.
3. Perform the installation using the SAPinst GUI.
For more information, see:
■ Starting SAPinst on the Remote Host [page 106]
7 Additional Information
7.3 Performing a Remote Export Using SAPinst
2012-04-12 PUBLIC 105/120
![Page 106: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/106.jpg)
■ Starting SAPinst GUI Separately [page 109]
7.3.1 Performing a Remote Installation with SAPinst
You use this procedure to install your SAP system on a remote host. In this case, SAPinst runs on the
remote host, and the SAPinst GUI runs on the local host. The local host is the host from which you
control the installation with the SAPinst GUI. The SAPinst GUI connects using a secure SSL connection
to SAPinst.
Only valid for: IBM DB2 for i5/OS |
CAUTION
This is the default on IBM i. Since there is no GUI on IBM i, you must perform a remote installation.
SAPinst will run on the IBM i host and the SAPinst GUI will run on your Windows PC.
End of: IBM DB2 for i5/OS |
Only valid for: IBM i5/OS;UNIX |
If your security policy requires that the person performing the installation by running the SAPinst GUI
on the local host is not allowed to know root credentials on the remote host, you can specify another
operating system user for authentication purposes. You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command
line.End of: IBM i5/OS;UNIX |
Only valid for: Windows |
If your security policy requires that the person performing the installation by running the SAPinst GUI
on the local host is not allowed to know administrator credentials on the remote host, you can specify
another operating system user for authentication purposes. You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinst.exe from the command line.End of: Windows |
As an alternative to remote installation you can use an X server for Microsoft Windows or other remote
desktop tools such as VNC Viewer or NX Server / NX Client – offered by various vendors or open
source – for remote access to SAPinst GUI on Windows workstations. We recommend that you use the
Open Text Exceed X Server, which we use to validate installations with SAPinst. For more
information, see SAP Note 1170809.
Only valid for: UNIX;Windows | Linux;Windows |
You can run the SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host.
For more information, see Starting SAPinst GUI Separately [page 109].End of: UNIX;Windows | Linux;Windows |
7 Additional Information
7.3 Performing a Remote Export Using SAPinst
106/120 PUBLIC 2012-04-12
![Page 107: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/107.jpg)
Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |
CAUTION
In this section, “local host” refers to the Windows installation host, and“ remote host” refers to
the IBM i host where the SAP system is installed.
End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |
Prerequisites
■ The remote host meets the prerequisites for starting SAPinst as described in Running SAPinst in your
installation guide.
■ Both computers are in the same network and can ping each other.
To test this:
Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle;Sybase ASE |
1. Log on to your remote host and enter the command ping <local host>.
2. Log on to the local host and enter the command ping <remote host>.End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle;Sybase ASE |
Only valid for: IBM DB2 for i5/OS |
1. Log on to your remote host (IBM i) and enter the command PING RMTSYS('<local
host>').
2. Log on to the local host (Windows PC) and enter the command ping <remote host>.End of: IBM DB2 for i5/OS |
■ If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter, make sure that this user exists on the remote host.
ProcedureOnly valid for: Windows |
1. Log on to your remote host as a user that is a member of the local administrators group.
2. Insert the Installation Master DVD in the DVD drive on your remote host.
3. Open a command prompt and change to the required directory by entering the following
commands:
Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;Sybase ASE |
cd /d <DVD drive>:\IM_WINDOWS_<platform>
End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;Sybase ASE |
Execute sapinst.exe -nogui
NOTE
If you need to specify another operating system user for authentication purposes, enter the
following command:
sapinst.exe -nogui SAPINST_REMOTE_ACCESS_USER=<specified OS user>
SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the
command prompt:
7 Additional Information
7.3 Performing a Remote Export Using SAPinst
2012-04-12 PUBLIC 107/120
![Page 108: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/108.jpg)
guiengine: no GUI connected; waiting for a connection on host <host_name>, port
<port_number> to continue with the installation
4. Start the SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 109].End of: Windows |
Only valid for: UNIX |
1. Log on to your remote host as user root.
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database.
2. Mount the Installation Master DVD.
3. Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;Sybase ASE |
Change to the directory of the sapinst executable by entering the following command:End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;Sybase ASE |
4. Start SAPinst by executing the following command:
./sapinst -nogui
NOTE
If you need to specify another operating system user for authentication purposes, enter the
following command:
./sapinst -nogui SAPINST_REMOTE_ACCESS_USER=<specified OS user>
SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the
command prompt:
guiengine: no GUI connected; waiting for a connection on host <host_name>, port
<port_number> to continue with the installation
5. Start the SAPinst GUI on your local host as described in Starting the SAPinst GUI Separately [page
109].End of: UNIX |
Only valid for: IBM i5/OS |
1. Log on your IBM i host as a user with similar authorization rights as QSECOFR. For more information,
see Preparing an IBM i User Profile [page 39].
CAUTION
Make 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.
3. Start SAPinst from the Installation Master DVD by entering the following commands:
■ CD DIR('<Installation Master_DVD>/IM_OS400_PPC64')
■ CALL PGM(QP2TERM) PARM('./sapinst' '-nogui')
SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the
command prompt:
7 Additional Information
7.3 Performing a Remote Export Using SAPinst
108/120 PUBLIC 2012-04-12
![Page 109: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/109.jpg)
guiengine: no GUI connected; waiting for a connection on host <host_name>, port
<port_number> to continue with the installation
Only valid for: HA (UNIX) |
NOTE
If 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' '-nogui' 'SAPINST_USE_HOSTNAME=<virtual
host name>')
End of: HA (UNIX) |
4. Since there is no GUI on IBM i, you do not see an SAPinst Welcome screen. Start the SAPinst GUI
separately on your Windows installation host and connect to the port number specified by the
message: GUI server port:<port_ number>. For more information, see Starting SAPinst GUI
Separately [page 109].End of: IBM i5/OS |
7.3.2 Starting SAPinst GUI Separately
You use this procedure to start the SAPinst GUI separately. You need to start the SAPinst GUI separately
in the following cases:
■ Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |
You are running IBM i and did not set a DISPLAY environment variable.End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |
■ You closed the SAPinst GUI using File Exit from the SAPinst menu while SAPinst is still
running.
■ You want to perform a remote installation, where the SAPinst GUI runs on a different host from
SAPinst. For more information, see Performing a Remote Installation with SAPinst [page 106].
■ Only valid for: IBM i5/OS;UNIX |
You want to run SAPinst in accessibility mode. In this case, you have to start the SAPinst GUI
separately on a Windows host as described below with the additional command line parameter –
accessible. For more information, see Running SAPinst in Accessibility Mode in your installation guide.End of: IBM i5/OS;UNIX |
Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |
CAUTION
This is the default on IBM i. Since there is no GUI on IBM i, you must start the SAPinst GUI
separately.
End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |
7 Additional Information
7.3 Performing a Remote Export Using SAPinst
2012-04-12 PUBLIC 109/120
![Page 110: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/110.jpg)
Prerequisites
The host on which you want to start the SAPinst GUI meets the prerequisites for starting SAPinst as
described in Exporting the Source System Using SAPinst [page 32]
Procedure
Starting SAPinst GUI on Windows
1. Insert the SAP Installation Master DVD into your DVD drive.
2. Change to the directory of the sapinstgui executable:
Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle |
<Drive>:\<Installation_Master_DVD>\IM_WINDOWS_<platform>
End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle |
Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |
NOTE
If you want to start the SAPinst GUI on a Windows 32-bit operating system, change to the
following directory:
<Drive>:\<Installation_Master_DVD>\IM_WINDOWS_I386
End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle |
Only valid for: IBM DB2 for i5/OS |
NOTE
If you start the SAPinst GUI executable on Windows 7 or Windows 2008, you must use the
option Run as administrator. Typically, you first start a command prompt using Run as
administrator. Then in this command prompt, you enter the SAPinst GUI command.
End of: IBM DB2 for i5/OS |
Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |
NOTE
If you want to start the SAPinst GUI on a Windows 32-bit operating system, you can use the
executable available in the DVD or change to the following directory:
<Installation_Master_DVD>\IM_WINDOWS_I386
End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |
Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |
NOTE
If you have a share ROOTBIN on your IBM i and you have mapped this share to the drive X,
you can start the SAPinst GUI using your copied Installation Master DVD:
X:\tmp\<SID>\<Installation_Master_DVD>\IM_WINDOWS_I386
End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |
3. Start the SAPinst GUI from a command prompt by executing sapinstgui.exe with the relevant
command line parameters:
■ If you want to perform a remote installation, execute the following command:
7 Additional Information
7.3 Performing a Remote Export Using SAPinst
110/120 PUBLIC 2012-04-12
![Page 111: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/111.jpg)
sapinstgui.exe -host <remote_host> -port
<port_number_gui_server_to_gui_client>
– where <remote_host> is the name of the remote host, and
<port_number_gui_server_to_gui_client> is the port the GUI server uses to communicate
with the GUI client (21212 by default).
■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, proceed
as follows:
● If you are performing a local installation with SAPinst and SAPinst GUI running on the
same host, execute the following command:
sapinstgui.exe -port <port_number_gui_server_to_gui_client>
– where <port_number_gui_server_to_gui_client> is the port the GUI server uses to
communicate with the GUI client (21212 by default).
● If you are performing a remote installation with SAPinst and SAPinst GUI running on
different hosts, execute the following command:
sapinstgui.exe -host <remote_host> -port
<port_number_gui_server_to_gui_client>
– where <remote_host> is the name of the remote host, and
<port_number_gui_server_to_gui_client> is the port the GUI server uses to
communicate with the GUI client (21212 by default).
The SAPinst GUI starts and connects to SAPinst.
Starting SAPinst GUI on UNIX
1. Mount the Installation Master DVD.
NOTE
Mount the DVD locally.
We do not recommend that you use Network File System (NFS).
2. Change to the directory of the sapinstgui executable by entering the following command:
cd <Mountpoint of Installation Master DVD>/IM_<OS>
NOTE
If you want to start the SAPinst GUI on a Linux 32–bit platform, enter the following command:
cd <Mountpoint of Installation Master DVD>/IM_LINUX_I386
3. Only valid for: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |
Start the SAPinst GUI by executing ./sapinstgui with the relevant command line parameters:
■ If you want to perform a remote installation, execute the following command:
./sapinstgui -host <remote_host> -port <port_number_gui_server_to_gui_client>
– where <remote_host> is the name of the remote host, and
<port_number_gui_server_to_gui_client> is the port the GUI server uses to communicate
with the GUI client (21212 by default).
7 Additional Information
7.3 Performing a Remote Export Using SAPinst
2012-04-12 PUBLIC 111/120
![Page 112: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/112.jpg)
■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, proceed
as follows:
● If you are performing a local installation with SAPinst and SAPinst GUI running on the
same host, execute the following command:
sapinstgui -port <port_number_gui_server_to_gui_client>
– where <port_number_gui_server_to_gui_client> is the port the GUI server uses to
communicate with the GUI client (21212 by default).
● If you are performing a remote installation with SAPinst and SAPinst GUI running on
different hosts, execute the following command:
sapinstgui -host <remote_host> -port
<port_number_gui_server_to_gui_client>
– where <remote_host> is the name of the remote host, and
<port_number_gui_server_to_gui_client> is the port the GUI server uses to
communicate with the GUI client (21212 by default).
The SAPinst GUI starts and connects to SAPinst.End of: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |
4. Only valid for: z/OS |
Start the SAPinst GUI in one of the following ways:
■ If the SAPinst GUI runs on the same host as SAPinst, enter the following command
without any additional parameters:
./startInstGui.sh
By default, SAPinst GUI uses the local host.
■ If SAPinst runs on a different host from the SAPinst GUI (remote installation), enter the
following command with additional parameters:
./startInstGui.sh -host <host_name>, where <host_name> is the host name of the
installation host
NOTE
● If you enter the command without additional parameters, the SAPinst GUI uses the
local host as default. The SAPinst GUI starts and tries to connect to SAPinst. Since
SAPinst is running on another host, the SAPinst GUI cannot connect and the SAP
Installation GUI Connection dialog appears.
In this case, enter the name of host on which SAPinst is running and choose Log on.
The first screen of the installation appears and you can perform the remote
installation from your local host.
● For a list of options to start the SAPinst GUI, change to the same directory as your
SAPinst executable and enter the command:
./startInstGui.sh -h
End of: z/OS |
7 Additional Information
7.3 Performing a Remote Export Using SAPinst
112/120 PUBLIC 2012-04-12
![Page 113: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/113.jpg)
7.4 Troubleshooting with SAPinst
Procedure
If an export process aborts due to a hardware failure (for example, file system full, power outage,
operating system crash), you have to repeat the export of the complete package. Remove the dump
files <package>.<nnn>, the TOC file <package>.TOC, the log file <package>.log and make sure that
all tables in the TSK file <package>.*TSK* have the status flag 'xeq' or 'err' set.
■ If there is not enough disk space in the export directory, the R3load database export fails. You can
then find error messages in the log files SAP*.log.
You can then move the dump files that have been created from the file system in which the export
directory is located to a different file system during the export. It is currently not possible to
distribute the export over different file systems automatically.
■ If an error occurs during the dialog phase, SAPinst:
● Stops the export.
● Displays a dialog that informs you about the error.
You can now view the log file directly by choosing View Logs.
Finally, you have to abort the export with OK and try to solve the problem.
■ If an error occurs during the processing phase, SAPinst:
● Stops the export.
● Displays a dialog that informs you about the error.
You can now:
● View the log file directly by choosing View Logs.
● Try to solve the problem.
● Continue the export by choosing Retry.
● Abort the export by choosing OK.
Only valid for: UNIX |
■ System Copy - export on UNIX (especially for upgraded systems)
Symptom:
Processes started as <sid>adm or ora<sid> OS users cannot create or open files in the installation
directory.
Reason:
Only members of sapinst UNIX group can access the installation directory. This group is created
by SAPinst as of SAP NetWeaver 7.0 SR1.
Solution:
1. Manually associate <sid>adm and ora<sid> OS users with sapinst group if this association is
missing.
2. Verify the /etc/group file and check if the sapinst group exists and OS users are members
of this group.
7 Additional Information
7.4 Troubleshooting with SAPinst
2012-04-12 PUBLIC 113/120
![Page 114: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/114.jpg)
3. If the sapinst group does not exist yet, start SAPinst. SAPinst will create this group during
startup before the product catalog list is displayed.
4. Edit /etc/group file and associate OS users with sapinst group.
5. Continue with the export.End of: UNIX |
For more information, see Interrupted Installation with SAPinst [page 102] and Performing a Remote Export Using
SAPinst [page 105].
7 Additional Information
7.4 Troubleshooting with SAPinst
114/120 PUBLIC 2012-04-12
![Page 115: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/115.jpg)
A Reference
A Reference
2012-04-12 PUBLIC 115/120
![Page 116: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/116.jpg)
Typographic Conventions
Example Description
<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.
ExampleExample
Arrows separating the parts of a navigation path, for example, menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
http://www.sap.com Textual cross-references to an internet address
/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.
■ Cross-references to other documentation or published works
Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard
116/120 PUBLIC 2012-04-12
![Page 117: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/117.jpg)
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +49/18 05/34 34 34F +49/18 05/34 34 20
www.sap.com
© Copyright 2012 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the United States and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.Oracle and Java are registered trademarks of Oracle and its affiliates.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc.HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.IOS is a registered trademark of Cisco Systems Inc.RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.INTERMEC is a registered trademark of Intermec Technologies Corporation.Wi-Fi is a registered trademark of Wi-Fi Alliance.Bluetooth is a registered trademark of Bluetooth SIG Inc.Motorola is a registered trademark of Motorola Trademark Holdings LLC.Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.
2012-04-12 PUBLIC 117/120
![Page 118: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/118.jpg)
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.
Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides
118/120 PUBLIC 2012-04-12
![Page 119: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/119.jpg)
![Page 120: 702 Guide](https://reader033.fdocuments.us/reader033/viewer/2022050818/55cf9aed550346d033a40b4f/html5/thumbnails/120.jpg)
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com
© Copyright 2012 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.