Solution : https://service.sap.com/sap/support/notes/16534 (SAP Service marketplace login required)
Summary :
Batch jobs are prematurely terminating due to spooler errors highlighted by the invalid writer count and issues in TemSe object handling, leading to runtime error "SPOOL_INTERNAL_ERROR" and transaction termination. The problem stems from the spooler consistency checks RSPO0043 or RSPO1043 being set with a lock-delete duration that is too brief to account for the typical batch job execution times. RSPO0043 is outdated and should not be used; instead, RSPO1043 is recommended with a lock duration of 10080 minutes to avoid overlapping write locks on spool requests. Modify RSPO1043's "Release locks after..." setting to align with the new standard as preventative action.
Key words :
software component sap_basis sap basis compo, prerequisites spooler consistency check rspo0043, symptom batch job terminates due, spooler consistency check rspo1043 deletes, spooler temse consistency check, open temse object, temse managementruntime error, invalid writer count, magic==x'4f444f23', lock-delete duration
Related Notes :
| 1560450 | |
| 453069 | DART extraction terminates with SPOOL_INTERNAL_ERROR |
| 48400 | Reorganization of TemSe and Spool |
| 46621 | No handle for open TemSe object |