:34 AM
>To: Multiple recipients of list ORACLE-L
>Subject: Re: re BCV / SnapShot / SnapClone and the ALTER SYSTEM
>
>
>John, I know that fro RMAN tablespaces need not be in hot backup
>mode. The trick with susspend is quick & dirty way of achieving
>the same effect as wi
; http://www.klove.com
>
> ** The opinions and facts contained in this message are entirely mine and do
> not reflect those of my employer or customers **
>
> >-Original Message-
> >From: Hemant K Chitale [mailto:[EMAIL PROTECTED]
> >Sent: Saturday, January 10,
65 at
http://www.klove.com
** The opinions and facts contained in this message are entirely mine and do
not reflect those of my employer or customers **
>-Original Message-
>From: Hemant K Chitale [mailto:[EMAIL PROTECTED]
>Sent: Saturday, January 10, 2004 6:34 AM
>To: Multiple
Yes, I hadn't read the line
"so the tablespaces had to be put into backup mode or (8i and after) the
database had to be suspended"
you _do_ have an OR between the backup mode and the database .. suspended.
We hadn't heard of anyone using the SUSPEND and didn't want to take the chance
of a databas
I should have expressed myself more clearly. Suspend is not necessary, it's only fast.
Basically,
with suspend, you don't put tablespaces into backup mode. You suspend, resync, split
and start aonther instance as if it crashed. As no I/O is going to disk, datafiles
aren't
fuzzy, so no recovery
