Liberate your data

Intelligence is all about knowledge. This website is dedicated sharing expertise on Oracle BI. More »

 

Introducing the Rittman Mead OBIEE Performance Analytics Service

Fix Your OBIEE Performance Problems Today

OBIEE is a powerful analytics tool that enables your users to make the most of the data in your organisation. Ensuring that expected response times are met is key to driving user uptake and successful user engagement with OBIEE.

Rittman Mead can help diagnose and resolve performance problems on your OBIEE system. Taking a holistic, full-stack view, we can help you deliver the best service to your users. Fast response times enable your users to do more with OBIEE, driving better engagement, higher satisfaction, and greater return on investment. We enable you to :

  • Create a positive user experience
  • Ensure OBIEE returns answers quickly
  • Empower your BI team to identify and resolve performance bottlenecks in real time

Rittman Mead Are The OBIEE Performance Experts

Rittman Mead have many years of experience in the full life cycle of data warehousing and analytical solutions, especially in the Oracle space. We know what it takes to design a good system, and to troubleshoot a problematic one.

We are firm believers in a practical and logical approach to performance analytics and optimisation. Eschewing the drunk man anti-method of ‘tuning’ configuration settings at random, we advocate making a clear diagnosis and baseline of performance problems before changing anything. Once a clear understanding of the situation is established, steps are taken in a controlled manner to implement and validate one change at a time.

Rittman Mead have spoken at conferences, produced videos, and written many blogs specifically on the subject of OBIEE Performance.

Performance Analytics is not a dark art. It is not the blind application of ‘best practices’ or ‘tuning’ configuration settings. It is the logical analysis of performance behaviour to accurately determine the issue(s) present, and the possible remedies for them.

Diagnose and Resolve OBIEE Performance Problems with Confidence

When you sign up for the Rittman Mead OBIEE Performance Analytics Service you get:

  1. On-site consultancy from one of our team of Performance experts, including Mark Rittman (Oracle ACE Director), and Robin Moffatt (Oracle ACE).
  2. A Performance Analysis Report to give you an assessment of the current performance and prioritised list of optimisation suggestions, which we can help you implement.
  3. Use of the Performance Diagnostics Toolkit to measure and analyse the behaviour of your system and correlate any poor response times with the metrics from the server and OBIEE itself.
  4. Training, which is vital for enabling your staff to deliver optimal OBIEE performance. We work with your staff to help them understand the good practices to be looking for in design and diagnostics. Training is based on formal courseware along with workshops based on examples from your OBIEE system where appropriate

Let Us Help You, Today!

Get in touch now to find out how we can help improve your OBIEE system’s performance. We offer a free, no-obligation sample of the Performance Analysis Report, built on YOUR data.

Don’t just call us when performance may already be problematic – we can help you assess your OBIEE system for optimal performance at all stages of the build process. Gaining a clear understanding of the performance profile of your system and any potential issues gives you the confidence and ability to understand any potential risks to the success of your project – before it gets too late.

The physical column has property Length set to zero

Problem: Consistency Check Warning No. 39064

Screenshot:

The physical column has property Lenght set to zero

Screenshot text:

WARNINGS: 
GLOBAL:
[39064] The physical column '[PHYSICAL_SCHEMA].[PHYSICAL_DB]."S_NQ_ACCT"."QUERY_BLOB"' has property Length set to zero.

Solution:

When you view data in physical layer, the column is not displayed in the results

  • double click on the physical column, in this case QUERY_BLOB

The physical column has property Lenght set to zero 2

  • set Length to 4000 (= maximum size)
  • click OK
  • check consistency

Het bericht The physical column has property Length set to zero verscheen eerst op OBIEE 24/7 | Oracle Business Intelligence.

HTML in column heading

It is possible to use HTML tags in column headings.

  • edit a report
  • edit column formula

break in column heading 1

  • check Contains HTML Markup
  • enter Column Heading (for example the tag <br> is used)
  • go to Results

break in column heading 2

The tag <br> is read as a HTML Markup and handled as a “break”. We can see that the “C” is under the “B”.

Het bericht HTML in column heading verscheen eerst op OBIEE 24/7 | Oracle Business Intelligence.

Logical element has no physical data link

Problem: Consistency Check Error No. 42004

Screenshot:

Logical element has no physical data link

Screenshot text:

[nQSError: 42004] Logical element [ELEMENT] (ID=2006:232445) has no physical data link.
[nQSError: 23013] An error occurred when extracting the metadata definition for the Attribute '[SUBJECT AREA].[TABLE].[COLUMN]'.
[nQSError: 15023] Error in setting up logical column measure: [COLUMN].
[nQSError: 15001] Could not load navigation space for subject area [SUBJECT AREA].

Cause:

The physical column that belongs to the presentation column [ELEMENT] is deleted, but the logical column where this physical column was mapped to, is still in the logical model.

Solution:

  • insert the physical column again or remove the logical column
  • check in

Het bericht Logical element has no physical data link verscheen eerst op OBIEE 24/7 | Oracle Business Intelligence.

The Level has a primary key whose columns are variable based

Problem: Model Check Error No. 38160

Screenshot;

Level has a primary key whose columns are variable based. Aggregate Persistence will not be able to create any aggregates at this level

Screenshot text:

[38160] The Level [BUSINESS MODEL].[HIERARCHY].[LEVEL] has a primary key whose columns are variable based. Aggregate Persistence will not be able to create any aggregates at this level.

Possible solution:

  • open Logical Table Source

Level has a primary key whose columns are variable based. Aggregate Persistence will not be able to create any aggregates at this level 2

  • click Content
  • remove WHERE clause
  • click OK
  • check model

The Model Error is gone

Het bericht The Level has a primary key whose columns are variable based verscheen eerst op OBIEE 24/7 | Oracle Business Intelligence.