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

CLPPLUS DISPLAYS SERVER OUTPUT MESSAGES MULTIPLE TIMES.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
This is an issue in CLPPlus where it is not flushing the 
messages after writing it on to the console. 
 
For example, the following code 
---------- 
SQL> set serveroutput on 
SQL> begin 
2 for i in 1..30 loop 
3 dbms_output.put_line('Count '||i); 
4 end loop; 
5 end; 
6 / 
---------- 
 
Gives the following output: 
---------- 
Count 1 
<snip> 
Count 25 
Count 1 
<snip> 
Count 25 
Count 27 
Count 28 
Count 29 
Count 30 
DB250000I: The command completed successfully. 
SQL> 
---------- 
i.e. We see the first 25 lines duplicated. 
 
The reason for this is, CLPPlus fetches server output messages 
in a chunk of 25 at a time. After each fetch CLPPlus is supposed 
to clear the list of messages which are already displayed on the 
screen, but it fails to do so, hence we see the duplicate 
messages on screen after every fetch. 
 
N.B. The above example also shows APAR IC82246: Consecutive 
calls to DBMS_OUTPUT.GET_LINES() skips a line in between each 
call, since CLPPlus depends on DBMS_OUTPUT.GET_LINES procedure 
to retrieve the server output messages from buffer.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLPPlus users.                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 Fixpack 2                               * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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

Lösung
First fixed in DB2 v10.1 Fixpack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.11.2012
17.12.2012
17.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList