DB2 - Problem description
Problem IC88321 | Status: Closed |
SQL0413N MAY BE RETURNED WHEN QUERYING AGAINST SYSIBMADM.DBA_IND EXES OR SYSIBMADM.DBA_IND_PARTITIONS IF FULLKEYCARD IS 0 | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * 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: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.11.2012 25.01.2013 25.01.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.2 | |
10.5.0.2 |