SAP Note 11070 - Space requirements of TemSe and spooler

Component : TemSe (Repository for temporary sequential objects) -

Solution : https://service.sap.com/sap/support/notes/11070 (SAP Service marketplace login required)

Summary :
The SAP Note addresses issues with insufficient disk space for TemSe and Spooler files, commonly generating UNIX error messages with errno 28 "No space left on device". The root cause is the provision of less space than required. TemSe primarily stores sequential datasets like batch logs and spool files. Space requirements vary based on application profile, data volume, and cleanup frequency. Specific paths for logs, spool requests, and output requests are detailed, along with deletion protocols. It's critical to manage space effectively, especially under /usr/sap//SYS/global/*. Solutions include assigning more disk space, avoiding simultaneous use of space-heavy applications, and regularly running cleanup programs.

Key words :
profile setting  rspo/store/location = gscope, location /usr/sap/<system>/sys/global/, /usr/sap/<system>/sys/global/, /usr/sap/<system> /<instanz>/data/, temse stores sequential datasets, space requirements depend greatly, /usr/spool/ / delete, symptom key word, additional key words, currentlythe batch logs

Related Notes :

48400Reorganization of TemSe and Spool
20176Where is the spool request saved?
19706Tuning the Spooler
16513File system is full - what do I do?
16083Standard jobs, reorganization jobs