RE: ECM / BCV / hot backup

[Gogala, Mladen]

I agree with that. Unfortunately, that is the only way because RMAN doesn't support BCV's just yet. The problem with BCV is that the database on the "Business Continuity Volume" is the same as the original, including the DBID. As you know, RMAN uses DBID for registration purposes and you cannot register the resulting database. What would be needed is for RMAN to start time-finder itself and copy (used to be "SRDF") the original database to the "BCV" version, but we aren't there yet. What is that "ECO alliance" doing, anyway (ECO = EMC, Cisco, Oracle). Be sure to have large MAXHISTORY value so that your control file contains sufficient number of redo logs. -----Original Message----- From: Tim Gorman [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 05, 2002 8:49 AM To: Multiple recipients of list ORACLE-L Subject: Re: ECM / BCV / hot backup   Do backup controlfile before step #1 and make sure that it is swept up by Omniback during step #6.   There is no need for step #2.   Don't forget that step #6 also has to back up archivelogs as well as datafiles and the controlfile backup.   ---   Better yet, do use RMAN instead.  The RMAN user's guide describes exactly this scenario... ----- Original Message ----- From: Vladimir Barac To: Multiple recipients of list ORACLE-L Sent: Thursday, December 05, 2002 5:03 AM Subject: ECM / BCV / hot backup Good morning/afternoon/evening to everyone...     I'm about to "configure"  oracle backup policy using ECM storgae and HP OmniBack. My idea is as follows     1. put all tablespaces into backup mode (db is in arch. mode),   2. sleep <some_time>   3. do the split   4. take out tablespaces of backup mode,   5. alter system switch logfile,   6. let the Omni Back do it's job.   Anu do's and don't's regarding EMC/Oracle combination?