|
Problem IT09753
|
Status: Closed |
TRAP IN SQLDUNCHAINGIXCB DURING HADR TAKEOVER |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
On a HADR system with Reads On Standby (ROS) enabled, if a
range-partitioned table with non-partitioned indexes
is accessed by ROS, then log records that remove the index
are replayed against that table (such as drop index, or a
rollback of a create index), and then a takeover occurs
and the standby is shut down, DB2 may trap due to a stale
pointer. The db2diag.log will report a sigsegv and the
resulting trap file will show the following stack:
sqldUnchainGIXCB
sqldRemoveGIXCBsFromMasterChain
sqldDelTCBsInPoolLocal
sqldDelTCBsInPool
sqldTermDBCB |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Reads On Standby *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest fix pack. *
**************************************************************** |
| Local Fix: |
|
| Solution |
Problem is first fixed in DB2 UDB Version 10.5 fix pack 7. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.06.2015
20.01.2016
20.01.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
