Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC66626 Status: Closed

V97FP1/FP2: DB2LOOK -WLM MISSES PRODUCING FORCE APPLICATION CLAUSE FOR
CREATE THRESHOLD UOWTOTALTIME

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Group Reporting Issue: SVT  (but this is a functional problem) 
 
Problem Abstract: V97FP1/FP2: db2look -wlm misses producing 
FORCE APPLICATION clause for CREATE THRESHOLD UOWTOTALTIME 
 
Problem Details: 
Problem introduced in V97FP1 with new functionality of new 
UOWTOTALTIME from PCR043581 - WLM Enhancements. 
Note: For this threshold a new exceed action was introduced, 
FORCE APPLICATION, with 'F' marked in the EXECUCTION column of 
SYSCAT.THRESHOLDS. 
 
If a database has a UOWTOTALTIME theshold with FORCE APPLICATION 
exceed action, db2look -wlm produces a wrongful CREATE THRESHOLD 
DDL with the FORCE APPLICATION clause missing. 
 
Steps to repro 
1) Use this DDL to create a UOWTOTALTIME threshold with FORCE 
APPLICATION exceed action: 
CREATE THRESHOLD thresholddatabaseuowtotaltimeG1 
    FOR DATABASE ACTIVITIES 
    ENFORCEMENT DATABASE 
    WHEN UOWTOTALTIME > 17 MINUTES 
    COLLECT ACTIVITY DATA ON ALL WITH DETAILS AND VALUES 
    FORCE APPLICATION ; 
2) issue db2look -wlm to get the DDL for this threshold 
Here is the DDL from db2look that is produced; you will noticed 
that "FORCE APPLICATIONS" is missing. 
CREATE THRESHOLD "THRESHOLDDATABASEUOWTOTALTIMEG1" 
FOR DATABASE ACTIVITIES 
ENFORCEMENT DATABASE 
WHEN UOWTOTALTIME > 17 MINUTES 
COLLECT ACTIVITY DATA 
ON ALL DATABASE PARTITIONS 
WITH DETAILS AND VALUES; 
 
Note: If you run this DDL from db2look, you will get this error 
since the exceed action clause is missing: 
SQL0104N  An unexpected token "END-OF-STATEMENT" was found 
following "H 
DETAILS AND VALUES".  Expected tokens may include: 
"<threshold_exec_options>".  SQLSTATE=42601 
 
 
Problem Origin: 
Problem introduced in v97fp1 via PCR043581, 
but problem found in v97fp2 (from adhoc testing). 
 
Note to CE/Dev: 
Pls add a TC to the db2look bucket when you fix this defect.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Software                                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* db2look -wlm misses producing FORCE APPLICATION clause for   * 
* CREATE THRESHOLD UOWTOTALTIME                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* fixed in v97 fp2                                             * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
db2look -wlm misses producing FORCE APPLICATION clause for 
CREATE THRESHOLD UOWTOTALTIME
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66628 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.02.2010
08.04.2010
08.04.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList