Note 1738258 - System Copy of Systems Based on SAP NetWeaver 7.1 and Higher

One of the Classic notes all basis should know... 

Summary

Symptom
************************************************************************
*              Homogeneous and Heterogeneous System Copy              *
*                         for Systems Based on                         *
*                      SAP NetWeaver 7.1 and Higher                     *
************************************************************************
Other terms
migration r3load
Reason and Prerequisites
Problems discovered after the publication of the documentation:
System Copy - SAP Systems Based on the Application Server <Technology> of SAP NetWeaver Using Software Provisioning Manager 1.0
Solution
This note contains the following sections:

1  All Databases: Database-Independent r3load and jload Procedures
2  All Databases: Database-Specific Procedures (Homogeneous System Copy)
3  MaxDB-Specific Procedure
4  MS SQL Server-Specific Procedure
5  Oracle-Specific Procedure
6  IBM DB2 for Linux, UNIX, and Windows-Specific Procedure
7  IBM DB2 for i-Specific Procedure
8  IBM DB2 for z/OS-Specific Procedure
9  Sybase ASE-Specific Procedure
10 SAP HANA Database Specific Procedure
11 Windows-specific Topics



     Table of Contents
     =================

date         section   description
-----------------------------------------------------------------------
22/AUG/13     6     Heterogeneous Java system copy to IBM DB2 for Linux, UNIX, and Windows: SAPJVM patch required
29/JUL/13     1     Migration to SAP HANA Database: SAP NetWeaver Instance Parameters
19/JUL/13     1     Migration from SAP HANA DB to another database: Table sizes
16/MAY/13     1     BW, APD: Problems with system copy
08/MAY/13     5     SAP System Copy on Oracle Solaris with Oracle Database
29/APR/13     10    More information about migration to SAP HANA Database
21/MAR/13     9     SYB: System copy import fails with source database SAP MaxDB
25/FEB/13     1     System Copy: The system copy import fails when migration monitor tries to import packet SAPAPPL2
25/FEB/13     1     System Copy: Error DDL Statement Failed
29/JAN/13     1     Development Infrastructure (DI): Activities are back in status 'waiting' after system copy
10/DEC/12     10    SAP Business Suite powered by SAP HANA 1.0: Migration to SAP HANA Database
26/NOV/12     10    Kernel Version
26/NOV/12     10    The program can't start because libSQLDBCHB.dll is missing from your computer
26/NOV/12     1     Not all packages are loaded
17/JUL/12     5     Create an Oracle account and groups also for non ASM installation / systemcopy
09/MAY/12     9     Information about heterogeneous system copy on Sybase ASE
10/FEB/12     5     SAP NetWeaver 7.3 only: ORA_SID is not created yet
30/JAN/12     1     SAP NetWeaver 7.3, Java only: SAFE mode causes issues when starting target Java system
13/JAN/12     2     Exporting the source system is no longer required
12/DEC/11     9     Import fails with SQL syntax error
01/AUG/11     4     Modified kernel DVD
01/AUG/11     4     Unknown template variable "compression_page"
17/NOV/10     1     Error during step JMigmonJavaDump
10/AUG/10     4     SQL Server: R3load-import error with Fastloader
10/DEC/09     3     Error in starting DB after restore due to different SYSDBA passwords
28/SEP/09     5     Error in invoking target 'agent_nmo_nmb' of makefile during Oracle RUNINSTALLER installation
13/MAY/09     4     Extended dbs/mss/server parameter causes R3load/Jload export failure
08/APR/09     2     Wrong key phrase: UME services don't start
14/JAN/09    2     ABAP+Java, Java: Do not uninstall all application server instances
19/DEC/08     4     Jload export fails with java.lang.OutOfMemoryError
18/DEC/08     1     Remote primary application server causes abort of unattended DB refresh/move
12/DEC/08     5     Error during export preparation with R3szchk
09/DEC/08     1     ABAP import fails with "invalid migration key"
29/OCT/08     1     Export on UNIX: Error modifying users
22/JUL/08     1     Table splitting:export/import using MigMon
17/MAR/08     6     Error during database refresh
15/FEB/08     5     Prerequisites: Homogeneous Copy of Oracle DB
14/FEB/08     1     Invalid trusted relationships after creating a new database
23/Jan/08     1     After Table Splitting Preparation: Add R3ta_hints.txt file
11/JAN/09     8     Known errors with R3load/R3ldctl/R3szchk
07/JAN/08     1     ABAP only: Error after Restart the SAPMMC
06/DEC/07     1     R3ldctl: correct 'negdat' entry in DDL template
27/SEP/07     1     ABAP/HET: Enter Migration Key
09/JUL/07     1     Table splitting: restrictions
13/JUN/07     1     Table splitting for tables starting with '/'
13/JUN/07     1     Table splitting: '/' characters in column names


=======================================================================
1  All Databases: Database-Independent r3load and jload Procedures
=======================================================================

------------------------< I055161, 29/JUL/13 >-------------------------
Migration to SAP HANA Database: SAP NetWeaver Instance Parameters
When migrating from another database to SAP HANA database, make sure that the following parameters are not set in the SAP NetWeaver Instance Profiles.

rsdb/prefer_in_itab_opt
rsdb/max_in_blocking_factor
rsdb/min_in_blocking_factor
rsdb/prefer_union_all
rsdb/prefer_join
rsdb/prefer_fix_blocking
rsdb/max_blocking_factor
rsdb/min_blocking_factor
rsdb/max_union_blocking_factor
rsdb/min_union_blocking_factor

This will ensure that the default values are used.

------------------------< D028265, 19/JUL/13 >-------------------------
Migration from SAP HANA DB to another database: Table sizes
R3szchk (ABAP) or jsizecheck.jar (Java) reads the sizes of individual tables from a system table that issues 0 if the table is not in main memory. This means that the details in the EXT files of R3szchk / jsizecheck.jar are imprecise. The EXT files are required for subsequent package splitting, so it is important to have precise details in the EXT files.

To ensure that the correct table sizes are returned, you must execute the following script as user <sid>adm on the DB server before starting a system copy from HANA to any other database:

              <HANA DB Host>:/usr/sap/<SID> /SYS/exe/hdb> python ./python_support/loadAllTables.py --user=System --password=<password> --address=<hostname> --port=3<instanzNummer>15 --namespace=SAP<SID>
              [140630154512128, 0.002] >> starting loadAllTables (at Tue Apr 30 09:54:07 2013)


After executing this script, you can start the software provisioning manager 1.0 or execute R3szchk / jsizecheck.jar.


------------------------< I043270, 16/MAY/13 >-------------------------
BW, APD: Problems with system copy
In case of a heterogeneous system copy of a BW system, errors in the connection to database tables in the namespace /BIC/000APR* occur.
Proceed as described in SAP Note 1476120.

------------------------< I043270, 25/FEB/13 >-------------------------
System Copy: Error DDL Statement Failed

When performing a system copy of a product running Kernel 7.20 an error might occur during the import phase with a message like the following:
DB) ERROR: DDL statement failed
(                                          ALTER TABLE "/BI0/SPM_ORDER" enable persistent merge; )
DbSlExecute: rc = 99
  (SQL error 257)
  error message returned by DbSl:
sql syntax error: incorrect syntax near ";": line 1 col 91 (at pos 91)
(DB) INFO: /BI0/SPOBOX~0 created #20130201165415
To prevent this error please update the Kernel of the source system to Kernel 7.21 or 7.20 with the latest PL before performing the export.
Another option is to perform the export with the original Kernel and replace the file DDLHDB.TPL located at /ABAP/DB/ on the migration export DVD with the one attached to SAP note 1753759.
For more information,see SAP Note 1808260.

------------------------< D024975, 25/FEB/13 >-------------------------
System Copy: The system copy import fails when migration monitor tries to import packet SAPAPPL2

If the system copy import fails when the migration monitor tries to import packet SAPAPPL2, proceed as follows:
Start the R3load in the installation directory with os-user <sid>adm:
\usr\sap\IN2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd
-dbcodepage 4103 -l SAPAPPL2.log -nolog -c 50000 -force_repeat
-para_cnt 12 -loadprocedure DBSL

A solution with R3load patch is decribed in SAP Note 1814306.

--------------------------<D051496, 29/JAN/13>-------------------------
Development Infrastructure (DI): Activities are back in status 'waiting' after system copy
If activities are back in status 'waiting' after copying an SAP system with usage type DI installed in it, check SAP Note 1813461.

--------------------------<D056915, 26/NOV/12>-------------------------
Not all packages are loaded
During the system copy procedure, the following message is displayed:

Not all packages are loaded. DIAGNOSIS: For details see output file with missing packages invalid_packages.txt and log file package_checker.log.
Normally it indicates the data load error but in some special cases (for example, if some packages were processed externally) you can choose OK to continue.

SOLUTION:
In the log files, check if all packages have been loaded successfully. If they are loaded, you may ignore the warning and continue the installation by choosing "Cancel".



--------------------------<D056915, 30/JAN/12>-------------------------
SAP NetWeaver 7.30, Java only: SAFE mode causes issues when starting target Java system
SYMPTOM:
You copied a Java system that is running in SAFE mode. When starting the Java target system, errors occur.

SOLUTION:
Before you start copying a Java system, make sure that it is running in NORMAL mode. To switch to NORMAL mode, proceed as follows:

1. Make sure that you stop all pending JSPM or deployment processes.

              In case of JSPM related issues, create a messageon on component BC-UPG-OCS-SPJ.

2. Start the Config Tool script file from the /usr/sap/<SID>/ <Central instance name>/j2ee/configtool/ directory.

3. Choose File -> Safe Mode. A dialog box appears.

4. In the Safe Mode Enabled drop-down list, choose No. Confirm your entry.

5. Save the settings and confirm all occuring messages.

6. Restart the J2EE engine.

----------------------------<D041051, 17/Nov/10>-----------------------
Error during step JMigmonJavaDump
Problem:
Installation stopped with error in step JMigmonJavaDump.

Solution:
Apply SAP Note 942766.


------------------------<D037196, 18/DEC/08>---------------------------
Remote primary application server causes abort of unattended DB refresh/ move
Symptom:
The unattended DB refresh/move for a distribute system with ABAP aborts when starting the primary application server
Solution:
Start the primary application server manually and restart unattended DB refresh/move.


------------------------<D019527, 09/DEC/08>---------------------------
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 licens is only displayed when you click on the 'New Licenses' button.

Solution:
Use the following migration key (valid until 31/DEC/13):
1G5fdEM50DaIrBzjt6TE5Pae

-------------------------- <D037196, 29/OCT/08>------------------------
Export on UNIX: Error modifying users
The export aborts with the following error:
FSL-05014  Command '/usr/sbin/usermod' with parameters '-G "dba,oper, sapinst" oraxxx' failed with return code 8: Login oraxxx is currently in use

The operating system users for the SAP system (<sid>adm) and for the database need to be member of the group sapinst. This is done when the users are created during installation.
If they are not member of the group sapinst and some processes are still runing, modifying the users may fail.
In this case stop all processes for that user, e.g. for the SAP system invoke as <sid>adm
>stopsap r3
>stopsap startupsrv
or
>stopdb
and continue the export.


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

----------------------------<D019527, 14/FEB/08>-----------------------
Invalid trusted relationships after creating a new database
When performing a system copy with R3load, you must set up the trusted/ trusting relationships again.
For more information, see SAP Note 128447.

------------------------------<D019527, 23/JAN/08>---------------------
After Table Splitting Preparation: Add R3ta_hints.txt file
After the Table Splitting Preparation, make sure you select the Split predefined tables checkbox and add the R3ta_hints.txt file in the Split STR Files dialog box.


------------------------------<D037196, 07/JAN/08>---------------------
ABAP only:
Symptom: After copying a database instance only and restarting the SAPMMC an error occurs.

Solution:
1. Remove the line rdisp/j2ee_start = 1 from the DVEBMGSXX Instance Profile.
2. Restart the instance start service: sapcontrol -nr XX -function RestartService where XX is the instance number of the DVEBMGS instance.


------------------------------<D019527, 06/DEZ/07>---------------------
R3ldctl: correct 'negdat' entry in DDL template
Before starting a system copy resp. the export part, download the latest R3ldctl patch (patch level 2, compile date younger than 29th of November 2007) from the SAP service marketplace and replace the old one in the SAP kernel directory. The generated DDL<DBTYPE>.TPL file should only contain the entries 'LICHECK' and 'MLICHECK' for the 'negdat' parameter.


------------------------------<D019527, 27/SEP/07>---------------------
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.


------------------------------<D019527, 09/JUL/07>---------------------
Table splitting: restrictions

1. The tables to be split have to be listed in the input file in alphabetical order.

2. The following tables must not be split:

• DDNTF

• DDNTF_CONV_UC

• DDNTT

• DDNTT_CONV_UC

• DDLOG

3. SAP NetWeaver 7.1 / 7.1 EHP1 only: 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 >=2 (compile date newer than 10/JULY/2007). This R3ta will ignore RAW and LRAW fields when creating where conditions

------------------------------<D019527, 13/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 inthe control.xml file is required:

1. Start the SAPinst service 'Table Splitting Preparation'. When you are asked for the first input, interrupt the installation.

2. Edit the file control.xml in your installation directory (for the export).

3. 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";

4. 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, 13/JUN/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 >=1 (compile date newer than 24/MAY/2007). This R3ta will quote the column names correctly.


=======================================================================
2  All Databases: Database-Specific Procedures (Homogeneous System Copy)
=======================================================================

----------------------<D056915, 13/JAN/12>-----------------------------
When performing a system copy using a database-specific method, it is no longer required to perform an export of the source system.


----------------------<D040270, 08/APR/09>-----------------------------
Wrong key phrase: UME services don't start
Problem:
After the import on the target system, the UME services cannot be started.
Solution:
Make sure that you create the SecureStore of the target system using the same key phrase as for the source system.


----------------------<D050445, 14/JAN/09>-----------------------------
ABAP+Java, Java: Do not uninstall all application server instances
You must not uninstall all application servers of an SAP system if you want to continue using the database instance of this SAP system. Otherwise, you delete configuration-specific data in the database instance that is required for performing the homogeneous system copy.


=======================================================================
3  MaxDB-Specific Procedure
=======================================================================

-----------------------------<D028265, 10/DEC/09>----------------------
Error in starting DB after restore due to different SYSDBA passwords
Symptom:
If the passwords of the SYSDBA user ("superdba") differ on source system and target system an error may occur while starting the database after restore.
Example: The masterpassword on the target system is different to the SYSDBA password on the source system.
The SdbCmdOut.log file in the installation directory shows the following(example):
Wed Dec 09 18:17:10 CET 2009
| class com.sap.sdb.sllib.utils.connection.session.DbmJdbcSession
| Run command: load_systab -u *,* -ud *Wed Dec 09 09 18:17:11 CET 2009
| class com.sap.sdb.sllib.utils.connection.session.DbmJdbcSession
| Close dbmcli Session.Wed Dec 09 18:17:11 CET 2009
| class com.sap.sdb.sllib.utils.DbCommandForApi
| <DBMException -24907 ERR_DBAWRONG wrong SYSDBA>

Solution:
Change the password of SYSDBA user by means of dbmcli:

1. Load the database system tables:

              <drive> :\sapdb\programs\pgm\dbmcli -d <TargetSid> -u control, <MasterPassword> load_systab -u superdba,<SourcePassword> -ud domain

2. Enter the masterpassword as password of the SYSDBA user:

              <drive> :\sapdb\programs\pgm\dbmcli -d <TargetSid> -u control, <MasterPassword> user_put superdba password=<MasterPassword>

-----------------------------<D020263, 05/APR/13>----------------------
Error during SMIGR_CREATE_DDL
Symptom:
SMIGR_CREATE_DDL faild on Sybase with runtime error DYN_CALL_METH_NOT_FOUND

Solution:
Apply SAP note 1842405
=======================================================================4 MS SQL Server-Specific Procedure
=======================================================================

------------------------<D000312, 01/AUG/11>---------------------------
For installing the target system, we strongly recommend that you create and use a modified kernel DVD as described in SAP Note 1480785. This will for example avoid the problem of incompatibilities between the R3load/R3loadctl executables used for export and import (see the next topic "unknown template variable").

------------------------<D000312, 10/AUG/10>---------------------------
SQL Server: R3load-import error with Fastloader (for ABAP, ABAP+Java, non-Unicode only)
Symptom:
Due to an error in certain dbmssslib.dlls, R3load erroneously distorts special characters (for example, German "Umlaute", French accented characters, and so on) during the import.
Solution:
Make sure that you replace the dbmssslib.dll used for the import by the latest one. For more information, see SAP note 1279941.
To avoid import errors, see SAP Note 1152240, section "SYSTEM COPY ON SQL Server 2008".

