2012 in review – My Blog …Wish you all Happy New Year !

The WordPress.com stats helper monkeys prepared a 2012 annual report for this blog.

Here’s an excerpt:

About 55,000 tourists visit Liechtenstein every year. This blog was viewed about 210,000 times in 2012. If it were Liechtenstein, it would take about 4 years for that many people to see it. Your blog had more visits than a small country in Europe!

Click here to see the complete report.

Fixing Pivoted Graph Conditional Formatting – OBIEE 11g

OBIEE 11g upgrade has a lot of issues and among couple of them common is on Conditional Formatting . This emphasis that even if the Catalog upgrade is successful there are some of the problem still persists in XML conversion engine of the Upgrade Assistant(UA) leading though several catalog defects due to malformed XML . This is another example as my upgraded 11g charts failing to show its conditional formatting which is was working perfectly in 10g ….

Lets deep dive on whats the issue …

Below is the conditional format definition in 11g which is aligned with 10g:

So ideally it should show Chart bars (which is generated from Combined request Pivoted Graph) and see the below comparison:

To understand the reason of why 11g chart not showing the conditional format I went through the full XML from Advanced tab of 11g and find the below discrepancies:

This is malformed XML generated by UA during the upgrade of 10g code .If we look into 10g Advanced XML this is actually decimal but for some reason UA failed to put correct literal against it .

So the fix is replace all the instances of string “untypedLiteral” with “decimal’ like below:

Now after applying the XML the 11g chart output like :

And voila …. the problem is fixed … There could be another workaround to copy your 10g entire XML to 11g and yes it should work     🙂 🙂

Enjoy ..till next time…


Fixing the BAD XML Instance Issue – OBIEE 11g

“The current xml is invalid with the following errors: Bad xml instance!” is very unusual error but when this has been encountered it is become frustrating as it sounds the entire report can’t be saved !

I remember last time I had faced the similar issue in version while I was building a new report from scratch . The error enforced me not to even edit the reports so I neither I can move to criteria nor I can save this . That was weird !  The only option left was to edit the XML using Catalog manager but until and unless you know where the problem lies you can’t fix it right ?

Now recently I got similar kind of issue in one of our upgraded report which is a Combined request report and when I tried to edit the Criteria Analysis properties Interaction tab to remove Sort column of un-check any other options it throws me below error during the save:

Okay … so the error was at the very last line of the displayed XML as below:

Line:814, Col:61, Element ‘criteria’ is not valid for content model: ‘((criteria,interactionOptions,views,prompts,listOptions),segmentOptions)’

so the bug is around the green circled tags !! Reason is whenever you un-check some options under “Analysis-Properties” it will throw errors !! Probably this is some problem with the up-graded code in 11g from 10g as I tried to replicate the same creating a new reports from scratch which was pretty cool and removing any interaction works perfectly okay in the dashboard report .

After spending some times the reason of the issue found with the fix . I have customized the location for the below tag from Advanced XML :

<saw:interactionOptions drill=”true” movecolumns=”true” sortcolumns=”false” addremovevalues=”true” groupoperations=”true” calcitemoperations=”true” showhidesubtotal=”true” showhiderunningsum=”true” inclexclcolumns=”true”/>

Edited the XML and moved it from beforesection to the end of all. As it is combined request hence several would be present but placed it after all of them.

 After that apply the changes in Advanced XML and voila …. your problem fixed !  Note that this could be the one of incident with BAD XML error and probably you can found it in several other places with no relation to my above fix note . This those cases you need to dig down into more details of the Advanced XML generated and fix those issues as applicable for your case .

Bottom line is same . Dig into the XML details to find out the crappy code and the fix it ! …

So that’s it …. till next time… Happy weekend 🙂


OBIEE 11g/10g Column Header Freeze

I thought to post this thread long time back during version but just waited for 11g new release .5 and upcoming edition assuming Oracle might include this demanding features soon and still surprised there is no OOB feature included while we are in .6 now.

I know the couple of fellow bloggers already tried that and everybody could have different approach . So lets put what I had experimented in last year in .3 release which is still valid in .6 . And this approach and implementation still valid in 10g.

Its simple to have column header freeze adding some scripting with embedded content . I took a simple dimension and simple fact to create one Tabular report and one Pivot report in two different tab where I have applied same logic but just want to show that the feature still feasible in both view.

So lets see how it will look like after Tabular column freeze (I would rather say it is kind of floating column header attributes)

Now I have scrolled at the right pane and watch the year attributes.  Now you can see that the column header retains.

Now see the implementation:

I have added Text and Embedded content in the dashboard page:

The text properties(HTML Markup checked): I can’t put it like text for your copy paste as the tag is restricted to use in wordpress and sorry for that 😦 Hence click on the image to get the detail view.

Embedded Content URL: 


So I have created a simple tabular report with the above columns and saved it under my folder and referred that in the URL .

That’s it and you are done …

Now if you try to implement the same, you will see some alignment issue and in that case you need to adjust the Width and height and other parameters of HTML content to get the cropped column list  . Note that in above implementation I just remove my title view from report .

Though the above design has a lot of other restrictions (Downloading , Column sort ) but there could be possible workaround for that. At-least you can get something which is better than nothing. 😀

Similar way I did it in Pivot view :

In this case my Embedded URL is different: (note the Viewname param at the end which only pull the compoundView2 which is my pivot table)


Refer this same URL  under the HTML content defined in above image as Text HTML Markup properties.

Let the soul of the above approach rest in peace once Oracle implements this as OOB functionality in upcoming releases !!!  🙂 

And we expect this to be sooner than later …. Catch you again ..till then …. 

