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 IC88321 Status: Geschlossen

SQL0413N MAY BE RETURNED WHEN QUERYING AGAINST SYSIBMADM.DBA_IND EXES OR
SYSIBMADM.DBA_IND_PARTITIONS IF FULLKEYCARD IS 0

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When you have oracle compatibility mode turned on and have a 
table that has fullkeycard of zero, you may receive SQL0413N if 
you try to query against table SYSIBMADM.DBA_INDEXES. Also, when 
you have a partitioned index that has fullkeycard of zero, you 
will receive SQL0413N if you query against table 
SYSIBMADM.DBA_IND_PARTITIONS. 
 
For example, 
db2set DB2_COMPATIBILITY_VECTOR=ORA 
db2 "CREATE TABLE foo(a int)" 
db2 "CREATE INDEX i on foo(a)" 
db2 "RUNSTATS ON TABLE db2user.foo ON KEY COLUMNS AND 
INDEXES ALL" 
db2 "SELECT * FROM SYSIBMADM.DBA_INDEXES" 
SQL0413N  Overflow occurred during numeric data type conversion. 
 
or 
 
db2set DB2_COMPATIBILITY_VECTOR=ORA 
db2 "CREATE TABLE foo(a INT)  PARTITION BY RANGE (a) (STARTING 
FROM (1) ENDING AT (100) EVERY (20))" 
db2 "CREATE INDEX i ON foo(a) PARTITIONED" 
db2 "RUNSTATS ON TABLE db2user.foo ON KEY COLUMNS AND 
INDEXES ALL " 
db2 "SELECT * from SYSIBMADM.DBA_INDEXES" 
SQL0413N  Overflow occurred during numeric data type conversion.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users running servers on DB2 Version 10.1 on platforms   * 
* Linux, Unix and Windows.                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 Version 10.1 and Fix Pack 2                    * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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 first fixed in DB2 Version 10.1 and Fix Pack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.11.2012
25.01.2013
25.01.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList