|
Problem IC67295
|
Status: Closed |
DB2 CLI FIXES FOR USE WITH IBM OPTIM PERFORMANCE MANAGER EXTENDED INSIGHT VERSION 4.1 |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
The following items have been addressed in DB2 CLI V9.7 Fixpack
2 for use with IBM OPM EI 4.1:
If an SQL statement fails due to certain compilation errors,
such as SQL syntax errors, while you are monitoring CLI
applications that target DB2 LUW v9.7 and higher, OPM EI might
incorrectly report the re-execution of a previously executed
statement in the Extended Insight Analysis dashboard.
When a CLI statement failure produces multiple SQLCODEs, the
Extended Insight Analysis Dashboard might display the last
SQLCODE for the failing statement rather than the first SQLCODE.
Also, actual statement failures might not be shown for CLI
statements that fail do to client side errors that do not have
an associated SQLCODE (-99999 native error).
Partial monitoring data will appear in the Extended Insight
Analysis dashboard when you monitor statements that use
column-wise array input to bind parameter markers. Partial
monitoring data will also appear when you attempt to monitor
statements that use CLI LOAD functionality, which is currently
an unsupported scenario. Partial monitoring will also appear
when monitoring CALL statements that return multiple result
sets. In the scenario, statistics are collected until the close
of the first result set rather than the close of the last result
set.
Under certain conditions, while you are monitoring a CLI
application with OPM EI, the application might fail while
attempting the application attempts to cancel an executing SQL
statement with SQLCancel().
Statements with open result sets might not be monitored in
certain error scenarios where CLI prevents the application from
performing additional statement executions on the same handle
until previously opened result sets are closed (CLI0115E).
The diagnostic log might contain extraneous entries when the
diagnostic level is set to info.
If you monitor a CLI application with Optim Performance Manager
Extended Insight and the CLI application is using the CLI driver
of DB2 V9.7 Fix Pack 1 then you might see very high values in
the range of multiple days for the following metrics on the
Extended Insight dashboard: Average end-to-end response time,
Maximum end-to-end response time, Maximum inflight time and
Driver time. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of DB2 CLI and Optim Performance Manager Extended *
* Insight 4.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See error description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 CLI V9.7 Fixpack 2 *
**************************************************************** |
| Local Fix: |
n/a |
| 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 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 |
Fixes in DB2 CLI V9.7 Fixpack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.03.2010
23.04.2010
23.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
|
 |
