Posted: Thu Sep 16, 2004 7:52 am Post subject: Handling Oracle Stored Procedure Errors
Apprentice
Joined: 01 Aug 2002 Posts: 45 Location: Rochester, NY
We have a situation while accessing an External Oracle Stored Procedure through our WBIMB V5 CSD03 Broker where if the SP owner changes logic in code that is called by the SP, the Call Procedure call in the message flow thinks it has successfully run the SP, but errors are thrown on the Database side.
We are able to 'receive' the error message now by setting a parameter on the Call Procedure statement to INOUT and then interrogating the value.
It looks like the Broker's ODBC instance does not recognize when something internally has changed on the Database instance? Is this expected? The only way we can resolve this issue is to restart the Broker service. This is not really acceptable since I really don't want to have to restart my broker(s) in a production environment.
Has anyone encountered this situation and how did you resolve it without writing processes to restart the brokers?
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