SYMPTOM:
Users trying to connect to Oracle Essbase data sources can possibly face the error shown below:
This error will show up when trying to open the MDX Cube catalog from Strategy Developer.
Additionally, no error is seeing while creating the Database Instance to connect to a specific Essbase Catalog.
Also, the errors shown below could be found in the DSSErrors logs:
Catalog Server trace:
2011-03-22 13:17:44.506-06:00 [HOST:HOST1][PID:8764][THR:1348][Catalog Server][Error][0x8004180E] Error in accessing information from the external data source (Database Instance: EssBase Database Instance, Error: XMLA Discover failed. SOAP Error. Error type: XMLA error. XMLAError[SOAP Fault]: <faultcode> SOAP-ENV: client </faultcode><faultactor> XML for Analysis Provider for Essbase </faultactor><faultstring>null</faultstring><detail></detail>. The embedded SOAP error is: <?xml version="1.0" encoding='UTF-8'?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode> SOAP-ENV: client </faultcode> <faultstring><![CDATA[null]]></faultstring> <faultactor> XML for Analysis Provider for Essbase </faultactor> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> . Connection String: PROVIDER=Essbase;DATA SOURCE=SOURCE1;.)
DB Classes Traces:
2011-03-22 13:17:44.506-06:00 [HOST:HOST1][PID:8764][THR:1348][Database Classes][Error] XMLA Discover failed. SOAP Error. Error type: XMLA error. XMLAError[SOAP Fault]: <faultcode> SOAP-ENV: client </faultcode><faultactor> XML for Analysis Provider for Essbase </faultactor><faultstring>null</faultstring><detail></detail>. The embedded SOAP error is: <?xml version="1.0" encoding='UTF-8'?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode> SOAP-ENV: client </faultcode> <faultstring><![CDATA[null]]></faultstring> <faultactor> XML for Analysis Provider for Essbase </faultactor> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> . Connection String: PROVIDER=Essbase;DATA SOURCE=source;. Connection String: PROVIDER=Essbase;DATA SOURCE=SOURCE1;. SQL Statement: MDSCHEMA_PROPERTIES.
CAUSE:
This issue can occur if customers are trying to connect from Strategy to an empty Catalog on the Essbase side.
ACTION:
Users should try to connect to a different cube using the same Database instance. They can review whether a specific cube contains data using a different Essbase tool (Microsoft Excel Add-in, or any other native tool) to make sure that the connection will be successful.
Third Party Software Installation WARNING
The third-party product(s) discussed in this article is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
