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

SQL SCALAR, TABLE AND ROW FUNCTIONS MISS WITH GRANT PRIVILEGE FOR THE
CREATOR IN A NON-RESTRICTIVE DATABASE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
For a normal database (non-restrictive), at database creation 
time, in DB2 version 9.7 PUBLIC has EXECUTE with GRANT option on 
353 system 
routines. While in DB2 version 10.1, PUBLIC only has EXECUTE, 
but not the 
GRANT option. 
 
This becomes a problem when an user (e.g. dbusr1) creates 
functions that call system routines (e.g. EXPLAIN_GET_MSG). 
 
For example, if dbusr1 has EXECUTE on EXPLAIN_GET_MSG through 
PUBLIC only, and db2usr1 creates a function P1 which calls 
EXPLAIN_GET_MSG, then in DB2 version 9.7, dbusr1 would have 
EXECUTE with GRANT option on P1 (because dbusr1 has EXECUTE with 
GRANT on routines that P1 depends on, namely EXPLAIN_GET_MSG). 
 
However, in DB2 version 10.1, dbusr1 only has EXECUTE on 
EXPLAIN_GET_MSG (without GRANT option), so therefore dbusr1 
would only have EXECUTE privilege on P1, and he would not be 
able to grant EXECUTE to other users. 
 
This only impacts SQL scalar, table and row functions, but not 
external functions or procedures.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

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