Quantcast
Channel: SCN : All Content - All Communities
Viewing all articles
Browse latest Browse all 3353

Endless phase (SUM) - MAIN_SHDIMP/SUBMOD_SHD2_RUN/RUN_RSGEN

$
0
0

Hello,

 

I´m doing an update support packges activity in our Solution Manager 7.1 SR1 system, the SPS12. I´m doing this activity with the latest version of SUM tool, but now I´m stucked in the Preprocessing phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/RUN_RSGEN

 

This phase is taking so long time... is an endless phase, this is running in this same phase at two days!

 

I see in SM37, in the shadow instance, two endless jobs:

- RSPARAGENER8M

- RSGEN_GENER8_SHADOW

 

I also checked two log files in the SUM directory:

- RSGEN.SM1

- RSGEN.LOG

 

I see in the file RSGEN.LOG the following entries:

A4 ETSGEN 312 Job "RSPARAGENER8M"("17235500") for machine type "562" still has "73626" object(s) to process

 

SNAG-1195.jpg

 

In the SAP note 1878193 (Central Note - Software Update Manager 1.0 SP10 [lmt_006]) I read a notification regarding this type of message:

 

"---------------------< D024828 MAR/04/2014 >--------------------------

Updating to SAP Business Suite 7 Innovation 2013 SP3: Endless loop in MAIN_SHDIMP/SUBMOD_SHD2_RUN/RUN_RSGEN

In certain cases, the phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/RUN_RSGEN might loop endlessly.

You could identify such a case by inspecting the (temporary) log file <SUM-Directory>/abap/tmp/RSGEN.<SID>. At the end

of this log file there could be a lot of similar entries such as

 

A4 ETSGEN 312 Job "RSPARAGENER8M"("xxxxxxxx") for machine type "xxx" still has "nn" object(s) to process” where nn stays constant over time

 

If you encounter such a case during your update procedure, report an incident on the component BC-ABA-LA."

 

 

Can you tell me please if anyone faced the same problem and how can you solved it?

 

Can you help me please?

 

 

Kind regards,

samid raif


Viewing all articles
Browse latest Browse all 3353

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>