|
Problem IC75597
|
Status: Closed |
DB2 instance crash in cases when Instance is experiencing lockin g issues and the SQL has XML column in SELECT list. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
DB2 instance could crash in cases when Instance is experiencing
locking issues (Failed lock excalations for example) and SQL
used has XML column in SELECT list, i.e. the conditions are
1. TABLE MUST HAVE XML (XML in SELECT list. Check the table's
definition for XML column.)
2. Encounter LOCKING ERRORs
Stack will look as following:
</Siginfo_t>
Signal #31 (SIGUSR2); si_code: 9 (SI_EMPTY:siginfo_t contains no
useful information.)
</SignalDetails>
......
sqle_panic
sqldInvCursorPos
sqldInvCursorPos
sqldEndTransaction
sqlrr_cleanup_tran_before_DPS
sqlrrbck
sqlrr_process_close_request
sqlrr_process_close_request
sqlrr_fetch_error
sqlrr_fetch
sqljs_ddm_cntqry
Symptoms of this problem will be as follows:
1. Lock errors will appear in db2diag.log. Example of Lock
Excalation failed:
2010-08-19-16.32.09.494621+600 E2882779A568 LEVEL: Error
PID : 1028104 TID : 53386 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-54691 APPID:
10.0.0.0.47992.100819024852
AUTHID : AUTHID01
EDUID : 53386 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, data management, sqldEscalateLocks, probe:4
MESSAGE : ADM5503E The escalation of "24" locks on table
"VAR01.TABLETB_ITEM" to lock intent "S" has failed. The SQLCODE
is "-911".
2. 901 in db2diag.log with "sqlricls_complex: unexpected
non-NULL table->handle " diagnostic message:
2010-08-19-16.32.10.001219+600 I2887234A882 LEVEL: Severe
PID : 1028104 TID : 56173 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-55870 APPID:
10.0.0.0.35026.100819063145
AUTHID : AUTHID01
EDUID : 56173 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:300
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 51
sqlerrmc: sqlricls_complex: unexpected non-NULL table->handle
sqlerrp : SQLRI1B8
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0xFFFFF503 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
3. Diagnostic message will appear with debug information about
an open scan on the permanent table:
2010-08-19-16.32.10.248626+600 I2946467A531 LEVEL: Severe
PID : 1028104 TID : 56173 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-55870 APPID:
10.0.0.0.35026.100819063145
AUTHID : AUTHID01
EDUID : 56173 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary
logging fu, Probe:0
MESSAGE : SQLD_CCB:
DATA #1 : String, 52 bytes
pool(TID)=24, obj(FID)=7447, indexid(IID)=3, class=0
2010-08-19-16.32.10.255504+600 I2948798A532 LEVEL: Severe
PID : 1028104 TID : 56173 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-55870 APPID:
10.0.0.0.35026.100819063145
AUTHID : AUTHID01
EDUID : 56173 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary
logging fu, probe:0
MESSAGE : SQLD_TCB:
DATA #1 : String, 52 bytes
Perm Table(24:7447)=VAR01 .BTX_ASSISTANCE_PROVIDER
At this point instance will Panic.
Detailed Stack:
The stack looks like:
</Siginfo_t>
Signal #31 (SIGUSR2); si_code: 9 (SI_EMPTY:siginfo_t contains no
useful information.)
</SignalDetails>
......
<StackTrace>
------Function + Offset------
pthread_kill + 0x88
_p_raise + 0x68
raise + 0x34
abort + 0xB4
abort@glue74C + 0x94
sqloExitEDU + 0xA0
sqle_panic__Fv + 0x17C
sqldInvCursorPos__FP8sqeAgenti + 0x2B0
sqldInvCursorPos__FP8sqeAgenti@glue2CA + 0x7C
sqldEndTransaction__FP8sqeAgenti + 0x1D4
sqlrr_cleanup_tran_before_DPS__FP8sqlrr_cbiN62PiT9b + 0x3EC
sqlrrbck__FP8sqlrr_cbiN32P15SQLXA_CALL_INFO + 0xA40
sqlrrbck__FP8sqlrr_cbiN32P15SQLXA_CALL_INFO@glueB65 + 0x84
sqlrr_process_close_request__FP8sqlrr_cbiN32 + 0x200
sqlrr_process_close_request__FP8sqlrr_cbiN32@glue1015 + 0x84
sqlrr_fetch_error__FP8sqlrr_cbP14db2UCinterfaceP15db2UCCursorInf
oiT4@glueD98
+ 0x538
sqlrr_fetch__FP14db2UCinterfaceP15db2UCCursorInfo + 0x58
sqljs_ddm_cntqry__FP14db2UCinterfaceP13sqljDDMObject + 0x9E8
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface
+ 0x164
.sqljsParse.fdpr.clone.624__FP13sqljsDrdaAsCbP14db2UCinterface +
0x330
@64@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x3CC
@64@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4
@64@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x2B0
sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0xFC
RunEDU__8sqeAgentFv + 0x80
EDUDriver__9sqzEDUObjFv + 0xE4
sqloEDUEntry + 0x264
</StackTrace> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All. *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2 instance crash in cases when Instance is experiencing *
* lockin issues and the SQL has XML column in SELECT list. *
* *
* *
* DB2 instance could crash in cases when Instance is *
* experiencing locking issues (Failed lock excalations for *
* example) and SQL used has XML column in SELECT list, i.e. *
* the conditions are *
* *
* 1. TABLE MUST HAVE XML (XML in SELECT list. Check the *
* table's definition for XML column.) *
* 2. Encounter LOCKING ERRORs *
* *
* Stack will look as following: *
* </Siginfo_t> *
* Signal #31 (SIGUSR2); si_code: 9 (SI_EMPTY:siginfo_t *
* contains no useful information.) *
* </SignalDetails> *
* ...... *
* sqle_panic *
* sqldInvCursorPos *
* sqldInvCursorPos *
* sqldEndTransaction *
* sqlrr_cleanup_tran_before_DPS *
* sqlrrbck *
* sqlrr_process_close_request *
* sqlrr_process_close_request *
* sqlrr_fetch_error *
* sqlrr_fetch *
* sqljs_ddm_cntqry *
* *
* *
* Symptoms of this problem will be as follows: *
* *
* 1. Lock errors will appear in db2diag.log. Example of Lock *
* Excalation failed: *
* *
* 2010-08-19-16.32.09.494621+600 E2882779A568 LEVEL: *
* Error *
* PID : 1028104 TID : 53386 PROC : *
* db2sysc 0 *
* INSTANCE: db2inst1 NODE : 000 DB : *
* SAMPLE *
* APPHDL : 0-54691 APPID: *
* 10.0.0.0.47992.100819024852 *
* AUTHID : AUTHID01 *
* EDUID : 53386 EDUNAME: db2agent (SAMPLE) 0 *
* FUNCTION: DB2 UDB, data management, sqldEscalateLocks, *
* probe:4 *
* MESSAGE : ADM5503E The escalation of "24" locks on table *
* "VAR01.TABLETB_ITEM" to lock intent "S" has failed. The *
* SQLCODE *
* is "-911". *
* *
* 2. 901 in db2diag.log with "sqlricls_complex: unexpected *
* non-NULL table->handle " diagnostic message: *
* *
* 2010-08-19-16.32.10.001219+600 I2887234A882 LEVEL: *
* Severe *
* PID : 1028104 TID : 56173 PROC : *
* db2sysc 0 *
* INSTANCE: db2inst1 NODE : 000 DB : *
* SAMPLE *
* APPHDL : 0-55870 APPID: *
* 10.0.0.0.35026.100819063145 *
* AUTHID : AUTHID01 *
* EDUID : 56173 EDUNAME: db2agent (SAMPLE) 0 *
* FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, *
* probe:300 *
* DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes *
* sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 51 *
* sqlerrmc: sqlricls_complex: unexpected non-NULL *
* table->handle *
* sqlerrp : SQLRI1B8 *
* sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) *
* 0x00000000 *
* (4) 0x00000000 (5) 0xFFFFF503 (6) *
* 0x00000000 *
* sqlwarn : (1) (2) (3) (4) (5) (6) *
* *
* (7) (8) (9) (10) (11) *
* sqlstate: *
* *
* 3. Diagnostic message will appear with debug information *
* about *
* an open scan on the permanent table: *
* *
* 2010-08-19-16.32.10.248626+600 I2946467A531 LEVEL: *
* Severe *
* PID : 1028104 TID : 56173 PROC : *
* db2sysc 0 *
* INSTANCE: db2inst1 NODE : 000 DB : *
* SAMPLE *
* APPHDL : 0-55870 APPID: *
* 10.0.0.0.35026.100819063145 *
* AUTHID : AUTHID01 *
* EDUID : 56173 EDUNAME: db2agent (SAMPLE) 0 *
* FUNCTION: DB2 UDB, trace services, sqlt_logerr_string *
* (secondary *
* logging fu, Probe:0 *
* MESSAGE : SQLD_CCB: *
* DATA #1 : String, 52 bytes *
* pool(TID)=24, obj(FID)=7447, indexid(IID)=3, class=0 *
* *
* 2010-08-19-16.32.10.255504+600 I2948798A532 LEVEL: *
* Severe *
* PID : 1028104 TID : 56173 PROC : *
* db2sysc 0 *
* INSTANCE: db2inst1 NODE : 000 DB : *
* SAMPLE *
* APPHDL : 0-55870 APPID: *
* 10.0.0.0.35026.100819063145 *
* AUTHID : AUTHID01 *
* EDUID : 56173 EDUNAME: db2agent (SAMPLE) 0 *
* FUNCTION: DB2 UDB, trace services, sqlt_logerr_string *
* (secondary *
* logging fu, probe:0 *
* MESSAGE : SQLD_TCB: *
* DATA #1 : String, 52 bytes *
* Perm Table(24:7447)=VAR01 .BTX_ASSISTANCE_PROVIDER *
* *
* At this point instance will Panic. *
* Detailed Stack: *
* *
* The stack looks like: *
* </Siginfo_t> *
* Signal #31 (SIGUSR2); si_code: 9 (SI_EMPTY:siginfo_t *
* contains no useful information.) *
* </SignalDetails> *
* ...... *
* <StackTrace> *
* ------Function + Offset------ *
* pthread_kill + 0x88 *
* _p_raise + 0x68 *
* raise + 0x34 *
* abort + 0xB4 *
* abort@glue74C + 0x94 *
* sqloExitEDU + 0xA0 *
* sqle_panic__Fv + 0x17C *
* sqldInvCursorPos__FP8sqeAgenti + 0x2B0 *
* sqldInvCursorPos__FP8sqeAgenti@glue2CA + 0x7C *
* sqldEndTransaction__FP8sqeAgenti + 0x1D4 *
* sqlrr_cleanup_tran_before_DPS__FP8sqlrr_cbiN62PiT9b + 0x3EC *
* sqlrrbck__FP8sqlrr_cbiN32P15SQLXA_CALL_INFO + 0xA40 *
* sqlrrbck__FP8sqlrr_cbiN32P15SQLXA_CALL_INFO@glueB65 + 0x84 *
* sqlrr_process_close_request__FP8sqlrr_cbiN32 + 0x200 *
* sqlrr_process_close_request__FP8sqlrr_cbiN32@glue1015 + 0x84 *
* sqlrr_fetch_error__FP8sqlrr_cbP14db2UCinterfaceP15db2UCCursorI
* + 0x538 *
* sqlrr_fetch__FP14db2UCinterfaceP15db2UCCursorInfo + 0x58 *
* sqljs_ddm_cntqry__FP14db2UCinterfaceP13sqljDDMObject + 0x9E8 *
* sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2
* + 0x164 *
* .sqljsParse.fdpr.clone.624__FP13sqljsDrdaAsCbP14db2UCinterface
* + 0x330 *
* @64@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x3CC *
* @64@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4 *
* @64@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x2B0 *
* sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0xFC *
* RunEDU__8sqeAgentFv + 0x80 *
* EDUDriver__9sqzEDUObjFv + 0xE4 *
* sqloEDUEntry + 0x264 *
* </StackTrace> *
****************************************************************
* RECOMMENDATION: *
* Update to version 9.5 fixpack 8 or later fixpack. *
**************************************************************** |
| Local Fix: |
Please, use LOCKLIST AUTOMATIC and make sure that there is
enough instance memory. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
This problem is first fixed in version 9.5 fixpack 8. |
| Workaround |
Please, use LOCKLIST AUTOMATIC and make sure that there is
enough instance memory. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.04.2011
27.06.2011
27.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
