Skip to main content

Mastering SAP System Copy: Unlocking the Secrets of Seamless Migrations

Part1 : Say Hello to tools and terminologies 

System Copy Solutions:

- Backup/Restore

- Third-party tools for data unload/load (Not Supported by SAP unless explicitly mentioned in the SAP Notes)

- SAP system copy tools

Homogeneous System Copy:

- Moving or copying an SAP system to a new environment where the source and target systems use the same operating system (OS) and database (DB) system.

- Hardware architecture remains the same or is a certified successor.

- Reasons for a homogeneous system copy include system moves, multiple components stored in one database configurations, setting up additional SAP systems, and changing the SAPSID for company-related reasons or the use of SAP reserved SIDs.

Heterogeneous System Copy:

- Moving or copying an SAP system to a new environment where the source and target systems use different OS or DB systems.

- Involves a change in hardware architecture in many cases.

- Requires a certified person for OS/DB migrations, except when using the database migration option for SUM (DMO), which automates necessary tasks.

- Depending on the method used, it may be necessary to upgrade the DB or OS of the source system first.

refer : Image from TADM70

SAP OS/DB Migration Check Service:

- Consists of OS/DB Migration Check Analysis and Verification sessions.

- Provides standardized procedures for all migrations, avoids planning errors, and offers parameter recommendations for the target system.

- Fee-based service, specific to customer location, and delivered as a remote service.

- Benefits include efficient project implementation and cooperation with experienced migration partners.

ABAP System Copy/Migration Tools:

- SAPINST: Controls the system copy process.

- R3LDCTL: Unloads ABAP Dictionary structures from the DB. When ABAP Dictionary structures are unloaded from the DB, it means that the database objects defined in the ABAP Dictionary, such as tables or views, and their associated metadata are unloaded or extracted from the database. The unloaded ABAP Dictionary structures are typically saved in files with the extension ".STR" (structure files). These structure files contain the necessary information to recreate the ABAP Dictionary structures in the target system during the system copy or migration process.

- R3SZCHK: Computes the size of ABAP tables/indexes.

- R3LOAD: Unloads or loads ABAP table data from or into the DB. It allows for the export of data from ABAP database tables into files, and subsequently, the import of that data into the target system. R3load plays a crucial role in ensuring the successful transfer of ABAP data during system copies or migrations, maintaining the integrity and consistency of the data throughout the process

- SMIGR_CREATE_DDL (ABAP Report): Generates DB-specific DDL statements for nonstandard DB objects of the ABAP Dictionary, mainly SAP Business Warehouse (BW) objects. More non standard object are Custom Tables, Custom Views, Custom Data Types, Custom Function Modules etc.

- RS_BW_POST_MIGRATION (ABAP Report): Posts system copy activities for nonstandard DB objects in the ABAP Dictionary.

Don’t get confused here, Unloading the table data refers to exporting or extracting the actual records and data stored within a database table. This process retrieves the rows of data that exist in the table, including the values for each column which is done by R3LOAD.Unloading the table structure refers to retrieving or exporting the metadata and definition of a database table without including the actual data stored within the table which is done by R3LDCTL.

Support Tools for ABAP System Copies:

- PACKAGE SPLITTER: Splits R3LOAD *.STR and *.EXT files to reduce export and import times.

- TABLE SPLITTER: Creates WHERE conditions to allow multiple R3LOADs on a single table during export and import.

- MIGMON (Migration Monitor): Allows advanced control of R3LOAD processes, supports parallel unload/load processing, and automates dump shipping between source and target systems.

- DISTMON (Distribution Monitor): Runs multiple Migration Monitors distributed over different application servers (no longer supported by SAP refer 855772). You can not download it , and if you have that software you are running at your OWN RISK!

Distribution Monitor is not released for SAP HANA.

- MIGCHECK - PACKAGE CHECKER: Verifies the start of package import.

- MIGCHECK - OBJECT CHECKER: Verifies successful creation or loading of objects in the database.

- MIGCHECK - TABLE CHECKER: Compares exported rows with imported rows for each target DB table.

- MIGTIME (Time Analyzer): Analyzes export and import run-times of R3LOAD processes.

System Copy and Migration Tools for Java:

- JLOAD: Unloads or loads JAVA dictionary structures and table data from or into the DB.

- JSIZECHECK: Computes the size of the JAVA target DB.

OS/DB Migration Verification Session:

The OS/DB Migration Verification session focuses on the following aspects:

- Analysis Session: This session involves analyzing the current system landscape and reviewing the migration project schedule. It helps identify potential issues or challenges and ensures a well-planned migration process.

- Verification Session: This session verifies the successful execution of the system copy tools and checks the consistency and integrity of the migrated system. It ensures that all objects are correctly created or loaded in the database and that the expected number of rows are imported for each target DB table.


- The information provided here is based on TADM70 Guide and SAP Notes. It is essential to refer to the official SAP documentation and consult with experts when planning and executing system copies or migrations.

- The specific procedures, tools, and requirements may vary depending on the SAP system landscape, versions, and individual project needs.

- Always follow best practices, guidelines, and recommendations provided by SAP for a successful and smooth system copy or migration process.


Post a Comment

You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : Let's discuss the WORKLOAD MONITOR By D

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue  Go to System > Status and Check the Basis SP level as well as info

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set

SAP system migration blog series - part 1: migration overview

Summary : This blog is part 1 of the blog series on SAP system migration. In this blog, we will provide overview about SAP migration, types of migration, their differences and usage scenario. SAP migration overview :   As the Greek philosopher, Heraclitus, said: “change is the only constant.” Same goes within SAP world too, often customer have to change the SAP systems along with its underlying components to meet the changing requirements, be it change from old hardware to new one, changing operating system, database. This change in SAP system components (DB, OS or Hardware) is termed as migration. Before we go into details of migration, let’s understand architecture of a typical SAP system.   An SAP system consist of SAP application instances, running on database (DB), hosted on operating system (OS), provisioned on hardware. Change in any one or more of these underlying components (DB, OS or hardware) warrant us to perform migration. Types of migration:   Broadly, there are two types

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c