|
Problem IC63289
|
Status: Closed |
UNEXPECTED ERRORS CAN OCCUR WHEN REFERENCING A USER-DEFINED TYPE WITH THE SAME NAME AS A TYPE IN ANOTHER SCHEMA. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
An unexpected error can occur when referencing a user-defined
type with the same name as a type in another schema. The error
would be:
- an SQL0100W and statement failure, or
- an SQL1224N error, or
- no error may be reported, but expected type revalidation does
not occur.
To encounter one of these problems, the following general
conditions must be met:
- multiple types must exist in SYSCAT.DATATYPES with the same
TYPENAME, one of which is the type being referenced, and
- the type being referenced must not be qualified with a schema.
In addition to the general conditions, an SQL0100W error will be
reported when:
- the DB2 instance is using the Database Partitioning Feature,
and
- the type being referenced has the same name as a built-in type
that can not be directly referenced by the user (for example,
types in the SYSIBMADM schema).
In addition to the general conditions, an SQL1224N error will be
reported when:
- the type being referenced is a Distinct or an Array type, and
the ANCHOR clause was not used in the CREATE TYPE statement, and
- some other type with a matching name is invalid
(SYSCAT.DATATYPES.VALID is 'N').
In addition to the general conditions, no error may be reported
but revalidation will fail to occur when:
- the type being referenced is invalid (SYSCAT.DATATYPES.VALID
is 'N'), and
- some other type with a matching name is valid
(SYSCAT.DATATYPES.VALID is 'Y') |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 UDB systems on Linux, Unix, and Windows platforms at *
* service levels on Version 9.7.0. *
****************************************************************
* PROBLEM DESCRIPTION: *
* An unexpected error can occur when referencing a *
* user-defined type with the same name as a type in another *
* schema. The error would be: *
* - an SQL0100W and statement failure, or *
* - an SQL1224N error, or *
* - no error may be reported, but expected type revalidation *
* does not occur. *
* *
* To encounter one of these problems, the following general *
* conditions must be met: *
* - multiple types must exist in SYSCAT.DATATYPES with the *
* same TYPENAME, one of which is the type being referenced, *
* and *
* - the type being referenced must not be qualified with a *
* schema. *
* *
* In addition to the general conditions, an SQL0100W error *
* will be reported when: *
* - the DB2 instance is using the Database Partitioning *
* Feature, and *
* - the type being referenced has the same name as a built-in *
* type that can not be directly referenced by the user (for *
* example, types in the SYSIBMADM schema). *
* *
* In addition to the general conditions, an SQL1224N error *
* will be reported when: *
* - the type being referenced is a Distinct or an Array type, *
* and the ANCHOR clause was not used in the CREATE TYPE *
* statement, and *
* - some other type with a matching name is invalid *
* (SYSCAT.DATATYPES.VALID is 'N'). *
* *
* In addition to the general conditions, no error may be *
* reported but revalidation will fail to occur when: *
* - the type being referenced is invalid *
* (SYSCAT.DATATYPES.VALID is 'N'), and *
* - some other type with a matching name is valid *
* (SYSCAT.DATATYPES.VALID is 'Y') *
****************************************************************
* RECOMMENDATION: *
* Upgrade to product version 9.7 fix pack 1. *
**************************************************************** |
| Local Fix: |
Qualify the type reference with a schema name. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.09.2009
21.12.2009
21.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
