DB2 - Problem description
Problem IT33554 | Status: Closed |
SQL0901N PARTITIONED BLU SORT WITH 0 PARTCOLS IS UNEXPECTED | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
An OLAP query may fail with with the following error message: SQL0901N The SQL statement or command failed because of a database system error. (Reason "PARTITIONED BLU SORT with 0 PartCols is unexpected.".) SQLSTATE=58004 An FODC_AppErr folder will get created, and the trap.txt file inside that folder will contain a stack like this: 0 ossDumpStackTraceInternal 1 ossDumpStackTraceV98 2 OSSTrapFile::dumpEx 3 sqlo_trce 4 sqloDumpDiagInfoHandler 5 __restore_rt 6 pthread_kill 7 sqloDumpEDU 8 sqldDumpContext 9 sqlrr_dump_ffdc 10 sqlzeDumpFFDC 11 sqlzeMapZrc 12 sqlnn_erdm 13 sqlnx_explain_plan 14 sqlnn_cmpl 15 sqlnn_cmpl 16 sqlra_compile_var 17 sqlra_find_var 18 sqlra_get_var 19 sqlrr_prepare 20 sqljs_ddm_prpsqlstt 21 sqljsParseRdbAccessed 22 sqljsParse 23 sqljsSqlam 24 sqljsDrdaAsInnerDriver 25 sqljsDrdaAsDriver 26 sqeAgent::RunEDU 27 sqzEDUObj::EDUDriver 28 sqloEDUEntry 29 start_thread 30 clone This error is more likely if the following two conditions are met in the query: 1. An "OLAP function" (eg DENSE_RANK() or RANK() or ROW_NUMBER()) is used. 2. The "PARTITION BY XXXXX" in the "OLAP function" is referenced as well. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Will be fixed in future fixpack/version. * **************************************************************** | |
Local Fix: | |
db2set -im DB2_REDUCED_OPTIMIZATION=DISABLE_FDS If you prefer not to apply an instance wide parameter, you can use the following Optimization Guideline: /* */ | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT33544 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.07.2020 26.11.2020 26.11.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |