Veritas Storage Foundation for Oracle 5.0 Administrator's Guide, HP-UX 11i v3, Second Edition, December 2008

Control file 'ora_control2' path not explicitly
specified in init file; assuming ORACLE_HOME/dbs
All redo-log files found
Copying initTEST9i.ora to initNEW9.ora
in /local/oracle9/1/testvol
Altering db_name in initNEW9.ora
Altering control file locations in initNEW9.ora
Creating new link for clone database init file
Creating archive log directory
About to start up new database and begin reconfiguration
Database NEW9 is being reconfigured
Altering clone database archive log directory
Updating log_archive_dest in clone database init file
Found archive log destination at /testvol
The latest archive log(s) must now be applied.
To apply the logs, open a new window and perform the following steps:
1. copy required archive log(s) from primary to clone:
primary archive logs in /testvol
clone archive logs expected in /local/oracle9/1/testvol
2. ORACLE_SID=NEW9; export ORACLE_SID # sh and ksh, OR
setenv ORACLE_SID NEW9 #csh
3. /local/oracle9/links/bin/sqlplus /nolog
4. CONNECT / AS SYSDBA
5. RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE
6. enter the archive log(s) you wish to apply
7. EXIT
Press <Return> after you have completed the above steps.
<>
Resetting logs on new database NEW9
Database instance NEW9 is up and running
To clone an Oracle instance with automatic Oracle recovery
◆
Use the dbed_clonedb command as follows:
$ /opt/VRTS/bin/dbed_clonedb -S NEW9 -m /local/oracle9/1 \
-c Checkpoint_988813047
Primary Oracle SID is TEST9i
New Oracle SID is NEW9
Checkpoint_988813047 not mounted at /local/oracle9/1
Mounting Checkpoint_988813047 at /local/oracle9/1
Veritas Storage Foundation for Oracle Command Line Interface
About the command line interface
334