homogeneous and heterogeneous system copy for sap systems based on sap web application server abap...

8/20/2019 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP Web Application Server ABAP 6.4…

http://slidepdf.com/reader/full/homogeneous-and-heterogeneous-system-copy-for-sap-systems-based-on-sap-web 1/94

SAP NetWeaver ’04 SR1

Installation Guide

Homogeneous and

Heterogeneous

System Copy for

SAP Systems Based

on SAP Web

Application Server

ABAP 6 40 SR1

Document Version 1.70 – May 19, 2006



© Copyright 2004 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, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,

xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,

Tivoli, and Informix are trademarks or registered trademarks of IBM

Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

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.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used

under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and

other SAP products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of SAP AG

in Germany and in several other countries all over the world. 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.

Disclaimer

Some components of this product are based on Java™. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressively 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 Marketplace

You can find this documentation at the following Internet address:service.sap.com/instguides

SAP AG

Neurottstraße 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www sap com



Terms for Included Open

Source SoftwareThis SAP software contains also the third party open source software

products listed below. Please note that for these third party productsthe following special terms and conditions shall apply.

SAP License Agreement for STLport

SAP License Agreement for STLport

between

SAP Aktiengesellschaft

Systems, Applications, Products in Data Processing

Neurottstrasse 16

69190 Walldorf

Germany

( hereinafter: SAP )

and

you

( hereinafter: Customer )

1. Subject Matter of the Agreementa. SAP grants Customer a non-exclusive, non-transferable,

royalty-free license to use the STLport.org C++ library

(STLport) and its documentation without fee.

b. By downloading, using, or copying STLport or any portion

thereof Customer agrees to abide by the intellectual property

laws, and to all of the terms and conditions of this

Agreement.

c. The Customer may distribute binaries compiled with

STLport (whether original or modified) without any

royalties or restrictions.

d. Customer shall maintain the following copyright and

permission notices on STLport sources and its

documentation unchanged:

Copyright 2001 SAP AG

e. The Customer may distribute original or modified STLport

sources, provided that:

• The conditions indicated in the above permission notice

are met;

• The following copyright notices are retained when

present, and conditions provided in accompanying

permission notices are met:

Copyright 1994 Hewlett-Packard Company

Copyright 1996,97 Silicon Graphics Computer

Systems, Inc.

Copyright 1997 Moscow Center for SPARC

Technology.

Copyright 1999,2000 Boris Fomitchev

Copyright 2001 SAP AG

Permission to use, copy, modify, distribute and sell this

software and its documentation for any purpose is

hereby granted without fee, provided that the above

copyright notice appear in all copies and that both that

copyright notice and this permission notice appear in

supporting documentation. Hewlett-Packard Company

makes no representations about the suitability of this

software for any purpose. It is provided "as is" without

express or implied warranty.






supporting documentation. Silicon Graphics makes no

representations about the suitability of this software for

any purpose. It is provided "as is" without express or

implied warranty.

Permission to use, copy, modify, distribute and sell thissoftware and its documentation for any purpose is




supporting documentation. Moscow Center for SPARC



Technology makes no representations about the

suitability of this software for any purpose. It is

provided "as is" without express or implied warranty.

Boris Fomitchev makes no representations about the

suitability of this software for any purpose. This

material is provided "as is", with absolutely no

warranty expressed or implied. Any use is at your own

risk. Permission to use or copy this software for any

purpose is hereby granted without fee, provided the

above notices are retained on all copies. Permission to

modify the code and to distribute modified code is

granted, provided the above notices are retained, and a

notice that the code was modified is included with the

above copyright notice.






supporting documentation. SAP makes no

representations about the suitability of this software for

any purpose. It is provided with a limited warranty and

liability as set forth in the License Agreement

distributed with this copy. SAP offers this liability and

warranty obligations only towards its customers and

only referring to its modifications.

2. Support and Maintenance

SAP does not provide software maintenance for the STLport.

Software maintenance of the STLport therefore shall be not

included.

All other services shall be charged according to the rates for

services quoted in the SAP List of Prices and Conditions and

shall be subject to a separate contract.

3. Exclusion of warranty

As the STLport is transferred to the Customer on a loan basis and

free of charge, SAP cannot guarantee that the STLport is error-

free, without material defects or suitable for a specific application

under third-party rights. Technical data, sales brochures,

advertising text and quality descriptions produced by SAP do not

indicate any assurance of particular attributes.

4. Limited Liability

a. Irrespective of the legal reasons, SAP shall only be liable for

damage, including unauthorized operation, if this (i) can be

compensated under the Product Liability Act or (ii) if caused

due to gross negligence or intent by SAP or (iii) if based on

the failure of a guaranteed attribute.

b. If SAP is liable for gross negligence or intent caused by

employees who are neither agents or managerial employees

of SAP, the total liability for such damage and a maximum

limit on the scope of any such damage shall depend on the

extent to which its occurrence ought to have anticipated by

SAP when concluding the contract, due to the circumstances

known to it at that point in time representing a typical

transfer of the software.

c. In the case of Art. 4.2 above, SAP shall not be liable for

indirect damage, consequential damage caused by a defect or

lost profit.

d. SAP and the Customer agree that the typical foreseeable

extent of damage shall under no circumstances exceed EUR

5,000.

e. The Customer shall take adequate measures for the

protection of data and programs, in particular by making

backup copies at the minimum intervals recommended by

SAP. SAP shall not be liable for the loss of data and its

recovery, notwithstanding the other limitations of the present

Art. 4 if this loss could have been avoided by observing this

obligation.

f. The exclusion or the limitation of claims in accordance with

the present Art. 4 includes claims against employees or

agents of SAP.

Typographic Conventions

Type Style Description

Example Text Words or characters quotedfrom the screen. These includefield names, screen titles,pushbuttons labels, menunames, menu paths, and menuoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, graphic titles, andtable titles

EXAMPLE TEXT Technical names of systemobjects. These include reportnames, program names,transaction codes, tablenames, and key concepts of aprogramming language whenthey are surrounded by body

text, for example, SELECT andINCLUDE.

Example text Output on the screen. Thisincludes file and directorynames and their paths,messages, names of variablesand parameters, source text,and names of installation,upgrade and database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly as

they appear in thedocumentation.

<Example text> Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Librarydocumentation to help you identify differenttypes of information at a glance. For more

information, see Help on Help → GeneralInformation Classes and Information Classesfor Business Information Warehouse on the

first page of any version of SAP Library.



6

Homogeneous and Heterogeneous System Copy for SAPSystems Based on SAP WAS 6.40 SR1.............................................8

1 Planning .............................................................................................10

2 Preparations ......................................................................................14

3 Database-Specif ic Procedures ........................................................18

3.1 Oracle-Specif ic Procedure .................................................................. 19 3.1.1 Generating the Control File Structure.........................................................................21 3.1.2 Preparing the Target System......................................................................................24 3.1.3 Creating an Offline Backup.........................................................................................27 3.1.4 Restoring the Database Files on the Target System..................................................27 3.1.5 Restarting SAPinst......................................................................................................28

3.2 MS SQL Server-Specific Procedure .................................................... 29

3.3 IBM DB2 UDB for UNIX and Windows Specific Procedure ............... 30

3.4 IBM DB2 UDB for z/OS Specific Procedure........................................ 32

3.5 IBM DB2 UDB for iSeries Specific Procedure ....................................33

3.6 Informix-Specif ic Procedure................................................................34

3.7 MaxDB-Specif ic Procedure ................................................................. 35

4 R3load Procedures ...........................................................................38

4.1 R3load Procedure on UNIX..................................................................40 4.1.1 Setting the Library Path Environment Variable...........................................................40 4.1.2 Generation of DDL statements ...................................................................................42 4.1.3 Running SAPinst to Export the Database...................................................................43

4.2 R3load Procedure on Windows........................................................... 47 4.2.1 Generation of DDL statements ...................................................................................48 4.2.2 Running SAPinst to Export the Database...................................................................48

4.3 R3load Procedure on IBM eServer iSeries ......................................... 52 4.3.1 Preparing the Windows Host for the SAP System Installation ...................................52 4.3.2 Preparing a Windows User Account and iSeries User Profile....................................53 4.3.3 Installing TMKSVR and Creating an Installation Share..............................................54 4.3.4 Generation of DDL statements ...................................................................................56 4.3.5 Running SAPinst to Export the Database...................................................................56

4.4 Setting up the Target System.............................................................. 60 4.4.1 Transferring the Export Files to the Target Host ........................................................60 4.4.2 Installing the Target System .......................................................................................61 4.4.3 RELOAD Procedure....................................................................................................62

5 R3load Procedures using the Migration Monitor ...........................63

5.1 R3load Procedure with Migration Monitor on UNIX .......................... 64

5.2 R3load Procedures with Migration Monitor on Windows ................. 65

5.3 Configuring the Import and Export Properties Files ......................... 66

5.4 Starting the Migration Monitor ............................................................75

5.5 Restarting R3load Processes .............................................................. 77



7

5.6 Output Files of the Migration Monitor ................................................78

5.7 Setting up the Target System using the Migration Monitor .............. 79 5.7.1 Installing the Target System Using the Migration Monitor..........................................79

6 Final Act iv it ies ...................................................................................81

6.1 Performing Follow-On Actions in the Source System ...................... 82

6.2 Performing Fol low-On Act ions in the Target System ....................... 83

7 Additional Information......................................................................87

7.1 Remote Installation with SAPinst ....................................................... 88 7.1.1 Starting SAPinst on the Remote Host.........................................................................89 7.1.2 Starting SAPinst GUI on the Local Host .....................................................................90

7.2 Interrupted Installation with SAPinst.................................................. 92



1 Planning

8

Homogeneous and HeterogeneousSystem Copy for SAP Systems Basedon SAP Web AS 6.40 SR1Purpose

When a homogeneous system copy is performed, the target SAP system is installed on thesame operating system and the same database system as the source SAP system. Thecontents of the database are copied from the source to the target system.

During a heterogeneous system copy, the operating system or the database system ischanged. Migration is a synonym for heterogeneous system copy. Familiarize yourself withthe migration procedure. For detailed information, see:

• SAP System Copy & Migration page on SAP Service Marketplace atservice.sap.com/systemcopy .

• SAP OS/DB Migration page on SAP Service Marketplace atservice.sap.com/osdbmigration .

Additionally to the information contained on this page, check the SAP OS/DB MigrationPlanning Guide that is available in the Media Library.

• SAP Note 82478

A homogeneous system copy should only be done by a person withexperience in copying systems and with knowledge of the operating system,

the database, and the ABAP Dictionary. A heterogeneous system copy must be done by a certified system supportconsultant or a certified SAP Technical Consultant.

Create an SAPNet - R/3 Frontend message in the application area BC-INS-UNX (UNIX), BC-INS-NT (Windows), or BC-INS-AS4 (IBM eServer iSeries) ifyou experience problems during the homogeneous system copy.In the case of a heterogeneous system copy (OS/DB migration), create anSAPNet - R/3 Frontend message in the application area BC-INS-MIG if youexperience problems.

Terminology

•

Homogeneous System Copy The copy of the system is installed on the same operating system and database platformas the original system.

• Heterogeneous System Copy

During the copy, either the operating system or the database system is switched, 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 thesystem to which the database copy is to be imported is called the target system. Their

SAP system names are abbreviated to SOURCE_SAPSI D and TARGET_SAPSI D (IBM

1 Planning

9

eServer iSeries: source_<SI D>and t arget _<SI D>). The terms source database and

target database are also used in this description.

• System Copy

Duplication of an SAP system. Certain SAP parameters may change in a copy. When asystem copy is made, all the instances are newly installed, but the database is set upusing a copy of the source system database.

• Database Copy

Database-dependent part of the system copy.

• Placeholders

Placeholders such as <SAPSI D>are used in commands. They are used in the same way

as in the SAP system installation documentation, and must be replaced with the valuesvalid for your site.

The following additional placeholders are used:

Placeholder Meaning How to find out

<S_HOST> System name of the source host Command host name

<T_ HOST> System name of the target host Command host name

<S_SAPSI D> SAP system ID of the source system <SAPSI D>of the original system

<T_SAPSI D> SAP system ID of the target system <SAPSI D>of the target system

<S_DBSI D> Database ID of the source system <DBSI D>of the original system

<T_DBSI D> Database ID of the target system <DBSI D>of the target system

Constraints

• A system copy should only be done by a person with experience in copying systemsand with knowledge of the operating system, the database, and the ABAP Dictionary.

• Client transport is not supported as a system copy method. Transporting productionclients is not supported at all. You can use client transport for the initial set up of a SAPsystem infrastructure. The client copy procedure is not handled in this documentation.

• Export and import of a database with the installation tools for reorganization purposesis not described in this documentation, and is not supported by SAP. Use theappropriate tools for database reorganization.

• 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 Note130906.

• Copying data from SAP R/2 Systems to an SAP system based on SAP Web Application Server ABAP is not described in this documentation. Copying data fromnon-SAP systems to SAP systems is not described in this documentation either.

• If you want to convert a non-Unicode systems to a Unicode systems or perform systemcopy of a Unicode systems, see SAP Note 548016.



1 Planning

10

1 Planning

Purpose

Before you begin with the practical system copy tasks, it is essential to have a planningphase in which you make a number of fundamental decisions that influence the subsequentsystem copy procedure. Careful planning is a prerequisite for the successful system copy ofthe system.

SAP recommends that you make a system copy in order to set up a test, demo, training orstandby system (Oracle and Informix: standby systems cannot be created with a systemcopy). You should perform upgrades in a test system first. This way you can identifycustomer-specific problems which might result from modifications.

The SAP system infrastructure (development, quality assurance and production system) canbe set up without making a system copy as follows:

• Install all SAP systems (begin with the development system). Customize thedevelopment system as described in the implementation documentation.

• Transport the client-dependent and client-independent data to the quality assuranceand production systems.

However, if you do not follow this concept, you can also install a system, customize it andthen perform a system copy.

When copying a system which contains production data it is important to choose the rightmoment for the copy. This could be a month-end or year-end closing. Make sure that there isa well-defined starting point for the data in the new system.

Prerequisites

Read the following SAP Note before beginning the system copy. This notecontains the most recent information regarding the system copy.SAP Note 784931 System Copy for SAP Systems Based on SAP Web AS6.40 SR1 Make sure that you have the most recent version of the note. SAP Notes arelocated on SAP Service Marketplace at service.sap.com/notes.

A consistent system copy can only be ensured if you perform all steps described in thisdocumentation.

The system copy is applicable for:

• Setting up system landscapes (where the SAP systems have different SAPSIDs).

• Creating systems for testing, demonstration, training and standby. Depending on thepurpose of the system, it may be advisable to use the same SAP system name, eventhough the system cannot be included in a system group for transports in this case.

The SAP system release of the source and target systems must be the same.

Process Flow...

1. Obtain the latest versions of the SAP Notes.

2. In the case of a major change in hardware configuration (for example, new machinetype, new hard disk configuration, new file system type), consult your SAP-authorized

hardware partner.



1 Planning

11

3. Create a plan for performing the system copy.

Take into account the downtime of the source system (for preparations and copying)when planning the system copy.

4. Decide which homogeneous system copy method you want to use:

With database-specific tools (tools provided by the database vendor):

Some database vendors offer specific tools for copying a database. These tools allowyou to:

Restore a backup of one database (source DB) in another one (targetDB) (backup method)

Unload the source DB and load the data into the target DB.

