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

ADMIN_MOVE_TABLE DOESN'T RECREATE THE SECURITY LABEL ON A COLUMN

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Customer has a table with security label on a column. 
 
After execute ADMIN_MOVE_TABLE stored procedure the table was 
moved but without the security label on column.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4                       * 
****************************************************************
Local Fix:
Manually create a target table with the same definition of the 
source table and then run ADMIN_MOVE_TABLE with the target table 
approach, for example, 
CALL 
ADMIN_MOVE_TABLE('TEST','TAB1','TAB1T','COPY_USE_LOAD,KEEP','MOV 
E'); 
For more information, see 
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.i 
bm.db2.luw.sql.rtn.doc/doc/r0055069.html
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in Version 10.1 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.11.2013
02.06.2014
02.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList