DB2 - Problembeschreibung
| Problem IC89606 | Status: Geschlossen |
CREATE TYPE STATEMENT FAILS WITH -104 WHEN USING A QUALIFIED OBJECTTYPE VALUE | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v10.1 Fixpack 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) ) | |
| verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
| Lösung | |
First fixed in DB2 v10.1 Fixpack 3 | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC95211 Nachfolger : | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 17.01.2013 07.10.2013 07.10.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 10.1.0.3 |
|
| 10.1.0.3 |
|