Tag Archives: tutorial

OBIEE quiteness

It’s been awfully quite and peaceful lately in the OBIEE environment. I think everyone is busy, which is a great thing – it means people are making money. I actually remember that the most active times are the ones when there’s slow amount of work. I quickly run through the list of the OBIEE blogs I usually attend to – and most  (most – not all) of the posts are dated back in March. Myself, I’ve not had much time to blog – too busy on the project as well as developing network relationships. I apologize if I couldn’t answer one of your questions in the comments – I hope you were able to resolve the issue.

On another topic – OBIEE google’s group is doing well and growing strong (although the goal isn’t the numbers, but the quality). The quality of topics is amazing, as well as insight provided. I am starting to think that it would be advantageous to hide the material from public view (in order to encourage registrations and discourage lurkers).

I wonder how many people are doing beta testing of OBIEE 11g (and can’t tell due to NDA). I’ve already advised the client that many issues we’re battling would be solved in the new version, however, it doesn’t mean that the “fix” is right around the corner.

Stay well and feel free to connect.

The Rittman Mead BI Forum

If you’re in the UK  in late May and eager to improve your OBIEE skills, do some networking, and meet top experts in the field – I suggest you attend The Rittman Mead BI Forum. Kurt Wolff will be present (expert on all OBIEE-related topics, who worked on OBIEE’s grandfather product) for a very advanced session , where some of the topics will include:

Data modeling topics will include fact tables with different grains, solving complex security requirements, inputting user choices into formulas (for example, calculating a discounted price) without using variables, ragged hierarchies, using dynamically named physical tables, the use of specialized tables to avoid errors at query time or when setting prompts, preserving dimension values, calculations that require inner and outer joins among multiple tables, modeling a near real-time transaction environment, modeling a multi-tenant architecture.

Attendants will include: ” John Minkjan (OBIEE), Venkat Janakiraman (OBIEE, Essbase, Fusion Middleware), Mark Rittman (OBIEE, OLAP), Craig Stewart (ODI), Adam Bloom and Mike Durran (Oracle BI EE), Tony Heljula (OBIEE) and Emiel van Bockel (OBIEE, Database) and this year we are pleased to have Gerard Braat (OBIEE) and Robin Moffatt (OBIEE, Database).”

Sounds like a great opportunity to learn directly from the great OBIEE minds.


Another good one.


You are on OBI and have configured a Dashboard Prompt with a couple of columns where the value selected by the user in the first prompt column gets stored in a presentation variable, and the values in the second prompt column depends on
the value in this presentation variable.

When both column prompts are defined as ‘Drop down’ type. The prompts work
fine. The second column correctly displays in the dropdown the values.

However when the second column prompt control is defined as ‘multi select’.

No data is displayed in the prompt. The prompt displays ‘No Choices available’.

The multiselect prompt column should correctly display values in the prompt as it does when it is defined as a dropdown.


Statement describing the cause of the problem
This issue has been determined to be a bug, which is now reported in Change Request Bug No: 7571682 (MULTISELECT PROMPT AND PRESENTATION VARIABLE CAUSES ‘NO CHOICES AVAILABLE’).
The proof that this is the cause of the problem
This issue is caused by Bug No: 7571682 (MULTISELECT PROMPT AND PRESENTATION VARIABLE CAUSES ‘NO CHOICES AVAILABLE’) as per our inhouse testcase which replicated the same behavior your system exhibits.


This issue has been determined to be a bug, which is now reported in Change Request Bug No: 7571682 (MULTISELECT PROMPT AND PRESENTATION VARIABLE CAUSES ‘NO CHOICES AVAILABLE’).

As possible workarounds we have found that, on the Dashboard, when you click the ellipsis and invoke the multiselect popup and you get the message “No Choices Available.”,

1. Click the ‘Go’ button will bring back data

2. Alternatively you can enter a value in the match box and it returns data

3. Also you can consider using the vanilla constrain option for the dashboard prompts, so you can have column 2 constrained by column 1.

Please consider the above as possible workarounds.

OBIEE Tutorials

While browsing web, I’ve found the following question:

“The query logs do show that there is a cache hit but the report still takes more than 1.5 mins to display. Why ?”

Solution offered

Checking the nqquery.log when the cache is hit, it was found the time elapsed between running the query, and getting the results was only 34 seconds
2008/10/20 07:17:38
2008/10/20 07:18:12

There is a defect logged to address the fact that you might see differences in the following measures for the same query:
-Time (Analytics web > Administration > Manage Sessions > Time column
-TOTAL_TIME_SEC (Usage tracking parameter)
-Elapsed Time (in NqQuery.log)

Elapsed Time (in NqQuery.log):
This is the total clock time it takes from the point SAS receives request to
the moment it gets data from SAW or ODBC client, until the moment data leaves
Analytics Server. Response Time and Physical Query Response Time are both
included in this.
These time parameters in NQQuery.log file do not reflect the time data spent
travelling between Analytics Web and Analytics Server.

TOTAL_TIME_SEC (Usage tracking parameter):
The time in seconds that the Oracle BI Server spent working on the query
while the client waited for responses to its query requests.

Time (Analytics web > Administration > Manage Sessions > Time column

This defect is targeted to be fixed in the next main release

Also it was recommended to change the following NQSconfig.ini settings which were set very high to 100000.. The recommended values are as follows:

MAX_QUERY_PLAN_CACHE_ENTRIES = 1024; // default is 1024
MAX_DRILLDOWN_INFO_CACHE_ENTRIES = 1024; // default is 1024
MAX_DRILLDOWN_QUERY_CACHE_ENTRIES = 1024; // default is 1024

How to create a measure from data that is stored in a dimension table.

Sometimes, we need to define an Aggregated Measure based on a Dimension Table.

If aggregated calculations are performed directly from a dimension logical table field, an error similar to the following will appear:

A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: ). Please fix the metadata consistency warnings.

To resolve this type of error, put the measure indicated by the error message in a fact table object.

To define an aggregated measure of a dimension table, complete the following steps:

– Create a new fact logical table with the physical dimension table as source.

– Include all fields that should be aggregated as a measure of this new fact object.

In the Siebel Analytics version 7.5.3 repository, a good example is the Fact – Campaign Metrics fact table that is based on the W_PRG_CAMP_D physical table: