DB2 FOR LUW / DB2FORLUW / A50 - DB2

SYSPROC.REORGCHK_IX_STATS stored procedure call from a CLI 
application fails with: 
 
"SQL0440N No authorized routine named "GET_INDEX_COLNAMES" of 
type "FUNCTION" having compatible arguments was found. 
SQLSTATE=42884" 
 
It works from Command Line Processor without any issues. 
 
Since CURRENT PATH is an updatable special register, the 
REORGCHK_IX_STATS procedure inherits the user's setting.  CLI 
must qualify all references to built-in SYSIBM, SYSPROC, SYSFUN 
and SYSIBMADM objects to get consistent behavior. 
 
This APAR fixes this problem.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using CLI driver based applications                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 10.5 Fix Pack 3 or higher                         * 
****************************************************************

Using the CurrentFunctionPath keyword should avoid this problem. 
 
 
For example, modifying the db2dsdriver.cfg as follows should 
avoid this problem: 
 
<configuration> 
    <dsncollection> 
        <dsn alias="SAMPLE" name="SAMPLE" host="ADMINIB-7025GJS" 
port="50000"> 
            <parameter name="Authentication" value="Server"/> 
            <parameter name="CurrentFunctionPath" 
value="SYSIBM,SYSPROC,X"/> 
        </dsn> 
    </dsncollection> 
</configuration>

DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

First fixed in DB2 V10.5 Fix Pack 3

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

27.08.2013
27.02.2014
27.02.2014