Categories
Exceeded configured maximum number of allowed output prompts, sections, rows, or columns.
Hi,
I am facing an ' Exceeded configured maximum number of allowed output prompts, sections, rows, or columns.' error in OAC.
Is this related to 'Maximum Number of Rows Processed when Rendering a Table View ' and in the Oracle support knowledge document, it says to raise SR and get the maximum number of rows processing increased.
Appreciate it if anyone has any idea on how to proceed with this.
Thanks in advance,
Kusuma
Best Answers
-
Hi @kusuma l -Oracle ,
The error message that you are getting is usually associated with a suboptimal report (and/or data model) design. Could you please a screenshot of how you created the visualization which is causing the issue?
In OAC, the limit on the maximum number of rows is strictly related to the OCPUs number of your instance. You can increase the number of OCPUs in order to increase the limits on rows, but this will not fix any suboptimal design in your reports/data models.
Please have a look at this page as a reference: https://docs.oracle.com/en/cloud/paas/analytics-cloud/acoci/create-services.html#GUID-7D6DB4EE-8DD5-44C5-9B6E-9FA847463A5F__TABLE5
0 -
we are migrating their reports from 12c to OAC, The error report has only 30k records and it is working fine in 12c.
Working fine in OBIEE 12c doesn't mean anything: in OBIEE you have full control on config files, allowing you to remove any limit on number of rows, columns, cells.
OAC is a "black box" for configuration: you have few settings accessible and everything else is decided by Oracle.
If you want to be able to configure the tool as you want, you will need to use OAS (can be hosted in the cloud but has to be installed and maintained by you).
There are steps required in an OBIEE to OAC migration, redesigning analyses and limit number of results is one of them. It's all known, somebody should have told that customer before they decided to move to OAC....
4 -
If you check the original (old) OBIEE documentation it spell out item by item all the default values which are applied and which can be overridden in the isntanceconfig:
For example MaxCells was 50'000 by default. You have to be careful and precise about "cells" vs "rows" vs "columns" for all these settings on-premises. Rows x columns = cells for example.
0
Answers
-
Hi @Federico Venturin ,
Here is the screenshot.
Oracle support feedbacked saying if there are more cells to display we may face this issue. please suggest.
0 -
Hi @kusuma l -Oracle ,
Can you open the table in the analysis editor and share a screenshot of the Layout Editor (bottom section)? This is required to spot any subptimal design in your analysis.
In order to avoid the issue, I highly recommend to reduce the number of columns in your analysis, and eventually split it into multiple analyses/dashboard pages. As an example, you could add a dashboard prompt where users are allowed to select a Year at a time, or you could create one analysis per each measure in your pivot table.
Please remember that Classic Analytics and Data Visualization are web tools which have been designed for BI/Analytics purposes, and displaying a static report with million of rows in a web page is never a smart idea. If your final goal is to export data, then you should use a different tool such as Analytics Publisher (which has higher limits compared to Classic Analytics and DV).
0 -
Just to note that the KM doc you referenced here was created for 'Primavera Cloud Services' product and is not applicable to Oracle Analytics Cloud. For OAC we cannot increase any configured limit via backend. You have to apply necessary filters, reduce columns/cells to be within the documented export limit based on your instance shape.
1 -
Hi @Federico Venturin I got your point.
This is a client environment and we are migrating their reports from 12c to OAC, The error report has only 30k records and it is working fine in 12c.
Are there any limitations that apply if the pivot view is displaying more cells or more columns?
Thanks,
0 -
Please see if the explanation provided here helps to redesign the analysis
OAC: Bubble Graph / Chart Limits For Maximum Number Of Allowed Output Prompts, Sections, Rows, Or Columns (Doc ID 2772771.1)
1 -
Hi @kusuma l -Oracle ,
The documentation states that you can have at most 300 visible columns in a pivot table. It does not mention a maximum number of cells, but I suspect that such a limit is in place.
How many years are you displaying the in the pivot? Given that there are 12 months in a year and you have 3 measures, each year will add 36 columns to the pivot
What happens if you drag the "Time"."Month Year" column to the Rows drop target (or replace the pivot with a standard table)?
Do you have any column into the Prompts drop target? If so, I recommend to replace it with a proper dashboard prompt in order to reduce the number of rows retrieved by the analysis (and improve performance as well).
IMHO the best way to fix the issue is to replace the analysis with a Publisher report, or eventually split the pivot into smaller ones (e.g. one pivot per year) or add a mandatory prompt for selecting at most 1 year value.
0 -
Hi All,
Thank you for the detailed explanation,
Our Client querying for almost 12 years Date range, that was around 470 columns. Ideally best to have more specific filters instead of just date range, Or to have focused data in different dashboards.
Thanks,
Kusuma
0
