Some users may experience issues accessing the case portal. For more information, please click here.

This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
sree335
Level 5
‎Mar 23, 2020 02:10 AM

Issue with DB Migration script while upgrading from 2017R2 to 2019 R!

Hi,

 

Did anyone face any issue while upgrading to 2019R1 version with DB migration script?

I am facing issue during 13.0 to 13.1 and it is exactly at Running 'cm-migr1310-MigrateSAPRoleConsumptionBulkCopy.sql'.

I can see SAPRoleConsumption_MT being renamed as _OLD and the new SAPRoleConsumption_MT being created with one of the column's data type modification and the size is have of the old table.

Size is about 

Select count(*) from SAPRoleConsumption_MT_OLD  -  912123308 records

Select count(*) from SAPRoleConsumption_MT             -  470000000 records

If anyone know any solution to overcome this issue please let me know, initially I thought this huge size is something unique but later when I went through the documentation, this size is expected it seems.

Thanks in Advance,

Srikanth

0 Kudos

This thread has been automatically locked due to inactivity.

To continue the discussion, please start a new thread.
1 Reply
WheresThePizza
Level 5 Flexeran
Level 5 Flexeran
‎Mar 25, 2020 08:37 AM

It appears that you already have a case with support that you are working on this. It would appear that the difference in data is the result of an error during the migration scripts execution. Since you already have a support case for this, it would be best to continue to work through that. 

0 Kudos