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

CALLING A STORED PROCEDURE FROM DB2 V9.7 FP 4 AND HIGHER FIXPACK LEVEL
DATABASE SERVER MAY HIT SQL0727N SQLCODE "-7" ERROR

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
In DB2  V9.7 FP 4 and higher, you may hit error similar to below 
when calling a stored procedure SQL0727N An error occurred 
during implicit system action type "5". Information returned for 
the error includes SQLCODE "-7", SQLSTATE "42601" and message 
tokens " |= :HV00082 :HI00082". SQLSTATE=56098.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V9.7 FP 4 and higher users on all Operating Systems      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 FP 3 or higher                          * 
****************************************************************
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 DB2 V10.1 FP 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2013
01.10.2013
01.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