We have a Websphere message broker application calling a sql server 2005 stored procedure. The message broker application connects to the sql server through a ODBC driver.
I made changes to the stored procedure (altering the input parameter length) using the SQL management studio with the 'alter procedure....' syntax.
When the message broker application calls this stored proc, it still gets the prior version of the stored proc and not the latest one. However I can the see the changes when I execute the procedure directly from SQL management studio.
I tried to drop the stored proc and create it again but still the problem persists. Finally when we created the procedure with a new name, the issue is resolved.
Please guide me to the problem area.
Answer by Matt Whitfield ·
I would imagine that this is something to do with websphere, rather than the procedure itself - perhaps Websphere is caching information about the procedure?
If you drop the object, and re-create it, then it will give the object a new object_id, and that may well cause Websphere to update it's cache...