cancel
Showing results for 
Search instead for 
Did you mean: 

Phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/TABIM_POST_SHD is in hanged status

Former Member
0 Kudos

Hi Team,

I m upgrading solman to SPS11 stack using SUM tool my upgrade is currently in preprocessing stage and In step ENH mass activation

In the background in SAP Shadow system it triggers a job called  RDDGEN0L which is active from very long time and CPU utilization is 0 also all workprocesses in SM50 is in waiting state

So job and upgrade step is in hanged state, As per Job log it "reached enque lock for mass activation"

Please suggest what could be possible reason and how to fix this issue

System information

SAP SOLUTION MANAGER 7.1

Database system ORACLE

Release              11.2.0.3.0

Operating System Windows

Machine Type 4x X86_64

SAP_BASIS : 702

Accepted Solutions (0)

Answers (2)

Answers (2)

Reagan
Advisor
Advisor
0 Kudos

Hello

Check whether the logs are getting updated in the <DIR_PUT>/abap/tmp directory ?

As you have an Oracle / Windows combination check whether you are hitting this bug.

1635605 - CLIENT HANGS ON INSERT INTO TABLE WITH SECUREFILE LOB

Set the Oracle parameter _use_zero_copy_io=false and restart the database.

Restart the upgrade and see if that helps.

Regards

RB

Former Member
0 Kudos

Hi RB, Thanks for your reply

No logs are not updating i checked inside D:\usr\sap\<SID>\SUM\SUM\abap\tmp

and and regarding that Oracle parameter I was facing issue for shadow import step, it was also running for long time so that time itself i set the parameter _use_zero_copy_io=false

and after setting the above parameter that step went fine.

but now its hanging in step TABIM

Reagan
Advisor
Advisor
0 Kudos

Hello Kajal

Connect to the SAP system and do a "Check Status" for the background job from Tx SM37 and see if the job status changes. If there is no change then I would consider restarting the system and see if that helps.

Regards

RB

former_member264034
Active Contributor
0 Kudos

Hi,

I would recommend to check SM21 from the same timestamp as the hanging job to
see if there are any errors, also the correcponding dev_w? work trace file that is
responsible for the job from job details may contain further details of the possible reason for
job hanging.

Regards,
Aidan