DB2 - Problem description
Problem IC87911 | Status: Closed |
CLPPLUS DISPLAYS SERVER OUTPUT MESSAGES MULTIPLE TIMES. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * USERS AFFECTED: * * CLPPlus users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v10.1 Fixpack 2 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 v10.1 Fixpack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.11.2012 17.12.2012 17.12.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.2 | |
10.5.0.2 |