Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 


Dimension and Cube Loading Using OWB "Paris" - Part II
July 21, 2005
Mark Rittman

When you run the dimension mapping, the way the underlying table is then populated seems a bit odd at first:

What you end up with is a set of rows for each level in the dimension. The most familiar looking rows are the ones with a dimension key > 0, which are the type of dimension rows we're currently used to, with a column for each level in the dimension and one row per dimension member at the lowest level. What we also get with Paris is additional sets of rows for each of the levels above the base level, with contain data about that level and all the ones above it  - the reason for this is that it will allow future OLAP tools to create cubes that link to dimensions at all levels, not just the base level as you currently get with OWB 10g. One side effect however with the beta is that these extra rows cause the dimension member viewer in Paris, BI Beans and Discoverer for OLAP to display the dimension hierarchy incorrectly, as these additional rows (those ones with a negative dimension key) need to be filtered out at this stage - if you're having this problem at the moment, you'll need to manually remove these rows from Paris-generated dimensions and fill in the missing "Total" level column data in the remaining rows to get your dimensions displayed correctly, so you end up like this:

In the production release, Paris will still create the dimensions in this way (as they're more flexible), but the tools themselves will have a fix so they display the dimension hierarchy properly.

Once you've build your dimension (and applied the fix if you're using the beta) you can view your dimensions as normal using the Paris data viewer:

All interesting stuff. I'll try and take a look at the data profiler tomorrow if get some spare time.


 

 
��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational