| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMB v7: caching an SQL Server stored procedure parameters |
« View previous topic :: View next topic » |
| Author |
Message
|
| gisly |
 Posted: Mon Jul 06, 2015 7:18 am Post subject: WMB v7: caching an SQL Server stored procedure parameters |
 |
|
Apprentice
Joined: 10 May 2012
Posts: 29
|
Hi!
I've got the following issue:
we call an SQL Server 2012 stored procedure via ODBC in Message Broker v 7 (tested on Windows and HP-Unix).
Here's the procedure definition in ESQL:
| Code: |
CREATE PROCEDURE testSP (IN someParam CHARACTER)
LANGUAGE DATABASE
EXTERNAL NAME "%.testSP";
|
The corresponding procedure someParam is VARCHAR(1).
The parameter is taken from the input message.
When we call it with a longer parameter, we get an exception:
| Code: |
(0x01000000:Name ):DatabaseException = (
(0x03000000:NameValue):File = '/build/S700_P/src/DataFlowEngine/ImbOdbc.cpp' (CHARACTER)
(0x03000000:NameValue):Line = 530 (INTEGER)
(0x03000000:NameValue):Function = 'ImbOdbcHandle::checkRcInner' (CHARACTER)
(0x03000000:NameValue):Type = '' (CHARACTER)
(0x03000000:NameValue):Name = '' (CHARACTER)
(0x03000000:NameValue):Label = '' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPmsgs' (CHARACTER)
(0x03000000:NameValue):Severity = 3 (INTEGER)
(0x03000000:NameValue):Number = 2322 (INTEGER)
(0x03000000:NameValue):Text = 'Child SQL exception' (CHARACTER)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = '22001' (CHARACTER)
)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 2 (INTEGER)
(0x03000000:NameValue):Text = '0' (CHARACTER)
)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = '[IBM][ODBC SQL Server Driver]String data, right truncation' (CHARACTER)
|
Now, the procedure owners want to correct it so that it accepts longer strings.
However, changing the procedure and even dropping it seems to have no effect on WMB. WMB only "updates" its stored procedure desciption after we restart the execution group.
Has anyone come across this issue? Of course, changing parameters is a one-time operation. Still, we wouldn't like to restart the group just because of one flow's problems. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Jul 06, 2015 10:16 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
We had this problem at one of my customers not that long ago.
Thankfully, the site procedures came to the rescue and and change like this needed a short 'outage' while the EG was restarted.
Sadly the only time we could get was 03:00-03:15. guess who drew the short straw...
I regard Stored Proc definition changes as being the same as API changes.
Personally in this case, I would have changed the name of the SP othewise confusion over what API was valid could have reigned.
Get an outage and restart the EG.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| 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
|
|
|
|
