Spool size too big and program giving dump

[Former Member]

Hi experts,

I have an interface report, that generates a spool when run as a background job.

I encountered a situation when the spool was too large in size, somewhere close to 2 GB,

and the interface report gave a dump as seen in the job log.

The dump was by the name "SPOOL_INTERNAL_ERROR".

The error analysis session indicated:

More detailed description of error: "spool overflow ".

The logic for displaying the spool is written as a separate subroutine which is being called in the main

interface report.

Is there any way to spilt/break the spool into 2 parts, so that once the spool size is > 2 GB, then the next spool

is automatically displayed?

Any help would be highly appreciated.

Thanks,

Mohit.

[Former Member]

Hi Mohit,

For SPOOL maintenance ,

1. You can schedule standard system hygiene jobs using SAP note: 16083

2. You can also, Using tcode SP12, you can delete temse objects : SP12 -> Temse data Storage- > Consistency check. Select the objects to be deleted.(It might take time for the objects to get displayed)

3. If still the issue persists, you can refer note 48284 and follow the steps mentioned in client 000 of your system.

SNRO->Change->Click on button 'Number Ranges'->Click on button Change 'Intervals'

In the "'To No." column , change the upper limit of the interval SPO_NUM to 999,999

Kindly consult your administration team before doing this.

All the best.

[Former Member]

This message was moderated.

[Former Member]

Delete the old spool requests by RSPO1041 abap program in SE38.

Hope this resolve ur issue.

Cheers

ElNino

[Former Member]

Hi,

You only have 2 solutions :

Reduce the job spool size by modifying the program

or

Increase the global spool size (table TST03)

Regards,

Olivier