OBIEE 11g – Up-gradation Catalog and Env/Config Issues/Challenges and Fixes ( &

Since(Oct 2011) I had started working on OBIEE 11g ( for four different projects in parallel to up-grade the 10g to 11g lot of challenges have been faced specially with the Catalog and Environment issues. (You can see the already reported RPD issues under: https://debaatobiee.wordpress.com/2012/01/26/obiee-11g-up-gradation-rpd-gotchas-and-glitches/ )

I could report all of them in below threads with the possible resolution but as I am writing this blog now (actually I am bit late posting this thread L ) some of them already taken care of in version however not all and bit surprised that though Oracle agreed to release the patch in .6 version and file the bug report they didn’t work out yet on those mentioned issues reported during .5 up-grade.

Worth to see the link here for possible changes in BI reports due to new features before taking the assumption that it is a bug.

As par my latest up-gradation from 10g to is concerned it went well but still some of the defects which are already noticed in .5 not fixed yet, some of them appeared new and some of them totally ridiculous and critical too as per business perspective and some of them not reported yet to Oracle and hence no relevant information found in Support.

I am happy to categorizing them into two different areas below: (I have used .5 and .6 interchangeably to mean and

Environment and Configuration Issues

  • Up-gradation of RPD and Catalog separately could cause the issue with the Dashboard Privileges and Object permissions. I had experiencing the issue when upgrade the catalog first and then RPD and reason which I could think of is that until the RPD up-gradation completed successfully by the UA it doesn’t going to reflect all the Users/Groups information in the Weblogic Security store. So if you are experiencing the issue recommendation is to at-least perform the RPD first and then catalog.
  • During the migration process we have followed the approach to up-grade the same 10g RPD in the higher environment (say Test or UAT) to ensure the security store upgrades taken care of by the UA automatically. Other approach could be taken the export of the security store from the Weblogic Console for my security realm and then Import the security details to target env which basically perform a XML upgrade of security details in target environment
  • Job ManagerPassword is not upgraded with RPD upgrade .It still retains the password of source RPD and target RPD password needs to be changed manually. At-least the behavior has been seen in and have not tried yet this in the .6 version
  • Upgrade can’t be done if the parameters are locked in FMW EM console: Upgrade will fail with below status. Need to release the lock and retry.
  • Take extra caution when you are enabling the RPD Read only option in the EM as I found this is quite weird but finally checking and un-checking multiple time resolves my problem. So there is possible bug around this features in .5 didn’t try the .6 yet.
  • Never try to deploy the RPD using the undocumented and wrong procedures except from EM .Otherwise you will find “CSK Key not found” issue during RPD deployment process.
  • Missing Application roles in catalog results the new roles to be created inside Weblogic Admin Console and map to the groups i.e. required.
  • Deploying EAR file gives: “Deployer:149082 You cannot deploy application ‘analytics’ without version” . OBIEE 11g: Error: ” <[WebAppModule(analytics [Version=11.1.1]:analytics)] Error Parsing Descriptor in Web Application” Whilst Deploying Analytics.ear File . This is 11g bug . See the resolution and patch note in Support
  • While changing the password of Administrator account in EM and Weblogic make sure both are in synchronize.
  • Loglevel Bug – NULL loglevel value set against user in external table based authorization scheme cause the user login failure however the same configuration in database level works perfectly okay with 10g setup. Resolution is to have must non-null values against all users in database records. This persists till .5 version and did not check yet the .6 version.
  • While executing OPatch utility to apply the patches provided by Support to .5 env it displays with below information:

    Running prerequisite checks…

    Prerequisite check “CheckActiveFilesAndExecutables” failed.

    The details are:

    Following files are active :





    ApplySession failed during prerequisite checks: Prerequisite check “CheckActiveFilesAndExecutables” failed.

    System intact, OPatch will not attempt to restore the system

    OPatch failed with error code = 74

    Resolution is to change the Privilege of “C:\Program Files\Oracle\Inventory” directory from read-only to Read-Write with Full-Control . However that was never documented in Oracle OPatch Readme.

  • While changing the BISystemUser password make sure those are in sync with EM security store and Weblogic Console and till .5 version there was issue with using special character as BISystemUser password. Make sure that it should not have special characters.

Catalog Issues

  • “Act As” doesn’t populate the list of users and throwing functionality disabled by Admin. For Act As to work for the LDAP based users required configuration needs to be done (except what is the to-do configuration for 10g) as the security model for 11g is different from 10g. I will detail the change in “Act As” process in separate thread.
  • There are always problem with the report or prompts decimal issues .Either new decimal value appended , decimal value missing, 3 decimal places appears in place of 2 or decimal values not appearing at all in Charts mouse over option. Also the issue persist in aggregate calculations which possibly results the wrong value in Sub-Total or Grand total. The problem needs to be diagnosed and isolated before fixing.
  • causing the issue for Multi Path navigation . While there is single navigation path in 10g there is no needs to have a pop-up with the Action link text name but UA not being able to trace the link name while it is a single path. Also if there is ‘&’ character in the Action Link text it improperly translate it as ‘&’. However there is no quick fix available as of now and you need to go to individual navigation where problem exist and fix it by clicking option ‘don’t show pop-up in place of single navigation”
  • Upgrade Assistant (UA) not really able to up-grade properly the navigated links/interactions against column header, value name and hence post up-gradation we had to manually remove all the unwanted navigation paths from column values. This typically occurs if any column of the table/pivot view has interaction, it is going to add the same interactions/Action Links to the measures columns across the reports.
  • Typical problem has been faced in the Aggregate calculation and the conditions specified in the pivoted report. Those have been faced case by case.
  • There is severe issue with Count Distinct measures specially to calculate the Grand Total and results the calculation mismatch between 10g/11g reports.
  • Sorting of columns having the hard-coded customized values not works for Combined request. Special tweaking needs to be done to fix the issue by appending some space characters once, twice, thrice etc.
  • Problem with SQL_TSI_WEEK function and Can’t properly cast the value caused CASTing errors. Not sure if that fixed in .6 version and not tried yet.
  • iBots causing the issue after executing it and reports : “AgentID: /shared/Test – DxP/DxP_iBot” , Invalid subscribers skipped: DEBA . The reason is SASystemSubject area enabled . The problem found in .5 version and the fix is to disable the SystemSubjectArea using the special tag inside instanceconfig.xml file
  • OBIEE 11g: Error While Fetching a Large Pivot Table: “Exceeded Configured Maximum Number of Allowed Input Records” while downloading the reports with more than millions of rows . However it has been observed that the problem not exist in 10g and aligning the required parameter in instanceconfig doesn’t resolve the issue. The same issue persists if download operation of the report triggered using the JavaScript’s and the iBots scheduler. Below error reported in the downloaded excel file. So far the issue persists in .5 and bug opened for that. Not sure if that is fixed in .6 yet

                 “Exceeded configured maximum number of allowed input records” onclick=”SAWMoreInfo(event)

                 Error Codes: EKMT3FK5

  • Redundant Legend for Chart View in OBIEE Pivot and Table based Charts causing the weird legend display. However part of that has been fixed and still some of the customized charts the issue retained in .6 version.
  • 45 degree angle Chart axis label causing blurred labeling which is un-readable and pretty difficult to understand. Support suggests ‘EmbedFonts’ tag under instancconfig which also doesn’t help and I have seen the problem still persists in .6 release.
  • Some of the crowded/busy charts axis labeling doesn’t plot the label value at all in the axis .However data and bar shows perfectly fine during hovering but the axis label under some of the vertical or horizontal bar seems missing. Resolution as of now is to increase the charts width and height, reduce the axis label fonts and make the label as 0 or 90 degree. The problem typically found in .6 version
  • Pivot table column header formatting not properly upgraded for some of the reports and not all. The problem typically found in .6 version
  • Additional row in every table or pivot view cause the format difference with 10g reports. Not sure when the fix or ever the fix will be available
  • In .5 release if we want to remove some column from the view of the table in Dashboard page it was possible but you couldn’t add those later and never find those removed column. But it seems that Oracle fixed the issue in .6 release.
  • In .6 version critical data issue exist if the presentation column (P1) (where P1 and P2 refers the same logical column) used in reports with combination of other measures. In those cases it was causing weird data issues. So has been fixed by pulling correct relational presentation dimension column relevant to the logically same place of the metrics
  • Critical catalog issue has been observed while Navigating from the Chart or Pivoted Chart where the value in the database having & character like (‘HOME & BEAUTY’) .In those case navigation to the detail report caused no results as the value itself from the chart passing to DB is like ‘HOME & BEAUTY’ in the where clause of the query. Didn’t got any response yet from Oracle about the fix and the patch. Latest Update(June/08/2012) — Oracle agreed the defect and raise the priority bug fix with no estimated SLA .However the issue escalated and waiting for Development team response. They also confirmed that the same issue will be there while Drill down from data value having special characters (like ‘&’) .
  • In Chart pivoted result one of the metric value which is NULL, appeared in Pivot table and not in Chart for 10g, but in 11g it is coming for both Pivot and Chart . No solution apart from segregating the view into new Chart view.
  • The expression like “CAST(((max(saw_3 by saw_1) /max(saw_4 by saw_1))*100) AS VARCHAR(50)))” no more valid in 11g at-least in .5 version.
  • Presentation variable report filter default values are no more Case sensitive in 11g at-least observed in .5 version
  • BI Publisher issue in one of the up-graded report as “oracle.xdo.XDOException: oracle.xdo.XDOException: Unable to create saw session. Please verify the server connection” and entire report needs to redesign for that using different security approach.
  • Sometime it will be seen that until the Results tab returns the values if you bring the column from presentation area to criteria it will not reflect and sounds like column not added yet .However after results returns come back to Criteria you will see the column added. There are possible synchronization issue which still persists in .5 and .6 version.
  • Clicking on Hierarchy column will show the results in left pane while we are in Results tab but same doesn’t exist if we click the column left pane in Criteria tab. This could be possible enhancement req on top on .6 version
  • In 10g we can press Control from keyboard against the presentation column and the filter condition pop-up can be appeared automatically but same feature doesn’t exist in 11g .This could be a future and very useful enhancement request.
  • In 11g .6 version has some issue with the Saved Filter post up-gradation and clicking on that filter view doesn’t pop-up the filter criteria and even the view doesn’t display anything in Dashboard page if we clicked it. However building the Saved filter from scratch resolves the problem. So issue there in catalog copy post .6 up-gradations. The problem identified later with the Integer value based column in filter criteria and the resolution is convert that to advanced SQL based values and that will sort out the problem . This is definitely another 11g .6 version bug.
  • Sorting issues are there for charts and on measure while using RANK order
  • In some of our Charts we have seen there is display issue in IE8/9 and Chrome but not in Mozilla Firefox after up-gradation . However re-creating or building the same using IE8/9 browser fixes all the display issues and it is working perfectly fine. Also in some situation I have observed creating new view doesn’t help, in that case bring the attribute from presentation once again and create the derived expression once again and that sorts out the issue.
  • In one of our request we have found the partial data  issue/mismatch with Combined request with Union . After digging into the details it has been found that the issue is due to a calculated column in pivot section (whereas the same view didn’t have any calculated column in 10g !!) .The issue is bit strange . Deleting the unnecessary calculated columns/ or recreating the same view from scratch caused the issue fixed.
  • Couple of the iBots not properly up-graded by UA and cause Bad XML instance error while executing the same. Even those iBots are not editable and can’t be saved during the XLM error. Support bug opened for that but not sure whether it has been fixed in .6 yet.
    This thread will be updated frequently to add more and more defects observed and the progress/resolution for it .
    So stay tuned 🙂
    Also just keep eye on OBIEE and patches and the related bug fixes to be up-to-date !

Performance Tuning and OBIEE 10/11g

Hello friends, after long time , I am again back on track … I was quite busy with couple of my mandatory schedules for last couple of weeks!

So today my topic is what are the Performance tuning key measures useful while doing report Performance testing. There are lots and I just tried to pull most of them and cover the highlights which would be very helpful while doing the Report Performance testing. Actually this could be separated across several areas like sometime it would be from DB perspective, sometime Environment parameters and sometime it would be the Repository design perspective. However the target objective is same but we need to work well to understand the performance bottleneck from which angles! This will definitely come with the experience and the different challenging environment and every places different rules needs to be applied.

Database Environment Framework:

  • RAC/Cluster / Grid based in NAS and SAN storage – This is recommended in Enterprise Architecture Platform with robust and performance resilient framework.
  • Exadata / Greenplum Architecture – For high performance and high throughput the database Architecture should be robust and especially when there lot of in memory operations intended for better performance especially for transactional analysis.
  • Memory SGA/PGA/Buffer Cache/ Temp, Undo, Redo tablespaces should be optimized using the best practice guided suitable for the underlying hardware.
  • 64 bit Processor (Multicore- Parallel server) and hyper-thread architecture required for better performance on CPU based calculations

Database Tuning Aspects:

  • Bitmap Index / Unique Index (lookup Explain Plan for less Query Cost and Index required suitable for your scenario …typically for all the join keys involved in Dimensional Star modeling)
  • Partitioning is very important and key areas to get most effective performance benefit as most of the analysis involve the time dimension.
  • Gather Statistics or analyze 30% sample of table at-least for Cost Based Optimizer to use, otherwise Rule Based Optimizer will be used . Oracle recommendation to use DBMS_STATS.AUTO_SAMPLE_SIZE for fastest gathering of stats.
  • DB Compression significantly reduces DB block read and enhance performance
  • De-normalization required rather Normalized Snowflakes
  • Parallel query(DB Environment parameter) to get benefit of report accessed on partitioned data leveraging the parallel CPU processing speeds
  • Faster Aggregation – enable Oracle DB Star Transformation (Bitmap join Indexes)

Tuning OBIEE Environment :

  • Multinode Clustering – Horizontal/Vertical scale-out in terms of multiple Admin and Managed Server in Weblogic domain.
  • Leveraging BI Server Caching to get most benefits out of the Cached queries and return the same result without hitting the database multiple times.
  • Switch off Usage Tracking to avoid extra DB operations running against each query.
  • Tuning WLS Param / JVM memory parameters


  • Remove Snowflake across dimensions and create the Foreign Key for each Dim into Fact to create Star model
  • Bitmap Index for all Foreign Key columns (for Summary reports) and Bitmap Join Index (lowest granularity based query for detailed data)
  • NULL and NOT Null column in sync with RPD and Database to avoid full outer join with NVL
  • Number of Elements in OBIEE hierarchy definition to determine efficiency of Aggregated table
  • Fragmentation specification wherever required to logically hit different LTS based on fragmented data value sets
  • Limit the number of Initialization blocks to avoid the login performance degradation. However this feature improved in 11g to allow the database query fired once when that corresponding Values referred by Init block hitted.
  • Setting the query limit for a certain number of records and certain time window helps performance improvement for long running Ad-hoc analysis.
  • Limit the Concurrent user access by setting additional parameters
  • Number of DB connection to open settings in connection pool
  • Turn off higher Query log level to avoid File system IO based operations and performance degradation.
  • Manage optimally some key values like MAX_SESSION_LIMIT (to specify how long DB connections remain open with the accessed session), SERVER_THREAD_RANGE , DB_GATEWAY_THREAD_RANGE (DB and Server execution threaded execution)



  • Charting thread and Queue related parameters amendment (MaxQueue, MaxThreads)
  • Cache related tunable parameters:

<!– Remove from the cache everything older than N minutes –>




<!– AbsoluteMaxEntries is the enforced maximum number of entries. When this maximum is reached –>

<!– subsequent queries will fail until the maximum is no longer exceeded. –>


<!– CruiseEntries is amount of entries the OracleBI Presentation server tries to maintain in its cache. –>


<!– Forces the cache to attempt to remove an old entry when MaxEntries is exceeded. –>


<!– Cleanup this cache every N minutes. –>



  • Aggregated Tables /Mviews – Follow this approach if there are huge volume of data in detail fact table. Multi-level aggregated table based design return best results.
  • Typically the biggest gains for “Detail” reports performance is :

    •Star Transformation

    •Bitmap Join Indexes


  • The biggest gains for “Summary” reports:

    •Gathering Stats 30%


    •Star Transformation


OBIEE 11g Up-Gradation – RPD Gotchas and Glitches

Objective of this thread is to walk through across several issues found in RPD post Up-gradation from 10g to 11g. Let’s first start with OBIEE 11g Warnings / Errors and then I quickly moved to other areas to explore other glitches …. Idea is to bring a valuable thread for target audience to include important topics rather the conventional one found over several other fellow Bloggers post !

Nice Oracle documentation is there to detail out the step by step up-gradation process…


Pretty simple huh?? Yes …. Until you know the unknown and erratic issues on your way soon … So hold your seat belt tight to fly across the unknown territory with several assumptions/concerns/endless issues/unpredictable behaviors and finally achieving the goal …successful Up-gradation 🙂

Repository Up-Gradation Issues

1)      There are lots of unusual warnings have been observed after up-grading the RPD to 11g version. Some of them are really nonsense. However as Oracle said that strong consistency checker is involved in the whole process to mitigate the future risk of enhancement resulting these number of warnings. Details of the warnings could be found at 11g Up-grade planning ref doc:

Refer to section: Enhanced Repository Consistency Checking


Each warning has some specific number by which we can call them. Let’s see each of them one by one:

A)     Warnings [39028] 

Resolution: Call interface checked by consistency checker to see how compatible it is with the underlying database specification and how much it is aligned with database features defined in repository. Typically we have seen after up-gradation the features retains what is in 10g. In that case, solution is to make it Default database feature against each Physical layer database. That will remove the warnings however make sure that none of your overriding database features will cause performance concern. Some of them in 10g which could be done to get performance benefit in terms of better utilization of joins. So be careful before making them default and if that is mandatory to gain the similar performance benefits then that needs to be retained even if that will throw warnings irrespective of Oracle’s recommendation.

B)      Warnings [39055]/[39054]

Resolution: Typically the join missing between the mentioned Logical Dimension and Facts. Adding the extra join will resolve your problem. Make sure it is necessary and could not cause impact in other areas or otherwise ignore if you are not going to extract the projects. It is not really mandatory to fix these warnings. We remove these warnings to get some lesser counts.

Out of this warning context, in terms of join conditions I have experienced issues with Physical layer join problems post up-gradation. Some of my join conditions were invalid and this has been observed particularly in Usage Tracking physical database. However the error it will throw is really not comprehensible and hence I removed the invalid physical joins and add them back and did similar for logical joins too. This might be one-off incident but that is true for me.

C)      Warnings [39057]

Resolution: The reason of this warning as per my analysis is , whenever you add inner joins/outer joins with logical tables in the single logical table source you definitely specify the join condition with attributes and it is not a mandate to map those logical columns with the column mapping. But this warning expects attributes participated in the join conditions should be part of the column mapping. Necessarily older designs either 7.8.5 or, it is not mandatory to be those columns in the column mapping. But here at-least the join condition column needs to be in the column mapping. I don’t know the rationale behind this extra check and I don’t know the other possible solutions to remove these warnings. But the above mentioned approach helpful for me and I am sure if you are unlucky enough but want to fix these warnings then you might have to do a lot of hard-work as one of our repository we fix around 550 of this kind of warnings … Really annoying …! Without much business or design benefit. Good luck 🙂

D)     Warnings [39059]

Resolution: Most unwanted and most confusing and problematic warnings. This warning emphasis some best practices to be adhered. Typically we have seen some snow-flaking across dimensions and leveling those dimensions in different level of hierarchy across logical table source resulting these problems. You seem to hit this problem due to incorrect and un-orthodox content aggregation leveling. However there might be several other angles and reasons too.As in the document it specified that  “a new consistency check warning (39059) highlights when a fact logical table source joins to a lower-level dimension logical table source, resulting in a potentially invalid join. If you get a 39059 warning after upgrade, verify that the join is as intended and does not result in incorrect double counting.”

Fixing those warnings is really a tedious jobs specially when my RPD already build in 7.8.5, migrated to 10g and then 11g as lot of developers mind-blowing design already enriched the RPD a lot 🙂 and while you don’t know the business reason there is no point of fixing those warnings as this caused the design changes in greater aspects and this is quite impossible if you are old enough with your RPD. Fixing this warning is good for health of the RPD for new development & indeed bad for developers but bit difficult and quite risky for older data models. For our case we left ~1500 warnings in our Repository as it is as we are not sure how much the data impact will be there in our ~650+ reports.As per Oracle ” If the join is as intended, then ignore the 39059 warning”

 Last but not the least

Apart from those warnings all errors should be fixed to have a Consistent repository and essentially you need to note that while there are 3 errors in repository your warnings count could be say 20 but after fixing those errors (which you must have to do) count can increase to 600 .Sound strange.. ! Really not , as when Consistency checker encounter error it skips showing the warnings and insist you to fix the errors before it proceed with further level of checks ! So best of luck. One more things don’t worry much about the warnings … even if there are your repository is consistent and none of the reports (apart from the complex one in catalog specially the combined requests) will show incorrect results. We have experienced this and you can easy to go ahead with warnings …. Let’s keep the life simple …. Now lets see what Oracle made for us to lead simple life …

Essentially Oracle has faced lot of questions with this mind-blowing checker (!) (yes I mean it) and they release a patch for OBIEE 11g ( to hide those warnings(not errors) but not yet for They are yet to fix this in future version, if any. See Oracle Doc ID 1365964.1 [How to Hide Selected Consistency Check Warnings in BIEE 11G]

Patch 11810367

As of when I am writing this thread for BIEE Development teams are working on a Patch for BIEE Please open an SR with BIEE Support to check if the Patch is available for your platform or not. This issue will be fixed in BIEE

2)      During up-gradation the Upgrade Assistant migrate the Security groups / roles and users from Repository to Weblogic security policy store and hence it is the best practice to up-grade the repository at-least irrespective of whether you upgrade the catalog at all. But if you think of to up-grade the catalog first then you will definitely lose all the Catalog groups and permissions setup inside your Catalog objects even if you up-grade the RPD next time. So upgrade either RPD or RPD and Catalog both and never Catalog alone.  You will hit a lot of unforeseen behavior post up-gradation with catalog privileges as it has been observed that the permissions are not propagated properly in the online catalog.

3)      Job Manager “Administrator” Password is not upgraded with RPD upgrade .It still retains the password of source RPD and you need to change it manually.

4)      Usage Tracking (S_NQ_ACCT) and Scheduling objects (S_NQ_) moved from the target database area to RCU schema and the object definition itself changed like new column added and several column types changed. So ideally it is better to copy the 11g provided Usage tracking RPD layers and merge it with your upgraded RPD .However in that case all the Usage Tracking customization needs to be properly applied too.

