DB2 - Problem description
Problem IT30256 | Status: Closed |
SQL0901N MAY BE RETURNED FOR QUERIES WITH UNION REFERENCING NODENUMBER/DBPARTITIONNUM FUNCTIONS | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
A query may return SQL0901N when the following conditions are satisfied: 1. The query involves a UNION (could also be via view with UNION or full outer join, EXCEPT or INTERCEPT which the compiler will generate a UNION for), and 2. At least one branch below the UNION applies a NODENUMBER or DBPARTITIONNUM function The following is the error stack when the SQL0901N is returned: sqlnn_cmpl[380] sqlno_exe[900] sqlno_planning_phase[200] sqlno_planning_scan[400] sqlno_scan_utils_qgm[200] sqlno_each_qur[400] sqlno_top_qtb[100] ... sqlno_walk_qun[100] sqlno_each_opr[1200] sqlno_plan_end_opr[1700] sqlno_crule_mate[100] sqlno_itr_plan::next[300] SQL0901N The SQL statement or command failed because of a database system error. (Reason "sqlno_itr_plan::next [300]:rc(-2144272209) No plan found. ".) SQLSTATE=58004 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 11.1 Modification 4 FixPack 5 or * * later * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT19243 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.09.2019 26.02.2020 26.02.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |