|
Problem IC71417
|
Status: Closed |
DB2 BACKGROUND EDUS MIGHT BE SHUT DOWN UNEXPECTEDLY DURING NODE FAILURE RECOVERY |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
DB2 background EDUs such as the WLM statistics daemon or event
monitor fast writers might get interrupted by node failure
recovery and shut down rather than handling the interrupt and
continuing execution.
When the problem occurs, you will see db2diag.log messages like
below:
2010-09-21-04.22.53.383850-240 E187460E358 LEVEL: Info
PID : 31072 TID : 47720668588352PROC :
db2sysc 1
INSTANCE: db2inst1 NODE : 001
EDUID : 18 EDUNAME: db2pdbc 1
FUNCTION: DB2 UDB, base sys utilities, sqleExecuteNodeRecovery,
probe:1
DATA #1 : String, 34 bytes
Starting node recovery for node 20
2010-09-21-04.22.53.384160-240 I187819E590 LEVEL:
Warning
PID : 31072 TID : 47720509204800PROC :
db2sysc 1
INSTANCE: db2inst1 NODE : 001 DB : SAMPLE
APPHDL : 1-87 APPID: *N1.DB2.100921080237
AUTHID : db2inst1
EDUID : 92 EDUNAME: db2wlmd (SAMPLE) 1
FUNCTION: DB2 UDB, WLM, sqlrwWlmStatsCollector::main, probe:20
RETCODE : ZRC=0x800F0003=-2146500605=SQLO_INTRP "Interrupt.
User Cancel."
DIA8003C The interrupt has been received.
DATA #1 : String, 34 bytes
WLM Stats Collector Shutting Down.
And at the same time, it might also cause one of the fast writer
EDUs to shut down. For example, in the below EDUs output, db2fw2
is missing.
119 47720530176320 6003 db2fw7 (SAMPLE) 1
0.000000 0.000000
118 47720534370624 6002 db2fw6 (SAMPLE) 1
0.000000 0.000000
117 47720563730752 6001 db2fw5 (SAMPLE) 1
0.000000 0.000000
116 47720538564928 6000 db2fw4 (SAMPLE) 1
0.000000 0.000000
115 47720567925056 5999 db2fw3 (SAMPLE) 1
0.000000 0.000000
98 47720505010496 2580 db2fw1 (SAMPLE) 1
0.000000 0.000000
96 47720496621888 2270 db2fw0 (SAMPLE) 1
0.000000 0.000000
When one of the db2 fast writers is gone, it can cause newly
issued DB2 commands such as db2 connect/global snapshot and new
queries to hang. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See above Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 4 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 Version 9.7 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC73208
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.09.2010
02.05.2011
02.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
