SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 13458: Attempts to define a calculated member for an OLAP cube may fail with errors

DetailsHotfixAboutRate It
When a SAS 9 cube is initially opened by the OLAP Server, the global
objects defined for the cube are loaded by the Metadata Server. If an
error occurs during this process, the entire cube open fails and every
time a session (the same or another) tries to open the cube, the open
will fail and the cube is never accessible.

For example, say you have an existing cube created from SASHELP.PRDSALE
that has a calculated member defined using the ACTUALSUM measure. You
then decide to delete ACTUALSUM. You edit the cube structure in OLAP
Cube Studio, delete ACTUALSUM, and recreate cube. Then you decide to
create a new calculated member and get the following errors:

   ERROR: None of the global definitions in the DEFINE statement(s)
      could be verified as syntactically correct, or none of the
      global definitions could be registered with the metadata server.

   The MEMBER command named "[prdcube].[Measures].[newMeasure]"
      registration failed.
   The reason for failure is as follows:
   ERROR:  The immediate MDX execution failed.
   The immediate MDX execution failed.
   Formula error - An invalid member name was encountered in the MDX
      statement near: "[Measures].[ACTUALSUM]"
   An MDX syntax error occurred.
   ERROR: DEFINE and UNDEFINE statement processing failed.

To circumvent this problem, you can create a new cube with a new name.
Or starting in SAS 9.1.3, you can use the UNDEFINE statement in PROC
OLAP to undefine the problem calculated member.

Starting in SAS 9.1.3, to prevent this problem from happening, you
should undefine any calculated members that contain measures or levels
to be removed before you actually recreate the cube without them.

A hotfix will be available soon to address this, allowing you to access
the rest of the cube except the calculated members in error. Notes will
be written to the OLAP Server log about the calculated member problem
but access to the cube will resume as normal.


A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#013458

For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#013458


Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemSAS OLAP ServerTru64 UNIX9.1 TS1M09.1 TS1M3 SP1
64-bit Enabled AIX9.1 TS1M09.1 TS1M3 SP1
OpenVMS Alpha9.1 TS1M09.1 TS1M3 SP1
64-bit Enabled HP-UX9.1 TS1M09.1 TS1M3 SP1
HP-UX IPF9.1 TS1M09.1 TS1M3 SP1
Linux9.1 TS1M09.1 TS1M3 SP1
z/OS9.1 TS1M09.1 TS1M3 SP1
64-bit Enabled Solaris9.1 TS1M09.1 TS1M3 SP1
Microsoft Windows 2000 Advanced Server9.1 TS1M09.1 TS1M3 SP1
Microsoft Windows 2000 Datacenter Server9.1 TS1M09.1 TS1M3 SP1
Microsoft Windows 2000 Professional9.1 TS1M09.1 TS1M3 SP1
Microsoft Windows 2000 Server9.1 TS1M09.1 TS1M3 SP1
Microsoft Windows Server 2003 Datacenter Edition9.1 TS1M09.1 TS1M3 SP1
Microsoft Windows Server 2003 Enterprise Edition9.1 TS1M09.1 TS1M3 SP1
Microsoft Windows Server 2003 Standard Edition9.1 TS1M09.1 TS1M3 SP1
Microsoft® Windows® for 64-Bit Itanium-based Systems9.1 TS1M09.1 TS1M3 SP1
Microsoft Windows NT Workstation9.1 TS1M09.1 TS1M3 SP1
Microsoft Windows XP Professional9.1 TS1M09.1 TS1M3 SP1
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.