Operations Guide | PUBLIC Software Provisioning Manager 1.0 SP32 Document Version: 3.7 – 2021-06-21
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database company. All rights reserved. affiliate
THE BEST RUN 2021 SAP SE or an SAP © Content
1 Homogeneous and Heterogeneous System Copy...... 9 1.1 About Software Provisioning Manager 1.0...... 10 1.2 SAP Products Based on SAP NetWeaver 7.3 EHP1 to 7.52 Supported for System Copy Using Software Provisioning Manager 1.0 ...... 11 1.3 New Features...... 12 1.4 Naming Conventions...... 18 1.5 Constraints...... 19 1.6 Accessing the Installation Guides...... 21 1.7 Accessing the SAP Library...... 21
2 Planning...... 22 2.1 Before You Start...... 22 2.2 Use Cases for System Copy...... 23 2.3 System Copy Methods...... 24 2.4 Creating a System Copy Plan...... 25 2.5 Basic Planning Aspects and Parameters...... 26 2.6 System Copy and Migration Optimization...... 29 Database Tuning for Source Databases other than SAP HANA...... 29 Sorted Versus Unsorted Unload...... 31 Package Splitting...... 32 Table Splitting...... 33 R3load Options...... 35 Migration Monitor...... 36 Distribution Monitor...... 36 Defining the Unload/Load Order...... 37 2.7 Migration to SAP HANA Database...... 37 General Information About the Migration to SAP HANA...... 38 Prerequisites and Restrictions...... 40 Involved Tools...... 40 Considerations for Performance...... 43 Database Instance Export on Additional Hosts...... 43
3 Preparation...... 44 3.1 General Technical Preparations ...... 44 3.2 Product-Specific Preparations...... 47 3.3 Preparing the Migration to SAP HANA Database...... 48 3.4 Preparing the Media Required for Performing the Export...... 52
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 2 PUBLIC Content Downloading and Extracting the Software Provisioning Manager 1.0 Archive...... 53 Downloading Dedicated Kernel Archives for the Export...... 54
4 Database Independent System Copy...... 56 4.1 System Copy Procedure...... 57 Generating DDL Statements...... 64 Using a Dedicated Kernel for the Export...... 66 Preparing the Table Split...... 67 Preparing the Package Split...... 71 Preparing Parallel Export and Import...... 73 Additional Considerations for the Migration to SAP HANA Database (Export)...... 74 Exporting the Source System...... 75 Setting Up the Target System...... 95
5 Database-Specific System Copy...... 105 5.1 SAP HANA Database-Specific Procedure...... 106
6 Copying Single Instances Only...... 107 6.1 Copying the Primary Application Server Instance Only...... 107 6.2 Copying the Database Only – Move Database Instance...... 108 6.3 Copying the Database Only – Refresh Database Instance...... 109 6.4 Copying the Database Only – Refresh Database Content...... 110
7 Follow-Up Activities...... 113 7.1 Performing Follow-Up Activities in the Source System...... 113 7.2 Performing Follow-Up Activities in the Target System...... 114 Installing the SAP License Key...... 114 SAP Solution Manager: Connection Between SLD and LMDB...... 115 Performing Follow-Up Activities for ABAP...... 115
8 Additional Information...... 126 8.1 R3load Procedures Using the Migration Monitor...... 126 About the Migration Monitor...... 127 Configuration...... 128 Assigning DDL Files to Packages...... 144 Defining Groups of Packages...... 145 Processing Split Tables...... 146 Starting the Migration Monitor...... 147 Using the “migmonCtrl” Add-On for the Export...... 153 Using the migmonCtrl Add-On of the Import Migration Monitor...... 154 Output Files...... 155 8.2 Analysis of the Export and Import Times...... 156 8.3 Table Comparison with Software Update Manager...... 157
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Content PUBLIC 3 Restrictions...... 157 Modes of the Table Comparison Tool...... 157 Using the Table Comparison Tool...... 158 8.4 Using the Package Splitter...... 161 Configuration...... 161 Starting the Package Splitter...... 164 Output Files...... 165 Executing the STR Splitter and the WHERE Splitter...... 166 8.5 Troubleshooting for Migration to SAP HANA...... 166 8.6 Using PowerShell...... 168
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 4 PUBLIC Content Document History
The following table provides an overview on the most important document changes.
Note
Before you start reading, make sure you have the latest version of this system copy guide, which is available at https://support.sap.com/sltoolset System Provisioning Copy a System using Software Provisioning Manager System Copy Option of Software Provisioning Manager 1.0 SP
Version Date Description
3.7 2021-06-21 Updated version for Software Provisioning Manager 1.0 SP32 (SL Toolset 1.0 SP32)
3.6 2021-02-15 Updated version for Software Provisioning Manager 1.0 SP31 (SL Toolset 1.0 SP31)
3.5 2020-10-05 Updated version for Software Provisioning Manager 1.0 SP30 (SL Toolset 1.0 SP30)
3.4 2020-06-08 Updated version for Software Provisioning Manager 1.0 SP29 (SL Toolset 1.0 SP29)
3.3 2020-01-20 Updated version for Software Provisioning Manager 1.0 SP28 (SL Toolset 1.0 SP28)
3.2 2019-09-16 Updated version for Software Provisioning Manager 1.0 SP27 (SL Toolset 1.0 SP27)
3.1 2019-05-27 Updated version for Software Provisioning Manager 1.0 SP26 (SL Toolset 1.0 SP26)
3.0 2019-01-21 Updated version for Software Provisioning Manager 1.0 SP25 (SL Toolset 1.0 SP25)
2.9 2018-09-17 Updated version for Software Provisioning Manager 1.0 SP24 (SL Toolset 1.0 SP24)
2.8 2018-05-07 Updated version for Software Provisioning Manager 1.0 SP23 (SL Toolset 1.0 SP23)
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Document History PUBLIC 5 Version Date Description
2.7 2018-01-15 Updated version for Software Provisioning Manager 1.0 SP22 (SL Toolset 1.0 SP22)
● New Features: ○ Installer Log Files Improvements, documented in: New Features, Useful Informa tion about the Installer, Troubleshooting with the Installer ○ Secure ABAP message server connection, documented in: New Features, SAP System Parameters ○ Using SAPuptool for table splitting, documented in: New Features, Table Splitting, Preparing the Table Split ○ LOADTOOLS.SAR archive in Software Provisioning Manager enabled for NUC, documented in: New Features, Downloading and Extracting the Software Provision ing Manager Archive ○ Enabling IPv6, documented in: New Features, Prerequisites for Running the Instal ler ● New Features section restructured: As of SP22, a dedicated subsection for each new SP has been created. New features below SP22 remain in a common table. ● The Java SDT GUI - which was in the SP21 version still available in parallel to the SL Common GUI - has been deprecated with SP22. As of SP22, SL Common GUI is the only available installer GUI: ○ The following sections which were explicitely related to Java SDT GUI were com pletely removed from this documentation: Performing a Remote Installation Re mote Processing of the Installer ( Java SDT GUI only), Starting the Java SDT GUI Separately, Running the Installer in Accessibility Mode (general accessibility infor mation was moved to Useful Information About the Installer). ○ The Java SDT GUI-specific information was removed from the common installer sections: Running the Installer, Useful Information About the Installer, Interrupted Processing of the Installer, Troubleshooting with the Installer ● New section Using the Step State Editor (SAP Support Experts Only) was added to sec tion Additional Information About the Installer
2.6 2017-09-11 Updated version for Software Provisioning Manager 1.0 SP21 (SL Toolset 1.0 SP21)
● New Features: ○ Media Signature Check, documented in: New Features, Running the Installer, Pre paring the Media Required for Performing the Export . This feature implies that section Creating Kernel Archives from an Existing SAP System has been deleted from this documentation because the related option in the installer had to be removed. ○ Load tools are now available as LOADTOOLS.SAR in the Software Provisioning Manager archive, documented in: New Features, Downloading and Extracting the Software Provisioning Manager Archive, System Copy and Migration Optimization, Database Independent System Copy, R3load Procedures Using the Migration Moni tor ○ Simplified additional application server instance installation, documented in: New Features, Preparing the Installation Media, Downloading SAP Kernel Archives (Ar chive-Based Installation)
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 6 PUBLIC Document History Version Date Description
2.5 2017-05-22 Updated version for Software Provisioning Manager 1.0 SP20 (SL Toolset 1.0 SP20)
● New Features: ○ New SAPUI5-based graphical user interface (GUI) “SL Common GUI”, docu mented in: Prerequisites for Running the Installer, Running the Installer, Useful In formation About the Installer ○ Refresh database content using a database backup enabled for SAP MaxDB , documented in: Copying the Database Only - Refresh Database Content .
2.4. 2017-02-06 Updated version for Software Provisioning Manager 1.0 SP19 (SL Toolset 1.0 SP19)
● New Features: Verification of the integrity of data units in Software Provisioning Manager, docu mented in: New Features, Downloading the Software Provisioning Manager Archive Using a dedicated kernel for the export, documented in: New Features, Using a Dedi cated Kernel for the Export , Downloading Dedicated Kernel Archives for the Export, Sys tem Copy Procedure Refreshing database content using a database backup, documented in: New Features, Copying the Database Only - Refresh Database Content . Option to restrict access to database export directory, documented in: New Features, System Copy Procedure
● Section Preparing the Media Required for Performing the Export [page 52] refac tored, created subsections Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 53], Downloading Dedicated Kernel Archives for the Ex port [page 54]
2.3 2016-10-07 Updated version for Software Provisioning Manager 1.0 SP18 (SL Toolset 1.0 SP18)
● New Features: Refreshing database content using a database backup, documented in: Copying the Database Only – Refresh Database Content [page 110] Using RMOSSWPM*.SAR instead of SWPM*.SAR for outdated OS versions not sup
ported by SAP kernel 7.40 and higher, documented in: Introduction Constraints
2.2 2016-06-06 Updated version for Software Provisioning Manager 1.0 SP17 (SL Toolset 1.0 SP17):
● Archive-Based Installation (see New Features [page 12]) ● Export option description corrected in Running the Installer [page 78]
2.1 2016-02-15 Updated version for Software Provisioning Manager 1.0 SP10 (SL Toolset 1.0 SP16)
2.01 2015-10-12 Updated version for Software Provisioning Manager 1.0 SP09 (SL Toolset 1.0 SP15)
2.0 2015-10-12 Updated version for Software Provisioning Manager 1.0 SP09 (SL Toolset 1.0 SP15)
1.9 2015-09-14 Updated version for Software Provisioning Manager 1.0 SP09 (SL Toolset 1.0 SP14)
1.81 2015-04-29 Updated version for Software Provisioning Manager 1.0 SP08 (SL Toolset 1.0 SP13)
1.8 2015-04-27 Updated version for Software Provisioning Manager 1.0 SP08 (SL Toolset 1.0 SP13)
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Document History PUBLIC 7 Version Date Description
1.7 2014-11-24 Updated version for Software Provisioning Manager 1.0 SP07 (SL Toolset 1.0 SP12)
1.6 2014-07-07 Updated version for Software Provisioning Manager 1.0 SP06 (SL Toolset 1.0 SP11)
1.5 2014-03-17 Updated version for Software Provisioning Manager 1.0 SP05 (SL Toolset 1.0 SP10 )
1.4 2014-03-05 Updated Version
1.3 2013-11-22 Updated version
1.2 2013-10-28 Updated version
1.1 2013-08-19 Updated version
1.0 2013-07-17 Initial version
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 8 PUBLIC Document History 1 Homogeneous and Heterogeneous System Copy
This document describes how to perform a homogeneous or heterogeneous system copy of an SAP system based on the application server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 with source operating system Windows to SAP HANA database as target database, using Software Provisioning Manager 1.0 SP32 [page 10] (“installer” for short), which is part of SL Toolset 1.0 SP32.
Note
Application Server ABAP based on SAP NetWeaver 7.10, 7.11, 7.20, 7.30, 7.40 SR1 are supported in mainstream maintenance only until the end of 2020. Extended maintenance will not be provided.
For more information, see SAP Note 2980160 .
You can download the last published version of the guide set for the last Software Provisioning Manager 1.0 SP30 for out-of-maintenance products (SWPM10RMSP30_
The system copy procedures described in this guide consist of two phases:
1. Export of the source system's database content. 2. Installation of the target system using the source system's database content exported in the previous step. The target system installation consists of both the target database and target instance/application server installations.
Note
This system copy guide describes only the export of the source system in detail. For the installation of the target system, you use the installation guide for the database and operating system platform of your target system. This procedure describes only the additional system copy-specific steps for the target system installation and refers for the remaining steps to the target system installation guide [page 21].
Using Software Provisioning Manager 1.0 you can use either database-specific methods or database- independent methods [page 24].
Note
Before you start preparing for a system copy with Software Provisioning Manager 1.0, make yourself also familiar with the Database Migration Option (DMO) of Software Update Manager (SUM) and make a decision, which tool - either Software Provisioning Manager or DMO - would best serve your purpose.
For more information about DMO, see https://support.sap.com/sltoolset System Maintenance Database Migration Option with SUM
For information about Software Provisioning Manager 1.0, see About Software Provisioning Manager 1.0 [page 10].
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Homogeneous and Heterogeneous System Copy PUBLIC 9 For information about SAP system products and releases covered by this guide, see SAP Products Based on SAP NetWeaver 7.3 EHP1 to 7.52 Supported for System Copy Using Software Provisioning Manager 1.0 [page 11] .
For information about supported operating system and database platforms, see the Product Availability Matrix at https://support.sap.com/pam .
Note
Not all SAP NetWeaver releases or SAP Business Suite applications that are available in Software Provisioning Manager 1.0 and are described in this guide might have been released already. To make sure that the system copy options you want to perform are already supported, see SAP Note 1680045 .
Note
As an alternative to using Software Provisioning Manager, you can copy or refresh your system with a completely automated end-to-end framework available using SAP Landscape Management. For more information, see SAP Note 1709155 and https://help.sap.com/lama .
Related Information
About Software Provisioning Manager 1.0 [page 10] New Features [page 12] Naming Conventions [page 18] Constraints [page 19] Accessing the SAP Library [page 21]
1.1 About Software Provisioning Manager 1.0
Software Provisioning Manager 1.0 is the successor of the product- and release-specific delivery of provisioning tools, such as “SAPinst”. We strongly recommend that you always download the latest version of Software Provisioning Manager 1.0. Software Provisioning Manager 1.0 is part of the Software Logistics Toolset 1.0 (“SL Toolset” for short). This way, you automatically get the latest fixes and supported processes. For more information about Software Provisioning Manager as well as products and releases supported by it, see SAP Note 1680045 and http://scn.sap.com/docs/DOC-30236 .
“SAPinst” has been renamed to “Software Provisioning Manager” (“installer” for short) in this documentation, but the terms “SAPinst” and “sapinst” are still used in:
● The name of the technical framework of Software Provisioning Manager. For more information about the SAPinst Framework, see SAP Note 2393060 . ● Texts and screen elements in the Software Provisioning Manager GUI (SL Common GUI) ● Names of executables, for example sapinst.exe ● Names of command line parameters, for example SAPINST_HTTPS_PORT
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 10 PUBLIC Homogeneous and Heterogeneous System Copy In the following, we generally refer to Software Provisioning Manager 1.0 as the “installer”. We only use the term “Software Provisioning Manager 1.0” if this is required for technical reasons.
Related Information
Preparing the Media Required for Performing the Export [page 52]
1.2 SAP Products Based on SAP NetWeaver 7.3 EHP1 to 7.52 Supported for System Copy Using Software Provisioning Manager 1.0
Here you can find the list of SAP products based on SAP NetWeaver 7.3 EHP1 to 7.52 that are supported for system copy using Software Provisioning Manager 1.0, on the specific operating system and database combinations described in this guide.
SAP Product Based on the following SAP NetWeaver Release
SAP S/4HANA 1709 SAP NetWeaver AS for ABAP 7.52 ● SAP S/4HANA Server ● AS ABAP for SAP S/4HANA Frontend
foundation 1709 on SAP NetWeaver Application Server for SAP NetWeaver AS for ABAP 7.52 ABAP 7.52, version for SAP HANA
SAP NetWeaver AS for ABAP 7.52 SAP NetWeaver AS for ABAP 7.52
SAP S/4HANA 1610 SAP NetWeaver AS for ABAP 7.51 innovation package
● SAP S/4HANA Server ● AS ABAP for SAP S/4HANA Frontend
SAP NetWeaver AS for ABAP 7.51 innovation package SAP NetWeaver AS for ABAP 7.51 innovation package
SAP S/4HANA on-premise edition 1511 Server Support Re SAP NetWeaver 7.5 lease 1
SAP S/4HANA on-premise edition 1511 Support Release 1 SAP NetWeaver 7.5 ● SAP S/4HANA Server ● AS ABAP for SAP S/4HANA Frontend
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Homogeneous and Heterogeneous System Copy PUBLIC 11 SAP Product Based on the following SAP NetWeaver Release
SAP Business Suite 7i 2016: SAP NetWeaver 7.5
● EHP4 for SAP CRM 7.0 ABAP SAP NetWeaver 7.4 Support Release 2 ● EHP8 for SAP ERP 6.0 ABAP SAP NetWeaver 7.3 EHP1 ● EHP8 for SAP ERP 6.0 ABAP including SAP S/4HANA Finance 1605 SP03 ● EHP4 for SAP SRM 7.0 ABAP ● EHP4 for SAP SCM 7.0 ABAP
SAP BW/4HANA 1.0 SAP NetWeaver 7.5
SAP NetWeaver 7.4 Support Release 2
SAP NetWeaver 7.3 EHP1
SAP Business Suite 7i 2013 Support Release 2: SAP NetWeaver 7.5
● EHP3 for SAP CRM 7.0 ABAP Support Release 2 SAP NetWeaver 7.4 Support Release 2 ● EHP7 for SAP ERP 6.0 ABAP Support Release 2 SAP NetWeaver 7.3 EHP1 ● EHP7 for SAP ERP 6.0 ABAP including SAP Simple Fi nance 1.0 / 1503 ● EHP3 for SAP SRM 7.0 ABAP Support Release 2 ● EHP3 for SAP SCM 7.0 ABAP Support Release 2
SAP NetWeaver 7.5 SAP NetWeaver 7.5
SAP Solution Manager 7.2 Support Release 2 SAP NetWeaver 7.4 Support Release 2
AS ABAP 7.4, OEM version 1.0 SAP NetWeaver 7.4 Support Release 2
SAP NetWeaver 7.4 Support Release 2 SAP NetWeaver 7.4
SAP Business Suite, powered by SAP HANA: SAP NetWeaver 7.3 EHP1
● EHP2 for SAP CRM 7.0 On SAP HANA ● EHP6 for SAP ERP 6.0 On SAP HANA ● EHP2 for SAP SCM 7.0 On SAP HANA
1.3 New Features
This section provides an overview of the new features in Software Provisioning Manager 1.0 (the“ installer” for short).
Make sure that you also read the Release Notes for your SAP product at https://help.sap.com
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 12 PUBLIC Homogeneous and Heterogeneous System Copy Feature Description Availability
Switch from Kernel 7.21 has reached end of maintenance. In addition, some is Software Provisioning Manager 7.21_EXT Kernel to 1.0 SP31 (SL Toolset 1.0 SP31) sues have been fixed with the new 7.22_EXT kernel media. 7.22_EXT Kernel
Support of SAP Software Provisioning Manager 1.0 supports SAP HANA SSL Cer Software Provisioning Manager HANA SSL Certifi- 1.0 SP29 (SL Toolset 1.0 SP29) tificates for configuring secure access to the SAP HANA data cates base.
For more information, see the installation guide [page 21].
Support for Export/ Software Provisioning Manager improvements for Export/Import Software Provisioning Manager Import of Big Tables 1.0 SP26 (SL Toolset 1.0 SP26) of SAP HANA files with more than 2 billion entries.
For more information, see Preparing the Table Split [page 67] and SAP Note 2784715 .
Support of Secure Software Provisioning Manager 1.0 supports configuring the SAP Software Provisioning Manager Connection to SAP 1.0 SP26 (SL Toolset 1.0 SP26) system to be installed to access the SAP HANA database using HANA database. encryption.
For more information, see the installation guide [page 21].
New Look and Feel As of version 1.0 SP24 Patch Level (PL) 5, Software Provisioning Software Provisioning Manager of SL Common GUI Manager comes with a new look and feel of the SL Common GUI. 1.0 SP24, PL05 (SL Toolset 1.0 For more information, see https://blogs.sap.com/2018/11/10/ SP24) new-look-for-software-provisioning-manager/ .
Installer Log Files Installer log files are now available immediately after the installer Software Provisioning Manager Improvements has been started, that is before a product has been selected on 1.0 SP22 (SL Toolset 1.0 SP22) the Welcome screen. For more information, see Useful Informa tion about the Installer [page 82] and Troubleshooting with the Installer [page 91].
Using SAPuptool If the SAP kernel version of the source system is 7.40 or higher, Software Provisioning Manager for table splitting 1.0 SP22 (SL Toolset 1.0 SP22) the SAPuptool which is contained in LOADTOOLS.SAR is used for table splitting instead of R3ta. For more information, see Pre paring the Table Split [page 67].
Note This feature is related to features LOADTOOLS.SAR archive in Software Provisioning Manager enabled for NUC in this ta ble below and LOADTOOLS.SAR archive in Software Provi sioning Manager below in this table.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Homogeneous and Heterogeneous System Copy PUBLIC 13 Feature Description Availability
LOADTOOLS.SAR The load tools in Software Provisioning Manager archive in Software 1.0 SP22 (SL Toolset 1.0 SP22) SWPM10SP
For more information, see Downloading and Extracting the Soft ware Provisioning Manager 1.0 Archive [page 53]
Note This feature enhances feature LOADTOOLS.SAR archive in Software Provisioning Manager of Software Provisioning Man ager 1.0 SP21 (SL Toolset 1.0 SP21) (see entry LOADTOOLS.SAR archive in Software Provisioning Manager below in this table).
Media Signature The signature of media is checked automatically by the installer Software Provisioning Manager 1.0 SP21 (SL Toolset 1.0 SP21) Check during the Define Parameters phase while processing the Media Browser screens. As of now the installer only accepts media whose signature has been checked. See also the description of this new security feature in SAP Note 2393060 .
For more information, see Preparing the Media Required for Per forming the Export [page 52] and Running the Installer [page 78].
LOADTOOLS.SAR An up-to-date version of the load tools - such as R3load, Software Provisioning Manager archive in Software R3szchk, R3ldctl, SAPuptool - which were available so far only 1.0 SP21 (SL Toolset 1.0 SP21) Provisioning Man in the SAPEXEDB.SAR archive of the kernel media, has now been ager made available in the Software Provisioning Manager archive. For a system copy using Unicode kernel version 7.40 or higher, the load tools from the SWPM10SP
For more information, see Downloading and Extracting the Soft ware Provisioning Manager 1.0 Archive [page 53]
Support of Oracle Software Provisioning Manager (the “installer”) now supports sys Software Provisioning Manager 1.0 SP21 (SL Toolset 1.0 SP21) 12.2 tem copy for SAP systems with Oracle 12.2.
SL Common GUI With the new installer framework version SAPINST 7.49, you can Software Provisioning Manager with SAPINST 7.49 now use the new SAPUI5-based graphical user interface (GUI) “SL 1.0 SP20 (SL Toolset 1.0 SP20) Common GUI”. For more information, see Useful Information about the Installer [page 82], Running the Installer [page 78].
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 14 PUBLIC Homogeneous and Heterogeneous System Copy Feature Description Availability
Verification of Integ The integrity of data units extracted from the Software Provision Software Provisioning Manager rity of Data Units in 1.0 SP19 (SL Toolset 1.0 SP19) ing Manager archive is verified. For more information, see Down Software Provision loading and Extracting the Software Provisioning Manager 1.0 Ar ing Manager chive [page 53] .
In addition, check SAP Note 1680045 whether additional infor mation is available.
Option to Restrict When running the database export, you can specify restricted ac Software Provisioning Manager Access to Database 1.0 SP19 (SL Toolset 1.0 SP19) cess to the export directory. For more information, see Prerequi Export sites in System Copy Procedure [page 57].
Use Dedicated Ker During the Define Parameterswant to use for the system copy. For Software Provisioning Manager nel for System Copy more information, see phase of the source system export, you can 1.0 SP19 (SL Toolset 1.0 SP19) now specify dedicated SAP kernel archives that you Downloading Dedicated Kernel Archives for the Export [page 54].
Refresh Database You can now refresh the content of an existing database using a Software Provisioning Manager Content for SAP database backup. 1.0 SP18 (SL Toolset 1.0 SP18) HANA For more information, see Copying the Database Only – Refresh Database Content [page 110].
Archive-Based In You can now download the required installation archives instead Software Provisioning Manager stallation of the complete SAP kernel installation media. For more informa 1.0 SP17 (SL Toolset 1.0 SP17) tion, see section Downloading Specific Installation Archives (Ar chive-Based Installation) in section Preparing the Installation Me dia in the target system installation guide [page 21]..
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Homogeneous and Heterogeneous System Copy PUBLIC 15 Feature Description Availability
System Provisioning All system provisioning tasks (installation, system copy, system Software Provisioning Manager for SAP NetWeaver rename) are available for the new SAP NetWeaver 7.5 release. 1.0 SP09 (SL Toolset 1.0 SP15) 7.5 and SAP The Dual Stack option, which integrates an AS ABAP and AS Java NetWeaver 7.5- in a single system (common System ID
● After upgrading to SAP NetWeaver 7.5 PI, you first have to split the still existing dual stack-system before you can use SAP NetWeaver 7.5 PI productively. For more information, see the Upgrade Master Guide - SAP
NetWeaver 7.5 at: http://help.sap.com/nw75 Installation
and Upgrade ● SAP NetWeaver 7.5 is Unicode only ● The primary application server instance directory has been renamed from /usr/sap/
System Provisioning All system provisioning tasks (installation, system copy, system Software Provisioning Manager for SAP Solution rename) are available for the new SAP Solution Manager 7.2 re 1.0 SP09 (SL Toolset 1.0 SP15) Manager 7.2 lease. Compared to previous SAP Solution Manager releases, SAP Solution Manager 7.2 is no longer provided as a classical dual- stack system (ABAP system with Java Add-in), but consists of a separate ABAP and Java stack.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 16 PUBLIC Homogeneous and Heterogeneous System Copy Feature Description Availability
Creating Kernel Ar You can reuse the binaries of a dedicated SAP system for a new Software Provisioning Manager chives from existing SAP system installation or target system installation in the con 1.0 SP09 (SL Toolset 1.0 SP14) SAP System text of a system copy by creating *.SAR archives based on the *.lst files from the executable (exe) directories of the source SAP system.
Note
This feature is only available for Unicode systems.
Caution
This feature has been deprecated with Software Provisioning Manager 1.0 SP21 (SL Toolset 1.0 SP21) and the related op tion has been removed from the Welcome screen. This depre cation has been accomplished to ensure compliancy with the new feature “Media Signature Check” of Software Provision ing Manager 1.0 SP21 (SL Toolset 1.0 SP21) described above in this table.
Executing R3szchk You can now execute R3szchk in parallel. Using this feature you Software Provisioning Manager in Parallel can improve the runtime of the export. 1.0 SP08 (SL Toolset 1.0 SP13)
Database Instance To increase the performance of the export you can use more than Software Provisioning Manager Export on Additional one SAP application server of the source system for the export. 1.0 SP07 (SL Toolset 1.0 SP12) Hosts For more information, see Database Instance Export on Additional Hosts [page 43]
Feedback Evaluation SAP SE’s aim is to provide fast and efficient procedures. To evalu Software Provisioning Manager Form ate the procedure you just carried out, we need information gen 1.0 SP07 (SL Toolset 1.0 SP12) erated by the tool during process execution and your experience with the tool itself. A new evaluation form contains a simple ques tionnaire and XML data generated during the procedure.
Port 4239 is used for displaying the feedback evaluation form. For more information, see Prerequisites for Running the Installer [page 75].
Option Verify Signed The digital signature ensures that the signatory of a digital docu Software Provisioning Manager Media ment can be identified unambiguously and signatory’s name is 1.0 SP06 (SL Toolset 1.0 SP11) documented together with the signed document, the date, and the time.
For more information, see SAP Note 1979965 .
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Homogeneous and Heterogeneous System Copy PUBLIC 17 1.4 Naming Conventions
This section contains the naming conventions used in this documentation.
● “usage type”, “technical usage”, and “product instance” As of software provisioning manager 1.0 SP07 (SL Toolset 1.0 SP12), the term “product instance” replaces the terms “ usage type” and “technical usage” . ● System Copy Duplication of an SAP system. Certain SAP parameters might change in a copy. When you perform a system copy, the installer installs all the instances again, but it uses a copy of the source system database to set up the database. ● Source System and Target System The SAP system containing the original database is called the source system and the system to which the database copy is to be imported is called the target system. Their SAP system names are abbreviated to SOURCE_SAPSID and TARGET_SAPSID. The terms source database and target database are also used in this description. ● Homogeneous System Copy During homogeneous system copy, you use the same operating system and database platform as the original system. You can perform it using either Database Independent System Copy [page 56] or Database-Specific System Copy [page 105] methods. ● Heterogeneous System Copy During heterogeneous system copy, you change either the operating system or the database system, or both. Heterogeneous system copy is a synonym for migration. You can perform it using the Database Independent System Copy [page 56] method. Use this system copy to migrate data of any database platform to the SAP HANA Database platform. ● Database Copy Database-dependent part of the system copy. ● Placeholders Placeholders such as
Placeholder Meaning How to find out
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 18 PUBLIC Homogeneous and Heterogeneous System Copy Placeholder Meaning How to find out
Note
Database ID
The
● “SAP liveCache” refers to “SAP MaxDB liveCache”. ● “SAP liveCache client” refers to “SAP MaxDB liveCache client”.
1.5 Constraints
This section contains the constraints valid for the system copy procedures described in this documentation.
● SAP NetWeaver 7.3 on SAP HANA is only supported for BW. For more information, see SAP Note 1600929 . ● If SAP HANA is the source database, you cannot use the Database Independent System Copy [page 56] procedure for SAP systems based on SAP NetWeaver AS for ABAP 7.52, because SAP NetWeaver AS for ABAP 7.52 already uses certain artifacts in the SAP HANA 2.0 database which are not supported by R3load . Use the SAP HANA Database-Specific Procedure [page 106] instead. ● Declustering with Software Provisioning Manager only works if you perform a system copy of the complete system using the method described in section Database Independent System Copy [page 56]. An “inplace-declustering” solution with Software Provisioning Manager is not supported. ● If you want to perform a Unicode Conversion, see one of the following SAP Notes: ○ SAP Note 551344 – Unicode Conversion Documentation ○ SAP Note 1051576 – Conversion of Single Code Page Systems to Unicode ○ SAP Note 928729 – Combined Upgrade & Unicode Conversion (CU) ● System copy is not supported for the Diagnostics Agent. For more information and guidance see the Diagnostics Agent Maintenance Procedures article at http:// wiki.scn.sap.com/wiki/x/n4efFg .
● Only perform a system copy if you have experience in copying systems and thorough knowledge of the operating system, the database, and the ABAP Dictionary . Only perform a heterogeneous system copy (of a production, development, or test (QA) system) if you are a certified system support consultant or a certified SAP Technical Consultant. ● SAP does not support client transport as a system copy method. Transporting production clients is not supported at all. You can use client transport for the initial setup of an SAP system infrastructure. This documentation does not cover the client copy procedure. ● This documentation does not describe how to export and import a database with the installation tools for reorganization purposes. Use the appropriate tools for database reorganization, as SAP does not support this installation option. ● If you have made modifications in your development system and want to copy your quality assurance or production system onto the development system, see SAP Note 130906 .
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Homogeneous and Heterogeneous System Copy PUBLIC 19 ● This documentation describes how to copy data from one SAP system to another SAP system based on SAP Netweaver Application Server. This documentation does not describe how to copy data from non-SAP systems to SAP systems. ● SAP does not support all data archiving operations after a system copy. If you used data archiving in the source system, you might not always have access from the target system to the archive files that were created. For more information, see SAP Note 153433 and Data Management Landscape & Transformation Solutions at https://support.sap.com/dm< . Access from the target system to archived files in the source system without a dedicated archive migration project is only supported as follows: ○ You have copied a source system that uses external data archiving. The target system has read-only access to this archive. ○ You have copied a source system that uses data archiving locally. You can either arrange network access for appropriate archive file sharing or copy all archive files to the file system of the target system.
Note
Only valid for SAP Business Warehouse:
If you use ADK-based archiving of request administration data in SAP Business Warehouse, you have to copy all archive files related to archiving object BWREQARCH to the file system of the target system. Only then write access (like deletion of requests, deletion of the complete data target content, further upload of data to other targets, changing the quality status of requests or InfoProvider rebuild) to requests with archived administration data is possible in the target system of the copy.
In all other cases, contact Data Management Landscape & Transformation Solutions at https:// support.sap.com/dm< . ● When you perform a system copy, all product instances or usage types in the source system are copied to the target system. This means that none of the product instances or usage types in the target system can be excluded from the system copy, nor can you select product instances or usage types. ● “Dos and Don'ts” for system copy: ○ Do: ○ Follow the Open SQL standard. ○ Make sure that all communication runs through the database pool. ○ Don't: ○ Save any system and infrastructure-specific data in business objects. Use a pointer to the central storage of such information, for example: ○ SAP system ID and SID (SAPSID = SID = SAP system name) ○ Host name ○ IP addresses ○ Services and ports ○ Logical destinations and logical system names ○ Other technical infrastructure names ○ Use file system persistency. ○ Set up dependencies between Java and ABAP.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 20 PUBLIC Homogeneous and Heterogeneous System Copy 1.6 Accessing the Installation Guides
The references to the “installation guide” in this system copy guide always refer to the following location on the SAP Support Portal, where you can access or download the installation guide for your operating system platform, database, and technical stack: http://support.sap.com/sltoolset System Provisioning Install a System using Software Provisioning Manager Installation Option of Software Provisioning Manager 1.0 SP
In the table, filter for the following: Database =
1.7 Accessing the SAP Library
The references to the SAP NetWeaver Library documentation in this guide always refer to the following on SAP Help Portal. When you come across a reference to SAP Library documentation in this guide, you always have to add the path of this reference to the basic URL for the SAP NetWeaver release your SAP product is based on, as given in the list below:
● SAP systems based on SAP NetWeaver AS for ABAP 7.52: https://help.sap.com/nw752abap Application Help SAP NetWeaver Library: Function-Oriented View ● SAP systems based on SAP NetWeaver Application Server for ABAP 7.51 innovation package: https://help.sap.com/nw751abap Application Help SAP NetWeaver Library: Function-Oriented View ● SAP systems based on SAP NetWeaver 7.5: http://help.sap.com/nw75 Application Help SAP NetWeaver Library: Function-Oriented View ● SAP systems based on SAP NetWeaver 7.4: http://help.sap.com/nw74 Application Help SAP NetWeaver Library: Function-Oriented View ● SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1: http://help.sap.com/nw731 Application Help SAP NetWeaver Library: Function-Oriented View
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Homogeneous and Heterogeneous System Copy PUBLIC 21 2 Planning
This section describes how to plan your system copy.
Related Information
Before You Start [page 22] Use Cases for System Copy [page 23] System Copy Methods [page 24] Creating a System Copy Plan [page 25] Basic Planning Aspects and Parameters [page 26] System Copy and Migration Optimization [page 29] Migration to SAP HANA Database [page 37]
2.1 Before You Start
● The SAP OS/DB Migration Check prepares you in an optimal way for a successful migration and supports smooth continued operations on the new platform. The OS/DB Migration Check is mandatory, if you are going to migrate a productive system. For more information, see https://support.sap.com/support-programs-services/services/os-db- migration.html . In addition to the information contained on this page, check the SAP OS/DB Migration Planning Guide that is available in the Media Library. ● Before you start the system copy, you must read the following : ○ SAP Notes Read the following SAP Notes for up-to-date information on system copy and corrections to the system copy documentation: ○ SAP Note 1680045 – Release Note for Software Provisioning Manager 1.0 ○ SAP Note 1738258 – System Copy of Systems Based on SAP NetWeaver 7.1 and Higher ○ SAP Note 888210 – NW 7.**: System copy (supplementary note) Make sure that you have the most recent version of the SAP Notes, which you can find at: https://support.sap.com/notes . ○ Guides for the target system installation This system copy guide describes only the source system export in full detail. As for the installation of the target system, this system copy guide describes only the system copy-specific steps in section Setting Up the Target System [page 95], but refers for all steps that are identical with a new system installation to the appropriate operating system and database-specific installation guide [page 21]. ○ SAP System Copy and Migration at https://wiki.scn.sap.com/wiki/display/SL/System+Copy+and +Migration
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 22 PUBLIC Planning ○ SAP system landscape copy: ○ Best Practice document SAP System Landscape Copy for SAP NetWeaver and SAP Solutions available at https://support.sap.com/esacademy ○ SAP Note 885343 – SAP System Landscape Copy ○ SAP Note 1990240 – Support of mixed landscapes (Unicode and Non-Unicode) ○ SAP Note 82478 – SAP system OS/DB migration ● If you have problems during the system copy, create a customer message using the application area BC- INS-MIG.
2.2 Use Cases for System Copy
You can apply the system copy for the following:
● Setting up system landscapes, where the SAP systems have different system IDs (
Note
You should perform a system copy in a test system first. This way you can identify customer-specific problems that might result from modifications.
● Changing the operating system, the database, or both. You can use different operating system releases or database releases for the source and target systems, but the SAP system release of the source and target systems must be the same. ● Changing the hardware. ● Disaster recovery from an existing database backup
Note
SAP systems based on SAP NetWeaver 7.4 SP03 and higher:
During any migration or copy of a system with declustered and/or depooled tables – such as an SAP HANA system – your target system receives the same database layout. That is, it receives declustered and depooled tables. Therefore, consider the recommendations for your target platform as described in SAP Note 1892354 .
Note
You can set up the SAP system infrastructure (development, quality assurance, and production system) without making a system copy as follows:
1. Install all SAP systems, starting with the development system. Customize the development system as described in the implementation documentation. 2. Transport the client-dependent and client-independent data to the quality assurance and production systems.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Planning PUBLIC 23 However, if you do not follow this concept, you can also install a system, customize it, and then perform a system copy.
2.3 System Copy Methods
You can choose between the following system copy methods:
Note
Before making your decision, read the documentation SAP System Copy and Migration at https:// wiki.scn.sap.com/wiki/display/SL/System+Copy+and+Migration in order to make yourself familiar with the available system copy and migration procedures.
● The database-independent procedure using SAP tools Use this method if database-specific methods are either not available or not suitable. For more information, see Database-Independent System Copy [page 56].
Note
If SAP HANA is the source database, you cannot use the Database Independent System Copy [page 56] procedure for SAP systems based on SAP NetWeaver AS for ABAP 7.52, because SAP NetWeaver AS for ABAP 7.52 already uses certain artifacts in the SAP HANA 2.0 database which are not supported by R3load . Use the SAP HANA Database-Specific Procedure [page 106] instead.
● The database-specific procedure using tools provided by the database vendor For more information, see Database-Specific System Copy [page 105] . ● Copy single instances only The following options are supported: ○ You can move a primary application server instance to a different host within your system. For more information, see Copying the Primary Application Server Instance Only [page 107]. ○ You can move a database instance to a different host within your system. For more information, see Copying the Database Only – Move Database Instance [page 108]. ○ You can refresh an existing database instance without having to copy the primary application server instance and to reinstall additional applications servers. For more information, see Copying the Database Only – Refresh Database Instance [page 109]. ○ You can refresh the content of an existing database without having to export the database content, but using a database backup.
Recommendation
We recommend that you use option Refresh Database Content if you need to equalize the database content of two or more already existing and configured systems, for example in automatized system landscapes with “template” systems which have to correspond to precisely defined standards, such as predefined host names, network settings, users, security policies.
For more information, see Copying the Database Only – Refresh Database Content [page 110].
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 24 PUBLIC Planning Caution
You cannot copy single product instances, usage types, or components!
● Changing the system variant If you want to change your system variant (for example, if you want to make your standard system a distributed or high-availability system), proceed as follows: 1. Perform the export [page 75]. 2. For the import, choose the relevant system copy options as described in the process flows of the system copy procedure [page 57].
2.4 Creating a System Copy Plan
Create a plan to perform the system copy.
Procedure
1. When copying a system that contains production data, choose the moment for the copy carefully. This could be a month-end or year-end closing. 2. Consider the downtime of the source system (for preparations and copying) when planning the system copy. 3. Consider a test run. Perform a test run of the system copy. You can use the time taken by the test run to calculate the system downtime:
○ If you want your target system to replace your source system, try to perform a complete test run. This means that the entire database is exported from the source system, transferred to the target system, and imported there. System downtime is approximately equal to the total test time (that is, time for export, transport, and import). ○ If you do not want to replace your source system, a partial test run (export of the entire database or parts of it) can be sufficient to calculate the system downtime. The source system is only down for the time of the export. Calculating the system downtime is particularly important for very large databases (VLDB) or when tapes are being used. The test run is also to determine the amount of export data. Choose the best data transfer method (for example, FTP or tape). We recommend that you only perform read/write actions on local file systems. 4. Define a schedule for the test migration and the final migration.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Planning PUBLIC 25 2.5 Basic Planning Aspects and Parameters
This section provides information about basic planning aspects and parameters required for system copy.
Support of Mixed Landscapes (Unicode and Non-Unicode)
If your system landscape is mixed with Unicode and Non-Unicode systems, or if you have third party software in your system landscape which does not support Unicode at all, check SAP Note 1990240 for potential support restrictions.
Using NFS-Mounted File Systems
Note that the overall performance of the system copy depends on all links in the chain, starting from the performance of the source database to the following:
● Performance of the server on which the export is executed ● File system to which the export data is written ● Target side that reads from the export medium and imports it into the target database ● Use a local directory to perform the export, in order to increase the performance and avoid data corruption. When using NFS, consult SAP Note 2093132 for recommendations about NFS configuration and restrictions. Also take into account that it may directly affect performance.
You have to make sure that all aspects are configured for optimal performance. For recommendations on NFS configuration, see .
Note
If you want to use NFS for the system copy export, make sure that you create secure file share permissions. Be aware that the communication protocol for NFS needs to be a safe one, for example SSFS.
Using a Network-Drive
If you want to use a Network-drive for system copy, make sure that you create secure file share permissions. Be aware that the communication protocol for this drive needs to be a safe one, for example SSFS (see also General Technical Preparations [page 44]).
Configuration Analysis and Hardware Configuration
● In the event of a major change in hardware configuration (for example, new machine type, new hard disk configuration, new file system type), consult your SAP-authorized hardware partner.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 26 PUBLIC Planning ● You need to determine the following: ○ Number of application servers ○ Expected size of the database ○ Additional disks or other hardware required ○ Required memory
Note
Refer to the section on hardware and software requirements in the SAP system installation documentation to determine the system requirements.
Choosing an SAP system ID
You can choose the new SAP system ID
Caution
To meet the requirements of the Workbench Organizer, you must choose different SAP system IDs for different SAP systems.
Make sure that your SAP system ID:
● Is unique throughout your organization Do not use an existing
SAP License
Once the installation is completed and the SAP system copy has been imported, you require a new license key for the target system. The license key of the source system is not valid for this system.
For information about ordering and installing the SAP license, see the SAP Library [page 21] for your release at:
Note
Navigate to the SAP Help Portal page for the SAP NetWeaver release your SAP product is based on as described in section Accessing the SAP Library [page 21] , and then continue the navigation as described below.
Solution Life Cycle Management SAP Licenses
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Planning PUBLIC 27 For more information about SAP license keys, see http://support.sap.com/licensekey or SAP Note 94998 .
Archiving files
Data that has been archived in the source system (data that does not reside in the database but was moved to a different storage location using SAP Archive Management) must be made accessible in the target system. Adapt the file residence information in the target system.
For more information, see the following:
● The SAP Library [page 21] for your release at:
Note
Navigate to the SAP Help Portal page for the SAP NetWeaver release your SAP product is based on as described in section Accessing the SAP Library [page 21] , and then continue the navigation as described below.
SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Data Archiving ● The blogs at https://blogs.sap.com/2016/10/11/software-application-lifecycle-management-sap-bw/ regarding SAP NetWeaver Application Lifecycle Management and housekeeping
Access to archive files is platform-independent.
When Using SAP Landscape Transformation Replication Server
If you use SAP Landscape Transformation Replication Server in your system landscape, we recommend that you stop replication and remove existing database triggers before you start the system copy. For more information about SAP Landscape Transformation Replication Server and its dependencies, see SAP Note 1605140 .
More Information
FAQ - System Copy and Migration at: https://wiki.scn.sap.com/wiki/display/SL/FAQ+-+System+Copy+and +Migration
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 28 PUBLIC Planning 2.6 System Copy and Migration Optimization
This section lists several methods that you can use to optimize the standard system copy procedure.
More information about system copy optimizations can be found in the document System Copy and Migration - Optimization at https://archive.sap.com/documents/docs/DOC-14257 and in SAP Note 1875778 .
Database Tuning for Source Databases other than SAP HANA [page 29] This is just a list of database parameters which could help you to tune your source database when migrating to SAP HANA. This list is not meant to give you detailed recommendations about the parameter settings.
Sorted Versus Unsorted Unload [page 31]
Package Splitting [page 32]
Table Splitting [page 33]
R3load Options [page 35] This section provides information about available R3load options.
Migration Monitor [page 36] The Migration Monitor is a tool which helps you to perform and control the unload and load process during the system copy procedure. The Migration Monitor is integrated into the Software Provisioning Manager (the “installer” for short), but it is also possible to use the monitor for copying older releases by starting it manually.
Distribution Monitor [page 36] You can use the Distribution Monitor to speed up Unicode Conversion by distributing the R3load workload to multiple machines.
Defining the Unload/Load Order [page 37]
2.6.1 Database Tuning for Source Databases other than SAP HANA
This is just a list of database parameters which could help you to tune your source database when migrating to SAP HANA. This list is not meant to give you detailed recommendations about the parameter settings.
Database Tuning Measures – Database Independent
If possible, update the database statistics.
Note
This recommendation is not valid for MSSQL Databases. For more information, see SAP Note 1660220 .
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Planning PUBLIC 29 Database Tuning Measures – IBM Db2 for z/OS
Create indexes deferred.
Database Tuning Measures – IBM Db2 for Linux, UNIX, and Windows
Refer to the documentation DB2 Optimization Techniques for SAP Database Migration And Unicode Conversion available at: http://www.redbooks.ibm.com/abstracts/sg247774.html and to the relevant SAP Note.
Note
IBM Db2 for Linux, UNIX, and Windows databases have their recommendations in separate notes, one for each release. You can find them easily searching for Standard Parameter Settings under SV-BO application area. For example, for IBM Db2 for Linux, UNIX, and Windows V9.7, the relevant SAP Note is 1329179 .
Database Tuning Measures – Oracle
● Refer to SAP Notes 936441 and 1918774 regarding Oracle settings for R3load- based system copy. ● Enlarge the number and size of redo logs experiences from other pilot projects by adding 4 additional redo logs of 100 MB each. ● Enlarge the number of db writers. ● Enlarge temporary tablespace PSAPTEMP (~20-30 GB). ● Increase sort_area_size or use pga_* parameters. ● Increase PSAPROLL (~20 GB).
Database Tuning Measures – SAP MaxDB
● You can find general documentation about tuning measures of the current SAP MaxDB release in the SAP Library for your release [page 21] at:
Note
Navigate to the SAP Help Portal page for the SAP NetWeaver release your SAP product is based on as described in section Accessing the SAP Library [page 21] , and then continue the navigation as described below.
Application Help Function Oriented View English SAP NetWeaver by Key Capability Database Administration Database Administration for MaxDB MaxDB Basic Information Concepts of the Database System Performance
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 30 PUBLIC Planning ● Increase the parameter CACHE_SIZE to the maximum available size of main memory. Add the unused main memory of non-running Application Server components to the database cache. ● Increase the parameter MAXCPU to the maximum available number of processors to which the database system can distribute user tasks. ● You can use the parameter checker. For more information, see SAP Note 1111426 .
Database Tuning Measures – SAP ASE
Refer to SAP Note 1722359 for recommendations on how to size and tune the SAP ASE database in an SAP NetWeaver or SAP Business Suite environment.
Database Tuning Measures – MS SQL Server
Refer to SAP Note 1054852 for recommendations on how to size and tune the MS SQL database in an SAP NetWeaver or SAP Business Suite environment.
2.6.2 Sorted Versus Unsorted Unload
During a system copy, you can perform the data export either “sorted” or “unsorted”.
The default setting is Use Unsorted Unload - the default was changed from “sorted” to “unsorted” with only some hard-coded exceptions. It is recommended that you keep the defaults. Only change the default on explicit advice by development support.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Planning PUBLIC 31 2.6.3 Package Splitting
It might be possible that some packages take long time to be exported due to the fact they contain much data. In such situations it is worth to split the package by using the Package Splitter. An example of the improvement when performing a split can be seen in the figure below:
The installer by default applies Package/STR Splitting . The installer prepares and runs the Package Splitter.
Related Information
Using the Package Splitter [page 161]
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 32 PUBLIC Planning 2.6.4 Table Splitting
It might be possible that specific tables take long time to be exported due to the fact they contain much data. In such situations you might consider splitting the table by using the Table Splitter. An example of the improvement when performing a table split can be seen in the figure below:
For copying large ABAP tables, the tool R3ta or - if the SAP kernel version of the source system is 7.40 or higher - SAPuptool has been developed to automatically generate WHERE conditions, with which a subset of table data can be accessed. These WHERE conditions are integrated into the R3load TSK files. Using WHERE conditions may not be optimal for every database management system and therefore has to be considered carefully.
Availability
You can use table splitting for ABAP systems with SAP kernel 6.40 or higher.
SAPuptool is available for table splitting with SAP kernel version 7.40 or higher. It is supported for both Unicode and non-Unicode source system and for both Unicode and non-Unicode target systems.
The installer automatically selects the corresponding tool depending on the SAP kernel version
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Planning PUBLIC 33 Advantages
● Large tables are processed in many small packages. If the export or import of a table aborts with an error, only the processing of the package with the error has to be repeated instead of (un)loading the complete table once again. ● The export and import of one table can be performed in parallel by starting several R3load processes to work on some packages in parallel.
Disadvantages
● If the parallel processing is not optimal or if the single packages are processed serial, the complete processing time for one table may increase when using WHERE conditions. ● R3ta tool only: The creation and evaluation of WHERE conditions is an iterating process which requires some experience and some detailed database knowledge. Many manual steps have to be performed. ● R3ta tool only: Under certain conditions it is recommended to create additional temporary indexes on the column used in the WHERE condition. Depending on the database, this may not be feasible during productive operation (time consuming, table locking, ...).
Known Problems
The sorting order may be different on non-Unicode source system and Unicode target system. This may lead to problems when deleting parts of table data during restart. If the import of one package aborted with an error, you therefore have to delete all data from this table and reload them all again.
Attention
● As the usage of WHERE conditions requires a lot of experience and many manual steps and because there are still some problems not yet solved, we cannot release this feature generally. ● You may use the feature WHERE conditions and the R3ta or - if the SAP kernel version of the source system is 7.40 or higher - the SAPuptool and in many cases it will work without problems, but if you run into problems, you cannot claim for support or an immediate fix of the problem. Nevertheless, we welcome any feedback which helps us to improve the tools. ● The generated WHERE conditions should not cover more than one column. If R3ta calculated conditions with more columns, run the tool again with different row-count parameters. ● If you decide to create WHERE conditions manually (without the R3ta or - if the SAP kernel version of the source system is 7.40 or higher - the SAPuptool), you must be aware of the fact, that a badly chosen WHERE condition can increase the total table processing time a lot. In addition, the consultant takes over the responsibility for the completeness of the data! ● You can often reduce the export time of a table which is processed with WHERE conditions if you create a (temporary) additional index on the column used within the WHERE condition.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 34 PUBLIC Planning Caution
This may not be possible on databases that need exclusive access on the table when creating an index.
Database-Specific Information about Table Splitting
Oracle: SAP Note 1043380 (Efficient Table Splitting for Oracle Databases)
Related Information
Preparing the Table Split [page 67] R3load Options [page 35]
2.6.5 R3load Options
This section provides information about available R3load options.
Note
An up-to-date version of the load tools - such as R3load, R3szchk, R3ldctl, SAPuptool - which were available so far only in the SAPEXEDB_<...>.SAR archive of the kernel media, has now been made available in the Software Provisioning Manager archive (SWPM10SP
You can use the following R3load options:
● R3load option -fast or -loadprocedure fast. ● R3load socket option: You can use the socket option, if your R3load has at least patch level 73 (compile date: 12.01.2008) ● Several R3load processes can be launched in parallel to export the packages. However, at a certain point, increasing the number of processes will not help with the performance and has the opposite effect. There is no direct way to determine the optimal number of processes. A rule of thumb though is to use 3 times the number of available CPUs. If you want to find the optimal value, you can perform tests in similar environments, such as in a DEV system.
● IBM Db2 for Linux, UNIX, and Windows: For more information, see SAP Note 1058437 – DB6: R3load options for compact installation
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Planning PUBLIC 35 ● Oracle: For more information, see SAP Note 1045847 – Oracle Direct Path Load Support in R3load
2.6.6 Migration Monitor
The Migration Monitor is a tool which helps you to perform and control the unload and load process during the system copy procedure. The Migration Monitor is integrated into the Software Provisioning Manager (the “installer” for short), but it is also possible to use the monitor for copying older releases by starting it manually.
Note
An up-to-date version of the load tools - such as R3load, R3szchk, R3ldctl, SAPuptool - which were available so far only in the SAPEXEDB_<...>.SAR archive of the kernel media, has now been made available in the Software Provisioning Manager archive (SWPM10SP
The Migration Monitor
● creates R3load command files ● triggers the creation of R3load task files if required ● starts the R3load processes to unload the data ● transfers packages from the source to the target host if required ● starts the R3load processes to load the data as soon as a package is available ● informs the person performing the system copy in case of errors
More Information
For more information, see:
● R3load Procedures Using the Migration Monitor [page 127] ● SAP Note 784118 (System Copy Tools for ABAP Systems)
2.6.7 Distribution Monitor
You can use the Distribution Monitor to speed up Unicode Conversion by distributing the R3load workload to multiple machines.
For more information, see SAP Note855772 .
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 36 PUBLIC Planning Note
An up-to-date version of the load tools - such as R3load, R3szchk, R3ldctl, SAPuptool - which were available so far only in the SAPEXEDB_<...>.SAR archive of the kernel media, has now been made available in the Software Provisioning Manager archive (SWPM10SP
2.6.8 Defining the Unload/Load Order
If you select the checkbox Define Special Package Unload Order on the installer screen SAP System Database Export, a dialog opens on which you can choose among the following options how to process the packages:
● In alphabetical order ● In custom order ● According to their size (largest first, for import and export)
The Migration Monitor has a property orderBy to specify the order of processing packages.
2.7 Migration to SAP HANA Database
This section provides information about special planning aspects of the migration to SAP HANA database.
Related Information
General Information About the Migration to SAP HANA [page 38] Prerequisites and Restrictions [page 40] Involved Tools [page 40] Considerations for Performance [page 43] Database Instance Export on Additional Hosts [page 43]
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Planning PUBLIC 37 2.7.1 General Information About the Migration to SAP HANA
To migrate your source database to the SAP HANA database, you perform a heterogeneous system copy using standard tools, such as software provisioning manager (the “installer”), R3load, and the Migration Monitor.
A heterogeneous system copy has the following characteristics:
● Operating system is changed (in this case, system copy is called OS migration – not relevant for the migration to SAP HANA) or ● Database system is changed (in this case, system copy is called DB migration) or ● Operating system and database system are changed (in this case, system copy is called OS/DB migration)
You perform a heterogeneous system copy using a database-independent procedure (with some exceptions for certain OS migrations, where cross-platform backup or restore is supported).
You can migrate your database to SAP HANA database as of the following releases:
● SAP Business Warehouse only: SAP NetWeaver 7.3 EHP1 Support Package 4 ● SAP NetWeaver 7.4 ● SAP NetWeaver 7.5 and higher
To migrate your database to SAP HANA database, the following conditions have to be met:
● Your SAP system must meet the minimum hardware and software requirements listed in the following table:
Requirement Values
Hardware Your operating system platform must be 64-bit.
Operating System Version For a comprehensive list of supported operating system releases, see the Prod uct Availability Matrix (PAM) at: https://support.sap.com/pam .
Database Software The following source database platforms are supported:
○ Oracle 11.2 or higher ○ MS SQL Server 2008 or higher ○ IBM DB for Linux, UNIX, and Windows V9.7 or higher ○ SAP MaxDB 7.8 or higher ○ SAP Sybase ASE 15.7 or higher ○ IBM Db2 for i 6,1 or higher ○ IBM Db2 for z/OS V9 or higher
SAP Kernel ○ SAP NetWeaver 7.3 EHP1 only: SAP Kernel 7.22 EXT 64-bit is installed. ○ AS ABAP 7.4 (SP0 and SP01) only: SAP Kernel 7.38 is installed. ○ AS ABAP 7.4 (SP02 and higher) only: SAP Kernel 7.40 or higher is instal led. Update the kernel to the latest patch available in the Marketplace as per SAP Note 19466 . If an update of the kernel is required, follow the instructions in SAP Note 1636252 .
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 38 PUBLIC Planning Requirement Values
SAP Java Virtual Machine (SAP SAP JVM 6 or higher is installed. JVM)
● SAP HANA database is available only for SAP systems based on SAP Netweaver Application Server ABAP or for SAP systems based on SAP Netweaver Application Server Java. It is not available for SAP NetWeaver dual-stack (ABAP+Java) systems such as SAP Process Integration.
Note
If your system is a dual-stack (ABAP+Java) one, you first have to split it into one ABAP and one Java stack before migrating to SAP HANA database. For example, perform a dual-stack split procedure before upgrading or uninstall the Java stack and re-install it as a separate system if it is possible for your scenario.
For more information about how to perform a dual-stack split procedure, see the Dual-Stack Split guide, which is available at: https://support.sap.com/sltoolset System Provisioning Split Option of Software Provisioning Manager Dual-Stack Split Guides
● SAP HANA runs only on Unicode.
Generic Information
● Read the following information: ○ The blog Migration to SAP HANA: SAP Kernel update for the migration in SAP Community Network about R3* tools provided with the SAP kernel that are involved in the migration to SAP HANA (Migration to SAP HANA: SAP Kernel Update for the Migration): http://scn.sap.com/community/it-management/alm/software-logistics/blog/2013/09/30/ migration-to-sap-hana-sap-kernel-update-for-the-migration ○ In addition, take a look at the blog Migration to SAP HANA using Software Provisioning Manager: How to Begin? at: http://scn.sap.com/community/it-management/alm/software-logistics/blog/2013/10/04/migration- to-sap-hana-using-swpm-how-to-begin ○ The blog SAP BW Powered by SAP HANA- Some points to remember for Database Migration to HANA providing further details for the migration to SAP HANA – with focus on SAP BW, but partly also valid for general migrations to SAP HANA: http://scn.sap.com/community/netweaver-bw-hana/blog/2013/08/29/sap-bw-powered-by-sap- hana-some-points-to-remember-for-database-migration-to-hana ● For an overview of migration path options to SAP NetWeaver 7.4 or SAP NetWeaver 7.5 running on SAP HANA, see the End-to-End Implementation Roadmap guides available at: https://help.sap.com/nw SAP NetWeaver <7.4 or 7.5> Integration ● See also page Migration of SAP Systems to SAP HANA at https://blogs.sap.com/2013/12/03/migration-of- sap-systems-to-sap-hana/ for information on planning the migration procedure of your SAP systems to in an on-premise landscape. ● For more information about release and roadmap information around the kernel versions and their relationship to SAP NetWeaver support packages including important notes on downward compatibility
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Planning PUBLIC 39 and relSAP HANAease dates, see the document Understanding Kernel Releases for the SAP NetWeaver AS ABAP at: https://archive.sap.com/documents/docs/DOC-54170
Application-Specific Information
For the migration of SAP Business Warehouse (SAP BW), see the following information:
● For SAP BW running on SAP HANA, see the End-to-End Implementation Roadmap for SAP NetWeaver BW powered by SAP HANA at https://help.sap.com/nw SAP NetWeaver <7.4 or 7.5> Integration ● SAP NetWeaver BW Application Lifecycle Management at: https://blogs.sap.com/2016/10/11/software- application-lifecycle-management-sap-bw/ ● Best practice information for SAP NetWeaver BW powered by SAP HANA scale out at: https:// blogs.sap.com/2013/03/27/sap-netweaver-bw-powered-by-sap-hana-scale-out-best-practices/
2.7.2 Prerequisites and Restrictions
Make sure that you take the following prerequisites and restrictions into consideration:
● Delivery of SAP HANA appliances can take some time – therefore, order required target hardware early. ● Before starting the database migration, perform a hardware check using the script HanaHwCheck.py – for more information, see SAP Note 1652078 . In case the hardware check fails, try the latest version of the script that is attached to SAP Note 1658845 . ● For recommended Linux settings, refer to SAP Note 1824819 (SAP HANA DB: Recommended OS settings for SLES11 / SLES4SAP SP2). ● Install the latest available revision of SAP HANA before the migration. ● Make sure that you install a current SAP HANA client that has the same version as the SAP HANA database. For more information about how to install a current SAP HANA client, see SAP Note 1825053 . ● Install the SAP HANA studio as described in the SAP HANA Studio Installation Guide available at http:// help.sap.com/hana_appliance ● Installation and Upgrade Information and in SAP Note 1789632 . ● Installation of external software on the SAP HANA appliance must be in compliance with SAP Note 1730928 . ● To prepare the adjustment of your custom code, install the ABAP Development Tools as described in the guide provided in SAP Note 1718399 . ● For SAP Warehouse (SAP BW), check SAP Note 1600929 , providing further information relevant for the migration to SAP HANA.
2.7.3 Involved Tools
This section provides expert information and recommendation for some of the involved migration tools.
For an overview of the most important migration tools for ABAP, see https://archive.sap.com/documents/ docs/DOC-34258 .
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 40 PUBLIC Planning Software Provisioning Manager
Software Provisioning Manager (the “installer”) offers many services, including system installation and system copy. For our use case of database migration, it orchestrates all involved tools.
For more information about latest corrections in Software Provisioning Manager 1.0 for the migration to SAP HANA, see the corresponding blog Migration to SAP HANA: Latest News about Software Provisioning Manager 1.0 in SAP Community Network at:https://blogs.sap.com/2013/09/30/latest-news-about-swpm-10-sl- toolset/
Migration Monitor (Migmon)
The Migration Monitor is part of software provisioning manager 1.0. It uses the EXT, WHR, STR, TPL files to control the unload and load, to accelerate the load by automatic parallelization, and to generate the R3load task and command files (TSK and CMD files).
Especially for SAP HANA, the Migration Monitor comprises a migmonctrl.jar add-on that gets invoked automatically to adjust the amount of R3load jobs dynamically during the import – this is described in the Import section below.
For more information, see:
● R3load Procedures Using the Migration Monitor [page 127] ● SAP Note 784118 (System Copy Tools for ABAP Systems) ● Restarting R3load Processes [page 94].
R3load
R3load performs all load tasks in a database- and platform-independent format. It generates the database export of all SAP objects that are defined in the ABAP Dictionary and archives the configuration and components in the file system. Then, it performs the load of ABAP tables into the target database. It is available via the kernel of the ABAP application server.
R3ldctl
R3ldctl makes information of source system database tables available for migration tools offline by reading ABAP Dictionary structures from the source database. It creates structure (STR) files that describe the definition of tables, indexes and views, and it creates database-specific template (TPL) files containing commands in Data Definition Language (DDL), which define data structures. R3ldctl is also available via the kernel of the ABAP application server.
For more information, see Exporting the Source System [page 75].
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Planning PUBLIC 41 R3ta or - if the SAP kernel version of the source system is 7.40 or higher - SAPuptool
To copy large tables, use the R3ta table splitter tool or - if the SAP kernel version of the source system is 7.40 or higher - SAPuptool. Both automatically generate WHERE conditions with which a subset of table data can be accessed and with which the export and import of one table can be performed in parallel by starting several R3load processes that work on packages. These WHERE conditions are integrated into the R3load TSK files. If the export or import of a table is cancelled with an error, only the processing of the package with the error has to be repeated instead of loading or unloading the complete table another time. R3ta or - if the SAP kernel version of the source system is 7.40 or higher - SAPuptool is available via the kernel of the ABAP application server.
Package Splitter
Package Splitter reduces the overall runtime of export and import by distributing packages in an optimal way from the existing structure files (STR + EXT). It is part of software provisioning manager 1.0.
Time Analyzer (Migtime)
To get statistical data about runtimes, use Migtime. It supports you in analyzing the runtimes of the export and the import:
● It calculates the runtime per package ● It lists the long running objects within a package for further splitting ● It creates a list (either a text or an HTML file) with start and end date or time per package ● It is provided with software provisioning manager 1.0 (MIGTIME.SAR is available in
For more information, see SAP Note 784118 .
Tools Specific for SAP BW
For SAP BW, consider to use the following specific tools:
● A specific checklist tool for SAP BW (see SAP Note 1729988 – SAP NetWeaver BW powered by SAP HANA - Checklist Tool) automates the check of best practice guidelines for operations and pre-requisites for the migration of an existing SAP BW system to SAP HANA. ● Before migrating to SAP BW on SAP HANA, you can use the SAP BW ABAP Routine Analyzer to identify ABAP statements that can potentially be optimized for SAP HANA – for more information, see SAP Note 1847431 (SAP NetWeaver BW ABAP Routine Analyzer). ● To make the migration of an existing SAP BW deployment to SAP HANA easier, the SAP NetWeaver Migration Cockpit for SAP HANA combines several tools – for more information, see SAP Note 1909597 (SAP NetWeaver BW Migration Cockpit for SAP HANA).
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 42 PUBLIC Planning 2.7.4 Considerations for Performance
Note the following recommendations for the performance of the migration procedure:
● As a rule of thumb, it is recommended that you configure two or three parallel R3load processes per CPU on the host on which the corresponding R3load is running. ● Closely monitor the CPU and I/O utilization to adapt the number to actual project conditions. ● If possible, keep a dedicated internal disk with an own controller for the export directory. ● Only change table type from column store to row store, if proposed by SAP HANA development support. ● We recommend to use the mass loader option of the installer: ○ For this, SAP HANA Revision 51 or higher is required (see SAP Note 1806935 ) ○ To activate the option, set the environment variable HDB_MASSIMPORT=YES before starting the installer.
● With the latest versions of the installer, parallel export/import is available for products based on SAP NetWeaver 7.3 including EHP1. For latest information, see SAP Note 1775293 . ● If scale-out is released for your product, consider to use an SAP HANA standby server node for the import to improve performance. For more information, see the corresponding information in Installing the Target System - Additional Considerations for the Migration to SAP HANA Database [page 100]. ● Throughput is quite individual and depends on the hardware configuration and other factors. You can use the Java tool Migtime to evaluate the runtime of export/import – for more information, see SAP Note 784118 . It might require multiple runs to find bottlenecks and optimize them. ● For comparing ABAP code execution times after a migration to SAP HANA, consider the recommendations in SAP Note 1942889 (Comparing ABAP code execution times after HANA migration). ● To increase the performance of the export you can use more than one SAP application server of the source system for the export. For more information, see Database Instance Export on Additional Hosts [page 43].
2.7.5 Database Instance Export on Additional Hosts
Especially for the migration to SAP HANA, it has become common to use an SAP HANA standby server for the import into the database instance. As SAP HANA servers are very powerful, the import is delayed because it has to wait for the relatively slow data delivery from the export.
To increase the performance of the export you can use more than one SAP application server of the source system for the export. For example, you can use the hosts of the existing additional application server instances of the source system.
You can do this by choosing Database Instance Export on Additional Host in the installer after starting the Database Instance Export.
During the procedure, if the feature is chosen, “package-filter files” are created, which split the packages into equal (by size or runtime) parts according to the number of hosts entered.
For more information about the additional steps required for this procedure, see System Copy Procedure [page 57].
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Planning PUBLIC 43 3 Preparation
Before you start the system copy, you must perform the following preparation steps.
3.1 General Technical Preparations
To make a consistent copy of the database , you need to prepare the source system and perform some subsequent actions on the target system. This is not necessary when performing a test run.
Context
The following section describes important preparations on the source system before you perform homogeneous or heterogeneous system copy.
For more information about SAP System Administration, see the Administration information in the SAP Library [page 21] for the SAP NetWeaver release your source system is based on:
Note
Navigate to the SAP Help Portal page for the SAP NetWeaver release your SAP product is based on as described in section Accessing the SAP Library [page 21] , and then continue the navigation as described below.
SAP NetWeaver Release SAP Library Path
● SAP systems based on SAP NetWeaver 7.3 including En Operations Technical Operations for SAP NetWeaver hancement Package 1 ● SAP systems based on SAP NetWeaver 7.4 ● SAP systems based on SAP NetWeaver 7.5 ● SAP systems based on SAP NetWeaver Application Server for ABAP 7.51 innovation package ● SAP systems based on SAP NetWeaver Application Server for ABAP 7.52
Procedure
1. Before you start a system copy , check the minimum kernel patch level required by the support package level of the source system.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 44 PUBLIC Preparation It might be necessary to replace the SAP kernel delivered with the installation kit and installed during the installation of the target system by a newer kernel patch level before starting the target system. If you have to replace the delivered SAP kernel, you can do this after the installation of the primary application server instance.
For more information about release and roadmap information around the kernel versions and their relationship to SAP NetWeaver support packages including important notes on downward compatibility and release dates, see the document Understanding Kernel Releases for the SAP NetWeaver AS ABAP at: https://archive.sap.com/documents/docs/DOC-54170 2. Check if canceled or pending update requests exist in the system. If canceled or pending updates exist, you must update these again or delete them from all clients. Proceed as follows: a. Call transaction SM13. b. Delete the default values for the client, user, and time. c. Choose all update requests. d. Check if table VBDATA contains any entries. If there are entries, update or delete the corresponding update requests. e. To check whether this action was successful, call transaction SE16 for table VBDATA. 3. Stop scheduling of all released jobs.
Go to transaction SE38 and run report BTCTRNS1. For more information, see SAP Note 37425 . 4. Adapt the operation mode timetable to make sure that no switching of operating modes takes place while a system is being copied (transaction SM63). 5. Write down the logical system names of all clients: ○ If you plan to overwrite an existing system with a system copy, make sure you write down the logical system names of all clients in the system that will be overwritten (transaction SCC4). Since the logical system names will be overwritten, in the event of differences, you must change them back to their original names (as they existed in the system that is overwritten) in the follow-up actions after the system copy . ○ If you create a new system with a system copy (for example, create an upgrade test system), make sure that the logical naming strategy for this new system is consistent with your existing logical system naming convention. SAP Business Warehouse (BW) only: If you are still in the process of planning your BW system landscape, see SAP Note 184447 for information about how to set up your system landscape, especially for information about system naming. ○ If your system copy is used to replace hardware for the DB server, migrate to a different database system or operating system (that is, source system for the copy is the same as the copy target), no changes to logical system names are required. 6. Before you run the export of the SAP HANA database, check the fragmentation of the rowstore and – if required – defragment it as described in SAP Note 1813245 . 7. Before performing the source system export, make sure that you do the following: a. Delete QCM tables from your source system: 1. Before you delete the QCM tables, ensure the following: ○ The tables are consistent – no restart log or conversion procedure termination must be displayed. ○ The data of the original table can be read. ○ The application programs that use the affected original table run correctly. 2. Call transaction SE14.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Preparation PUBLIC 45 3. Choose Extras Invalid temp. table All QCM tables that can be deleted are displayed. 4. Mark the tables and delete them. b. Run report RS_SCRP_D020S_CLEAN to check if there are invalid entries in tables D020S and DYNPSOURCE. If invalid entries are detected, remove them before running the export. For more information, see SAP Note 870601 . 8. To avoid stopping the database due to a log directory being full, make sure that the log backup is enabled during the import. 9. Heterogeneous System Copy: If you plan to migrate your database to SAP HANA database, do the following: a. Perform the preparation steps described in SAP Note 1600929 . b. Perform the following preparation steps: ○ SAP BW only: Perform the preparation steps described in SAP Note 1600929 . ○ AS ABAP 7.4 only: ○ For more information about the SAP HANA database migration, check the Administrator's Guide for your SAP Business Suite application available at: ○ https://help.sap.com/viewer/p/SAP_ERP,_VERSION_FOR_SAP_HANA Operations Administrator’s Guide ○ https://help.sap.com/viewer/p/ SAP_CUSTOMER_RELATIONSHIP_MANAGEMENT_FOR_HANA Installation and Upgrade Administrator’s Guide ○ https://help.sap.com/scm Operations Application Operations Guide ○ https://help.sap.com/srm Operations Application Operations Guide ○ Perform the steps described in SAP Note 1851549 . 10. Prepare the media required for the export [page 52]: a. Prepare the Software Provisioning Manager archive as described in Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 53]. b. If you want to use a dedicated kernel, you can specify this on the screen Use Dedicated Kernel for System Copy while performing the export. If you choose this option, you are prompted for the required kernel archives.
For more information, see Downloading Dedicated Kernel Archives for the Export [page 54].
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 46 PUBLIC Preparation 3.2 Product-Specific Preparations
FI Customers
● You can perform an additional consistency check by running the job SAPF190 before copying the source system, as well as after copying the target system, and then compare the results. Make sure that no customer data is changed in the meantime. You can do this as follows: In transaction SAPF190, for classic FI, choose Accounting Financial Accounting General ledger Periodic Processing Closing Check/count Reconciliation . For a new general ledger, choose Accounting Financial Accounting General ledger Periodic Processing Closing Check/count Reconciliation (New) . ● You can further check consistency by running the jobs listed below before copying the source system, as well as after copying the target system, and then compare the results. ○ RFUMSV00 (tax on sales/purchases) ○ RAGITT01 (asset history sheet) ○ RAZUGA01 (asset acquisitions) ○ RAABGA01 (fixed asset retirements) Make sure that no customer data is changed in the meantime.
CO Customers
You can perform an additional consistency check by running the report group 1SIP before copying the source system, as well as after copying the target system, and then compare the results. Make sure that no customer data is changed in the meantime.
Caution
Prerequisites for an export:
Before performing an export, make sure that no incremental conversion is in progress.
To test if an incremental conversion is in progress, run transaction ICNV. If there are any table entries in table TICNV, an incremental conversion is in progress. In this case, you have the following options:
1. Defer the migration until the incremental conversion has finished. 2. Try to finish the incremental conversion by performing the following steps:
● If the tables are in state For conversion or in state Done, delete the entries by choosing Control Delete Entry . ● If the tables are in any other state, you have to finish the incremental conversion. Choose Assistant and proceed according to the online documentation.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Preparation PUBLIC 47 Caution
Heterogeneous system copy only:
Before you start the export of your source system, make sure that the tables TATGPC and TATGPCA are empty. To do so, use your database utility and delete the contents of these tables with the following statements:
DELETE from TATGPC
DELETE from TATGPCA
If the tables are not empty and you do not delete the contents of these tables you encounter problems while importing the data to your target system because of non-NULL capable fields in these tables.
SAP Business Warehouse
● When planning the copy of an SAP Business Warehouse (BW) system, read SAP Notes 886102 and 1707321 . ● Especially if you want to perform a heterogeneous system copy to another database, make sure that all the data from the Persistent Staging Area (PSA) associated with a 7.X DataSource are extracted and loaded to the Data Targets using Data Transfer Process (DTP) before you perform the database migration. For more information, see SAP Note 2129192 . ● For special preparations regarding the migration to SAP HANA database, see Preparing the Migration to an SAP HANA Database [page 48]
3.3 Preparing the Migration to SAP HANA Database
This section provides references to information about how to prepare the migration to SAP HANA database.
Note
SAP Kernel Version 7.38 and higher: Cluster and pool tables are made transparent during the migration to the SAP HANA database. Once you migrate to SAP HANA database, currently there is no automatic way to return back to your source database.
Prerequisites
Apply SAP Note 1783937 , so that partitioning restrictions are recognized when SQL files are created. Otherwise, the import of tables with more than 2 billion records will fail.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 48 PUBLIC Preparation Unicode Conversion
SAP HANA requires Unicode. Should you have a non-Unicode system, perform a Unicode conversion before the migration or plan a combined migration with Unicode conversion, which is technically also possible. Be aware that R3load requires significantly more CPU time with a combined Unicode conversion, resulting in a reduced number of configurable R3load jobs. For more information, see the Unicode Conversion Overview Guide available at: https://blogs.sap.com/2009/04/08/unicode-conversion-overview-guide/
The Distribution Monitor can optimize the downtime of a Unicode conversion by distributing the R3load workload to several machines – nevertheless, the Distribution Monitor is not released for SAP HANA, so it cannot be used in a combined migration and Unicode conversion procedure, but only if you convert to Unicode as separate activity before the migration. Because the approach with Distribution Monitor increases the complexity of the conversion, use it only if really needed. For more information, see:
● SAP Note 855772 (Distribution Monitor) ● SAP Note 1001383 (Distribution Monitor - Known problems and fixes) ● User guide that is part of the tool archive (DISTMON.SAR) ● SAP Note 989116 (Distribution Monitor: Troubleshooting Guide)
Migration Tool Versions
Always use latest versions of the migration tools:
● R3* tools (R3load, R3ldctl, R3szchk, R3ta or - if the SAP kernel version of the source system is 7.40 or higher - SAPuptool): ○ An up-to-date version of the load tools - such as R3load, R3szchk, R3ldctl, SAPuptool is available in the Software Provisioning Manager archive (SWPM10SP
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Preparation PUBLIC 49 Kernel
Use the latest kernel media for the installer as listed in SAP Note 1680045 ( Release Note for software provisioning manager 1.0 Kernel media for SWPM* ). Make sure to use the same kernel version both for export and import. For more information, see General Technical Preparations [page 44].
For more information about release and roadmap information around the kernel versions and their relationship to SAP NetWeaver support packages including important notes on downward compatibility and release dates, see the document Understanding Kernel Releases for the SAP NetWeaver AS ABAP at: https://archive.sap.com/ documents/docs/DOC-54170
Creating DDL Statements
Before you start the export, make sure to run the report SMIGR_CREATE_DDL that generates DDL statements for the migration.
For more information, see Generating DDL Statements [page 64].
Table Splitting Preparation
For more information about how to prepare table splitting, see Preparing the Table Split [page 67]
Package Splitting
Package splitting is activated by default. Do not deactivate it.
For more information about how to prepare table splitting, see Preparing the Package Split [page 71]
Housekeeping
Before the migration, delete and archive obsolete data from tables that show the largest growth in data volume. For more information, see:
● The Data Management Guide for SAP Business Suite available in SAP Service Marketplace at: https:// support.sap.com/en/solution-manager/processes-72.html Processes Data Volume Management ● SAP Note 679456 (Reducing data volume before Unicode conversion).
If not instructed otherwise, carry out the corresponding activities to reduce the data volume during system uptime.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 50 PUBLIC Preparation Implement SAP Note 1659622 in the source system. It provides the ABAP report SMIGR_BIG_ROW_STORE_TABS. This report can be used to identify large tables that will be stored as row store tables in SAP HANA. A small memory footprint of the row store is beneficial to minimize the database startup time.
Especially for SAP Business Warehouse (SAP BW), you can profit from an automated housekeeping, offered as task list of the ABAP task manager for lifecycle management automation. For more information, see SAP Note 1829728 (BW Housekeeping Task List).
Further Preparations
● Read SAP Note 1775293 (Migration/system copy to SAP HANA using the latest SWPM 1.0)
Note
If you want to get automatic notifications about changes to this SAP Note, you can configure to receive email notifications on this page in SAP Community Network.
● R3szchk calculates space requirements on the target database for ABAP tables and indexes and rough estimation of overall size for target database. Per default, R3szchk gets executed by the installer. The result is an EXT and a DBSIZE.XML file.
Note
If the target database is SAP HANA, the DBSIZE.XML file is not used as the sizing is done already by SAP’s sizing tools for SAP HANA.
If R3szchk is very slow, check SAP Note 1047369 . ● Request or generate a migration key. For more information, see https://support.sap.com/en/my-support/ keys.html . ● Before the export, run the reports SDBI_CLUSTER_CHECK_PERFORM and SDBI_CHECK_BCD_NUMBERS. This avoids issues during the export and import because of corrupt or initial cluster records or decimal numbers. For more information, see SAP Note 1784377 (Checking pool tables and cluster tables). ● Avoid more than one statistics server for your SAP HANA database. Otherwise, the import step can fail because of a “standby” statistics server. Remove any configured standby statistics servers before the import. ● Perform a test run of the system copy procedure to calculate downtimes of your source system based on experiences made during the test run. Adapt the general process to your system and environment. For more information, see Creating A System Copy Plan [page 25]. ● Order and install a new SAP license. For more information, see Various Planning Aspects and Parameters [page 26]. ● Prepare the source system as described in General Technical Preparations [page 44] and Product-Specific Preparations [page 47]. For example, check for canceled or pending update requests and operation mode
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Preparation PUBLIC 51 SAP Business Suite Applications
For more information about the overall migration process, see SAP Note 1785057 .
To ensure a successful migration, you should perform the following preparation steps:
1. If there are tables with high data volume in your source database where the number of records exceeds a certain limit, partitioning of these tables in your SAP HANA database is required. For more information, see SAP Note 1783937 . 2. Note that for both SAP tables and customer tables, cluster tables will be automatically transformed into transparent tables during the migration. Also pool tables will be converted into transparent tables. For more information about which pool tables are converted into transparent tables and when, see SAP Note 1785057 . To verify that this transformation will work properly during the migration, the source database should be checked. For more information, see SAP Note 1784377 . For example, cluster or pool tables that contain invalid values cannot be migrated. Check if there is custom code (customer development) in your system that can directly access tables that can be resolved. Such code is no longer valid. Note that applications may not rely on implicit sorting of result sets of accesses to former pool and cluster tables that have been transformed to transparent tables. For more information, see SAP Note 1785057 .
SAP Business Warehouse
● Perform the preparation steps described at: ○ The document Best Practice Guide - Classical Migration of SAP NetWeaver AS ABAP to SAP HANA available at: https://archive.sap.com/documents/docs/DOC-47657 ○ https://blogs.sap.com/2016/10/11/software-application-lifecycle-management-sap-bw/ ○ https://rapid.sap.com/bp/#/RDS_RDBMS_4_BW Solution Deployment: Configuration Guide of the SAP Rapid Deployment Solution "Rapid Database Migration of SAP NetWeaver BW to SAP HANA" ● Perform the preparation steps described in SAP Note 1600929 .
3.4 Preparing the Media Required for Performing the Export
For performing the export on the source system, you only need to download and extract the Software Provisioning Manager 1.0 archive which contains the installer.
For the media required for performing the target system installation, see section Preparing the installation Media in the installation guide [page 21] for the operating system platform and database of your target system.
Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 53] You must always download and extract the Software Provisioning Manager 1.0 archive from the SAP Software Download Center because you must use the latest version.
Downloading Dedicated Kernel Archives for the Export [page 54]
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 52 PUBLIC Preparation If you want to use a dedicated kernel for the database export , you must download the SAPEXE.SAR and SAPEXEDB.SAR for your operating system, kernel release and database beforehand.
3.4.1 Downloading and Extracting the Software Provisioning Manager 1.0 Archive
You must always download and extract the Software Provisioning Manager 1.0 archive from the SAP Software Download Center because you must use the latest version.
Prerequisites
● Make sure that you use the latest version of the SAPCAR tool when manually extracting the Software Provisioning Manager archive.
Note
An older SAPCAR version might extract archive files in a wrong way and this could prevent the installer from working consistently.
Proceed as follows to get the latest version of SAPCAR: 1. Go to https://launchpad.support.sap.com/#/softwarecenter SUPPORT PACKAGES & PATCHES By Category SAP TECHNOLOGY COMPONENTS SAPCAR . 2. Select the archive file for your operating system and download it to an empty directory. 3. To check the validity of the downloaded executable, right-click the executable and choose Properties. On the Digital Signatures tab you can find information about the SAP signature with which the executable was signed. 4. Rename the executable to sapcar.exe. For more information about SAPCAR, see SAP Note 212876 .
Context
An up-to-date version of the load tools - such as R3load, R3szchk, R3ldctl, SAPuptool - which were available so far only in the SAPEXEDB_<...>.SAR archive of the kernel media, has now been made available in the Software Provisioning Manager archive (SWPM10SP
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Preparation PUBLIC 53 Procedure
1. Download the latest version of the Software Provisioning Manager 1.0 archive SWPM10SP
https://support.sap.com/sltoolset System Provisioning Download Software Provisioning Manager 2. Unpack the Software Provisioning Manager archive to a local directory using the following command:
Note
Make sure that all users have at least read permissions for the directory to which you unpack the installer.
Caution
Make sure that you unpack the Software Provisioning Manager archive to a dedicated folder. Do not unpack it to the same folder as other installation media.
3.4.2 Downloading Dedicated Kernel Archives for the Export
If you want to use a dedicated kernel for the database export , you must download the SAPEXE.SAR and SAPEXEDB.SAR for your operating system, kernel release and database beforehand.
Context
Using this feature, you no longer have to do kernel updates in your systems just for the purpose of being able to copy it. Instead, the installer provides you the option to use a different kernel just for the purpose of system copy. This means you do not provide a kernel to be installed but only to be used by the installer for performing the export. For this option, you have to provide a separately downloaded SAPEXEDB.SAR and SAPEXE.SAR archive.
Note
The signature of installation archives is checked automatically by the installer [page 78] during the Define Parameters phase while processing the Software Package Browser screens. The installer only accepts archives whose signature has been checked. After scanning the archives and verifying the signature, an info file is written where you can find detailed information about matching and non-matching archive files. You can access this info file by choosing the info file link in the Archive Scanning Result section of the Software Package Browser screen. The info file contains only the results of the latest archive scan. For more information, see SAP Note 2393060 .
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 54 PUBLIC Preparation Procedure
1. Go to http://support.sap.com/swdc Software Downloads SUPPORT PACKAGES & PATCHES By Category Additional Components SAP Kernel
Caution
○ Make sure that you always choose SAPEXE
Example
○ If SAPEXE
○ SAPEXE
Note
SAP KERNEL
○ If you want to install an SAP system based on SAP NetWeaver 7.5, you can only choose 7.45 UNICODE forSAP KERNEL
Note
SAP KERNEL
○ If you want to install an SAP system based on SAP NetWeaver 7.5, you can only choose 7.45 UNICODE forSAP KERNEL
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Preparation PUBLIC 55 4 Database Independent System Copy
With the installer, you can export and import your database content in a database-independent format. The installer uses the R3load tool for exporting and importing the database content .
R3load generates a database export of all SAP objects that are defined in the ABAP Dictionary, including the configuration and components in the file system.
Note
Make sure that you have the most recent version of the R3load tool , which you can download from https://launchpad.support.sap.com/#/softwarecenter .
An up-to-date version of the load tools - such as R3load, R3szchk, R3ldctl, SAPuptool - which were available so far only in the SAPEXEDB_<...>.SAR archive of the kernel media, has now been made available in the Software Provisioning Manager archive (SWPM10SP
Note
Declustering / depooling of ABAP tables is supported for SAP systems based on SAP NetWeaver 7.4 SP03 and higher. For more information, SAP Note 1892354 .
Constraints
R3load Restrictions ● The installer generates a database dump of all SAP objects that are defined in the ABAP Dictionary (R3load). Other objects are not exported by the installer. ● For a consistent database export, no transactions on export-relevant database objects are allowed during the export. Otherwise, the export has to be restarted. Therefore, we recommend that you shut down the SAP system (excluding the database!) for the export. The database must still be running. ● Changes to database objects that cannot be maintained in the ABAP Dictionary (transaction SE14), such as the distribution of tables over several tablespaces or dbspaces, are lost after the system copy. ● Indexes longer than 18 characters are not allowed on the database to be exported.
Multiple Applications in SAP HANA Systems For more information about multiple applications in SAP HANA systems, see SAP Notes 1826100 and 1661202 .
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 56 PUBLIC Database Independent System Copy If the database configuration of your database is stored in the file system, we recommend you to back up these configuration files before deleting the database.
Splitting STR Files
● During the standard system copy process, all tables of the SAP system are grouped into packages, whereby all tables with the same data class belong to the same package. The processing unit for one unload/load process is a package. The packages differ in number and size of contained tables, resulting in varying unload/load runtimes. The overall runtime can be reduced by creating packages of the same size, that is, creating packages with a similar processing time. You can achieve this by splitting the default packages (one package per data class) into more and smaller pieces. ● There are several options of how to split packages. For a detailed description of the options, see the F1 help about the parameters prompted on the Split STR Files screen while running the installer 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 enabled by default. If you select the splitting option (if you did not already perform some tests before), using the splitting tool parameters selected by the installer is a good starting point.
Caution
If you want to split STR files, you must first create the EXT files for the target database system. You can find the EXT files in your export dump directory, subdirectory DB/
4.1 System Copy Procedure
This section describes the system copy procedure using R3load.
Prerequisites
Specify an empty directory with sufficient disk space for the export dump on the host where you want to perform the export. Make sure that this directory does not contain any files from any previous system copy exports. If you cancelled a system copy export and want to perform the export again, make sure that you remove all files from the previously cancelled export before you start the export from scratch.
Note
As a result of the export, a dump of the database schema belonging to the SAP system is stored in the export directory. During the entire life-cycle of this export dump, you must ensure adequate protection from unauthorized read access and modification of the data exported. Therefore, you now have the option to specify a restricted access level for the export directory when you run the installer [page 78] to perform the export. You are enabled to specify that only the
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Database Independent System Copy PUBLIC 57 Process Flow on the Source System (Export)
When performing the export, the installer creates a migration export media which contains the data of the exported system, and which you use to install the target system.
The following figure shows the export options and the resulting output files.
Overview on Export Options
Follow the sequence of steps described below for a:
● Standard system ○ Standard system – Performing the Export on the Source System ○ Standard system – Setting Up the Target System ● Distributed system or high-availability system ○ Distributed system or high-availability system – Performing the Export on the Source System ○ Distributed system or high-availability system – Setting Up the Target System
Standard System – Performing the Export on the Source System
To perform the export for a standard system, proceed as follows on the standard system host:
1. Heterogeneous system copy only: Generate the migration key at https://support.sap.com/migrationkey , entering the installation number of your source system when prompted.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 58 PUBLIC Database Independent System Copy 2. Perform the export on the standard system host: 1. Make sure that the QCM tables are deleted from your system as described in General Technical Preparations [page 44]. 2. Generate DDL statements [page 64]. 3. Prepare the system for table splitting [page 67] (optional). 4. You run the installer [page 78] to prepare the source system for the export. On the Welcome screen, choose the Export Preparation option.
Note
You must run this option if you want to perform export processes in parallel with import processes during the system copy. Otherwise, this step is optional.
5. If required, you prepare parallel export and import [page 73]. 6. Start the installer [page 78] from an application server instance host to export the database instance.
Note
If you want to run a system copy with parallel export/import using the Migration Monitor with the R3load socket option, and the target database is declustered, start the installer with command line option SUPPORT_DECLUSTERING=false.
On the Welcome screen, choose option Database Instance Export.
Note
○ If parallel export and import has been prepared, ensure the following: ○ You choose Parallel Export and Import for the database instance ABAP export on the SAP System Database Export screen. ○ If you decided to transfer the export directory instead of sharing it to the target host, make sure that you transfer it while you are processing the Database Instance Export option, after you have stopped the source system and before you proceed with the export procedure. ○ If table splitting for ABAP tables has been prepared before the data export via the installer, the installer export automatically does the following: ○ It forces package splitting. ○ It forces the use of an input file for table splitting. ○ It uses the existing whr.txt file from the dump directory for the package splitter.
You only have to execute the following steps if you intend to run the export on additional hosts [page 43]: 1. If you want to use additional hosts for the export, you have to mark the Use Additional Export Hosts checkbox on the SAP System Database Export screen. Some additional screens now appear where you can specify the additional hosts on which you intend to run the export and the size of the packages each export run is to contribute to the complete export dump. 2. Follow the instructions on these screens and then finalize the export on the database instance host.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Database Independent System Copy PUBLIC 59 Note
The total number of jobs should only be the number of jobs which are processed on the current host.
As a result, the first part of the export dump is created in the export directory. 3. Mount the export directory on each of the additional hosts on which you want to perform the export. In addition, you have to mount the SGN (signal) directory if you run the export/import in parallel. For more information about the SGN directory, see the documentation of the netExchangeDir option in the Migration Monitor Configuration [page 128] documentation. 4. Run the installer [page 78] on each of the additional hosts on which you want to perform the export. On the Welcome screen, choose the system copy option Database Instance Export on Additional Hosts. Follow the instructions on the screens and finalize the export on the additional hosts.
Note
If R3load processes fail due to an error, solve the problem, and perform the restart as described in Restarting R3load Processes [page 94].
3. If you want to perform table comparison with Software Update Manager (SUM) [page 157], proceed as follows: 1. Stop all instances of the source system once the export has completed. 2. Run table comparison [page 158] for the source system. 3. You can restart the instances of the source system.
Standard System – Setting Up the Target System
You use the installer to set up the target system and import the database files that you have exported from the source system.
Note
This system copy guide describes only the source system export in full detail. As for the installation of the target system, this system copy guide describes only the system copy-specific steps in section Setting Up the Target System [page 95], but refers for all steps that are identical with a new system installation to the appropriate operating system and database-specific installation guide [page 21].
You perform the following steps on the standard system host:
Note
The SAP HANA database is part of the SAP HANA appliance. It is pre-installed by SAP partners before the installation of your SAP system. Therefore, the SAP HANA database instance always runs on a separate host, even if your SAP system is a standard system.
1. You prepare the standard system host for the installation of your target system as described in the installation guide.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 60 PUBLIC Database Independent System Copy 2. If you have already prepared the export [page 73] on the source system because you want to perform export processes in parallel to import processes, you perform the following steps: 1. If you use the FTP Exchange option during the export (transfer type FTP on the SAP System Data Transfer Parameters for Export screen and communication type Exchange Directory on the SAP System Communication Parameters for Export screen), make sure that you have transferred all files that have been generated in step Preparing Parallel Export and Import [page 73] on the source system. 2. You transfer the export files to the standard system target host [page 96]. 3. You install the target system [page 97]. If you did not prepare the export on the source system, you install the target system. For more information, see Installing the Target System [page 97] 3. If required, on the host or hosts of the application server instance, you install further additional application server instances as described in the installation guide.
Distributed System or High-Availability System – Performing the Export on the Source System
To perform the export for a distributed system or a high-availability system, proceed as follows:
1. Heterogeneous system copy only: Generate the migration key at https://support.sap.com/migrationkey , entering the installation number of your source system when prompted. 2. You perform the database instance export. We recommend that you perform this step on the database instance host. If your source database is SAP HANA, you perform this step on any application server instance host. 1. Make sure that the QCM tables are deleted from your system as described in General Technical Preparations [page 44]. 2. Generate DDL statements [page 64]. 3. You run the installer [page 78] to prepare the source system for the export. On the Welcome screen, choose the Export Preparation option.
Note
You must run this option if you want to perform export processes in parallel with import processes during the system copy. Otherwise, this step is optional.
4. Prepare the system for table splitting [page 67] (optional). 5. If required, you prepare parallel export and import [page 73]. 6. Run the installer [page 78] to export the database instance.
Note
If you want to run a system copy with parallel export/import using the Migration Monitor with the R3load socket option, and the target database is declustered, start the installer with command line option SUPPORT_DECLUSTERING=false.
On the Welcome screen, choose the system copy option Database Instance Export.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Database Independent System Copy PUBLIC 61 Note
○ If parallel export and import has been prepared, ensure the following: ○ You choose Parallel Export and Import for the database instance ABAP export on the SAP System Database Export screen. ○ If you decided to transfer the export directory instead of sharing it to the target host, make sure that you transfer it while you are processing the Database Instance Export option, after you have stopped the source system and before you proceed with the export procedure. ○ If table splitting for ABAP tables has been prepared before the data export via the installer, the installer export automatically does the following: ○ It forces package splitting. ○ It forces the use of an input file for table splitting. ○ It uses the existing whr.txt file from the dump directory as default for the package splitter input file.
You only have to perform the following steps if you intend to run the export on additional hosts [page 43]: 1. If you want to use additional hosts for the export, you have to mark the Use Additional Export Hosts check box on the SAP System Database Export screen. Some additional screens now appear where you can specify the additional hosts on which you intend to run the export and the size of the packages each export run is to contribute to the complete export dump. 2. Follow the instructions on these screens and then finalize the export on the database instance host.
Note
The total number of jobs should only be the number of jobs which are processed on the current host.
As a result, the first part of the export dump is created in the export directory. 3. Mount the export directory on each of the additional hosts on which you want to perform the export. In addition, you have to mount the SGN (signal) directory if you run the export/import in parallel. For more information about the SGN directory, see the documentation of the netExchangeDir option in the Migration Monitor Configuration [page 128] documentation. 4. Run the installer [page 78] on each of the additional hosts on which you want to perform the export. On the Welcome screen, choose the system copy option Database Instance Export on Additional Hosts. Follow the instructions on the screens and finalize the export on the additional hosts.
Note
If R3load processes fail due to an error, solve the problem, and perform the restart as described in Restarting R3load Processes [page 94].
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 62 PUBLIC Database Independent System Copy 3. If you want to perform table comparison with the Software Update Manager (SUM) [page 157], proceed as follows: 1. Stop all instances of the source system once the export has completed. 2. Run table comparison [page 158] for the source system. 3. You can restart the instances of the source system.
Distributed System or High-Availability System – Setting Up the Target System
You use the installer to set up the target system and import the database files that you have exported from the source system.
Note
This system copy guide describes only the source system export in full detail. As for the installation of the target system, this system copy guide describes only the system copy-specific steps in section Setting Up the Target System [page 95], but refers for all steps that are identical with a new system installation to the appropriate operating system and database-specific installation guide [page 21].
In the following, we refer to this guide as “installation guide”.
Perform the following steps on the relevant installation hosts of your target system:
1. You prepare the ASCS instance host, the database instance host, and the host of the primary application server instance for the installation of the corresponding instances of your target system as described in the installation guide. 2. You install the ASCS instance for the target system as described in the installation guide. 3. You perform the following steps from any application server instance host: ○ If you have already prepared the export [page 73] on the source system because you want to perform export processes in parallel to import processes, you perform the following steps: 1. If you use the FTP Exchange option during the export (transfer type FTP on the SAP System Data Transfer Parameters for Export screen and communication type Exchange Directory on the SAP System Communication Parameters for Export screen), make sure that you have transferred the files, which have been generated in step Preparing Parallel Export and Import [page 73] on the source system.
Recommendation
Use different network exchange directories for the ABAP and Java stack in the configuration phase of the parallel export/import. Otherwise, both Migration Monitor and Java Migration Monitor might fail at the beginning of the import, if the exchange directory of the respective tool contains signal files (*.SGN) from the respective tool of the other stack. For more information, see SAP Note 2742371 .
2. You transfer the export files to the database instance target host [page 96]. 3. You install the database instance of the target system. For more information, see Installing the Target System [page 97]. ○ If you did not prepare the export on the source system, you install the database instance of the target system.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Database Independent System Copy PUBLIC 63 ○ You transfer the export files to the database instance target host [page 96]. ○ You install the database instance of the target system. For more information, see Installing the Target System [page 97]. 4. On the host of the primary application server instance, you install the primary application server instance of the target system. 5. If required, on the host or hosts of the additional application server instance, you install further additional application server instances as described in the installation guide.
4.1.1 Generating DDL Statements
To migrate nonstandard database objects, you need to generate DDL statements using the ABAP report SMIGR_CREATE_DDL.
Prerequisites
● Only valid for SAP systems based on SAP NetWeaver 7.4 on SAP HANA (not for SAP BW 7.3 EHP1 and SAP BW 7.4): If you want to migrate your system to a distributed SAP HANA database, make sure that you also consider the prerequisites as listed in SAP Note 1781986 (Business Suite on SAP HANA Scale Out), such as running report SHDB_GROUP_TABLES_LOAD_BASED in order to classify tables in the context of the migration. You must execute the report before the migration, in particular before running report SMIGR_CREATE_DDL. ● In addition, make sure that you applied all SAP Notes referenced in SAP Note 1921023 in the source system. Especially for migrations to SAP BW on SAP HANA, also apply the SAP Notes listed in the attachment REQUIRED_CORRECTION_NOTES.TXT of SAP Note 1908075 . These SAP Notes contain corrections and enhancements to SMIGR_CREATE_DDL, such as: ○ Rowstore list: ○ For SAP systems based on SAP NetWeaver 7.3 EHP1, the file rowstorelist.txt is used to distinguish between row-store and column-store packages, which can get created via an additional option of the report SMIGR_CREATE_DDL. ○ For SAP systems based on SAP NetWeaver 7.4, corresponding information is stored in DDIC instead of rowstorelist.txt, so no action is required. ○ Table list with estimated record count: ○ SMIGR_CREATE_DDL creates a file HDB_ESTIMATES.TXT or ESTIMATED_ROW_COUNT.TXT that contains a list of all relevant tables and the estimated number of rows per table. This information is used during migration into scale-out systems after the initial table creation and before the actual load of data. At that point, the installer performs an initial landscape redistribution of the empty tables. The estimated record counts are used in this step to ensure an equal distribution of data across the index server slave nodes. ○ The blog SAP HANA Landscape Redistribution with SP6 at http://scn.sap.com/community/hana- in-memory/blog/2013/09/03/sap-hana-landscape-redistribution-with-sp6 provides additional information on table placement and landscape redistribution. ● For migrations into scale-out systems: ○ Follow the recommendations provided in SAP Note 1908075 (set database parameters, maintain entries in control table for table placement, grant authorizations).
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 64 PUBLIC Database Independent System Copy ○ Check SAP Note 1958216 (HANA landscape redistribution configuration) for revision-specific parameter settings. ● For partitioning, make sure that SAP Note 1783937 (SMIGR_CREATE_DDL Enhancement for Suite on HANA) is applied, so that partitioning restrictions are recognized when SQL files are created (that is, large tables get partitioned during the migration). Otherwise, the import of tables with more than 2 billion records (German: 2 Mrd.) will fail. ● If you want to migrate an SAP Business Suite system to a distributed SAP HANA database, see SAP Note 1899817 (Suite on distributed HANA database - table redistribution).
Context
● You must perform this procedure before starting the installer. ● Always run SMIGR_CREATE_DDL before performing a heterogeneous system copy with SAP HANA as target database. SMIGR_CREATE_DDL checks the size of any table and generates corresponding DDL statements with partitioning clause for very big tables. In an SAP HANA database, all tables with more than two billions of records must be partitioned. ● For additional database-specific information, see also SAP Note 888210 .
Procedure
1. Log on to the system as a system administrator in a productive client. 2. Call transaction SE38 and run the program SMIGR_CREATE_DDL.
The Report SMIGR_CREATE_DDL: Generate DDL Statements for Migration screen appears. 3. Specify the required parameters on the Report SMIGR_CREATE_DDL: Generate DDL Statements for Migration screen.
○ Select the Target Database. Depending on the database manufacturer, you might need to select the database version. The value help supports you in selecting the database version.
Note
This parameter Is not relevant for SAP HANA.
○ Additonal Parameters: ○ Unicode Migration: This checkbox should be enabled if the target system is a Unicode system. For SAP systems based on SAP NetWeaver 7.5 or higher, this checkbox is always enabled and is not changeable any longer. ○ Installation Directory: Specify a directory to which the generated files are to be written. ○ Optional Parameters: The parameters Table Category and Table Name are used to limit the amount of tables to be processed in SMIGR_CREATE_DDL. These parameters are for test purposes only.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Database Independent System Copy PUBLIC 65 ○ SAP HANA Options: ○ Table Classification: If you mark this checkbox, the table attributes GROUP NAME, GROUP TYPE, and SUBTYPE will be set for BW tables. You should always mark this checkbox if the target system is an SAP BW Scale Out system. ○ Estimated Table Size: If you mark this checkbox, the files HDB_ESTIMATES.TXT and/or ESTIMATED_ROW_COUNT.TXT will be generated. These files contain information about table sizes. They are necessary if the target system is an SAP BW Scale Out system. ○ SAP Business Suite on SAP HANA: Do not use this option. Instead, refer to SAP Note 2408419 and the attached documentation for SAP Business Suite migration to an SAP HANA Scale Out system. ○ Extended Storage in Target Sys : This checkbox is intended for SAP BW system where Dynamic Tiering - formerly known as “Extended Storage” - with Sybase IQ is enabled. Mark this checkbox if Dynamic Tiering with Sybase IQ is also configured in the target system. For more information about SAP HANA Scale Out, see the SAP HANA documentation at https:// help.sap.com/hana_platform 4. Execute the program.
The DDL statements are generated and are written to the specified directory.
Note
Ensure that the user
From there, the installer copies them to the
Caution
If no database-specific objects exist in the database, no SQL files will be generated. As long as the report terminates with status Successfully, this is not an error.
If database-specific objects exist without being assigned to a specific TABART in the ABAP dictionary (table DD09L), the object definition is written to SMIGR.SQL, otherwise to
4.1.2 Using a Dedicated Kernel for the Export
As a customer running a productive system, you are sometimes confronted with kernel patches that are required for an ABAP system copy. Since you do not want to change the kernel for your productive landscape, you would like to be able to use a dedicated kernel just for software lifecycle activities for the system, whereas the system itself is to remain unchanged. During the system copy export, while processing the Use Dedicated Kernel for System Copy screen, you can specify that you want to use a dedicated kernel. Having chosen this option, on the next screen you are prompted for SAP kernel archives that you want to use for the export itself - SAPEXE.SAR and SAPEXEDB.SAR. The installer then uses these archives instead of those installed in the source system for running the export.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database 66 PUBLIC Database Independent System Copy Related Information
Preparing the Media Required for Performing the Export [page 52] System Copy Procedure [page 57]
4.1.3 Preparing the Table Split
The R3ta or - if the SAP kernel version of the source system is 7.40 or higher - SAPuptool processes large tables. Instead of exporting/importing one table with one R3load process, the table is processed in, for example, 10 entities.
Prerequisites
● For prerequisites, see SAP Note 1783927 (Prerequisites for Table Splitting with target HANA database). ● We recommend that you perform a test run to identify the tables with the longest runtime, as not always the largest tables require the longest runtime. To get statistical data about runtimes, use Migtime during the export and import. For more information, see SAP Note 784118 ). ● Otherwise, create a list of the largest tables in the database before the export to identify candidates for table splitting (by using transaction DBACOCKPIT or DB02). ● For using the R3ta or - if the SAP kernel version of the source system is 7.40 or higher - the SAPuptool, consider the following: ○ The installer offers a corresponding option in the export dialog – see below for more information. ○ Under certain conditions, we recommend that you create additional temporary indexes on the column used in the WHERE condition. Depending on the database, this may not be feasible during productive operation because of time and table locking. ○ In contrast to previous statements, you can also use database-specific splitters, not only the generic R3ta or - if the SAP kernel version of the source system is 7.40 or higher - the generic SAPuptool. ○ As for all R3* tools, always use the latest version of the R3ta or - if the SAP kernel version of the source system is 7.40 or higher - the SAPuptool. Using an outdated version of the R3ta or the SAPuptool increases your risk of receiving incomplete WHR files, which can cause data corruption. ○ If parallel processing is not optimal or if the single packages are serially processed, the complete processing time for one table can increase when using WHERE conditions. ○ The export and import must be performed with Migration Monitor if the table splitting feature is used. ○ For R3ta some platforms allow the creation and usage of an R3ta_hints.txt file, with which you can instruct the R3ta to use specific columns of a table to create a WHERE condition. For more information, see section Using Hints. If you plan to use R3ta_hints.txt , check whether it contains a valid column for the table that you want to split. You can reduce the runtime of R3ta significantly by choosing a table column with a good selectivity. If no field is provided, a selectivity analysis has to be performed over several columns, which will increase the overall runtime of the splitting.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows : SAP HANA Database Database Independent System Copy PUBLIC 67 Context
Each entity can be processed by different R3load processes. The advantages of splitting the tables are:
● Large tables are processed in smaller packages. If the export or import of a table aborts with an error, only the processing of the package where the error occurred has to be repeated and not for the complete table. ● The export and import of one table can be performed in parallel by starting several R3load processes to work on some packages in parallel. ● The export and import has to be performed with the Migration Monitor when the table splitting feature is used. For more information about the Migration Monitor, see R3load Procedures Using the Migration Monitor [page 127].
Restrictions
● Only tables that are described in the SAP dictionary can be split. ● The following tables cannot be split: ○ DDNTF ○ DDNTF_CONV_UC ○ DDNTT ○ DDNTT_CONV_UC ○ DDLOG (is never copied, but created empty in the target system) ○ DDXTT ○ DDXTF ○ DDXTT_CONV_UC ○ DDXTF_CONV_UC ● Parallel data export of a table is supported by all database platforms but not parallel data import. When the target database platform does not support the parallel data import, the Migration Monitor has to be configured in the way that the data import processes the packages are sequentially. For more information, see Processing Split Tables.
Procedure
1. Create a file that contains lines of the form