Summary
Symptom
Which procedure is to be used for data transfer between two R/3 Systems?
Additional key words
Heterogeneous system copy, homogeneous system copy, OS/DB migration, client copy, client transport, Customizing, OS/DB migration service, R3COPY, R3load, export, import, production system, test system, copy, development system
Cause and prerequisites
Case A
You want to make a copy of an R/3 production system to set up a test system. Both systems have the same operating system and database.
Case B
You want to bring a production, test or development system to another operating system or database platform.
Case C
You want to transfer the Customizing settings from a development system to a test system which has already been installed.
There was no productive operation on the development system.
Solution
For the data transfer between two R/3 Systems, the following procedures exist:
1. R/3 System copy
With a system copy, all data of the R/3 System is exported from the database and imported to a new database system which is empty at the beginning.
For a homogeneous system copy (case A) operating system and database system are retained. For a heterogeneous system copy (case B), the operating system or the database are changed. The second case is an OS or database migration.
To support OS/DB migrations (heterogeneous system copies), SAP supplies the OS/DB migration service. The R/3 migration tools must be released with a key for OS/DB migrations. This requires that you purchase the OS/DB migration service. For additional information refer to Note 82478.
a) Database-independent R3load procedure
As of Release 3.0D, system copies can be made available with the R3load procedure by SAP. The program module R3load is integrated in the SAP migration tools R3INST (until Release 3.1) and R3SETUP (as of Release 4.0). For older systems you must carry out an upgrade beforehand.
For heterogeneous system copies (OS/DB migrations) only use the R3load procedure. The migration tools are part of the migration service.
If you use the R3load procedure for a homogeneous system copy, you need an installation package of a higher release then 3.0D with the following database operating system combinations:
* Oracle/UNIX at least Release 3.1I.
We ask you to order, if necessary, this installation package at SAP.
b) Database dependent backup/restore procedures
Database-specific backup/restore procedures (for example R3COPY procedure for Oracle databases) can generally only be used for homogeneous system copies. For the source and the target system binary compatibility must be given. In this case the file system or raw device structure and the hard disk management system are transferred by the source system.
c) Database dependent export import procedures
The export import procedure for Oracle databases is no longer recommended by SAP. It is based on the Oracle tools exp and imp. Their operation was integrated up to Release 3.1 in the SAP installation program R3INST. Instead, use the R3load procedure.
In certain cases, you can use the xload procedure for databases Adabas D to version 6.1. Preferably, the R3load procedure should be used.
d) SAPDBA
The program SAPDBA in general is NOT suitable for a database copy.
The technical procedure for the individual procedures is described in detail in the guides "Homogenous System Copy Guide" and "Heterogenous System Copy Guide" of the respective update level. The "Homogenous System Copy Guide" is delivered in the installation package and is in the PDF format on the export CD 1 up to and including Release 4.0B, as of Release 4.5A on the separate CD 'Installation Guides'.
The "Heterogenous System Copy Guide" is part of the chargeable one migration service. Note the corresponding notes on the homogeneous and heterogeneous system copy.
Note 89698 describes which procedures are supported by SAP to copy from Informix databases.
IMPORTANT !!!
For the system copy you must have the installation package for the R/3 Release platform combinations of your systen copy. You have to order it in time before your system copy.
2. Client transport
Do not use the client copy tools for the migration of production clients. Otherwise you are, for example, no longer able to access change documents and archived data. For details on the client copy tools refer to Notes 19574, 24853, 67205, and 70547.
Header Data
Release Status:
Released on: 07.02.2000 23:00:00
Master Language: 德语
Priority:
Category:
Primary Component: BC-INS
