SAP Knowledge Base Article - Preview

2552308 - DB6: Poor performance of transaction code DB12

Symptom

Transaction code DB12 (history overview) takes a long time (1-2 minutes).

ST12 trace shows that most of the time is spent on a SQL statement (attached) on the database level.
The table function PD_GET_DIAG_HIST is called within the statement.


Read more...

Environment

SAP on IBM Db2 for Linux, UNIX, and Windows

Keywords

DB12, performance, poor, slow , KBA , BC-DB-DB6-CCM , CCMS/Database Monitors for DB2 Universal Database , BC-DB-DB6 , DB2 Universal Database for Unix / NT , BC-DB-DB6-DBA , Database Administration with DB2 Universal Database , Problem

About this page

This 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.