|
Problem IT23238
|
Status: Closed |
HANG CAUSED BY DB2VEND PROCESS IN ACTIVATION PROCESS
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
If a session to the TSM server appears to 'hang', and DEACTIVATE
DATABASE or DB2STOP command is issued, Db2 will wait for pending
archive requests to complete. But since the TSM/vendor API call
is not responding, the database will not deactivate, which
during this time means no new applications can connect to the
database leaving customer applications not responding looking
like a system outage. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 fp10 *
**************************************************************** |
| Local Fix: |
N/A |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.11.2017
23.02.2020
23.02.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
