|
Problem IC80596
|
Status: Closed |
ON AIX DUIRNG DB2DIAG LOG CONTENTION, THE RETRY-OPENING DB2DIAG.LOG MAY TAKE TOO LONG IF DB2DIAG.LOG WAS LOCKED BY ANOTHER PROCE |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
On AIX, duirng db2diag.log contention, when db2diag.log is
locked by another process, the retry-opening db2diag.log will
take longer time ( 4 - 5 minutes ) before giving up. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of version 9.5 on AIX *
****************************************************************
* PROBLEM DESCRIPTION: *
* On AIX, duirng db2diag.log contention, when db2diag.log is *
* locked by another process, the retry-opening db2diag.log *
* will *
* take longer time ( 4 - 5 minutes ) before giving up. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.5 Fix Pack 10. *
**************************************************************** |
| Local Fix: |
Release the db2diag.log file lock by moving or archiving
db2diag.log |
| Solution |
Problem was first fixed in Version 9.5 Fix Pack 10. |
| Workaround |
Release the db2diag.log file lock by moving or archiving
db2diag.log |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC82427
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.12.2011
22.08.2012
22.08.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.10
|
 |
