Moving development form database to database, I frequently end up with Warning: "OBIEE RPD – The feature in Database do not match the defaults. This can cause problems." I assume this can be attributed to all these database (and servers) having slightly different settings, defaults, connections properties. Sometimes I move databases and it does warning does not show up. Sometimes it does.
One of OBIEE’s idiosyncrasies is that, by default, only the user that installed the product can start the server from the Window’s Start menu. For more information on this, please read this old post.
The solution outlined on that post enables ADDITIONAL users to start OBIEE. This is still borderline unacceptable on a production environment. Ideally, we want OBIEE to start with the Windows Server.
What we want is OBIEE to start as a service on boot up. The only original information I’ve found on this comes from Oracle itself.
Everything else ‘on the tubes’ so far is a copy/paste job from Oracle doc. However, I have found no success stories from anyone. I could not get this to work either for OBIEE.
This is where Windows Scheduler comes in. Using Windows Scheduler, I was able to set OBIEE to start on system startup without any trouble.
Talk about running behind. I recently found out that Oracle does offer a client tools ONLY set for OBIEE. As of this writing (126.96.36.199.0), you can head over here and grab Oracle Business Intelligence Developer Client Tools Installer.
At a bit larger than 300 MBs, this download is a walk in the park compared to them 25 GBs.
I am successfully running Admin Tool now sans server on local box but I ran into a few odd things along the way.
You finish revising RPD for project and, upon checking global consistency, you get the following error(s):
 Physical tables "<TABLE_ONE>" and "<TABLE_TWO>" have multiple joins. Delete new foreign key object if it is a duplicate of existing foreign key.
Each of these errors points to different tables but they are all of the same type. Sensibly, error states that the tables in question have more than one join between them.
- You cannot log into your RPD in online mode.
- You are certain that you are using the proper credentials: repository password, weblogic username and weblogic user password.
- You can, however, log into RPD in offline mode.
It is likely that the OBIEE server was shutdown while you had the RPD open in online mode in the Admin Tool.
- Ensure the OBIEE server is shut down.
- On the OBIEE server, navigate to the location of your RPD. You should see, together with your RPD a ‘.sav’ and a ‘.log’ version of your RPDfile.
- Remove these two files.
- Start BI Services again.
After OBIEE is up, you should be able to open your RPD file in online mode again.
Oracle provides one of the best resources for learning to use it’s extensive BI stack of tools. The company freely distributes an ‘OBIEE’ virtual machine that runs, of course, on VirtualBox. Not a bad thing, Virtualbox runs equally well on Windows, Macs and Linux. This VM has many of its most powerful products already configured. Not only are the products configured, they are also integrated with SampleApps deployed, a BI project highlighting product features for Oracle’s Apps.
Failure to start BI Services from the Windows Start Menu.
The most likely reason is that OBIEE was installed under one windows account and you are attempting to start it under a different account. This is, for some reason unknown to me, the default behaviour for the OBIEE installation. Other windows users wanting to start OBIEE have to be both added and given permission to run installer.
You cannot log into OBIEE’s Web Interface with the WebLogic credentials.
However, you can log into both Enterprise Manager (/em) and Console (/console) on the WebLogic server with the same login credentials that fail on OBIEE.
This post describes how to use the Set Icon feature in OBIEE to keep track of items your RPD file.
Imagine you are about to extensively revise your project’s RPD file with many additions made to the data warehouse schema. The general workflow for this type of task involves methodically working on metrics and attributes from the Physical Layer on the right to working on aggregations, hierarchies, etc. on the Business Layer to exposing a select group of all these items in the Presentation Layer.