|
Problem IC72104
|
Status: Closed |
INSTANCE CRASH FOR MISSING SORT FILE |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
Error Description:
DB2 instance can crash due DB marked bad message as a result of
improper error handling. The stack trace for the problem may
look like the following: -902 error and may have a stack trace
like the following:
<StackTrace>
sqloCrashOnCriticalMemoryValidationFailure
sqloCrashOnCriticalMemoryValidationFailure@glue1E8
sqlofmblkEx
sqldTermApplication
sqlesrsp
sqlesrspWrp
sqleUCagentConnectReset + 0xA0
sqljsCleanup
sqljsDrdaAsInnerDriver
sqljsDrdaAsDriver
sqleRunAgent
In addition to "DB Marked Bad" errors you may see the
db2diag.log messages similar to the following:
2009-09-30-13.36.50.901110-420 I268486A536 LEVEL: Error
PID : 1286386 TID : 1 PROC : db2agent (PROD9) 0
INSTANCE: inst1 NODE : 000 DB : dbname
APPHDL : 0-3780 APPID: XXXXXXXX.ID08.01C700203835
AUTHID : userid
FUNCTION: DB2 UDB, access plan manager, sqlracal, probe:12
RETCODE : ZRC=0x87130055=-2028797867=SQLS_PRGERR
"A data management services programming error occurred."
DIA8576C A data management services programming error occurred.
>><<
And that is why:
2009-09-30-13.36.50.901852-420 I269023A470 LEVEL: Error
PID : 1286386 TID : 1 PROC : db2agent (PROD9) 0
INSTANCE: inst1 NODE : 000 DB : dbname
APPHDL : 0-3780 APPID: XXXXXXXX.ID08.01C700203835
AUTHID : userid
FUNCTION: DB2 UDB, access plan manager, sqlracal, probe:999
MESSAGE : Error on rollback
DATA #1 : Hexdump, 2 bytes
0x0000000110052858 : 0004 ..
2009-09-30-13.36.50.902493-420 I269494A768 LEVEL: Error
PID : 1286386 TID : 1 PROC : db2agent (PROD9) 0
INSTANCE: inst1 NODE : 000 DB : dbname
APPHDL : 0-3780 APPID: XXXXXXXX.ID08.01C700203835
AUTHID : userid
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 2 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* N/A *
****************************************************************
* PROBLEM DESCRIPTION: *
* Error Description: *
* *
* DB2 instance can crash due DB marked bad message as a result *
* of *
* improper error handling. The stack trace for the problem *
* may *
* look like the following: -902 error and may have a stack *
* trace *
* like the following: *
* *
* <StackTrace> *
* *
* sqloCrashOnCriticalMemoryValidationFailure *
* sqloCrashOnCriticalMemoryValidationFailure@glue1E8 *
* sqlofmblkEx *
* sqldTermApplication *
* sqlesrsp *
* sqlesrspWrp *
* sqleUCagentConnectReset + 0xA0 *
* sqljsCleanup *
* sqljsDrdaAsInnerDriver *
* sqljsDrdaAsDriver *
* sqleRunAgent *
* *
* In addition to "DB Marked Bad" errors you may see the *
* db2diag.log messages similar to the following *
* *
* 2009-09-30-13.36.50.901110-420 I268486A536 LEVEL: Error *
* PID : 1286386 TID : 1 PROC : db2agent (PROD9) *
* INSTANCE: inst1 NODE : 000 DB : dbname *
* APPHDL : 0-3780 APPID: XXXXXXXX.ID08.01C700203835 *
* AUTHID : userid *
* FUNCTION: DB2 UDB, access plan manager, sqlracal, probe:12 *
* RETCODE : ZRC=0x87130055=-2028797867=SQLS_PRGERR *
* "A data management services programming error occurred." *
* DIA8576C A data management services programming error *
* occurred. *
* *
* >><< *
* *
* And that is why: *
* *
* 2009-09-30-13.36.50.901852-420 I269023A470 LEVEL: Error *
* PID : 1286386 TID : 1 PROC : db2agent (PROD9) 0 *
* INSTANCE: inst1 NODE : 000 DB : dbname *
* APPHDL : 0-3780 APPID: XXXXXXXX.ID08.01C700203835 *
* AUTHID : userid *
* FUNCTION: DB2 UDB, access plan manager, sqlracal, probe:999 *
* MESSAGE : Error on rollback *
* DATA #1 : Hexdump, 2 bytes *
* 0x0000000110052858 : 0004 .. *
* *
* 2009-09-30-13.36.50.902493-420 I269494A768 LEVEL: Error *
* PID : 1286386 TID : 1 PROC : db2agent (PROD9) 0 *
* INSTANCE: inst1 NODE : 000 DB : dbname *
* APPHDL : 0-3780 APPID: XXXXXXXX.ID08.01C700203835 *
* AUTHID : userid *
* FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 *
* DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes *
* sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 2 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.5 Fix Pack 8 *
**************************************************************** |
| Local Fix: |
Not applicable |
| 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 |
Fixed in DB2 Version 9.5 Fix Pack 8 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.10.2010
16.07.2011
16.07.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
|
 |
