RE: Shutdown immediate - not quite as immedaite as I want it to

The processes the immediate shutdown waits for are long running PL/SQL-procedures retrieving information from several tables inside a loop and then inserting the results into a table at the and of each loop before it fetches the next record.
Some of these processes can run for over 40 hour. Killing the user session is often very quick. A shutdown immediate however seems to keep waiting for the entire loop to finish.

Shutdown Abort does the trick, but seems a bit of overkill all the other nights when nothing is wrong.

> -----Original Message-----
> From: Colin.Shaw_at_phs.com [SMTP:Colin.Shaw_at_phs.com]
> Sent: Friday, May 26, 2000 5:08 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Shutdown immediate - not quite as immedaite as I want it
> to
>
> Jonathan:
>
> An immediate shutdown doesn't wait for a user to complete their current
> SQL
> statement. It's just as if you KILLed the user session. If they had done
> a
> large update or insert in the current transaction you will have to wait
> for
> that all to be rolled back. However, having said that, there are some
> points-in-time when Oracle will not allow a current session to be KILLed
> immediately because it is in the middle of something which cannot be
> interrupted for any reason ("Don't interrupt me - I'm on the PHONE!").
> These are usually very short instances (no pun intended) and so normally a
> KILLed session (or all sessions from shutdown immediate) should start
> rolling back and disappearing very quickly. HTH.
Received on Fri May 26 2000 - 03:31:01 CDT