S41610 to S419109 Upgrade slowness in shadow instance creation during language import

[dnyandevk007]

hello Team,

We have doing S41610 to S41909 upgrade in development. During the Preprocessing phase(MAIN_SHDCRE/SHADOW_IMPORT_UPG1: Imports upgrade and language data into the shadow tables (no new tables)) we are facing slowness . We are running upgrade on AWS with 40 CPU and 160 GB memory on SLES 12 SP4 and HANA 2.0 SPS04 rev 44. We have SUM Kernel 777 patch 6 and also added latest tp and R3trans patches. Currently following packags are getting import for languages. we have parallel 35 R3trans processes running.

SAPKLLTCA1909S4HOPF6.SD1 SAPKLLVCA1909S4HOPF6.SD1 SAPKLETCA1909S4HOPF6.SD1 SAPKLHRCA1909S4HOPF6.SD1 SAPKLNLCA1909S4HOPF6.SD1 SAPKLSLCA1909S4HOPF6.SD1 SAPKLSHCA1909S4HOPF6.SD1 SAPKLTRCA1909S4HOPF6.SD1 SAPKLZFCA1909S4HOPF6.SD1 SAPKLELCA1909S4HOPF6.SD1 SAPKLITCA1909S4HOPF6.SD1 SAPKLCACA1909S4HOPF6.SD1 SAPKLHICA1909S4HOPF6.SD1 SAPKLPLCA1909S4HOPF6.SD1 SAPKLKOCA1909S4HOPF6.SD1 SAPKLESCA1909S4HOPF6.SD1 SAPKLHUCA1909S4HOPF6.SD1 SAPKLPTCA1909S4HOPF6.SD1 SAPKLJACA1909S4HOPF6.SD1 SAPKLROCA1909S4HOPF6.SD1 SAPKLSVCA1909S4HOPF6.SD1 SAPKLBGCA1909S4HOPF6.SD1 SAPKLHECA1909S4HOPF6.SD1 SAPKLARCA1909S4HOPF6.SD1 SAPKLRUCA1909S4HOPF6.SD1 SAPKLVICA1909S4HOPF6.SD1 SAPKLCSCA1909S4HOPF6.SD1 SAPKLZHCA1909S4HOPF6.SD1 SAPKLDACA1909S4HOPF6.SD1 SAPKLFICA1909S4HOPF6.SD1 SAPKLKKCA1909S4HOPF6.SD1 SAPKLNOCA1909S4HOPF6.SD1 SAPKLUKCA1909S4HOPF6.SD1 SAPKLTHCA1909S4HOPF6.SD1 SAPKLSKCA1909S4HOPF6.SD1

I also observed Threads waiting for locks(see attached files) but there is no blocking transactions. I also observed uncommitted write for more than 400 mins alerts on SD1 for R3trans processes. The progress is slow. Any idea why R3trans is not committing frequently?

Any idea what is the issue.

[kashyap_shah3]

Hi Dnyandev,

SAP Note 2659395 - bad performance during language import in systems with many clients may not be the answer but little helpful.

I'd faced similar slowness with language import while upgrading from S/4HANA 1610 to 1709. I couldn't find a way around but probably because time it was taking was legit due to the fact that best practice was activated on source S/4HANA 1610 system with all languages. Again, not very helpful I guess unless you're in same situation.

Best Regards,
Kashyap Shah