shutdown transactional Vs shutdown normal

[naushi]

What is the difference between the two. It seems the same to me since as long as one continues to send transactions in, he/she could stay logged on and neither option will bring the database down. Or does the user has to expressly log off for database to 'shutdown normal' and this is not true in 'shutdown transactional' case?

So if I log on and run a procedure which has a bunch of selects and inserts, will 'shutdown transactional' wait for the whole procedure to finish or just one select statement.

Any thoughts will be appreicated. Regards,
Naushi Hussain
Naushi.hussain@honeywell.com

 

[karluk]

Shutdown transactional is intermediate in severity between shutdown normal and shutdown immediate.

shutdown normal - no new logins. Shutdown happens after all current users disconnect. This is a very gentle way of performing shutdown, but is likely to take a long time - you are catering to your users' convenience, not your own.

shutdown transactional - no new transactions. Shutdown happens after currently active transactions complete. Connected users get automatically logged off, but not at the cost of losing work in progress. This type of shutdown will probably go faster than shutdown normal because connected users are disconnected automatically. The only delay would be if there is a run away transaction active that won't complete in a reasonable length of time.

shutdown immediate - active transactions are rolled back. Connected users get logged off after their transactions are rolled back. This figures to be the fastest of the non-abort shutdowns. The main delay would be a long running rollback of a large transaction.