With SAP tools (R3load procedure):

The system copy is carried out with SAP tools. This method should be used ifdatabase-specific methods are either not available or not suitable.

Copying an SAP system with these tools is described in section R3load Procedures.

For a heterogeneous system copy, only the R3load procedure is available.

Neither of these methods is supported for all database systems. See the following tableto check which copy methods are available for your database system:

Database OS Platform Available Methods

UNIX Use one of the following:

• The R3load method (see section R3loadProcedure on UNIX).

• The MaxDB backup/restore method [Page 35]

MySQL MaxDB

In thisdocumentation we referto theMySQLMaxDBdatabase asMaxDB fromnow on.

Windows Use one of the following:

• The R3load method (see section R3loadProcedure on Windows).

• The MaxDB backup/restore method [Page 35]

IBM DB2UniversalDatabase foreServer iSeries

eServer iSeries Use the R3load method (see section R3loadProcedure on eServer iSeries) or the Save/RestoreLibrary method (see SAP Note 585277).

IBM DB2UniversalDatabase forUNIX andWindows

UNIX orWindows

Use one of the following:

• The R3load method (see the correspondingsection R3load Procedure on UNIX or R3loadProcedure on Windows)

• The backup method of IBM DB2 UniversalDatabase for UNIX and Windows is supportedfor SAP systems based on SAP Web AS 6.40SR1. For more information, see IBM DB2 UDBfor UNIX and Windows Specific Procedure[Page 30].

1 Planning

12

IBM DB2UniversalDatabase for z/OS

eServer zSeries Use one of the following:

• The R3load method (see section R3loadProcedure on UNIX or R3load Procedure onWindows).

• The IBM DB2 Universal Database for z/OSspecific procedure as described in IBM DB2UDB for z/OS Specific Procedure [Page 32].


• The R3load method (see section R3loadProcedure on UNIX).

• The Informix backup/restore method [Page 34].

Informix


• The R3load method (see section R3load

Procedure on Windows).

• The Informix backup/restore method [Page 34].


• The R3load method (see section R3loadProcedure on UNIX)

• The R3load method with Export/ImportMonitors (see section R3load Procedure with Export/Import Monitors)

• The Oracle backup/restore method (see

section Database-Specific Procedures →

Oracle-Specific Procedure)

Oracle


• The R3load method (see section R3loadProcedure on Windows)

• The Oracle backup/restore method (see

section Database-Specific Procedures → Oracle-Specific Procedure, and SAP Note676468).

• The R3load method with Export/ImportMonitors (see section R3load Procedure with Export/Import Monitors).

MS SQL Server Windows Use one of the following:

• The R3load method (see section R3loadProcedure on Windows)

• The Backup/Restore or Detach/Attach Method

(see section Database-Specific Procedures → MS SQL Server-Specific Procedure).

5. Order the right version of the installation kit before starting the system copy.

6. Choose an SAP system name. The new SAP system name <TARGET_SAPSI D>can

be chosen freely (during a new installation), but to meet the requirements of the



1 Planning

13

Workbench Organizer you must choose different SAP system names for differentsystems.

7. Make sure that the versions of the SAP system and the installation tools are the sameon the target and source systems (exceptions are only allowed if they are described in

an SAP Note).

Several SAP systems can be operated on a single host without encounteringany problems. Nevertheless, SAP recommends that you use a separate hostfor each system because an SAP system upgrade may depend on an OSupgrade. If the SAP systems are on separate hosts, it is possible to upgradethem at different times.

The source system must be in a consistent state before it can be copied.

8. Heterogeneous System Copy: Get Migration Key

If you change the operating system or the database system during the copy(heterogeneous system copy), you need a migration key.You can generate the migration key via SAP Service Marketplace atservice.sap.com/migrationkey . Enter the installation number of your

source system when your are requesting the key.



2 Preparations

14

2 PreparationsBefore you start the system copy, you must perform steps to prepare the procedure.

Organizational Preparations

• Required DVDs

Make sure that all required CDs / DVDs for the system copy are available. You do nolonger require a special migration CD. The tools are located on the SAP InstallationMasterDVD.

In case you want to perform a copy of a non-R/3 SAP system as a pilot project, see SAPNote 543715 (APO, BW), SAP Note 693168 (IMIG) and SAP Note 611232 (releasedCRM/EBP products).

• Tool Versions

Check that you have the appropriate tool versions for your SAP Kernel.• SAP License

Once installation is complete and the SAP system copy has been imported, you willrequire a new license key for the target system. The license key of the source system isnot valid for this system. You can order a new license key for the target system asfollows:

SAP Service Marketplace at service.sap.com .

Remote Connection to SAP support to request help with these tasks. For moreinformation see service.sap.com/remoteconnection .

Telefax

For more information, see SAP Note 94998.

• Archive Files

You must make data archived in the source system (data that does not reside in thedatabase 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.

Refer to the SAP Online Documentation (SAP Library → Cross-Application Components

→ Archiving Application Data) for help.

Access to archive files is platform-independent.

• Configuration Analysis / Hardware Analysis

The following factors have to be determined:

The number of application servers

The expected size of the database

Additional disks or other hardware required

Required memory

See Hardware and Software Requirements Check in the SAP systeminstallation documentation to determine the system requirements.

• Test Run / Schedule



2 Preparations

15

Perform a test run of the system copy. The time taken by the test run is used tocalculate the system downtime:

If your target system will replace your source system, try to perform acomplete test run, meaning that the entire database is exported from the

source system, transferred to the target system and imported there. Approximately system downtime will be equal to the total test time (thatis, time for export, transport and import).

If you do not want to replace your source system, a partial test run(export of entire database or parts of it) may suffice to calculate thesystem downtime. The source system will only be down for the time ofthe export.

Calculating the system downtime is particularly important for very largedatabases (VLDB) or when tapes are being used. The test run is alsodone to determine the amount of export data. You should choose thebest data transfer method (for example, FTP or tape). We recommend toperform read/write actions only on local file systems. Do not use NFS-mounted file systems, as:

Reading from NFS-mounted file systems may fail.

Writing to NFS-mounted file systems may cause corrupted dumps.

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

Technical Preparations

In order to make a consistent copy of the database, it is necessary to prepare the sourcesystem and to carry out some subsequent actions on the target system. This is not necessarywhen performing a test run.

The following list describes important preparatory actions. For further information on SAPsystem administration, see the SAP Online Documentation.

• Preparing the Source System

Before starting a system copy, check the minimal kernel patch level which isrequired by the support package level of the source system. It may benecessary to replace the SAP kernel which is delivered with the kernel CD ofthe installation kit and installed during the installation of the target system by anewer kernel patch level before starting the target system. If you have to replacethe delivered SAP kernel, you can do that after the installation of the centralinstance.

No canceled or pending update requests should be in the system. Check this

via: Tools→ Administration → Monitor → Update (SM13). If canceled or

pending updates exist, these must be updated again or deleted from all clients.You can see whether canceled or pending updates exist by checking if table

VBDATA contains any entries. Proceed as follows in order to find the canceled or

open updates:

i. Call transaction SM13.

ii. Delete the default values for the client, user, and time.

iii. Choose all update requests.

If canceled or pending records exist, then these must be updated againor deleted. Check whether this action was successful using transaction

SE16 for table VBDATA.



2 Preparations

16

Cancel all released jobs: Tools→ CCMS → Jobs → Maintenance. This alsoapplies to the jobs which must run periodically (see SAP Note 16083). Select all

jobs (include start after event): Job → Schedule Job → Cancel.

Adapt the operation mode timetable to make sure that no switching of operating

modes takes place while a system is being copied: Administration → CCMS → Configuration → Operation mode calendar .

Note the logical system names of all clients:...

i. If you plan to overwrite an existing system with a system copy (i.e. thesource and target systems will both exist after the system copy), makesure you note the logical system names of all clients in the system thatwill be overwritten (transaction SCC4). As the logical system names willbe overwritten, in case of differences, they must be changed back to theiroriginal names (as they existed in the system that is overwritten) in thefollow-on actions after the system copy.

ii. BW customers: When planning an SAP BW system copy, read SAP

Note 325525.

iii. If you create a new system with a system copy (i.e., create an upgradetest system), the logical naming strategy for this new system should beconsistent with your existing logical system naming convention. SeeOSS note 184447 if you are still planning your BW system landscape.

iv. If your system copy is used to replace hardware for the DB server,migrate to a different database system or operating system (i.e., sourcesystem for the copy is the same as the copy target), no changes tological system names are required.

Before the export, delete QCM tables from your system. Proceed as follows:...

i. Before deleting you must always check

that the tables are consistent (no restart log or conversion proceduretermination must be displayed)

that the data of the original table is legible

If application programs do not run correctly which use the affectedoriginal table, do not delete the QCM table yet.

ii. Start transaction SE14.

iii. Choose Extras → Invalid temp. table

All QCM tables that can be deleted are displayed.

iv. Mark the tables and delete them.

FI customers: You can perform an additional consistency check by running the

job SAPF190 before the system copy in the source system, as well as after the

copy in the target system, and then comparing the results. No customer data

may be changed in the meantime. ( Accounting→ Financial Accounting →

General ledger → Periodic Processing→ Closing → Check/count → Comparison)

FI customers: You can further check consistency by running the jobs RFUMSV00

(tax on sales/purchases), RAGI TT01 (asset history sheet), RAZUGA01 (asset

acquisitions), RAABGA01 (fixed asset retirements) before the system copy in the

source system, as well as after the copy in the target system, and thencomparing the results. No customer data may be changed in the meantime.



2 Preparations

17

CO customers: You can perform an additional consistency check by running thereport group 1SI P before the system copy in the source system, as well as after

the copy in the target system, and then comparing the results. No customer datamay be changed in the meantime.

Prerequisites for an export:Before performing an export, make sure that:- No upgrade-prepare is performed.- No incremental conversion is in progress.To test if an incremental conversion is in progress, start the transaction ICNV.If there are any table entries in the TICNV, an incremental conversion is inprogress. 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 conver si on’ 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 the button Assi st ant and proceed according to

the Online Documentation.

Only Heterogeneous System Copy: 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 thesetables you will encounter problems while importing the data to your targetsystem because of non NULL capable fields in these tables.



3 Database-Specifi c Procedures

18

3 Database-Specific ProceduresThe following sections describe database-specific procedures for the homogeneous system

copy. Database-specific methods are not available for all database systems. For informationon the availability, see the section Planning [Page 10] in this documentation and check theSAP Service Marketplace for SAP Notes describing the homogeneous system copy for yourdatabase system.

3 Database-Specif ic Procedures

19

3.1 Oracle-Specific Procedure

Purpose

In an SAP system environment, you can create a homogeneous copy of an Oracle databaseby copying database files. This method is suitable for creating an exact copy of an existingdatabase. The source of the copy can be an offline backup or the file system of your sourcehost.

SAPinst is used for the installation on the target system host as described in the installationdocumentation for your SAP component. Only the SAPinst steps for setting up and loadingthe database steps are modified.

As of SAP Web AS 6.40 SR 1, the new OraBRCopy Java tool replaces the former R3COPYshell script. It works on Unix and Windows as well. The tool generates a file CONTROL.SQLinto the current working directory, which can be used without further adaptions on the targetsystem..

The tool is located on the SAP Installation Master DVD:

• Unix:

(<DVD- DI R>: / I M_<xx>/ SAPI NST/ UNI X/ COMMON/ I NSTALL/ ORA/ ORABRCOPY. SAR)

• Windows:

(<DVD- DI R>: \ I M_<xx>\ SAPI NST\ NT\ COMMON\ I NSTALL\ ORA\ ORABRCOPY. SAR)

For a detailed description of the OraBRCopy tool refer to the delivered documentationORABRCopy.pdf which is part of the OraBRCOPY.SAR archive.

Advantages

• Existing offline backups can be used (provided redo logs were cleaned up with forcedlog switches).

• Procedure is faster than the R3load method.

Disadvantages

• Offline backup/copy of database files in a heterogeneous environment is not possible ashardware of the source and target systems must be binary compatible.

• We recommend that you use different host for the source system and the target system.

• SAP system and database must be shut down during offline backup/copy of databasefiles.

• You cannot change the database schema and the tablespace names.

Prerequisites

Make sure that the following requirements are met:

• You use the same Oracle release and patch level for your database in the source andtarget system.

• If you want to upgrade your database from 32-bit to 64-bit, add the following lines at thebottom of the cont r ol . sql file:

shutdown immediate;

startup restrict

20

spool utlirp.log

@?/rdbms/admin/utlirp.sql

spool off

alter system disable restricted session;

• You must have installed JRE version 1.4.1 or higher on your system

• The J AVA_HOME environment variable must point to the JRE directory.

• The classes12.jar must exist in the <ORACLE_HOME>/ j dbc/ l i b di r ect ory

(installed using a standard Oracle installation).

• The backup must be done offline.

• The source and target systems must run on different hosts for security reasons.

• The source and target systems must be binary compatible.

If you use Windows, note that the source or target system must be 32 or 64-bit systems (I386 or IA64). You can copy from 32-bit systems to 64-bitsystems and vice versa.

• UNIX only: The hard disk type and the disk management system of the source andtarget systems must be the same.

• Make sure that all redo log groups are archived.

If your source system uses the US7ASCII character set, you must choose this character setwhen installing the target system. SAPinst prompts for the character set during the installation

(key: Dat abase Char act er 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<schemai d>or sapr 3 with sql pl us and enter: SELECT * FROMV$NLS_PARAMETERS;

Process Flow...

1. Generate the control file structure for the target database on the source system.

2. Prepare the target system.

3. If required, create an offline backup of the source database.

4. Restore the data files, log files, trace file and structure information file on the targetsystem by using the offline backup or by copying the listed files directly from the sourcehost.

5. Restart SAPinst.

Result

You finished this part of the system copy. To complete the system copy, you have to performthe steps in section Final Activities [Page 81].

21

3.1.1 Generating the Control File Structure

Prerequisites

We recommend that you shut down the SAP system before you perform thefollowing steps. The database must still be running.

Procedure...

1. Create an installation directory (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 find the archive in the following directory:

For Unix:

(<DVD-DI R>: / I M_<xx>/ SAPI NST/ <UNI X>/ COMMON/ I NSTALL/ ORA/ ORABRCOPY. SAR)

Windows:

(<DVD-DI R>: \ I M_<xx>\ SAPI NST\ NT\ COMMON\ I NSTALL\ ORA\ ORABRCOPY. SAR)

3. Start the OraBRCopy tool as an OS user with Oracle DBA privileges (user ora<dbsi d>

on UNIX, user <sapsi d>admon Windows):

On UNIX, enter the following commands:

./ora_br_copy.sh –targetSid <TARGET_DBSID> -password <system’s password> -listenerPort <listener port>

On Windows, enter the following commands:

ora_br_copy.bat –targetSid <TARGET_DBSID> -password <system’s password> -listenerPort <listener port>

The tool will create the files CONTROL. SQL, CONTROL. TRC and

i ni t <t ar get SI D>. or a in your installation directory, shutdown and restart the

database and perform the required log switches.

If an error occurs, check the log file:

/ ora. br copy. l og4. Verify and, if necessary, update the CONTROL. SQL control file using the CONTROL. TRC

trace file as follows:




22

Example for Windows

In the following example for Windows, entries of CONTROL.SQL written in boldshould be compared to the trace file:

REM====================================================================

REM CONTROL. SQL

REM

REM SAP AG Wal l dor f

REM Syst eme, Anwendungen und Pr odukt e i n derDatenver arbei t ung

REM

REM ( C) Copyr i ght SAP AG 2004

REM====================================================================

REM Gener ated at :

REM Fr i Sep 17 08: 33: 25 CEST 2004

REM f or t ar get syst em NEW

REM on

REM Wi ndows 2000 5. 0 x86

CONNECT / AS SYSDBA

STARTUP NOMOUNT

CREATE CONTROLFI LE REUSE

SET DATABASE "NEW"

RESETLOGS

ARCHI VELOG

MAXLOGFI LES 255

MAXLOGMEMBERS 3

MAXDATAFI LES 1022

MAXI NSTANCES 50

MAXLOGHI STORY 1134

LOGFI LE

GROUP 1 (

' D: \ ORACLE\ NEW\ ORI GLOGA\ LOG_G11M1. DBF' ,

' D: \ ORACLE\ NEW\ MI RRLOGA\ LOG_G11M2. DBF'

) SIZE 50M ,

GROUP 2 (

' D: \ ORACLE\ NEW\ ORI GLOGB\ LOG_G12M1. DBF' ,

' D: \ ORACLE\ NEW\ MI RRLOGB\ LOG_G12M2. DBF'




23

) SIZE 50M ,

GROUP 3 (

' D: \ ORACLE\ NEW\ ORI GLOGA\ LOG_G13M1. DBF' ,

' D: \ ORACLE\ NEW\ MI RRLOGA\ LOG_G13M2. DBF') SIZE 50M ,

GROUP 4 (

' D: \ ORACLE\ NEW\ ORI GLOGB\ LOG_G14M1. DBF' ,

' D: \ ORACLE\ NEW\ MI RRLOGB\ LOG_G14M2. DBF'

) SIZE 50M

DATAFI LE

' D: \ ORACLE\ NEW\ SAPDATA1\ SYSTEM_1\ SYSTEM.DATA1' ,

' D: \ ORACLE\ NEW\ SAPDATA3\ I MS_1\ IMS.DATA1' ,


' D: \ ORACLE\ NEW\ SAPDATA3\ I MS_3\ IMS. DATA3',







' D: \ ORACLE\ NEW\ SAPDATA1\ I MS640_1\ IMS640.DATA1' ,' D: \ ORACLE\ NEW\ SAPDATA1\ I MS640_2\ IMS640.DATA2' ,

' D: \ ORACLE\ NEW\ SAPDATA1\ I MS640_3\ IMS640.DATA3' ,









' D: \ ORACLE\ NEW\ SAPDATA1\ I MSUSR_1\ IMSUSR.DATA1' ,

' D: \ ORACLE\ NEW\ SAPDATA2\ ROLL_1\ ROLL.DATA1'

;

ALTER DATABASE OPEN RESETLOGS;

ALTER TABLESPACE PSAPTEMP ADD TEMPFI LE' D: \ ORACLE\ NEW\ SAPDATA3\ TEMP_1\ TEMP. DATA1'

SIZE 350M REUSE AUTOEXTEND OFF;

24

This is an example for Windows, but the following changes to be made arevalid for UNIX, too.

Changes to be made:

a. MAXLOGFI LES 255

…The numbers must be greater or equal to the corresponding numbers in the trace file.

b. GROUP 1 (' D: \ ORACLE\ NEW\ ORI GLOGA\ LOG_G11M1. DBF' ,' D: \ ORACLE\ NEW\ MI RRLOGA\ LOG_G11M2. DBF') SIZE 50M ,Gr oup 2 (

…The sizes of the respective groups must be equal to the sizes of the corresponding

groups in the trace file.

c. ' D: \ ORACLE\ NEW\ SAPDATA1\ SYSTEM_1\ SYSTEM.DATA1' ,' D: \ ORACLE\ NEW\ SAPDATA3\ I MS_1\ IMS.DATA1' ,

… ' D: \ ORACLE\ NEW\ SAPDATA1\ I MS640_1\ IMS640.DATA1'

…The count of the data files must be equal to the count of the corresponding data files inthe trace file.

d. ALTER TABLESPACE PSAPTEMP ADD TEMPFI LE' 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.

e. The number of the rows with ALTER TABLESPACE must be equal to the number of the

corresponding rows in the trace file.

3.1.2 Preparing the Target System

Prerequisites

Make sure that the sapdata<n>file systems on the target system host are large enough.

Procedure...

1. Install the target SAP system with SAPinst as described in the installationdocumentation for your SAP component.

When you install the central instance and the database instance, make sure thatyou cannot change the database schema names. The schema names of thesource and target system must be identical.

...

When SAPinst prompts for the installation type, choose:

25

Syst emCopy / Or acl e Backup/ Rest ore.

Install until SAPinst stops to restore the database files on the target system.

The following message is displayed:

SAPi nst now st ops t he i nst al l at i on. Pl ease pr oceed asf ol l ows: . . . .

2. UNIX: Install the Oracle database software on your target system:

a. If necessary, extract the Oracle stage archives manually.

b. Install the Oracle Software as described in the installation documentation foryour SAP component.

3. Create the following directories on the target system, if they do not exist:

UNIX:

/ or acl e/ <TARGET_DBSI D>/ mi r r l og<x>

/ or acl e/ <TARGET_DBSI D>/ or i gl og<x>

/ or acl e/ <TARGET_DBSI D>/ sapdat a<x>

/ oracl e/ <TARGET_DBSI D>/ sapreor g

/ or acl e/ <TARGET_DBSI D>/ saparch

/ oracl e/ <TARGET_DBSI D>/ oraar ch

/ oracl e/ <TARGET_DBSI D>/ sapt r ace

/ oracl e/ <TARGET_DBSI D>/ sapt r ace/ background

/ oracl e/ <TARGET_DBSI D>/ sapt r ace/ user t r ace

/ oracl e/ <TARGET_DBSI D>/ or i gl ogA/ cnt r l

/ oracl e/ <TARGET_DBSI D>/ sapdata1/ cnt r l

/ oracl e/ <TARGET_DBSI D>/ saparch/ cnt r l

/ oracl e/ <Tar get_DBSI D>/ sapcheck

Windows:

<dr i ve>: \ or acl e\ <TARGET_DBSI D>\ mi r r l og<x>

<dr i ve>: \ oracl e\ <TARGET_DBSI D>\ or i gl og<x>

<dr i ve>: \ or acl e\ <TARGET_DBSI D>\ sapdat a<x>

<dr i ve>: \ oracl e\ <TARGET_DBSI D>\ sapreor g

<dr i ve>: \ oracl e\ <TARGET_DBSI D>\ sapar ch

<dr i ve>: \ oracl e\ <TARGET_DBSI D>\ oraar ch

<dr i ve>: \ oracl e\ <TARGET_DBSI D>\ sapt r ace

<dr i ve>: \ oracl e\ <TARGET_DBSI D>\ sapt r ace\ background

<dr i ve>: \ oracl e\ <TARGET_DBSI D>\ sapt r ace\ user t r ace

<dr i ve>: \ oracl e\ <TARGET_DBSI D>\ or i gl ogA\ cnt r l

26

<dr i ve>: \ oracl e\ <TARGET_DBSI D>\ sapdat a1\ cnt r l

<dr i ve>: \ oracl e\ <TARGET_DBSI D>\ saparch\ cnt r l

<dr i ve>: \ oracl e\ <Tar get_DBSI D>\ sapcheck

Note that for Windows, one of the cntrl files can also be located in the

directory <dr i ve>: \ oracl e\ <TARGET_DBSI D>\ sapdat a1\ syst em_1\ cnt r l

4. Make sure that the following directories are empty (except the subdirectorysapar ch/ cnt r l ).

UNIX: / or acl e/ <TARGET_DBSI D>/ saparch and/ oracl e/ <TARGET_DBSI D>/ oraar ch

Windows: <dri ve>: \ oracl e\ <TARGET_DBSI D>\ sapar ch and<dr i ve>: \ oracl e\ <TARGET_DBSI D>\ oraar ch

5. UNIX: All directories must be owned by the user ora<t arget _dbsi d>.

To achieve this enter the following command:

chown ora<target_dbsid>:dba<directory>

6. Windows: For all Oracle directories set the security settings for the built-in accounts

and groups SYSTEM, Admi ni st r at or s , SAP_<SAPSI D>_Gl obal Admi n (domain

installation), and SAP_<SAPSI D>_Local Admi n (local installation) as follows:

a. In the Windows Explorer, right-click the Oracle root directory and chooseProperties.

b. Under Security, choose Advanced.

c. Uncheck Allow inheritable permissions from the parent …. (Windows Server2003), or Inherit from parent the permission entries that apply to child objects(Windows 2000).

d. In the upcoming dialog, choose Copy, to copy the permission entries that werepreviously applied from the parent to this object.

e. Choose OK.

f. Set the permissions for the above-mentioned accounts SYSTEM,

Admi ni st r at or s, SAP_<DBSI D>_Gl obal Admi n, or

SAP_<DBSI D>_Local Admi n to Full Control.

g. Delete all other accounts.

27

3.1.3 Creating an Offl ine BackupCreate an offline backup if required. There are different possibilities to prepare the actual

transfer of the database files:

• If you have an existing offline backup which is up-to-date, you can use it (provided redologs were cleaned up with forced log switches).

• If you want to transport the database file (for example, on tape) or if you have toperform the database shut-down at a certain time, stop the database (normal shut-down) and perform a complete offline backup. You can use the trace fileCONTROL. TRC created by OraBrCOPY to determine the file system trees that have to

be saved.

• Otherwise, stop the database (normal shutdown) and copy the database files when theactual transfer to the target system takes place. You do not have to perform anypreparations for the actual transfer now. Proceed with the next step.

3.1.4 Restoring the Database Files on the TargetSystem

If you do not use an offline backup but copy the database files directly fromthe source to the target system host, make sure that you shut down thedatabase on the source system before you copy the listed files from thesource to the target directories.

...

1. Copy the following files from the source to the target system host either by using anoffline backup or by copying the listed files from the source directories to the targetdirectories:

The table shows the directories on Unix.

For Windows you have the corresponding directories, for example

<dr i ve>: \ oracl e\ <DBSI D>\ sapdat a<x>:

Source and Target Directory Files

/ or acl e/ <DBSI D>/ sapdat a<x> All files

/ oracl e/ <DBSI D>/ or i gl og<x> All files

/ oracl e/ <DBSI D>/ mi r r l og<x> All files

source: 

target: 

CONTROL. SQL

source: target:/ or acl e/ <DBSI D>/ <DB_VERSI ON>_<BI T>/ dbs

i ni t <TARGET_DBSI D>. or a

• If you use an existing offline backup, the source data files and log filesare not located in the directories shown in the table.

• On Windows, the installation directory of the target system is normallylocated in the directory:

28

%progr amf i l es%\ sapi nst _i nst di r \ NW04SR1\ WebAS_ABAP_ORA_NUC\ DB

2. Windows: After you have copied the database files, make sure that the files on thesource and target system are not located in different directories or drives. If required,

make the corresponding changes in the cont r ol . sql and the i ni t <DBSI D>. ora file.

3. UNIX: Verify that the created directories and copied files have the ownerora<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 parameter contr ol _ f i l es of the i ni t <TARGET_DBSI D>. ora file.

3.1.5 Restarting SAPinst

Procedure...

1. Restart SAPinst. Continue as described in the installation documentation for your SAPcomponent.

2. Request a new license key from SAP. For more information, see the installationdocumentation for your SAP component, section Post-Installation Activities - Installingand Using the SAP License and SAP Note 94998.




29

3.2 MS SQL Server-Specific Procedure

Purpose

In an SAP system environment, you can create a homogeneous system copy of an MS SQLServer database by using the backup/restore method or the detach/attach method. For moreinformation, see SAP Notes 193816 and 151603. The SAPinst installation tool supports bothmethods.

The backup/restore method and the detach/attach method have the following advantagescompared to the R3load method:

• You can use an existing backup.

• These methods are much faster than the R3load method.

Process Flow

3. You run SAPinst to install the central instance.

4. You back up or detach the MS SQL Server database that you want to copy.

5. You restore or attach the database on the target database server instance.

6. You download the SAP Tools for MS SQL Server from SAP Service Marketplace at

service.sap.com/msplatforms → Microsoft→ SQL Server .


7. You run SAP Tools for MS SQL Server, choose Migration setup in the root menu, andfollow the dialogs.

Alternatively, you can perform the Postprocessing step of SAP Note 151603. However, this involves many manual steps. It is much easier to make a systemcopy with SAP Tools for MS SQL Server .




30

3.3 IBM DB2 UDB for UNIX and WindowsSpecific Procedure

Purpose

In an SAP system environment, you can create a homogeneous system copy of a DB2database using the backup method or by relocating your database. The relocation of thedatabase is usually used in conjunction with split mirror (for more information, see SAP Note594301 and the DB2 documentation). This section provides information on the backupmethod.

SAPinst is used for the installation on the target system host as described in the installationdocumentation for your SAP component. Only the SAPinst steps for setting up and loadingthe database steps are replaced by a database restore.

Advantages of the Backup Method

• You can use existing offline backups.

• Using the backup method is faster than the R3load method.

Disadvantages of the Backup Method

An offline backup or copy of database files in a heterogeneous environment is not possible asthe hardware of the source and target systems must be binary compatible.

With DB2 UDB for UNIX and Windows, it is possible to use backup imagescross platform for AIX, Solaris and HP-UX.

Prerequisites

• For security reasons, the source and target systems should run on different hosts.

If your source and target system reside on the same host, you have to use theredirected restore or relocate your database.

• The source and target systems should be binary compatible.

• If errors occur when restoring the backup on the target system, the complete restoremust be repeated.

Process Flow...

1. You perform an offline backup or restore an existing backup copy. For the restore ofyour 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 informationsee the IBM DB2 documentation DB2 Command Reference.

Redirected restore

To perform a redirected restore, use tool brdb6br t that retrieves a database backup

and creates a CLP script for the restore of this backup image. For more detailed

information on how to use tool brdb6br t , see the documentation Database

Administration Guide: SAP on IBM DB2 Universal Database for UNIX and Windows section Usage of Tool brdb6brt and the IBM DB2 documentation DB2 Command

Reference.

31

Be aware of the following constraints, when using the backup method for ahomogeneous system copy:

• You cannot change the connect user. During the dialog phase you haveto make sure, that you enter exactly the name of the connect user like youdid on your source system.

• The tablespace names remain the same during the database restore.However, you may change them after the installation.

• If you want to change the container names on the target system, you haveto adapt the container names in the redirected restore script and thenperform a redirected restore. For more information, see thedocumentation Database Administration Guide: SAP on IBM DB2Universal Database for UNIX and Windows, section Usage of Toolbrdb6brt.

2. You run SAPinst to install the central instance.

3. You run SAPinst to install the database instance.

During the installation phase you will be prompted to perform the database restore. Formore information, see SAP Note 784931.

4. Perform the database restore and continue with the installation.

5. If required, you can modify the tablespace names after the installation using thefollowing command:

db2 rename tablespace <old name> to <new name>

db2 rename tablespace <SAPSID_SOURCE>#STABD to<SAPSID_TARGET>#STABD

In addition, you have to update the tablespace names in tables TSDB6, IADB6 andTADB6 using 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)

See also:

• Database Administration Guide: SAP on IBM DB2 Universal Database for UNIX andWindows

• IBM DB2 documentation → DB2 Command Reference




32

3.4 IBM DB2 UDB for z/OS SpecificProcedure

Purpose

In an SAP system environment, you can create a homogeneous system copy of a DB2database using the offline system copy method.

Advantage of the Off line System Copy Method

This method is faster than the R3load method.

Restric tion of the Offline System Copy Method

At the moment, you cannot copy an individual MCOD component to another system. You canonly copy the complete system.

The offline system copy must be performed by an experienced databaseadministrator.





33

3.5 IBM DB2 UDB for iSeries Specific Procedure

Purpose

In an SAP system environment, you can create a homogeneous system copy of a DB2database using the SAV/ RSTLI B system copy method.

Advantage of the Off line System Copy Method

This method is faster than the R3load method.





34

3.6 Informix-Specific Procedure

Purpose

In an SAP system environment, you can create a homogeneous system copy of an Informixdatabase using the backup and restore method. This is possible for databases running onUNIX or Windows operating systems. The SAP installation tool, SAPinst, supports the systemcopy.

Advantages of the Backup and Restore Method

• You can use an existing backup.

• This method is faster than the R3load method.

Disadvantages of the Backup and Restore Method

Source system host and target system host should be different.

Prerequisites

You can find the documentation SAP Database Guide: Informix referred to below at:

help.sap.com → Documentation → SAPNetWeaver → English→ SAP NetWeaver →

Application Platform (SAP Web Application Server) → Databases→ IBM Informix

Process Flow...

1. You back up the Informix database that you want to copy.

For more information on database backup, see the Informix documentation or the SAPdocumentation SAP Database Guide: Informix.

2. You run SAPinst to install the central instance.3. You run SAPinst to install the database instance.

During the installation phase SAPinst prompts you to select the database instanceinstallation method in screen Selecting the Database Instance installation Method.

4. You choose System Copy / Restore of the database using a database specific method.

SAPinst displays the following message and waits for you to perform the restore.

Please restore your Informix database NOW. After you have completed this and thedatabase is online again, press ‘OK’.

5. You restore your Informix database.

For more information on database restore, see the Informix documentation or the SAPdocumentation SAP Database Guide: Informix.

6. If required, you rename your target database system ID, T_DBSI D.

7. You drop the table SAPUSER in the target database system.

8. You choose OK in SAPinst to continue.

35

3.7 MaxDB-Specific Procedure

Purpose

In an SAP system environment, you can create a homogeneous copy of a MaxDB databaseby using the backup and restore method. This method is suitable for creating an exact copyof an existing database. The source of the copy is a complete data backup of your sourcedatabase.

The SAPinst tool is used for the installation on the target system host as described in theinstallation documentation for your SAP component. In SAPinst you select the backup andrestore method as the database installation method. SAPinst stops before the databaseinstance initialization and asks you to perform the recovery on the target database. After youhave performed recovery and post-recovery activities you can continue the installation inSAPinst.

This description is not valid for the liveCache system copy.

Prerequisites

• CPU architecture

You can use the backup and restore method to copy systems to the same CPUarchitecture. That is, you can copy a system based on a swap byte architecture toanother system based on swap byte architecture. You can also copy a RISC-basedsystem to another RISC-based system. For example, the following combinations arepossible:

HP-UX <-> Sun Solaris

Sun Solaris <-> AIX

Windows <-> HP Tru64 Windows <-> Linux

Windows 32-bit <-> Windows 64-bit

However, you cannot copy between the following systems:

HP-UX <-> Windows NT

HP Tru64 <-> Sun Solaris

You can copy backups from 32-bit systems to 64-bit systems.

• Data backup

You perform the complete data backup of your source database.

• Recovery tool

You are using the MaxDB Database Manager (DBMGUI) version 7.5.0 Build 12 or above.

You can find more information on DBMGUI at either of the following:

dev.mysql.com/doc → MaxDB by MySQL → MaxDB Online Library →

Tools

help.sap.com → Documentation → SAPNetWeaver → English → SAP

NetWeaver → Application Platform (SAP Web Application Server) →

Databases → MySQL MaxDB → Tools → Database Manager GUI

• Database software

36

The database software on the target host must have the same version as the software onthe source host. The build number of the software version on the target host must begreater 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 'SELECTUSEDPERM FROM SERVERDBSTATISTICS'

The result of this query is the amount of used space, expressed as the number of 8 KBpages. By dividing this value by 128 you can get the used space expressed in MB. WhenSAPinst prompts you, configure the database data volumes according to this value.

Process Flow...

1. You do the following on the source system:

a. You create a complete data backup using the DBMGUI tool:

DBMGUI → Backup → Backup Wizard → Complete

b. You make the backup medium available on the target host.

2. You do the following on the target system:

a. You start SAPinst to configure the database instance parameters.

SAPinst stops before database initialization and asks you to perform the datarecovery.

b. You start the data recovery wizard from DBMGUI:

i. You register your database instance in the DBMGUIii. You check the database instance is in the admin state.

iii. You choose Recovery → Recovery with Initialization …

iv. In type of recovery you select Restore a medium.

v. You specify the backup medium.

vi. You start the restore procedure.

The recovery wizard does not start the recovery immediately. It initializes thedatabase instance first. It takes some time for the database server to format

the database volumes.c. After the restore, you check the state of the target database instance. Change

the database state to online if it is not already in online state.

d. You delete the entries from the following tables to make sure that informationabout the backup history for update statistics in the Computing CenterManagement System (CCMS) from the old system does not appear in the newsystem:

CNHIST, CNREPRT, CNMEDIA, DBSTATHADA, DBSTAIHADA, DBSTATIADA,DBSTATTADA, SDBAADAUPD

e. Reload the system tables in the target system as follows:

dbmcli -d <NEW_DBSID> -u control,control load_systab -u

superdba,admin -ud domain

37

f. You change the database user SAP<OLD_SI D>to SAP<NEW_SI D>. The name

of the database user must be exactly SAP<SI D>, where <SI D>is the system ID

of the SAP system to be installed. The password of the user must be sap. This

is necessary for the post-installation steps executed by SAPinst.

You change the database user as follows:

dbmcli -d <NEW_DBSID> -u control,control –u SQL superdba,adminsql_execute rename user SAP<OLD_SID> to SAP<NEW_SID>

You change the password of the SAP<SI D>database user as follows:

dbmcli –d <NEW_DBSID> -u control,control –u SQL superdba,adminsql_execute alter password SAP<NEW_SID> sap

g. You continue with SAPinst or restart it if you stopped it during the recovery.

h. After installation is completed you maintain the database connection for CCMS.For more information, see SAP Note 588515.



4 R3load Procedures

38

4 R3load Procedures

Purpose

With the SAP installation tool SAPinst, you can export and import your database in adatabase-independent format. The procedure generates a database export of all SAP objectsthat are defined in the ABAP Dictionary.

Prerequisites

R3load Restrictions

Keep the following restrictions of R3load procedures in mind:

• SAPinst generates a database dump of all SAP objects that are defined in the ABAPDictionary. Other objects are not exported by SAPinst.

• Changes to database objects that cannot be maintained in the ABAP Dictionary(transaction SE14), such as the distribution of tables over severalt abl espaces/dbspaces, are lost after the system copy.

• No indexes longer than 18 characters are allowed on the database to be exported.

• For a consistent database export, no transactions on export-relevant database objectsare allowed during the export. Otherwise, the export has to be restarted. Therefore, it isrecommended to shutdown the SAP system for the export. The database must still berunning.

Considerations concerning the System Copy Tools

• Every installation service (dialog instance installation, for example) must have its ownseparate installation directory whenever you start SAPinst.

• If the target system is already existing and if you do NOT plan to perform a MCODinstallation, delete the database on the target system before the import according tothe corresponding description in section Additional Information of the installationdocumentation for your SAP component.

If the database configuration of your database is stored in the file system, it is advisableto backup these configuration files before deleting the database.

Splitting STR Files

• During the standard system copy process, all tables of the SAP system are groupedinto packages, whereby all tables with the same ‘data class’ belong to the samepackage. The processing unit for one unload/load process is a package. The packages

usually differ in number and size of contained tables, resulting in varying unload/loadruntimes. The overall runtime can be reduced by creating packages of the same ‘size’,that is creating packages with a similar processing time. Splitting the default packages(one package per data class) into more and smaller pieces will help to reach this aim.

• There are several options of how to split packages. For a detailed description of theoptions, see the F1 help about the parameters prompted on the screen Split STR Files while running SAPinst to export the database. The options can be used separately or -when using the new Java based splitting tool - combined.

• 'Splitting of STR Files' is part of the 'Advanced Export Parameters' and is disabled bydefault. If you select the splitting option and unless you did not already perform sometests, using the splitting tool parameters selected by SAPinst is a good starting point.

4 R3load Procedures

39

If you want to split STR file, it is mandatory that EXT files for the targetdatabase system are created before. You will find the EXT files in your exportdump directory, subdirectory DB/<DBTYPE>, for example DB/ORA.

Process Flow

• On UNIX, see R3load on UNIX [Page 40].

• On Windows, see R3load on Windows [Page 47].

• On IBM eServer iSeries, see R3load on IBM eServer iSeries [Page 52]

4 R3load Procedures

40

4.1 R3load Procedure on UNIX

Purpose

This section describes the R3load system copy procedure for Oracle, Informix, IBM DB2 UDBfor UNIX and Windows, IBM DB2 UDB for z/OS, and SAP DB on UNIX platforms.

Process Flow

The R3load procedure consists of the following steps:...

1. Heterogeneous system copy: Generate the migration key via SAP ServiceMarketplace.

You need a migration key for a heterogeneous system copy.You can generate the migration key required for the heterogeneous system

copy via SAP Service Marketplace at service.sap.com/migrationkey .2. Export the source database:

a. Make sure that the QCM tables are deleted from your system [Page 14].

b. IBM DB2 UDB for UNIX and Windows, Informix and Oracle only:Set the library path environment variable [].

c. Generate DDL statements [Page 55].

d. Run SAPinst to export the database [Page 42].

3. Set up the target system [Page 60].

Result


4.1.1 Setting the Library Path EnvironmentVariable

Use

This section is only valid for IBM DB2 UDB for UNIX and Windows, Informix and Oracle.

You need to set the library path environment variable of user r oot before starting SAPinst.

Procedure

As user r oot , set the library path environment variable on your installation host according to

the following tables:

<ORACLE_HOME> is the home directory that you set up for the oracle instance

<DBSI D>: / or acl e/ <DBSI D>/ 920_32 if your operating system is of 32 bit,

or / oracl e/ <DBSI D>/ 920_64 if your operating system is of 64 bit.

Value of Library Path Environment Variable

4 R3load Procedures

41

DBVersion

OperatingSystem

Variable Value

AIX / usr / sap/ <SAPSI D>/ SYS/ exe/ r un: .

Linux (32Bit); LinuxIA64 (64Bit);Solaris

/ usr / sap/ <SAPSI D>/ SYS/ exe/ r un: .

IBMDB2UDB forUNIXandWindows

HP-UX: / usr / sap/ <SAPSI D>/ SYS/ exe/ r un: / opt / I BM/ db2/ V8. 1/ l i b64: .

Informix All UNIXoperatingsystems

/ i nf or mi x/ <SAPSI D>/ l i b: / \i nf or mi x/ <SAPSI D>/ l i b/ esql

HP Tru64UNIX

<sapmnt >/ <SAPSI D>/ exe: \/ <ORACLE_HOME>/ l i b: / or acl e/ cl i ent / \92x_64/ l i b

Linux <sapmnt >/ <SAPSI D>/ exe: \

/ <ORACLE_HOME>/ l i b

Oracle8.1.7

Oracle9.2.0

All otherUNIXoperatingsystems

<sapmnt >/ <SAPSI D>/ exe

Name of Library Path Environment Variable

Operating System Variable Name

AIX LI BPATH

All other UNIX operatingsystems

LD_LI BRARY_PATH

If you are using the Bourne shell (sh):<Variable Name>=<Variable Value> \export <Variable Name>

That is, if your operating system is Linux and your database is Oracle:LD_LIBRARY_PATH=/sapmnt/<SAPSID>/exe: \<ORACLE_HOME/lib

If you restart SAPinst at a later time, make sure the variable is still set.



4 R3load Procedures

42

4.1.2 Generation of DDL statements

Use

To migrate non-standard database objects, you need to generate DDL statements using the ABAP report SMIGR_CREATE_DDL.

You need to follow this procedure before starting SAPinst.

Procedure

4. Log on to the system as system administrator in the productive BW-client.

5. Call transaction SE38 and run the program SMIGR_CREATE_DDL.

6. Select the target database. Depending on the database manufacturer, you might needto select the database version. Value help supports you in the selection of databaseversion. In general, you should not enter a database version that is not available in the

value help.

7. You are able to select Unicode Migration if you also wish to perform Unicode systemcopy (from UC to UC) or a Unicode conversion (from non-UC to UC).

8. Specify an empty working directory to which the files generated by the report will bewritten.

9. Optional: You can restrict the generation of DDL statements to specific table types orindividual tables.

10. Execute the program. The DDL statements are generated and are written to thespecified directory.

If no DB specific objects exists in the database, then no SQL files will begenerated. As long as the report terminates with status ‘successfully’, this isnot an error!

See also:

SAP Note 771209 for additional database specific information.

4 R3load Procedures

43

4.1.3 Running SAPinst to Export the Database

We recommend that you shut down the SAP system before the export. Thedatabase must still be running. Otherwise, the target system may beinconsistent.

Use

This procedure tells you how to run SAPinst to export the database of your SAP system.

The following sections describe a local export, that is, SAPinst and SAPinst GUI run on thesame host.

However, you can also perform a remote export using a standalone SAPinst GUI on aseparate Windows or UNIX host. This enables you to perform the installation on a remotehost while monitoring it with SAPinst GUI from a local host. If you want to perform a remote

installation, also see section Performing a Remote Installation with SAPinst [Page 87].

Prerequisites...

• Make sure that your operating system does not delete the temporary directory TEMP,

TMP, TMPDI R or / t mp and its subdirectories when the system is rebooted.

SAPinst normally creates the installation directory sapi nst_i nstdi r

directly below the temporarydirectory. SAPinst finds the temporary directory by checking the value of the

environment variables TEMP, TMP, or TMPDI R. If no value is set for these

variables, SAPinst uses / t mp as default installation directory.The SAPinst Self-Extractor extracts the SAPinst executables to the temporary

directory, TEMP, TMP, TMPDI R or / t mp. These executables are deleted again

after SAPinst has stopped running.

If SAPinst cannot find a temporary directory, the installation terminates with

the error FCO-00058.

• Make sure that you have at least 50 MB of free space in the installation directory for

each ABAP installation service. In addition, you need 60 ‒ 200 MB free space for the

SAPinst executables. If you cannot provide 200MB free space in the temporary

directory, you can set one of the environment variables TEMP, TMP, or TMPDI R to

another directory with 200 MB free space for the SAPinst executables.

Each SAP instance requires a separate installation directory.

• Make sure that umask is set to 022 for user root . As user root, enter the following

command: umask 022

• If you want to perform a standard, that is, a local installation with SAPinst, theDI SPLAY environment variable to must be set to <host_name>:0.0, where

<host _name>is the host on which the SAPinst GUI will be displayed.

• If required, you can terminate SAPinst and the SAPinst Self-Extractor by pressingCtrl+C.

4 R3load Procedures

44

• If required, delete directories with the name sapi nst _exe. xxxxxx. xxxx after

SAPinst has finished. Sometimes these remain in the temporary directory.

If there are errors with SAPinst Self-Extractor, you can find the Self-Extractorlog file dev_selfex.out in the temporary directory.

We recommend that you keep all installation directories until you are fullysatisfied that the system is completely and correctly installed.

• Oracle only:

Make sure that the password for the database user SAP<SCHEMAI D> or SAPR3 is SAP

and that the password for the database user syst emis manager:

a. Log on as user ora<dbsi d>.

b. If the password of user systemis not manager , enter: brconnect -u system/<passwd> -c –f chpass –o system –p manager

c. Enter: brconnect –c –f chpass -o SAP<SAPSCHEMAID> -p SAP

• IBM DB2 Universal Database for Unix and Windows only:

Before you start the export of existing SAP System, you have to download the current

version of R3szchk from SAP Service Marketplace at the Internet address

servi ce. sap. com/ pat ches and copy it into directory

/ usr / sap/ <SAPSI D>/ SYS/ exe/ r un/ .

Procedure...

1. Log on to your host as user r oot .

2. Mount t he SAP Installation Master DVD.

For more information on mounting DVDs, see section “Mounting a CD / DVD for <yourOS>” in the documentation SAP Web Application Server 6.40 SR 1 ABAP on <your OS>:<your database> Part II - Installation and Post-Installation.

Mount the DVDs locally. We do not recommend using Network File System(NFS) as reading from NFS-mounted DVDs may fail.

3. Start SAPinst from the SAP Installation Master DVD in one of the following ways:

Using the default installation directory (recommended)

Enter the following commands:cd <SAP_Installation_Master_DVD>/IM<x>_<OS>/SAPINST/UNIX/<OS>

./sapinst

SAPinst creates a directory called sapi nst_i nstdi r , which is the current working

directory for your installation, below the temporary directory of your operating system.

Using an alternative installation directory

If you want to use an alternative installation directory, set the environment

variable TEMP, TMP, or TMPDI R.

4 R3load Procedures

45

SAPinst uses the port 21212 during the installation for communication withSAPinst GUI. If this port is already used by another service you must add the

parameter SAPI NST_DI ALOG_PORT=<f r ee_por t _number>to the relevant

sapinst command above. For example:./sapinst SAPINST_DIALOG_PORT=<free_port_number>

SAPinst GUI normally starts automatically by displaying the Welcome screen.

However , i f t her e i s onl y one component t o i nst al l , SAPi nstdi r ectl y di spl ays t he f i r st i nput di al og wi t hout t he Welcome

screen.

4. I n t he Welcome scr een, sel ect ABAP System → <your database> →

<Unicode or non-Unicode> → ABAP Database Content Export.

5. Choose Next.

6. If you generated SQL files with DDL statements (see Generation of DLL Statements

[Page 55]), then copy now the generated files into the SAPinst installation directory.

7. Follow the instructions in the SAPinst input dialogs and enter the required parameters.

To find more information about each parameter, use the F1 key in SAPinst. Ifyou need information about input parameters, position the cursor on the fieldof the respective parameter and choose F1.

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

Troubleshooting

If an export process aborts due to a hardware failure (e.g. filesystem full), youhave to repeat the export of the complete package. Remove the dump files<package>. <nnn>, the TOC file <package>. TOC, the log file

<package>. l og and make sure that all tables in the TSK file

<package>. *TSK* have the status flag ' xeq' or ' er r ' set.

• If there is not enough disk space in the export directory, the R3load database export

will fail. You will then find error messages in the log files SAP*. l og.

You can subsequently move the dump files that have been created from the file system inwhich the export directory is located to a different file system during the export. Currentlythere is no possibility to automatically distribute the export over different file systems.

• If an error occurs during the dialog phase, SAPinst:

Stops the export.

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 export with OK and try to solve the problem.

• If an error occurs during the processing phase, SAPinst:

Stops the export.


You can now:



4 R3load Procedures

46

Directly view the log file by choosing View Logs.

Try to solve the problem.

Continue the export by choosing Retry.

Abort the export by choosing OK.

See also: Continuing an Interrupted Installation [Page 64].



4 R3load Procedures

47

4.2 R3load Procedure on Windows

Purpose

This section describes the R3load system copy procedure for Oracle, Informix, IBM DB2Universal Database for UNIX and Windows, IBM DB2 UDB for z/OS, MS SQL Server andSAP DB on Windows platforms.

Process Flow


1. For a heterogeneous system copy, generate the migration key in the SAP ServiceMarketplace.

You need a migration key for a heterogeneous system copy.

You can generate the migration key required for the heterogeneous systemcopy in SAP Service Marketplace at service.sap.com/migrationkey .

2. Export the source database:...

a. Before the export, delete QCM tables from your system. Proceed as follows:

i. Before deleting you must check that

the tables are consistent (no restart log or conversion proceduretermination must be displayed)

the data of the original table is legible

If application programs do not run correctly which use the affectedoriginal table, do not delete the QCM table yet.

ii. Start transaction SE14.

iii. Choose Extras→ Invalid temp. table

All QCM tables that can be deleted are displayed.

iv. Mark the tables and delete them.

b. Generate DLL-statements [Page 55].

c. Run SAPinst to export the database [Page 48].


Result




4 R3load Procedures

48


Use



Procedure




value help.






See also:



It is recommended to shutdown the SAP system before the export. Thedatabase must still be running. Otherwise, the target system may beinconsistent.

Use...

You use this procedure to run SAPinst to export the database of your SAP system. Thefollowing describes a standard export, that is, SAPinst and SAPinst GUI run on the samehost.

However, you can also perform a remote export using a standalone SAPinst GUI on aseparate Windows or UNIX host. This enables you to perform the installation on a remote

4 R3load Procedures

49

host while monitoring it with SAPinst GUI from a local host. If you want to perform a remoteinstallation, also see section Performing a Remote Installation with SAPinst [Page 87].

Prerequisites...

• SAPinst normally creates the installation directory sapinst_instdir directly below theProgram Files directory. If SAPinst is not able to create sapinst_instdir directly belowthe Program Files directory, SAPinst tries to create sapinst_instdir in the directory, towhich the environment variable TEMP is set.

Each SAP instance requires a separate installation directory.

• The SAPinst Self-Extractor extracts the executables to a temporary directory ( TEMP,

TMP, TMPDI R, or Syst emRoot ). These executables are deleted after SAPinst has

stopped running. Directories with the name sapi nst _exe. xxxxxx. xxxx sometimes

remain in the temporary directory. You can safely delete them.

In the temporary directory you can also find the SAPinst Self-Extractor log file

dev_selfex.out, which might be useful if an error occurs.

• If you want to terminate SAPinst and the SAPinst Self-Extractor, do one of thefollowing:

Right-click the icon for the SAPinst output window located in the Windows trayand choose Exit.

Click the icon for the SAPinst output window located in the Windows tray andchooseFile→ Exit.

• You need at least 50 MB of free space in the installation directory for each ABAP

installation service. In addition, you need 60-200 MB free space for the SAPinstexecutables.

We recommend that you keep all installation directories until the system iscompletely and correctly installed.

If SAPinst cannot find a temporary directory, the installation terminates with

the error FCO-00058.

• Oracle, MS SQL Server, IBM DB2 UDB for UNIX and Windows, IBM DB2 UDB forz/OS:

Before you start the export of an existing SAP system, check if the current version ofR3szchk and R3l dcdl (IBM DB2 UDB for z/OS) is available on your kernel DVD.

If not, download the current file from SAP Service Marketplace at:

ser vi ce. sap. com/ pat ches and copy i t t o di r ect or y\ usr \ sap\ <SAPSI D>\ SYS\ exe\ r un\ .

Procedure...

1. Log on to your host as a user who is a member of the local administration group.

2. Insert the SAP Installation Master DVD in your DVD drive.

3. Double-click sapinst.exe from the following path:

4 R3load Procedures

50

<DVD drive>:\IM<x>_<OS>\SAPinst\NT\<OS>

SAPinst uses the ports 21212 and 21213 during the installation for

communication with SAPinst GUI. You get an error message if one of theseports is already in use. In this case, you must do the following:

• Open a command prompt.

• Change to <DVD drive>:\IM<x>_<OS>\SAPINST\NT\<OS> and run.\sapinst.exe SAPINST_DIALOG_PORT=<port>

where <por t >is an unused port on your host.

4. Select ABAP System → <your database> → <Unicode or Non-Unicode> → ABAPDatabase Content Export and choose Next.

5. If you generated SQL files with DDL statements (see Generation of DLL Statements[Page 55]), then copy now the generated files into the SAPinst installation directory.


If you need more information about input parameters, position the cursor onthe field of the respective parameter and press F1.

If SAPinst prompts you to log off, log off and log on again.The installation restarts automatically.

If you have entered all required information during the dialog phase, SAPinst starts theexport and displays the export progress during the processing phase.

Troubleshooting

If an export process aborts due to a hardware failure (e.g. filesystem full), youhave to repeat the export of the complete package. Remove the dump files<package>. <nnn>, the TOC file <package>. TOC, the log file



• If there is not enough disk space in the export directory, the R3load database export

will fail. You will then find error messages in the log files SAP*. l og.

You can subsequently move the dump files that have been created from the file system inwhich the export directory is located to a different file system during the export. Currentlythere is no possibility to automatically distribute the export over different file systems.

• If an error occurs during the input phase, SAPinst:

Stops the installation.



You must abort the installation with OK and try to solve the problem.




You can now:



4 R3load Procedures

51

Directly view the log file by choosing View Logs.

Try to solve the problem

Retry the installation by choosing Retry.

Abort the installation by choosing OK.

For more information, see Continuing an Interrupted Installation with SAPinst [Page 64].



4 R3load Procedures

52

4.3 R3load Procedure on IBM eServer iSeries

Purpose

This section describes the R3load system copy procedure for IBM DB2 UDB on iSeries.

Process Flow


1. Heterogeneous system copy: Generate the migration key via SAP ServiceMarketplace.

You need a migration key for a heterogeneous system copy.You can generate the migration key required for the heterogeneous systemcopy via SAP Service Marketplace at service.sap.com/migrationkey .

2. Preparing the Windows Host for the SAP System Installation [].

3. Preparing a Windows User Account and iSeries User Profile [Page 53].

4. Installing TMKSVR and Creating an Installation Share [Page 54].

5. Generate DDL statements [Page 55].

6. Running SAPinst to Export the Database [Page 56].

7. Setting up the Target System [Page 60].If youhaveinstalledyour SAPsystemonSAPR/3releaseprior to3.0D, youhavetodeleteQCMtablesfromyour systemasdescribedin SAPNote9385beforetheexport.TargetdatabaseIBMDB2UDBfor OS/390andz/OSonly:

Result

You finished this part of the system copy. To complete the system copy, you have to perform

the steps in the section Final Activities [Page 81].

4.3.1 Preparing the Windows Host for the SAPSystem Installation

Use

The Java-based SAPinst graphical user interface (GUI) called SAPinst GUI requires a JavaDevelopment Kit (Java™ 2 SDK, Standard Edition) with graphical capabilities (AWT, Swing).Since IBM eServer iSeries does not provide a graphical user interface, you must install theJDK on a Windows host to perform the installation with SAPinst.

Prerequisites

To prepare the system for SAPinst and SAPinst GUI you need to do the following:

• Necessary operating system versions: Windows NT/2000/2003/XP

• Check your Java Runtime Environment (JRE) on the host where SAPinst GUI runs,because the JRE cannot be integrated into the SAPinst GUI executable for allplatforms due to licensing issues.

• Set the system path if you install on Windows.

4 R3load Procedures

53

Procedure

The J2EE Engine requires a Java Development Kit (Java™ 2 SDK, Standard Edition).Therefore, make sure a valid JDK version is installed on every host on which you want toinstall an SAP instance including the J2EE Engine.

For more information on the JDK versions that are released for the SAP Web ApplicationServer, SAP components based on SAP Web AS and the J2EE Engine, see SAP Service

Marketplace at service.sap.com/platforms → Product Availability Matrix → SAP

NetWeaver→ SAP NetWeaver ’04 → JSE Platforms.

JDK is not part of the SAP shipment. If necessary, you need to download andinstall it.To check the version of an already installed JDK, enter: java -version

If you have more than one Java Virtual Machine (JVM) installed on yoursystem

(for example, you have two JDKs with different versions installed), make surethat the J AVA_HOME environment variable is set to the valid <J AVA_HOME>directory. Make sure that %J AVA_HOME%\ bi n is included in your system path.

4.3.2 Preparing a Windows User Account andiSeries User Profile

UseFor the installation you need to create a user account on your Windows installation host anda user profile on the iSeries you want to install.

The following requirements apply:

• The iSeries user profile and the Windows user account must have the same name andpassword.

• The iSeries user profile must have user class *SECOFR and all special authorities that

belong to user QSECOFR.

• The Windows user account must have administrator rights on the Windows installationhost.

Procedure

The user name SAPINST and the password SAP are used in the procedures

as examples.

Windows :...Createalocaluser.

i. Create a local user.

ii. In the field User name, enter your installation user name, for example,SAPINST.

iii. In the fields Password and Confirm password, enter the password SAP.

4 R3load Procedures

54

iv. Deselect User must change password at next logon.

v. Assign the new user SAPI NST to group Administrators.

iSeries:

Execute the following command:

CRTUSRPRF USRPRF(SAPINST) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('TestUser for SAP Installation') SPCAUT(*USRCLS)

4.3.3 Installing TMKSVR and Creating an

Installation ShareUse

The TMKSVR is the interface between iSeries and Windows for the installation with SAPinst.

SAPinst is running on Windows, but has to install the product on iSeries. This means that allactions required for iSeries are initiated remotely on Windows but executed locally using the TMKSVR. The communication is done using TCP/IP.

In addition, an installation share on the iSeries host needs to be created and mapped to the

Windows installation host, which is done automatically by the TMKSVR.

The TMKSVR has to be installed and an installation share has to be created on all iSeries

hosts where instances of an SAP system should be installed.

Prerequisites

• An FTP server must be running on iSeries.

• You must prepare a user. For more information on how users are prepared, seePreparing a Windows User Account and iSeries User Profile [Page 53].

• Copy the SAP Installation Master DVD from the DVD drive to the iSeries.

Procedure...

1. Log on to your Windows host as the installation user. For more information, seePreparing a Windows User Account and iSeries User Profile [Page 53].

2. Run SETUP. EXE from the directory I M( x) _OS400_64\ SAPI NST\ AS400\ TMKSVR onthe DVD containing the installation package. You can start the setup program bydouble-clicking it in the Windows Explorer.

To find the SAPinst executable in your platform-specific I M<x>directory,

look in the README.TXT file on the SAP Installation Master DVD.

The following dialog box appears:

4 R3load Procedures

55

3. Enter the following values:

iSeries Hostname

Enter the name of the iSeries host where you want to install TMKSVR.

iSeries Administrator (QSECOFR or similar) Enter iSeries user. For more information, see Preparing a Windows User Account and iSeries User Profile [Page 53].

Update existing TMKSVR instances

Do not select this option.

Yes, create TMKSVR instance Select this option.

TMKSVR instance number

Leave the value at 0.

TMKSVR Instance Port (also referred to as the Dispatcher Port)

Leave the value at 59975, if possible. Only change this port number if you

encounter problems during installation because the port is in use.

Result

The installation uses FTP to install and start the TMKSVR on iSeries. During installation, the

TMKSVR library is created on iSeries. If you want a TMKSVR instance to be created, a library

named TMKSVR<nn>is also created, where <nn>is the instance number (for example,

TMKSVR00).

A NetServer share named ROOTBI N will be created on the iSeries host. You can map it now

to your Windows PC or let SAPinst do it during the installation.

For more information, see the documentation i ns tal l . pdf on the DVD in directory

I M<x>_OS400_64\ SAPI NST\ AS400\ TMKSVR.



4 R3load Procedures

56


Use



Procedure




value help.






See also:



This section refers to “installation of an instance”. This can be viewed as asynonym for “export an SAP system”.

Use

This procedure tells you how to run SAPinst to install one or more SAP instances. It describesan installation where SAPinst GUI and SAPinst server are running on the same Windowshost.

SAPinst creates the installation directory \ usr\ sap\ sapi nst on iSeries.

4 R3load Procedures

57

Prerequisites

• TMKSVR is up and running: WRKACTJ OB SBS ( TMKSVR00) (there must be a DI SPATCH

job). For more information, see Installing TMKSVR and Creating an Installation Share[Page 54].

• The Windows host is set up. For more information, see Preparing the Windows Host forthe SAP System Installation [Page 52].

• The users required for the installation are prepared. For more information, seePreparing a Windows User Account and iSeries User Profile [Page 53].

• Make sure that the J AVA_HOME environment variable is set correctly on your Windows

host.

Procedure...

1. Log on to the Windows host as the installation user. For more information, seePreparing a Windows User Account and iSeries User Profile [Page 53]:

2. Start SAPinst from the SAP Installation Master DVD in one of the following ways:

• Using the default installation directory

sapinst.exe

• in the path <Mapped_Drive>:\<Copied SAP Installation MasterDVD>\IM<x>_OS400_64\SAPINST\OS400\AS400 .

SAPinst uses the port 21212 and 21213 during the installation for communication with theSAPinst GUI. If this port is already used by another service you must add the parameterSAPI NST_DI ALOG_PORT=<f r ee_por t _number>to the relevant sapi nst command

above.

For example:sapinst.exe SAPINST_DIALOG_PORT=<free_port_number>

• Using an alternative installation directory

Change to your installation directory.

Enter the following command to start SAPinst from the SAP Installation MasterDVD: <Mapped_Drive>:\<Copied SAP Installation MasterDVD>\IM<x>_OS400_64\SAPINST\OS400\AS400\sapinst.exe

3. The SAPinst/TMKSVR – Session Parameters dialog box appears and prompts you forthe target iSeries parameters. Enter your values.

4 R3load Procedures

58

The SAPinst GUI now starts automatically by displaying the Welcome screen.

4. In the Welcome screen, select ABAP System <your database> <Unicode or Non-Unicode> ABAP Database Content Export and then choose Next.

5. If you generated SQL files with DDL statements (see Generation of DLL Statements[Page 55]), then copy now the generated files into the SAPinst installation directory.


To find more information on each parameter, use the F1 key in SAPinst. If youneed information about input parameters, position the cursor on the field ofthe respective parameter and press F1.

After you have entered all required input parameters, SAPinst starts the installationand displays the progress of the installation.

When the installation has successfully completed, the screen Finished installation isdisplayed.

Troubleshooting

If an export process aborts due to a hardware failure (e.g. filesystem full), you

have to repeat the export of the complete package. Remove the dump files<package>. <nnn>, the TOC file <package>. TOC, the log file



• If an error occurs during the dialog phase, SAPinst:




Finally you must abort the installation with OK and try to solve the problem.



4 R3load Procedures

59




Try to solve the problem.

Retry the installation by choosing Retry.

Abort the installation by choosing OK.

For more information, see Interrupted Installation with SAPinst [Page 64].

4 R3load Procedures

60

4.4 Setting up the Target System

Purpose

With the SAP installation tool SAPinst you can install the target system and import thedatabase files that you have exported from the source system.

Process Flow

Perform the following actions:...

1. Transfer the export files to the target host. []

2. Install the target system and use the database export to load the database during theinstallation process. [Page 60]

3. If you want to load data from a system into the existing database of another system,perform the RELOAD Procedure [Page 62]

4.4.1 Transferring the Export Files to the TargetHost

Procedure...

1. On the target host, create a directory <EXPDI R>with sufficient space for the database

export files available.

2. Copy all files and directories (recursively) that are located on the source host in themigration export directory from the source host to the target host.

If you transfer the files with ftp, make sure that you use binary mode fortransferring the files <EXPDI R>/ DATA/ *. 00<n>and use ASCII mode for

transferring all other files.

3. Check the permissions of the transferred files on the target host. All files have to beaccessible for user <sapsi d>admof the target system.

4 R3load Procedures

61

4.4.2 Installing the Target System

Make sure there is enough free space on the target system for the databaseload. To find out the size of the export and the sizes of the tablespaces ordbspaces that will be created, look at the file DBSI ZE. XML located in the

directory <DRI VE>: \ <EXPDI R>\ DB\ <DATABASE>(Windows) or

<EXPDI R>/ DB/ <DATABASE> (UNIX).

Procedure...

1. You start SAPinst as described in the installation documentation for your SAPcomponent.

2. To install the target system follow the instructions in the SAPinst input dialogs andenter the required parameters up to the window Selecting the Database Instance

Installation Method. On this screen, you choose System Copy/Migration.


3. When SAPinst displays the CD Browser-Window and asks for the CD Export Migration,

enter the path to the export directory <EXPDI R>.

4. When SAPinst displays the window General Load Parameters, specify the followingsettings:

Migration Key: If you perform a heterogeneous system copy, enter the migrationkey.

General Settings:

Specify the order in which the packages are loaded (alphabetical order,according to the size or custom order)

If you choose Load packages in custom order the additional window DataLoad Options is displayed (see below).

DB code page: You normally do not have to change this value.

Number of parallel jobs: Specify the number of parallel R3loadprocesses.

Advanced Configuration of Packages

If you choose Individual configuration for task file generation the windowTask File Generation Options is displayed.

If you choose Individual configuration for data load the window DataLoad Options is displayed.

Advanced package configuration should only be performed by certifieddatabase administrators. We recommend that you use the default settings ifpossible.

5. Complete the installation as described in the installation documentation for your SAPcomponent.

4 R3load Procedures

62

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

4.4.3 RELOAD Procedure

Use

You want to load data from a system (for example, your productive system) into the existingOracle database of another system (for example, your test system).

The RELOAD service reinstalls the target database while keeping the SAP settings. Data

stored in the target database is deleted. Then, data from the source database is reloaded.

RELOAD is not intended to add additional data (that is, merge data from two databases bykeeping old data and adding new data). After the RELOAD procedure, only data from thesource database is left.

The RELOAD service is not available for MCOD systems. During theRELOAD procedure the database is created again and therefore all data (andall database schemas) is lost.

At the moment, this RELOAD service is available for Oracle databases only.

The RELOAD service cannot be used to refresh any database schema in anMCOD system.

Procedure...

1. Dialog input:

On the screen ABAP System > Database Instance Installation Method, choose SystemCopy / Migration by Reload: Refresh the database content of a non-MCOD system(R3load).

2. Additional input for the procedure:

Before you start the installation of the target system,

To save any changes made to this file, make a backup of the file

i ni t <SI D>. or a located in <ORACLE_HOME>/ dbs .

Delete all entries of the directories saparch and or aar ch in your target

system.

From your old instance, delete all data files located in your sapdat a directories

and all control files.

3. To save your database configuration, proceed as follows after the installation of thenew system has been finished successfully:

Make sure that the parameters of your old i ni t <SI D>. or a file (that you backed up in

step 2) are also contained in the new i ni t <SI D>. or a f i l e that was created by

SAPinst.



5 R3load Procedures using the Migration Monitor

63

5 R3load Procedures using theMigration Monitor

Purpose

The Migration Monitor is a tool which helps you to perform and control the unload and loadprocess during the system copy procedure.

From SAP Web AS 6.40 on the Migration Monitor is integrated into the SAPinst system copytool, but it is also possible to use the monitor for copying older releases by starting itmanually.

The Migration Monitor will

• create R3load command files

• create R3load task files if required

• start the R3load processes to unload the data

• transfer packages from the source to the target host if required

• start the R3load processes to load the data as soon as a package is available

• inform the person performing the system copy in case of errors.

The Migration Monitor has to be started on the source database host (=> Export Monitor) andon the target database host (=> Import Monitor).

The advantage of using the Migration Monitor is, that R3load Procedures run faster.

The Migration Monitor is currently available for Oracle only.

Prerequisites

You have to stick to the same restrictions and considerations that apply to the R3loadprocedures without using Migration Monitor (see Prerequisites of R3load Procedures [Page38]).

In addition, you have to keep the following restrictions in mind:

• The version of your Java Runtime Environment (JRE) on both the export and theimport host must be 1.4.1 or higher.

• The JAVA_HOME environment variable on both the export and the import host mustpoint to the relative JRE directory.

• The correct directory structure for R3load dump files must exist on both the source andtarget host.

Process Flow

• On UNIX, see R3load with Migration Monitor on UNIX [Page 64].

• On Windows, see R3load with Migration Monitor on Windows [Page 65].

64

5.1 R3load Procedure with Migration Monitoron UNIX

Purpose

This section describes the R3load system copy procedure with Migration Monitor for Oracleon UNIX platforms.

Process Flow

The R3load procedure with Migration Monitor consists of the following steps:...

1. Unpack the MI GMON. SAR SAPCAR archive:

The file is located in <SAP I nst al l at i on Mast er DVD> / UNI X/ COMMON/ I NSTALL .

2. Configure the export properties file [Page 66] export _moni t or_cmd. pr oper t i es .

3. Heterogeneous system copy: Generate the migration key on SAP Service Marketplace.

You need a migration key for a heterogeneous system copy.You can generate the migration key required for the heterogeneous systemcopy on SAP Service Marketplace at service.sap.com/migrationkey .


5. Export the source database:


b. Set the library path environment variable [Page 40].

c. Generate DDL statements [Page 55].

d. Run SAPinst to export the database [Page 42].

e. Start the Migration Monitor [Page 75].

f. Check the output files [Page 78] of the Migration Monitor.

Result

You have finished this part of the system copy. To complete the system copy, you have toperform the steps in the Final Activities [Page 81] section.

65

5.2 R3load Procedures with MigrationMonitor on Windows

Purpose

This section describes the R3load system copy procedure with Migration Monitor for Oracleon Windows.

Process Flow

The R3load procedure with Migration Monitor consists of the following steps:...

1. Unpack the MI GMON. SAR SAPCAR archive:

2. The file is located in <SAP Mast er CD> \ NT\ COMMON\ I NSTALL.

3. Configure the export properties file [Page 66] export _moni t or_cmd. pr oper t i es .

4. Heterogeneous system copy: Generate the migration key on SAP Service Marketplace.

You need a migration key for a heterogeneous system copy.You can generate the migration key required for the heterogeneous systemcopy on SAP Service Marketplace at service.sap.com/migrationkey .

5. Build up the target system [Page 60].

6. Export the source database:


b. Generate DDL statements [Page 55].

c. Run SAPinst to export the database [Page 48].

d. Start the Migration Monitor [Page 75].

e. Check the output files [Page 78] for the Migration Monitor.

Result

You have finished this part of the system copy. To complete the system copy, you have toperform the steps in the Final Activities [Page 81] section.




66

5.3 Configuring the Import and ExportProperties Files

Use

You have to configure both the export properties file export _moni t or_cmd. pr opert i es

and the import properties file i mport _moni t or_cmd. pr opert i es as specified in the

tables below.

Options that refer to both scripts:

• Common options

• E-mail options

• Trace options

Options, which concern only the export property file export _moni t or_cmd. pr opert i es :

• Export options

• Network exchange options

• FTP exchange options

• Export socket options

• FTP copy options

Some of these options are mandatory for the Export Monitor.

Options, which concern only the import property file i mport _moni t or_cmd. pr opert i es :

• Import options

• Import exchange options

• Import socket options

Some of these options are mandatory for the Import Monitor.

Features

Help Options

Name Descript ion Comments

help Migration Monitor help

?

The Migration Monitor toolwill display the help on theavailable parameters, if youcall it with either –help or -?

Common Options


monitorTimeout Migration Monitor timeout inseconds

During a timeout, theMigration Monitor threadsleeps and checks every xseconds whether there is

67

work to do.

The normal sleep duration is30 – 120 seconds.

Trace Options


Trace Trace level Possible values:

All, off, 1 (error), 2

(warning), 3 (info), 4 (config,

default), 5, 6, 7 (trace)

Email Options


mai l Server SMTP server Server name or IP address ofthe company SMTP server

mai l From “From” email address

mai l t o “To” email address Can contain an address list

separated by ‘; ’ or spaces.

Export Options

Option Descript ion Comments

expor t Di r s List of export directories Separator on Windows is “; ”,

on UNIX “: ”.

The expor t Di r s parameter

points to the directory wherethe R3load dump files will bewritten to. In the expor t Di r s

directory, the subdirectoriesDATA, DB and

DB/ <t ar get_DBTYPE>(e.g.

DB/ ORA) have to exist.

i nst al l Di r SAPinst start directory The directory where theinstallation tool (SAPinst,R3SETUP) is started; if yourun the Migration Monitorwithout using the installationtools, then the installationdirectory is the directory,where the R3load TSK and logfiles will be written.

omi t R3load omit value (makessense for import only)

68

All options below are for the server mode. The Import Monitor always runs in theserver mode. If you want to run the Export Monitor in the server mode, specify the

parameter ‘Server’ in the Export Monitors properties file.server Server operating mode Running in server mode

means, the Monitor willcreates R3load TSK files (ifnecessary), R3load cmd filesand start the R3loadprocesses.

order By Package order Can be the 'name' or path of

the file that contains packagenames.

r 3l oadExe Path of the R3load executable Optional; the default is R3load.

If only the name of the R3loadexecutable is available, thenJVM looks for the R3loadexecutable using OS-specificprocess search rules.

t skFi l es 'yes ' to create task files; 'no'

to skip

Before version 4.6 must be set

to ‘no’; starting from version

4.7 ‘yes’.

If the R3load task files‘ * . TSK’ already exist then

the monitor will not overwritethem.

ext Fi l es 'yes ' to include EXT files;

'no' to skip

Add EXT file entries to cmdfiles;

If the EXT files cannot befound in/ expDi r s/ DB/ <t arget _DB TYPE>the package

processing is aborted.

Always use ‘extFi l es=no’

for the export!

dat aCodepage Code page for data files See SAP Note 552464.

Possible values: 4102,4103, 1100

t askAr gs Additional R3load argumentsfor the TASK phase

Appended to the R3loadcommand line.

Options already set by themonitor:

- c t f ; - l ; - o (if the omit

argument is specified).

l oadAr gs Additional R3load argumentsfor the LOAD phase


Options already set by the

69

monitor:

- e; - dat acodepage; - l ; - p;

- r ; - socket (if the socket

option is specified); - o (if theomit argument is specified andtask files are not used, that is,the value of the tskFiles optionis no).

expJ obNum Number of parallel export jobs;the default is 1.

Any positive number; 0 for an

unlimited number of jobs.

Network exchange options


net Network operating mode Exported dump files must bevisible on the import host touse this mode.

net ExchangeDi r Network exchange directory Used for communicationbetween the export and ImportMonitors.

Must be writable for ExportMonitor and readable forImport Monitor. The ExportMonitor will write a file<package>. SGN to the

net ExchangeDi r as a signalfor the Import Monitor, that thepackage is exportedsuccessfully and the importcould be started.

FTP exchange options


f tp FTP operating mode Exported dump files will betransferred automatically from

the source host (directoryexpor t Di r s) to the target

host (directory i mpor t Di r s)

using FTP.

f t pHost Remote FTP host Name or IP address of theimport server

f t pUser Name of the remote FTP user The ftpUser specified hereshould be the <sapsi d>admto make sure, that thepackage files can be read byduring the import (which is

started as <sapsi d>adm).

70

f t pPassword Password of the remote FTPuser

Security risk

f t pExpor t Di r s List of remote FTP directories

for export dump

Both ‘; ’ or ‘: ’ separators are

valid.

This is the directory on thetarget host to which the dumpwill be transfered. The valuewill be the same as for‘importDirs’ in the ImportMonitors property file.

f t pExchangeDi r Remote FTP exchangedirectory

Used for communicationbetween the export and ImportMonitors.Must be writable for the ExportMonitor and readable for the

Import Monitor. The ExportMonitor will write a file<package>. SGN to the

ftpExchangeDir as a signal forthe Import Monitor, that thepackage is exportedsuccessfully and the importcould be started.

f t pJ obNum Number of parallel FTP jobs;

the default is 1. Any positive number; 0 for an

unlimited number of jobs.

Export socket options


socket Socket operating mode R3load will not write dumpfiles to the file system but theexport and import workthrough the socket connection.

host Remote import host Name or IP address of theimport host.

port Host port number Must be the same as the portnumber on the import host.

Any free port on the importhost from 1024 to 65535.

FTP copy options


f t pCopy FTP copy operating mode Used as a separate programcall for migration with sockets.

All files produced by R3l ctl

and R3szchk will be

transferred from the source to

71

the target host using FTP.

expor t Di r s List of export directories Separator on Windows: ‘;’Separator on UNIX: ‘:’

In the expor t Di r s directory,

the subdirectories DATA, DBand DB/ <t arget _DBTYPE>(for example DB/ ORA) have to

exist. The R3load STR fileshave to exist in the

subdirectory DATA, the

DDL*. TPL files in the

subdirectory DB, and the

R3load EXT files (if required)in the subdirectoryDB/ <t ar get_DBTYPE>.

f t pHost Remote FTP host Name or IP address of theimport server.

f t pUser Name of the remote FTP user The ftpUser specified here

should be the <sapsi d>admto make sure, that thepackage files can be read byduring the import (which is

started as <sapsi d>adm).

f t pPassword Password of the remote FTPuser

Security risk

f t pExpor t Di r s List of remote FTP directories

for export dump

Both ‘;’ or ‘:’ separators are

valid.This is the directory on thetarget host to which the dumpwill be transfered. The valuewill be the same as for‘importDirs’ in the ImportMonitors property file.

Mandatory options for the Export Monitor

Mode Options

Cl i ent mode: i ns tal l Di r , expor t Di r s,

one of the options f t p, nf s, socket (and their

related parameters)

Ser ver mode: i ns tal l Di r , expor t Di r s, t skFi l es ,

ext Fi l es,

one of the options f t p, nf s, socket (and their

related parameters)

FTP copy expor t Di r s , f t pHost, f t pUser ,

f t pPassword, f t pExpor t Di r s,f t pExchangeDi r

72

The value of the dbType option is determined automatically in the shell

script/batch files from the dbms_t ype environment variable.

Import Options


i mpor t Di r s List of import directories Separator on Windows: ‘; ’

Separator on UNIX: ‘: ’

The i mpor t Di r s parameter

points to the directory with theR3load dump files. In the

i mport Di r s directory, the

subdirectories DATA, DB and

DB/ <t ar get_DBTYPE>(e.g.

DB/ ORA) have to exist.

i nst al l Di r Installation directory Directory where the installationtool (SAPinst, R3SETUP) isstarted; if you run theMigration Monitor withoutusing the installation tools,then the installation directoryis the directory, where theR3load TSK and log files willbe written.

order By Package order This option is used only if theImport Monitor works withoutthe Export Monitor in stand-alone mode, that is, all exportdump files are available on theimport host before the ImportMonitor is started.

Values can be:

name : load packages in

alphabetical order,

si ze : load packages starting

with the largest one,or a path of the file thatcontains package names.

r 3l oadExe Path of the R3load executable Optional; the default is

R3l oad.

If only the name of the R3loadexecutable is available thenJVM looks for the R3loadexecutable using OS-specificprocess search rules.

t skFi l es 'yes ' to create task files; 'no' Before version 4.6, must be

set to ‘no’; starting from

73

to skip version 4.7 ‘yes’.

If task files already exist thenthe monitor does not overwritethem.

ext Fi l es 'yes ' to include EXT files; 'no'

to skip them

Add EXT file entries to cmdfiles;

If the EXT files cannot befound in/ i mpor t Di r s/ DB/ <t ar get _DBTYPE>the package

processing is aborted.

dbCodepage Database code page for thetarget database

See SAP Note 552464.

Possible values: 4102, 4103,1100

mi grat i onKey Migration key

omi t R3load omit value Can contain only 'DTI PV'

letters.

- o D : omit data; do not load

data

- o T: omit tables; do not

create tables

- o I : omit indexes; do not

create indexes

- o P: omit primary keys; do

not create primary keys

- o V: omit views; do not

create views

If you want to combine severalomit options, list these optionswithout blank (for example- o TV).

t askAr gs Additional R3load argumentsfor the TASK phase


Options already used by the

monitor:- c t f ; - l ; - o (when the omit

argument is specified).

l oadAr gs Additional R3load argumentsfor the LOAD phase


Options already used by themonitor:

- i ; - dbcodepage; - l ; - p;

- k; - r ; - socket (if the

socket option is specified); -

o (if the omi t argument is




74

specified and task files are notused, that is, the value oftskFi l es option is no).

i mpJ obNum Number of parallel import jobs;

the default is 1.

Any positive number; 0 for an

unlimited number of jobs

Import exchange options


exchangeDir Exchange directory If this option is not set, thenthe monitor runs in stand-alone mode, that is withoutthe Export Monitor.

All the export dump files or

the SAP export CDs from theinstallation kit must beavailable on the import hostand be specified with theparameter importDirs (for

example, in the propertiesfile).

Import socket options


socket Socket operating modeport Server port number Any free port from 1024 to

65535.

Mandatory options for the Import Monitor

Mode Options

Server mode (default) installDir, importDirs, tskFiles,

extFiles,

one of the options exchangeDir or socket

(and its related parameters)

Stand-alone mode installDir, importDirs, tskFiles,extFiles

The value of the dbType option is determined automatically in the shell

script/batch files from the dbms_t ype environment variable.




75

5.4 Starting the Migration Monitor

Use

The Migration Monitor can be started using:

• UNIX shell scripts expor t _moni t or . sh / i mport _moni t or . sh

• Windows batch files expor t _moni t or. bat / i mport _moni t or . bat

• The JRE java tool (this way is preferable when the command line is generated in anexternal application such as SAPinst).

The application allows you to specify options in the command line or in the export or importproperty files [Page 66]. The names of the property files are export_monitor_cmd.propertiesand 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.

The options specified in the command line take precedence over the corresponding options inthe application property file. Options are case sensitive; any options that are not recognizedare ignored.

To specify an option in the command line, enter -optionName optionValue; in the

application property file, insert a new line optionName=optionValue .

Example of a command line for a UNIX terminal:./export_monitor.sh –ftp./export_monitor.sh –ftpCopy./export_monitor.sh –socket –host import_server –port5000

Example of a command line for Windows cmd. exe:export_monitor.bat –netexport_monitor.bat -socket

Procedure

For the export with Migration Monitor, proceed as follows:...

1. Run the export of the ABAP system.

2. Select the SAPinst option Export using Migration Monitor

3. To specify the correct monitor options, create or edit theexport_monitor_cmd.properties file.

4. If you use FTP access, verify that the required directories exist on the import server

before the Migration Monitor is started. The file i mpor t _di r s. sh or

i mpor t _di r s. bat can be used to create a correct directory structure.

5. To specify the correct monitor options, create or edit the file

export _moni t or_cmd. pr oper t i es .

6. If FTP access is used, verify that the required directories exist on the import server

before the export files are copied to the import server. The script i mpor t _di r s. sh /

the batch file i mpor t _di r s. bat can be used to create the correct directory structure.

76

7. Sockets only: If FTP access is used, transfer all export files to the import server usingthe –f t pCopy monitor option

8. Sockets only: Start the Import Monitor and wait until it starts listening at the specifiedport

9. Start the Migration Monitor as user <sapsi d>admafter the export process has been

started

10. If any export errors occur, restart the Migration Monitor as soon as the problem is fixed.

11. After all packages have been loaded successfully, continue/restart the installation tooland finish the installation.

Using the Export Monitor in parallel with SAPinst:The Export Monitor can be started as an additional tool for the SAPinststandard export process. In this case, the monitor transfers any completedexport packages to the target host.

The Export Monitor can be started in parallel with SAPinst, but only after thedump directories are created on both the export and import server.

For the import with Import Monitor, proceed as follows:...

1. Install the Central Instance.

2. Run the installation of the Database Instance.

If you want to start the installation of the target system before the export of thesource system has been started, make sure that at least the files/ LABEL. ASC and/ DB/ <your dat abase>/ DBSI ZE. {TPL| XML}

/ DB/ DDL<your dat abase>. TPLexi st and cont ai n t he cor r ect dat a

3. Select the SAPinst option Installation using Migration Monitor

4. Create or edit the i mport _moni t or_cmd. pr opert i es file to specify the correct

monitor options.

5. After the exit step, stop SAPinst

6. Sockets only: Make sure that all files on the export server generated by SAPinst (withR3l dct l / R3szchk) are copied to or available on the import server (including all STR,

EXT package-specific files).

7. Start the Migration Monitor as user <sapsi d>adm.

8. If any import errors occur, restart the Migration Monitor as soon as the problem is fixed.

9. After all packages have been loaded successfully, restart or continue with theinstallation tool and finish the installation.

For more information, see the documentation Migration Monitor – User’sGuide on the SAP Installation Master DVD




77

5.5 Restarting R3load Processes

Use

The state file allows package states to be manually updated to restart failed R3loadprocesses.

For example, if package processing failed and the package state has thevalue –, the state can be set to 0 and processing of the package will bestarted again.

Activ it ies

• 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 databasecontent.)

• If the package is currently being processed (the package state is ?), then any manual

modifications of the package state are ignored.

• Sockets only: You cannot restart processes.

78

5.6 Output Files of the Migration Monitor

Use

During the system copy procedure, the Migration Monitor writes to the following log files:

• Export

expor t _moni t or. l og

expor t _st at e. pr oper t i es

• Import

i mpor t _moni t or. l og

i mpor t _st at e. pr oper t i es

Features

The export state file contains package state lines such as:

SAPUSER=++

The format of the line is <PACKAGE>=<STATE>. Possible values for <STATE>are:

0 Package export/import has not started.

? Package export/import is in progress.

- Package export/import has finished with errors.

+ Package export/import has finishedsuccessfully.

If any ftp/net exchange options are used, then the export state file may contain a second<STATE>column, which refers to the state of the package transfer.

Then the export state file contains package state lines such as the following:

SAPUSER=++

The format of the line is <PACKAGE>=<STATE>. Possible values for <STATE>are:

0 Package export has not yet started.

? Package export is in progress

- Package export has finished with errors.

+0 Package export has finished successfully;

package transfer has not yet started.

+? Package transfer is in progress.

+- Package transfer has finished with errors.

++ Package transfer has finished successfully.

79

5.7 Setting up the Target System using theMigration Monitor

Purpose

With the SAP installation tool SAPinst you can install the target system and import thedatabase files that you have exported from the source system.

In addition you have to configure the import scripts [Page 66] and to invoke the MigrationMonitor [Page 75].

Process Flow

Perform the following actions:...

1. Configure the import properties file [Page 66].

2. Install the target system [] and use the database export to load the databaseduring the installation process.

3. Invoke the Migration Monitor [Page 75].

4. Check the output files [Page 78] of the Migration Monitor.

5.7.1 Installing the Target System Using the

Migration Monitor

Prerequisites

Make sure there is enough free space in the target system for the databaseload. To find out the size of the export and the sizes of the tablespaces or

dbspaces that are created, look at the file DBSI ZE. XML located in the

directory <DRI VE>: \ <EXPDI R>\ DB\ <DATABASE>(Windows) or

<EXPDI R>/ DB/ <DATABASE>(UNIX).

Procedure...

1. You start SAPinst as described in the installation documentation for your SAPcomponent.

2. To install the target system follow the instructions in the SAPinst input dialogs andenter the required parameters up to the window Selecting the Database InstanceInstallation Method. On this screen, you choose System Copy/Migration usingMigration Monitor (R3load).


3. When SAPinst displays the CD browser-window and asks for the Export Migration CD,

enter the path to the export directory <EXPDI R>.




80

4. Continue as described in the installation documentation for your SAP component until adialog box appears that states:I f t he export has been st ar t ed on t he sour ce syst emand t heExport Moni t or i s r unni ng, you can now st art t he dat a l oad byst ar t i ng t he I mpor t Moni t or .

5. Check that the prerequisites in the dialog box are fulfilled by your system. If so, you canstart the Migration Monitor.

6. Complete the installation as described in the installation documentation for your SAPcomponent.

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



6 Final Activ ities

81

6 Final ActivitiesTo finish the system copy of your SAP system:...

1. Perform follow-on actions in the source system [Page 82].

2. Perform follow-on actions in the target system [Page 83].



6 Final Activi ties

82

6.1 Performing Follow-On Actions in theSource System...

1. Reschedule your canceled 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 Final Activ ities

83

6.2 Performing Follow-On Actions in theTarget System

Procedure

Actions on Operating System Level...

1. Adapt the configuration files on operating system level to meet network and SAPrequirements.

2. Adapt additional SAP software components (for example, RFC, CPIC, SAP ArchiveLink) if required.

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) ifrequired.

5. Adapt non-SAP directories, file systems, NFS mounts, etc. 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. Oracle: Adapt the database profiles i ni t <SAPSI D>. ora, i ni t <SAPSI D>. dba and

i ni t <SAPSI D>. sap.

Actions on Database Level...

1. Before starting the SAP system, make sure that the logging mechanism of thedatabase is active.

2. Check the parameters in the database profiles.

3. Oracle: Delete all entries from the following tables: DBSTATHORA, DBSTAI HORA,

DBSTATI ORA, DBSTATTORA.

4. Oracle: Delete the user OPS$<SOURCE_SAPSI D>ADM.

5. Oracle: If you changed the <DBSI D>during the system copy, it is recommended to

adapt the global_name parameter with the following SQL command:alter database rename global_name to <NEW_DBSID>;

If the parameter is not existing on your system, ignore this step.

Actions on SAP System Level...

1. Run installation check: Administration → System administration → Administration → Installation Check (transaction SM28).

2. Configure the Workbench Organizer (SE06) with the option Database Copy. This

releases all transport, repair, and customizing requests that have not been released inthe source system.

3. Adapt the transport parameters and transport routes in the Transport Management

System (TMS):

6 Final Activi ties

84

a. Choose transaction STMS → Overview → Systems.

b. Select the system and select the tab Transporttool.

To adapt the transport routes:

Choose transaction STMS → Overview → Transport routes.

4. Delete all entries from the following tables: ALCONSEG, ALSYSTEMS, DBSNP, MONI ,

OSMON, PAHI , SDBAD, SDBAH, SDBAP, SDBAR.

5. Delete canceled and finished jobs.

Execute ABAP program RSBTCDEL, marking the field delete with forced mode: Tools →

ABAP Workbench → ABAP Editor (SE38).

6. Adapt all jobs needed in the target system:

a. Copy the old jobs.

b. Modify the new jobs.

c. Delete the old jobs.

7. Check the consistency of the Temporary Sequential Objects (TemSe) by searching for

files of TemSe objects for which no TemSe objects exist: Administration → CCMS →

Spool → TemSe administration (SP12). For more information, see SAP Note 16875.

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. Delete entries in table DDLOG for buffer synchronization. Synchronize the buffers as

described in SAP Note 36283. Adapt the client information for the logical system.

10. Adapt the RFC destination: Tools→ Administration → Administration → Network→

RFC destinations (SM59). Clean the transactional RFC: Tools→ Administration →

Monitor → Transactional RFC (SM58). See the relevant description in the SAP Online

Documentation.

11. Create new operation modes and remove old ones:...

a. Create new operation modes and instance definitions.

b. Maintain the timetable using the new operation modes.

c. Delete the old operation modes and old instance definitions.

12. Adapt the operation mode time tables (CCMS): Administration→

CCMS→

Configuration → Operation mode calendar (SM63).

13. Adapt the instances and profiles (CCMS): Administration→ CCMS→ Configuration → OP modes/instances (RZ04).

14. Define or remove the SAP system users: Tools → Administration → User maintenance

→ Users (SU01). Furthermore, revise the authorizations of the system users.

15. Delete all entries from tables TPFET and TPFHT. These contain information about

changes made to the profile of your source system: Administration → CCMS →

Configuration → Profile Maintenance (RZ10).

IBM DB2 UDB for iSeries: Use the commands CLRPFM R3<SID>DATA/TPFET and

CLRPFM R3<SID>DATA/TPFHT.



6 Final Activ ities

85

16. Adapt other CCMS settings (for example, alert thresholds, reorganization parameters ofCCMS table MONI) if required.

17. Delete all entries from table TLOCK which holds the repair requests from your sourcesystem.

18. Make data archived in the source system (data that does not reside in the database butwas moved to a different storage location using SAP Archive Management) accessiblein the target system. Adapt the file residence information in the target system. Refer to

the SAP Online Documentation (SAP Web Application Server → System

Administration → Application Data Archiving and Reorganization) for help.

19. Redefine database actions (backup, update statistics, etc.) if you have used the DBAcalendar in the source system (DB13).

20. Check logon groups and assignment of application servers to logon groups (SMLG).

21. Check the connection to SAPNet - R/3 Frontend (OSS1).

22. Check self-defined external commands (SM69).

23. Check the thresholds (RZ06).

24. Check entries of the following tables in all involved systems:

TXCOM(SM54)

THOSTS (SM55)

25. Check the logical system names: Refer to the discussion of logical system names inthe preparation section of this guide [Page 14]. If your circumstance is such that logicalsystem names must be changed in the system that results from the copy, then performthis logical system name change at this time per OSS notes 103228 and 544509. Yourcorporate logical system naming strategy should be observed when making thischange.

BW customers: If you have copied a BW system, read SAP Note 325525.

26. Check for every client in your SAP system the detail settings (client role, changes andtransports for client-dependent objects, changes for client-independent objects,

protection level, restrictions) (SCC4).

27. Check if you can delete clients that will no longer be used in the target system (SCC5).

28. Check the contexts and segments of remote application servers for the SAP MonitoringInfrastructure if required (RZ21).

29. Configure the domain controller in the Transport Management System (TMS) by usingtransaction code STMS.

30. Post-processing concerning customer objects:...

If customer objects are not original in the new system, modify the corresponding entries

in table TADI R.

If you encounter problems modifying a customer development class using transactionSMTS or SM31, try to use the option Validate (ENTER) instead of the option Save tosave your changes.

31. ABAP Program Loads

The ABAP loads are platform-dependent programs which are generated during runtimeand which are stored in database tables. They are not exported when you use theR3load procedure to copy your SAP system. The ABAP loads are generated in the targetsystem when they are first used. This may, however, reduce production system



6 Final Activi ties

86

performance. To avoid this, you can use transaction SGEN to generate the missingloads.

Load generation requires a large amount of system resources. You should schedule thegeneration job to run overnight.

For a detailed description of the features, see the online documentation in transactionSGEN by choosing Information on the SAP Load Generator , or in the Job Monitor bychoosing Job Monitor .

32. If you did not change the database when copying the system, you have to startprogram RS_BW_POST_MIGRATION in the background with variantSAP&POSTMGR. Otherwise, if you changed the database when copying the system,you have to start program RS_BW_POST_MIGRATION in the background with variantSAP&POSTMGRDB. Program RS_BW_POST_MIGRATION performs necessarymodifications on DB specific objects (mainly BW objects)..

Checking the Target System

The following actions are suitable for checking the consistency of the target system:...

1. Perform initial consistency check (SM28).

2. Check the system log on all application servers (SM21).

3. Check the consistency of the database (DB02).

4. Perform server check (SM51).

5. Test transactions frequently used by the customer.

6. 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).7. FI customers: Run the jobs RFUMSV00 (tax on sales/purchases), RAGI TT01 (asset

history sheet), RAZUGA01 (asset acquisitions), RAABGA01 (fixed asset retirements) and

