DB2 - Problem description
Problem IC92016 | Status: Closed |
SQL0901 ERROR WHEN EXECUTING AN SQL STATEMENT ELIGIBLE FOR ZIGZAG JOIN STRATEGY | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
You might encounter an SQL0901 error with reason "Descriptor row length exceeds maximum allowed." and producing the following stack trace sqldCompleteTCBforDAT sqldCreateDAT sqldInternalCreateTable sqldTableCreateTemp sqlriCreateIndexedTempTable sqlritib sqlriExecThread sqlriZZOpenDims sqlriZZInit sqlriZigZagJoin sqlriExecThread sqlriSectInvoke when executing an SQL statement that fits the required criteria for a zigzag join and the combined size of the columns retrieved from any of the dimension tables is too large to fit in any temporary tablespace available. You can refer to the topic "Ensuring that queries fit the required criteria for the zigzag join" in the DB2 InfoCenter for details about the required criteria. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 Version 10.1 Fix Pack 3 * **************************************************************** | |
Local Fix: | |
db2set DB2_REDUCED_OPTIMIZATION="ZZJN OFF" OR Use optimization level 0 | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 Version 10.1 Fix Pack 3 | |
Workaround | |
See Local Fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.04.2013 27.09.2013 27.09.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |