I definitely agree, the shutdown is not the problem, it is doing what
it is supposed to do in order to maintain data integrity and preserve
transactions. The real questions is 'why do you shutdown at all??', I
haven't been forced to perform a cold backup on a schedule in years. I
thought 7X24 really meant 7X24. If the production environment can deal
with the downtime necessary to perform cold backups, then couldn't that
time be used to perform batch transactions or some other necessary task.
I would recommend spending some time on hot backups and showing your
boss that the software is a little smarter these days and a complete,
point in time/ or some other time recovery is easy. Take a few
days/weeks and show him that you can give him an exact copy of his
production system anytime he wants it. Make him comfortable and your
cold backups will be a thing of the past, otherwise, get another boss!
Just my .02
Mike
Edgar Chupit wrote:
The easiest way would be shutdown abort; startup restrict; shutdown
immediate; In fact I have suspicion that this three step process will
not be much faster than a simple shutdown immediate.
But hey, it is still dangerous to restart database for backup
purposes, what if database will not startup from the script for some
reason.
It is much safer to do online backups, and you can prepare and test
all the scripts for online backup by next Sunday. At least you can
test restore of small database, and partial restore of a large one.
On 2/27/06, Robyn <robyn.sands@gmail.com> wrote:
Hello all,
Databases are Oracle 9.2.0.6 on HP-UX approximately a TB in size. (some
slightly bigger, some slightly smaller)
recommendations appreciated ...
--
Best regards,
Edgar Chupit
callto://edgar.chupit
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Feb 27 2006 - 18:13:11 CST
