DB2 - Problem description
| Problem IC85307 | Status: Closed |
RUNNING ADMIN_GET_INDEX_INFO ON A TABLE THAT IS CURRENTLY RUNNIN G REDISTRIBUTE...DROP DBPARTITIONNUM(N) COULD RESULT IN A -901 | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
The -901 could occur if the timing of the two commands is such
that the request for index information is processed at the
database partition being dropped just after the table
information is removed from that partition.
2012-02-13-22.18.59.767522-300 I125017366E2703 LEVEL:
Severe
PID : 13271 TID : 140227477759744 KTID :
13690
PROC : db2sysc 3
FUNCTION: DB2 UDB, data management, sqldGetTablePools,
probe:14835
MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR
"non-severe dms programming error"
DIA8532C An internal processing error has occurred.
DATA #1 : String, 31 bytes
Table not found in object table
DATA #2 : String, 9 bytes
sqldtcb.C
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x00007F8955A5182E pdLog + 0x230
[1] 0x00007F895BC3FB7F sqlzSetAndLog901 + 0x47B
[2] 0x00007F89567300A2 _Z17sqldGetTablePoolsP8sqeAgentiiiPiS1_
+ 0x4E4
[3] 0x00007F89564EAB85
_Z14sqldCheckPoolsP8sqeAgentP14SQLP_LOCK_INFOiti + 0x25F
[4] 0x00007F89564ECB64
_Z13sqldLockTableP8sqeAgentP14SQLP_LOCK_INFOjti + 0xB20
[5] 0x00007F89564F1B9C
_Z19sqldLockTableFixTCBP8sqeAgenttthiiiimmiPciS1_iP14SQLP_LOCK_I
NFOPP8SQLD_TCBjj + 0xD88
[6] 0x00007F89566089FB
_Z29sqldLockAndFixTCBforTableDataP8sqeAgentP19SQLD_TABLE_DATA_RE
QtthtPP8SQLD_TCBP14SQLP_LOCK_INFO + 0x3BF
[7] 0x00007F89565FD7FD
_Z29sqldGetTableDataForPermOrTempP8sqeAgentP19SQLD_TABLE_DATA_RE
QP15SQLD_TABLE_DATAtthtm + 0x1F5
[8] 0x00007F89565FE531
_Z32sqldGetTableDataForDataPartitionP8sqeAgentP19SQLD_TABLE_DATA
_REQP15SQLD_TABLE_DATAP8SQLD_TCBtm + 0x221
[9] 0x00007F89565FEB32
_Z25sqldGetTableDataForGlobalP8sqeAgentP19SQLD_TABLE_DATA_REQP15
SQLD_TABLE_DATA + 0x53E
[10] 0x00007F89565FEF55
_Z16sqldGetTableDataP8sqeAgentP19SQLD_TABLE_DATA_REQP15SQLD_TABL
E_DATA + 0x135
[11] 0x00007F895ADB36DE
_Z8sqlrkrtcP8sqlrr_cbP13SQLR_RPC_DRTDP17SQLR_RPCRPLY_DRTD +
0x16E
[12] 0x00007F895AD88506
_Z20sqlrl_rpc_dms_routerP8sqlrr_cbP16sqlkdRqstRplyFmtiP15SQLR_RP
CMESSAGE + 0xEEC
[13] 0x00007F8959E0CA0B _Z16sqlrr_rpc_routerP8sqlrr_cb + 0x8A7
[14] 0x00007F8959E0B18A
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0x24D0
[15] 0x00007F89569E758B
/db2home/svtdbm2/sqllib/lib64/libdb2e.so.1 + 0x301858B
[16] 0x00007F89569E87B6 _Z21sqleProcessSubRequestP8sqeAgent +
0x352
[17] 0x00007F8956A4341A _ZN8sqeAgent6RunEDUEv + 0x3DA
[18] 0x00007F895BC3E650 _ZN9sqzEDUObj9EDUDriverEv + 0x17C
[19] 0x00007F895BC3E278 _Z10sqlzRunEDUPcj + 0x26
[20] 0x00007F89594C3F3F sqloEDUEntry + 0x971
[21] 0x0000003CF72077E1 /lib64/libpthread.so.0 + 0x77E1
[22] 0x0000003CF66E153D clone + 0x6D
2012-02-13-22.18.59.795131-300 I125020070E563 LEVEL:
Error
PID : 13271 TID : 140227477759744 KTID :
13690
FUNCTION: DB2 UDB, data management, sqldGetTablePools,
probe:14835
DATA #1 : unsigned integer, 4 bytes
12
DATA #2 : unsigned integer, 4 bytes
149 | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1.0.2. * **************************************************************** | |
| Local Fix: | |
Re-issue the SYSPROC.ADMIN_GET_INDEX_INFO command. There is no outage and if the SYSPROC.ADMIN_GET_INDEX_INFO command is issued again it will succeed. | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
| Solution | |
The problem is first fixed in DB2 version 10.1.0.2. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.07.2012 31.12.2012 31.12.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.2 |
|
| 10.5.0.2 |
|