OBIEE 11g: Error: “Server not initialized. Please make sure the repository is ready” When Accessing BI Publisher from OBIEE 11g After Upgrading Repository from 10g to 11g

Starting OBIEE 11g Server Or Running Requests After Upgrade From OBIEE 10g Fails With Error: “ORA-12504 or ORA-12154″
February 21, 2012
The OBIEE Dashboard Is Empty After Upgrading From 10g To OBIEE 11g
February 29, 2012

Applies to:

Business Intelligence Server Enterprise Edition – Version: 11.1.1.3.0 [1905] to 11.1.1.5.0 [1308] – Release: 11g to 11g
Business Intelligence Suite Enterprise Edition – Version: 11.1.1.3.0 [1905] to 11.1.1.5.0 [1308]   [Release: 11g to 11g]
Information in this document applies to any platform.

Symptoms

You have installed OBIEE 11g and upgraded the repository from 10g to 11g.  You log into OBIEE as Administrator and click on the Administration link and then the Manage BI Publisher link.  You get the error:
Server not initialized. Please make sure the repository is ready

Cause

You are missing the privileges Access to SOAP and Impersonate as System User from the  BIAdministrator and BISystem roles.

The BISystemUser communicates with the different components of the OBIEE and when BI Publisher is accessed from answers, it communicates with BI Publisher via SOAP.  The Access to SOAP privilege should be granted to the BISystem role.  Also the Impersonate as System User privilege should be granted to the BIAdministrator and BISystem roles.

Solution

1. Log in to OBIEE 11g with Administrator credentials (superuser in 10g rpd which was upgraded to 11g).

Note: The reason you need to log into OBIEE 11g with Administrator credentials, is because the error is seen only with an upgraded 10g repository.  Also the superuser in OBIEE 11g (the user created at the time of 11g install, the default name of which is weblogic) will not have access to the Administration link with the upgraded repository. See note 1262219.1 for how to add the missing Administration link in OBIEE 11g with the upgraded repository.

2. Click on Administration > Manage Privileges.

3. Assign BISystem or BIConsumer roles the Access to SOAP privilege.

4. Assign Impersonate as System User to BIAdministrator or BISystem role.

Leave a Reply