Scribd
Upload
7 views

Copy or Clone Database To Another Machine

Oracle RMAN

Uploaded by

Nasir Ali
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
7 views

Copy or Clone Database To Another Machine

Oracle RMAN

Uploaded by

Nasir Ali
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Procedure to copy or clone a database from

one machine to another:

Procedure to copy or clone a database from one machibe to another:


==================================================================

1. If your database is not in ARCHIVE LOG mode, take an off-line


database
backup. If in ARCHIVELOG MODE, you can either take an on-line or off-
line
database backup.

2. On your production database, connect to "SYS AS SYSDBA" (internal)


and
do a:

SQL> alter database backup controlfile to trace;

3. Edit the controlfile trace (in $ORACLE_BASE/admin/$ORACLE_SID>/udump)


and remove the lines until you get to the 'CREATE CONTROLFILE ..'
statement. Edit this stement to read:

CREATE CONTROLFILE SET DATABASE "new_db_name" RESETLOGS


ARCHIVELOG

4. Move this script to the new machine. Edit this script to


update the directories for the datafiles and redo log
files. Also comment out the lines for "RECOVER ..." and
"ALTER DATABASE OPEN ..."

5. Restore/ or copy the backup and the archived logs (if any) to the new
machine.

6. Copy your INIT.ORA file to the new machine. Ensure your controlfile
and
archive destinations in ini$ORACLE_SID.ora (or config$ORACLE_SID.ora)
are
set properly on the new machine.

7. Set your Oracle Environment by running ". oraenv" on Unix.

8. Start sqlplus, connect SYS AS SYSDBA (internal) and run the create
controlfile script.

9. Perform a database recovery using


SQLPLUS> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;

You'll be prompted to supply an archived log file, Restore that file


to the archive log destination (if not already there) and continue.
Repeat for all archived files till you get to the last one. At that
point specify 'CANCEL'.

10. Issue the command:


SQL> ALTER DATABASE OPEN RESETLOGS;

11. Change the global name of the new database to avoid problems with
networked applicationa and replication:

SQL> ALTER DATABASE RENAME GLOBAL_NAME = new_db_name;

12. Include the new database into your backup strategy.

You're all done.

************************************************************************

You might also like