cancel
Showing results for 
Search instead for 
Did you mean: 

Automatic of deletion of Spool requests

Former Member
0 Kudos

Hi,

Scheduled job SAP_REORG_SPOOL is running every night on our Production system.

Yet this morning we discovered our Spool database was full.

I've checked note 64333 and confirmed that the following parameter is set:

c_def_pexpi like pri_params_pexpi value '8

And yet still our spool files are not being automatically deleted.

Could anyone offer any advise on what I can check to try track down the problem please?

Thank you.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

As of the beginning of the year 2011, the report RSPO1041 no longer deletes spool requests. The job log contains a message stating that the factory calendar cannot be read.

Please follow the SAP note number 1532398..

As per the above note " The factory calendar used in the variant of the report RSPO1041 is invalid. As of January 1, 2011, this problem will occur more frequently because the factory calendars delivered by SAP in 1996 become invalid on December 31, 2010."

Please follow the instruction...

1. Use transaction SCAL to change the validity of the factory calendar.

2. After you implement the corrections contained in the above note, the report RSPO1041 responds as follows in the error It uses all of the days and not just all of the working days of the factory calendar to calculate whether or not a spool request is to be deleted.

After you implement the above said note, the report RSPO1041 will also no longer terminate in the background because it tries to delete its own spool request.

Regards

Bhuban

RKFL

JPReyes
Active Contributor
0 Kudos

What report are you running in the job?... you should use RSPO1041

Read, Note 130978 - RSPO1041 - Replacement for RSPO0041

Also check temse for consistency

Regards

Juan

Former Member
0 Kudos

Thanks for the quick reply.

No, it's running RSPO0041. Is that likely to be the culprit for thsi issue then?

JPReyes
Active Contributor
0 Kudos

Most likely, replace it and give it another go.

Regards

Juan

Former Member
0 Kudos

Ok, I've created another job to run immediately running RSPO1041 instead of RSPO0041.

Job ran successfully, but problem persists.

Still have Spool requests dating back to early May.

JPReyes
Active Contributor
0 Kudos

Did you run the consistency check on TEMSE (SP12)?

Former Member
0 Kudos

I have run the consistency check and deleted the inconsistencies.

I still have spool requests dating back weeks.

sivakumar_kilari3
Active Contributor
0 Kudos

Execute this RSPO1041 report directly in SA38

Fill all required information

save with variant and execute their itself

Create background job with saved variant.

Thanks

Siva

Former Member
0 Kudos

Paul,

If my guess is right, Just running RSPO1041 would not solve the issue. The selection crieterion matters. especially the inprocessing and incorrect status requests deletion crieterion. I am sure revisiting these will solve your issue