|
Problem IC62860
|
Status: Closed |
DB2 INSTANCE PANICS IN SQLO_SLATCH_CAS64::RELEASECONFLICTCOMPLEX |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
DB2 keeps track of its open files. It was observed that under
an extreme case where DB2 was kept running for days in a file
system full environment, various file I/O releated OS
subroutines may fail, and DB2 instance panics. Heres the
message that would appear when the panic occurs and the
instance goes down.
2009-02-20-14.00.48.456184-300 E104501158E2273 LEVEL: Severe
(OS)
PID : 1234 TID : 1234567890 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-12345 APPID: *LOCAL.db2inst1.123456789
AUTHID : DB2INST1
EDUID : 241 EDUNAME: db2agent (LNX1)
FUNCTION: DB2 UDB, SQO Latch Tracing,
SQLO_SLATCH_CAS64::releaseConflictComple, probe:330
MESSAGE :
ZRC=0x870F011E=-2029059810=SQLO_LATCH_ERROR_EXPECTED_HELD
expected latch to be held.
CALLED : OS, -, unspecified_system_function
DATA #1 : String, 39 bytes
Attempting to unlock an invalid latch:
<snipped...>
DATA #7 : String, 411 bytes
{
state = 0x0000000000000000
= {
held X: 0
reserved for X: 0
shared holders: 0
firstSharIndex: 0x0
firstExclIndex: 0x0
}
starve X mode = false
xWaitCount = 0
requestCount = 0
identity = sqlofmga.C::SQLO_TLFL_m_fileLatch (693)
}
<snipped...>
CALLSTCK:
[0] 0x00007F608D05CF24 pdLogSysRC + 0x12C
[1] 0x00007F608DEF2DE9
_ZNK17SQLO_SLATCH_CAS6420dumpDiagInfoAndPanicEPKcjmmlmiS1_mi +
0x1DF
[2] 0x00007F608CC5B5D0
_ZN17SQLO_SLATCH_CAS6422releaseConflictComplexEv + 0x35A
[3] 0x00007F608CC5B23F
_ZN17SQLO_SLATCH_CAS6415releaseConflictEv + 0x33
[4] 0x00007F608CC990F2
/wsdb/db2_v95fp4/linuxamd64nocc/s090216/INST/lib/libdb2e.so.1 +
0x133B0F2
[5] 0x00007F608CC997FB sqloclose + 0x1E1
<snipped...>
This APAR fix will address the panic, so that DB2 will record
diagnostic messages to db2diag.log. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Environment constrained with file system operations *
****************************************************************
* PROBLEM DESCRIPTION: *
* Same as ERROR DESCRIPTION *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7 Fix Pack 1 *
**************************************************************** |
| 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 6 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 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 |
Fixed in DB2 9.7 Fix Pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.08.2009
21.02.2010
21.02.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
|
 |
