Latest versionsfixlist
11.1.0.7 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

DB2 - Problem description

Problem IC89749 Status: Closed

DB2 SERVER MAY TERMINATE ABNORMALLY WHEN ROWID IS REFERENCED IN A TRIGGER

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
SQL1224N may be returned when ROWID is referenced in a compiled 
trigger. 
 
The execution returns SQL1224N instead of SQL0206N, as a trap is 
encountered. The stack in the trap file may appear similar to: 
 
sqlnq_handle_rid_bit 
sqlnq_resolve_as_pseudocolumn 
sqlnq_sem_col_ref 
sqlnq_sem 
sqlnp_smactn 
sqlnp_parser 
sqlnp_main 
sqlnn_cmpl 
...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to v10.1 Fix Pack 3                                   * 
****************************************************************
Local Fix:
If the corresponding inline trigger returns SQL206N, avoid 
referencing ROWID in the compiled trigger because the 
specification of ROWID is invalid anyway.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem first fixed in v10.1 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.01.2013
21.10.2013
21.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList