DB2 - Problembeschreibung
Problem IT16112 | Status: Geschlossen |
A CORRELATED SCALAR SUBQUERY IN AN UPDATE STATEMENT MAY NOT CORRECTLY RETURN SQL0811N | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problembeschreibung: | |
A correlated scalar subquery in an UPDATE statement may not correctly return SQL0811N. SQL0811N The result of a scalar fullselect, SELECT INTO statement, or VALUES INTO statement is more than one row. Assuming 2 rows in table B will match the same row of A: Case 1) Expects success but SQL0811N is returned UPDATE TEST.A A SET COLUMN_B = (SELECT COLUMN_B FROM TEST.B B WHERE A.COLUMN_A=B.COLUMN_A FETCH FIRST 1 ROWS ONLY) ; Case 2) Expects SQL0811N but it succeeds UPDATE TEST.A_COL A SET COLUMN_B = (SELECT COLUMN_B FROM TEST.B_COL B WHERE A.COLUMN_A=B.COLUMN_A ORDER BY COLUMN_A FETCH FIRST 2 ROWS ONLY) ; | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 11.1 Fix Pack 1 * **************************************************************** | |
Local-Fix: | |
Workaround: db2set -im DB2COMPOPT=NO_UPDATE_COMP | |
verfügbare FixPacks: | |
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows | |
Lösung | |
Problem fixed in DB2 11.1 FP1 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.07.2016 20.12.2016 20.12.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
11.1.1.1 |