If you import a SAS package file containing OLAP cube metadata where there is member-level security defined to one or more dimensions in the exported cube, the SECURITY_SUBSET setting might not be honored. If the original cube does not include secured members in presummarized computations, where the SECURITY_SUBSET=YES option is enabled, this setting might not correctly be applied to the cube's imported metadata. If this setting is not applied, then secured members might be included in the parent totals for secured dimensions. This behavior can occur when cube metadata is imported but the underlying physical cube files are not recreated.

You can circumvent this issue by either of the two methods below:

• After the import, recreate your OLAP cube to correctly update the metadata.

• Submit the following PROC OLAP code with the UPDATE_DISPLAY_NAMES option to update the cube's metadata without rebuilding the cube:

  PROC OLAP CUBE="/Shared Data/CubeName" Description="Cube Description" UPDATE_DISPLAY_NAMES ; metasvr olap_schema='SASApp - OLAP Schema' repository='Foundation' host='hostname' port=8561 userid="userid" pw="password"; run;

Click the Hot Fix tab in this note to access the hot fix for this issue.

The following SAS Notes provide information on the SECURITY_SUBSET setting for an OLAP cube:

• Usage Note 38756: Using the SECURITY_SUBSET feature of SAS® OLAP Server
• Usage Note 38872: Using the SECURITY_SUBSET=YES option and the impact on parent and visual totals

For more information and examples of using the SECURITY_SUBSET= option, refer to the SAS 9.2 OLAP Server MDX Guide.

Operating System and Release Information

A fix for this issue for Base SAS 9.21_M3 is available at: