Heterogeneous migration using R3SETUP

[Former Member]

Hi there

We are doing SAP 4.6C migration from HP-UX IA64 and Oracle 9.2. DB size is 4.2TB.

We are using R3SETUP and splitting .STR and .EXT file.

The export is fine for a start but after 2 days, we realized that package SAPAPPL1 has a huge number of size.

Our forecast is showing that another 8 days are required to complete the export.

We have decided to use a package splitter. Download a java based package splitter and split the SAPAPPL1.

Now we have 148 of small .STR and .EXT files, which include one table per packages, and new .STR and .EXT of SAPAPPL1, which does not include the 148 tables.

We wait until R3SETUP hits an error for R3LOAD SAPAPPL1 due to PSAPTEMP is not enough.

Ensure there is no more R3load running.

Replace the existing .STR and .EXT files with the new ones from package splitter tools and start the export again.

Question now is whether the integrity of data in SAPAPPL1 remains consistent?

Please advise.

[former_member188883]

Hi ,

Package Splitter and Table Splitter are standard tools from SAP and it ensures data integrity is maintained. You need to ensure that all the packages run with return code 0.

Just a small suggestion. As your database size is 4.2 TB you may also look for table splitting in addition to package splitting. This will help in reducing the export as well as import time.

Regards,

Deepak Kori

[Former Member]

Thanks Deepak.

Unfortunately, my understanding table splitting only available for version 6.40 and above.

Not 4.6C.

When you said packages should run with return code 0, does this means to check the package log?

Any chance to check using migration check tools?

What is expected result should I get?

[former_member188883]

Hi ,

As per SAP note 784118 - System Copy Tools for ABAP Systems You can use migmon for 4.6C systems as well. Below is an extract from the same.

New Java based tools have been developed to improve the system copy process for ABAP systems. The tools can be used together with the old system copy procedures based on R3SETUP as well as for copying older SAPinst based products.

If you want to use newer tools from the SAP Service Marketplace instead of the original ones from the installation kit, then extract the corresponding archive (e.g. MIGMON.SAR) into the 'installation' directory after SAPinst has copied the installation files (xml file, libraries, ...) into it. All listed tools are downwards compatible and we recommend always to use the latest tool version available - unless not stated otherwise.These tools are available for copying ABAP systems of releases 3.1I SR1 or higher.

When you said packages should run with return code 0, does this means to check the package log?

Yes. You need to check the package log.

Any chance to check using migration check tools? What is expected result should I get?

Migration Checker (MIGCHECK)

  The Migration Checker pack includes 3 different tools:

The Package, the Object, and the Table Checkers.

The checkers can be called on the target database host to verify that the import has been performed successfully. 

The Package Checker is used to verify that the import of all packages was at least started.

The Object Checker is used to verify that all objects (tables, views, indexes, primary keys) are successfully created/loaded in database.

The Table Checker is used to verify if the number of rows been exported is the same as the number of rows in the database (not usable in Socket mode).

Hope this helps and answers your query.

Regards,

Deepak Kori

[former_member188883]

Hi Ace,

Incase your query is answered you may close this thread.

Regards,

Deepak Kori

[former_member188883]

Hi Ace,

Hope this query is answered. Could you close this thread.

Regards,

Deepak Kori