|
Problem IT01604
|
Status: Closed |
ON WINDOWS ONLY, THE INSTANCE MAY PANIC AFTER A FAILED ASYNCHRONOUS I/O (AIO) OPERATION. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
On Windows only, the AIO collector EDU doesn't distinguish
between a failure in the API used to gather AIO operation
results and a failed AIO operation. On detection of either
failure it causes an instance panic which results in a shut
down. For example, asynchronous SMS tablespace writes failing on
a disk full condition will result in such a reaction by the AIO
collector EDU.
With this APAR fix DB2 can distinguish between a failed API call
and a failed AIO operation and will not panic at this point for
failed AIO operations. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Windows OS *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v97 FP 11 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.05.2014
06.10.2015
06.10.2015 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP11
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.11
|
 |
