| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Stored Proc call error - MS SQL Server 2008 |
« View previous topic :: View next topic » |
| Author |
Message
|
| wmbv7newbie |
 Posted: Fri Jul 25, 2014 3:45 am Post subject: Stored Proc call error - MS SQL Server 2008 |
 |
|
Centurion
Joined: 13 May 2014
Posts: 121
|
Hi,
I am calling a Stored Proc from an external database. They are using SQL server version 10.50.4000.0.
They have two parameters, one input and other output. Both are set to accept and return xml.
We have tried changing several things on both sides but I am not getting any results back from them. Although I am able to send the xml to them successfully.
1. Tried with in and out params. They have type defined as xml.
| Code: |
CREATE PROCEDURE CREATE_ORDER_SP_OASIS(IN p1 CHARACTER, OUT p2 CHARACTER)
LANGUAGE DATABASE
EXTERNAL NAME "dbo.P_ICOM_ESB_COSTPROPOSAL_PRI"; |
This gives error -
| Quote: |
| The procedure '&1' with '&2' parameters could not be match with a corresponding Database stored porocedure |
2. Tried with Result Set but getting NULL in returning result Set. They removed the out parameter and returned the xml as result set.
| Code: |
CREATE PROCEDURE CREATE_ORDER_SP_OASIS(IN p1 CHARACTER)
LANGUAGE DATABASE
DYNAMIC RESULT SETS 1
EXTERNAL NAME "dbo.P_ICOM_ESB_COSTPROPOSAL_PRI"; |
Not sure if there is any specific setting on either side that is missing.
The same code works fine with Oracle server.
Thanks!
Last edited by wmbv7newbie on Fri Jul 25, 2014 12:49 pm; edited 1 time in total |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jul 25, 2014 4:43 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Did you check whether the ODBC is set up properly? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wmbv7newbie |
| Posted: Fri Jul 25, 2014 5:39 am Post subject: |
|
|
Centurion
Joined: 13 May 2014
Posts: 121
|
I checked the properties in the ODBC settings but doesn't look like there is any specific config.
| Quote: |
Driver=/opt/ibm/mqsi/8.0.0.2/ODBC/V6.0/lib/UKmsss24.so
Description=
Address=
AnsiNPW=Yes
Database=
QuotedId=No
ColumnSizeAsCharacter=1
LoginTimeout=0 |
The address and Database have values specific to the DB we are connecting. |
|
| Back to top |
|
|
| wmbv7newbie |
| Posted: Fri Jul 25, 2014 12:59 pm Post subject: |
|
|
Centurion
Joined: 13 May 2014
Posts: 121
|
I found a similar topic being discussed in another question -
http://mqseries.net/phpBB/viewtopic.php?t=63812&sid=a3e3587ad50bfd94364d863f2d2ad851
From all the replies, it looks like WMB version 8.0.0.2 should have fixed this issue.
I gather that I need to check all the below one by one and if none of this works, will need to raise the problem with IBM.
1. Check the ODBC driver to be 'SQL Native Client 10.0' since it is SQL Server 2008.
2. Try using the varchar(8000) as datatype.
3. Try representing the varchar(max) as BLOB
If anyone can think of anything else, please advise.
Thanks! |
|
| 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
|
|
|
|
