DB2 10.5 for Linux, UNIX, and Windows

INSERT, UPDATE, and DELETE (including MERGE) statement restrictions for column-organized tables

Some options on the INSERT, UPDATE, and DELETE statements are not supported for column-organized tables in DB2®Version 10.5.

The following items are not supported. The restrictions on column-organized tables also apply to views on one or more column-organized tables:

SELECT FROM INSERT / UPDATE / DELETE, when the target table of the INSERT, UPDATE, or DELETE statement is a column-organized table. As a result, there is no need to support the include-columns clause of the INSERT, UPDATE, and DELETE statements. That clause is supported only in cases where a select operation is run from the INSERT, UPDATE, or DELETE statement. Because the include-columns clause is not supported, the assignment-clause clause in a DELETE statement is not supported.
Triggers, when the subject table or the target of an INSERT, UPDATE, or DELETE statement that is in the body of the trigger is a column-organized table.
Positioned UPDATE or DELETE. That is, an UPDATE or DELETE WHERE CURRENT OF cursor-name, where the target table is a column-organized table. You cannot declare a cursor that can be updated or deleted when the outer fullselect includes a reference to a column-organized table.
SELECT...FOR UPDATE when the target table is a column-organized table.
Prior to DB2 Cancun Release 10.5.0.4, the MERGE statement when the target table is a column-organized table. As of DB2 Cancun Release 10.5.0.4, this restriction is lifted.
INSERT, UPDATE, or DELETE statement inside an atomic block when the target table is a column-organized table.
INSERT, UPDATE, or DELETE statement on a UNION ALL view when the UNION ALL view includes a column-organized table.
Extended indicator variable values of DEFAULT or UNASSIGNED in statements that are modifying column-organized tables.
Repeatable read (RR) and read stability (RS) isolation levels when the table that is scanned is a column-organized table. As a result, the WITH isolation-level clause of the INSERT, UPDATE, or DELETE statement accepts only the uncommitted read (UR) or cursor stability (CS) isolation level if the underlying table that is scanned is a column-organized table. Setting the cur_commit database configuration parameter to DISABLED for CS scans on column-organized tables is not supported. Additionally, if the ConcurrentAccessResolution CLI/ODBC keyword specifies CurrentlyCommitted for a CS scan on a column-organized table, an error is returned. As of DB2 Cancun Release 10.5.0.4, this restriction also applies to a MERGE statement that includes the WITH isolation-level clause.