I've recently performed several assessments to help our clients diagnose and fix their OBIEE performance problems. They often share similar design or implementation issues, and I thought it would be useful to present them here as a handy reference: * No software monitoring * Randomly changing configuration settings * Data transformation
At the Polish Oracle Users Group (POUG) conference [http://poug.org/en/timeline/] this week I'm presenting one of my favourite talks, [Still] No Silver Bullets - OBIEE Performance in the Real World [https://speakerdeck.com/rmoff/still-no-silver-bullets-obiee-12c-performance-in-the-real-world] . This presentation is based on the shared experiences of myself
One of the big changes in OBIEE 12c for end users is the ability to upload their own data sets and start analysing them directly, without needing to go through the traditional data provisioning and modelling process and associated leadtimes. The implementation of this is one of the big architectural
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
After over two years since the last major release of OBIEE, Oracle released version 22.214.171.124 in May 2015. You can find the installers here [http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/downloads/bi-downloads-2537285.html] and documentation here [https://docs.oracle.com/middleware/11119/biee/docs.htm]. 11.
Flame Graphs [http://www.brendangregg.com/flamegraphs.html] are a visualisation that I learnt about through the excellent Linux systems performance work of Brendan Gregg [http://www.brendangregg.com/], and saw Luca Canali [https://twitter.com/lucacanalidb] talk about recently at UKOUG Tech 14 [http://tech14.ukoug.org/default.asp?
Nearly four years ago I wrote a blog post entitled “Instrumenting OBIEE - The Final Chapter” [https://rnm1978.wordpress.com/2011/10/10/instrumenting-obiee-the-final-chapter/] . With hindsight, that title suffix (“The Final Chapter”) may have been a tad presumptuous and naïve of me (or perhaps I can just pretend to be
An important part of working with ODI is analysing the performance when it runs, and identifying steps that might be inefficient as well as variations in runtime against a baseline trend. The Operator tool in ODI itself is great for digging down into individual sessions and load plan executions, but
nqcmd ships with all installations of OBIEE and includes some very useful hidden functionality - the ability to generate load tests against OBIEE. There are lots of ways of generating load against OBIEE [https://www.rittmanmead.com/blog/2013/03/performance-and-obiee-test-build/], but most require third party tools of varying degrees
Understanding what is going on inside OBIEE is important for being able to diagnose issues that arise, monitor its health, and dig deep into its behaviour under stress in a load test. OBIEE exposes a set of metrics through the Dynamic Monitoring Service (DMS) and viewable through Enterprise Manager (EM)
This is the third article in my two-article set of posts (h/t [https://en.wikipedia.org/wiki/Trilogy_in_five_parts]) on extending the monitoring of OBIEE within EM12c. It comes after a brief interlude discussing Metric Extensions [https://www.rittmanmead.com/blog/2013/11/collecting-usage-tracking-data-with-metric-extensions-in-em12c/] as an alternative
In the first part of this article [https://www.rittmanmead.com/blog/2013/10/oracle-data-integrator-12c-release-part-1], we discovered the new mappings and reusable mappings, the debugger and the support of OWB jobs in the freshly released ODI 12c. Let's continue to cover the new features in ODI 12c with
This article is the final one in a series about OBIEE and performance. You can find the previous posts here: 1. Introduction [/2013/03/performance-and-obiee-introduction] 2. Test - Define [/2013/03/performance-and-obiee-test-define] 3. Test - Design [/2013/03/performance-and-obiee-test-design] 4. Test - Build [/2013/03/performance-and-obiee-test-build] 5. Execute [/2013/03/