cancel
Showing results for 
Search instead for 
Did you mean: 

RSPO1041 taking huge execution time after EHP5 upgrade

Former Member
0 Kudos

Hi All,

After EHP5 upgrade, report RSPO1041 is taking too long to execute.

Report RSPO1041 is scheduled to be executed daily in production system via a job.

Before EHP5 upgrade the job use to execute in 10 mins.

But after EHP5 upgrade the job needs to be cancelled as it takes more than 24 hours to execute.

The report deletes all the spools older than 45 days.

Please help to provide a solution to this problem.

Thanks,

Prashant

Accepted Solutions (0)

Answers (3)

Answers (3)

premsukh_bishnoi
Contributor
0 Kudos

Hi

Can you please check if this note is applicable to your case:

# 1422843 - Wrong deletion date in spool request

Can you please run consistency check, referring to the following:

# 48400 - Reorganization of TemSe and Spool

Spool Consistency Check :

http://help.sap.com/saphelp_nw04/helpdata/en/d9/

4a8f8a51ea11d189570000e829fbbd/content.htm

Maintaining the Spool Database :

http://help.sap.com/saphelp_nw04/helpdata/en/cd/

a9e63bcd8aed57e10000000a114084/content.htm

Please also ensure that all the spool re-org jobs of the attached Note

# 48400 are scheduled regularly in your system.

Regards

Former Member
0 Kudos

Hi Premsukh,

We ran the consistency check on the spools.

It didn't report a single inconsistency.

Finally, we are thinking of manually deleting the spools from production server.

Thanks,

Prashant

tomas_black
Employee
Employee
0 Kudos

Hello Prashant,

please run the following command on the OS level to increase the trace level of the work process that's being used by RSPO1041:

kill -USR2 <PID of the work process>

This will immediatelly populate the dev_w file with more information. Please attach the last entries (where an error should be visible) and the run the same command but with USR1 to decrease it back to trace level 1.

Also, what's your kernel patch level? Please ensure you're using the very last patch level availble, specially since this is a recently upgraded system.

Best regards,

Tomas Black

Former Member
0 Kudos

Hi Tomas,

The KERNEL level is as follows:

Kernel release720
Compilation   AIX 2 5 00092901D600 Mar  1 2012 22:11:06
Sup.Pkg lvl.  210
ABAP Load     1780
CUA load      39
Mode          opt

Thanks,

Prashant

tomas_black
Employee
Employee
0 Kudos

Hi Prashant,

would it be possible to patch your system with the latest PL (300)?


Also were you able to increase the trace level of the running RSPO1041 work process?

Best regards,

Tomas Black

Former Member
0 Kudos

Hi Tomas,

No, client is not ready to patch the system with the latest upgrades due to its business impact.

We do not have authorization to increase the patch level. So until we give the basis team a viable reason they won't change the trace level.

Thanks,

Prashant

paul_power
Active Contributor
0 Kudos

Hi Prashant,

Do you have any screenshots of SM66 during the runtime.

Is it stuck on a particular select for example?

Can you please run consistency check, referring to the following:

48400 - Reorganization of TemSe and Spool

regards,

Paul

Former Member
0 Kudos

Hi Paul,

The program isn't stuck on some select query.

In fact it gets stuck while deleting some special type of spools.

While debugging, we noticed it stucks for certain spools while deleting for as long as half an hour.

These spools have TSP01-RQAPPRULE greater than or equal to 3.

Our system patch level is 702 so Note 48400 isn't applicable.

Thanks,

Prashant