|
Problem IC76249
|
Status: Closed |
MISLEADING SEVERE ERRORS IN THE DB2DIAG.LOG FROM "DB2 UDB, INDEX MANAGER" AFTER FAILED REORG |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When undoing a failed REORG TABLE operation, the index manager
may write several error messages to the db2diag.log even though
there is no problem. It will also write data to a binary dump
file. However no FODC_IndexError directory will be created.
The first Severe error message from the index manager will
contain the line "FUNCTION: DB2 UDB, index manager, sqliundo,
probe:0"
The first few messages will look something like this:
2011-05-06-15.25.56.132402-240 I48813E466 LEVEL: Severe
PID : 21295 TID : 47629736077632PROC :
db2sysc
INSTANCE: dbuser NODE : 000 DB : WSDB
APPHDL : 0-7 APPID: *LOCAL.dbuser.110506192554
AUTHID : DBUSER
EDUID : 16 EDUNAME: db2agent (WSDB)
FUNCTION: DB2 UDB, index manager, sqliundo, probe:0
RETCODE : ZRC=0x00000003=3
DIA8003C The interrupt has been received.
2011-05-06-15.25.56.132622-240 I49280E539 LEVEL: Severe
PID : 21295 TID : 47629736077632PROC :
db2sysc
INSTANCE: dbuser NODE : 000 DB : WSDB
APPHDL : 0-7 APPID: *LOCAL.dbuser.110506192554
AUTHID : DBUSER
EDUID : 16 EDUNAME: db2agent (WSDB)
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
logging func, probe:0
MESSAGE : SQLP_LSN8
DATA #1 : Hexdump, 8 bytes
0x00002B51A97F60C0 : A76A 4802 0000 0000
.jH.....
2011-05-06-15.25.56.132704-240 I49820E547 LEVEL: Severe
PID : 21295 TID : 47629736077632PROC :
db2sysc
INSTANCE: dbuser NODE : 000 DB : WSDB
APPHDL : 0-7 APPID: *LOCAL.dbuser.110506192554
AUTHID : DBUSER
EDUID : 16 EDUNAME: db2agent (WSDB)
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
logging func, probe:0
MESSAGE : SQLI_LRH
DATA #1 : Hexdump, 16 bytes
0x00002B51A97F5078 : 0292 0200 0400 0200 0400 0100 0200 0000
................
2011-05-06-15.25.56.132764-240 I50368E176 LEVEL: Severe
PID:21295 TID:47629736077632 NODE:000 Title: SQLI_CB
Dump File:/home/dbuser/sqllib/db2dump/21295.16.000.dump.bin
2011-05-06-15.25.56.132872-240 I50545E177 LEVEL: Severe
PID:21295 TID:47629736077632 NODE:000 Title: sqeAgent
Dump File:/home/dbuser/sqllib/db2dump/21295.16.000.dump.bin |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* When undoing a failed REORG TABLE operation, the index *
* manager may write several error messages to the db2diag.log *
* even though there is no problem. It will also write data to *
* a binary dump file. However no FODC_IndexError directory *
* will be created. The first Severe error message from the *
* index manager will contain the line "FUNCTION: DB2 UDB, *
* index manager, sqliundo, probe:0" *
* *
* *
* *
* The first few messages will look something like this: *
* *
* *
* *
* 2011-05-06-15.25.56.132402-240 I48813E466 LEVEL: *
* Severe *
* PID : 21295 TID : 47629736077632PROC : *
* db2sysc *
* INSTANCE: dbuser NODE : 000 DB : *
* WSDB *
* APPHDL : 0-7 APPID: *
* *LOCAL.dbuser.110506192554 *
* AUTHID : DBUSER *
* EDUID : 16 EDUNAME: db2agent (WSDB) *
* FUNCTION: DB2 UDB, index manager, sqliundo, probe:0 *
* RETCODE : ZRC=0x00000003=3 *
* DIA8003C The interrupt has been received. *
* *
* 2011-05-06-15.25.56.132622-240 I49280E539 LEVEL: *
* Severe *
* PID : 21295 TID : 47629736077632PROC : *
* db2sysc *
* INSTANCE: dbuser NODE : 000 DB : *
* WSDB *
* APPHDL : 0-7 APPID: *
* *LOCAL.dbuser.110506192554 *
* AUTHID : DBUSER *
* EDUID : 16 EDUNAME: db2agent (WSDB) *
* FUNCTION: DB2 UDB, trace services, sqlt_logerr_data *
* (secondary logging func, probe:0 *
* MESSAGE : SQLP_LSN8 *
* DATA #1 : Hexdump, 8 bytes *
* 0x00002B51A97F60C0 : A76A 4802 0000 0000 *
* .jH..... *
* *
* 2011-05-06-15.25.56.132704-240 I49820E547 LEVEL: *
* Severe *
* PID : 21295 TID : 47629736077632PROC : *
* db2sysc *
* INSTANCE: dbuser NODE : 000 DB : *
* WSDB *
* APPHDL : 0-7 APPID: *
* *LOCAL.dbuser.110506192554 *
* AUTHID : DBUSER *
* EDUID : 16 EDUNAME: db2agent (WSDB) *
* FUNCTION: DB2 UDB, trace services, sqlt_logerr_data *
* (secondary logging func, probe:0 *
* MESSAGE : SQLI_LRH *
* DATA #1 : Hexdump, 16 bytes *
* 0x00002B51A97F5078 : 0292 0200 0400 0200 0400 0100 0200 0000 *
* ................ *
* *
* 2011-05-06-15.25.56.132764-240 I50368E176 LEVEL: *
* Severe *
* PID:21295 TID:47629736077632 NODE:000 Title: SQLI_CB *
* Dump File:/home/dbuser/sqllib/db2dump/21295.16.000.dump.bin *
* *
* 2011-05-06-15.25.56.132872-240 I50545E177 LEVEL: *
* Severe *
* PID:21295 TID:47629736077632 NODE:000 Title: sqeAgent *
* Dump File:/home/dbuser/sqllib/db2dump/21295.16.000.dump.bin *
* *
* ... *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7.0.5. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
The problem is first fixed in DB2 version 9.7.0.5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.05.2011
08.12.2011
08.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.0.5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
