Due to a limit on the length of an MDX string specified on a DEFINE statement, if you attempt to build a named set that is over 2048 characters in length, you may receive errors like:

   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.

   Syntax error detected on line 1 at column 2223.
   Found End of Statement, expecting }.

or:

   The NAMESE command named "cube.[Arpu Report Orion] AS
   {" registration failed.
   The reason for failure is as follows:
      ERROR:   The immediate MDX execution failed
               '<' is illegal in an attribute value.
   Critical TK KERNEL error
   Metadata error - A processing error was encountered
   Metadata error - The addition of the calculated member or the
      named set from the
   metadata server failed
   ERROR: DEFINE and UNDEFINE statement processing failed.

In one case, this error was received when a named set was created to include all calculated members for the cube and thus the string became too long. Using SAS^® Enterprise Guide^®, this instance was circumvented by defining several named sets, each containing some of the calculated members, and then a final named set was created to pull each of the other named sets together, still resulting in one named set to be used for reports.

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

Operating System and Release Information

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

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :