SAP OSS Notes
16534 SAP OSS Note - Job terminates due to SPOOL_INTERNAL_ERROR
SAP OSS Note 16534 version 0017 contains details of a know issue related to Job terminates due to SPOOL_INTERNAL_ERROR . This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.
...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.
Note 16534 Details:
When does this problem occur
Batch job terminates due to errors in the spooler
SysLog F82: Invalid writer count
No handle for an open TemSe object
(magic==X'4f444f23')
Some error in TemSe management
Runtime error "SPOOL_INTERNAL_ERROR" occurred
Transaction termination 00671
Cause of the problem and Pre-requisites
Spooler consistency check RSPO0043 or RSPO1043 is used in the productive
system with a "lock-delete duration" that is too low.
The problem can arise both during online checks in the SPAD and in the
batch.
To date, there has been no other definitive cause.
Important: RSPO0043 is obsolete. Use only RSPO1043 for the spooler TemSe
consistency check.
The spooler consistency check RSPO1043 deletes the write locks on spool
requests that are older than a certain duration. This duration
(the "age" of the write locks) is specified as the parameter
"Release locks after... minutes".
The standard value for RSPO1043 is 10080 minutes, that is, seven days.
The problem cannot occur with this standard value since there a
re normally no batch jobs that have a runtime up to seven days.
(Although RSPO0043 has a standard value of thirty minutes, it should no
longer be used, see above.)
Solution instructions
Select the parameter "Release locks after... minutes" so that it is
large enough so that no write locks of spool requests of current b
atch jobs are affected during the daily execution of RSPO1043.
(The corrections specified in this note set 10080 as the default for
write locks in RSPO0043.)
Description of problem
Spool, RSPO0043, RSPO1043
------------------------------------------------------------------------
|Manual Pre-Implement. |
------------------------------------------------------------------------
|VALID FOR |
|Software Component SAP_BASIS SAP Basis compo...|
| Release 710 Until SAPKB71009 |
| Release 711 Until SAPKB71104 |
------------------------------------------------------------------------
RESET N1
- Use transaction SE11 to create the structure BTC_SPOOLID_LINE with the
description 'TBTC_SPOOLID line'. Copy the components of the table
description TBTC_SPOOLID. - Use transaction SE11 to create the table type BTC_SPOOLID with the
description 'Table type for TBTC_SPOOLID' and the line type BTC_S - Use transaction SE11 to create the table type BTCLISTID_TAB with the
description 'Table type for BTCLISTID' and the line type BTCLISTID.
POOLID_LINE.
Solution instructions
Please import the corrections attached to this OSS note into your SAP system using SNOTE.
You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.
You can also check if a new version of note 16534 has been released as well as see if the note is valid for your current SAP system landscape.
Check if SAP OSS note 16534 has already been downloaded and is valid
To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
From here you can just enter the note number 16534 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.
If note 16534 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.
Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)