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

LOAD/IMPORT REPLACE INTO A TABLE WITH LBAC/RCAC REQUIRES CONTROL/DBADM
AUTHORITY

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
If a table has LBAC or RCAC rules defined, the user ID that 
performs a LOAD REPLACE or IMPORT REPLACE requires the authority 
to drop the table, i.e. CONTROL authority for the table or DBADM 
authority for the database. Even though the user ID may have 
DELETE authority for the table, it cannot be assumed that the 
user ID has access to all rows in the table, and therefore, it 
does not imply the user can remove all rows in the table. 
 
If this requirement is unacceptable due to the organization's 
security policies, please contact DB2 Support for further 
assistance.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 v10.5 Fix Pack 7                               * 
****************************************************************
Local Fix:
N/A
Solution
Fixed in DB2 v10.5 Fix Pack 7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.05.2015
20.01.2016
20.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList