Readme for

MDX Provider for Oracle OLAP

October 15, 2015


  1. Release Package Content
  2. Last Minute Notes
  3. Change History
  4. Known Issues





1.      Release Package Content


This package consists of:


a.      MDXProviderforOracleOLAP_setup.exe

This single installer installs all the required components of the MDX Provider for Oracle OLAP.


b.      readme.html

This readme file.


2.     Last Minute Notes


None at this time.


3.     Change History


Changes in

a.      Fix display issue where a calculated member has no measure value.

b.      Fix crash that could occur after pressing ‘Test Connection’ when creating a connection.

c.       Fixed issue where DBPROMPT_NOPROMPT was not translated to SQL_DRIVER_NOPROMPT causing authentication dialog to appear when a password is not specified. Also change error message in certain scenarios with incorrect/missing password to return DB_SEC_E_AUTH_FAILED instead of E_FAIL.

d.      Fixed issue when using CurrentMember method defaulting to the Default/All member when used in an expression with a function. For example, HIERARCHY.CurrentMember.lead(-1).


Changes in

e.      Include both Oracle Instant Client and Simba Oracle ODBC drivers in installer.

f.        Fixes for various Excel errors including multi-select filters, double password prompting, slicer password prompting, and calculated member functionality.

g.      AWM plugin ‘Dynamic’ format string selection and fix ‘General Number’ format.

h.     Numerous fixes to reduce memory usage for various MDX functions and calculated member queries.

i.        Add option to select long description as the member caption (default is short description).


Changes in

a.     Fixed issue with inconsistent ordering between hierarchy metadata query and level cardinality query

Changes in

a.      Added EnableHideCube option

Changes in

a.      Fixed issue with session close causing Excel crash

Changes in

a.      Fix to get cell properties for defined calculated measures in Excel 2013

Changes in

a.      Fix to find the correct ALL member when custom member is created (which has NULL level_name)

Changes in

a.      Fixed SQL that requires HIER_ORDER to be not NULL, which is not always the case. Check the Member_Type instead ( .

Changes in

a.      Fixed issue with LEVEL_NUMBER restriction.

Changes in

a.      Optimizations for sparse queries.

Changes in

a.      Corrected a regression where non-string short descriptions were not being properly converted to member captions

What’s new in since

a.      Support for Excel 2013.

b.      Support for Windows 8.

c.       Additional improvements to MDX functions.

d.      Support for mixed case specification of the [MEASURES] dimension in MDX queries to better support client tools.

e.      Support for date-time filtering within Excel 2007, Excel 2010, and Excel 2013.

f.        Support for hiding of base cubes, see the manual for additional details.

g.      Support for display of Oracle OLAP custom members.

h.     Return levels from the correct cube when successive MDSCHEMA_LEVELS queries are performed with different cube names.

i.        A new extended property, “MemberUniqueNameConstruction”, has been added. Setting this property to 1 will turn off depth-based level names for value-based hierarchies. The default value of 0 will maintain previous behavior.


4.     Known Issues


·         For a production environment, ensure you have updated your Oracle OLAP installation to correct a few bugs (some described immediately below) and obtain improved performance.

·         Without the Oracle OLAP C patch, a user who has access to multiple analytic workspaces may encounter an “end-of-file” error from the database when retrieving cube metadata.

·         Without the Oracle OLAP B patch, Excel’s report filter may be slow or not work at all when used with a moderate number of members.

·         Without the Oracle OLAP D patch, Excel’s report filter may not return correct results in a rare combination of 4 circumstances. This is documented in the Known Issues section of the User and Admin Guide.

·         Without the Oracle OLAP D Patch, if an aggregator is not typical for that data type (e.g. not sum for numeric nor concatenation for strings), you will not get the desired aggregation when a report filter is applied and the report filter has N of M members selected (where 1 < N < M). Instead, you will just get the typical aggregation function for that data type.

·         When creating dimension attributes in AWM, using the ‘Create level attribute columns in views’ option will result in the display of duplicate member properties in Excel pivot tables. This option is used to allow level-specific attributes to be more readily accessible within Oracle OLAP views and is not required for the MDX Provider for Oracle OLAP to retrieve and display member properties.

·         If the machine that AWM is running under (i.e., the machine that is used to create your schema) is a Windows machine that has a locale other than ‘English (United States)’, then you need to set the NLS_LANG environment variable on the client machine (e.g., the machine that you are running Excel Pivot Table) to the same locale as the AWM machine. Otherwise, you will not see the correct caption for your dimension, hierarchies, attributes, etc. in your pivot table. This is due to the fact that AWM uses system locale on Windows, while Oracle ODBC driver uses NLS_LANG environment variable/registry to set the session NLS parameters. For more information on how NLS_LANG environment affects Oracle ODBC performance refer to the manual.

·         Also, please see the Known Issues and Troubleshooting sections of the User and Admin Guide.