|
Problem IT18831
|
Status: Closed |
OUTPUT OF SELECT STATEMENT IS DUPLICATED TWICE IN SPOOL OUTPUT FILE WHEN TRIMSPOOL IS SET TO ON IN CLPPLUS
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
In clpplus, output records from a select statement to the spool
file are duplicated twice.
This happened when TRIMSPOOL was set to ON and the select
statement returned data for one column.
Example of this problem:
$ clpplus e105q8a/password@localhost:60432/SAMPLE -nw
CLPPlus: Version 1.6
Copyright (c) 2009, 2011, IBM CORPORATION. All rights reserved.
Database Connection Information :
---------------------------------
Hostname = localhost
Database server = DB2/AIX64 SQL10058
SQL authorization ID = e105q8a
Local database alias = SAMPLE
Port = 60432
SQL> set trimspool on
SQL> spool clpplus_1.log
SQL> select actkwd from act;
ACTKWD
------
MANAGE
ECOST
DEFINE
LEADPR
SPECS
LOGIC
CODE
TEST
ADMQS
TEACH
COURSE
STAFF
OPERAT
MAINT
ADMSYS
ADMDB
ADMDC
DOC
18 rows were retrieved.
SQL> quit
$ cat clpplus_1.log
SQL>
ACTKWD
------
MANAGE
MANAGE
ECOST
ECOST
DEFINE
DEFINE
LEADPR
LEADPR
SPECS
SPECS
LOGIC
LOGIC
CODE
CODE
TEST
TEST
ADMQS
ADMQS
TEACH
TEACH
COURSE
COURSE
STAFF
STAFF
OPERAT
OPERAT
MAINT
MAINT
ADMSYS
ADMSYS
ADMDB
ADMDB
ADMDC
ADMDC
DOC
DOC
18 rows were retrieved.
SQL>
Note:
The each output rows may have a succeeding blank line instead
of duplicated lines as a variation of this problem. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* CLPPLus user. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 11.1 Mod 2 Fix Pack 2. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : IT18704
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.01.2017
17.10.2017
17.10.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
