SAP Basis Tech Supports

Symptom
***********************************************************************
* Homogeneous and Heterogeneous System Copy
* for SAP Systems based on SAP NetWeaver 7.0 (2004s) SR2
*
* This SAP Note applies to SAP systems based on SAP NetWeaver 7.0 SR2
* ABAP only, Java only, ABAP+Java.
* This comprises: SAP ERP 2005, SAP CRM 5.0, SAP SRM 5.0, SAP SCM 5.0,
* SAP Solution Manager 4.0
*
***********************************************************************
Other terms
migration r3load jload
Reason and Prerequisites
Problems discovered after publication of the documentation “Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP NetWeaver 7.0 SR2″ on SAP Service Marketplace at http://service.sap.com/installNW70.
Caution:
The Help Portal page for SAP NetWeaver 7.0 has changed. The paths to SAPNetWeaver Library documentation in the installation and upgrade guides still refer to the old structure. If you need to follow a path as described in the guides, you can use the entry to the old SAP NetWeaver Library structure from the following link:
http://help.sap.com/nw70 -> Supplementary Information -> SAP NetWeaver Library [EN] [DE]

Solution
This SAP Note contains the following sections:
1 All Databases: Database-Independent r3load and jload Procedures
2 MaxDB-Specific Procedure
3 MS SQL Server-Specific Procedure
4 Oracle-Specific Procedure
5 IBM DB2 UDB for UNIX and Windows-Specific Procedure
6 IBM DB2 UDB for eServer iSeries-Specific Procedure
7 IBM DB2 UDB for OS/390, z/OS-Specific Procedure
8 Windows-specific Topics
This SAP Note contains information relevant to all released installation
types (usage types, software units) for SAP NetWeaver 7.0 SR2 and Business Suite 2005 SR2 (SAP ERP 2005, SAP CRM 5.0, SAP SRM 5.0, SAP SCM 5.0).
Each entry is marked with a prefix (for example ABAP+Java, BI, SRMLAC, JCRM ) to make clear which installation type the information applies to. If there is no prefix, the information applies to all types.
Released components:
The system copy has been generally released for the ABAP stack.
The system copy has been released for the Java stack – support package stack SP06 or higher – of
SAP Netweaver 7.0 (2004s)SAP CRM 2005SAP ERP 2005SAP SRM 2005SAP SCM 5.0SAP Solution Manager 4.0
with the following exceptions:
DI (Development Infrastructure)
Minimum SPS level for system copy of DI (Development Infrastructure): SPS07PI (Process Integration)
Minimum SPS level for system copy of PI (Process Integration): SPS07

Table of Contents
=================
Date Section description
———————————————————————–
17/JUN/09 1 UPDATE: element.name may cause errors in the
NetWeaver Administrator
(Version 04/MAY/2009 and 28/MAY/09 CHANGED)
25/MAY/09 1 Export error on upgraded system: dbms_type not set
13/MAY/09 3 Extended dbs/mss/server parameter causes
R3load/Jload export failure
02/APR/09 1 NFS-mounted installation directory: Java tools
might not start
12/MAR/09 1 Table Splitting Preparation: Missing *.WHR files
08/JAN/09 3 Jload export fails with java.lang.OutOfMemoryError
08/JAN/09 4 UPDATE:Error in sapinst_dev.log: (…)runCatprocSql
(version 18/SEP/08 CHANGED)
01/DEC/08 3 SQL Server: R3load-import error with Fastloader
06/OCT/08 4 !!!DELETED!!! 08/DEC/05 CJS-00081 Assertion failed: Component OraDbBuild: Context parameter tDirectoryToDriveMapping, no drive for directoryoriglogA found
28/JUL/08 1 System copy of MDMP systems
22/JUL/08 1 Table splitting: export/import using MigMon
19/JUN/08 1 Low performance during DB import
05/JUN/08 1 Follow-Up Activity for UT PI – Integration Server:
Maintain RFC user groups
14/FEB/08 1 Invalid trusted relationships after creating a new
database
08/FEB/08 1 Availability of R3load socket option (changed)
07/DEZ/07 1 ABAP: Follow-up activity for transaction STMS
06/DEC/07 1 Constraint for double-stack systems: no system copy of separate stacks
30/NOV/07 1 Unicode system: table UMGPOCNV contains entries
18/OCT/07 1 Java: Follow-Up Activity for PCK
16/OCT/07 1 ABAP: UNICODE conversion error
10/OCT/07 1 ABAP: SAPinst crashes when custom package order is used
10/OCT/07 1 Java (EP): Path to IMG for Business Intelligence
17/SEP/07 1 Java export (UNIX): Unable to create archive PORTAL.MISC.SAR
28/AUG/07 1 ABAP/Package splitting: extracting SPLIT.SAR terminates with error message
02/AUG/07 1 Java: Server unable to start when migrating from
platforms with IBM JDKs
30/JUL/07 1 Object Checker reports unloaded packages for split tables
18/JUL/07 1 Table splitting restrictions: LRAW and RAW fields
17/JUL/07 1 Using virtual hosts for central and/or DB instances
12/JUL/07 1 Java: FollowUp Activity: Installing the License Key
04/JUN/07 1 Table splitting for tables starting with ‘/’
22/MAY/07 1 Table splitting: ‘/’ characters in column names
15/MAY/07 1 Copying an upgraded system: client 001 missing
15/MAY/07 1 SQL files in export directory need to have read access
15/MAY/07 8 HA (MSCS): Installing a Dialog Instance (changed path on installation DVD)
18/APR/07 4 BW only: Error during “Import ABAP” phase in step “runMigrationMonitor”
08/MAR/07 1 ABAP/Table Splitting: wrong format of input file
15/FEB/07 1 ABAP: RUTSMJOB returns error on view definitions after import
31/JAN/07 1 Java: Follow-Up Activity: Adapt SAP JVM parameters
system copy guide
25/JAN/07 1 R3ta missing on installation master DVD
23/JAN/07 4 Error during system copy with Oracle-specific procedure
05/JAN/07 4 Error in step createTempLicense, iaora, DDLORA.TPL
19/DEC/06 1 Follow-Up Activity: Copy job logs, batch input logs , and spool jobs into the new DIR_GLOBAL directory
04/DEC/05 1 Java Export: error during export of table CAF_GP_R3USRMPGCFG or CAF_GP_IF_CONTEXT
28/NOV/06 5 Export of SAP system
07/NOV/06 1 Heterogeneous BW system copy: Missing P indexes
26/OCT/06 1 Export directory must not end with /DATA
26/OCT/06 8 ABAP/ABAP+Java: Export the database: ABAP Message server needs to be running
04/AUG/06 1 ABAP/HET: Enter Migration Key
24/JUL/06 3 “User tables belonging to the dbo schema were found in the database”; the export stops.
17/JUL/06 5 DBADM privilege on the database is missing
13/JUL/06 4 Win Oracle: Upgrade information
27/JUN/06 1 Template Installer may not be used after a system copy
30/MAY/06 8 Export for Windows X86_64
26/MAY/06 2 Homogeneous MaxDB System Copy: Exporting database statistics
12/MAY/06 1 System copy export with incorrect SP level
09/MAY/06 1 ABAP import fails with ‘invalid migration key’
05/MAY/06 1 Configuration needs to be edited after the target system installation (< SPS9)
20/APR/06 2 System Copy with Target Database MaxDB 7.6
04/APR/06 8 Environment variable SAPSYSTEMNAME to be checked
02/MAR/06 1 J2EE Engine does not start after installation
17/JAN/06 1 System Copy to AMD64, from/to AS/400
15/DEC/05 4 unable to assign default tablespace to user: … ORA-00959: tablespace ‘PSAPSR3USR’ does not exist
13/DEC/05 1 Doublestack export DB2 on Unix: Export Preparation with modified control.xml from SMP
08/DEC/05 1 System copy import fails during ‘unpackSDMKITJAR’
08/DEC/05 4 CJS-00081 Assertion failed: Component OraDbBuild: Context parameter tDirectoryToDriveMapping, no drive for directory origlogA found
30/NOV/05 1 Java system copy: corrupt GZIP trailer
24/NOV/05 1 Java Export: error in SDM call createsdmkitjar
24/NOV/05 1 Java System Copy: Frequent Restart of J2EE Engine on Target Host
10/NOV/05 1 Java System Copy: Missing KM Images
07/NOV/05 1 Java System Copy: Target system installation copying Enterprise Portal (<SP7)
02/NOV/05 1 Java export MaxDB: Output columns too long
02/NOV/05 1 Java Export/HP-UX: remote export required (<SP6)
27/OCT/05 1 Java: KMC Cleanup Script for Content Exchange
25/OCT/05 1 Java Export/UNIX: Error when trying to write to <export dump directory>/JAVA/DB/<DBTYPE>
12/Sep/05 2 Java: Export Restrictions
13/SEP/05 1 Java: Copying NW2004s SP4 on Windows
08/MAY/07 1 Java: Export Distributed System
========================================================================
1All Databases: Database-Independent r3load and jload Procedures
========================================================================

——————CHANGED <D029385, 17/JUN/09>————————–
——————CHANGED <D029385, 28/MAY/09>————————–
————————<D029385, 04/MAY/09>—————————-
element.name may cause errors in the SAP NetWeaver Administrator
Symptom:
After the system copy, the element.name properties of server and dispatcher have wrong custom values, that is, values of the source system:
wrong custom value = Server 0 <sys_nr_of_source_system>_
correct default value = Server 0 <sys_nr_of_target_system>_
Solution:
Use the Config Tool to correct the element.name value:

————————<D033350, 25/MAY/09>—————————-
Export error on upgraded system: dbms_type not set
Symptom:
If you perform an export on an SAP system upgraded from 6.40 to 7.0, the following error may occur:
ERROR ( Last error reported by the step :Caught ESAPinstException in
Modulecall: in component: NW_getDBInfo
step:fillContext at this point the dbtype has to be != ind.).
Solution:
Make sure that the dbms_type environment variable is set in the environment of the SIDADM user before you start the export.

—————————-<D029385, 01/APR/09>——————-
NFS-mounted installation directory: Java tools might not start
If you would rather create an installation directory manually than the default installation directory, make sure that you create it locally. Otherwise, you might experience problems when starting the Java tools.

—————————-<D019527, 12/MAR/09>———————–
Table Splitting Preparation: Missing *.WHR files
Symptom:
During the table splitting preparation, *.WHR files were not created in the export directory <export dump directory>/ABAP/DATA for every table that is to be split.
Solution:
If no *.WHR files could be produced for some of these tables, create fewer packages for these tables
1. Create a new, empty installation directory.2. Define a new, empty export dump directory <temporary dump directory>.3. Run the Prepare Table Splitting service again and provide an input file that contains only the missing tables with a lower number of packages for each defined table.
If the *.WHR files have been created for the missing tables, merge these results with the results from the first Prepare Table Splitting run:
4. Copy the *.WHR files from <temporary dump directory>/ABAP/DATA to <export dump directory>/ABAP/DATA.5. Add the lines from <temporary dump directory>/ABAP/DATA/whr.txt to <export dump directory>/ABAP/DATA/whr.txt.

—————————-<D019527, 28/JUL/08>———————–
System copy of MDMP systems:
PROBLEM:
If you copy an MDMP system using the R3load unload/load method, then youh have to enter ‘MDMP’ as DB code page on the dialog screen ‘General
Load Parameters’ during the import phase. The XML files delivered with the installation pack will not allow to enter non-numeric values (like MDMP) as DB code page.
SOLUTION:
Modify the file dialog.xml as described below.
Either copy the installation master DVD to a local directory and edit the file dialog.xml in the directory IM_<platform>/NW04S/WEBAS/IND before you start the installation orStart the installation as described in the installation guide, abort sapinst when you come to the dialog screen where you have to enter the code page, modify the dialog.xml file in the installation directory, then restart sapinst and ‘continue old installation’.
1. Search for the string ‘fldDbCodepage’ in file dialog.xml.
2. Correct the line three lines further down by removing the
‘type=”numeric”‘ instruction:
OLD: <value maxlength=”4″ minlength=”4″ type=”numeric”/value>
NEW: <value maxlength=”4″ minlength=”4″/value>
3. Repeat step 1.+ 2., because this correction has to be done twice!
—————————-<D029385, 22/JUL/08>————————
Table splitting: perform export/import with MigMon
The export and import has to be performed with the Migration Monitor when the table splitting feature is used.
—————————-<D027120, 19/JUN/08>————————
Low performance during DB import
If you plan to use Advanced Configuration options during the SAP System Database Import, make sure you have installed the most current version of SAPinst to avoid performance problems during the dialog phase. You can find the latest version of SAPinst at http://service.sap.com.
—————————-<D027782, 05/JUN/08>———————–
Follow-Up Activity for UT PI- Integration Server: Maintain RFC user groups
Call transaction RZ12 and change the instance name under Group assignment.
—————————-<D019527, 14/FEB/08>———————– When performing a system copy with R3load, you must set up the trusted/ trusting relationships again. For more information, see Note 128447.
________________________CHANGED <D019527, 08/FEB/08>___________________
________________________CHANGED <D019527, 25/JAN/08>___________________
—————————-<D019527, 25/SEP/07>———————–
Availability of R3load socket option
In chapter 6.1 “R3load Procedure Using the Migration Monitor” the use of R3load’s socket option is restricted to non-Unicode systems. This is not correct.You can use the Socket option, if your R3load has at least patch level 73 (compile date: 12.01.2008).
—————————-<D019527, 07/DEZ/07>———————–
ABAP: Follow-up activity for Transport Management System: Configure the Transport Management System (transaction STMS). If you did not change the SAPSID during the system copy, all open transport, repair and customizing requests that have not been released in the source system will not be released automatically.
—————————-<D037196, 06/DEC/07>———————–
As of SAP NetWeaver 7.0, when your system is a double-stack system and you perform a system copy, your source system is copied to the target system as a whole. This means, that it is neither possible to exclude a single stack from the system copy nor to copy a separate stack only.
————————–<D040933, 30/NOV/07>————————-
Symptom:
You have a Unicode system and table UMGPOCNV contains one or several entries.
Solution:
See SAP Note 1119611.
————————–<D027782, 18/OCT/07>————————–
Java: Follow-Up Activity for Partner Connectivity Kit (PCK)
You have to perform the following follow-up activity if you are running a PCK on the Java stack. The file named aii.properties resides in the file system of the source system and needs to be copied manually to the target system as described in SAP Note 746328.
————————-<D019130,16/OCT/07>—————————-
ABAP: UNICODE conversion error
Symptom:
During the import into a UNICODE system the following error occurs
(for example in the SAPCLUST.log):
myCluster (63.2.Imp): 2085: (Warning:) inconsistent field names(source):physical field K1N05 appears as logic K1N5.
myCluster (63.2.Imp): 2086: (Warning:) further investigation recommended
myCluster (63.2.Imp): 1924: error when checking key field consistency for logic table TACOPC .
myCluster (63.2.Imp): 1927: logic table is canonical.
myCluster (63.2.Imp): 1930: received return code 2 from c3_uc_check_key_field_descr_consistency.
myCluster (63.2.Imp): 1224: unable to retrieve nametab info for logic table TACOPC .
myCluster (63.2.Imp): 8032: unable to acquire nametab info for logic table TACOPC .
myCluster (63.2.Imp): 2807: failed to convert cluster data of cluster item.
myCluster: CLU4 **00001**
myCluster (63.2.Imp): 319: error during conversion of cluster item.
myCluster (63.2.Imp): 322: affected physical table is CLU4.
(CNV) ERROR: code page conversion failed rc = 2
———————————————————-
|
| RSCP – Error
| Error from: Codepage handling (RSCP)
| code: 128 RSCPENOOBJ No such object
| Dummy module without real rscpmc[34]
| module: rscpmm no: 2 line: 75 T100: TS008
| TSL01: CPV p3: Dummy-IPC p4: rscpmc4_init
`———————————————————-
Cause:
This problem is caused by incorrect data which should have been removed from the source system before the export.
Solution:
There are two possible workarounds:
1. Modify DDL<dbs>.TPL (<dbs> = ADA, DB2, DB4, DB6, IND, MSS, ORA) BEFORE the R3load TSK files are generated;
search for the keyword “negdat:” and add “CLU4″ and “VER_CLUSTR” to thisline.2. Modify the TSK file (most probably SAPCLUST.TSK) BEFORE R3load import is(re-)started.
search for the lines starting with “D CLU4 I” and “D VER_CLUSTR I” and change the status (i.e. “err” or “xeq”) to “ign” or remove the lines.
————————-<D041724, 10/OCT/07>————————–
ABAP: SAPinst crashes when custom package order is used
Symptom:
If custom package order is chosen for ABAP export/import and the amount of split R3load packages is significant (more then 100), SAPinst crashes.
The error occurs in step ‘configurePackageOrder’ with the following error message:
input buffer overflow, can’t enlarge buffer because scanner uses REJECT
Solution:
1. In the control.xml file, replace the following lines (2 occurrences in the file):
client. createClientParameter(”lbTableText”, “(’” + tableText + “‘)”);
with:
client. createClientParameter(”lbTableText”, “(’” + “abc” + “‘)”);
installer.writeTrace(”lbTableText: mapping done”);2. Re-run the export/import with the modified control.xml file.
————————<D038283, 10/OCT/07>————————–
EP: Basic Configuration for BI Java
Solution:m copy guide does not state the correct path to the IMG for BI.
Call transaction SPRO and choose “SAP Reference IMG” to display the structure for SAP NetWeaver BI.
————————-<D037196, 17/SEP/07>————————–
Java export (UNIX): Unable to create archive PORTAL.MISC.SAR
The export of the file system components of the central instance may abort with the following error message:
MUT-03011 Execution of the command “/tmp/sapinst_exe.0622747474/SAPCAR -c -v -g -i -C /usr/sap/C11/DVEBMGS00/j2ee -f /<export dir on NFS>/JAVA/APPS/PORTAL/PORTAL.MISC.SAR portal_misc/uninstall” finished with return code 6. Output:
SAPCAR: error opening <export dir on NFS>/JAVA/APPS/PORTAL/PORTAL.MISC.SAR
ERROR 2007-07-07 7:07:07
FCO-00011 The step archivePortalMisc with step key |NW_Export|ind|ind|i
nd|ind|0|0|NW_Java_Export_Dialog|ind|ind|ind|ind|5|0|NW_JAVA_Export_APPS
|ind|ind|ind|ind|4|0|NW_JAVA_Export_Portal|ind|ind|ind|ind|0|0|archivePo
rtalMisc was executed with status ERROR .
The <sid>adm user has no write permission in
<export dir on NFS>/JAVA/APPS/PORTAL, if it is mounted via NFS and the group sapinst does not exist on the NFS server.
Solution:
Invoke
chgrp -R sapsys <export dir on NFS>/JAVA/APPS
and continue the export

————————-<D019527, 28/AUG/07>————————–
ABAP/Package splitting: extracting SPLIT.SAR terminates with error msg.
If package splitting is configured, the archive SPLIT.SAR has to be extracted. The extraction terminates with an error, although the archive has been extracted completely:
SAPCAR: error reading from <path to SPLIT.SAR archive>
Solution:
Ignore the error message and repeat the SAPinst step which has stopped with the error. As the archive has already been extracted, SAPinst will not try again to extract it and therefore will continue with the next step.
————————-<D037196, 02/AUG/07>————————–
Java: Server unable to start when migrating from platforms with IBM
JDKs
When migrating from platforms with IBM JDKs (e.g AIX) to a platform
with e.g. Sun JDK, the application server Java may fail to start after
the system copy with the following error in dev_bootstrap (which can be
found in $(DIR_INSTANCE)/work):
Unrecognized option: -Xj9
[Thr 2960] *** ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-1) [
[Thr 2960] *** ERROR => Cannot load Java VM (server) (rc=-1) [jlnchxxi.c
[Thr 2960] *************************************************************
*** ERROR => Java VM initialization failed.
*** Please see SAP Note 943602 , section ‘Java VM initialization issues’
*** for additional information and trouble shooting.
**********************************************************************
[Thr 2960] JLaunchCloseProgram: good bye (exitcode = -1)
Solution:
1. Apply SAP note 8318122. Start the GUI ConfigTool and remove the XJ9 parameter from the
bootstrap settings for the instance, dispatcher and server.3. Edit the file $(DIR_INSTANCE)/j2ee/cluster/instance.properties and
remove the XJ9 setting from the bootstrap*.JavaParameters properties
as well.

————————-<D019527, 30/JUL/07>—————————
Object Checker reports unloaded packages for split tables
Symptom:
After the data import SAPinst displays a popup with the warning that not loaded packages have been found by the Object Checker.
The Object Checker’s logfile contains error messages like:
TSK file ‘<TABLE>.TSK’ not found for package ‘TABLE’.
…
<n> packages are not loaded (TSK files not found)
Not loaded packages are saved in ‘invalid_objects.txt’ file.
Solution:
Warnings referring to tables split by R3ta can be ignored. Currently the Object Checker cannot handle such packages correctly.
————————-<D019527, 17/JUL/07>—————————
Table splitting restrictions: LRAW and RAW fields
RAW or LRAW field cannot be used within the where condition. If you want to split a table, which contains RAW or LRAW fields as part of the table’s key, use an R3ta with patch level >=4 (compile date newer than 10/JULY/2007). This R3ta will ignore RAW and LRAW fields when creating where conditions.
————————-<D029385, 17/JUL/07>—————————
Using virtual hosts for central and/or DB instances
SYMPTOM:
You are using virtual host names for your central instance and/or the database instance (e.g. in a HA environment). Although SAPinst finishes successfully, some export steps are not being performed.
SOLUTION:
Start the export with the property SAPINST_USE_HOSTNAME=<virtual host>.
If the central instance and the database instance run on different hosts, run the database export with SAPINST_USE_HOSTNAME=<virtual host name of the DB server> and – if you run a Java or ABAP+Java system – run the central instance export with SAPINST_USE_HOSTNAME=<virtual host nameof the central instance host>.
If you run a central system with different host names in the profiles, handle the export as a distributed export, calling SAPinst with parameter SAPINST_USE_HOSTNAME. Perform the export of the database instance on the DB server, calling SAPinst with SAPINST_USE_HOSTNAME=<virtual host of the DB server>.
————————-<D019527, 12/JUL/07>—————————
Java: Follow-Up Activity: Installing the License Key
BEFORE installing the license key, make sure to apply SAP Note 831812.

————————-<D019527, 04/JUN/07>—————————
Table splitting for tables starting with ‘/’
When trying to process tables starting with ‘/’, the step ‘R3ta’ will abort when trying to create the R3ta log and WHR files. To leverage processing of tables starting with ‘/’, a correction in two functions in the control.xml file is required:
4. Start the SAPinst service ‘Table Splitting Preparation’. When you are asked for the first input, interrupt the installation.5. Edit the file control.xml in your installation directory (for the export).6. Search for string ‘function checkWhrCondOk’. Within the function, perform the following changes:a) Add the following line as first line of the function body:
var sTabName = sTable.replace(/\//g, “_”);b) Replace ’sTable’ by ’sTabName’ in the declaration of variable fWhrFile:
old: var fWhrFile = oFileMgt.getNode(sWhrDir+”/”+sTable+”.WHR”);
new: var fWhrFile = oFileMgt.getNode(sWhrDir+”/”+sTabName+”.WHR”);c) Search for string ‘function startR3ta’. Within the function, perform the following changes:d) Add the following line as first line of the function body:
var sTabName = sTable.replace(/\//g, “_”);e) Replace ’sTable’ by ’sTabName’ in the declaration of aR3taArgs[1], aR3taArgs[6] and aR3taArgs[8]:
old: aR3taArgs[1] = “Split/”+sTable+”.WHR”;
new: aR3taArgs[1] = “Split/”+sTabName+”.WHR”;
old: aR3taArgs[6] = “Split/”+sTable+”.STR”;
new: aR3taArgs[6] = “Split/”+sTabName+”.STR”;
old: aR3taArgs[8] = “R3ta_”+sTable+”.log”;
new: aR3taArgs[8] = “R3ta_”+sTabName+”.log”;7. Restart the installation and choose ‘Continue with old installation’. Now the installation will run with the control.xml file which you have adapted in the installation directory.
————————-<D019527, 22/MAY/07>—————————
Table splitting: ‘/’ characters in column names
When the column names used inside the R3ta WHR files contain ‘/’ characters, and these column names are not masked with double quotes, the R3load export will abort.
Use an R3ta with patch level >=3 (compile date newer than 24/MAY/2007). This R3ta will quote the column names correctly.
————————-<D029385, 15/MAY/07>—————————
Copying an upgraded system: client 001 missing
If you want to copy an upgraded system make sure that client 001 exists.
If this is not the case, proceed as follows:
Before logging on to the system, adjust parameter login/system_client in file DEFAULT.PFL according to the definition on the source system.
————————-<D029385, 15/MAY/07>—————————
SQL files in export directory need to have read access
Make sure that the SQL files in the export directory have read access (for example, 644).
————————-<D019527, 08/MAR/07>—————————
ABAP/Table Splitting: wrong format of input file
Ensure that the file with the list of tables to be split does not contain any empty lines. Otherwise SAPinst will abort with a message like:
Reading of table split file <input file> failed. Line “” does not fit to expected format tablename%numsplits.
————————-<I027628, 15/FEB/07>—————————
ABAP: The job RUTSMJOB returns an error in the system after the import: “View definitions in the ABAP dictionary and database are not consistent”
Solution:
Apply SAP Note 999910.
————————-<D019527, 31/JAN/07>————————–
Java: Follow-Up-Activity:
Before starting the Java engine, see SAP Note 831812 and adapt the SAP JVM parameters, if necessary.
————————–<D019527, 25/JAN/07>————————–
R3ta missing on installation master DVD
When running the service ‘Table Splitting Preparation’ the step ‘R3ta’ of component ‘TableSplitter’ will fail with the following error message in file sapinst_dev.log:
… Call to R3ta failed for table <table name>. …
In addition you will find the following error message in file sapinst_syslib_priv.log:
Error in execvpS(R3ta errno: 2, error text: A file or directory in the path name does not exist.
Solution:
Make sure that you have an R3ta in the kernel directory. In contrast to the system copy guide the installation master DVD does not contain an R3ta executable and a R3ta_hints.txt file. Download the R3ta*.SAR archive from the SAP SMP, extract it to the installation directory for the table splitting preparations and move the R3ta executable to the kernel directory.
————————–<D001658, 19/DEC/06>————————–
Follow-Up Activity:
After the system copy has finished, you have to perform the following step manually:
If the data is stored in the file system, job logs, batch input logs, and spool jobs are stored in the directory DIR_GLOBAL.
The files can be found in the following sub-directories:
xxxBDCLGxxxJOBLGxxxSPOOL
You have to copy these files manually from the source to the target system for every client.
————————-<D019527, 04/DEC/05>————————–
Java Export: error during export of table CAF_GP_R3USRMPGCFG or
CAF_GP_IF_CONTEXT
Symptom:
The export aborts with one of the following error message in jload.
java.log:
SEVERE: DB Error during export of CAF_GP_R3USRMPGCFG
…
SEVERE: Message: ORA-00942: table or view does not exist
or
SEVERE: DB Error during export of CAF_GP_IF_CONTEXT
…
SEVERE: Message: ORA-00942: table or view does not exist
Solution:
Delete the entry for table CAF_GP_R3USRMPGCFG or for table CAF_GP_IF_CONTEXT from the dictionary of the Java engine. Connect to the database as your database schema user and execute the following statement on database level:
DELETE FROM BC_DDDBTABLERT WHERE NAME = ‘CAF_GP_R3USRMPGCFG’;
or
DELETE FROM BC_DDDBTABLERT WHERE NAME = ‘CAF_GP_IF_CONTEXT’;
Disconnect from the database and repeat the export step with SAPinst.
————————<D019527, 07/NOV/06>—————————-
Heterogeneous BW system copy: Missing P indexes
Follow the instructions as described in SAP Note 996263.
————————<D029385, 26/OCT/06>—————————-
The name of the export directory that you specify during the exportmust not end with /DATA.
Otherwise SAPinst cannot find <TABART>.SQL files that may be located in the export directory <exportdir>/DB/<dbs>.
————————<D019527, 04/AUG/06>—————————-
ABAP/HET: Enter Migration Key
When installing the target system’s database instance during a heterogeneous system copy, you either have to choose parameter mode ‘Custom’ or have to check the dialog ‘SAP System > Database Import’ on the summary screen and then revise this dialog. Only then appears the dialog screen where you can enter the migration key, which is required for a heterogenous system copy. If you forget to revise this dialog setting during the dialog phase, SAPinst will abort in the processing phase when checking the migration key and will ask you for a valid migration key.
————————<D022726, 27/JUN/06>—————————-
The Template Installer may not be used after a system copy because it has not been tested under such condition and may break the system.
In case you access the Template Installer after the system copy nevertheless, you would notice that it still displays the old SID and host name that the system had before the copy. This information is fetched from a file that has been created by installation that is not updated by the system copy process. This has no adverse effects, because it is used only by the Template Installer, which must not be executed under this condition anyway.
——————<D041479, 12/MAY/06>———————————-
System copy export with incorrect SP level
If you perform a system copy export with a service pack level that is not the latest service pack level released by SAP for the Java stack, see SAP Note 937362 for more information.
————————-<D019527, 09/MAY/06>—————————
ABAP import fails with ‘invalid migration key’
The ABAP import aborts when checking the migration key. In the logfile test_MIGKEY.log the following error message appears:
ERROR: invalid migration key
Prerequisites:
The source system has already installed a new, digitally signed SAP license. You can check this by calling transaction SLICENSE: The license is only displayed when you click on the ‘New Licenses’ button.
Solution:
Use the following migration key (valid until 31/DEC/09):
1G5fdEM50TIIrBzjt6TE5Pae
————————-<D037196, 05/MAY/06>—————————
Configuration needs to be edited after the target system installation (< SPS9)
After the target system installation proceed as follows:
1. Start the GUI ConfigTool2. Select File -> Configuration Editor3. Switch to edit mode4. SPS9 and lower: Open Configurations -> cluster_data -> Propertysheet instance.properties.IDXXXXX and edit the following properties:instance.en.host (new value SCS host)instance.en.port (new value enqueue server port, default value is 32<SCS instance number>instance.system.id (new value CI instance number)
————————-<D037196, 02/MAR/06>—————————
J2EE Engine does not start after target system installation
Solution:
The J2EE Engine needs to be started manually after the target system has been installed and the follow-up acitivities have been performed. In order to start the J2EE Engine of a copied Add-In system, the whole instance must be restarted.
————————-<d037196, 17/JAN/06>—————————
System Copy to AMD64, from/to AS/400
Fix import of NetWeaver 2004s SPS06 and higher for AMD64, AS/400 with respect to the Java parameter settings
————————-<C5028898, 13/DEC/05>————————–
Doublestack export DB2 on Unix: Export Preparation with modified
control.xml from SAP Marketplace.
If you want to perform a systemcopy with DB2 UDB source database on Unix using parallelly export/import feature by choosing
SAP NetWeaver 2004s/Business Suite Application 2005 –> Lifecycle Management –> System Copy –> IBM DB2 UDB for UNIX and Windows –> Source System –> Central/Distributed/HA System –> Based on AS-ABAP and AS-Java–> Export Preparation
You have to download the control.xml from SAP Service Marketplace.
You can find patch PrepExpDB6NW04S at
http://service.sap.com/swdc
Support Packages and Patches
SAP KERNEL 7.00 32/64-BIT
_<bit>/DBINDEP
PrepExpDB6NW04S patch #1
To run SAPinst with the new control.xml:
Copy the Installation Master CD local and replace on CD:
<DVD>\\NW04S\SLM\EXP\control.xml
Or start SAPinst, choose the ‘Export Preparation’ option, abort after the first dialog, replace the control.xml in the installation directory and restart teh SAPinst. Choose the ‘Export Preparation’ option again and choose ‘Continue old installation’ on the next dialog.
————————-<I031908, 08/DEC/05>————————–
System copy import fails during ‘unpackSDMKITJAR’
Symptom:
Target system import fails during the unpackSDMKITJAR with such error : ‘<PATH to SDMKIT>/SDMKIT.jar is not a jar file!’
Reason:
Bug in some Java virtual machine implementations cause problems when getting the uncompressed size of big zip archive entries. The problem
depends on the actual Java virtual machine implementation.
Solution:
See SAP Note 904245.
————————-<D019130, 30/NOV/05>————————–
Java system copy: corrupt GZIP trailer
Symptom:
During DB import with jload GZIPInputStream throws an IOException complaining (falsely) about a corrupt GZIP trailer.
Reason:
The system contains at least one large table whose export generates more than 2 GB of uncompressed data. Compression with GZIPOutputStream will not lead to an error but the GZIP trailer written to the end of the output stream will not be interpreted correctly by GZIPInputStream.
Workaround:
Until the problem will be fixed in the JDKs use a jload from SP 6 (or higher) which implements a workaround. If your system is still on SP 5 or lower contact the hotline to check if and how tools from SP 6 might be used nevertheless.

————————-<D019527, 24/NOV/05>————————–
Java Export: error in SDM call createsdmkitjar
Symptom:
The export aborts in step packSDMKitJar (Export Java Central Instance) with the following error message:
Warning: Warning during command execution: No location information available for software component ‘SAP-JEECOR’/’sap.com’/'SAP AG’/ ‘1000.7.00.4.1.20050921171700′. Cannot pack this archive. Missing archives may lead to errors after the packed SDM installation has been extracted later. Info: This SDM installation has been packed to /sapdb/EXP/JAVA/SDM/SDMKIT.JAR To unpack this installation again, extract /sapdb/EXP/JAVA/SDM/SDMKIT. JAR and invoke the SDM command install with parameter extractpackedinst=true
Solution:
Stop sapinst. Then restart sapinst with the additional parameter ‘SAPINST_SKIP_ERRORSTEP=true’.
————————-<D019527, 24/NOV/05>————————–
Java System Copy: Frequent Restart of J2EE Engine on Target Host
Symptom:
After a system copy the J2EE engine frequently restarts on the target system when running with a HP or SUN JDK.
Solution:
Enlarge the parameters PermSize and MaxPermSize. The values depend on the number and complexity of your deployed applications. If the source JDK was an HP or SUN JDK as well, use the values from the source system.
For more information, see SAP Note 723909.
————————-<D020432, 10/NOV/05>————————–
Java System Copy: Missing KM Images
If after the system copy, the KM icons are not displayed and services do not start up, you need to adapt the path to the shared KM configuration folder. On each machine in a cluster:
1. Log on to the portal2. Choose System Administration -> System Configuration -> Knowledge Management -> Content Management -> Repository Managers -> File System Repository3. Select the etc repository and choose Edit.4. Set the parameter for Root directory appropriately for your operating system:
UNIX:
/sapmnt/< SID>/global/config/cm/etc
Windows:
//<central_instance_server>/sapmnt/<SID>/SYS/global/config/cm/etc5. To ensure that the correct path is preserved during an upgrade, also enter the path (without etc) in the cm.properties file. The file is located on the machine of the central instance under:UNIX:
Change the value of the parameter System.SharedFolder to:
/sapmnt/<SID>/global/config/cmWINDOWS:
Change the value of the parameter System.SharedFolder to:
//<central_instance_server>/sapmnt/<SID>/SYS/global/config/cm6. Restart the J2EE engine to activate the settings.

————————-<D037196, 07/NOV/05>————————–
Java System Copy: Target system installation copying Enterprise Portal (<SP7)
When copying EP (<SP7), the instructions in SAP Note 888718 must be applied. Using the installation master from NetWeaver 2004s SR1 or copying EP (>=SP7) this is obsolete.
————————-<D028265, 02/NOV/05>————————–
Java export MaxDB: Output columns too long
Symptom:
During the export of MaxDB database content using Jload an error like the following appears:
ERROR 2005-09-24 14:23:17 [iaxxgenimp.cpp:653]
showDialog() FCO-00011 The step exportJ2EEDatabase with step
key
NW_Export ind ind ind ind 0 0 NW_Java_Export_Dialog ind ind ind ind 4 0
NW_JAVA_Export_DB ind ind ind ind 3 0 exportJ2EEDatabase was executed
with status ERROR .
You find an error like the following in the jload.log
24.09.05 14:23:16 com.sap.inst.jload.Jload printSQLException
SEVERE: Message: [-2003] (at 8): Output columns too long
Solution:
Apply SAP Note 883533.
————————-<d019527, 02/NOV/05>————————–
Java Export/HP-UX: remote export required (<SP6)
If you want to export your J2EE engine from a HP-UX database host, continue as described in SAP Note 884452.
————————-<d020432, 27/OCT/05>————————–
Java: Cleanup Script for KMC Content Exchange
If content exchange is configured on the source system, the same configuration exists on the target system after the system copy. However, in most cases, it does not makes sense to have the same configuration on both the source and target system. For this reason, youneed to remove the configuration on the target system with the help of acleanup script and then set up a new configuration. The cleanup script is available as an attachment to SAP Note 883859.
————————-<d019527, 25/OCT/05>————————–
Java Export/UNIX: Error when trying to write to <export dump directory>/JAVA/DB/<DBTYPE>
Reason:
The directories belong to the root user with a group different than sapsys.
Solution:
Change owner and group of the <export dump directory> and all subdirectories to owner <sapsid>adm and group sapsys.
————————-<D037196, 13/SEP/05>————————–
Java: Copying NW2004s SP4 on Windows
After the target central instance installation set the Java VM
parameters for the J2EE Engine according to SAP Notes 723909 and 831812.
————————-<D037196, 08/MAY/07>————————–
Java: Export Distributed System
When exporting a distributed system, using local export directories,
the created exports directories
need to be merged, that is copied together. Make sure that the
SOURCE.PROPERTIES file is the one created when exporting the Central
Instance. Otherwise the import will abort with the following error:
FJS-00003 TypeError: sourceProps.get (”src.ci.host”) has no properties
(in script NW_Java_OneHost ind ind ind ind, line 11804: ???)
FCO-00011 the step InitPrivateContext with step Key
|NW_Java_OneHost|ind|ind|ind|ind|0|NW_OneHost_System|ind|ind|ind|ind|1|0
|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|i
nd|ind|ind|3|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0|InitPriva
teContext was executed with status ERROR
Solution: Copy the SOURCE.PROPERTIES from the Central Instance export
to the Java export DVD or add the property src.id.host to the
SOURCE.PROPERTIES file using the value created by the Central
Instance export.

———————————————————————–
2MaxDB-Specific Procedure
——————<D022376, 23/MAY/06>———————————-
Homogeneous MaxDB System Copy: Exporting database statistics
During a homogeneous MaxDB system copy, you can export the database statistics and import them into the target system. For exporting the database statistics call the database loader as follows:
On Unix:
/sapdb/programs/bin/loadercli -d <DBSID> -u SAP<SID>, <password>
On Windows:
<drive>:\sapdb\programs\bin\loadercli.exe -d <DBSID> -u SAP<SID>,<password>
The export of the statistics is performed by:
EXTRACT USER STATISTICS OUTSTREAM FILE ‘<ExportPath>/statistics’
As soon as the data export and the database statistics export are completed, copy the file ’statistics’ to the directory DB/ADA of the export directory. If the file ’statistics’ is available in the database export directory, it is automatically imported during the target system installation.
————————<D022376, 20/APR/06>—————————
System Copy with Target Database MaxDB 7.6
For system copies with target database MaxDB 7.6 check SAP Note 941635 for more information.

========================================================================
3MS SQL Server-Specific Procedure
========================================================================
————————<D050445, 13/MAY/09>—————————-
Extended dbs/mss/server parameter causes R3load/Jload export failure
Problem:
ABAP/ABAP+JAVA: R3load/Jload-based System Copy fails during the export if the profile parameter #dbs/mss/server# was manually extended.
Solution:
Apply SAP Note 1340471.
—————————<D000312, 08/JAN/09>————————-
Jload export fails with java.lang.OutOfMemoryError
Symptom:
A jload export of an MSSQL datasource fails with java.lang.OutOfMemory error.
Solution:
Apply SAP Note 1276704.

———————–<D000312, 01/DEC/08>—————————-
SQL Server: R3load-import error with Fastloader (for ABAP, ABAP+Java, non-Unicode only)
If you perform a system copy of a SAP system based on SAP NetWeaver 7.0 and your target system runs on SQL Server 2008 , you have to turn off the odbc-based Fastloader for SQL Server. Otherwise input character data is converted into the wrong format in the database. For more informationand how to turn off the Fastloader, see SAP note 1279941.
————————<D034302, 24/JUL/06>—————————
Symptom:
A dialog box with the following message appears during an export from a dbo-based system (dbs/mss/schema=dbo or not set):
“User tables belonging to the dbo schema were found in the database … You can only install an SAP system in a database with no user objects belonging to the system schema dbo.”
The export cannot be continued.
Solution:
Proceed as follows:
1. Stop SAPinst.2. Open the file control.xml in the sapinst log directory and look for the following lines:
AllowNew: mig ? “false” : “true”,
AllowDboObjects: mig ? “true” : “false”,3. Change these lines to
AllowNew: ins ? “true” : “false”,
AllowDboObjects: ins ? “false” : “true”,4. Save the control.xml, restart SAPinst and choose “Continue old installation”.

========================================================================
4Oracle-Specific Procedure
========================================================================
——————–CHANGED<d023322, 08/JAN/2009>———————-
——————–CHANGED<d023322, 18/SEP/2008>———————-
————————<d023322, 14/JUL/2008>————————-
Error in sapinst_dev.log: (…)runCatprocSql
This error occurs while installing oracle patch 10.2.04 only!
Error:
FCO-00011 The step runCatprocSql with step key NW_Onehost ind ind ind ind 0 0 NW_Onehost_System ind ind ind ind 1 0 NW_CreateDBandLoad ind inind ind 10 0 NW_CreateDB ind ind ind ind 0 0 NW_OraDBCheck ind ind ind ind 0 0 NW_OraDBMain ind ind ind ind 0 0 NW_OraDBStd ind ind ind ind 3 NW_OraDbBuild ind ind ind ind 5 0 runCatprocSql was executed with status ERROR .
Solution:
Choose one of the following options:
Download the latest SAPinst version from SAP Service Marketplace and repeat the installation.Edit file control.xml in your installation directory as follows:a) Search for “this.runCatproc =b) Go to “script.execute_AbortOnFailure();” some lines below.c) Replace “script.execute_AbortOnFailure();” with “script.execute();”d) Restart sapinst and continue with the installation.

————————-<D023322, 18/APR/07>————————–
BW only: Error during “Import ABAP” phase in step “runMigrationMonitor” of BW specific packages SAPDDIM, SAPDFACT, SAPDODS
The problem occurs during the export with R3szchk while creating the DBSIZE.XML file. The tablespaces PSAP@SCHEMAID@anything are mapped to PSAP@SCHEMAID@ but in DDLORA.TPL the tablespaces are mapped to BW specific tablespaces.
Solution:
1. Get the latest R3szchk from SAP Service Marketplace at: http://service.sap.com/swdc -> Download -> Support Packages and Patches -> Entry by Application Group -> SAP NetWeaver -> SAP NETWEAVER -> SAP NETWEAVER 2004S -> Entry by Component -> Application Server ABAP -> SAP KERNEL 7.00 <architecture> -> -> ORACLE2. Restart the export.
The DBSIZE. XML will be created also with the BW specific tablespaces.

————————-<D023322, 23/JAN/07>————————–
Error during system copy with Oracle-specific procedure
During a system copy with the Oracle-specific procedure, the following error may occur:
ERROR 2007-01-04 21:48:25 [iaxxejsbas.cpp:178]
EJS_ErrorReporter
FJS-00003 ReferenceError: row is not defined (in script NW_Java_DB|ind|ind|ind|ind, line 90323: ???)
ERROR 2007-01-04 21:48:25
FCO-00011 The step checkForLoadType with step key |NW_Java_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|checkForLoadType was executed with status ERROR.
Solution:
Edit the control.xml in the installation directory:
Search for “update ORACHECK_PAR” and delete the row “row.createDb = false;” underneath.

————————-<D023322, 05/JAN/07>————————–
Error in step createTempLicense with step key.
The error depends on a wrong DDLORA.TPL and the wrong DDLORA.TPL depends on a PSAPUNDO entry intaora or iaora on the source system.
Solution: Before you start with the database installation on the target system, modify DDLORA.TPL on the export folder /<your_export_path>/DB/DDLORA.TPL while removing the lines with PSAPUNDO.
Example
loc: USER2 PSAPUNDO 0000 APPL0 PSAP@SCHEMAID@ 0000 APPL1 …..
change to loc: APPL0 PSAP@SCHEMAID@ 0000 APPL1 …..
When you already ran into this error, you need to modify the keydb.xml so that all steps are restarted beginning with the step “runDdicoraSql” or start from the beginning.
————————-<D020904, 13/JUL/06>————————–
Windows Oracle:In chapter “Generating the Control File Structure” of the system copy guide for the database specific system copy procedure, add the following information as Step 1:
1. If you want to migrate your database from 32-bit to 64-bit or vice versa, add the following lines at the bottom of the control.sql file for Oracle 10.2: shutdown immediate
startup upgrade
spool utlirp.log
@?/rdbms/admin/utlirp.sql
spool off
Shutdown immediate
Startup
Spool utlrp.log
@?/rdbms/admin/utlrp.sql
Spool off
exit
Then continue with the other steps in the procedure.
————————-<D023322, 15/DEC/05>————————–
SYMPTOM:
Unable to assign default tablespace to user: SAPSR3
SAPinst cannot convert the old tablespace layout in DBSIZE.XML to the new tablespace layout. The tablespace mapping was not running.
SOLUTION:
1. Change the old DBSIZE.XML to a new DBSIZE.XML and restart the installation from the beginning.
You get an example of a right DBSIZE.XML from an export DVD under the folder <sap_export_dvd>/EXP1/DB/ORA/DBSIZE.XML2. Create this missing tablespace manually with sqlplus and restart SAPinst with the option “Continue old installation”.

———————————————————————–
5IBM DB2 UDB for UNIX and Windows-Specific Procedure
————————-<C5028898, 17/JUL/06>————————–
Homogeneous System Copy
SYMPTOM:
After performing a homogeneous system copy, the DBADM privilege on the database is missing for the user <sapsid>adm on the target system.
SOLUTION:
Execute the following commando as user db2<dbsid>:
db2 grant DBADM on database to USER <sapsid>adm
————————-<C5010742, 28/NOV/06>————————–
Homogenous System Copy – Export of your SAP System:
If you use DB2 9 and you want to export your SAP system, proceed as follows:
To avoid severe performance problems with R3szch during the export of your SAP System,download latest R3szch and dbdb6slib from service marketand apply both to your SAP system.
For lib_dbslt, at least patch level 86 is required.
———————————————————————–
6IBM DB2 UDB for eServer iSeries-Specific Procedure
<no input yet>
———————————————————————–
7IBM DB2 UDB for OS/390, z/OS-Specific Procedure
————————<D046257, 28/JAN/08>————————–
Homogeneous System Copy:
When doing a database migration using Database Tools on a NW2004s
System, you must carry out the steps described in SAP Note 1059145. As
well it is necessary to select “custom mode” as installation mode in
SAPinst.
———————————————————————–
8 Windows-specific Topics
——————<D029385, 15/MAY/07>———————————
HA (MSCS): Installing a dialog instance
To install a dialog instance during a system copy for MSCS systems, start the installation service from the installation master DVD from the following path:
Additional Software Life-Cycle Tass -> Application Server -> MS SQL Server -> Dialog Instance.

——————<D034879, 26/OCT/06>———————————
If you want to export the database of an ABAP or double stack system on Windows, where no other instance of the system is running on the same host, the ABAP message server instance has to be running during the dialog phase of the installation.
——————<d019527, 30/MAY/06>———————————
Due to a bug in JDK version 1.4.2_11, the export with jload suffers from serious performance problems. We recommended to wait for the next JDK version before performing an export from a host that is running on a Windows X86_64 server.
——————<D034302, 04/APR/06>———————————-
Environment variable SAPSYSTEMNAME to be checked
Before starting the export, make sure that the environment variable SAPSYSTEMNAME is set correctly in the environment of SIDADM:
SAPSYSTEMNAME=SID