Oracle Business Intelligence and Data Warehousing Practice Notes and Knowledge Repository

  • About Me

    Hello Friends,

    This is Santosh Kumar Gidadmani, a Business Intelligence and Data Warehouse Enthusiast passionate about blogging articles in the BI, Data warehousing, space. This is my attempt to share my experience and knowledge on Oracle BI & Data Warehousing Subjects.

  • OBIEE 11g Certified Implementation Specialist

  • Oracle Partner Network Certified Specialist

  • Visit My Profiles

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 73 other followers

  • Blog Hits Since Nov 2010

    • 364,321 Hits
  • Live Traffic

  • Visitors Country

    Since-Mar'12Free counters!

Archive for the ‘OBIEE 11g Errors’ Category

OBIEE 11g Null Values in Prompts

Posted by Santosh Kumar Gidadmani on October 25, 2014

If you get null values in prompts like shown below


There are two ways to fix this issue, either you make this prompt mandatory by checking on ‘Require user input’ or on the RPD level by unchecking the Nullable option under the physical column as shown below





Posted in OBIEE 11g, OBIEE 11g Dashboards, OBIEE 11g Errors, OBIEE 11g Prompts | Leave a Comment »

Dashboard Print Error – Page Number and Fmap Images – Error Codes: UH6MBRBC

Posted by Santosh Kumar Gidadmani on October 18, 2014

After apply patch, there was a big found when we click on the Dashboard Print -> Printable PDF if we use Page number or images. This is shown in my previous article…click here.

To fix this issue, you have to apply another patch – from my oracle support. (Refer this number in the my oracle support – Doc ID 1913713.1)

Error when click on Dashboard Print->Printable PDF

This error is caused if you include page number and fmap images on the header or footer.



Posted in OBIEE 11g, OBIEE 11g Analysis, OBIEE 11g Dashboards, OBIEE 11g Errors, OBIEE11g Dashboard Pages | Leave a Comment »

OBIEE Database Type for Teradata Database

Posted by Santosh Kumar Gidadmani on September 21, 2014

If you import the physical schema into the physical layer, the database name and type are usually assigned automatically. However, if the OBIEE server cannot determine the database type, an approximate database type is assigned to the database object. If necessary, replace the database type with the closet matching entry from the database drop down list.

Example: When you import the data from Teradata Database (tables or views), by default the OBIEE database type will be V2R6 but the latest database type will be different. I have connected to Teadata Database version 14.10 the OBIEE database type should be V13 as shown in second screen shot below.

Default Database Type


If you keep the Teradata V2R6, you will get the database features warning during global consistency check (the features in database ‘Semantic Views’ do not match the defaults).

Change to V13


When we have the closet database type, you should not see any errors or warning messages on the database features.




Posted in OBIEE 11g, OBIEE 11g Errors, OBIEE 11g Performance Tuning, OBIEE 11g RPD, OBIEE11g on Teradata Database | Leave a Comment »

%d bloggers like this: