home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC84143 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
User affected: 
  Users of Informix wrappers in InfoSphere Federation Server 
Problem description and summay: 
  See error description
Local-Fix:
verfügbare FixPacks:
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

Lösung
Problem was fistly fixed in Version 10, FixPak 1. This 
fix should be applied on the federation Server.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.06.2012
01.11.2012
01.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList