I already published a post about
rman> duplicate... a couple of years ago (Rman duplicating an oracle database in a new sid two host scenario), still on 10g at that time and using a backup set being transfered to a new host. With 11g, however,
rman> duplicate... offers another option to not only restore from a source backup, leaving source online, but from an up and running database (with takes archivelog mode and some rman catalogued entries in the control file or catalogue nevetheless). Following below therefore, I’m going to show the do’s for an
rman> duplicate ... from active database... in a same host scenario, on windows again, using
oradim as well as
lsnrctl this time. The main difference, however, is employing the
spfile clause of the
duplicate command, such that
rman will set up the destination
spfile on its own. Only some file name mappings, actually like before, need to be specified. My main reference to review any new features was Duplicating a Database from the oracle 11g1 docs, other references, concerning errors that showed up underway, will be given below.
Ok, working on the same host, nothing is due to be done for software installation and stuff and we can immediately set up the new instance (note that source will be denoted tgt, for
target and the destination aux for
auxiliary, respectively). Firstly, we create a new password file for destination, with the same sysdba password as on source.
cd /d e:\oracle\product\11.2.0\dbhome_1\database orapwd file=PWDAUX.ora ignorecase=y force=y