Agenda
Customer Overview
Oracle BI Version No. of Users Database Data Volumes Platform Dashboards/Reports (approx) Subject Areas (example)
10.1.3.4 100 Oracle Database EE 10G 450GB (Compressed) Windows (OBI) / Solaris (DB) 20 / 320 Network, Voice/Data Traffic, Registrations, Faults
11.1.1.5 50 Oracle Database EE 10G 230GB Linux 10 / 100 Sales, Stock, POs, Budgeting, Deliveries, Customers, Supplier
Some reports taking up to 2 minutes Still using OBI 10g, due to resource constraints and other projects taking precedence Further aggregates on the data warehouse were not created due to project time scales and scope Data Warehouse on an Oracle DB 10g platform, hardware/software not latest generation
Reports taking up to 27 minutes Reports were mainly of an operational nature, hard to optimise Many different Time Series calculations used in some reports, going back 2 years No aggregates deployed yet
60 sec average
Target
15 min average
Target
Peak Indicators Limited 10
Proposed Solution
11
For Inmarsat, the solution would be prototyped in Oracle BI 11g. RPD and dashboards had to be upgraded as part of the exercise
12
13
1 TB RAM, 40 cores, 2.4TB Flash Middleware focussed OBI / TimesTen / Essbase / Endeca
4 TB RAM, 22TB Flash, 160 cores, 14 Exadata Storage Cells Extreme performance for all types of OLTP/DW database workload. Database Consolidation. Half/Quarter/Eighth rack options available
15
Dashboard Analysis
16
18
19
20
Dimensions
22
9 aggregates identified that would provide good levels of summarisation and cater for all reports Summarising to Hourly, Day and Month levels About 18 dimensions in total used across 9 aggregates Aggregates were similar in dimensionality to the existing aggregates on the DW, but with some very granular dimensions removed e.g. Subscriber (IMSI)
No suitable aggregates identified All reports tended to be at the lowest levels of the 3 biggest dimensions: Day, Product, Store The new aggregate tables would not provide enough summary to significantly improve reports e.g. 36M rows down to 30M rows A further round of analysis was required summarising existing data would not provide sufficient benefit
23
24
Day
If we could eliminate the Time dimension then data volumes could, in theory, be reduced by 365x per year
Store
Product
26
Store
Company Division
27
The column formula uses a FILTER() expression based on a dimension attribute from the Time dimension
This filter is applied across all reports, the Stock Type attribute is at the lowest level of the Product dimension
Peak Indicators Limited 28
30
31
Aggregate Persistence would be configured to work of these new dedicated metrics A 12x reduction in aggregate data volumes was achieved:
36M records down to 3M records
32
Aggregate Persistence
33
NOTE: On an Exalytics machine, the Summary Advisor does this automatically for you
34
36
There are two PLAN_NAME values which are the same. It is not strictly a Logical Level Key
37
38
Read the TimesTen documentation to find out the most appropriate data types for your needs. For example:
Name ---------------------PRODUCT_KEY SUPPLIER_KEY CUSTOMER_KEY SALES_VALUE SALES_QTY Oracle Data Type -----------------NUMBER NUMBER NUMBER NUMBER NUMBER TT Data Type ----------------TT_SMALLINT TT_SMALLINT TT_INTEGER NUMBER(5,2) TT_SMALLINT
Failure to use the right data types with TimesTen can make your tables 5x bigger than they need to be. In one case we reduced a table from 2.4GB down to 600MB by changing data types
40
41
42
43
Incremental Loading
44
A solution for incremental loading had to be found, but the solution had to be based on Aggregate Persistence
45
Group 1: Dimensions
48
49
9x faster
20x faster
50
Summary
51
52
Inmarsat have recently doubled the number of OBI users New dashboards being implemented involving maps and Oracle Spatial Further lines of business being introduced to OBI 11g Hopefully in the future a consolidation exercise will see the DW migrated onto their Exadata platform
27x faster
53
NOTE: This map has been produced with mock-up test data. The shading across the map bears no relevance to actual figures
Peak Indicators Limited 54
The wider the practice is adopted, the stronger the case for Exalytics These 2 examples prove Oracle BI 11g can add significant business value to customers bringing savings in time, cost and complexity We look forward to further enhancements from Oracle!
55
Further Notes
56
The Oracle DB will alter its query plan to improve efficiency with larger queries e.g. hash joins, parallel query
TimesTen can be up to 9x faster for small-med workloads, especially with Columnar Compression (gains of at least 40% on every query)
57
58
Responsiveness
Cache Size: 2GB Optimal use when <50K cached records are analysed, and no rowlevel security is required
Oracle Database
Cache Size: 400GB Rapid responses for dashboard visualisations initiating many concurrent queries. Optimal use is with Compression enabled and each query analyses <1-2M fact records.
Cache Size: 0.5TB+ Used for large analytical queries requiring high degree of parallelism
Peak Indicators Limited 59
60
The difference is: $135,200 Choosing TimesTen instead of the Oracle DB will save you enough money to pay for an Exalytics box!
61
62