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 IC78904 Status: Closed

WLM DAEMON, LAST USED DAEMON, AND FAST WRITERS GET NODE FAILURE ERRORS EVEN
AFTER NODE IS BROUGHT BACK ONLINE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The wlm daemon, last used daemon, and fast writers are not 
recovering from node failures properly and continue to get NODE 
FAILURE errors even after the node failure is resolved. 
 
This is a typical message that would be seen in the db2diag.log 
even after the node failure has been resolved. 
 
2011-08-16-08.20.00.960332-240 I10265006A522        LEVEL: 
Severe 
PID     : 516680               TID  : 39198         PROC : 
db2sysc 0 
INSTANCE: dbinst1          NODE : 000            DB   : TESTDB 
APPHDL  : 0-113               APPID: *N0.DB2.110812125911 
AUTHID  : dbinst1 
EDUID   : 39198               EDUNAME: db2agntp 0 
FUNCTION: DB2 UDB, WLM, sqlrwWlmRPCRouter, probe:20 
CALLED  : DB2 UDB, WLM, sqlrwWlmRPCRouter 
RETCODE : ZRC=0x81580016=-2124939242=SQLKD_NODE_FAILURE 
          "Mapping for SQLKF_NODE_FAILED"
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF environments                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See above.                                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.7 fp6 or higher.                               * 
****************************************************************
Local Fix:
Deactivate the database and terminate all connections to the 
database. In other words, restart the database.
available fix packs:
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
After applying the fix for this APAR, background system 
applications (wlm daemon, last used daemon, fast writers) will 
recover from node failure properly so that they don't continue 
to report node failed errors after the node failure has been 
resolved. The fix was first included in v9.7 fp6.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.09.2011
04.06.2012
04.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.