The information in this article applies to:
BUG #: 469 (plato7x) SYMPTOMSWhen you change the structure of a shared dimension (in the Library folder) used in a write-enabled cube (for example, you add or delete a level), the cube stays write-enabled and you do not get any warning. If you process this cube, it remains write-enabled. This situation is problematic because:
WORKAROUNDTo prevent this problem, before making structural changes to a shared dimension, write disable the write-enabled cubes that include the dimension. Use one of the following procedures to do that:
If you have already made structural changes to a shared dimension, right-click the write-enabled cube that includes it, point to Write-Back Options, and click Delete Data. This action write-disables the cube. Repeat the preceding procedure for each write-enabled cube that includes the shared dimension. STATUSMicrosoft has confirmed this to be a problem in SQL Server version 7.0. MORE INFORMATIONAlso note that whenever a structural change is to be made to a write-enabled cube, it must be write-disabled first because its structure is no longer consistent with its write-back table. If you make any structural change within a write enabled cube, for example add a dimension, a dialog box opens in OLAP Manager that contains a warning message with the caption 'Delete Write-Back Data': If you click Yes, the cube is write disabled and all read/write permissions for the cube are disabled. If the user makes a nonstructural change, such as changing a measure's Data Type property in the cube, the cube remains write-enabled. This situation is normal. Additional query words:
Keywords : SSOSdso SSOSmgr |
Last Reviewed: July 30, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |