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

SQL0101N ERROR FOR A CREATE NICK NAME STATEMENT, WHEN THE NUMBER OF CREATED
NICKNAMES EXCEEDS 3000

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When remote server has more than 3000 tables each of which has 
an index with the same name, SQL0101N would be hit when 
nicknames are created against all of those remote tables. 
 
create nickname n1 for s1."user1"."testsb" 
SQL0101N  The statement is too long or too complex. 
 
When more than 3000 nicknames are being created against the same 
remote table which has at least one index, this error would be 
hit too.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all platforms, all relational data sources                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v101fp3                                           * 
****************************************************************
Local Fix:
NA
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
v101fp3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.09.2013
31.10.2013
31.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 FixList
10.1.0.3 FixList