|
Problem IT40758
|
Status: Closed |
HANG ON FIRST CONNECT DRIVING CRASH RECOVERY WHEN DB2LOGMGR HANGS DUE TO VENDOR PROBLEM
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
Background:
Overall, during crash recovery (CR), all EDUs spawned by CR run
as a critical EDU to ensure all memory operations have the best
chance to succeed. At the start of CR, we post all EDUs to mark
them critical. At the end of CR we post all EDUs again to mark
them no longer critical.
Problem:
The diag shows that crash recovery (CR) agent was successful but
before we were really complete db2logmgr made an archive
attempt. The archive attempt hangs in db2logmgr due to vendor
problem. Now the CR agent as part of it's clean up actually
attempts to post db2logmgr to mark the EDU no longer critical.
Because db2logmgr is hung, it cannot service this sync request
and now the CR agent is hung. The CR agent is driven by first
connect, so that means first connect is now hung. That explains
why the customer is experiencing a hang on a first connect
driving CR. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to latest modpack. *
**************************************************************** |
| Local Fix: |
- to get out of the hang: issue 'db2pd -fvp term' to kill the
db2vend process
- to avoid in the future: set LOGARCHOPT1/2 to use a
-VENDOR_ARCHIVE_TIMEOUT |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to latest modpack. *
**************************************************************** |
| Comment |
Problem was first fixed in Db2 Version 11.5.8.0. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.04.2022
12.05.2022
12.05.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
