Re: Session does not terminate when a connection drops while running PLSQL.

On 4 Jul 2002 13:17:47 -0700, rsarwar_at_ifsna.com (Rauf Sarwar) wrote:

>Generally...It is not good practice to have a client wait for "Several
>minutes" for a database call to return. If the process (Insert,
>Update, Delete) is going to take a long time then it is better to
>break it up into two. First, client submits a request and saves it in
>e.g. a holding table and returns immediately. Then that request can be
>picked up by a background process which may take several minutes to
>run independent of whether the calling client is still connected or
>not.

You aren't serious about that, aren't you? You just provided the number 1 recipe for a disaster database, requiring round the clock table maintenance. Problems like long-running statements should be *resolved* by tuning the statement.
However, you preach symptom-fighting here, adding an extra layer of crap. I'm working for more than 40 hours per week now with such a system, where I officially work 32, and I can tell you it is definitely *NOT FUNNY*

Regards

Sybrand Bakker, Senior Oracle DBA

To reply remove -verwijderdit from my e-mail address Received on Thu Jul 04 2002 - 16:30:57 CDT