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 Performance Tuning’ Category

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 »

Implementing Query Banding in OBIEE 11g using Teradata Database

Posted by Santosh Kumar Gidadmani on September 1, 2014

Query banding allows you to pass parameters into the teradata environment, which will help teradata DBAs to analyze the queries and tune the performance.

Using OBIEE connection pool, you can configure query banding and pass every query run into teradata database table called dbc.dbqlogtbl.

1. Add the below SQL script to the OBIEE Connection pool in execute before query section.

set query_band = ‘ApplicationName=OBIEE;ClientUser=Valueof(NQ_SESSION.USER);’ for Session;

You can add other requests to get more information but below is an example to get user details.


Click new and add the above script and save the RPD, restart the services.


2. Test the query banding configurations.

Firstly, make sure the OBIEE analysis server metadata is reloaded, run couple of reports.

Run the Teradata Studio or SQL Assistance and query for the below table.

select appid, username, queryband, starttime, statementtype, querytext

from dbc.dbqlogtbl where queryband is not null and appid=’nqsserver’ order by starttime desc

The query banding must be set for the session. Setting for transaction won’t work due to the way that OBIEE sends the SQL to the Teradata Database, other arguments may be added to the query band.


You can also see that the query banding tab is also added in the Teradata ViewPoint.

Screen shot of Teradata Viewpoint before configuring query banding.


After implementing query banding, a new tab is added to the query monitor screen.




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

%d bloggers like this: