DB2 - Problem description
Problem IC69267 | Status: Closed |
"RESOURCE GROUP MOVE" COMMAND IN DB2HAICU EXITS SUCCESSFULLY WITH PERSISTENT REQUEST ON THE RESOURCE DUE TO INCORROUT CHECK. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
The way db2haicu detects if a resource move is complete is to run a while loop "x" times with a 1 second sleep each time. "x" is derived by adding the start and stop timeout values for a resource group. This loop proceeds only if there are no pending requests on the resource. But in case there is a persistent request on the resource this will never be true. So the loop ends up waiting for the entire time and eventually exits successfully which is incorrect. It should exit unsuccessfully. This happens as the logic of code is if the timeout=0 db2haicu should log an error and exit with a bad rc. However in this case it is timeout=-1 and the error is not logged. The condition should be, if (timeout <= 0). | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Customers on DB2 V9.1, V9.5 and V9.7 * **************************************************************** * PROBLEM DESCRIPTION: * * "resource move" using db2haicu fails. * **************************************************************** * RECOMMENDATION: * * Upgrade to V9.7fp3 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Fixed on V9.7fp3 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC69375 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 16.06.2010 23.09.2010 23.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 | |
9.7.0.3 |