By Torben Hein -Oracle on Jun 13, 2014
(in via Senthil )
If your OBIEE 220.127.116.11.x is set up in the following way:
- The OBIEE repository is an Oracle Database and is set up as a data warehouse
- Usage tracking is enabled in OBIEE.
( For information on how to enable usage tracking in OBIEE, refer to the following link: Setting Up Usage Tracking in Oracle BI 11g )
- The OBIEE instance is discovered in EM Cloud Control.
( For information on how to discover an OBIEE instance in Cloud Control, refer to the following link: Discovering Oracle Business Intelligence Instance and Oracle Essbase Targets )
- The OBIEE repository is discovered in EM Cloud Control.
( For information on how to discover an Oracle database, refer to the following link: Discovering, Promoting, and Adding Database Targets )
then we've got news for you:
KM Article: OBIEE 11g: How To Diagnose Slowly Performing Dashboards using Enterprise Manager Cloud Control (Doc ID 1668236.1)
takes you step by step through monitoring the SQL query performance behind your OBIEE dashboard.
This Diagnostic approach ...
- .. will help you piece together information on BI dashboard performance, e.g. processing time from the different layers of the BI system including the repository.
- .. should enable you to get to the bottom of slow dashboards by using the wealth of information available in EM Cloud Control on OBIEE and Oracle DB.
- .. will NOT fix any performance issues on its own, but will help identify bottlenecks while processing dashboard requests.
(layout and post: Torben, authorized: Lia)