The main purpose of a homogeneous system copy is to build a test, demo or training system or to move a system to a new hardware. The difference to a heterogeneous system copy is that both the database and operating system remain the same. Because of this, there is the possibility on some platforms to perform the copy using database-dependent methods (such as backup/restore) Oracle Database Migration to Hana Database Motivation due HANA Features 1.it is performed by using SWPM. Download the Latest SWPM1.0 SP18 along with Supported Kernel.(Ensure that the SAP Netweaver Platform is atleast 7.3 SP7) 2.The Migration takes place by standard Export and Import Option of System Copy in SWPM The main purpose of a heterogeneous system copy is to create a copy of an already existing SAP system on the platform where either operating system, or database, or both differ from the operating system/database of the source system. The whole migration process consits of five main steps (described in detail in the system copy documentation): 1.Preparation steps on the source system 2.Export of the source system data into database-independent format 3.Transfer of the exported files to the target host 4.New system installation together with data import(data dependent) 5.Post-processing steps within the target system 3.The Following Files are used during Migration: DDL.TPL(template) is used for creation of table/index definition in database-specific syntax and contains negative list of tables, views and indexes, assignment of TABARTs to storeage unit and next extent size of table/index. TABART stands for a data class. SAP.TPL, export directory, block and file sizes. SAP. ( = 001, 002, ...), so called dump files, contain the data of all tables of a tabart in a non-platform-specific file (independent)format. These are binary files and they should never been changed/edited! SAP.EXT contain initial sizes for tables and indexes. Not applicable to some databases (such as for Microsoft SQL Server). SAP.TOC contain position of table data within the corresponded dump file, name of the dump file, time stamp of unload, and table rows number. TOC files must never be changed without approval of SAP support. SAP.log contain log file information in case of errors and for restarting. SAP.TSK are files used by R3load SAP.TSK.bck are files created and used by R3load during runtime. SAP.log the Package Import|Export Log import_ monitor_cmd.properties specifies the imported packages export_ monitor_cmd.properties specifies the exported packages 0 = To be executed. ? = In process. + = Execution was succesfull. – = Execution aborted ************************************************************************ ABAP kernel tools used during a migration, Tools used at the export on the source system must have the same version as on the target system. ********************************************************************* Tools: R3szchk,r3check,r3ldtcl,R3load,r3ta these are part of SAP Kernel. R3load Unloads the data during Export and Loads the data during Import. R3ta will be used split the larger tables using TABLENAME%100 Migration Monitor uses the EXT, WHR, STR, TPL files to control the unload and load, to accelerate the load by automatic parallelization, to trigger the creation of the R3loadtask files, and creates the command files (TSKand CMDfiles). Migration Monitor does the following: ?Creates R3load command files ?Triggers creation ofR3load task files if required(created by R3load) ?Starts R3load processes to unload the data ?Transfers packages from source to target host if required ?Starts R3load processes to load data as soon as a package is