home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IT06702 Status: Closed

DB2START MAY HANG AND LEAD TO GROUP RESTART IN PURESCALE BECAUSE OF NO
PROPER TIMEOUT BEFORE CALLING TSA COMMANDS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2start may hang and lead to group restart in pureScale because 
of no proper timeout before calling TSA commands. When the 
db2start command received the interrupt , we did a group restart 
of all the nodes 
 
We need to add a default timeout for the sqlhaCB structure 
 
Here in sqleIssueStartStop we do not set the timeout before 
calling sqlhaStopSDInfrastructure function 
 
 // try a cleanup if this is clusterEnv and db2start an 
individual CA 
 // this is to reverse the RG lock/unlock that may have been 
done 
 // by sqlhaStartSDInfrastructure above 
 // Do not do this cleanup if it was determined that the 
db2start command 
 // was invalid as that implies the SD infrastructure is already 
up. 
 if (clusterEnv && 
     status.caNodenum && 
     (SQLE_DB2ADMIN_DB2START == command) && 
     (SQLE_RC_INVSTRT != remoteSqlca.sqlcode)) 
 { 
    SQLHA_CONTROL_BLOCK sqlhaCB = {0x00}; 
    SQLHA_CLUSTER_OPERATION_RESULT_LIST *pResultList = NULL; 
    int tempRc = 0; 
 
    tempRc = sqlhaStopSDInfrastructure(pInstance, 
                                       &pResultList, 
                                       &sqlhaCB, 
                                       pStartOptions->iNodeNum);
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1fp5                                      * 
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.01.2015
15.07.2015
15.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList