DB2 - Problem description
| Problem IC92252 | Status: Closed |
Log full during table truncation causes critical error and marks database bad | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
While executing an ALTER TABLE ... ACTIVATE NOT LOGGED INITIALLY
WITH EMPTY TABLE command against a table that has row
compression enabled, if the statement fails with a LOG FULL
error, DB2 may not be able to undo the operation and the
database manager may fail with a critical error. You will see
messages similar to the following in the db2diag.log:
2013-04-18-15.28.31.714390+480 I105678060A540 LEVEL: Error
PID : 6291876 TID : 38889 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-54612 APPID:
192.168.144.49.35218.130418050004
AUTHID : TEST
EDUID : 38889 EDUNAME: db2agntp (SAMPLE) 32
FUNCTION: DB2 UDB, Common Trace API, sqlbfix, probe:2
MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE
"Log File has reached its saturation point"
DIA8309C Log file was full.
2013-04-18-15.28.31.714546+480 I105678601A2242 LEVEL: Severe
PID : 6291876 TID : 38889 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-54612 APPID:
192.168.144.49.35218.130418050004
AUTHID : TEST
EDUID : 38889 EDUNAME: db2agntp (SAMPLE) 32
FUNCTION: DB2 UDB, data management, sqldomUndo, probe:3697
MESSAGE : ZRC=0x87040055=-2029780907=SQLD_PRGERR "Unknown
PROGRAM ERROR"
DIA8576C A data management services programming error
occurred.
DATA #1 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 88 bytes
Obj: {pool:16;obj:19589;type:0} Parent={16;19589}
lifeLSN: 0001400472B81F5E
tid: 0 0 0
extentAnchor: 18021888
initEmpPages: 0
poolPage0: 18022016
poolflags: 4122
objectState: 27
lastSMP: 0
pageSize: 32768
extentSize: 32
bufferPoolID: 2
partialHash: 1283784720
bufferPool: 0x0700000058848580
pdef: 0x0700000060edc860
DATA #2 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
00014254BC306716
DATA #3 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
00014254BC316DB4
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x0900000007092B60 pdLog + 0xE4
[1] 0x0900000005A659B0
sqldomUndo__FP8sqeAgentP10SQLDOM_LRHP9SQLP_LSN8sP15SQLD_RECOV_IN
FO + 0x618
[2] 0x0900000003B954AC
sqldmund__FP8sqeAgentP9SQLP_LSN8PcUisT4P8SQLP_TIDP15SQLD_RECOV_I
NFO + 0x1FC
[3] 0x0900000007214974
sqlptudo__FP8sqeAgentPUlP15SQLD_RECOV_INFOP11SQLP_TENTRY + 0x1FC
[4] 0x0900000007214D1C sqlptud1__FP8sqeAgentUl + 0x40
[5] 0x090000000574263C sqlpSpRb__FP8sqeAgentiUl + 0x528
[6] 0x09000000047F6164
sqldTableAlter__FP8sqeAgentP18SQLD_TABLEALTER_CBP21SQLD_ATTACH_I
NDEX_MAP + 0x1D8
[7] 0x0900000004851C70
sqlrlAlterTableReceive__FP8sqlrr_cbP16sqlkdRqstRplyFmtiP13SQLR_R
PC_DATBP15SQLR_RPCMESSAGE + 0x1D08
[8] 0x0900000004150704
sqlrl_rpc_dms_router__FP8sqlrr_cbP16sqlkdRqstRplyFmtiP15SQLR_RPC
MESSAGE + 0x6FC
[9] 0x0900000003062A5C sqlrr_rpc_router__FP8sqlrr_cb + 0x444 | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V97FP9 or higher version. * **************************************************************** | |
| Local Fix: | |
N/A | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
| Solution | |
Fixed on DB2 V97FP9 or higher version. | |
| Workaround | |
N/A | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC96364 IC96823 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.05.2013 17.12.2013 17.12.2013 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP9 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.9 |
|
| 9.7.0.9 |
|