My name is Man-Ted Chan and I’m from the SAP HANA product support team. Today I’m just writing a quick post on what to do when running into DMO/SUM performance issues.
On the SAP Application server run ST04 to identify any long running statements. Alternatively you can check if there are active SQL statements running in view M_ACTIVE_STATEMENTS and/or it they are blocked in view M_BLOCKED_TRANSACTIONS
If you have access to the SAP HANA Studio or DBACockpit you can check the performance tab to see the following:
- if there are any blocked threads in the SAP HANA studio called by the SAP<SID> user
- if there are any long running threads on the HANA system
If nothing is apparent connect to the system via R/3 connection as the DDIC user and run the ST05 transaction and enable the SQL trace on the application server where the upgrade is executed.
After 30 minutes stop the trace and view it
Sort by the “Execution Duration” and then look for that statement is in the SQL Plan Cache (in HANA Studio or DBACockpit) and compare the execution times
If the execution time between the HANA system is equivalent to the execution on the application server then check then investigate why the SQL statement is having performance issues. If further assistance is needed on this please create a ticket under the SAP HANA component HAN-DB (subject to change)
If the time on the SAP HANA side is a lot shorter than the time on SAP Application server then the issue could be network/hardware related (check the ping time between the client and server or ask the customer about the data throughput). If it is determined to not be an issue on the SAP HANA or hardware side then please create an incident with the upgrade team under componet BC-UPG-TLS-TLA.