|
Problem IC89695
|
Status: Closed |
SQL20005N WHEN CREATING TYPES EVEN THOUGH LIMIT HAS NOT BEEN REACHED. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When creating new types in DB2, it is possible that a SQL20005N
error occurs, even though the maximum number of types allowed in
the database was not reached.
SQL20005N The internal identifier limit of "<limit>" has been
exceeded
for object type "<object-type>".
DB2 has a limit on the maximum TYPEID value that is allowed in
the database. When a new type is created DB2 will generate a
new TYPEID based on the value of the largest TYPEID that is
already in the database.
If types are dropped/altered/inserted many times in a
development environment (for example), it is possible that the
TYPEID values go out of sync. When that happens some TYPEID
values get lost and do not get reused. As such it is possible
that the database system has the capacity for more types but the
maximum value for the TYPEID was reached so DB2 returns an error
message.
DB2 should allow a little more than 28000 types in the database. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1, Fix pack 3 *
**************************************************************** |
| Local Fix: |
If possible, drop all the types in the database, and then
recreate them one at a time. That will ensure each TYPEID will
be in proper sync. |
| 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 :
| 22.01.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
|
 |
| 10.1.0.3
|
|
