suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT20871 Status: Closed

DB21034E OCCURS FOR "SELECT" SQL STATEMENTS STARTING WITH BLOCK
COMMENTS THROUGH CLP

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
When a block comment containing slash sign(s) '/' is inserted at 
the beginning of a statement, the following SELECT SQL fails 
with DB2 CLP. 
 
$ db2 -tvf jt_bad.sql 
/*************************************************************** 
**************** Script Name : Comment Block Date : 
23/02/2016 
**************************************************************** 
****************/ select  1 from sysibm.sysdummy1 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0084N  An EXECUTE IMMEDIATE statement contains a SELECT or 
VALUES 
statement.  SQLSTATE=42612
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               * 
****************************************************************
Local Fix:
You can do one of the following options as a workaround. 
 
1? Remove the slash '/' inside comment block 
 
$ db2 -tvf jt_good_1.sql 
/*************************************************************** 
**************** Script Name : Comment Block Date : 
23-02-2016 
**************************************************************** 
****************/ select  1 from sysibm.sysdummy1 
 
1 
----------- 
          1 
 
  1 record(s) selected. 
 
2? Insert another statement before the SELECT query 
 
$ db2 -tvf jt_good_2.sql 
/*************************************************************** 
**************** Script Name : Comment Block Date : 
23/02/2016 
**************************************************************** 
****************/ set current schema = 'JIANTANG' 
DB20000I  The SQL command completed successfully. 
 
select  1 from sysibm.sysdummy1 
 
1 
----------- 
          1 
 
  1 record(s) selected.
available fix packs:
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in DB2 11.1 Mod 2 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.06.2017
23.06.2017
23.06.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)