-----------------------<D023322, 28/SEP/09>----------------------------
Error in invoking target 'agent_nmo_nmb' of makefile during Oracle RUNINSTALLER installation
Symptom:
You get the following error message while phase "Linking Database" is performed:
Error in invoking target 'agent_nmo_nmb' of makefile
.../sysman/lib/ins_sysman.mk

Solution:
Proceed as follows:

1. Unset variables LD_LIBRARY_PATH and JAVA_HOME.

2. Restart the RUNINSTALLER.

              If you also should have to restart SAPinst, choose "Continue with the old option on the "What do you want to do" screen.


------------------------<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, 19/DEC/08>------------------------
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.

=======================================================================
5  Oracle-Specific Procedure
=======================================================================

--------------------------<D029385, 08/MAY/2013>-----------------------
SAP System Copy on Oracle Solaris with Oracle Database
For more  information about copying SAP Systems on Oracle Solaris with Oracle database, see SAP Note 1848918.

---------------------------<D023322,17/JUL/12>-------------------------
Create an Oracle account and groups also for non ASM installation/syscopy
Symptom:
Error in step createAccounts
FSL-01002  Unable to create account user="oracle".
During the installation SAPInst create the oracle user also for non ASM installation/systemcopy.

Solution:
Update the control.xml on your installation DVD.
You need to update the control.xml before you start the installation.
Search for "setdefaults_ora" in the control.xml file and then search for the following line:
"if (context.get("isASM") || context.get("isExadata"))"
Relace this line with the following:
"if (context.getBool("isASM") || context.getBool("isExadata"))"

You have to start the procedure from the beginning.


---------------------------<D023322,10/FEB/12>-------------------------
SAP NetWeaver 7.3 only: ORA_SID is not created yet
Symptom: During the dialog phase SAPInst stops with the above error while you call the sapinst with the paramter SAPINST_USE_HOSTNAME=<your virtual host>. SAPInst do not recognize that it is running on the database host.

