DB2 - Problem description
Problem IC62897 | Status: Closed |
SQL0901N MAY BE ISSUED COMPILING AN UPDATE OF A UNION ALL VIEW THAT HAS A DATA-PARTITIONED TABLE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
SQL0901N may be issued during compilation of an UPDATE on a UNION ALL view (UAV) that has a data-partitioned table (DPT) in one of its legs. The following additional conditions must be satisfied for this to occur: - At least one leg of the UAV is a simple base-table (has no distribution keys associated with it) - The database instance is serial - Only part of the DPT's partitioning key columns are updated in the UPDATE statement The SQL0901N issued will be: SQL0901N The SQL statement failed because of a non-severe system error. Subsequent SQL statements can be processed. (Reason "column number out of range".) SQLSTATE=58004 The stack trace from the SQL0901N may look something like: sqlnq_ftb::num2fcs sqlnq_qun::change_to_lower_box sqlnr_upddelpd_action sqlnr_comp sqlnr_seq sqlnr_rcc sqlnr_magic_detail_action ... | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * EE or EEE * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 1. * **************************************************************** | |
Local Fix: | |
Alter the CURRENT QUERY OPTIMIZATION special register or the dft_queryopt database configuration parameter to a value less than 5. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 Version 9.7 Fix Pack 1. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC68934 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 31.08.2009 19.02.2010 19.02.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |