Useful information for OS/DB Migration -1

OS/DB migration:

Copy of SAP system to another hardware is called a system copy.
If the target system will run on a different operating system or a different database system

than the source system, then It is called a heterogeneous system copy or OS/DB migration.

Homogeneous system copy:

A system copy that doesn't involve the change of either OS or DB is called a homogeneous system copy. 

To change from 32 bit to 64 bit on the same OS it is also  called a homogeneous system copy.

Database Migration Option (DMO)?

DMO is a part of the Software Update Manager 1.0 (SUM), the standard tool for system maintenance. 

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.

 

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

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

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

- SAP Service Marketplace, you can generate the key online.

R3LAOD *.STR files: contains below information: ABAP data type of fields, Primary key fields, TABART of tables.

R3LDCTL creates the DDL<DBS>.TPL, <PACKAGE>.STR  .

*.TOC files:  contains  Header information, R3LOAD Version ID,Code page.checksum information,

Name of the dump files used,Table name and position of data with in the dump file.First data block/last data block.Where condition in case of table splitting.