Solution: update control.xml in your installation directory:
search for:
NWDBora.prototype.updateOSAccounts = function() {

replace the line
if (!dbHost || !this.getNW().onDBHost()) {
with the following 2 lines
var nmgt = new NetworkMgt();
if ( dbHost && !nmgt.isHostLocal(dbHost)) {
restart the sapinst with the option continue old installation


------------------------<D000312, 01/AUG/11>---------------------------
unknown template variable "compression_page"
Symptom:
R3load import fails with error message

(TPL) ERROR: unknown template variable "compression_page"

Cause:
For the export a newer R3loadctl (April 2011 or younger) was used. This newer R3load produces a DDLMSS.TPL with the new variable "compression_page" in the DDL templates (see note 1505884). The R3load you're using for the import  is too old, it doesn't know the variable. Therefore the error occurs.
Solution:
Replace the R3load of your target system by the newest R3load patch for your release and platform from SAP MarketPlace.


-------------------------<D023322, 12/DEC/08>--------------------------
Error during export preparation with R3szchk
Symptom: When preparing the export, R3szchk creates wrong tablespace entries PSAPES70I and PSAPES700 in DBSIZE.XML. Hence SAPinst creates the wrong tablespace name PSAP <SCHEMAID>70 instead of PSAP<SCHEMAID>700.

Solution:
Get the latest R3szchk from the SAP Service Marketplace at http://service.sap.com/swdc -> Download -> Support Packages and Patches -> Entry by Application Group -> SAP NetWeaver -> SAP NETWEAVER -> <your product> -> Entry by Component -> Application Server ABAP -> <SAP KERNEL of your product> -> <your OS> -> ORACLE.

1. Restart the R3szchk step.

2. Correct the tablespace names in DBSIZE.XML befor you start the import on the target system.

------------------------------<D019527, 15/FEB/08>---------------------
When creating a homogeneous copy of an Oracle database with an ABAP only source system, make sure that a JRE version 1.5 or higher is installed on the database instance, and that the JRE environment variable points to the JRE directory.

=======================================================================
6  IBM DB2 for Linux, UNIX, and Windows-Specific Procedure
=======================================================================

-------------------------<D025792, 22/AUG/13>--------------------------
Heterogeneous Java system copy to IBM DB2 for Linux, UNIX, and Windows: SAPJVM patch required
With certain SAPJVM patch levels, loading data into a target system running on IBM DB2 for Linux, UNIX, and Windows using jload may abort. This problem is fixed with the following SAP JVM patch levels:

• SAP JVM 5.1 patch level 85 (5.1.085) - see SAP Note 1856320

• SAP JVM 6.1 patch level 50 (6.1.050) - see SAP Note 1855708

Therefore, before running the software provisioning manager on the target system, you must modify the kernel DVD with a patched SAPJVM package as follows:

1. Copy the kernel DVD of SL Toolset 1.0 SP08 to your local file system.

2. Change to directory <copied kernel DVD>\ K_720_U_<corresponding platform>\DBINDEP\

3. Systems based on 7.1x: Delete SAPJVM5.SAR and copy SAPJVM5*.SAR from SAP Note 1856320
Systems based on 7.20 and higher: Delete SAPJVM6.SAR and copy SAPJVM6*.SAR from SAP Note 1855708.

4. Systems based on 7.1x: Rename SAPJVM5*.SAR to SAPJVM5.SAR.
Systems based on 7.20 and higher: Rename SAPJVM6*.SAR to SAPJVM6.SAR.

5. Start software provisioning manager.

6. In the dialog phase of SWPM, enter the location of the modified kernel DVD on the local file system.

----------------------------<D37196, 17/MAR/08>------------------------
Error during database refresh
If you want to refresh your database schema and you receive an error message that the schema user already exists, delete the existing database manually as described in the instllation guide (section "Deleting the Database Schema Manually").


=======================================================================
7  IBM DB2 for i-Specific Procedure
=======================================================================

<no input yet>


=======================================================================
8  IBM DB2 for z/OS-Specific Procedure
=======================================================================

------------------------------<D046257, 11/JAN/08>---------------------
For known errors with R3load/R3ldctl/R3szchk, see Note 778729.


=======================================================================
9  Sybase ASE-Specific Procedure
=======================================================================

------------------------< D053089, 21/MAR/13 >-------------------------
System copy import fails with source database SAP MaxDB

The system copy import to SAP Sybase ASE with source database SAP MaxDB
fails during R3Load (Import) with the following error:
[ASE Error SQL1530]Create index with sorted_data was aborted because of
row out of order.
Since SAP MaxDB export is not sorted it is required to always use the unsorted template for system copy import to SAP Sybase ASE with source database SAP MaxDB.
Apply the solution described in SAP Note 1836598.

-----------------------------<D055517,09/MAY/2012>---------------------
For more information about heterogeneous system copy on Sybase ASE, see:

• For SAP NetWeaver 7.3: SAP Note 1672367.

• For SAP NetWeaver 7.3 EHP1: SAP Note 1697542.

----------------------------<D003491, 12/DEC/11>-----------------------
Import fails with SQL syntax error
SYMPTOM:
Heterogenous or homogenous system copy to Sybase ASE fails during import phase with SQL syntax error, if SQL files were generated for the migration of non-standard database objects with the SMIGR report.

SOLUTION:
Apply SAP Note 1612437.

=======================================================================
10  SAP HANA Database Specific Procedure
=======================================================================

----------------------------<I043270, 29/APR/13>-----------------------
More information about migration to SAP HANA Database
For  more information about the migration to SAP HANA database, see SAP Note 1851549.

----------------------------<I043270, 10/DEC/12>-----------------------
SAP Business Suite powered by SAP HANA 1.0: Migration to SAP HANA Database

Apply SAP Note 1789561 after migrating to SAP HANA Database

----------------------------<D021063, 12/DEC/11>-----------------------
Kernel Version
Before you migrate to SAP HANA database, you have to update the kernel to the latest patch level available on the SAP Service Marketplace.

----------------------------<D056915, 12/DEC/11>-----------------------
The program can't start because libSQLDBCHB.dll is missing from your computer
During the dialog phase of the installation/system copy the following error message is displayed:

"R3load.exe - System Error: The program can't start because libSQLDBCHB.dll is missing from your computer. Try reinstalling the program or fix this problem."

Confirm the message and continue without any further action.
If another dialog appears and asks whether the system is Unicode or Non-Unicode appears , choose 'Unicode' and continue.

=======================================================================
11  Windows-specific Topics
=======================================================================