SAP OS/DB Migration Check

Complete Support for a Migration of your Operating System and/or Database

If at any stage of the SAP software life cycle you should need to change your operating system and/or database, the SAP OS/DB Migration Check optimally prepares you 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. The service delivery then includes all the systems in that system landscape.

If you want full support for the migration (be it a production system or not) then you must secure the services of a technical consultant with a special certification for OS/DB migration.

Value Proposition

SAP OS/DB Migration Check minimizes technical risk involved in an operating system and/or database migration and avoids unforeseen costs that can occur during the migration.

The benefits of this service are as follows:

  • Efficient, technically robust operation of your new operating system and/or database is achieved with minimum cost
  • Your migration project is accelerated to get a faster return on your investment
  • Expensive system downtimes during the migration are minimized
  • System resource usage is optimized to make the most of your IT investment
  • Infrequently required migration expertise is outsourced

A well laid out, easy to follow plan based on experience with thousands of migrations successfully leads you through a migration. It prepares your SAP solution so it runs with optimal performance, availability and maintainability after the migration.

Description

The SAP OS/DB Migration Check is specially designed to support the customer in successfully migrating an operating system and/or a database. With this check it is possible to migrate all SAP systems for which a migration is technically feasible and for SAP systems that have been registered with an installation number specified in your SAP maintenance agreement. It consists of two remote sessions: the Analysis and Verification Session. It is important to note that problems existing before migration due to incorrect customizing are not taken into account in the realm of this check.

Analysis Session

The Analysis Session checks whether your current hardware is sufficient for the target system. It takes place five weeks before migrating the production system and is performed on the source system. The load distribution is analyzed and recommendations are made for the configuration of the new system. This session checks the following:

  • Migration project related issues
          *  Technical data of the source system environment
          *  Technical data of the target system environment
          *  The migration project schedule
  • Hardware sizing feasibility
  • Load distribution (if necessary, optimization recommendations are given)
  • Configuration of the new system
          *  SAP system parameters
          *  Database parameters
          *  User/load distribution
  • Performance before migration
  • Transaction profiles
  • Number and distribution of users

The result of this session is a report that indicates whether SAP recommends to continue the project or not to continue because of concerns, whether enough hardware resources are available and what parameter configurations need to be performed by you for a successful migration.

Verification Session

The Verification Session occurs six weeks after migration of the production system and is performed on the target system. It is a routine check of the new operating system and/or database to verify the assumptions from the Analysis Session. This session provides corrective measures for avoiding potential bottlenecks. The Verification Session looks at the following:

  • Comparison of response time before and after migration
  • Performance analysis on the new OS/DB combination
  • Verification of whether all the required SAP recommendations were implemented
           *  SAP system parameters
           *  Database parameters
  • User/load distribution
  • Optimization of load distribution and identification of potential bottlenecks

The result of this session is a report similar to that received in the Analysis Session. The difference is that now you have a productive system which contains representative data from daily operations. This final report confirms system configuration and provides additional recommendations for improvements.

Service Procedure & Prerequisites

A convenient delivery date is scheduled with you and you are asked to complete the "Prepare" step. The "Prepare" step than can be accessed via the SAP Solution Manager "Service Engagement and Service Delivery" workcenter. The Analysis Session takes place five weeks before your migration. The Verification Session is normally performed six weeks after your migration. Each session is a separate unit and results in an extensive report with detailed recommendations. For the checks in subsequent service sessions to be effective, you must implement the recommendations that are provided in each report.

The SAP OS/DB Migration Check is available for migrations of operating systems and databases. To fully benefit from the service, SAP strongly recommends an implemented SAP Solution Manager.Although the SAP OS/DB Migration Check ensures a successful migration with minimized downtime and maximum performance after the migration, a migration of an operating system and/or database is a time and cost intensive project. During the project, you may experience reduced availability and performance of your SAP systems. For this reason, SAP encourages you to check and to make sure that all other possibilities for improving performance of your hardware, operating system, and database have been considered.

The OS/DB migration of each and every SAP system must be performed according to the following rules:

  • The migration will be carried out by a technical consultant who has a special certification for OS/DB migration from SAP. If you are in doubt as to whether your consultant has this certification, contact SAP Customer Care.
  • Customer and consultant will make a project plan that provides sufficient time to react to unforeseen problems.
  • If the system is a production system the OS/DB Migration Check service must be ordered from SAP and applied to this system.
  • It is necessary that during this check, the members of your staff with the required expertise in the areas of operating system, database, SAP Basis components and migration tools be available for consultation.
  • Before the migration, you must ensure that the platform combination (operating system and database system) you have chosen is supported by SAP. See the Product Availability Matrix for details.
  • For the migration of a productive system, it is necessary that a separate target system environment is available to perform the tests and the final migration towards the target system. It can be a separate physical hardware, a hardware partition or any SAP supported virtualization. The new target system environment must have equal or higher performance than the source system.
  • The migrated productive source system is expected to stay available for trouble shooting purposes after the final migration; usually until the OS/DB Migration Check Verification Session was completed.

If an OS/DB migration is carried out in violation of one or more of the above rules, SAP can deny support for any problems arising during the migration process or any later problems in the target system that have their origin in the OS/DB migration. If SAP Active Global Support is involved in solving issues it may be billed according to the current remote consulting price list.

SAP strongly recommends running the SAP EarlyWatch Alert. This service runs automatically in the background and delivers performance data to the SAP Solution Manager. The service continuously measures system performance to identify system bottlenecks early on.

SAP OS/DB Migration Check is available worldwide for all SAP products that use an ABAP stack. All other products may be migrated without involvement of the SAP OS/DB Migration Check.

General FAQs

The copy of an SAP system to another hardware is called a system copy. If the target system will run on a different operating system (OS) and/or a different database system (DB) than the source system, then this is called a heterogeneous system copy or OS/DB migration.

Further, if you just add or change application servers and don't touch the database server, then this is not an OS/DB migration.

A system copy that doesn't involve the change of either OS or DB is called a homogeneous system copy. It is not covered by this subject and the restrictions of a migration don't apply. To change from 32 bit to 64 bit is also a homogeneous system copy.

DMO is a part of the Software Update Manager 1.0 (SUM), the standard tool for system maintenance (like release upgrade or EHP and SP implementation). For scenarios where the system has to be upgraded prior to the database migration, DMO combines this upgrade with the migration and simplifies the process. It will be offered for a migration to SAP HANA, for SAP NetWeaver BW systems as well as for systems that are part of the SAP Business Suite.

DMO for SUM is made to facilitate the migration to SAP HANA and to support the whole project with a lot of internal checks and procedures. Thus the safeguarding brought by DMO for SUM is considered to sufficiently substitute the checks by the OS/DB Migration Check. As a consequence, the OS/DB Migration Check is not necessary for migrations to SAP HANA that are performed with DMO for SUM.

No, it is not. You don't need the SAP OS/DB Migration Check (it would not help anyway) and you don't need a consultant who is certified for OS/DB Migrations. Nevertheless, a good preparation and skilled project team members are recommended.

A change of the version of the operation system and/or the database system is not relevant in the context of a migration or a homogeneous system copy. If you don't change the product, but only the release level it is a homogeneous system copy. If you change OS and/or DB, it is a migration.

An OS/DB Migration that is performed according to SAP's regulations and guidelines does not alter, convert, or modify the business related content of the database. It is a purely technical procedure.

I want to migrate a SAP BW, SAP CRM, SAP EBP or SAP SCM system. Is this the same as a migration of a R/3 system?

Service Contract & Software Delivery

If you plan to use the target system as a production system, you need to use the SAP OS/DB Migration Check, otherwise SAP cannot give you support for the migration. You do not need the SAP OS/DB Migration Check to migrate development or test systems. Also, you do not need it to migrate a production system for pure evaluation purposes as long as you don't use the target system as a production system later.

