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

DB2LOOK -XD DOES NOT GENERATE GRANTS FOR AUTHORIZATIONS IMPLICITLY GIVEN ON
THE OBJECT

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
$ db2 "select grantee from syscat.indexauth where 
indname='TAB_COMP_INFO_PK' and CONTROLAUTH='Y'" 
 
GRANTEE 
---------------------------------------------------------------- 
-------- 
-------------------------------------------------------- 
X793189 
DB2CCGU1 
 
  2 record(s) selected. 
 
DB2CCGU1 is the definer, so it got this permission 
automatically. 
However in db2look I am using the ?-xd? option which is supposed 
to generate the DDL for the original definer and it is not doing 
so. 
It is generating the grant DDL for the grant which has been 
executed explicitly. 
 
$ db2look -d ccgidsu1 -xd | grep -i x793189 
-- No userid was specified, db2look tries to use Environment 
variable USER 
-- USER is: DB2CCGU1 
GRANT CONTROL ON INDEX "DBA     "."TAB_COMP_INFO_PK" TO USER 
"X793189 ";
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 6                               * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 10.1 Fix Pack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.10.2016
02.03.2017
02.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)