5)      “Act As Proxy User” functionality no more going to work with Administrator while this user is part of Weblogic Default Authenticator scheme. Ideally this Administrator user-created by default in every Weblogic Default authentication scheme as it is automatically migrated from RPD to WLS security policy. Considering your RPD has authentication scheme set to LDAP in that scenario “ACT As” is no going to work with “Administrator” as dual switching of mixed Authentication scheme not possible (in this case one is WLS authentication and another is RPD LDAP authentication).So any of the LDAP user could Act as proxy users for other LDAP users and thus authentication scheme belongs to one area only. Otherwise you will see that Act As will not populated the list of proxy users and the list will be NULL or blank.

Another way will be to define the LDAP in Weblogic itself and maintain the Administrator user in the LDAP tree so that you can use Administrator to ACT AS proxy for other LDAP users.

So either all should be LDAP of Weblogic Default Authenticator or LDAP of RPD only at a time.

6)      Post upgrade Repository could not be opened online using the Administrator password .Resolution is perform the refresh GUID activities. You will get below error in log file:

[nQSError: 13041] The GUID of user ‘Administrator’ does not match user reference GUID at the repository. Please ask the administrator to delete the old user reference at the repository and login again. The process is explained under Oracle Doc ID 1265802.1. There might be several blog in the net which already listed down the steps.

7)      In our implementation we have seen that upgraded 11g repository crashes the environment while user try to log in .However this behavior not observed for all users. Digging into details our finding is that “Log Level” value populated from external table authorization should not be NULL otherwise 11g repository will crash your environment. So make sure the loglevel field must be updated at-least with some numeric value.

8)      While Saving Online RPD Changes in the Administrator Tool of OBIEE 11g Throws “[nQSError: 37005] Transaction update failed.” This is an Unpublished bug 9884975 – 11g admin tool receives nqserror: 37005 when saving online rpd changes

9)      During check-in and saving the repository we have encountered getting error : [46036] internal assertion: condition m_lock.isacquired() . For both 8) and 9) apply Patch 12909840

10)      Issue exist with Presentation column level security default access and it is not working properly with the PROJECT INACCESSIBLE COLUMN is NULL settings of NQSCONFIG.INI.Get the patch from Oracle to get rid of this issue.

11)      I have seen several connection related problem from RPD to database and most of the errors are Unable to connect the database. This happens due to Oracle Native OCI call and Middleware Native OCI conflict. As a best practice I usually follow below rule:

Copy the same tnsnames.ora across Oracle Home and Middleware home .Then create 3 variables in Windows : ORACLE_HOME , BI_ORACLE_HOME , ORACLE_BI_HOME as Middleware Home directory and then ORACLE_INSTANCE as Middleware instance directory . Bounce all services and you will be clean with any connection.


I hope above information is helpful for your 10g -) 11g Up-gradation process . Then don’t forget to rate this thread as above with Stars ! 🙂

Stay tuned for more update on Enviroment/Configuration Issues and BI Catalog Issues ….

Latest update for those available at: https://debaatobiee.wordpress.com/2012/05/14/obiee-11g-up-gradation-issueschallenges-11-1-1-5-and-6-too/

Cheers , DxP