// ]]>

Wednesday, 2 July 2014

How to fix SPOOL_INTERNAL_ERROR

ST22 




Analysis:
Actually this is a very common issue for SAP systems especially during the implementation phrase. Normally most of go-lived systems have already set a job to periodically clean the old spool requests. 
Those spool requests generated are stored as temporary sequence objects in SAP database table or OS file depending on parameter rspo/store_location definition. Due to the limit size of the tempse, a spool overflow error will occur if it gets full.
Solution:
Normally we can solve this issue by deleting old spool requests using the following ways:
1). Go to SPAD, choose Administration -> Clean-up Spool


2). Choose the methods you prefer below to delete old spool requests


 

Another way is to go to SP01 directly, choose the criteria below and execute



Delete whatever you want.

1

Summary:
To avoid this issue, we can take some ways below per your requirements.
1). Proactive monitoring can be made via RZ20 to see the percentage of used number.

2

3

We can configure an email alert when the percentage exceeds thresh-hold value we set like 80%.
2). Increase the spool numbers by changing object SPO_NUM using t-code SNRO

4
5

Be careful that it will affect database performance if you set the number to high.
3). Schedule a background job to clean those old spool requests periodically by running report RSPO0041 and RSPO0043 with proper variant.


NOTE-
48284
16534