Latest versionsfixlist
11.1.0.6 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC66900 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 / 950 - 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      * 
* ONUPDATE 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 newtransition variable from T- A value has   * 
* been provided in the INSERT/UPDATE statementfor column RCTS  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.5 fp6 or use the temporary fix.             * 
****************************************************************
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.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Db2 9.5 fp6
Workaround
- 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
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67198 IC68346 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.03.2010
31.05.2010
31.05.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.