DB2 - Problembeschreibung
Problem IC99490 | Status: Geschlossen |
DB2 MIGHT PRODUCE SQL0551N WHEN CREATING A COMPILED ROUTINE OR TRIGGER REFERENCING DGTT | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
Under rare scenarios, DB2 might produce SQL0551N error message when all the of conditions below are true: 1) The command being executed is during creation of function, procedure or trigger 2) The body of this object contains a CTE referencing a declared global temporary table (DGTT) 3) The command was executed by a user with non-dbadm priviledges Example: DECLARE GLOBAL TEMPORARY TABLE SESSION.DGTT1 ( c1 int, c2 int ) WITH REPLACE ON COMMIT PRESERVE ROWS NOT LOGGED IN userspace; CREATE or replace PROCEDURE proc1() LANGUAGE SQL MODIFIES SQL DATA DYNAMIC RESULT SETS 1 BEGIN -- Local Variables Declaration DECLARE CUR CURSOR WITH RETURN TO CALLER FOR WITH CTE AS ( SELECT c1, c2 FROM SESSION.DGTT1 where c1 > 10 ) SELECT * FROM CTE WITH UR; ...... END | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 4 * **************************************************************** | |
Local-Fix: | |
Workaround: 1) Execute the command as dbadm 2) Modify the procedure text to inline the CTE | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 10.1 Fix Pack 4 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC99509 IC99510 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 19.02.2014 02.06.2014 02.06.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.4 |