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 IC95211 Status: Closed

CREATE TYPE STATEMENT FAILS WITH -104 WHEN USING A QUALIFIED OBJECTTYPE
VALUE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
For example, the following statement 
 
CREATE TYPE myschema.objtyp AS OBJECT ( c1    NUMBER, c2 
VARCHAR2(10) ) 
 
Will fail with the following error. 
 
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 "CREATE TYPE MYSCHEMA.obj" was 
found following 
"BEGIN-OF-STATEMENT".  Expected tokens may include: 
"<collection_derived_table>".  SQLSTATE=42601 
 
This is a case for all other uses of "create type as " including 
'as TABLE' 'as VARRAY'
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 3.                      * 
****************************************************************
Local Fix:
As a workaround, the current schema can be set first: 
 
set current schema myschema 
 
Then issue the same create statement with an unqualified 
objectype parameter: 
 
CREATE TYPE objtyp AS OBJECT ( c1    NUMBER, c2    VARCHAR2(10) 
)
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
This problem is first fixed in DB2 Version 10.5 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
27.02.2014
27.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList