Move DB with Oracle 11g Binaries

Problem Statement:

  1. Move DB with Oracle Binaries on New Storage
  2. Create new DEV/UAT from Production.


While creating new UAT or DEV from production and make this version of oracle to the same patch set level as of production, there are more than to move DB with Oracle Binaries.


One way to move DB with Oracle Binaries is to install from the base version and upgrade the DB with the required patch set.

Another way to copy the entire binary from Production to the UAT/DEV and you will get the same patch set level of DB as of production.

The latter approach can be followed on same machine or on a different machine.

The approach:

Here, we are taking the second approach.  This approach requires below steps be performed on source and destination.

Steps on Source:

  • Login in Unix box with oracle user
  • Take the list of all DATAFILES, CONTROL FILES, LOGFILES including path

Perform steps:

    • Login using SQLPLUS with DBA user and execute below query.




  • Backup current init.ora file
  • Create new init.ora file using

Perform steps:

    • Login using SQLPLUS with DBA user
  • Shutdown existing DB using shutdown immediate using SQLPLUS with SYS user
  • Stop Listener using “lsnrctl stop”
  • Confirm there are no executable running for this DB using “ps –fu oracle
  • Get the list of oracle inventory using “$ORACLE_HOME/OPatch/opatch lsinv –all”
Steps on Destination:
  • Create directory /NewMountPoint/app/oracle/product/
  • Copy oracle binaries from source mount point to  destination mount point
  • Copy all data files (including indexes data files) of source DB to Destination DB
  • Copy control files on location:
  • Start-up Source DB
  • Modify init.ora on destination for relevant changes like DB Name and location related parameters.
  • Export ORACLE_SID=destdb
  • Copy oraInventory directory

Perform steps:

    • cp -Rp  /OldMountPoint/app/oraInventory  /NewMountPoint/app/
    • Update path in oraInst.loc file
  • Modify the environment file sourced from .bash_profile to reflect correct path.
  • clone the Oracle Home using:

/NewMountPoint/app/oracle/product/ \

-clone \

-silent \


ORACLE_HOME=/NewMountPoint/app/oracle/product/ \

ORACLE_BASE=/NewMountPoint/app/oracle \


  • Run any scripts which are asked to run as root user by runinstaller
  • Modify /etc/oratab.  tail –f /etc/oratab :

Entries to be replaced:

    • From: dbname:/OldMountPoint/app/oracle/product/11.2.0/dbhome_1:N
    • To : dbname: /NewMountPoint/app/oracle/product/
  • Reset current environment using . oraenv
  • Update listener.ora file
  • Check Oracle inventory to validate the cloning of oracle home

$ORACLE_HOME/OPatch/opatch lsinv -all

  • Copy new created init.ora of existing database
  • Make relevant path change in init.ora (i.e. control file location etc)
Entries to be replaced:
    • From: .control_files=’/OldMountPoint1/oracle/oradata/dbname/control01.ctl’,’/OldMountPoint2/oracle/oradata/dbname/control02.ctl’,’/OldMountPoint/oracle/oradata/dbname/control03.ctl’
    • .control_files=’/NewMountPoint1/oracle/oradata/dbname/control01.ctl’,’/NewMountPoint2/oracle/oradata/dbname/control02.ctl’,’/NewMountPoint3/oracle/oradata/dbname/control03.ctl’
  • Start-up Database to mount
  • Rename all data files and index files with the new location of data/index files copied.

Use this command for all data files:

  • Open DB using alter database.  You may have to perform instance recovery using reset logs.
  • Start the listener service.

Your DB at new location is ready to be used.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.