|
Problem IC84343
|
Status: Closed |
CATALOG NODE FAILURE CAN LEAD TO SYSTEM APPICATIONS NOT TERMINATING AND CAUSE SQL1229N ON NON-CATALOG NODES. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
A catalog node failure can lead to a timing issue on non-catalog
nodes where certain system applications are concurrently being
interrupted by a node failure interrupt and a force interrupt
causing the force interrupt to be lost. If the catalog node
failure interrupt happens and the agent does not process it
completely before the force interrupt comes in, (due to the last
user connection on a db forcing off all applications) the force
interrupt will be lost and the system application will return to
its waitpost. The last user connection will be waiting in
TermDbConnect on lastSysApplOut forever. Any other applications
attempting to connect to this db will get -1229.
The stack of the last user connection will be in this state:
thread_wait
sqloWaitEDUWaitPost
TermDbConnect
AppStopUsing
sqlesrspWrp
sqleUCagentConnectReset
sqljsCleanup
sqljsDrdaAsInnerDriver
sqljsDrdaAsDriver
RunEDU
EDUDriver
sqloEDUEntry
And the fast writer system application will be in this state:
thread_wait
sqloWaitEDUWaitPost
executeFastWriter
sqleIndCoordProcessRequest
RunEDU
EDUDriver
sqloEDUEntry |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 1 *
**************************************************************** |
| Local Fix: |
|
| 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 Version 10.1 Fix Pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.06.2012
13.11.2012
13.11.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
|
|
