DB2 - Problembeschreibung
Problem IC82489 | Status: Geschlossen |
Within a very small timing window DB2 can panic and trap in sqlbDecrementFixCountWithLatches. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
The following error messages will be generated in the db2diag.log before DB2 panics and comes down. 2010-06-15-08.45.41.147072-300 I586896E1748 LEVEL: Severe PID : 11111 TID : 183035406528PROC : db2agntp 7 INSTANCE: db2inst1 NODE : 007 APPHDL : 0-240 APPID: 10.80.176.143.32476.10061511111 AUTHID : TEST FUNCTION: <0>, <0>, <195>, probe:222 DATA #1 : String, 49 bytes sqlbDecrementFixCountWithLatches hashindx changed DATA #2 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 152 bytes Pagekey: {pool:3;obj:0;type:128} PPNum:1234 objectPageNum: 1887 bucketGroupHashIndex: -2 hashnext: 0x0000000000000000 hashprev: 0x0000000000000000 osslatch: 2010-06-15-08.45.41.382239-300 I588645E460 LEVEL: Severe PID : 23228 TID : 183035406528PROC : db2agntp 7 INSTANCE: db2inst1 NODE : 007 APPHDL : 0-240 APPID: 10.80.176.143.32476.10061511111 AUTHID : TEST FUNCTION: DB2 UDB, buffer pool services, sqlb_panic, probe:20 RETCODE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error detected" DIA8501C A buffer pool logic error has occurred. . . 2010-06-15-08.45.51.198126-300 I688988E456 LEVEL: Severe PID : 11111 TID : 183035406528PROC : db2agntp 7 INSTANCE: db2inst1 NODE : 007 APPHDL : 0-240 APPID: 10.80.176.143.32476.10061511111 AUTHID : TEST FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10 MESSAGE : sqle_panic: Panic/sleep = DATA #1 : Hexdump, 4 bytes 0x00000002000101CC : 0000 0000 .... . . 2010-06-15-08.45.57.478074-300 E695237E601 LEVEL: Severe PID : 11111 TID : 183035406528PROC : db2agntp 7 INSTANCE: db2inst1 NODE : 007 APPHDL : 0-240 APPID: 10.80.176.143.32476.10061511111 AUTHID : TEST FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:10 MESSAGE : ADM0503C An unexpected internal processing error has occurred. ALL DB2 PROCESSES ASSOCIATED WITH THIS INSTANCE HAVE BEEN SHUTDOWN. Diagnostic information has been recorded. Contact IBM Support for further assistance. Snippet of the stack that gets generated in the Trap file: 0000002A96BAD05C _Z10sqle_panicv + 0x0034 (/opt/IBM/db2/V9.1/lib64/libdb2e.so.1) 0000002A96A69F69 sqlb_panic + 0x0069 (/opt/IBM/db2/V9.1/lib64/libdb2e.so.1) 0000002A963EC86B _Z32sqlbDecrementFixCountWithLatchesP8SQLB_BPDP12SQLB_GLOBALSP15 SQLB_BufferPoolb + 0x013b (/opt/IBM/db2/V9.1/lib64/libdb2e.so.1) 0000002A980871E9 _Z7sqlbfixP11SQLB_FIX_CB + 0x1591 (/opt/IBM/db2/V9.1/lib64/libdb2e.so.1) 0000002A9809E878 address: 0x0000002A9809E878 ; dladdress: 0x0000002A956B3000 ; offset in lib: 0x00000000029EB878 ; (/opt/IBM/db2/V9.1/lib64/libdb2e.so.1) 0000002A9809D4E5 _Z7sqldfrdP13SQLD_DFM_WORK + 0x00d5 (/opt/IBM/db2/V9.1/lib64/libdb2e.so.1) 0000002A980FFA47 _Z12sqlsmergerecP20sqle_agent_privatecbP10SQLS_SLDESP10SQLS_MBUF Sm + 0x00d7 (/opt/IBM/db2/V9.1/lib64/libdb2e.so.1) 0000002A980FAF8F _Z8sqlsfetcP20sqle_agent_privatecbP8SQLD_CCBiP10SQLD_DPREDPP10SQ LD_VALUEP8SQLZ_RIDPc + 0x02d7 (/opt/IBM/db2/V9.1/lib64/libdb2e.so.1) 0000002A980E0215 _Z10sqlriFetchP8sqlrr_cbP9sqlri_taol + 0x0095 (/opt/IBM/db2/V9.1/lib64/libdb2e.so.1) 0000002A980ECE0A _Z7sqlritaP8sqlrr_cb + 0x00ca | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * See Error Description * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 for Linux, UNIX, Windows version 9.7 Fix Pack * * 7 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in DB2 for Linux, UNIX, Windows version 9.7 Fix Pack 7 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 03.04.2012 26.10.2012 26.10.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7., 9.7.FP* | |
Problem behoben lt. FixList in der Version | |
9.7.0.7 |