|
Problem IC67662
|
Status: Geschlossen |
DB2 SERVER MAY HANG ON CALL SYSPROC.WLM_SET_CLIENT_INFO WHEN APPLICATION AND SERVER CODEPAGES ARE DIFFERENT. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
If a clp script is used to call stored procedure
SYSPROC.WLM_SET_CLIENT_INFO and SYSPROC.WLM_SET_CLIENT_INFO
stored procedure is used to set only the accounting string
leaving rest of the parameter of the stored procedure call as
NULL. For example:
CALL SYSPROC.WLM_SET_CLIENT_INFO(NULL, NULL, NULL, 'Accounting
department', NULL)
DB2 Server may hang when client and server codepages are
different.
For example if Application codepage is IBM-943(943) and Database
codepage is JA_JP.UTF-8(1208), the above statment executed using
clp script can cause hang on the server. The stack trace of
hanging agent will look like:
0x0900000035728D7C sqlnls_getmap@glue3E8 + 0x54
0x0900000035CA0C94 sqlrrGetLiteral__FiPcN22UlPUlPPc + 0x13C
0x0900000035728C64 sqlrrGetLiteral__FiPcN22UlPUlPPc@glueB04 +
0x74
0x0900000035CA04A4 sqlrr_shortcut_excsqlset__FP8sqlrr_cbPcUiPb +
0x43C
0x0900000035358EBC sqlrr_excsqlset__FP14db2UCinterface + 0x110 |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* If a clp script is used to call stored procedure *
* *
* SYSPROC.WLM_SET_CLIENT_INFO and SYSPROC.WLM_SET_CLIENT_INFO *
* *
* stored procedure is used to set only the accounting string *
* *
* leaving rest of the parameter of the stored procedure call *
* as *
* NULL. For example: *
* *
* *
* *
* CALL SYSPROC.WLM_SET_CLIENT_INFO(NULL, NULL, NULL, *
* 'Accounting *
* department', NULL) *
* *
* *
* *
* DB2 Server may hang when client and server codepages are *
* *
* different. *
* *
* *
* *
* For example if Application codepage is IBM-943(943) and *
* Database *
* codepage is JA_JP.UTF-8(1208), the above statment executed *
* using *
* clp script can cause hang on the server. The stack trace of *
* *
* hanging agent will look like: *
* *
* *
* *
* 0x0900000035728D7C sqlnls_getmap@glue3E8 + 0x54 *
* *
* 0x0900000035CA0C94 sqlrrGetLiteral__FiPcN22UlPUlPPc + 0x13C *
* *
* 0x0900000035728C64 sqlrrGetLiteral__FiPcN22UlPUlPPc@glueB04 *
* + *
* 0x74 *
* *
* 0x0900000035CA04A4 *
* sqlrr_shortcut_excsqlset__FP8sqlrr_cbPcUiPb + *
* 0x43C *
* *
* 0x0900000035358EBC sqlrr_excsqlset__FP14db2UCinterface + *
* 0x110 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 9.7 fix pack 3. *
**************************************************************** |
| Local-Fix: |
1. Call stored procdure SYSPROC.WLM_SET_CLIENT_INFO to set both
application name accounting string.
For example:
CALL SYSPROC.WLM_SET_CLIENT_INFO(NULL, NULL, 'auditor',
'Accounting department', NULL)
2. Call SYSPROC.WLM_SET_CLIENT_INFO stored procedure when no
code page conversion is required |
| verfügbare FixPacks: |
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 3. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 06.04.2010
23.09.2010
23.09.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP3
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
