BRAINOLAPAPI - Nachrichtenklasse des OLAP API
The following messages are stored in message class BRAINOLAPAPI: Nachrichtenklasse des OLAP API.
It is part of development package RSR_MDX_BASE in software component BW-BEX-OT. This development package consists of objects that can be grouped under "MDX: Basis".
It is part of development package RSR_MDX_BASE in software component BW-BEX-OT. This development package consists of objects that can be grouped under "MDX: Basis".
Message Nr ▲ | Message Text |
|---|---|
| 010 | System error: Message handler could not be activated. |
| 011 | Error occurred when starting the parser: &1 |
| 012 | Unknown error when executing MDX |
| 099 | Invalid MDX command with &2 in &1 |
| 100 | Invalid MDX command with &1 |
| 101 | Cube name &1 is invalid. |
| 102 | Cube &1 was not found. |
| 103 | An error occurred when opening Cube &1. |
| 104 | System error: Maximum number of dimensions in dataset exceeded. |
| 105 | Dimension &1 unknown |
| 106 | No command was executed. |
| 107 | The start cell with the ordinal_no &1 is not contained in the dataset. |
| 108 | The end cell with the ordinal_no &1 is not contained in the dataset. |
| 109 | Member &1 of the structure dimension &2 (&3) is unknown. |
| 110 | MDX statement uses non-supported feature: &1 |
| 111 | Disallowed MDX statement. Axes are discontinuous! |
| 112 | MDX contains invalid tuple specification. Several members of a dimension. |
| 113 | Invalid MDX statement. Member in <set> output of incorrect dimension. |
| 114 | Invalid MDX statement. Tuple in <set> output of incorrect dimension. |
| 115 | Invalid MDX statement. Set in <set> output of incorrect dimension. |
| 116 | Invalid MDX statement. CROSSJOIN using the same dimensions. |
| 117 | Invalid <numeric value expression> im MDX statement. |
| 118 | Invalid MDX statement with '&1' |
| 119 | MDX statement contains disallowed UNION of two <set> outputs. |
| 120 | MDX would contain slicer axis that is not supported |
| 121 | MDX result contains too many cells (more than 1 million) |
| 122 | No data found |
| 123 | Insufficient restrictions when browsing a member rowset. |
| 124 | MDX statement contains axis specifications that are not permitted |
| 125 | Invalid MDX statement. DESCENDANTS using different dimensions |
| 126 | Error when processing the mdx statement with &1 |
| 127 | MDX statement contains unknown hierarchy |
| 128 | No authorization to execute the MDX statement |
| 129 | MDX statement does not contain a COLUMNS axis |
| 130 | No input-ready cells found for UPDATE |
| 131 | Error while parsing MDX command |
| 132 | Internal stack of parser has incorrect status |
| 133 | Error in a nested command |
| 134 | Method &1 call not permitted. See long text |
| 135 | The request description is inconsistent |
| 136 | Variables defined at invalid postion. See long text |
| 137 | Using NON EMPTY is not permitted. See long text |
| 138 | Using calculated members is not permitted. See long text |
| 139 | Using named sets is not permitted. See long text |
| 140 | The request for properties is not permitted. See long text |
| 141 | The call is not permitted for a nested MDX statement |
| 142 | You may not use more than one hierarchy per dimension |
| 143 | Cannot determine parent node |
| 144 | Level &1 is too big (maximum level is &2) |
| 145 | Transaction (name &1) not found |
| 146 | The XML document for the MDX statement is invalid |
| 147 | Error while parsing the MDX/XML document |
| 148 | The value of attribute &1 is invalid |
| 149 | XML element &1 has an invalid number of child nodes |
| 150 | The type of the child node for &1 is invalid |
| 151 | Error while reading the OLAP data. See additional messages. |
| 152 | Destination &1 is a unicode RFC destination. See long text. |
| 153 | Syntax error: &1, row &2, item: &3 |
| 154 | Hierarchy node not authorized |
| 155 | Too many BW display hierarchies (only up to 10 hierarchies supported) |
| 156 | Result exceeds the customized size (MDX_STOP_AFTER_COMBINATIONS) |
| 300 | --- Texts for Transaction MDXTEST --- |
| 301 | Error in pretty printer |
| 302 | MDX statement syntax check |
| 303 | No syntax errors found |
| 304 | A syntax error has been detected |
| 305 | Extended Check |
| 306 | No errors found |
| 307 | An error has been detected |
| 308 | 'OLAP Access' breakpoint reached |
| 309 | 'Calculation of Calculated Members' breakpoint reached |
| 310 | 'Formatting of Cell Data' breakpoint reached |
| 311 | 'Formatting of Axis Data' breakpoint reached |
| 312 | 'Parser Call' breakpoint reached |
| 501 | Error when reading the structure of query cube &1. |
| 502 | Error when reading the texts for query cube &1. |
| 503 | Cube &1 is unknown. |
| 504 | Error when opening query cube &1. |
| 505 | Error when reading data from query cube &1. |
| 506 | Catalog &1 unknown |
| 507 | Dimension &1 unknown |
| 509 | Statement contains a disallowed MEM_UNAM &1. |
| 510 | Value &2 for characteristic &1 unknown |
| 514 | Internal MDX error with &: Integer expected |
| 515 | Internal MDX error with &: Float expected |
| 517 | Incorrect parser version |
| 520 | Internal error when creating &1 SCHEMA ROWSET. Error #&1. |
| 800 | Use transaction MDXTEST |
| 801 | Request transfered is not a valid XML/SOAP document |