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

UNCATALOGED STORED PROCEDURE CALLS FROM APPLICATION FAIL INTERMITTENTLY
WITH SQL CODE -9999

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Uncataloged Stored Procedure calls from application fail 
intermittently with SQL CODE -9999 
The error is seen in the application logs only and its not 
dumped in db2diag.log 
[IBM][CLI Driver][DB2/AIX64] SQL9999N Placeholder sqlcode for 
development use only. Must be cha nged before code is shipped. 
Generic 
tokens: "Routine definition has changed. Please run 
db2updv10", "", "". SQLSTATE=ZZZZZ 
 
db2updv10 does not resolve the issue.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V10.1                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 FP3                                     * 
****************************************************************
Local Fix:
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 V10.1 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.11.2012
04.10.2013
04.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 FixList
10.1.0.3 FixList