Re: Why is it so difficult to shutdown Oracle?
Date: 1996/01/24
Message-ID: <sfunk-2401961519050001_at_ict48.southwind.net>#1/1
In article <4e5knd$hd5_at_caesar.ultra.net>, rblizard_at_bb.cmcsys.com (Bob Blizard) wrote:
:
:SHUTDOWN IMMEDIATE prevents new transactions from beginning, and
:forces rollbacks on all uncommitted transactions. Then it suts down
:the database. As a result, 'immediate' does not mean 'instant', but
:'start right now'.
:
:You can wait at the shutdown end (shutdown immediate), or wait at the
:startup end (shutdown abort), but no matter what, you will have to
:wait for uncommitted transactions to be rolled back. It is generally
:better to do it right than do it fast.
:
A little off the subject, but we use shutdown immediate and it takes care of everything fine. BUT does anyone know of an easy way to notify users of what is going on - that is, that they lost all uncommitted transactions. Also is there an easy way to let users know what is going on when they can't access the downed database?
We are using an IBM R6000 running AIX 3.2.5 and Oracle7. The clients are using IBM PS/2 486SLC3's running PC DOS 6.3, Windows 3.1, and Oracle Forms 4.0. The machines are connected by Oracle's TNS over TCP/IP.
-- ------------------------------------------------------------------ |Sam A. Funk http://www.southwind.net/~sfunk/ sfunk_at_southwind.net| |Wichita, KS Guitarist (self-proclaimed) Macintosh Fanatic| ------------------------------------------------------------------Received on Wed Jan 24 1996 - 00:00:00 CET