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

CREATE NICKNAME FAILED FOR AN INFORMIX TABLE WITH MORE THAN 2147483647 ROWS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Informix changes the type of nrows and npused from integer to 
float in informix.systables beginning from version 11.x. 
 
Here are the reproducing steps: 
 
set passthru <your_server> 
DB20000I  The SQL command completed successfully. 
 
select count(*) from user1.largetable 
 
(count(*)) 
----------------- 
      2180910240. 
 
  1 record(s) selected. 
 
update statistics for table user1.largetable 
DB20000I  The SQL command completed successfully. 
 
select tabid, tabtype, nrows, npused, rowsize FROM 
informix.systables where owner = 'user1' AND tabname = 
'largetable' for read only 
 
tabid tabtype nrows         npused        rowsize 
----  ------- ------------- ---------     ------- 
1111  T       +2.18091E+009 +8.55259E+006      1 
 
  1 record(s) selected. 
 
set passthru reset 
DB20000I  The SQL command completed successfully. 
 
create nickname NN_LARGETBALE for 
<your_server>."user1"."largetable" 
 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
SQL1822N  Unexpected error code "-1215" received from data 
source "<your_server>". Associated text and tokens are "Value 
exceeds limit of INTEGER precision".  SQLSTATE=560BD
Problem Summary:
User affected: 
  Users of Informix wrappers in InfoSphere Federation Server 
Problem description and summay: 
  See error description
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
Problem was fistly fixed in Version 10, FixPak 1. This 
fix should be applied on the federation Server.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.06.2012
01.11.2012
01.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList