Efforts in Technical Migration

This is a follow up article of SAP System Migration , please make sure that you have read the previous blogs or have the understanding of those topics :-

1. Overview

2. Migration Tools

3. Timeline of Migration

In the Source System we check first the components that needs to be certain that they can be migrated especially JAVA Based Components . To Point out these information need to be checked on Source System:

1. SAP Products Installed

2. Version of Installed Products (Enhancement Package, Support Package , Kernel Version)

3. Fully understand the System Landscape

4. Number of System to migrated and are in PROD state.

5. System Migration order and time schedule of the migration needed by customer.

6. Maximum System Downtimes for migration purposes.

7. System Access in case of hosting environments.

8. Operating System and Database System , as we have dependencies based on it.

Technical points needs to be checked at :-

1. Current Hardware (RAM, CPUs, disk sub system)

2. Size of Source Database (compressed / uncompressed)

3. Free local disk space for unloading the database.

4. Largest tables and indexes.

5. Code page used. Character Encoding

6. Tables in ABAP Dictionary but not in DB or the reverse.

7. External Files and interfaces (spool, archives, logs, transport files and interface)

8. Procedure for transporting the dump files from the source to target system.

Number of Export process required is decided by :-

1. Number of CPUs

2. Information about the I/O subsystem

Time that will be needed for migration is decided by :-

1. Database Size

2. Size of largest table (influence export significantly)

As we have understood in previous blogs that we need to perform test migration first that will require 10%-15% of the uncompressed source database size as export file system free space.

Apart from Source System we would also require information about the target system , Obviously!

Things to check :-

1. Target Hardware (RAM, CPU, Disk Sub System)

2. Target OS and DB version that is planned.

3. Date of Hardware Availability or Delivery.

How the Migration actually goes on :-

[ TEST ]

1. Install migration tools and prepare the source system. (Example : for ABAP R3LOAD, R3LDCTL, R3SZCHK for JAVA JLOAD, JSIZECHECK)

2. Export data from source system.

3. Install the SAP product and the database software on target system (on target perform the installation).

4. Transport / Share the data export to the target system (data transfer from source to target).

5. Create an empty target database.

6. Load the data export to the database (in step 2 we unloaded the data or made data ready for transport from source to target , in step 4 we shared from source to target, in this step the data from source db is loaded to our target db)

7. Complete the installation and perform the follow up tasks.

8. Configure the test environment.

9. Extensively test the migrated system.

[FINAL]

1. Create a cut-over plan (While planning cutover plan include active checklist and time schedule , also plenty of reserve time )

2. Perform the migration

3. Perform the follow-up task

4. Check the system (It is not required to repeat all the application test and checks that were already done in TEST phase . It should be reduced to absolute necessary)

5. Run a backup

6. Start production work

Comments

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 : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true 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

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 : sap-perf.ca Let's discuss the WORKLOAD MONITOR By D

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

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.

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

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

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 Router and SAP Web Dispatcher

SAP Router and SAP Web Dispatcher When I started reading about architecture , I was always confused what is the need and requirement of SAP Router , SAP Web dispatcher and thing that added to confusion was ICM , now we know the ICM handles the Web request but then why we need these two, These are Application level gateway provided by SAP and ICM happens to be on the SAP Application level , SAP Netweaver Application Server level. SAP ROUTER SAP WEB DISPATCHER Filtering Function Load balancing and filtering HTTP(S) requests Used for Routing and Filtering traffic at the SAP Net work Interface Layer Filter requests based on the IP address or protocol Require that a password is sent with request Require that secure authentication and data encryption occurs at network layer using SCN , Secure Network Communication To enforce access control, specify the IP addresses and address patterns that can access your SAP systems in the saprouttab configuration file The rules to use for filtering the

Let's Talk SAP

Search This Blog