|
Problem IT06792
|
Status: Closed |
DB2LOGMGR MAY GET INTO A SELF DEADLATCH SITUATION CAUSING A HANG |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.01.2015
14.07.2015
14.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
|
 |
