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

UNEXPECTED INSTANCE SHUTDOWN 8 HOURS AFTER DB2START HAS BEEN EXECUTED IN
TSA ENABLED ENVIRONMENT

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When TSA has a problem locking a resource group, as requested by 
DB2, then DB2 will spin for more than 8 hours waiting for TSA to 
change the lock state before returning an error. 
This can be hit during db2start. 
 
This APAR will reduce the time so that an error is returned much 
sooner when TSA fails to lock the resource group. 
 
 
Symptoms: 
 
- about 8 hours and 20 minutes after db2start was executed the 
instance will terminate unexpectedly 
 
- prior to the unexpected instance termination following message 
will repeatedly be printed to the db2diag.log 
(The 'DATA #2' information is a counter that will be increased 
by 1 with each occurence of the message.) 
 
2014-11-11-02.48.04.775811+000 I22195969A495        LEVEL: Error 
PID     : 3604862              TID : 1              PROC : 
db2star2 
INSTANCE: db2inst              NODE : 000 
HOSTNAME: db2host 
EDUID   : 1 
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:6396 
MESSAGE : ZRC=0x870F00B9=-2029059911=SQLO_SEM_TIMEOUT 
          "Return code from sqlowait when time out value has 
been reached" 
DATA #1 : String, 29 bytes 
Waiting for db2sysc. Retry# : 
DATA #2 : unsigned integer, 4 bytes 
8 
 
- right before the unexpected instance shutdown following errors 
will indicate failure to verify TSA resource lock state 
 
2014-11-11-11.11.04.393218+000 E28476647A772        LEVEL: Error 
PID     : 13369436             TID : 258            PROC : 
db2sysc 0 
INSTANCE: db2inst              NODE : 000 
HOSTNAME: db2host 
EDUID   : 258                  EDUNAME: db2sysc 0 
FUNCTION: DB2 UDB, high avail services, 
sqlhaEnableResourceGroup2, probe:500 
MESSAGE : 
ECF=0x90000550=-1879046832=ECF_SQLHA_ENABLE_GROUP_FAILED 
          Error unlocking resource group 
DATA #1 : String, 43 bytes 
Cluster Error during vendor call invocation 
DATA #2 : unsigned integer, 4 bytes 
16 
DATA #3 : String, 15 bytes 
db2_db2inst_0-rg 
DATA #4 : unsigned integer, 8 bytes 
1 
DATA #5 : signed integer, 4 bytes 
0 
DATA #6 : String, 86 bytes 
Line # : 9388--- db2haGetGroupLockState timeout, group could not 
be verified enabled. 
 
2014-11-11-11.11.04.419999+000 I28478828A432        LEVEL: 
Severe 
PID     : 13369436             TID : 258            PROC : 
db2sysc 0 
INSTANCE: db2inst              NODE : 000 
HOSTNAME: db2host 
EDUID   : 258                  EDUNAME: db2sysc 0 
FUNCTION: DB2 UDB, base sys utilities, 
sqleCMResourceGroupUnlock, probe:15460 
MESSAGE : ZRC=0x827300CD=-2106392371=HA_ZRC_ENABLE_GROUP_FAILED 
          "Error unlocking resource group" 
 
- instance termination will be indicated by following message in 
the db2diag.log file 
 
2014-11-11-11.11.04.420233+000 I28479261A500        LEVEL: 
Severe 
PID     : 13369436             TID : 258            PROC : 
db2sysc 0 
INSTANCE: db2inst              NODE : 000 
HOSTNAME: db2host 
EDUID   : 258                  EDUNAME: db2sysc 0 
FUNCTION: DB2 UDB, base sys utilities, sqleSysCtlr, probe:2572 
MESSAGE : ZRC=0xFFFFF973=-1677 
          SQL1677N  DB2START or DB2STOP processing failed due to 
a DB2 cluster 
          services error. 
 
DATA #1 : <preformatted> 
db2sysc abrupt termination
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local-Fix:
Lösung
First fixed in DB2 Version 10.1 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.11.2014
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