DB2 10.5 for Linux, UNIX, and Windows

Workload management scenarios

Workload management sample application
Comprehensive workload management features have been integrated into your DB2® data server with DB2 workload management, giving you finer control over activities, resources and performance, and deeper insight into how your system is running. A workload management sample application is now available on developerWorks®.
Scenario: Investigating a workload-related system slowdown
If you notice a system slowdown (for example, some applications take much longer to complete than expected) and are unsure whether the problem is related to the configuration of the workloads, you can use table function data to investigate and, if necessary, correct the problem.
Scenario: Aggregation of activity metrics across child activities
Each row in an activity event monitor contains information and monitor metrics describing the execution of a specific activity. Included in the activity information are the parent_uow_id and parent_activity_id monitor elements. These monitor elements are nonzero if the activity is a child of some other activity (nested) and the elements identify the parent activity.
Scenario: Identifying activities that are taking too long to complete
Workload management table functions simplify the task of identifying a specific activity inside the data server and, if necessary, canceling it without having to end the entire application.
Scenario: How to cancel activities queued for more than an hour
Using the example scripts described here, you can create a procedure to cancel activities that have been queued for more than an hour. In addition, an example script is provided that can be used to schedule the queued-activity-cancelling procedure to run every 10 minutes using the DB2 Administrative Task Scheduler.
Scenario: Identifying activities with low estimated cost and high runtime
The following example shows how you can use work classes, work action sets, thresholds, and activity collection to identify activities that have a low estimated cost but a high runtime. This situation could indicate that the estimated cost (in timerons) is inaccurate because of out-of-date table and index statistics.
Scenario: Cancelling all activities being executed in a service subclass
The following is an example of a stored procedure that can be used to cancel all currently executing activities in a particular service subclass.
Scenario: Disconnecting all applications either mapped to or executing activities in a service class
The following is an example of a stored procedure that can be used to disconnect (force) all applications that are either mapped to a particular service class or currently executing activities in a particular service class.
Scenario: Tuning a DB2 workload management configuration when capacity planning data is available
If you performed capacity planning, you should have information about the types of users and their expected response times. You can use this information to construct, determine the effectiveness of, and tune your DB2 workload management configuration.
Scenario: Tuning a DB2 workload management configuration when capacity planning information is unavailable
You can use the DB2 workload management tools to help design, monitor, and tune a workload management configuration even if you do not have capacity analysis data to use for designing the configuration.
Scenario: Moving table spaces to different storage devices
This scenario uses multi-temperature storage to set up a database system that uses service classes of different priorities, each class using a different type of storage device.