|
Problem IC64086
|
Status: Closed |
RUNSTATS AGAINST A SYTEM CATALOG TABLE CAN CRASH THE INSTANCE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
After successfully migrating a v8 database to v9.5 instance,
running runstats command against a system catalog table can
crash the instance.
RUNSTATS ON TABLE SYSIBM.SYSCOMMENTS ON ALL COLUMNS AND SAMPLED
DETAILED
INDEXES ALL ALLOW WRITE ACCESS
DB20000I The RUNSTATS command completed successfully.
COMMIT WORK
DB20000I The SQL command completed successfully.
RUNSTATS ON TABLE SYSIBM.SYSCONSTDEP ON ALL COLUMNS AND SAMPLED
DETAILED
INDEXES ALL ALLOW WRITE ACCESS
SQL2310N The utility could not generate statistics. Error
"-1224" was
returned.
COMMIT WORK
SQL1024N A database connection does not exist. SQLSTATE=08003
db2diag.log snippet:
2009-06-25-17.20.35.738548-240 E36771A1341 LEVEL:
Critical
PID : 2740314 TID : 1801 PROC : db2sysc
INSTANCE: muralids NODE : 000 DB : CUSTOM
APPHDL : 0-7 APPID:
*LOCAL.muralids.090625212021
AUTHID : MURALIDS
EDUID : 1801 EDUNAME: db2agent (CUSTOM)
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred:
"Trap". The instance may have been shutdown as a result.
"Automatic" FODC
(First Occurrence Data Capture) has been invoked and diagnostic
information has been recorded in directory
"/home/muralids/sqllib/db2dump/FODC_Trap_2009-06-25-17.20.23.622
993/"
.
Please look in this directory for detailed evidence about what
happened and contact IBM support if necessary to diagnose the
problem.
DATA #1 : Signal Number Recieved, 4 bytes
11
DATA #2 : Siginfo, 64 bytes
0x070000000E409DC0 : 0000 000B 0000 0000 0000 0032 0000 0000
...........2....
0x070000000E409DD0 : 0000 0000 0000 0000 0700 0000 AFA2 9909
................
0x070000000E409DE0 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x070000000E409DF0 : 0000 0000 0000 0000 0000 0000 0000 0000
................
<snip>
Trap file info:
----------------
DB2 build information: DB2 v9.5.0.2 s080911 SQL09052
timestamp: 2009-06-25-17.20.23.624941
instance name: muralids.000
EDU name : db2agent (CUSTOM)
EDU ID : 1801
Signal #11
uname: S:AIX R:3 V:5 M:00CCCAFC4C00 N:p6db2serv
process id: 2740314
thread id : 1801 (0x709)
kthread id : 2281695
<snip>
<StackTrace>
-------Frame------ ------Function + Offset------
0x0900000066AD4068
sqlr_construct_new_pd__FP8sqlrr_cbPP8sqlrg_pdP10SQLD_TSTATi +
0xA30
0x0900000066B13C74
sqlr_update_catalogs__FP8sqlrr_cbP11sqlrrstringT2P10SQLD_TSTATiP
P10SQLD
ISTATPiPP8sqlrg_pdP5s
qlcaT5P14sqlrg_nodecardUsUiUl + 0x1200
0x0900000064954EB8
sqlrLocalRunstats__FP8sqlrr_cbP11sqlrrstringN22UcUsT6PP8sqlrg_pd
iN39P16s
qlrl_stats_colsPPsUiP
PUsT15_dT15_T6PP20sqlr_runstats_resultPsUlT23_N26CUiT15_lP17sqlr
lc_stats
_infoPCUc + 0x21BC
0x090000006687458C
sqlrrsta__FP8sqlrr_cbP11sqlrrstringN22UcT5P17sqlrl_stats_parmsPC
UcPs
+
0x19DC
0x0900000066B74CF4 sqlrr_runstats_DA__FP5sqldaP5sqlca + 0x978
0x09000000657F9210
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5
sqlca
+
0x58C
0x09000000648678D0 sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo +
0x458
0x0900000064867E68
sqljs_ddm_excsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0xA8
0x090000006473EC74
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interfac
e - 0x50 |
| Problem Summary: |
RUNSTATS AGAINST A SYTEM CATALOG TABLE CAN CRASH THE INSTANCE
WITH SQLR_CONSTRUCT_NEW_PD
ERROR DESCRIPTION:
After successfully migrating a v8 database to v9.5 instance,
running runstats command against a system catalog table can
crash the instance.
RUNSTATS ON TABLE SYSIBM.SYSCOMMENTS ON ALL COLUMNS AND SAMPLED
DETAILED
INDEXES ALL ALLOW WRITE ACCESS
DB20000I The RUNSTATS command completed successfully.
COMMIT WORK
DB20000I The SQL command completed successfully.
RUNSTATS ON TABLE SYSIBM.SYSCONSTDEP ON ALL COLUMNS AND SAMPLED
DETAILED
INDEXES ALL ALLOW WRITE ACCESS
SQL2310N The utility could not generate statistics. Error
"-1224" was
returned.
COMMIT WORK
SQL1024N A database connection does not exist. SQLSTATE=08003
db2diag.log snippet:
2009-06-25-17.20.35.738548-240 E36771A1341 LEVEL:
Critical
PID : 2740314 TID : 1801 PROC : db2sysc
INSTANCE: muralids NODE : 000 DB : CUSTOM
APPHDL : 0-7 APPID:
*LOCAL.muralids.090625212021
AUTHID : MURALIDS
EDUID : 1801 EDUNAME: db2agent (CUSTOM)
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred:
"Trap". The instance may have been shutdown as a result.
"Automatic" FODC
(First Occurrence Data Capture) has been invoked and diagnostic
information has been recorded in directory
"/home/muralids/sqllib/db2dump/FODC_Trap_2009-06-25-17.20.23.622
993/"
.
Please look in this directory for detailed evidence about what
happened and contact IBM support if necessary to diagnose the
problem.
DATA #1 : Signal Number Recieved, 4 bytes
11
DATA #2 : Siginfo, 64 bytes
0x070000000E409DC0 : 0000 000B 0000 0000 0000 0032 0000 0000
...........2....
0x070000000E409DD0 : 0000 0000 0000 0000 0700 0000 AFA2 9909
................
0x070000000E409DE0 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x070000000E409DF0 : 0000 0000 0000 0000 0000 0000 0000 0000
................
<snip>
Trap file info:
----------------
DB2 build information: DB2 v9.5.0.2 s080911 SQL09052
timestamp: 2009-06-25-17.20.23.624941
instance name: muralids.000
EDU name : db2agent (CUSTOM)
EDU ID : 1801
Signal #11
uname: S:AIX R:3 V:5 M:00CCCAFC4C00 N:p6db2serv
process id: 2740314
thread id : 1801 (0x709)
kthread id : 2281695
<snip>
<StackTrace>
-------Frame------ ------Function + Offset------
0x0900000066AD4068
sqlr_construct_new_pd__FP8sqlrr_cbPP8sqlrg_pdP10SQLD_TSTATi +
0xA30
0x0900000066B13C74
sqlr_update_catalogs__FP8sqlrr_cbP11sqlrrstringT2P10SQLD_TSTATiP
P10SQLD
ISTATPiPP8sqlrg_pdP5s
qlcaT5P14sqlrg_nodecardUsUiUl + 0x1200
0x0900000064954EB8
sqlrLocalRunstats__FP8sqlrr_cbP11sqlrrstringN22UcUsT6PP8sqlrg_pd
iN39P16s
qlrl_stats_colsPPsUiP
PUsT15_dT15_T6PP20sqlr_runstats_resultPsUlT23_N26CUiT15_lP17sqlr
lc_stats
_infoPCUc + 0x21BC
0x090000006687458C
sqlrrsta__FP8sqlrr_cbP11sqlrrstringN22UcT5P17sqlrl_stats_parmsPC
UcPs
+
0x19DC
0x0900000066B74CF4 sqlrr_runstats_DA__FP5sqldaP5sqlca + 0x978
0x09000000657F9210
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5
sqlca
+
0x58C
0x09000000648678D0 sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo +
0x458
0x0900000064867E68
sqljs_ddm_excsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0xA8
0x090000006473EC74
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface - 0x50 |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 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 |
First fixed in v9.7 FP1
Users Affected: ALL
Defect: wsdbu00564120 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.10.2009
31.12.2009
31.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
