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 IT05906 Status: Closed

DB2 INSTANCE MAY CRASH DUE TO USERNAMES THAT EXCEED 128 BYTES OR DUE TO
LARGE NUMBER OF USER ON SERVER

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 instance may crash due to user names that exceed 128 bytes 
or due to large number of user on server: 
 
The following db2diag.log messages will be seen 
 
2014-09-24-16.43.12.687866-240 E336734A470        LEVEL: Severe 
 PID     : 8978600              TID  : 148723      PROC : 
db2sysc 0 
 INSTANCE: db2inst1                 NODE : 000         DB   : 
SAMPLE 
 APPHDL  : 0-29043              APPID: 
123.123.123.11.22222.123456789 
 AUTHID  : O001383 
 EDUID   : 148723               EDUNAME: db2agent (SAMPLE) 0 
 FUNCTION: DB2 UDB, oper system services, 
sqloEDUCodeTrapHandler, probe:12 
 DATA #1 : <preformatted> 
 Current stack size = 8388608 
 
 2014-09-24-16.43.12.688016-240 E337205A631        LEVEL: Severe 
 PID     : 8978600              TID  : 148723      PROC : 
db2sysc 0 
 INSTANCE: db2inst1                 NODE : 000         DB   : 
SAMPLE 
 APPHDL  : 0-29043              APPID: 
123.123.123.11.22222.123456789 
 AUTHID  : O001383 
 EDUID   : 148723               EDUNAME: db2agent (SAMPLE) 0 
 FUNCTION: DB2 UDB, oper system services, 
sqloEDUCodeTrapHandler, probe:1000 
 MESSAGE : ADM0502C  The DB2 instance has terminated abnormally. 
To remedy this 
          problem, increase the AGENT_STACK_SZ DBM configuration 
parameter. 
          Contact IBM Support for further assistance. 
 
 2014-09-24-16.43.12.688381-240 I337837A564        LEVEL: Error 
 PID     : 8978600              TID  : 148723      PROC : 
db2sysc 0 
 INSTANCE: db2inst1                 NODE : 000         DB   : 
SAMPLE 
 APPHDL  : 0-29043              APPID: 
123.123.123.11.22222.123456789 
 AUTHID  : O001383 
 EDUID   : 148723               EDUNAME: db2agent (SAMPLE) 0 
 FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, 
probe:1 
 MESSAGE : Error in agent servicing application with coor_node: 
 DATA #1 : Hexdump, 2 bytes 
 0x0700000015809350 : 0000 
.. 
 
 2014-09-24-16.43.12.688519-240 I338402A571        LEVEL: Error 
 PID     : 8978600              TID  : 148723      PROC : 
db2sysc 0 
 INSTANCE: db2inst1                 NODE : 000         DB   : 
SAMPLE 
 APPHDL  : 0-29043              APPID: 
123.123.123.11.22222.123456789 
 AUTHID  : O001383 
 EDUID   : 148723               EDUNAME: db2agent (SAMPLE) 0 
 FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, 
probe:2 
 MESSAGE : Error in agent servicing application with 
coor_agent_index: 
 DATA #1 : Hexdump, 2 bytes 
 
The following stack will be seen in the generate trap file: 
 
sqlogus3 
sqlrrTrustedCallbAccountGroups__FP5sqlcaiPcUiPUiPPc 
sqlerTrustedRtnCallbackRouter__FUiPPv 
accountsGroups 
sqloInvokeFnArgs 
sqlriInvokerTrusted__FP10sqlri_ufobP21sqlriRoutineErrorIntfb 
sqlriInvokeInvoker__FP10sqlri_ufobb 
sqlriutf__FP8sqlrr_cb 
sqlri_tfopn__FP8sqlrr_cbP9sqlri_tao 
sqlriopn__FP8sqlrr_cbP9sqlri_taoPi 
sqlriopn__FP8sqlrr_cbP9sqlri_taoPi@glue271 
sqlrita__FP8sqlrr_cb 
sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm 
sqlrr_process_fetch_request__FP14db2UCinterface 
sqlrr_open__FP14db2UCinterfaceP15db2UCCursorInfo 
sqljs_ddm_opnqry__FP14db2UCinterfaceP13sqljDDMObject 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface 
.sqljsParse.fdpr.clone.234__FP13sqljsDrdaAsCbP14db2UCinterfaceP8 
sqeAgentb 
@63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
@63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle 
@63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb 
sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T 
RunEDU__8sqeAgentFv 
EDUDriver__9sqzEDUObjFv 
sqloEDUEntry 
 
It can be verified by issuing the command ?lsusers ALL? to list 
all user names of the machine to check for user names that 
exceed 128 bytes or large number of users.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP11                                      * 
****************************************************************
Local Fix:
Increase AGENT_STACK_SZ to around 16MB and monitor for failure. 
As AGENT_STACK_SZ is measurable in 4K pages, the following 
command can increase to 16M. 
 
db2 update dbm cfg using agent_stack_sz 4096
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.12.2014
21.01.2016
21.01.2016
Problem solved at the following versions (IBM BugInfos)
9.7.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList