Feedback
Did this article resolve your question/issue?

   

Article

SELECT queries against MySQL (Community Edition) database via the HDP ODBC connection fails

Information

 
TitleSELECT queries against MySQL (Community Edition) database via the HDP ODBC connection fails
URL Nameselect-queries-against-mysql-community-edition-database-via-the-hdp-odbc-connection-fails
Article Number000111800
EnvironmentProduct: Hybrid Data Pipeline (HDP)
Version: 4.3
OS: Windows
Database: MySQL (Community Edition)
Application: All supported applications
Question/Problem Description
SELECT queries coming from Microsoft Linked ServerĀ  against MySQL (Community Edition) Database via the HDP ODBC connection fails with the following error.
Steps to Reproduce
Clarifying Information
Error MessageCannot obtain the schema rowset 'DBSCHEMA_PROVIDER_TYPES' for OLE DB provider 'MSDASQL' for linked server '<name of the linked server>'. The provider supports the interface, but returns a failure code when it is used. (Microsoft SQL Server, Error: 7311)
Defect Number
Enhancement Number
Cause
There were some configuration issue with the Microsoft Linked Server used in this problem scenario.
Resolution
After deleting the existing linked server, restarting the env, andĀ  creating a new linked server, all the queries coming from the newly created linked server started working fine.
Workaround
Notes
Last Modified Date1/17/2019 6:41 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.