DB2 - Problem description
Problem IC67325 | Status: Closed |
DB2 SERVER MAY HANG ON CALL SYSPROC.WLM_SET_CLIENT_INFO WHEN APPLICATION AND SERVER CODEPAGES ARE DIFFERENT. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
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 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See the APAR description. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 UDB version 9.5 fixpack 6. * **************************************************************** | |
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 | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.5 FixPack 6 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC67662 IC67663 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.03.2010 14.06.2010 14.06.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) |