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

A SQL0779N ERROR MIGHT BE RETURNED IF LABEL IS FOLLOWED BY ONE OF THE ARRAY
COLLECTION METHODS.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Under rare conditions a SQL0779N error might be return if label 
specified in GOTO statement is followed by array collection 
method 
TRIM/DELETE/EXTEND. 
The following example illustrates the problem. 
 
declare 
 TYPE tArray IS TABLE OF VARCHAR2(10); 
 Arr1 tArray; 
begin 
  GOTO LABEL1; 
  <<LABEL1>> 
  Arr1.delete; 
end; 
 
This situation might also occur in case of label being followed 
by assignment of DBMS function like DBMS_SQL.OPEN_CURSOR 
mycur := DBMS_SQL.OPEN_CURSOR ;
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2 luw                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to DB2 v101 fixpack 5                                * 
****************************************************************
Local Fix:
Please make sure that label is not followed by array collection 
methods.
Solution
upgrade to DB2 v101 fixpack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.02.2014
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList