I use this technique only as a failover routine, if the production machine
were to crash: Cloning I would use standards methods as it is much faster:
But once u restored the database you can rename it.
But the steps that I take are
1.Install executables on other machine as same owner and group id as
original database(this is very important)(RESTORE using Netbackup rather
than re-install)
2.Update bp.conf in oracle home and /usr/openv/netbackup/
3. set nb_ora_client=Original client
4.startup taget database nomount
5.connect rman catalog
6.Run scripts
Sam
p.s. scripts I use are
run {
allocate channel ch1 type 'sbt_tape';
restore controlfile;
alter database mount;
}
--select min(scn) from (select max(next_change#)scn from
v$archived_log
group by thread#); -- get the last scn in svrmgrl
run {
set until scn=100075926; allocate channel ch1 type
'sbt_tape';restore database;recover database;
}
--back in svrmgrl
alter database open resetlogs
--
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).
