DB2 - Problem description
Problem IC76165 | Status: Closed |
DB2PD -THRESHOLDS DOES NOT PRINT QUEUEING OR TICKETING INFORMATION | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
'db2pd' utility with '-thresholds' option does not print threshold queue information for CONCURRENTDBCOORDACTIVITIES and TOTALSCPARTITIONCONNECTIONS thresholds. The threshold ticket information may not be printed for CONCURRENTDBCOORDACTIVITIES either. If the first user created service class (Service Class ID = 14) is not referenced by a threshold with queue properties (CONCURRENTDBCOORDACTIVITIES or TOTALSCPARTITIONCONNECTIONS) then queue information will not get printed for any threshold. If the first user created service class is not referenced by a threshold with threshold ticket properties (CONCURRENTDBCOORDACTIVITIES) then threshold ticket information will not get printed for any threshold. REPRODUCTION: ****STEP 1****** db2 create service class sc1 //first user created service class (ID =14) db2 create service class sc2 db2 create service class sc3 db2 "create threshold th1 for service class sc1 activities enforcement database when ACTIVITYTOTALTIME > 10 minutes continue" //threshold with no queue and no ticket properties db2 "create threshold th2 for service class sc2 activities enforcement database partition when TOTALSCPARTITIONCONNECTIONS > 10 continue" //threshold with queue but no ticket properties db2 "create threshold th3 for service class sc3 activities enforcement database when CONCURRENTDBCOORDACTIVITIES > 200 continue" //threshold with queue and with ticket properties $ db2pd -db sample -thresholds Service Class Thresholds: Threshold Name = TH1 Threshold ID = 1 Domain = 30 Domain ID = 14 .. Threshold Name = TH2 Threshold ID = 2 Domain = 30 Domain ID = 16 .. Threshold Name = TH3 Threshold ID = 3 Domain = 30 Domain ID = 18 .. Service Class Threshold Queues: //No queue and no ticket information was printed **************** ****STEP 2****** //creating queue threshold for the first service class db2 "create threshold th4 for service class sc1 activities enforcement database partition when TOTALSCPARTITIONCONNECTIONS > 10 continue" //threshold with queue and no ticket properties $ db2pd -db sample -thresholds Database Partition 0 -- Database SAMPLE -- Active -- Up 0 days 00:09:20 -- Date 05/05/2011 05:10:09 Service Class Thresholds: Threshold Name = TH1 Threshold ID = 1 Domain = 30 Domain ID = 14 ... Threshold Name = TH4 Threshold ID = 4 Domain = 30 Domain ID = 14 ... Threshold Name = TH2 .. Threshold Name = TH3 .. Service Class Threshold Queues: Queue information for threshold: TH4 Max Concurrency = 10 Concurrency = 0 Max Queue Size = 0 Queue information for threshold: TH2 Max Concurrency = 10 Concurrency = 0 Max Queue Size = 0 Queue information for threshold: TH3 Max Concurrency = 200 Concurrency = 0 Max Queue Size = 0 // threshold queue information was printed **************** ****STEP 3****** // creating queue and ticket threshold for the first service class db2 "create threshold th5 for service class sc1 activities enforcement database when CONCURRENTDBCOORDACTIVITIES > 10 continue" //threshold with queue and ticket properties $ db2pd -db sample -thresholds Database Partition 0 -- Database SAMPLE -- Active -- Up 0 days 00:11:56 -- Date 05/05/2011 05:12:45 Service Class Thresholds: Threshold Name = TH1 Threshold ID = 1 Domain = 30 Domain ID = 14 ... Threshold Name = TH4 Threshold ID = 4 Domain = 30 Domain ID = 14 ... Threshold Name = TH5 Threshold ID = 5 Domain = 30 Domain ID = 14 ... Threshold Name = TH2 ... Threshold Name = TH3 ... Service Class Threshold Queues: Queue information for threshold: TH4 Max Concurrency = 10 Concurrency = 0 Max Queue Size = 0 Queue information for threshold: TH5 Max Concurrency = 10 Concurrency = 0 Max Queue Size = 0 Queue information for threshold: TH2 Max Concurrency = 10 Concurrency = 0 Max Queue Size = 0 Queue information for threshold: TH3 Max Concurrency = 200 Concurrency = 0 Max Queue Size = 0 Service Class Threshold Tickets: Ticket information for threshold: TH5 with threshold ID 5 No tickets currently held Ticket information for threshold: TH3 with threshold ID 3 No tickets currently held //Threshold queue and ticket information was printed | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * The issue is due to incorrect checking while we are printing * * threshold queue and threshold ticket information with 'db2pd * * -db <> -thresholds'. * * If the first user created service class (Service Class ID = * * 14) is not referenced by a threshold with queue properties * * (CONCURRENTDBCOORDACTIVITIES or TOTALSCPARTITIONCONNECTIONS) * * then threshold queue information will not be printed for any * * thresholds. * * Similar to that, if that service class (ID = 14) is not * * referenced by a threshold with ticket properties * * (CONCURRENTDBCOORDACTIVITIES) then threshold ticket * * information will not get printed for any thresholds. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 and Fix Pack 5. * **************************************************************** | |
Local Fix: | |
Have the first user created service class referenced by CONCURRENTDBCOORDACTIVITIES threshold to enable the printing of threshold ticket and queue information. A disabled dummy threshold may be created for this service class as a workaround, i.e. "create threshold dummy_th for service class sc1 activities enforcement database disable when CONCURRENTDBCOORDACTIVITIES > 1000 continue" | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 Version 9.7 and Fix Pack 5. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.05.2011 19.12.2011 19.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |