X

Oracle Customer Engineering & Advocacy Lab (CEAL) Blog covers BI Tech, EPM, BI Cloud and EPM Cloud.

OBIEE 11.1.1 - Web catalog upgrade from 10g to 11g corrupted some user permissions

Web catalog upgrade from 10G to 11.1.1.3 or 11.1.1.5 or 11.1.1.6 corrupted some user permissions, this may cause slow user login time and also slowness in accessing the dashboard.

Resolution:

  • Cleanup Web catalog via instanceconfig.xml using the steps documented in "Validating the Catalog" in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
  • Runcat cmd line commands to cleanup all permissions that appears to be Invalid.

Tip: It is recommended to run all above tasks each & every time content is delivered from a development environment into the production environment (e.g. weekly), as part of the OBIEE administrator's regular backup & maintenance of the catalog

Applies to: OBIEE 11.1.1.3 or 11.1.1.5 or 11.1.1.6

Symptoms:

Long login time, long navigation time
(dashboard drop down list), long search time (on web catalog especially),
especially using Internet Explorer.

Causes:

Web Catalog Permissions are invalid for
several users. Web Catalog is not clean and appears to be
corrupted for each Invalid occurrence (please see Picture 1)

Putting ONLY securities on another machine
with a standard Web Catalog is showing optimal answer time.

Picture 1: Example of corrupted permissions

Take a backup of full web catalog and open
it in Offline mode using OBIEE Catalog Manager



Resolution:

There are 2 steps that are MANDATORY to
perform to resolve performances issues:

1. Clean up invalid permissions in web
catalog:

Here are the command/instructions to remove
the users from the Web catalog:-


1) Open your Web Catalog using Catalog manager in Offline Mode

2) Locate “/” folder and Edit the
permissions

3) In Additional Users and Application
Roles box, choose in “User” and click on List button

4) On table result displayed, filter by
Type of users, putting “Invalid” one on top

5) List all Invalid users to be cleaned

6) Create a file called cleanusers.cmd in
the directory containing runcat.cmd file as follow


runcat -cmd forgetAccounts -username xxxxx -cleanup -offline "web catalog
PATH"

7) Run the command cleanuser.cmd as follow:


8) Open your Web Catalog using Catalog
manager in Offline Mode

9) Locate “/” folder and Edit the
permissions

10) In Additional Users and Application
Roles box, choose in “User” and click on List button

11) Verify that all Users are valid for now

Sometimes you will that it is not possible
to erase permissions running runcat commands.

The best is to do the following:





It can appear that those users are in fact
linked to Agents.



Clean appropriately to get rid of last
Invalid permissions


2. Run an automated clean via Presentation
Server.
Note: Refer to steps documented in "Validating the Catalog" in
System Administrator's Guide for Oracle Business Intelligence Enterprise
Edition.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.