DB2 - Problem description
Problem IC63633 | Status: Closed |
DB2 SHOULD ALLOW A BEFORE TRIGGER TO REFERENCE A TRANSITION VARIABLE OF A SECURITY LABEL COLUMN | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
When using a BEFORE TRIGGER to check the value of a security label column SQL20094N will be returned. 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: * * When using a BEFORE TRIGGER to check the value of a * * securitylabel column SQL20094N will be returned. The * * SQL20094Nshould only be returned if we are trying to change * * the valueof the security label column.This defect will relax * * the restriction so that transitionvariable of security label * * column can be referenced in aBEFORE trigger. However, * * modification of such transitionvariable will continue to be * * blocked (and SQL20094Nreturned). * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.5 FP6 or newer * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC63634 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.10.2009 14.05.2010 14.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) |