|
Problem IC65821
|
Status: Closed |
DB2 CLP DOES NOT SUPPORT THE <CR> CHARACTER (0X0D) AT THE LAST AND SECOND LAST POSITION OF CLP STATEMENT. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
1) To input the carriage return character, press (Ctrl+V+M) or
(Ctrl+V)+(Ctrl+M) or (Ctrl+V)+Enter. (In vi editor or on prompt)
2) In db2 prompt mode, create and drop a table which contains
the carriage return character. The table name should be quoted.
db2 => create table "tab1^M" (c1 int)
DB20000I The SQL command completed successfully.
db2 => drop table "tab1^M"
DB21034E The command was processed as an SQL statement
because it was not a valid Command Line Processor command.
During SQL processing it returned:
SQL0010N The string constant beginning with ""tab1" does not
have an ending string delimiter. SQLSTATE=42603
3) The table can't be dropped in shell command prompt
=> db2 'drop table "tab1^M"'
DB21034E The command was processed as an SQL statement
because it was not a valid Command LIne Processor command.
During SQL processing it returned:
SQL0204N "IIDEV22.tab1^M" is an undefined name.
SQLSTATE=42704
[1192] [iidev22@db2esv39] /home2/iidev22/sqllib/db2dump
=> db2 "drop table \"tab1^M\""
DB21034E The command was processed as an SQL statement
because it was not a valid Command Line Processor command.
During SQL processing it returned:
SQL0010N The string constant beginning with ""tab1" does not
have an ending string delimiter. SQLSTATE=42603
4) This issue is not reproducible on Windows, because we can't
type ^M(ctrl+V+M) on windows. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of the DB2 CLP *
****************************************************************
* PROBLEM DESCRIPTION: *
* The DB2 Command Line Processor (CLP) does not support the *
* 'carriage return' character (x'0D') in the last or second *
* last position of a CLP statement. The command will fail with *
* a DB21034E and SQL0100N errors. *
****************************************************************
* RECOMMENDATION: *
* Workaround is to put the commands in a script and execute: *
* db2 -tvf <script_name> *
**************************************************************** |
| Local Fix: |
Local Fix: Put the commands in a script and execute
db2 -tvf <script_name> |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 v9.5 FP6 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.01.2010
19.07.2010
19.07.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
