This content has been marked as final. Show 1 reply
If you miss out dimensions in the report then it's the responsibility of the reporting tool (via tool model/metadata) to (transparently) insert filters for the missing dimension so that the sql being sent to the database is a fully qualified olap sql query.
For example, using OBIEE as the reporting tool, the metadata built or setup in the obiee repository helps bring in the missing dimensions automatically in the report query sent to the database. More details at: http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/11g/r1/olap/biee/index.html (repository setup is part of first lesson).
If you're writing some kind of sql or using a reporting tool which does not contain an useful/intelligent middle layer (akin to the rpd in obiee) then i guess you are required to NOT miss dimensions in your query and to write or setup a more usable report which does include all dimensions. Missing out a dimension will force the sql results to come for all the members of the missing dimension and would still be correct but the flaw is more to do with "improper report specification" than "failure to return correct results".
NOTE: There are options like using Microsoft XL add-in for Oracle OLAP provided by Simba Technologies and OBIEE 22.214.171.124 or OBIEE 126.96.36.199 version which support native access to OLAP. Using either of these modes of access to Oracle OLAP Analytical Workspace, you are not constrained to refer to all dimensions.