|
Problem IT35211
|
Status: Closed |
POSSIBLE SIGSEGV IN Q Replication due to incorrect log records for column-organized DGTT in DPF ENVIRONMENT
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
This problem only applies to Q Replication while using
the new feature to support replication of column-organized
tables, which requires setting internal register variable
DB2_CDE_DCC, on a source database in DPF
environment, and there are column-organized DGTT being
created.
On an instance set up for Q replication, capture might crash.
This is due to one global transaction that has two different
local transactions in each node, where one will be aborted and
the other committed. This may causes Q Replication Capture to
hit a segmentation violation (SIGSEVG)
The error messages in Q Replication capture log are similar to
the following
....
2020-09-03-16.01.40.039877
ASN8999D the local transaction 0000:1500:0000:0cc8:b61e cannot
be unchained because it has special flag set:
isNotificationQueued Y isCommitted Y
2020-09-03-16.01.40.039892
ASN8999D the local transaction 0000:1600:0000:0cca:91d1 cannot
be unchained because it has special flag set:
isNotificationQueued Y isCommitted Y
2020-09-03-16.01.40.039917
ASN8999D the local transaction 0000:1700:0000:0cc8:b6ee cannot
be unchained because it has special flag set:
isNotificationQueued Y isCommitted Y
2020-09-04-03.26.42.298574 ASN8053D "Q
Capture" : "QASN" : "LogrdThread" : Signal handler for signal
'SIGSEGV' successfully dumped stack trace to file
'/head/bludr/logs/replication//db2inst1.KGORDOAY.QASN.QCAP.99549
.47838030481152.DUMP'
2020-09-04-03.26.42.298652 ASN0569E
"Q Capture" : "QASN" : "LogrdThread" : The program encountered
an internal error "SIGSEGV". The program will terminate.
2020-09-04-03.26.42.298707 ASN0591I "Q Capture"
: "QASN" : "LogrdThread" The thread "LogrdThread" received
"Handled" signal "SIGSEGV".
....
the pattern of these messages is that several messages of
"" followed by a sigsegv error
message. The sigsegv generates a dump file which will contain :
_ZN9sendQueue36removeTransIDFromListOfStreamedTransEPK5trans +
0x01d2 (/opt/ibm/db2/V11.5.0.0/bin/asnqcap)
0x0000000000555252 : 488B742408E953FE
-----FUNC-ADDR---- ------FUNCTION + OFFSET------
0x0000000000555252 [RSP]
_ZN9sendQueue36removeTransIDFromListOfStreamedTransEPK5trans +
0x01d2
(/opt/ibm/db2/V11.5.0.0/bin/asnqcap) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.5.5.1 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.5.5.1 or higher *
**************************************************************** |
| Comment |
Upgrade to Db2 11.5.5.1 or higher |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.12.2020
01.04.2021
01.04.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
