home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC99740 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
Lösung
upgrade to DB2 v101 fixpack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.02.2014
13.07.2015
13.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList