|
Problem IC63779
|
Status: Closed |
DURING FUNCTION RESOLUTION, IF WE HIT A SEVERE ERROR CONDITION WHILE TRYING TO LOOK UP A MODULE, THE ENGINE MIGHT TRAP. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
DB2 instance may trap if severe error such as lock time out or
dead
lock is encountered on catalog tables while running a function
For the instance to trap the error condition must happen while
DB2 is
trying to look up a module.
The call stack would show:
-------Frame------ ------Function + Offset------
0x090000003FFDFD80
sqlnq_findFn__FP12sqlnq_stringN21iPsP15sqlra_func_pathPUcPP9sqln
q_funPiT4P9sqlnq_pidP17sqlnn_dat_TYPTYPEP3locbsN314_
+ 0x4700
0x090000003FFE9BA0
sqlnq_resolveFn__FP9sqlnq_pidP12sqlnq_stringPUcPiP3locisT6 +
0x9C0
0x090000003F745EA4
sqlnq_fun_res_walk__FP9sqlnq_pidP12sqlnq_stringPUcPP9sqlnq_pidP3
lociT6
+ 0x8A4
0x090000003F7499BC
sqlnq_fun_tres__FP9sqlnq_pidP12sqlnq_stringPUcPP9sqlnq_pidP3loci
T6
+ 0x1BC
0x09000000400FBEA0
sqlnq_sem_function_call__FPP8stknode_i10actiontypePUcP3loc +
0x2A0
0x09000000400E2A30
sqlnq_resolve_as_function_name__FRbP9sqlnq_pidP5TokenRP9sqlnq_pi
dPUcP3loc
+ 0x4F0
0x090000004011C130 sqlnq_sem__FPP8stknode_i10actiontypePUcP3loc
+ 0x33B0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users that running functions under DB2 LUW v97 GA. *
****************************************************************
* PROBLEM DESCRIPTION: *
* During function resolution, if we hit a severe error *
* condition (e.g. lock time out or dead lock) while trying to *
* look up a module, we might end up trapping the engine. *
* *
* The call stack would show: *
* *
* -------Frame------ ------Function + Offset------ *
* 0x090000003FFDFD80 *
* sqlnq_findFn__FP12sqlnq_stringN21iPsP15sqlra_func_pathPUcPP9sq
* q_funPiT4P9sqlnq_pidP17sqlnn_dat_TYPTYPEP3locbsN314_ *
* + 0x4700 *
* 0x090000003FFE9BA0 *
* sqlnq_resolveFn__FP9sqlnq_pidP12sqlnq_stringPUcPiP3locisT6 + *
* *
* 0x9C0 *
* 0x090000003F745EA4 *
* sqlnq_fun_res_walk__FP9sqlnq_pidP12sqlnq_stringPUcPP9sqlnq_pid
* lociT6 *
* + 0x8A4 *
* 0x090000003F7499BC *
* sqlnq_fun_tres__FP9sqlnq_pidP12sqlnq_stringPUcPP9sqlnq_pidP3lo
* T6 *
* + 0x1BC *
* 0x09000000400FBEA0 *
* sqlnq_sem_function_call__FPP8stknode_i10actiontypePUcP3loc + *
* *
* 0x2A0 *
* 0x09000000400E2A30 *
* sqlnq_resolve_as_function_name__FRbP9sqlnq_pidP5TokenRP9sqlnq_
* dPUcP3loc *
* + 0x4F0 *
* 0x090000004011C130 *
* sqlnq_sem__FPP8stknode_i10actiontypePUcP3loc *
* + 0x33B0 *
* *
* The db2diag.log could have the following entries: *
* *
* 2009-10-11-22.50.03.409693-240 I5647488A593 LEVEL: *
* Error *
* PID : 1679504 TID : 14224 PROC : *
* db2sysc 0 *
* INSTANCE: svtdbm4 NODE : 000 DB : *
* PROTEUS *
* APPHDL : 0-126 APPID: *
* 127.0.0.1.41744.091012013013 *
* AUTHID : SVTDBM4 *
* EDUID : 14224 EDUNAME: db2agent (PROTEUS) 0 *
* FUNCTION: DB2 UDB, catalog services, *
* sqlrlCatalogScan::fetch, probe:40 *
* RETCODE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock *
* detected" *
* DIA8002C A deadlock has occurred, rolling back *
* transaction. *
* DATA #1 : Hex integer, 4 bytes *
* 0x0000000B *
* *
* 2009-10-11-22.50.03.410259-240 I5648082A551 LEVEL: *
* Error *
* PID : 1679504 TID : 14224 PROC : *
* db2sysc 0 *
* INSTANCE: svtdbm4 NODE : 000 DB : *
* PROTEUS *
* APPHDL : 0-126 APPID: *
* 127.0.0.1.41744.091012013013 *
* AUTHID : SVTDBM4 *
* EDUID : 14224 EDUNAME: db2agent (PROTEUS) 0 *
* FUNCTION: DB2 UDB, catalog services, sqlrlLookupModuleInfo, *
* probe:4146 *
* MESSAGE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock *
* detected" *
* DIA8002C A deadlock has occurred, rolling back *
* transaction. *
* *
* 2009-10-11-22.50.03.410675-240 I5648634A547 LEVEL: *
* Error *
* PID : 1679504 TID : 14224 PROC : *
* db2sysc 0 *
* INSTANCE: svtdbm4 NODE : 000 DB : *
* PROTEUS *
* APPHDL : 0-126 APPID: *
* 127.0.0.1.41744.091012013013 *
* AUTHID : SVTDBM4 *
* EDUID : 14224 EDUNAME: db2agent (PROTEUS) 0 *
* FUNCTION: DB2 UDB, catalog services, sqlrlLookupModule, *
* probe:3772 *
* MESSAGE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock *
* detected" *
* DIA8002C A deadlock has occurred, rolling back *
* transaction. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7.1 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 |
DB2 V9.7 fixpack 1
The customer will see the correct error being returned (-911) |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.10.2009
15.01.2010
15.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.1,
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
