DB2 - Problem description
| Problem IC84578 | Status: Closed |
THE DB2_ALL COMMAND MAY FAIL WITH A KSH SYNTAX ERROR WHEN SINGLE QUOTES APPEAR IN THE COMMAND. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
Problem Description:
In DPF environment the db2_all command may fail with a ksh
syntax error when a single quote appears within single quotes.
For example :
db2_all "db2 'values(current DBPARTITIONNUM)' "
ksh: 0403-057 Syntax error at line 1 : `(' is not expected.
ksh: 0403-057 Syntax error at line 1 : `(' is not expected.
ksh: 0403-057 Syntax error at line 1 : `(' is not expected.
ksh: 0403-057 Syntax error at line 1 : `(' is not expected.
ksh: 0403-057 Syntax error at line 1 : `(' is not expected.
ksh: 0403-057 Syntax error at line 1 : `(' is not expected. | |
| Problem Summary: | |
****************************************************************
* USERS AFFECTED: *
* DPF customer using a single quote in db2_all command. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Problem Description: *
* In DPF environment the db2_all command may fail with a ksh *
* syntax error when a single quote appears within single *
* quotes. *
* For example : *
* *
* db2_all "db2 'values(current DBPARTITIONNUM)' " *
* ksh: 0403-057 Syntax error at line 1 : `(' is not expected. *
* ksh: 0403-057 Syntax error at line 1 : `(' is not expected. *
* ksh: 0403-057 Syntax error at line 1 : `(' is not expected. *
* ksh: 0403-057 Syntax error at line 1 : `(' is not expected. *
* ksh: 0403-057 Syntax error at line 1 : `(' is not expected. *
* ksh: 0403-057 Syntax error at line 1 : `(' is not expected. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.1 FP2. *
**************************************************************** | |
| Local Fix: | |
Possible workarounds are : 1. db2_all "db2 values\(current DBPARTITIONNUM\) " or 2. db2_all 'db2 "values(current DBPARTITIONNUM)" ' | |
| Solution | |
Fixed included in DB2 10.1 FP2. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.06.2012 06.11.2012 06.11.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |