Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> hot backup discussion
Yes, very bad idea. But I was wondering what happens to the database if you put all the tablespaces in hot backup mode at the same time and then the database crashes during the backup. What kind of problems would this cause?
The reason I need a reality check is because a dba here wrote a script to put all tablespaces in hot backup mode at once and I told him that was a very bad idea. Not just because of the tremendous amount of redo generated, but because of the danger of the database crashing during the backup. But I need to back that statement up.
Thanks
In article <39d54212_at_news.iprimus.com.au>,
"Howard J. Rogers" <howardjr_at_www.com> wrote:
> Lousy idea, unless you want to see your redo log sub-system thrashed
to
> within an inch of its life. When a tablespace is placed in hot
backup mode,
> the smallest change to a block within that tablespace causes the
*entire*
> block to be written to the log buffer (and hence onwards into the
online
> redo logs and the archived logs). Normally, only the changed data
itself is
> written. Hence the throughput on redo goes up enormously.
>
> So, extremely bad idea.
>
> Regards
> HJR
> --
> ----------------------------------------------------------------------
Sent via Deja.com http://www.deja.com/
Before you buy.
Received on Mon Oct 02 2000 - 17:01:17 CDT
![]() |
![]() |