|
Problem IT20949
|
Status: Closed |
SQL0901N WHEN SAP MEMORY TABLE JOINS WITH UNION DISTINCT HAVING JOIN |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
DB2 my produce SQL0901N The SQL statement or command failed
because of a database system
error (Reason "this pred does not push to all branch".)
SQLSTATE=58004) or
DB2 my produce SQL0901N The SQL statement or command failed
because of a database system
error (Reason "Column number out of range".) SQLSTATE=58004
if the following conditions are met:
1. The query has join on UNION DISTINCT(UD) and SAP memory table
2. There is a join predicate on UD and SAP memory table
3. The UD has JOIN(s)
Sample query:
SELECT DISTINCT *
FROM (SELECT c1, c2
FROM t1
UNION SELECT DISTINCT t2.c1, t2.c2
FROM t2
LEFT OUTER JOIN t3 ON ( t2.c1 = t3.c1 ) ) t ,
TABLE( SAPTOOLS.MEMORY_TABLE ( CAST( '' AS BLOB( 2G )) ) ) AS
"t_00" ( "C_2" VARCHAR(60) )
WHERE t.c2 = "t_00"."C_2"; |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all users. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 M3 FP3. *
**************************************************************** |
| Local Fix: |
query optimization level 1 or use db2set
DB2COMPOPT=NO_BLU_SAP_MEMTBL |
| available fix packs: |
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
See Problem Description above. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.06.2017
16.03.2018
16.03.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
