Distinct Members Report

This report shows the number of distinct members within a hierarchy level. Aside from providing information about member counts, you can use the Distinct Members report to identify ragged hierarchies and hierarchies that have multiple top members.

Actions

Lists the hierarchy levels. Select a level to activate the Show SQL and Details buttons.

Click Show SQL to display the SQL statement that generated the result for the selected level.

Click Details to display the Details for Members at Level Level Name (depth) in Hierarchy dialog box.

The columns that the table can contain are the following:

Status: Indicates whether the level has a problem. A check mark in a green circle indicates that no problem exists. An exclamation point in a yellow triangle indicates a warning. An X in a red circle indicates an error condition.
Dimension Name: The name of the dimension.
Hierarchy Name: The name of the hierarchy of the dimension.
Level Name: The name of the level of the hierarchy.
Depth: The depth of the level in the hierarchy. Level 1 is the top-most level.
Distinct Members: The number of distinct dimension members in the level.

Tip:

Click the down arrow to select the columns to display in the table.

The columns the messages table are the following:

Severity: Indicates whether the message is an error condition or a warning.
Dimension: The name of the dimension to which the message applies.
Message: The text of the message, including a message code. Each message begins with a message code.

The Distinct Members report can contain the following messages.

DV-0001

This message indicates that a hierarchy has more than one top member. For example, a calendar year hierarchy might have multiple top members, such as 2011, 2012, 2013, and 2014.

Having more than one top member might cause problems in SQL-based and MDX-based applications that allow a dimension to be excluded from a query. For example, consider a cube dimensioned by time, product and customer. If a user creates a report with product and customer, but not time, values, then the application does not have a single top-level member that represents the total of the time dimension.

Some applications might attempt to summarize data from existing top members. Doing so might return data that is inconsistent with the calculation rules of the cube, for example summing a rank or a per cent change measure. Other applications might default to one of the top members.

You can resolve this condition by adding a single top member to the hierarchy. For example, you could add an ALL TIMES level to the hierarchy of the time dimension with a single member such as All Times.

DV-0002

This message indicates that a detail (leaf) level in a hierarchy has fewer members than the parent level. When this occurs, the hierarchy might be ragged, although other problems might also exist. See message DV-0006 in "Rows with Null Members Report" for more information on ragged hierarchies.

DV-0003

This message indicates that an aggregate level in a hierarchy has fewer members than the parent level. When this occurs, the hierarchy might be skip-level, although other problems might also exist. See message DV-0007 in "Rows with Null Members Report" for more information on skip-level hierarchies.