TimesTen/Exalytics/OBIEE: Queries With Nested Left Outer Joins Consume All Temporary Space And Fail With TT802 Errors
Last updated on SEPTEMBER 23, 2016
Applies to:Business Intelligence Suite Enterprise Edition - Version 184.108.40.206.0 and later
Oracle TimesTen In-Memory Database - Version 220.127.116.11.1 and later
Oracle Exalytics Software - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 1.0]
Information in this document applies to any platform.
***Checked for relevance 02-Apr-2015***
A customer observed that queries using a series of left-outer joins consumed all temporary space and failed with TT802 errors:
The SQL queries were being generated by the Oracle Business Intelligence "OBIEE" tool. Using queries and DDL supplied by the customer, the problem was subsequently reproduced in-house. Further testing showed that the problem reproduced regardless of the cardinalities of the tables in the query. Additionally, it was also observed that the problem reproduced only when the query involved a series of left outer joins. Rewriting the queries to use right outer joins or inner joins did not cause the same errors and the queries typically completed in timely fashion.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms