| Author |
Message
|
| wmb_wps_soa |
 Posted: Tue Jul 29, 2014 1:21 pm Post subject: |
 |
|
Acolyte
Joined: 19 Feb 2010
Posts: 65
Location: Detroit,Michigan,USA.
|
Hi All,
Does anyone knows if overloaded oracle procedure is supported in IIBv9 OR IIBv10 via ODBC?
Thanks
SJ |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jul 30, 2014 5:13 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| wmb_wps_soa wrote: |
| Does anyone knows if overloaded oracle procedure is supported in IIBv9 OR IIBv10 via ODBC? |
Have you tried it?
Currently no-one knows what IIBv10 can do that can talk about it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jul 30, 2014 5:13 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| wmb_wps_soa wrote: |
Hi All,
Does anyone knows if overloaded oracle procedure is supported in IIBv9 OR IIBv10 via ODBC?
Thanks
SJ |
Not liquely. Did you create an RFE for it? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 30, 2014 5:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
| Not liquely. |
Is the bar open already? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jul 30, 2014 5:44 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
| fjb_saper wrote: |
| Not liquely. |
Is the bar open already? |
Sure the Likor is running.... Not enough OJ this morning...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wmb_wps_soa |
| Posted: Wed Jul 30, 2014 9:02 am Post subject: |
|
|
Acolyte
Joined: 19 Feb 2010
Posts: 65
Location: Detroit,Michigan,USA.
|
Thank you both.,
So I assume its not supported in IIBV9 either.
I have a scenario, where the DBA created a wrapper stored procedure with an unique name which calls the overloaded procedure internally. Now when I call the wrapper stored procedure from broker (7.0.0.5), its still erroing out with "Mismatch in in/out parameters". Is this still not support by broker? Using the wrapper stored procedure which calls the overloaded stored procedure?
Any help will be much appreciated on this.
Thanks
SJ |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 30, 2014 9:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| wmb_wps_soa wrote: |
| Now when I call the wrapper stored procedure from broker (7.0.0.5), its still erroing out with "Mismatch in in/out parameters". Is this still not support by broker? |
If the wrapper procedure is a "simple" stored procedure with "simple" parameters it's perfectly supported; no version of IIB/WMB can see what the stored procedure is doing inside the database.
So what you're describing is a simple mismatch between the definition of the stored procedure parameters in ESQL and what the stored procedure is using. I would theorise that whatever highly ingenious mechanism the DBA has used to map multiple overloaded parameters into a single wrapper renders them not "simple" and hence beyond IIB's understanding.
What is the exact definition of the procedure in ESQL?
What is the exact definiton of the wrapper stored procedure called from ESQL?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| wmb_wps_soa |
| Posted: Wed Jul 30, 2014 10:49 am Post subject: |
|
|
Acolyte
Joined: 19 Feb 2010
Posts: 65
Location: Detroit,Michigan,USA.
|
The issue that I am talking about is in WMBV7005.
The wrapper stored procedure that the DBA created has the same name as the overloaded stored procedures(2 stored procedure with same name, one with 7 parameters and second one with 9 parameters).
However the wrapper procedure is in different oracle package(package# CSB1210) than the overload procedures(package#(CSB2450).
Theoretically, for brokerthe wrapper procedure is a unique stored procedure with unique name in the package, but why is it still failing with "Mismatch in parameters"
Thank you
SJ |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 30, 2014 10:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| wmb_wps_soa wrote: |
| why is it still failing with "Mismatch in parameters" |
| Vitor wrote: |
What is the exact definition of the procedure in ESQL?
What is the exact definiton of the wrapper stored procedure called from ESQL?
|
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| wmb_wps_soa |
| Posted: Wed Jul 30, 2014 2:03 pm Post subject: |
|
|
Acolyte
Joined: 19 Feb 2010
Posts: 65
Location: Detroit,Michigan,USA.
|
Sorry it was a mismatch in my declaration in the broker code. After I fixed it, everything started working with the wrapper stored procedure.
Summary:
Wrapper stored procedure Name # ABC in package# P123 calls overload procedure with the name# ABC in package# P456. And it works fine.
Thanks Guys
SJ |
|
| Back to top |
|
|
|
|
