Collecting MustGather data for IBM Db2 issues
Prepare the following MustGather information before you call HCL Support to help with IBM Db2 issues.
About this task
IBM DB2 database slow-downs may be caused by various factors. Before troubleshooting,
review the article Troubleshooting a performance
slowdown - DB2 side. The article will aid you in identifying and
resolving the problem using the following steps.
- When troubleshooting a performance slow-down where DB2 is a suspect, start from the application server layer and review the webcontainer activities using javacores. Verify that there are indeed threads waiting on DB2. Otherwise, the problem is elsewhere.
- Once you identified a possible DB2 issue, move to the database and collect the number of DB2 connections and their state. Depending on what’s normal for the environment, it may lead to the bottleneck of a performance problem.
- Examine what queries are being executed; and review key metrics such as the frequency of execution, elapsed time and number of rows read. These values may expose room for tuning queries, for instance.
- The article Troubleshooting a performance slowdown - DB2 side also provides a solution to review your findings using MON_GET_PKG_CACHE_STMT to confirm your findings. This is equivalent to snapshots for dynamic-sql providing cumulative statistics for all running SQLs.
Collecting data for IBM Db2