OBIEE ResultRowLimit

Post date: 04-Feb-2010 07:32:29

I still wonder why people want to do it: A report with more than 65000 rows, but still….

You can override the maximum number of rows that can appear in a Table view by modifying the Oracle BI Presentation Services configuration file (instanceconfig.xml) to add the following entry.

The internal default is 65000. If the user exceeds this value, the server returns an error message when the table view is rendered.

NOTE: This entry applies to the Table view, not the Pivot Table view.

The ResultRowLimit entry controls the maximum value that can be set for the DefaultRowsDisplayed, DefaultRowsDisplayedInDelivery, and the DefaultRowsDisplayedInDownload (fi download to Excel) entries.

To set DefaultRowsDisplayed, DefaultRowsDisplayedInDelivery, or DefaultRowsDisplayedInDownload to a value that exceeds the current value of ResultRowLimit, you also must increase the value of ResultRowLimit to equal or exceed the value that you want to set.

OBIEE Controling Pivot View behavior

One of the more powerful tools in OBIEE is the pivot view. If you have large amounts of data you sometime run out of rows and or columns or even worse out of cells

You can control these values by altering the instanceconfig.xml.

This file is usually found in ..\OracleBIData\web\config

Good info can be found in the Oracle® Business Intelligence Presentation

Services Administration Guide (b31766.pdf)

If you open instanceconfig.xml in notepad you get something like these parameters

The behavior of the pivot view can be altered with the following parameters:

[MaxVisibleColumns] Sets the maximum number of columns to be displayed in a Pivot View default{1000}
[MaxVisiblePages] Sets the maximum number of page choices (or pages in PDF) to be displayed in a Pivot View default{1000}
[MaxVisibleRows] Sets the maximum number of rows to be displayed in a Pivot View. Default{100000}
[MaxVisibleSections] Sets the maximum number of sections to be displayed in a Pivot View. Default{1000}

Altered in the instance config it would look like this:

If you still run out of cells try this:

[CubeMaxPopulatedCells] The maximum number of populated cells in the Pivot Table. If this maximum is exceeded, the user receives an error when rendering the pivot table. Default {150000 }
[CubeMaxRecords ] The maximum number of records returned by a query for the Pivot Table engine to process. This roughly governs the maximum number of cells that can be populated in a pivot table (unpopulated cells in a sparse pivot table do not count). If this maximum is exceeded, the user receives an error when rendering the pivot table.

They should be between the serverinstance tags.

http://knowledge.ciber.nl/weblog/OBIEE/OBIEE10340CONFIGURATIONTAGS.pdf

Compliled from

http://obiee101.blogspot.com/2008/02/obiee-controling-pivot-view-behavior.html