Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT06702 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1fp5                                      * 
****************************************************************
Local-Fix:
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.01.2015
15.07.2015
15.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList