DB2 FOR LUW / DB2FORLUW / A10 - DB2

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'

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 Fixpack 3                               * 
****************************************************************

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) 
)

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
 

First fixed in DB2 v10.1 Fixpack 3

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC95211 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

17.01.2013
07.10.2013
07.10.2013