> 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.
Aside: Even if you do this the database can be tricky to restart. One
example I had to deal with was automating the daily dump of a parallel-
server database. Problem is that the disks were split with the database
up. This made restarting difficult with my single-stream server, it got
disk files that looked like a parallel server had crashed in hot backup
mode. Recovering the database also wasn't simple since Oracle's best
guess as to the sequence of logs to replay wasn't very accurate and
required code to query the remote system for data files in each cycle.
I managed to get it done with Perl using Open3 and a pair of svrmgrl
proc's on my machine and the source but it was a serious pain to automate.
sl
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
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).
