home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC78826 Status: Closed

A table name including MBCS characters is not displayed in deadlock event
monitor.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
The db2evmon output for the deadlock event monitor may be 
garbled when: 
 - the target table includes MBCS characters 
 - the locale db2evmon running is different from database 
codepage 
 
The same thing applies to the SQL statement.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using event monitors                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.1 Fix Pack 11 or later.             * 
****************************************************************
Local Fix:
Run db2evmon with same locale as the database codepage.
available fix packs:
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Problem was first fixed in DB2 Version 9.1 Fix Pack 11.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC78906 IC78907 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.09.2011
19.01.2012
19.01.2012
Problem solved at the following versions (IBM BugInfos)
9.1.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.11 FixList