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.

 

Yesterday, someone ask for how to add a new user in OBIEE, oh! that is real foundation of OBIEE usage.  You can create the Group first which is focus on the authorization from DB and it is the set of permission. Then you can consider about create the User in Security Manager next.

 

But some things you should know with User management in OBIEE.

 

1. User Accounts can be defined in External Datebase Table and LDAP Server, not just Oracle BI repository.

 

2. If you use the Repository to create user, and that user just only can access business model in same Repository.

 

3. You can not deleted the Administrator account any more.

 

Today, I receive BIEE project needs from Beijing,  maybe that is off-site and multi-User requirement, so I set up Multi-User Development Environment for already. Becasue of the data security, so I just share with you using the Paint demo data. When creating a project, the Oracle BI Administrator selects a presentation catalog or a subset of logical fact tables related to the selected presentation catalog, and the Administration Tool automatically adds any business model and physical layer objects that are related. An object can be part of multiple projects. After you create projects, they become part of the metadata and are available to multiple developers who need to perform development tasks on the same master repository. When defined this way, projects typically become a consistent repository after a developer checks out the projects and saves them as a new repository file.

 

Steps below:

- Creating Projects for a Multiuser Development Environment.

- Set Up the Shared Network Directory.

- Copy the Master Repository to the Shared Network Directory.

 

First of all, you must ensure the user is offline not online, so you maybe should cut off the BI servier, and log in with User admnistrator. Then, you can select Manage > Projects from the BI Administrator.