OBIEE 11g Graphical Color Scheme like 10g

Salut à tous…. Joyeux Noël…. Wish you Merry X-Mas and good time with your near and dear ones … So I am back here with some new geeks … 🙂 Excuse me if somebody already know it !… and please let other to learn …. !

OBIEE 11g Graph colors are quite jazzy comparing to 10g… this is one of the recent feedback we received from clients in our post up-gradation review of codes .So one of the obvious requirement came into picture is that, how do we retain the 1og Graphical color schemes in 11g. This could be easily done by playing across the XML codes for color definition .

Lets do it …

As you might already be aware of that 10g Color contents (hex-codes) definition are stored in the palette.cxml file. So what you need to do is only copying the color Hexcodes from 10g files and put those under the file located : “..\Middleware\Oracle_BI1\bifoundation\web\msgdb\s_blafp\viewui\chart\dvt-graph-skin.xml” having the below sample syntax  (do the same for other style folders like s_FusionFX  if you need it)

So below content copied to the above xml and put this between the first and last tag of  SeriesSlice :

<Series id=”0″ color=”#A4D5F9″ borderColor=”#A4D5F9″/>
<Series id=”1″ color=”#5592D0″ borderColor=”#5592D0″/>
<Series id=”2″ color=”#EFD084″ borderColor=”#EFD084″/>
<Series id=”3″ color=”#687FA1″ borderColor=”#687FA1″/>
<Series id=”4″ color=”#CFC4E5″ borderColor=”#CFC4E5″/>
<Series id=”5″ color=”#8D9EB7″ borderColor=”#8D9EB7″/>
<Series id=”6″ color=”#5898AA” borderColor=”#5898AA”/>
<Series id=”7″ color=”#CEE4EA” borderColor=”#CEE4EA”/>
<Series id=”8″ color=”#90B5D1″ borderColor=”#90B5D1″/>
<Series id=”9″ color=”#F6E795″ borderColor=”#F6E795″/>
<Series id=”10″ color=”#C7C1C1″ borderColor=”#C7C1C1″/>
<Series id=”11″ color=”#85A8EE” borderColor=”#85A8EE”/>

Make sure all the services restarted before the change to be effective.


See below difference before applying the XML(11g Original) and after applying (aligned with 10g color).

N.B:- It has been observed that though the 10g color scheme applied for 11g but it is not at per with existing 10g colors and there are slight deviations in terms of colors which is not eye-catching but somehow not matching exactly due to the difference of the rendering engine of 10g and 11g.

A worth to note is that, in our implementation we have seen that in several charts the color change is not propagated and hence it seems that the color scheme is not applied properly as per the defined XML. However if you edit the chart and remove any measure and then drag the same measure again we see that the color starts changing as per XML . The behavior seems to be unpredictable for us. Assumption is that ,it might happened due to some internal cache specially for the chart engine here.  But the problem is not observed for any new reports created in answers in 11g and it starts reflecting the new colors scheme from very beginning.

Intelligent Deployment of RPD/Catalog – OBIEE 11g

As probably everybody knows that we have intelligent RPD deployment process as per OBIEE 11g is concerned using Enterprise manager Deployment module . But do you know if you have not follow the conventional procedure what problem you are going to hit …. Here you go …

 [nQSError: 13043] Could not get repository password for CSF key ‘repository.MyRPD_BI0001’ from CSF: [46147] The Repository credential does not exist.

The reason behind the issue is that I had just copied the RPD from 11g Dev env and Paste it to 11g Test env and change the RPD name in NQSConfig.INI file and try to up the server using unconventional way just to figure out what kind of check it does …. Quite intelligent… Each RPD has a unique identifier and it is stored in Credential Store and you can’t bypass the Credential store verification during your update of the RPD. So always do a clean deployment process otherwise you will be messed with it 🙂

So above error you will be getting for incorrect deployment procedure of your repository. This is specially recommended during the env migration . However I have seen in the same env if you are doing the copy paste of the same RPD and rename it and then change the name in NQSConfig.INI it somehow works out fine.

Again don’t try to Update Account GUID’s (FMW_UPDATE_…. under NQSCONFIG and UpdateAccountGUIDs under instanceConfig) and Deployment of RPD at the same time .It will give you erratic behavior. And in those scenario your RPD and Catalog name is always going to refer old name rather new one.

OBIEE 11g NULL value is not replaceable with “0”

As far the 11g release is concerned and ongoing experience to work with OBIEE 11g, among the several good features ,enhancement from all aspects there are a lot of glitches causing unnecessary itches for the Developers and also additional overhead from Administration’s perspective .

Hey Weblogic , not a good friend yet with OBIEE 11g causing a nightmare for last couple of weeks while engaged in couple of migration project from OBIEE 10g to 11g .Overall experience is not satisfactory with this new planet …. Weblogic … in the Universe…. 😦 Lets make it simple and manageable… !!

Okay coming to the point … Now not with Weblogic …but the analytics/reports piece itself …

As per the 10g release is concerned using some conditional clause any NULL value could be presented as 0 specially when there is divide by zero scenario . In 10g it is pretty easy to handle such situation from RPD or Webcatalog but in 11g it is a proven bug . Oracle Ref: Internal Bug Id: 13054445 .

Came to our notice in Pivot table operation neither the CASE WHEN in RPD/Catalog ,not the IFNULL or NULLIF handler able to replace the NULL value with 0 for my Pivot table. Forget anything to do in any of the config file or the database feature in RPD . Nothing will be helpful at all…If yes , your comments are most welcome !

Resolution: Nothing . Ask Oracle to get a patch if this is critical for you or wait till unplanned release.

Oracle BI Mobile App for iOS devices

Welcome back after long days … Just tied up with couple of  OBIEE 10g to 11g up-gradation projects nowadays and manage to have any time to Blog considering lot of other extra-curricular activities 🙂

Anyway today my experiment was with Oracle BI Mobile iPhone/iPad App. I have downloaded the app from AppStore couple of days ago but unfortunately have not receive any server details to see how the App looks like in my iPhone 4 .However recently Oracle launched this Demo Application and you need top register there to get the PDF having the details of the servers (Thanks to Mr. Barry for sending me the details).

Register Here and then download the App :

And view the Demo here:

BI Mobile sales demo –
Financial Analytics Mobile demo –

I believe underline iPhone App is based on OBIEE 11g as I can see the 11g interface only while connecting from my PC.

Here are the couple of screenshots first, taken in my iPhone, to get the flavor how it looks like. Later I will explain my comparative findings between 11g Desktop based and 11g Mobile BI App.

The text colored in “Green” is short briefing against each screen-shots:

+++++++++++++++++++++++++++ My findings +++++++++++++++++++++++++

1) Due to the Display limitation of iPhone I can see most of the Horizontal reports/Charts came in vertical view.But always you can switch to “Original Layout” from the actual default “Mobile Layout” to see the change report components layout across dashboard pages. I don’t know how it looks like in iPad by default… haven’t tried yet 😦

2) The Zoom-in and out features by playing with two fingers sometime doesn’t fit the display and causing some display out of the screen which obviously require to scroll by fingers both Vertically and Horizontally.

3) Online App via PC Browsers having “Graph Slider” while in iPhone it is drop-down. Not sure if iOS having different compilation process

4) No download to excel/pdf/ppt features yet.

5) Spatial Graph display and drill down works great .

6) All kind of Navigation and Drill-down feature is aligned. However Master-Detail event tracking has not been seen so far as per this application . Not sure whether this works or not !

That’s all ….