Posted: Tue Apr 15, 2008 5:43 am Post subject: Stored procedure exception handling
Novice
Joined: 13 Feb 2004 Posts: 14
We are planning to call Oracle stored procedures from within WBIMB V5.
I have been able to call them successfully.
I want to know how people who have used it in production handled errors.
The idea is that we should identify fatal errors (like database down, or stored procedure mismatch due to updates etc) and take appropriate action (say get inhibit queue automatically etc).
What are the most reasonable errors to catch and where?
You should be upgrading to v6, and not planning or developing new deployments to v5.
It goes out of support in September.
All of the rest of your questions depend entirely on the SLA of the application, and the practices of your site. And most of this should be handled outside your application. _________________ I am *not* the model of the modern major general.
Migration to V6 is being done. We are implementing this solution using V5 for the moment as it is required.
Talking to Oracle guys, apparently there is no recognized set of errors that can be checked.
So, I am checking for the presence of name of the stored procedure or
'DatabaseException' in the Exception List to stop the execution of the flow. Will see how that goes.
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