cancel
Showing results for 
Search instead for 
Did you mean: 

File to check for successful Migration.

Former Member
0 Kudos

Dear   Experts,

Which file needs to check whether Migration is successful or not.

Regards

S.Basis

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello,

There are answers for you in this note. There is a path to MIGCHECK document in that note:

2009651 - Table Checker Tool as Part of a System Copy with R3load

Download the table checker tool, contained in the archive MIGCHECK_<number>.SAR available on SAP Service Marketplace at:

http://service.sap.com/swdc --> Support Packages and Patches --> Archive for Support Packages and Patches --> Archive - Browse our Download Catalog --> Additional Components --> SYSTEM COPY TOOLS GEN --> SYSTEM COPY TOOLS GEN <release> --> #OS independent --> MIGCHECK_<number>.SAR.

And MIGCHECK is used for checking some checksums and consistency:

784118 - System Copy Tools for ABAP Systems

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

Best regards,

Serhat

Answers (3)

Answers (3)

former_member186845
Active Participant
0 Kudos

Hello,

In order to complement the reply given by Serhat Yücean, I would suggest you checking section Number of rows in tables are different in a system copy in the SAP document below:

This document has some troubleshooting notes and KBAs that can be helpful. The section I mentioned above has a KBA which describes how to compare the information from source and target systems.

Regards,

Henrique Girardi

SAP Active Global Support

-------------------------------------

#2081285 - How to enter good search terms to an SAP search?

https://service.sap.com/sap/support/notes/2081285

SWPM Troubleshooting documents:

http://scn.sap.com/docs/DOC-62646

former_member182657
Active Contributor
0 Kudos

In addition you could also check under exported / imported packages file logs.

Thanks,

Former Member
0 Kudos

Hi S Basis,

You can check for the .TSK, .log files for any error for the tables imported.

and if you had used the migmon option you do a migcheck for the tables export/import in the system.

Do refer to the hetrogenous system copy guide for more details.

Regards,

Ram

Former Member
0 Kudos

Hi  Ram,

To check .tsk & .log files isn't right option if we have lot of tables & packages.  Migcheck option is suitable for this.  What do you say...

Regards

s. Basis

Former Member
0 Kudos

Hi S Basis,

Yes true there will be lot of files if your using a tablesplitting methodology, so mainly the Large table tsk & logs files are checked and you can use tools like the one mentioned by Serhat and me .

Also SAP Has provided migcheck & migtime to analyze the table export/import and the time taken by migmon to perform it.

so based on this two tools you can perform your migration more effective for the next runs as you can get the larger tables and there phase which ran longer and then you can further apply table split or package splitting to get more time effective procedures.

Regards,

Ram

former_member182657
Active Contributor
0 Kudos

Hi,

Could you be more specific with your issue ?

Regards,

Former Member
0 Kudos

Hi  Gaurav,

Suppose, In the end we get pop-up...Migration is done successfully. Then, from OS level Which file or log suggest successful export of all packages.

Regards

S.Basis

former_member182657
Active Contributor
0 Kudos

Hi,

You could check with sapinst log files at OS level.For more i suggest you to refer SCN doc at

Also suggest you to refer SAP migration guides in detail.

Thanks,