Limitations on FDI / OAC Narrative views for row counts even when set to display a single row

Doug Ross

We have some analyses in FDI's OAC Classic instance that are getting Maximum Row Limit Exceeded errors on Narrative views that are set to only display a single row. The standard format for the analysis has a narrative at the top that displays the row count which is a column that has a formula of MAX(RSUM(1)).. below that is a table format view with 15 columns… and beneath that is a Narrative view that shows the values of 6-10 presentation variables that are used in the filters.

The analysis renders fine without the two narratives and displays more than 75k rows in some unfiltered cases. But adding either Narrative view gives the rows exceeded error on the Narratives. There isn't much information available on the limits for Narratives but I did find a ten year old blog post on OBIEE that said the default row limit for narratives was 40k.

It said:

• Make sure the value between the MaxRecords tag is sufficient per your need.

                <Narrative>
                <MaxRecords>600000</MaxRecords>
                <DefaultRowsDisplayed>30</DefaultRowsDisplayed>
                </Narrative>

MaxRecords tag applies for the Narrative and Ticker views and specifies the maximum number of records that can be processed in the view. Default value is 40K.

Since we have no ability to modify the instanceconfig.xml file in FDI OAC, this seems to be a real limitation. At a minimum, the setting for the MaxRecords should be set to the same as the table view maximum.

We are looking for alternatives but it would seem the easiest solution would be to increase the limit.

Please do not suggest increasing the OCPUs (at a significant cost) to fix what should be a standard configuration.

Silvio Garber-Oracle

Hi Doug, please create a Service Request and support will let you know how they typically handle this.

Regards, SG

Doug Ross

We did initially when we saw the issue but the response from Oracle Support was incorrect (they kept referencing OTBI row limits of 64K for table analyses). We eventually determined the cause was the narrative views ourselves and closed the SR. Frankly, the response from Oracle Support was slow (took several days to get a response) and suggested limited expertise with FDI.