compare the results to those gained on the source system before the system copy.

8. CO customers: Run the report group 1SI P and compare the results to those gained on

the source system before the system copy.



7 Additional Information

87

7 Additional Information

7.1 Remote Installation with SAPinst

88


Purpose

You can run the SAPinst GUI in standalone mode to perform a remote installation.

This enables you to install an SAP system on another host (the remote host) while monitoringthe installation with the SAPinst GUI on your local Windows or UNIX computer (the localhost).

Prerequisites

• Make sure that you have performed the preparation activities for your local host(SAPinst GUI host) and your remote host.

For more information, see Installation Preparations in this documentation.

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

• SAPinst ports

SAPinst uses the port 21212 during the installation for communication with the SAPinstGUI. If one of these ports is already used by another service, SAPinst aborts theinstallation with an appropriate error message.

In this case, you must start SAPinst or the SAPinst GUI from the command prompt asfollows:

In the following commands, <f r ee_por t _number >defines an unused port

number. Since SAPinst also uses <f r ee_por t _number> + 1, this must

also be free.

For example, if you enter 60000 as <f r ee_por t _number >, SAPinst uses

the port 60000.

UNIX:

SAPinst: ./sapinstSAPINST_DIALOG_PORT=<free_port_number>

SAPinst GUI: ./sapinstgui.sh -port <free_port_number>

Windows:

SAPinst: sapinst SAPINST_DIALOG_PORT=<free_port_number>

SAPinst GUI: sapinstgui.bat -port <free_port_number>

Process Flow...

1. You start the SAPinst server on your remote host.

2. You start the SAPinst GUI on your local host.

3. You perform the installation using the SAPinst GUI.

For more information, see:

89

• Starting SAPinst on the Remote Host []

• Starting SAPinst GUI on the Local Host [Page 90]

7.1.1 Starting SAPinst on the Remote Host

Use

You use this procedure to run SAPinst on the remote host when you want to run SAPinst asa remote installation [Page 87]. The remote host is the host where you want to install the SAPsystem.

Prerequisites

You have prepared your system for SAPinst, that is you must have set the DISPLAY

environment variable to <host _name>: 0. 0, where <host _name>is the host on which theSAPinst GUI will be displayed.

Procedure

Your Remote Host Runs on a Windows Platform...

1. Log on to your remote host as a user who is a member of the local administrationgroup.

2. Insert the installation DVD in your DVD drive.

3. Start SAPinst from the SAP Installation Master DVD:

Enter the following commands:

<DVD drive>:\IM<x>_<OS>\SAPinst\NT\<OS>\sapinst.exeSAPINST_START_GUI=false

4. SAPinst now gets started without the SAPinst GUI and waits for the connection to theSAPinst GUI. That is, you see the following at the command prompt:

gui engi ne: no GUI connect ed; wai t i ng f or a connect i on on host<host _name>, por t <por t _number > t o cont i nue wi t h t he i nst al l at i on

5. Start the SAPinst GUI on your local host, as described in Starting SAPinst GUI on theLocal Host [Page 90].

Your Remote Host Runs on a UNIX Platform...

1. Log on to your remote host as user r oot .

2. Mount the SAP Installation Master DVD.

3.

Mount the DVD locally. We do not recommend using Network File System(NFS).

4. Start SAPinst from the SAP Installation Master DVD:

Using the default installation directory

Enter the following commands:cd <SAP_Installation_Master_DVD>/IM<x>_<OS>/SAPINST/UNIX/<OS>

./sapinst SAPINST_START_GUI=false

90

5. SAPinst now gets started without the SAPinst GUI and waits for the connection to theSAPinst GUI. That is, you see the following at the command prompt:

gui engi ne: no GUI connect ed; wai t i ng f or a connect i on on host<host _name>, por t <por t _number > t o cont i nue wi t h t he i nst al l at i on

6. Start the SAPinst GUI on your local host, as described in Starting SAPinst GUI on theLocal Host [].

7.1.2 Starting SAPinst GUI on the Local Host

Use

You use this procedure to run SAPinst GUI on the local host when you want to run SAPinstas a remote installation [Page 87]. The local host is the host where you want to control the

installation with the SAPinst GUI.

Prerequisites

You have prepared your system for SAPinst, that is you must have set the DISPLAY

environment variable to <host _name>: 0. 0, where <host _name>is the host on which the

SAPinst GUI will be displayed.

Procedure

Your Local Host Runs on a Windows Platform...

1. Log on to your local Windows host.

2. Insert the installation DVD into your DVD drive.

3. Change to the following directory:

cd <DVD drive>:\IM<x>_<OS>\SAPinst\NT\<OS>

4. Start the SAPinst GUI in one of the following ways:

With additional parameters:

Enter the following from the Windows command line:

startinstgui.bat host -<host_name> -port <port_number>

<host_name> is the host name of the installation host

<port_number> is the same port as SAPinst uses on the remote host

Without additional parameters:i. Enter the follwing from the Windows command line:

startinstgui.bat

The SAPinst GUI starts and tries to connect to SAPinst on the local host.However, normally there is no SAPinst running on the local host.

Therefore, the SAPinst GUI cannot connect and the SAP Installation GUIConnection dialog appears.

ii. Enter the host name of the Installation Host and the same Port asSAPinst uses on the remote host and choose Log on.

5. Perform the installation from your local host.

91

Your Local Host Runs on a UNIX Platform...

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

2. Mount your installation DVD


3. Change to the following directory:

cd <SAP_Installation_Master_DVD>/IM<x>_<OS>/SAPINST/UNIX/<OS>

4. Start the SAPinst Gui in one of the following ways:

With additional parameters:

Enter the following from the UNIX command line:

./startInstGui.sh –host <host_name> -port <port_number>

<host_name> is the host name of the installation host

port_number> is the same port as SAPinst uses on the remote host

Without additional parameters:

i. Enter the following from the UNIX command line:

startinstgui.sh

The SAPinst GUI starts and tries to connect to SAPinst on the local host.However, normally there is no SAPinst running on the local host.

Therefore, the SAPinst GUI cannot connect and the SAP Installation GUIConnection dialog appears.

ii. Enter the host name of the Installation Host and the same Port asSAPinst uses on the remote host and choose Log on.

5. Perform the installation from your local host.

92

7.2 Interrupted Installation with SAPinst

Use

The SAP system installation might be interrupted for one of the following reasons:

• An error occurred during the processing phase:

SAPinst does not abort the installation in error situations. If an error occurs during theprocessing phase, the installation will hold and a dialog box appears. The dialog boxcontains a short description about the choices listed in the following table as well as a

path to a log file that contains detailed information about the error.

• You interrupted the installation by choosing Cancel.

The following table describes the options in the dialog box:

If youchoose...

Meaning

View Log A frame appears with history information (log files) about the steps that you

performed last . These log files contain a short description of the error that has

occurred. The dialog box will remain in the background, so you can choose one ofthe following two options (Retry or Stop) after viewing the log information.

Retry Since SAPinst records the installation progress in the keydb. xml file, you can

continue the installation by choosing Retry.

The installation continues from the point of failure without repeating any

of the previous steps.

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 again, the dialog box will appear again.

Stop The dialog box and the SAPinst GUI will be closed. The installation stops but

SAPinst records the installation progress in the keydb. xml file. Thus, you can

continue the installation from point of failure without repeating any of the previoussteps. See the procedure below.

Reset You must restart from the beginning, that is, with the default keydb. xml file.

You must delete the previous installation before you restart SAPinst.For more information about deleting a SAP Web AS installation, seeDeletion of an SAP System Installation in the documentationComponent Installation Guide - SAP Web Application Server Java6.40 SR 1 on <OS>: <DB>, Part II — Installation and Post-Installation.

93

UNIX only: You can also terminate SAPinst by choosing Ctrl+C. However, wedo not recommend that you use Ctrl+C, because this kills the processimmediately .

Procedure

The following procedures describe the steps to restart an installation, which you stopped bychoosing Stop, or to continue an interrupted installation after an error situation.

Log on to your remote host as a user who is a member of the local administration group....

1. Insert the installation DVD in your DVD drive.

2. Enter the following commands from the Windows command prompt:

cd <DVD drive>:\IM<x>_<OS>\SAPinst\NT\<OS>

sapinst.exe

3. From the tree structure in the Welcome screen, select the installation task that youwant to continue and choose Next.

If there is only one component to install, SAPinst directly displays the dialogWhat do you want to do? without presenting the Welcome screen.

The What do you want to do? screen appears.

4. In the What do you want to do? screen, decide between the following alternatives andchoose OK.

Al ternative BehaviorRun a newInstallation

The installation will not be continued.

Instead, SAPinst deletes the mentioned installation directory for the choseninstallation service and starts the installation from the beginning.

The log files from the old installation are put into a backup directory with thefollowing naming convention:

<l og_day_mont h_year _hour s_mi nut es_seconds>(for example,

l og_01_Oct _2003_13_47_56).

Continue oldinstallation

The installation that was interrupted is continued from the point of failure.

UNIX

Log on to your local UNIX host as user root.

5. Mount your installation DVD.


6. Enter the following commands:

cd <SAP_Installation_DVD>/IM<x>_<OS>/SAPINST/UNIX/<OS>

./sapinst

7. From the tree structure in the Welcome screen, select the installation task that youwant to continue and choose Next.

If there is only one component to install, SAPinst directly displays the dialogWhat do you want to do? without presenting the Welcome screen.

The What do you want to do? screen appears.

8. In the What do you want to do? screen, decide between the following alternatives andchoose OK.

Al ternative Behavior

Run a newInstallation

The installation will not be continued.

Instead, SAPinst deletes the mentioned installation directory for the choseninstallation service and starts the installation from the beginning.

The log files from the old installation are put into a backup directory with thefollowing naming convention:

<l og_day_mont h_year _hour s_mi nut es_seconds>(for example,

l og_01_Oct _2003_13_47_56).

Continueoldinstallation

The installation that was interrupted is continued from the point of failure.

homogeneous and heterogeneous system copy for sap systems based on sap web application server abap...

Documents