Scribd
Upload
21 views

Cloning Database Method

The document provides steps to clone an Oracle database from an old system to a new system. The steps include: 1) Generating a script on the old system to create a new control file and copying data files and redo logs to the new system. 2) Editing the control file script to point to the new file names and locations on the new system. 3) Creating necessary directories and copying the initialization file to the new system. 4) Running the control file script to start the database clone and enabling archivelog mode.

Uploaded by

diranj
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
21 views

Cloning Database Method

The document provides steps to clone an Oracle database from an old system to a new system. The steps include: 1) Generating a script on the old system to create a new control file and copying data files and redo logs to the new system. 2) Editing the control file script to point to the new file names and locations on the new system. 3) Creating necessary directories and copying the initialization file to the new system. 4) Running the control file script to start the database clone and enabling archivelog mode.

Uploaded by

diranj
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Cloning Database

STEP 1: On the old system, go into SQL*Plus, sign on as SYSDBA and issue: alter database
backup controlfile to trace. This will put the create database syntax in the trace file directory. The trace keyword tells oracle to generate a script containing a create controlfile command and store it in the trace directory identified in the user_dump_dest parameter of the init.ora file. It will look something like this:
STARTUP NOMOUNT CREATE CONTROLFILE REUSE DATABASE "OLD" NORESETLOGS NOARCHIVELOG MAXLOGFILES 16 MAXLOGMEMBERS 2 MAXDATAFILES 240 MAXINSTANCES 1 MAXLOGHISTORY 113 LOGFILE GROUP 1 ('/u03/oradata/OLD/log1a.dbf', '/u03/oradata/olslsq/log1b.dbf') SIZE 30M, GROUP 2 ('/u04/oradata/OLD/log2a.dbf', '/u04/oradata/OLD/log2b.dbf') SIZE 30M DATAFILE '/u01/oradata/OLD/system01.dbf', '/u01/oradata/OLD/mydatabase.dbf' ; # Recovery is required if any of the datafiles are restored # backups, or if the last shutdown was not normal or immediate. RECOVER DATABASE # Database can now be opened normally. ALTER DATABASE OPEN;

STEP 2: Shutdown the old database STEP 3: Copy all data files into the new directories on the new server. You may change the file names if you want, but you must edit the controlfile to reflect the new data files names on the new server.
rcp rcp rcp rcp /u01/oradata/OLD/* /u01/oradata/OLD/* /u03/oradata/OLD/* /u04/oradata/OLD/* newhost:/u01/oradata/CLONE newhost:/u01/oradata/CLONE newhost:/u03/oradata/CLONE newhost:/u04/oradata/CLONE

STEP 4: Copy and Edit the Control file Using the output syntax from STEP 1, modify the controlfile creation script by changing the following: Old:
CREATE CONTROLFILE REUSE DATABASE "OLD" NORESETLOGS

New:
CREATE CONTROLFILE SET DATABASE "CLONE" RESETLOGS

STEP 5: Remove the recover database and alter database open syntax
# Recovery is required if any of the datafiles are restored # backups, or if the last shutdown was not normal or immediate. RECOVER DATABASE # Database can now be opened normally. ALTER DATABASE OPEN;

STEP 6: Re-names of the data files names that have changed. Save as db_create_controlfile.sql. Old:
DATAFILE '/u01/oradata/OLD/system01.dbf', '/u01/oradata/OLD/mydatabase.dbf'

New:
DATAFILE '/u01/oradata/CLONE/system01.dbf', '/u01/oradata/CLONE/mydatabase.dbf'

STEP 7: Create the bdump, udump and cdump directories


cd $DBA/admin mkdir CLONE cd CLONE mkdir bdump mkdir udump mkdir cdump mkdir pfile

STEP 8: Copy-over the old init.ora file


rcp $DBA/admin/olslsq/pfile/*.ora newhost:/u01/oracle/admin/CLONE/pfile

STEP 9: Start the new database


@db_create_controlfile.sql

STEP 10: Place the new database in archivelog mode

You might also like