DB2 - Problem description
Problem IC63245 | Status: Closed |
SQL0901N OCCURS INSERTING OR UPDATING AN LBAC PROTECTED ROW WITH A BEFORE TRIGGER THAT MODIFIES A NEW TRANSITION VARIABLE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - 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 * * aBEFORE 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'tuse LBAC on * * the table or (2) don't use SET statement thatmodifies new * * transition variable in before trigger. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.5 FP6 or newer. * **************************************************************** | |
Local Fix: | |
N/A | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Solution | |
Upgrade to DB2 v9.5 FP6 or newer. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC63246 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.09.2009 21.09.2010 21.09.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) |