|
Problem IC84174
|
Status: Closed |
UPDATING THE NEWLOGPATH DATABASE CONFIGURATION PARAMETER WHILE THE DATABASE IS NOT ACTIVE CAN CAUSE DB2 TO HANG |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Updating the NEWLOGPATH db cfg parameter while the database is
not active can cause DB2 to hang.
Stack trace reports deadlatch between functions
SQLO_LT_sqeDBMgr__dbMgrLatch and
SQLO_LT_SQLE_KRCB__cfg_change_latch. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10 Fix Pack 1 *
**************************************************************** |
| Local Fix: |
Activate the database prior to issuing an update command on the
NEWLOGPATH database parameter. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 V10 Fix Pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.06.2012
17.12.2012
17.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
