Re: jdbc and kill -14

Ryan,

 > This leaves data in an erroneous state because all the processing was not
> finished and yet some of the dml was committed. We have a need to
> periodically shut down the application for maintenance.
>

I would work the issue from the other point of view. Bad things happen. Databases crash, servers crash, applications crash, networks fail. Think of your maintenance shutdown as a gentle reminder of the inevitable. The application must not be designed assuming everything always goes right. That is a bad design. The application needs to be changed so that it isn't vulnerable to the occasional catastrophe. Barring that, the responsible parties need to create a process for making things right. Tell them your maintenance window is like a gentle but firm dope slap.

Dennis Williams

--
http://www.freelists.org/webpage/oracle-l