|
Problem IC66780
|
Status: Closed |
A CRASH IN A THREADED FMP PROCESS WHILST WRITING TO THE DB2DIAG.LOG CAN BLOCK ACCESS TO THE DB2DIAG.LOG. |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
If a thread in a threaded FMP process crashes in a function
writing to the db2diag.log, access to the db2diag.log will
be blocked. The scope for such a crash is limited.
The file lock held whilst writing will prevent other
processes from access the db2diag.log until the FMP process
terminates. Internal latching within the process to
protect access to the db2diag.log will prevent the FMP
from terminating. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error description *
****************************************************************
* RECOMMENDATION: *
* Update to DB2 UDB LUW V9.1 FP10. *
**************************************************************** |
| Local Fix: |
Kill the offending FMP process or issue "db2diag -A" to
create a new db2diag.log file. |
| available fix packs: |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
Update to DB2 UDB LUW V9.1 FP10. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66782 IC66793
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.03.2010
14.06.2011
14.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.10
|
 |
