Skip to Content
Technical Articles

Table TST03 grow fast

Hello Fellows,

Due to the large use of Spool data since Go live, many Clients forget to clean up, follow a very detailed roadmap on how to maintain Table TST03

The size of table TST03 grew rapidly, how to identify the application objects and reorganize the table?

Table TST03 is storing all types of Temse(temporary sequential) objects, the first step is to check which Temse object is large from transaction SP12, click on menu Temse Data Storage-> Memory Allocation, the result is like below:

1. If the size “In database” is very less comparing with the LOB segment you see on database level, a reorganization on database level is required, see SAP Note 2203297 for more details.

2. If you see any application specific data is large, run the corresponding report as described in SAP Note 48400, Solution 2.

3. Sometimes the SPOOL size can be increased abnormally by some very large spool requests, on latter pages we can see daily statistics:

 

 

From menu System-> List-> Save-> Local File-> Text with Tabs, we can save the result list to Excel, and then sort on header column “Number of Bytes in DB”.

 

 

In above example we can see the size is around 580GB on 03.03.2000, in this case we can run report RSPO1041 to delete the large spools, refer to note 852141 if you see performance problem when deleting large spools.

Regards,

Cléo Machado

SAP Basis

1 Comment
You must be Logged on to comment or reply to a post.
  • Hi,

    Nice content.

    Small Hint: After you delete via RSPO0041, you see in TemSe, 30,000 to 40,000 TemSe. Deleting them directly manually can be painful. So, we can use rdisp/max_wprun_time=0 dynamic parameter instead before deletion. This is specially applicable after a System Refresh activity or a System Migration activity. Probably you may want to add this step too

    Thanks,

    Kaushik