DB2 - Problembeschreibung
Problem IT05719 | Status: Geschlossen |
UNDER RARE CIRCUMSTANCES, QUERY IN DPF ENVIRONMENT MIGHT HANG IN MERGING DIRECTED TABLE QUEUE (MDTQ) | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
In partitioned partitioned environment (or with INTRA_PARALELL=YES), query involving merging directed table queue (MDTQ) might hang due to specific data layout (skew). Receiving subsections will wait for any node in state: Subsection status = Waiting to receive on tablequeue Node for which waiting on tablequeue = Any node Tablequeue ID on which agent is waiting = <id_of_mdtq> and stack: sqloWaitEDUWaitPost sqkfChannel::WaitRecvReady sqkfChannel::ReceiveAnyBuffer sqlktrcv sqlkt_unpack_tuple whilst senders will await specific specific partition, e.g Subsection status = Waiting to send on tablequeue Node for which waiting on tablequeue = 10 Tablequeue ID on which agent is waiting = <id_of_mdtq> and stack: sqloWaitEDUWaitPost sqkfChannel::WaitSendReady sqkfChannel::isAnySendReady sqlkqsnd sqlktsnd sqlkt_pack_tuple sqlktins sqlritqb sqlriSectInvoke | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DPF/INTRA_PARALELL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 5 or higher. * **************************************************************** | |
Local-Fix: | |
In most situations, hang can be avoided by: DB2_SORT_AFTER_TQ=YES on global (db2set) or statement level (profile): <REGISTRY><OPTION NAME='DB2_SORT_AFTER_TQ' VALUE='YES'/></REGISTRY> | |
Lösung | |
Fixed in DB2 Version 10.1 Fix Pack 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 21.11.2014 13.07.2015 13.07.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.5 |