Re: Need a reality check!

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

--
--------------------------------------------------------------------------
Opinions expressed are my own, and not those of Oracle Corporation
Oracle DBA Resources:               http://www.geocities.com/howardjr2000
--------------------------------------------------------------------------



<kal121_at_my-deja.com> wrote in message news:8qolvs$ok5$1_at_nnrp1.deja.com...


> What do you think of the practice of putting ALL OF YOUR TABLESPACES in

> hot backup mode simultaneously? Is this a good idea or bad idea and why?

>

> (Of course I would never do this myself, but what do you all think of

> it?)

>

> Thank you

>

>

> Sent via Deja.com http://www.deja.com/

> Before you buy.