|
Problem IT06793
|
Status: Geschlossen |
DB2LOGMGR MAY GET INTO A SELF DEADLATCH SITUATION CAUSING A HANG |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
DB2 is pruning backups and log files at the end of a backup and
a simultaneous request to archive or retrieve a log file comes
in.
If for example something wents wrong inside TSM and a signal
gets raised, it causes DB2 to not free the sessionCount latch
and hanging the instance.
You will see the following for db2logmgr:
<LatchInformation>
Waiting on latch type: (SQLO_LT_sqluvend_C__sessionCountLatch) -
Address: (000000001347B008), Line: 277, File: sqluvend.C
Holding latch type: (SQLO_LT_sqluvend_C__sessionCountLatch) -
Address: (000000001347B008), Line: 277, File: sqluvend.C
HoldCount: 1
</LatchInformation> |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* DB2 LUW *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.5 FP7 *
**************************************************************** |
| Local-Fix: |
|
| Lösung |
|
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 28.01.2015
14.01.2016
14.01.2016 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.7
|
 |
