Inconsistent Results from LIMITMAP passed to OLAP_TABLE Function When Measure Has a Qualified Data Reference (QDR) on a Dimension
(Doc ID 1569464.1)
Last updated on NOVEMBER 07, 2023
Applies to:Oracle OLAP - Version 18.104.22.168 to 22.214.171.124 [Release 11.2]
Information in this document applies to any platform.
An OBIEE-generated query against an OLAP AW using the OLAP_TABLE table function returns inconsistent or wrong results. In the user case on which this note was based, a query would return zero rows when initially run, but would return rows after running another query.
Here are the details for the wrong results:
* Query 1 would run, in a new session, an 8 dimensional query (defined in olap_table limitmap) with a single custom measure. The custom measure was defined over an 8 dimensional measure but the formula pinned one of the dimensions to a single value using a Qualified Data Reference (QDR). No rows were returned for Query 1.
* Query 2 would run right after Query 1. Query 2 was the same as Query 1 except that Query 2 had an additional measure that was 8 dimensional. It would return the correct rows and columns.
* Query 1 would be run again, but this time it would produce the correct number of rows and columns.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document