home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC98018 Status: Geschlossen

IF A TABLE HAS DB2SECURITYLABEL COLUMN, ADMIN_MOVE_TABLE FAILED WITH
SQL0683N.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
You may fail to move table that has a DB2SECURITYLABEL column 
(row level security label) using ADMIN_MOVE_TABLE because 
if the user will return the following message. The message might 
be different on  different DB2 version or fixpack level. 
 
ADMIN_MOVE_TABLE failed with SQL0683N: 
SQL0683N  The specification for column, attribute, user-defined 
type or 
function "USER_SECURITY" contains incompatible clauses. 
SQLSTATE=42842 
 
If there's row level LBAC defined on the table, DB2 used to 
block the move table in ADMIN_MOVE_TABLE because if the user 
cannot access all rows in the LBAC table, the move may cause 
data loss. 
 
However, if the user id has all privileges to access all rows, 
and DBA is aware of that if the user cannot access all rows, the 
move may cause data loss, the APAR is to provide a new option 
ALLOW_RLBAC to allow the move data. 
The KEEP and ALLOW_RLBAC may be required to be specified 
together. 
 
For example, 
call 
admin_move_table('TEST','TAB1','newtbs','newtbs','newtbs','','', 
'','','ALLOW_RLBAC, COPY_USE_LOAD, KEEP','MOVE,TRACE') 
 
The original table will be renamed and kept in the table space 
so that the original table can be used for data recovery purpose 
in case data loss during move due to access permission.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4.                      * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
First fixed in Version 10.5 Fix Pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.11.2013
08.09.2014
08.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList