When you execute some transactions, the system runs into a standstill or the transactions run for a longer period than the normal. In the meanwhile, the work process monitor (SM66) shows the processes are running on tables with LOB (Large Object) columns. RAWSTRING and STRING are ABAP dictionary datatypes that represent BLOB and CLOB respectively. Some of the most common tables are DYNPSOURCE, DYNPLOAD, REPOSRC, REPOLOAD, FPLAYOUTT, and FPCONTEXT.
The transaction will show up and the system will come back to normal after several minutes. Additionally, we can take a look into the STAD records of the long running transactions as shown in following figures:
Usually, most of the time is spent on Database request time, and the direct read/ sequential read time will be very high as shown in the left STAD record. Sometimes, it will show most of the time is spent in processing time as shown in the right STAD record.
Database: IBM DB2 for Linux, UNIX, and Windows
- DB2 10.1 lower than fix pack FP5SAP
- DB2 10.5 lower than fix pack FP6SAP
System hang, Performance, Transaction, REPOLOAD, DYNPLOAD, FPLAYOUTT, FPCONTEXT , KBA , SV-PERF , Performance Messages , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.