DB2 - Problembeschreibung
Problem IC91715 | Status: Geschlossen |
SYSPROC.REORGCHK_IX_STATS STORED PROCEDURE CALL FROM A CLI APPLICATION FAILS WITH SQL0440N | |
Produkt: | |
DB2 CONNECT / DB2CONNCT / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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> | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 V10.1 Fix Pack 3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC92357 IC95309 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 22.04.2013 27.09.2013 27.09.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |