home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC63246 Status: Closed

SQL0901N OCCURS INSERTING OR UPDATING A LBAC PROTECTED ROW WITH A BEFORE
TRIGGER THAT MODIFIES A NEW TRANSITION VARIABLE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
An INSERT or UPDATE into an LBAC protected row that fires a 
BEFORE TRIGGER containing a SET statement that modifies a new 
transition variable will result in an SQL0901N. 
 
There is no proper workaround, but we can either (1) don't use 
LBAC on the table or (2) don't use SET statement that modifies 
new transition variable in before trigger.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of LBAC on tables with a BEFORE TRIGGER                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* An INSERT or UPDATE into an LBAC protected row that fires    * 
* a BEFORE TRIGGER containing a SET statement that modifies    * 
* anew transition variable will result in an SQL0901N. There   * 
* is no proper workaround, but we can either (1) don't use     * 
* LBAC                                                         * 
* on the table or (2) don't use SET statement that modifies    * 
* new                                                          * 
* transition variable in before trigger.                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 FP2 or newer.                            * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
Upgrade to DB2 v9.7 FP2 or newer.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.09.2009
14.07.2010
14.07.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList