Symptom
The TemSe data is stored in the file system (as job logs or BDCLG files), and also in the database (e.g. spool requests or HR objects).
From the database side the table TST03 can appear to be very large. This can be also completely normal if there is a large amount of data in TemSe.
However, this is not always the case. To confirm this the size of the table needs to be compared with the actual data stored in the TemSe.
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Read more...
Environment
- SAP R/3 4.6C and above with ORACLE database
- SAP ERP 6.0 all releases with ORACLE database
- SAP NetWeaver all releases with ORACLE database
Product
Keywords
large, huge, TemSe-Datenablage, Platzbelegung, Statistiken ueber Speicherbelegung, In der Datenbank, In Dateien, Insgesamt, Tabelle TST03, Objekt TST03, sp01 , KBA , BC-CCM-PRN , Print and Output Management , BC-DB-ORA , Oracle , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview