DB2 Workload Manager (WLM) as a Monitoring Solution – Understanding WLM (Part1 of 3)

You may also like...

6 Responses

  1. Kovthe says:

    How can we list details of sqls such as statement text, tables accessed , etc executing in a workload?

    • Abhik Roy says:

      Hello
      more of that will be covered in part 2 and part 3.

      When we create the WLM event monitors (to be covered in part2) the below tables get created. We could query those or the WLM table functions to find information on statement text, execution time etc.
      ACTIVITYSTMT_DB2ACTIVITIES
      ACTIVITYVALS_DB2ACTIVITIES
      ACTIVITY_DB2ACTIVITIES
      CONTROL_DB2ACTIVITIES
      CONTROL_DB2STATISTICS
      HISTOGRAMBIN_DB2STATISTICS
      QSTATS_DB2STATISTICS
      SCSTATS_DB2STATISTICS
      WCSTATS_DB2STATISTICS
      WLSTATS_DB2STATISTICS

      Thanks

      Abhik

      • Kovthe says:

        Thanks for your reply. I will wait for your next post. I have a question,how much overload these WLM event monitors will cause on the database?

        • Abhik Roy says:

          It could cause overload on the database based on the level of data collected. Both activity metrics and aggregate activity data can be collected at a base level or the extended level. Extended data collection on the database tends to have an impact on the database and should be used only to troubleshoot specific database issues.

  2. Joydeep says:

    Nice Post 🙂

  1. April 7, 2015

    […] is part three of a three part series. The full series includes: DB2 Workload Manager (WLM) as a Monitoring Solution – Understanding WLM (Part1 of 3) DB2 Workload Manager (WLM) as a Monitoring Solution– How to Set up WLM (Part 2 of 3) DB2 Workload […]

Leave a Reply

Your email address will not be published. Required fields are marked *