If you lose one side of a mirrored pair, the instance doesn't notice - it just
continues to process against the survivor(s).
On the other hand, if you need to restore a backup (BCV, split mirror or
otherwise), you need to be able to roll it forward to a consistent state.
Consider a BCV split as just a fast hot backup. That is, in fact, exactly what
it is.
-Don Granaman
[OraSaurus - Honk if you remember UFI!]
----- Original Message -----
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Monday, September 24, 2001 12:40 PM
> It is my understanding that the common implementation of copying an Oracle
database on an EMC using BCVs is this;
>
> 1) put the source database in BEGIN BACKUP mode for all the tablespaces,
> 2) break the mirror,
> 3) put tablespaces in END BACKUP mode
> 4) recover on target, or backup the files.
>
> Question:
> Why is it necessary to put the database in 'hot backup' mode when splitting a
BCV? If it is just like splitting a mirror, why do you need the database in hot
backup mode at all? Wouldn't it be the same as losing one side of a mirrored
pair? When that happens, no extra processing is needed.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Don Granaman
INET: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] (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).
