Message-Id: <10704.124033@fatcity.com> From: "Kevin Kostyszyn" Date: Fri, 8 Dec 2000 10:34:07 -0500 Subject: RE: shutdown for backup : pro's and con's This is a multi-part message in MIME format. ------=_NextPart_000_000C_01C06102.64E40D70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit RE: shutdown for backup : pro's and con'sPersonally, we do a shutdown immediate. As far as I know, if you don't do it this way and then say try to bring the database up on another machine with using the same name and the datafiles and init file, the redo logs will be corrupt and the database will not come up. I would go with the shutdown immediate. Kevin Kostyszyn DBA, Dulcian, Inc -----Original Message----- From: root@fatcity.com [mailto:root@fatcity.com]On Behalf Of Koivu, Lisa Sent: Friday, December 08, 2000 8:26 AM To: Multiple recipients of list ORACLE-L Subject: RE: shutdown for backup : pro's and con's Hi Pat, I have to use SHUTDOWN ABORT/STARTUP RESTRICT/SHUTDOWN IMMEDIATE. Otherwise our databases hang due to some refresh jobs that run continually, and my backups never start. I haven't had any problems. Think about it - If you startup and shutdown nice after a shutdown abort, the database has a chance to clean itself up. HTH Lisa Rutland Koivu Oracle Database Administrator Qode.com 4850 North State Road 7 Suite G104 Fort Lauderdale, FL 33319 V: 954.484.3191, x174 F: 954.484.2933 C: 954.658.5849 http://www.qode.com "The information contained herein does not express the opinion or position of Qode.com and cannot be attributed to or made binding upon Qode.com." -----Original Message----- From: Pat Howe - Contractor [mailto:pat.howe@Terabeam.com] Sent: Thursday, December 07, 2000 10:34 PM To: Multiple recipients of list ORACLE-L Subject: shutdown for backup : pro's and con's I would like to be convinced one way or the other on the following issue : What is the best way to take a database down for a cold backup ? SHUTDOWN ABORT STARTUP RESTRICT SHUTDOWN NORMAL or SHUTDOWN IMMEDIATE I have seen both widely used. I have always stayed away from the ABORT option because I am uneasy about taking any database down this way (hard). I am looking for a dialog on the pro's and con's of each approach. ie: Any horror stories about taking down with the ABORT option ? -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Pat Howe - Contractor INET: pat.howe@Terabeam.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). ------=_NextPart_000_000C_01C06102.64E40D70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: shutdown for backup : pro's and con's
Personally, we do a shutdown immediate.  As far as I know, = if you=20 don't do it this way and then say try to bring the database up on = another=20 machine with using the same name and the datafiles and init file, the = redo logs=20 will be corrupt and the database will not come up.  I would go with = the=20 shutdown immediate.
 
Kevin=20 Kostyszyn
DBA,=20 Dulcian, Inc
-----Original Message-----
From: root@fatcity.com=20 [mailto:root@fatcity.com]On Behalf Of Koivu, = Lisa
Sent:=20 Friday, December 08, 2000 8:26 AM
To: Multiple recipients of = list=20 ORACLE-L
Subject: RE: shutdown for backup : pro's and=20 con's

Hi Pat,

I have to use SHUTDOWN ABORT/STARTUP = RESTRICT/SHUTDOWN=20 IMMEDIATE. Otherwise our databases hang due to some refresh jobs that = run=20 continually, and my backups never start.  I haven't had any=20 problems.  Think about it - If you startup and shutdown nice = after a=20 shutdown abort, the database has a chance to clean itself = up.

HTH

Lisa Rutland Koivu
Oracle = Database=20 Administrator
Qode.com
4850=20 North State Road 7
Suite G104 =
Fort Lauderdale, FL  33319

V: 954.484.3191, x174
F: = 954.484.2933=20
C: 954.658.5849
http://www.qode.com

"The information contained herein does not express = the opinion=20 or position of Qode.com and cannot be attributed to or made binding = upon=20 Qode.com."


-----Original Message-----
From: Pat=20 Howe - Contractor [mailto:pat.howe@Terabeam.com]=20
Sent: Thursday, December 07, 2000 10:34 PM =
To: Multiple recipients of list ORACLE-L
Subject: shutdown for backup : pro's and con's =



I would like to be convinced one way or the other on = the=20 following issue :
What is the best way to = take a=20 database down for a cold backup ?
 =20
SHUTDOWN ABORT
STARTUP=20 RESTRICT
SHUTDOWN NORMAL
<BACKUP>

or

SHUTDOWN IMMEDIATE
<BACKUP>

I have seen both widely used.
I have=20 always stayed away from the ABORT option because I am uneasy = about=20
taking any database down this way (hard). =
I am looking for a dialog on the pro's and con's of each=20 approach.
ie: Any horror stories about = taking down=20 with the ABORT option ?

--
Please see the official = ORACLE-L=20 FAQ: http://www.orafaq.com =
--
Author: Pat Howe - = Contractor=20
  INET: pat.howe@Terabeam.com

Fat City Network Services    -- (858) = 538-5051  FAX: (858) 538-5051
San = Diego,=20 California        -- Public = Internet access=20 / Mailing Lists
----------------------------------------------------------------= ----=20
To REMOVE yourself from this mailing list, send an = E-Mail=20 message
to: ListGuru@fatcity.com (note EXACT = spelling=20 of 'ListGuru') and in
the message BODY, = include a line=20 containing: UNSUB ORACLE-L
(or the name of = mailing=20 list you want to be removed from).  You may