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:

The rest of the pivot view behavior is controled by

• [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.