Check the memory distribution in TemSe:
-> Tools -> Administration
-> Spool -> TemSe administration (Transaction SP12)
-> TemSe data Storage -> Memory allocation
Check whether the number of your TemSe objects is very large. Also check whether many of your objects are stored with an unlimited retention period. Note that you cannot see the retention period of spool requests here as it is stored in Table TSP01 and can be read from Transaction SP01.
Delete any objects that are no longer required:
- Delete spool objects that are no longer required:
(Transaction SPAD) -> Administration -> Clean-up spool
You can also use the report RSPO0041 to delete out-of-date spool requests.
- Delete job logs no longer required using report RSBTCDEL
- To delete background input logs that are no longer needed, use the RSBDCREO report
There is another report RSTS0022 for deleting old Temse objects but I suggest not using this report as this report does not take into account dependencies between TemSe tables and other tables.
Dig deeper on SAP Basis administration and NetWeaver administration
Related Q&A from Farooq Ali
SAP BI/BW expert Farooq Ali discusses the differences in the use of SAP Software Deployment Manager (SDM) and SAP Java Support Package Manager (JSPM)...continue reading
Find out how resetting a transport buffer can help fix an error that occured during the installation of an SAPGUI patch. Learn how to avoid an ...continue reading
Find out how to set a default SAP BI client within an SAP Business Intelligence (BI) system. Learn how to run an SAP Basis TCode in a default SAP BI ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.