Custom file transfer for Homogeneous migration using parallel export/import

[Vikash_bth]

While performing classical Homogeneous migration for SAP Business Suite systems with Oracle database, the business downtime become key area. This was mainly due to critical business transactions being performed and longer business downtime will have impact on business operation.

The initial export using SAP SWPM (SAP Software Provisioning Manager) took more than 5 days and eventually had to cancelled. As this was not aligned with downtime.

SAP recommended following migration optimizations were performed in further exports:

• Package splitting
• Table splitting using PL/SQL table splitter for Oracle Database
• Update of Oracle database statistics

The above task helped in reducing the downtime but overall business downtime still much higher. Proceeding further with below optimization task were done:

• Use of “migmonCtrl” Add-On for the Export

Though the downtime was still on higher side. Now parallel export was only next available option which can reduce the business downtime.

After multiple iteration incorporating all above, the overall downtime does reduce.

However, the overall downtime (export + File transfer + import) were still exceeding the overall downtime.

 There were technical challenges associated with file transfer while choosing parallel export/import:

• Source and target SAP systems were situated in different data centers
• There was no common file system between source and target
• FTP protocol not supported on target
• Normal copy was taking longer

Taken Approach for minimizing the transfer runtime:

• A custom utility was developed for performing copy of completed packages automatically from source to target.
• FDT (Fast Data Transfer) was chosen tool for transferring files

 The python based custom utility is configured to perform following tasks:

• Check for files created in exchange directory for looking of completed packages
• Transfer all such completed packages files using FDT to target
• After successful completion of files transfer to SAP target systems, copy of signal files to target exchange directory

Further details :

1. Custom utility will copy the export_state.properties in local folder for files transfer processing
2. Script will read the export_state.properties file and search of completed packages (package with status “=++”)

The number of package copied is captured in variable b

1. If this is first run , there will be no comparison . But if this is not the first run an earlier copy of export_state.properties will be present. And both files will be compared for finding the delta packages which are completed since last run of python script.

For example : during one of delta run where PCL2-5 package was completely exported. Script has copied all files of PCL2-5

1. The packages list is generated after execution of step 3
2. Script will internally has also generated command to copy files using FDT. The generated copy command will get executed using custom utility and FDT will start copying files.

The custom script has been embedded in wrapper script which will call the copy script.

The wrapper script is having control input, where wait time can be defined dynamically.

Execution of custom utility :

Conclusions:

The overall downtime was now aligned with business and all migration activities completed within the stipulated timelines.

Reference:

System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on UNIX

https://help.sap.com/docs/SLTOOLSET/6ffd9a3438944dc39dfe288d758a2ed5/f1677053e4960150e10000000a44176...

SAP Note 1043380 - Efficient Table Splitting for Oracle Databases

https://me.sap.com/notes/1043380/E

SAP Note 1875778 - Performance Optimization for System Copy Procedures

https://me.sap.com/notes/1875778

Using the “migmonCtrl” Add-On for the Export

https://help.sap.com/docs/SLTOOLSET/8ae69d90e23d4b06b33f84515bb5eccf/dd8c33548601e10ce10000000a44538...