DB2 - Problembeschreibung
Problem IT28616 | Status: Geschlossen |
pureScale - MON_GET_PKG_CACHE_STMT causes several sqleSubRequestRouter and sqlkdReceiveData probes messages in db2diag.log. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problembeschreibung: | |
We have a query calling MON_GET_PKG_CACHE_STMT (with the member parameter set to "-2" so that request is sent to all nodes). Moreover, that query also specifies "FETCH FIRST 1 ROWS ONLY" so that the query is satisfied when 1 row is returned. Since "-2" was specified the MON_GET_PKG_CACHE_STMT request is sent to all nodes. The local node returns its data and the table function closes due to the "FETCH FIRST 1 ROWS ONLY". In addition the app issuing this query immediately terminates; this termination results in a "STOP USING" interrupt being sent to all nodes. On a remote node by the time the app is initialized and the MON_GET request is passed to a subagent the STOP USING interrupt has arrived. The arrival of that interrupt is detected and the probes are written out and the MON_GET request is aborted. This is highly timing sensitive; it only occurs if the STOP USING interrupt arrives before the subagent receives the MON_GET request for processing. This scenario keeps repeating as DMS keeps running the query in the manner described above. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local-Fix: | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 29.03.2019 16.01.2020 16.01.2020 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version |