DB2 - Problem description
Problem IC91715 | Status: Closed |
SYSPROC.REORGCHK_IX_STATS STORED PROCEDURE CALL FROM A CLI APPLICATION FAILS WITH SQL0440N | |
product: | |
DB2 CONNECT / DB2CONNCT / A10 - DB2 | |
Problem description: | |
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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users using CLI driver based applications * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 10.1 Fix Pack 3 or higher * **************************************************************** | |
Local Fix: | |
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> | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 V10.1 Fix Pack 3 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC92357 IC95309 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.04.2013 27.09.2013 27.09.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 |