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 IC77781 Status: Geschlossen

INCORRECT LINE NUMBER DISPLAYED IN ERROR MESSAGES WHEN ISSUING PL/SQL
CREATE TRIGGER STATEMENTS

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When a PL/SQL CREATE TRIGGER statement is used, the error 
messages for sqlcode -206 and -628 display incorrect line 
numbers.  The correct line number is displayed if an equivalent 
SQL PL CREATE TRIGGER statement is used.  Please see the 
scenarios below. 
---------------------------------------------------------------- 
 
create or replace trigger TRIG001 
instead of insert or update or delete on v1 
for each row 
when (2 > 1) 
declare v0 int := 0; 
begin 
   v0 := 10; 
end 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0628N  Multiple or conflicting keywords involving the "WHEN" 
clause are 
present.  LINE NUMBER=2.  SQLSTATE=42613 
====> should be line number 4 
 
create or replace trigger TRIG001 
before insert or update or delete on t1 
for each row 
when ( updating = TRUE ) 
declare v0 int := 0; 
begin 
   v0 := 10; 
end 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0206N  "UPDATING" is not valid in the context where it is 
used.  LINE NUMBER=2.  SQLSTATE=42703 
 
===> should be line number 4
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When a PL/SQL CREATE TRIGGER statement is used, the error    * 
*                                                              * 
* messages for sqlcode -206 and -628 display incorrect line    * 
*                                                              * 
* numbers.  The correct line number is displayed if an         * 
* equivalent                                                   * 
* SQL PL CREATE TRIGGER statement is used.  Please see the     * 
*                                                              * 
* scenarios below.                                             * 
*                                                              * 
* ------------------------------------------------------------ * 
* ----                                                         * 
*                                                              * 
*                                                              * 
* create or replace trigger TRIG001                            * 
*                                                              * 
* instead of insert or update or delete on v1                  * 
*                                                              * 
* for each row                                                 * 
*                                                              * 
* when (2 > 1)                                                 * 
*                                                              * 
* declare v0 int := 0;                                         * 
*                                                              * 
* begin                                                        * 
*                                                              * 
*   v0 := 10;                                                  * 
*                                                              * 
* end                                                          * 
*                                                              * 
* DB21034E  The command was processed as an SQL statement      * 
* because                                                      * 
* it was not a                                                 * 
*                                                              * 
* valid Command Line Processor command.  During SQL processing * 
* it                                                           * 
* returned:                                                    * 
*                                                              * 
* SQL0628N  Multiple or conflicting keywords involving the     * 
* "WHEN"                                                       * 
* clause are                                                   * 
*                                                              * 
* present.  LINE NUMBER=2.  SQLSTATE=42613                     * 
*                                                              * 
* ====> should be line number 4                                * 
*                                                              * 
*                                                              * 
*                                                              * 
* create or replace trigger TRIG001                            * 
*                                                              * 
* before insert or update or delete on t1                      * 
*                                                              * 
* for each row                                                 * 
*                                                              * 
* when ( updating = TRUE )                                     * 
*                                                              * 
* declare v0 int := 0;                                         * 
*                                                              * 
* begin                                                        * 
*                                                              * 
*   v0 := 10;                                                  * 
*                                                              * 
* end                                                          * 
*                                                              * 
* DB21034E  The command was processed as an SQL statement      * 
* because                                                      * 
* it was not a                                                 * 
*                                                              * 
* valid Command Line Processor command.  During SQL processing * 
* it                                                           * 
* returned:                                                    * 
*                                                              * 
* SQL0206N  "UPDATING" is not valid in the context where it is * 
*                                                              * 
* used.  LINE NUMBER=2.  SQLSTATE=42703                        * 
*                                                              * 
*                                                              * 
*                                                              * 
* ===> should be line number 4                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
This problem is fixed in DB2 Version 9.7 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.07.2011
07.12.2011
07.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList