|
Problem IC91229
|
Status: Closed |
SQL FUNCTION DEFINER NOT GIVEN WITH GRANT OPTION (CAN LEAD TO ERRORS LIKE SQL0551N ON LATER GRANT) |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The definer of a SQL function should be given the WITH GRANT
OPTION on the function if the definer has
WITH GRANT OPTION on all privileges required to define the
function, or if the definer has SYSADM
or DBADM authority. However, if all of the following conditions
are true, the definer is incorrectly
given only EXECUTE privilege without the WITH GRANT OPTION:
- The SQL function is inlined
- The function definer does not have SYSADM or DBADM authority
- SQL function body references one or more procedures
- The function definer has the WITH GRANT OPTION on all
referenced procedures
This can lead to errors like SQL0551N when trying to GRANT
privileges on such a function.
With the conditions above all true you would see that the
created function privileges
in SYSCAT.ROUTINEAUTH would show a 'Y' for the 'EXECUTEAUTH'
column instead of a 'G'. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 fix pack 3 *
**************************************************************** |
| Local Fix: |
Explicitly grant EXECUTE privilege WITH GRANT OPTION to the
function definer |
| available fix packs: |
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 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.04.2013
07.10.2013
07.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
