A number of stored procedures I support query remote databases over a WAN. The network occasionally goes down, but the worst that ever happened was the procedures failed and would have to be restarted.
The last couple weeks it’s taken a sinister turn. Instead of failing the procedures hang in a wierd locked state. They can’t be killed inside of Oracle and as long as they exist any attempt to run other copies of the procedure will hang too. The only solution we’ve found is to kill the offending procedures with a ‘kill -9’ from the OS. Some of these procedures haven’t been changed for months, even years, so I suspect a root cause in the DB or DB configuration.
Any one have any ideas of what we can do to either fix the problem? Or does PL/SQL have a time-out mechanism I can add to the code so that I can create an exception that I can handle programatically?
We were never able to determine what caused this to happen. We believe it was a defect in the October 2008 cumulative patch. Perhaps a later patch as fixed it. It hasn’t happened for a couple months (and we’ve had some network outages) so hopefully the problem has gone away.