|
Problem IC65838
|
Status: Closed |
EXTENT MOVEMENT FAILS WITH SQLE_RC_DUP_TASK_ID "THIS TASK ID ALREADY EXISTS" |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A single DB2 UDB instance contains multiple databases. On each
such database there has been an operation requiring an extent
movement, for example a new container has been added to a
tablespace. If the respective extent movement operations start
at around same time, and if the tablespaces where the extent
movement is about to begin share the same tablespace ID, the
extent movement may fail with an SQLE_RC_DUP_TASK_ID error
reported by "sqlbSpawnExtentMovementIcoord, probe:5015",
indicating that a duplicate extent movement task has been
submitted. A sample db2diag.log message:
2009-12-03-14.57.12.915728-300 I251906E516 LEVEL: Severe
PID : 18874 TID : 479610986765 PROC :
db2sysc
INSTANCE: db2inst1 NODE: 000 DB : SAMPLE
APPHDL : 0-266 APPID:
*LOCAL.db2inst1.091203195635
AUTHID : DB2INST1
EDUID : 168 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, buffer pool services,
sqlbSpawnExtentMovementIcoord, probe:5015
MESSAGE : ZRC=0x80050153=-2147155629=SQLE_RC_DUP_TASK_ID
"This task ID already exists"
This is a timing dependent error. The fundamental problem is
that extent movement tasks are currently using an identifier
that is not sufficiently unique. The purpose is to improve the
design of the task identifier. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* see APAR description *
****************************************************************
* RECOMMENDATION: *
* Problem first fixed in DB2 UDB 9.7 FixPak 2. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 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 9a 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 |
see APAR description |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.01.2010
13.05.2010
13.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
