Mauro Souza wrote:
Hi Rich,
Oracle have a shutdown mode called *immediate*, which will disconnect all
logged users, rollback all transactions, flush cache, then bring down the
database. The *normal* way takes more time, and the *abort* way will bring
down you db pretty fast, but it will take longer to bring it back later.
As Pieter said, I usually leave the SHUTDOWN TIMEOUT big enough to prevent
data loss. In the systems I worked with, 20 minutes have been enough, but is
better to wait and avoid a long database recovery process.
Regards!
That's good to know, thanks. It sounds like 'abort' is really bad, it
apparently needs
to do some recovery upon startup. 'Immediate' may not be as bad and seems to
do some of
that recovery on the shutdown end. 'Normal' is certainly ideal for data
integrity.
But, in the interest of getting the database down in a reasonable amount of
time, if
you're just going to putty in to the guest and do an immediate shutdown then
why not
just set that up automatically and set the shutdown timer to a very big number?
While
you're fiddling about with other guests Oracle can be doing it's thing and then
you can
get back to Oracle to investigate why it's taking so long later (while the
timer is
still ticking). If it happens to shutdown in the interim, all is good.
--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service: 360-715-2467
rich.smrcina at vmassist.com
http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org
WAVV 2009 - Orlando, FL - May 15-19, 2009
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