If you want to migrate a system without involving a certified consultant, then you do this at your own risk. Any support for the migration and for problems that result from the migration will be billed as consulting. This applies also for non-production systems. You are obliged to let a certified consultant perform the migration.

Java-only components may be migrated without the restrictions that apply to the OS/DB migration of an ABAP system. Further, Java components are not covered by the SAP OS/DB Migration Check

As mentioned above, the OS/DB Migration Check is not the right choice here. Provided you have followed best practices in your system copy project, including test copies and test on the copied system (at least of the core business processes), in most cases it is sufficient to check the EarlyWatch Alert reports and look at reported issues. In case of performance issues an EarlyWatch Check might be a good choice for further treatment of the system.

An OS/DB migration is a lot more complex than a homogeneous system copy. A productive SAP system is almost never a stand-alone system. It has interfaces in every direction. Operating systems of different brands or technology use different conventions for file storage (i.e. line-feed convention; big-endian vs. little-endian). Databases of different brands use different technology (raw devices vs. file system) and interfaces. This is not a comprehensive list, but you get the idea. All these issues may cause interface failure that lead to a complete failure of the migration project.

To minimize the risk of failure of the migration project and the support cost, SAP has set up the regulations (certified consultant and the SAP OS/DB Migration Check for productive systems) for a migration it is willing to support. Because of the innumerable variety of projects it is impossible to draw a line between "complex projects" and "less complex projects". Therefore SAP decided to draw the line between "homogeneous system copy" and "heterogeneous system copy".

If you decide to deviate from the regulations, you do so at your own risk. Nevertheless, if something goes wrong with your production system due to a failed migration project, SAP will take action to help. But it may be billed on time-and-material basis.

If you plan to use the target system as a production system, you need to use the SAP OS/DB Migration Check. Also, to migrate any SAP system at all, you must secure the services of a technical consultant with special certification for OS/DB migration (through SAP training course TADM70). The consultant must perform the migration onsite. If SAP support is required, the consultant is the contact person. Almost every consulting company that offers SAP consulting has employees with the necessary certificates. Please ask your favourite consulting partner first. See also the Partner area on SAP's public web site. Also, the CIC has a list of suitable consultants and will help you to find one.

Service Session Delivery

Technically, a migration occurs when you transfer your source system unchanged to another platform, so you cannot upgrade during the migration. The SAP OS/DB Migration Check is designed to support the migration. Before you perform an upgrade, or other activities such as adding new applications or users, all the Migration Check service sessions should be completed. For the upgrade, you should then perform the SAP GoingLive Functional Upgrade Check. For other changes, such as adding new applications or users, perform a SAP GoingLive Check. As an exception of the rule "one project at a time" you can include a Unicode Migration into an OS/DB migration, because the same tools are used in both cases. On the other hand, a Unicode migration adds a noticeable amount of complexity to the project that may not be covered exhaustively by the SAP OS/DB Migration Check.

The DMO for SUM method, however, wraps all necessary changes for, say, a migration from any DB to SAP HANA, into one project. This may include not only the database migration but also a Unicode conversion and an SAP system upgrade. DMO for SUM helps to safeguard all steps and thus it is the recommended method for these kinds of projects.

When will the service sessions be delivered? Must the migration project be in a specific phase?

You can start the planning and preparation. However, the first service session may recommend changes in the planning of the project and the hardware sizing or database layout for your target system. Before you can perform the final migration, you need time to implement the recommendations.

Planning & Performing a Migration

This depends very much on your hardware capacities and on the parameterization and tuning of the migration tools. You cannot tell it until you tried it. This is the reason, why SAP recommends comprehensive test migrations before the final migration of the production system.

Your migration expert (the certified consultant) will assist you in the planning. Another source of information is the Planning Guide.

Please see the information on supported platforms in the [Product Availability Matrix] (https://support.sap.com/pam) in the SAP Service Marketplace.

In the SAP Service Marketplace, you can [generate the key online]( https://support.sap.com/migrationkey). Do not use the fax forms on the migration CDs (these are obsolete).