Not-Unicode ERP6 SR3 System Copy Export using SWPM - Error UMG_TEST_P

[Former Member]

Hello,

I have an ECC 6 SR3 Not Unicode running on Windows Server 2003 + MS SQL Server 2005. I'm performing a load based system copy in order to migrate it to a Windows Server 2008 R2 + SQL Server 2008 R2 to use features like page compression and such.

I don't want to convert the system to unicode.

Using the new SAPINST tool i'm getting an error in 1 of the 88 exports.

The error is the following:

SAPPOOL.LOG

(GSI) INFO: instno   = "0020719004"

(FLT) ERROR: no BLOCKNR field in table UMG_TEST_P

(DB) INFO: disconnected from DB

E:\usr\sap\DEV\DVEBMGS00\exe\R3load.exe: job finished with 1 error(s)

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

I'm also using the last R3load available:

E:\usr\sap\DEV\DVEBMGS00\exe\R3load.exe: version R7.20/V1.4

Compiled Jan 25 2013 23:39:13

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

And here is export monitor status:

Export Monitor jobs: running 0, waiting 0, completed 87, failed 1, total 88.

Unloading of 'SAPPOOL' export package: ERROR

I can't seem to find anything related to this problem. I can modify the TSK file and advance with the export but i would like a proper solution so that i won't have integrity problems later on.

Any ideas??

[AtulKumarJain · Accepted solution]

Hi Pedro,

Please check sap note  603575 and check the table "UMG_TEST_P" and also check  note 686357.

Best Regards,

Atul

[Former Member · Accepted solution]

Hello Atul,,

First of all, thanks for the reply.

I've checked both notes and they seem to be related with incorrect lenght in the UMG_TEST_P column fields.

Everything seems to be OK regarding that matter. I've compared the table with another Unicode System and Not-Unicode System.

[former_member188883 · Accepted solution]

Hi Pedro,

Please check the number of entries in table UMG_TEST_P in source system.

If the number of entries are 0 then you may ign this in .TSK file.

Use the report attached with Note 603575 to re-active the UMG_TEST_P table.

Regards,

Deepak Kori

[Former Member · Accepted solution]

Hi Pedro.

   I would suggest you to raise a SAP message in the meantime too..

Try to re-activate the table  UMG_TEST_P and check again.

Thanks and Regards,

Vimal

[Former Member · Accepted solution]

Even tho the column fields had the correct size, as soon as i hit activate one of them got reset to 0.

I followed the instructions to reactivate the table ( note: 603575 )

This time the export was flawless

Thanks

[former_member188883]

Hi Pedro,

Have you tried repeating the import process ?

Also look into SAP Note 421554 - R3load: Problems when converting cluster table

Regards,

Deepak Kori

[Former Member]

Hello Deepak,

First of all, thanks for the reply.

I've read the note indicated and the problems reported don't seem related with the one i'm facing.

Like i said before i'm not even trying to convert the system to unicode. Plus, i'm already using the latest R3load as stated in the original post.

To answer your first question i only performed the export once until now.

[former_member188883]

Hi Pedro,

Could you retry only the failed packaged ?

Regards,

Deepak Kori

[Former Member]

I did a couple of "retries", so the package could be processed again, when the error appeared.

No success.