FIX: Dimension Wizard Does Not Allow Creating Time Dimension Hierarchies with DB2 Date Columns

This article was previously published under Q248619
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 1378 (SQLBUG_70)
SYMPTOMS
OLAP Manager Dimension Wizard does not allow users to create time dimension hierarchies (such as year, month, day, and so forth) with IBM Data Base 2 (DB2) database columns of "date" data type. When the user tries to specify a "time" dimension, the following error message appears:
OLAP Manager
Could not count the members of the ‘Year’ level.
Cannot open the record set.
Query: …
Error: The operation requested by the application is not allowed if the object is closed.
WORKAROUND
To work around this problem, use the Dimension Wizard to create this dimension as a "standard" dimension and then use the Dimension Editor to manually edit the "member key column" property of the levels with corresponding DB2 date functions to display the time hierarchy (such as year, month, day, and so forth). Other properties such as "level type" may need to be changed as well.
STATUS
Microsoft has confirmed this to be a problem in SQL Server OLAP Services version 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server OLAP Services version 7.0. For information about how to download and install the latest SQL Server OLAP Services Service Pack, see the following Microsoft Web site: For more information, contact your primary support provider.
MORE INFORMATION
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Properties

Article ID: 248619 - Last Review: 02/28/2014 00:29:54 - Revision: 4.1

  • Microsoft SQL Server OLAP Services
  • kbnosurvey kbarchive kbbug kbfix KB248619
Feedback