|
Problem IC70608
|
Status: Closed |
CONCURRENTLY COMPILING QUERIES REFERENCING USER DEFINED FUNCTIONS MAY EXPERIENCE DEADLOCKS(SQL0911N-rc 68). |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
Sample queries accessing two different user-defined functions
(sample.demo1/sample.demo2), compiling at the same time which
lead to a deadlock.
-- select count(*) AS COUNT1 from
table(sample.demo1(20100601,2563,1)) as sam1
-- select count(*) AS COUNT2 from
table(sample.demo2(20100501,40,1)) as sam2
Deadlock information about the participants from the event
monitor log might look similar to the following:
Deadlock ID: 1
Participant no.: 2
Participant no. holding the lock: 1
Appl Id: 172.31.80.207.46801.10072611524
Appl Seq number: 00003
Appl Id of connection holding the lock:
172.31.80.207.56528.10072611513
Seq. no. of connection holding the lock: 00001
Lock wait start time: 07/26/2010 07:52:47.973473
Lock Name : 0x0000000105003D120000000052
Lock Attributes : 0x00000010
Release Flags : 0x80000000
Lock Count : 1
Hold Count : 0
Current Mode : none
Deadlock detection time: 07/26/2010 07:52:54.234412
Table of lock waited on : SYSROUTINES
Schema of lock waited on : SYSIBM
Data partition id for table : 0
Tablespace of lock waited on : SYSCATSPACE
Type of lock: Row
Mode of lock: U - Update
Mode application requested on lock: U - Update
====
Deadlock ID: 1
Participant no.: 1
Participant no. holding the lock: 2
Appl Id: 172.31.80.207.56528.10072611513
Appl Seq number: 00032
Appl Id of connection holding the lock:
172.31.80.207.46801.10072611524
Seq. no. of connection holding the lock: 00001
Lock wait start time: 07/26/2010 07:52:47.973425
Lock Name : 0x000000010600222D0000000052
Lock Attributes : 0x00000010
Release Flags : 0x80000000
Lock Count : 1
Hold Count : 0
Current Mode : none
Deadlock detection time: 07/26/2010 07:52:54.268655
Table of lock waited on : SYSROUTINES
Schema of lock waited on : SYSIBM
Data partition id for table : 0
Tablespace of lock waited on : SYSCATSPACE
Type of lock: Row
Mode of lock: U - Update
Mode application requested on lock: U - Update |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* USERS ON DB2 VERSION V9.1 FIXPACK-9 ONLY *
****************************************************************
* PROBLEM DESCRIPTION: *
* Incorrect locking protocols were introduced in Fix Pack-9 *
* that ends up causing concurrency issues when resolving *
* function names *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.1 Fix Pack 10. *
**************************************************************** |
| Local Fix: |
It is possible to get around the problem by re-arranging the
queries. |
| available fix packs: |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
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 |
First fixed in DB2 Version 9.1 Fix Pack 10. |
| Workaround |
N/A |
| Comment |
N/A |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.08.2010
09.02.2011
09.02.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.10
|
 |
