home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC90349 Status: Closed

SQL0104N WHEN CREATING A VARIABLE CALLED PIPE IN PL/SQL STATEMENT

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The following SQL statement will return an SQL0104N (syntax 
error): 
 
db2 "create or replace package test is pipe constant char(10) := 
'blah'; end" 
 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
SQL0104N  An unexpected token "pipe" was found following "create 
or replace package test is pipe constant char(10) := 'bla". 
Expected tokens may include:  "".  LINE NUMBER=1. 
SQLSTATE=42601 
 
 
The problem will only occur if the variable is named "pipe".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1, Fix pack 3                      * 
****************************************************************
Local Fix:
Use a different name for the variable or use delimited 
identifier "PIPE" as variable name .   Example: 
 
db2 "create or replace package test is pipe1 constant char(10) 
:= 'blah'; end" 
or 
 
db2 "create or replace package test is "PIPE" constant char(10) 
:= 'blah'; end"
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1, Fix pack 3
Workaround
see Local Fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.02.2013
17.10.2013
17.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList