| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| ODBC 5.3(a) Driver]Optional feature not supported |
« View previous topic :: View next topic » |
| Author |
Message
|
| Dave Ziegler |
 Posted: Thu Mar 19, 2015 7:11 pm Post subject: ODBC 5.3(a) Driver]Optional feature not supported |
 |
|
Centurion
Joined: 15 Apr 2014
Posts: 118
|
We've been at this one all day, I've run out of queries to run through The Googles.
Websphere Integration Bus V9, HTTP input node to ESQL calling SQL Server stored procs. Not an ideal setup, but... SQL Server linked server to a MySQL database. All the SELECTs work, but when we attempt to INSERT or UPDATE, we get:
| Code: |
| 2322 Child SQL exception [Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB provider "MSDASQL" for linked server "MCD" returned message "[MySQL][ODBC 5.3(a) Driver]Optional feature not supported". |
If we execute the same procs in a SQL Enterprise Manager query window, they work just fine. It is only when I go through broker when the problem appears. Which made me think: permissions since two devs and a DBA can run this just fine, but once the broker user tries... choke. The DBA assures me permissions are set correctly.
We are using OPENQUERY if that matters, not sure if there's another way to do this or not, our DBA team set that all up. I'm just the guy in the middle and the front end dev is getting desperate because "Websphere is busted".
I'm not sure where else to turn, but thought I'd see if anyone out here has run into this before I start logging PMRs. Nothing more useful than that ODBC error has appeared in traces or log files, and I'm stumped 
Last edited by Dave Ziegler on Thu Mar 19, 2015 7:44 pm; edited 1 time in total |
|
| Back to top |
|
 |
| Dave Ziegler |
| Posted: Thu Mar 19, 2015 7:12 pm Post subject: |
|
|
Centurion
Joined: 15 Apr 2014
Posts: 118
|
Not sure about MySQL version, but can get that tomorrow.
| Code: |
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4266.0 (X64) Sep 26 2012 17:08:07 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
|
Edit: caught a DBA online:
| Code: |
5.6.19-enterprise-commercial-advanced-log
|
|
|
| Back to top |
|
|
| Dave Ziegler |
| Posted: Thu Mar 19, 2015 8:13 pm Post subject: |
|
|
Centurion
Joined: 15 Apr 2014
Posts: 118
|
I see this in InfoCenter:
| Code: |
Microsoft SQL Server
Define a data source for Microsoft SQL Server:
Select the driver for the version of SQL Server that you are using:
SQL Native Client for SQL Server 2005.
SQL Native Client 10.0 for SQL Server 2008.
|
I selected SQL Server for the driver, the client options are not available on my dev server but they are locally. I've tried 10.0 and 11.0 locally as well and that didn't seem to matter. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Mar 20, 2015 4:25 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I know mySQL does not show up in the list of supported DBs. However have you tried a direct ODBC or JDBC connection to mySQL?
If nothing else helps, may be a .NET Compute node or procedure could get you there...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Dave Ziegler |
| Posted: Fri Mar 20, 2015 3:04 pm Post subject: |
|
|
Centurion
Joined: 15 Apr 2014
Posts: 118
|
Tried the .NET route and same problem.
Turns out we can't issue UPDATES and INSERTS from within OPENQUERY procs also doing SELECTs. Not ideal anyway, but that enlists DTC which this driver apparently doesn't care for.
Altering the procs to EXEC other procs vs. doing everything all in one single query string solved the issue and now all is right with the world... |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
