|
Problem IC62977
|
Status: Closed |
INSTANCE PANIC WHILE ACTIVATING DATABASE WITH DB CFG AUTO_STATS_PROF TURNED ON AND SYSTOOLS.POLICY TABLES CREATED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If a database contains SYSTOOLS.POLICY table and its
configuration AUTO_STATS_PROF is turned on, the "activate db"
command against the database will fail with the following
message:
SQL1224N The database manager is not able to accept new
requests, has
terminated all requests in progress, or has terminated the
specified request
because of an error or a forced interrupt. SQLSTATE=55032
Snippet of db2diag.log :
+45255 2009-08-07-11.19.20.628904-240 I1655710A1509 LEVEL:
Severe
+45256 PID : 286858 TID : 2085 PROC :
db2sysc
+45257 INSTANCE: svtdbm4 NODE : 000 DB :
SCOB4
+45258 APPHDL : 0-9 APPID:
*LOCAL.svtdbm4.090807151904
+45259 AUTHID : SVTDBM4
+45260 EDUID : 2085 EDUNAME: db2agent (SCOB4)
+45261 FUNCTION: DB2 UDB, global services, sqlzAssertFailed,
probe:10
+45262 DATA #1 : String, 114 bytes
+45263 ASSERTION FAILED!!!
+45264 ASSERTION EXPRESSION: 0 != versionTimes
+45265 SOURCE FILENAME: sqlrlc_systables.C
+45266 LINE NUMBER: 1787
+45267 CALLSTCK:
+45268 [0] 0x0900000012D6A5D8 pdLog + 0x1D8
+45269 [1] 0x0900000012D3D39C sqlzAssertFailedValist + 0x25C
+45270 [2] 0x0900000012D3D484 sqlzAssertFailed + 0x64
+45271 [3] 0x09000000134F1224
sqlrlc_systables_fetch_from_disk__FP8sqlrr_cbPUcUsT2T3UiN26P13SQ
LO_MEM_POOLP21sqlrlc_systabl
es_infoP8SQLZ_RIDPUi + 0x1904
+45272 [4] 0x0900000014C88C10
sqlrlc_systables_load_entry__FP8sqlrr_cbP22sqlrlc_entry_systable
sUiN23PUi
+ 0x2B0
+45273 [5] 0x0900000014C89378
sqlrlc_load_entry__FP8sqlrr_cbP19sqlrlc_entry_commonUiN23PUi +
0x198
+45274 [6] 0x0900000014C81260
sqlrlc_request_ulock__FP8sqlrr_cbP19sqlrlc_entry_commonP20sqlrlc
_anchor_commonPbUiN25PUiP14S
QLP_LOCK_INFOT8 + 0x440
+45275 [7] 0x0900000014C83C7C
sqlrlc_find_request_usage_lock__FP8sqlrr_cbP10sqlrlc_keyUiN23PP1
9sqlrlc_entry_commonPUiP14SQ
LP_LOCK_INFO + 0x47C
+45276 [8] 0x09000000134F3898
sqlrlc_systables_fetch__FP8sqlrr_cbPUcUsT2T3UiN26P13SQLO_MEM_POO
LP14SQLP_LOCK_INFOP21sqlrlc_
systables_info + 0xB18
+45277 [9] 0x0900000013DCD2E0 sqlpiGetPolicy + 0x200
+45278
+45279 2009-08-07-11.19.20.643690-240 E1657220A928 LEVEL:
Critical
+45280 PID : 286858 TID : 2085 PROC :
db2sysc
+45281 INSTANCE: svtdbm4 NODE : 000 DB :
SCOB4
+45282 APPHDL : 0-9 APPID:
*LOCAL.svtdbm4.090807151904
+45283 AUTHID : SVTDBM4
+45284 EDUID : 2085 EDUNAME: db2agent (SCOB4)
+45285 FUNCTION: DB2 UDB, base sys utilities, sqle_panic,
probe:10
+45286 MESSAGE : ADM14001C An unexpected and critical error
has occurred: "Panic".
+45287 The instance may have been shutdown as a
result. "Automatic" FODC
+45288 (First Occurrence Data Capture) has been
invoked and diagnostic
+45289 information has been recorded in directory
+45290
"/home/svtdbm4/sqllib/db2dump/FODC_Panic_2009-08-07-11.19.20.630
386/"
+45291 . Please look in this directory for detailed
evidence about what
+45292 happened and contact IBM support if necessary
to diagnose the
+45293 problem.
+45294
+45735 2009-08-07-11.19.20.804243-240 I1681131A527 LEVEL:
Severe
+45736 PID : 286858 TID : 2085 PROC :
db2sysc
+45737 INSTANCE: svtdbm4 NODE : 000 DB :
SCOB4
+45738 APPHDL : 0-9 APPID:
*LOCAL.svtdbm4.090807151904
+45739 AUTHID : SVTDBM4
+45740 EDUID : 2085 EDUNAME: db2agent (SCOB4)
+45741 FUNCTION: DB2 UDB, base sys utilities, sqle_panic,
probe:10
+45742 MESSAGE : sqle_panic: Panic/sleep =
+45743 DATA #1 : Hexdump, 4 bytes
+45744 0x07800000002A0224 : 0DB2 CAFE
....
+45745
+45746 2009-08-07-11.19.20.805099-240 E1681659A665 LEVEL:
Severe
+45747 PID : 286858 TID : 2085 PROC :
db2sysc
+45748 INSTANCE: svtdbm4 NODE : 000 DB :
SCOB4
+45749 APPHDL : 0-9 APPID:
*LOCAL.svtdbm4.090807151904
+45750 AUTHID : SVTDBM4
+45751 EDUID : 2085 EDUNAME: db2agent (SCOB4)
+45752 FUNCTION: DB2 UDB, oper system services,
sqloSleepInstance, probe:38
+45753 MESSAGE : ADM0504C An unexpected internal processing
error has occurred. All
+45754 DB2 processes associated with this instance
have been suspended.
+45755 Diagnostic information has been recorded.
Contact IBM Support for
+45756 further assistance.
<StackTrace>
-------Frame------ ------Function + Offset------
0x090000000054E470 pthread_kill + 0xB0
0x0900000012E546B4 sqloDumpEDU + 0x94
0x0900000012D00E08 sqle_panic__Fv + 0xA8
0x0900000012D0106C sqle_trap__Fv + 0xC
0x0900000012D3D3B0 sqlzAssertFailedValist + 0x270
0x0900000012D3D484 sqlzAssertFailed + 0x64
0x09000000134F1224
sqlrlc_systables_fetch_from_disk__FP8sqlrr_cbPUcUsT2T3UiN26P13SQ
LO_MEM_POOLP21sqlrlc_systables_infoP8SQLZ_
RIDPUi + 0x1904
0x0900000014C88C10
sqlrlc_systables_load_entry__FP8sqlrr_cbP22sqlrlc_entry_systable
sUiN23PUi
+ 0x2B0
0x0900000014C89378
sqlrlc_load_entry__FP8sqlrr_cbP19sqlrlc_entry_commonUiN23PUi +
0x198
0x0900000014C81260
sqlrlc_request_ulock__FP8sqlrr_cbP19sqlrlc_entry_commonP20sqlrlc
_anchor_commonPbUiN25PUiP14SQLP_LOCK_INFOT
8 + 0x440
0x0900000014C83C7C
sqlrlc_find_request_usage_lock__FP8sqlrr_cbP10sqlrlc_keyUiN23PP1
9sqlrlc_entry_commonPUiP14SQLP_LOCK_INFO
+
0x47C
0x09000000134F3898
sqlrlc_systables_fetch__FP8sqlrr_cbPUcUsT2T3UiN26P13SQLO_MEM_POO
LP14SQLP_LOCK_INFOP21sqlrlc_systables_info
+ 0xB18
0x0900000013DCD2E0 sqlpiGetPolicy + 0x200
0x0900000013DCB560 sqlpiGetStatsProfile + 0xE0
0x0900000013DB421C sqlrr_readAutonomicPolicies__FP8sqlrr_cb +
0x1BC
0x0900000013DC7308 sqlrr_appl_init__FP8sqeAgentP5sqlca + 0x1B68
0x090000001319184C
InitEngineComponents__14sqeApplicationFcP8sqeAgentP8SQLE_BWAP5sq
lcaP22SQLESRSU_STATUS_VECTORT1
+ 0xC2C
0x09000000131951BC
AppStartUsing__14sqeApplicationFP8SQLE_BWAP8sqeAgentcT3P5sqlcaPc
+ 0xA5C
0x09000000131958B4
sqleProcessConnectType__FP14db2UCinterfaceP8SQLE_BWAP8sqeAgentP5
sqlcaP22SQLELOST_STATUS_VECTOR
+ 0x214
0x09000000131980A0
AppLocalStart__14sqeApplicationFP14db2UCinterface + 0x4A0
0x09000000131717AC sqlelostWrp__FP14db2UCinterface + 0x4C
0x09000000131738F0 sqleUCengnInit__FP14db2UCinterfaceUs + 0x4F0
0x090000001317957C sqleUCagentConnect + 0x137C
0x09000000149B1244
sqljsConnectAttach__FP13sqljsDrdaAsCbP14db2UCinterface + 0x224
0x09000000149E762C
sqljs_ddm_accsec__FP14db2UCinterfaceP13sqljDDMObject + 0x14C
0x0900000014A5C94C
sqljsParseConnect__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCinte
rface
+ 0x14C
0x0900000014A5AF1C
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterface + 0x1FC
0x0900000014A1D854 sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb +
0x494
0x0900000014A1F69C
sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x15C
0x0900000014A26660
sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x460
0x0900000014A286DC sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T +
0x23C
0x0900000012F65D8C RunEDU__8sqeAgentFv + 0x3AC
0x0900000012F558FC EDUDriver__9sqzEDUObjFv + 0x19C
0x0900000012F55C1C sqlzRunEDU__FPcUi + 0x3C
0x0900000012E5CBA4 sqloEDUEntry + 0x6A4
</StackTrace> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all DB2 Version 9.7 GA on Linux, Unix and Windows platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* If a database contains SYSTOOLS.POLICY table and its *
* configuration AUTO_STATS_PROF is turned on, the "activate *
* db" command against the database will fail with the *
* following message: *
* SQL1224N The database manager is not able to accept new *
* requests, has *
* terminated all requests in progress, or has terminated the *
* specified request *
* because of an error or a forced interrupt. SQLSTATE=55032 *
* *
* *
* Snippet of db2diag.log : *
* *
* +45255 2009-08-07-11.19.20.628904-240 I1655710A1509 *
* LEVEL: Severe *
* +45256 PID : 286858 TID : 2085 *
* PROC : db2sysc *
* +45257 INSTANCE: svtdbm4 NODE : 000 DB *
* : SCOB4 *
* +45258 APPHDL : 0-9 APPID: *
* *LOCAL.svtdbm4.090807151904 *
* +45259 AUTHID : SVTDBM4 *
* +45260 EDUID : 2085 EDUNAME: db2agent *
* (SCOB4) *
* +45261 FUNCTION: DB2 UDB, global services, *
* sqlzAssertFailed, probe:10 *
* +45262 DATA #1 : String, 114 bytes *
* +45263 ASSERTION FAILED!!! *
* +45264 ASSERTION EXPRESSION: 0 != versionTimes *
* +45265 SOURCE FILENAME: sqlrlc_systables.C *
* +45266 LINE NUMBER: 1787 *
* +45267 CALLSTCK: *
* +45268 [0] 0x0900000012D6A5D8 pdLog + 0x1D8 *
* +45269 [1] 0x0900000012D3D39C sqlzAssertFailedValist + *
* 0x25C *
* +45270 [2] 0x0900000012D3D484 sqlzAssertFailed + 0x64 *
* +45271 [3] 0x09000000134F1224 *
* sqlrlc_systables_fetch_from_disk__FP8sqlrr_cbPUcUsT2T3UiN26P13
* es_infoP8SQLZ_RIDPUi + 0x1904 *
* +45272 [4] 0x0900000014C88C10 *
* sqlrlc_systables_load_entry__FP8sqlrr_cbP22sqlrlc_entry_systab
* + 0x2B0 *
* +45273 [5] 0x0900000014C89378 *
* sqlrlc_load_entry__FP8sqlrr_cbP19sqlrlc_entry_commonUiN23PUi *
* + 0x198 *
* +45274 [6] 0x0900000014C81260 *
* sqlrlc_request_ulock__FP8sqlrr_cbP19sqlrlc_entry_commonP20sqlr
* QLP_LOCK_INFOT8 + 0x440 *
* +45275 [7] 0x0900000014C83C7C *
* sqlrlc_find_request_usage_lock__FP8sqlrr_cbP10sqlrlc_keyUiN23P
* LP_LOCK_INFO + 0x47C *
* +45276 [8] 0x09000000134F3898 *
* sqlrlc_systables_fetch__FP8sqlrr_cbPUcUsT2T3UiN26P13SQLO_MEM_P
* systables_info + 0xB18 *
* +45277 [9] 0x0900000013DCD2E0 sqlpiGetPolicy + 0x200 *
* +45278 *
* +45279 2009-08-07-11.19.20.643690-240 E1657220A928 *
* LEVEL: Critical *
* +45280 PID : 286858 TID : 2085 *
* PROC : db2sysc *
* +45281 INSTANCE: svtdbm4 NODE : 000 DB *
* : SCOB4 *
* +45282 APPHDL : 0-9 APPID: *
* *LOCAL.svtdbm4.090807151904 *
* +45283 AUTHID : SVTDBM4 *
* +45284 EDUID : 2085 EDUNAME: db2agent *
* (SCOB4) *
* +45285 FUNCTION: DB2 UDB, base sys utilities, sqle_panic, *
* probe:10 *
* +45286 MESSAGE : ADM14001C An unexpected and critical *
* error has occurred: "Panic". *
* +45287 The instance may have been shutdown as a *
* result. "Automatic" FODC *
* +45288 (First Occurrence Data Capture) has been *
* invoked and diagnostic *
* +45289 information has been recorded in directory *
* +45290 *
* "/home/svtdbm4/sqllib/db2dump/FODC_Panic_2009-08-07-11.19.20.6
* +45291 . Please look in this directory for *
* detailed evidence about what *
* +45292 happened and contact IBM support if *
* necessary to diagnose the *
* +45293 problem. *
* +45294 *
* *
* +45735 2009-08-07-11.19.20.804243-240 I1681131A527 *
* LEVEL: Severe *
* +45736 PID : 286858 TID : 2085 *
* PROC : db2sysc *
* +45737 INSTANCE: svtdbm4 NODE : 000 DB *
* : SCOB4 *
* +45738 APPHDL : 0-9 APPID: *
* *LOCAL.svtdbm4.090807151904 *
* +45739 AUTHID : SVTDBM4 *
* +45740 EDUID : 2085 EDUNAME: db2agent *
* (SCOB4) *
* +45741 FUNCTION: DB2 UDB, base sys utilities, sqle_panic, *
* probe:10 *
* +45742 MESSAGE : sqle_panic: Panic/sleep = *
* +45743 DATA #1 : Hexdump, 4 bytes *
* +45744 0x07800000002A0224 : 0DB2 CAFE *
* .... *
* +45745 *
* +45746 2009-08-07-11.19.20.805099-240 E1681659A665 *
* LEVEL: Severe *
* +45747 PID : 286858 TID : 2085 *
* PROC : db2sysc *
* +45748 INSTANCE: svtdbm4 NODE : 000 DB *
* : SCOB4 *
* +45749 APPHDL : 0-9 APPID: *
* *LOCAL.svtdbm4.090807151904 *
* +45750 AUTHID : SVTDBM4 *
* +45751 EDUID : 2085 EDUNAME: db2agent *
* (SCOB4) *
* +45752 FUNCTION: DB2 UDB, oper system services, *
* sqloSleepInstance, probe:38 *
* +45753 MESSAGE : ADM0504C An unexpected internal *
* processing error has occurred. All *
* +45754 DB2 processes associated with this *
* instance have been suspended. *
* +45755 Diagnostic information has been recorded. *
* Contact IBM Support for *
* +45756 further assistance. *
* *
* *
* <StackTrace> *
* -------Frame------ ------Function + Offset------ *
* 0x090000000054E470 pthread_kill + 0xB0 *
* 0x0900000012E546B4 sqloDumpEDU + 0x94 *
* 0x0900000012D00E08 sqle_panic__Fv + 0xA8 *
* 0x0900000012D0106C sqle_trap__Fv + 0xC *
* 0x0900000012D3D3B0 sqlzAssertFailedValist + 0x270 *
* 0x0900000012D3D484 sqlzAssertFailed + 0x64 *
* 0x09000000134F1224 *
* sqlrlc_systables_fetch_from_disk__FP8sqlrr_cbPUcUsT2T3UiN26P13
* RIDPUi + 0x1904 *
* 0x0900000014C88C10 *
* sqlrlc_systables_load_entry__FP8sqlrr_cbP22sqlrlc_entry_systab
* + 0x2B0 *
* 0x0900000014C89378 *
* sqlrlc_load_entry__FP8sqlrr_cbP19sqlrlc_entry_commonUiN23PUi *
* + 0x198 *
* 0x0900000014C81260 *
* sqlrlc_request_ulock__FP8sqlrr_cbP19sqlrlc_entry_commonP20sqlr
* 8 + 0x440 *
* 0x0900000014C83C7C *
* sqlrlc_find_request_usage_lock__FP8sqlrr_cbP10sqlrlc_keyUiN23P
* + *
* 0x47C *
* 0x09000000134F3898 *
* sqlrlc_systables_fetch__FP8sqlrr_cbPUcUsT2T3UiN26P13SQLO_MEM_P
* + 0xB18 *
* 0x0900000013DCD2E0 sqlpiGetPolicy + 0x200 *
* 0x0900000013DCB560 sqlpiGetStatsProfile + 0xE0 *
* 0x0900000013DB421C sqlrr_readAutonomicPolicies__FP8sqlrr_cb *
* + 0x1BC *
* 0x0900000013DC7308 sqlrr_appl_init__FP8sqeAgentP5sqlca + *
* 0x1B68 *
* 0x090000001319184C *
* InitEngineComponents__14sqeApplicationFcP8sqeAgentP8SQLE_BWAP5
* + 0xC2C *
* 0x09000000131951BC *
* AppStartUsing__14sqeApplicationFP8SQLE_BWAP8sqeAgentcT3P5sqlca
* + 0xA5C *
* 0x09000000131958B4 *
* sqleProcessConnectType__FP14db2UCinterfaceP8SQLE_BWAP8sqeAgent
* + 0x214 *
* 0x09000000131980A0 *
* AppLocalStart__14sqeApplicationFP14db2UCinterface + 0x4A0 *
* 0x09000000131717AC sqlelostWrp__FP14db2UCinterface + 0x4C *
* 0x09000000131738F0 sqleUCengnInit__FP14db2UCinterfaceUs + *
* 0x4F0 *
* 0x090000001317957C sqleUCagentConnect + 0x137C *
* 0x09000000149B1244 *
* sqljsConnectAttach__FP13sqljsDrdaAsCbP14db2UCinterface + *
* 0x224 *
* 0x09000000149E762C *
* sqljs_ddm_accsec__FP14db2UCinterfaceP13sqljDDMObject + 0x14C *
* 0x0900000014A5C94C *
* sqljsParseConnect__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCin
* + 0x14C *
* 0x0900000014A5AF1C *
* sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterface + 0x1FC *
* 0x0900000014A1D854 sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb *
* + 0x494 *
* 0x0900000014A1F69C *
* sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x15C *
* 0x0900000014A26660 *
* sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x460 *
* 0x0900000014A286DC sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T *
* + 0x23C *
* 0x0900000012F65D8C RunEDU__8sqeAgentFv + 0x3AC *
* 0x0900000012F558FC EDUDriver__9sqzEDUObjFv + 0x19C *
* 0x0900000012F55C1C sqlzRunEDU__FPcUi + 0x3C *
* 0x0900000012E5CBA4 sqloEDUEntry + 0x6A4 *
* </StackTrace> *
****************************************************************
* RECOMMENDATION: *
* See local fix or apply DB2 Version 9.7 fix pack 1 and *
* reissue activate database. *
**************************************************************** |
| Local Fix: |
Turn off AUTO_STATS_PROF database configuration or connect to
database without doing database activation first. |
| 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 |
The problem is fixed in DB2 Version 9.7 fix pack 1 and all
subsequent fix packs. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.09.2009
04.01.2010
04.01.2010 |
| 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
|
 |
