home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC67824 Status: Closed

INSTANCE MAY GO DOWN WHEN DISK FULL OR OTHER CRITICAL ERROR APPEARS.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If you encouter a disk full situation and db2diag.log has a 
message as similar as below, your instance may go down. 
 
------ 
2010-03-11-14.38.26.900973+540 E69461696A1212     LEVEL: Error 
(OS) 
PID     : 663608               TID  : 140612      PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : xxx 
APPHDL  : 0-307                APPID: 
10.11.5.18.55236.100311052536 
AUTHID  : DWH 
EDUID   : 140612               EDUNAME: db2lfrm0 0 
FUNCTION: DB2 UDB, oper system services, sqlowrite, probe:70 
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full." 
          DIA8312C Disk was full. 
CALLED  : OS, -, write 
OSERR   : ENOSPC (28) "No space left on device" 
------ 
 
The associated trap file may have a similar stack trace as 
below: 
. 
<StackTrace> 
. ?unknown + 0x0 
. _gtraceExitVar + 0x400 
. pdtExit2 + 0x118 
. efTraceExit__FUiiPUlUlT4PPc + 0x1FC 
. eftExitEx__FUiPUlUlT3PiP6EFRuleN23e + 0x94 
. eftExitEx__FUiPUlUlT3PiP6EFRuleN23e@glue14E + ... 
. sqlowrite + 0x70 
... 
. 
If there is no disk full condition, instance may not go down.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.7.                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 3.                            * 
****************************************************************
Local Fix:
Removing a disk full situation for preventing instance down by 
this problem.
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 9.7 FixPack 3.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC68029 IC68786 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.04.2010
27.09.2010
27.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList