SAP Knowledge Base Article - Preview

2247686 - Identify expensive sql statements in a non-ABAP environment

Symptom

The business functions give a result only after a unusual high wait time. The reproduction steps of this performance problem are known. There is a hint, that most of the time is spent on the MaxDB database. It should be clarified which sql statements are responsible for the wait. On the database environment there is no local ABAP stack, so it is not possible to create an sql trace with ST05.


Read more...

Environment

Any MaxDB database version of a system without any SAP Netweaver Application Server ABAP

for example: MaxDB database of a Java-only instance, Content server database, Livecache database

Keywords

DBACOCKPIT, command monitor, performance analysis, sql tuning, bind variables, native sql , KBA , BC-DB-SDB , MaxDB , BC-DB-LVC , liveCache , 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.