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 IC63634 Status: Closed

DB2 SHOULD ALLOW A BEFORE TRIGGER TO REFERENCE A TRANSITION VARIABLE OF
A SECURITY LABEL COLUMN

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
SQL20094N will be returned when using a BEFORE TRIGGER to check 
the value of a security label column.  The SQL20094N should only 
be returned if we are trying to change the value of the security 
label column. 
 
This APAR will relax the restriction so that transition 
variable of security label column can be referenced in a BEFORE 
trigger. However, modification of such transition variable will 
continue to be blocked (and SQL20094N returned).
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users checking the value of a security label column          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQL20094N will be returned when using a BEFORE TRIGGER       * 
* tocheck the value of a security label column.  The           * 
* SQL20094Nshould only be returned if we are trying to change  * 
* thevalueof the security label column.This defect will relax  * 
* therestriction so that transition variable of security       * 
* labelcolumn can be referenced in a BEFORE trigger.           * 
* However,modification of such transition variable will        * 
* continue to beblocked (and SQL20094N returned).              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 FP2 or newer                             * 
****************************************************************
Local Fix:
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
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.10.2009
25.05.2010
25.05.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