DB2 - Problem description
Problem IT26282 | Status: Closed |
UPDATE ON FULL TABLE WHICH USES SUB_SELECT COULD INCORRECTLY SET VALUES TO NULL FOR COLUMN BEING UPDATED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Update using a sub-select on the full table could incorrectly set column value to NULL. Single row update is correct and is setting a proper value for the column. The problem only exists in v11. example: update test1 t1 set col_a = (select t2.col_a from test2 t2 where t1.col_a = t2.col_a) col_a will be updated to NULL incorrectly. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * Please, see Error Description and install this Fix: v11 * * Fixpak 4. * **************************************************************** * RECOMMENDATION: * * Please, see Error Description and install this Fix: v11 * * Fixpak 4. * **************************************************************** | |
Local Fix: | |
db2set DB2COMPOPT=NO_UPDATE_COMP | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.09.2018 02.12.2018 02.12.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |