When you execute some transactions, the system seems to come to a standstill, or the transactions run for a longer period than normal.
Meanwhile, the work process monitor (SM66/SM50) shows the processes are running on tables with LOB (Large Object) columns. RAWSTRING and STRING are ABAP dictionary datatypes that are represented by BLOB and CLOB columns respectively in the database.
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.
To confirm if the tables listed in SM66/SM50 contain LOB columns, use the following query:
SELECT table_name, column_name FROM dba_lobs WHERE owner = '<sapuser>';
Additionally, we can take a look into the STAD records of the long running transactions as shown in following figures:
Most of the time is spent on Database request time, and the average direct/sequential read time per row will be very high as shown in the STAD record above.
It may also show most of the time is spent in processing time as shown in the STAD record below. (This is due to how actions within a single dialog step are measured. The Load & Generate process will make DB requests which are not accounted for in the Database section of the STAD record and thus appear as increased processing time.)
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 , KBA , SV-PERF , Performance Problems , 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.