DB2 - Problem description
Problem IC81166 | Status: Closed |
THE DB2CLUSTER COMMAND MAY FAIL IF THE GRACE PERIOD RSCT PARAMETER IS CHANGED FROM ITS INITIAL VALUE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
The db2cluster command may fail with an error after changing the grace period value of RSCT with the RSCT command manually. The grace period RSCT parameter is set initially according to the configuration of PureScale. But the user can change it with the command of RSCT. If it is changed from the initial value set by PureScale, the user may get an error for db2clsuter command. Example of failing db2cluster command) # db2cluster -cm -list -HOSTFAILUREDETECTIONTIME Unable to determine the host failure detection time of the shared file system . cluster. A diagnostic log has been saved to '/tmp/ibm.db2.cluster.-4aoUa'. . Example of logged error) 2012-01-11-14.34.32.320223+540 E3085A413 LEVEL: Error PID : 13959406 TID : 1 PROC : db2cluster INSTANCE: instname NODE : 000 HOSTNAME: hostname EDUID : 1 FUNCTION: DB2 UDB, high avail services, sqlhaGetInfoForClusterObject, probe:4154 RETCODE : ECF=0x90000603=-1879046653=ECF_SQLHA_COMM_GROUP_BAD_CONFIG A communication group is in bad configuration 2012-01-11-14.34.32.321415+540 I3499A401 LEVEL: Error PID : 13959406 TID : 1 PROC : db2cluster INSTANCE: instname NODE : 000 HOSTNAME: hostname EDUID : 1 FUNCTION: DB2 UDB, high avail services, sqlhaUIGetFFDTime, probe:485 MESSAGE : ECF=0x90000603=-1879046653=ECF_SQLHA_COMM_GROUP_BAD_CONFIG A communication group is in bad configuration | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users using db2cluster command. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.8 Pix Pack 5. * **************************************************************** | |
Local Fix: | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.8 Fix Pack 5. | |
Workaround | |
Not available. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.02.2012 21.06.2012 21.06.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.8., 9.8.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.8.0.5 |