|
Problem IT21719
|
Status: Closed |
'DB2 WRITE SUSPEND FOR DATABASE' COMMAND HUNG DUE TO DEAD LATCH WHEN USING 'EXCLUDE LOGS' OPTION
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Rarely dead latch may happen in 'db2 write suspend for database'
command when using with 'exclude logs' option.
1. The EDU running 'db2 write suspend for database exclude logs'
does not
complete while waiting for the latch
'SQLO_LT_SQLP_TENTRY__tranEntryLatch'.
( Stack pattern )
...
sqloSpinLockConflict
sqlpLatchTranEntry
sqlpWriteLRSingularTran
sqlpSuspendLog
sqlbSuspendDBControlFiles
sqlbSuspendWrite
sqlbSetWriteSuspend
sqlbSetWriteAction
sqlbSetPoolChange
...
2. An application holding the latch
'SQLO_LT_SQLP_TENTRY__tranEntryLatch'
is trying to write log record and waiting for the end of db
suspend status and resuming.
( Stack pattern )
...
sqloWaitEDUWaitPost
sqlpWriteToLog
sqlpWriteLR
sqlpWriteLRSingularTran
sqlpWriteLRSingularTran
... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 LUW V10.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version V11.1 Fixpack 3 *
**************************************************************** |
| Local Fix: |
Use 'db2 write suspend for database' without using 'exclude
logs' option |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : IT11328
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.08.2017
11.10.2017
11.10.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
