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

Function execution blocked with SQL0551N when invoked with
authenticated group from non-catalog database partition

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The following SQL0551N can be returned when a function from 
non-catalog database partition is invoked even if it is 
correctly authenticated on EXECUTE by group to which the 
requester id belongs. 
 
SQL0551N "USERXXXX" does not have the privilege to perform 
operation "EXECUTE" on object "SCHEMAXXX.FUNCTIONXXX". 
SQLSTATE=42501
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Multi-partitioned db user                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The SQL0551N can be returned when a function fromnon-catalog * 
* database partition is invoked even if it iscorrectly         * 
* authenticated on EXECUTE by group to which therequester id   * 
* belongs.                                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 9.7 FixPak 2                          * 
****************************************************************
Local Fix:
There are several workaround available - they should all be 
noted here explicitly, such as: 
- Execute from catalog node. 
- Grant explicit privilege to the user themselves 
- Executing the exact same SQL which invokes the function on the 
catalog node first, *may* allow non-catalog nodes to 
successfully execute as well.
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.7 FixPak 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.01.2010
25.05.2010
25.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList