|
Problem IC67198
|
Status: Closed |
SQL407N RETURNED WHEN INSERTING INTO OR UPDATING TABLE WITH GENE RATED BY DEFAULT ROW CHANGE TIMESTAMP COLUMN AND BEFORE TRIGGER |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
SQL407N is returned upon INSERT/UPDATE on a table T where:
- T has a generated column (RCTS) defined as FOR EACH ROW ON
UPDATE AS ROW CHANGE TIMESTAMP
- Column RCTS is specified with GENERATED BY DEFAULT
- T has a corresponding BEFORE INSERT/UPDATE trigger
- The trigger body has a SET statement that modifies a new
transition variable from T
- A value has been provided in the INSERT/UPDATE statement for
column RCTS |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* SQL407N is returned upon INSERT/UPDATE on a table T where: *
* - T has a generated column (RCTS) defined as FOR EACH ROW ON *
* UPDATE AS ROW CHANGE TIMESTAMP *
* - Column RCTS is specified with GENERATED BY DEFAULT *
* - T has a corresponding BEFORE INSERT/UPDATE trigger *
* - The trigger body has a SET statement that modifies a new *
* transition variable from T *
* - A value has been provided in the INSERT/UPDATE statement *
* for column RCTS *
****************************************************************
* RECOMMENDATION: *
* First fixed in DB2 Version 9.7 Fix Pack 3. *
**************************************************************** |
| Local Fix: |
- Specify the DEFAULT keyword as the value for the ROW CHANGE
TIMESTAMP column in the INSERT/UPDATE statement.
- Do not specify an explicit value for the ROW CHANGE TIMESTAMP
column in the INSERT/UPDATE statement.
- Specify GENERATED ALWAYS, instead of GENERATED BY DEFAULT, for
the ROW CHANGE TIMESTAMP column |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Upgrade to DB2 Version 9.7 Fix Pack 3. |
| Workaround |
N/A |
| Comment |
N/A |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.03.2010
27.09.2010
27.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
