Attributes in Partitions

For block storage databases, you can use attribute functions for partitioning on attribute values, but you cannot partition an attribute dimension. Use attribute values to partition a database to access members of a dimension according to their characteristics.

For example, in the Sample.Basic database, you cannot partition the Pkg Type attribute dimension, but you can create a partition that contains all the members of the Product dimension that are associated with either or both members (Bottle and Can) of the Pkg Type dimension. If you create a partition that contains members associated with Can, you can access data only on Product members that are packaged in cans; namely, 100-10, 100-20, and 300-30.

Note:

Retrieving data on attribute members of block storage databases may result in missing data. See the entry for “Dense Dynamic Calc members in nonexisting stored blocks” in Table 18, Differences Between Attribute and Standard Dimensions.

You can use the @ATTRIBUTE command and the @WITHATTR command to define partitions.

For example, to extract data on all members of the Product dimension that are associated with the Caffeinated attribute dimension, you can create a partition such as @ATTRIBUTE (Caffeinated). But you cannot partition the Caffeinated attribute dimension.

Based on the previous example, this partition is correct:

Source                    Target
@ATTRIBUTE(Caffeinated)   @ATTRIBUTE(Caffeinated)

This partition is incorrect:

Source         Target
Caffeinated    Caffeinated

For more information about these commands, see the Oracle Essbase Technical Reference.

Also see Working with Attributes.