Scribd
Upload
6 views3 pages

8-User Managed Online Cloning Handout

The document outlines the steps required to clone a database from node8 to node53, emphasizing the need for the database to be in archive log mode. It includes pre-requisites such as applying necessary patches, preparing the target node, and executing specific scripts to facilitate the cloning process. Additionally, it details post-cloning configurations and updates needed for the target node to function correctly.

Uploaded by

saddamshaikhdba0401
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
6 views3 pages

8-User Managed Online Cloning Handout

The document outlines the steps required to clone a database from node8 to node53, emphasizing the need for the database to be in archive log mode. It includes pre-requisites such as applying necessary patches, preparing the target node, and executing specific scripts to facilitate the cloning process. Additionally, it details post-cloning configurations and updates needed for the target node to function correctly.

Uploaded by

saddamshaikhdba0401
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

------------------------------> Online

Cloning(s/s)>----------------------------------
------------------------

source : node8

target : node53

Note: DB must be in archive log mode.


----

- Check the pre-requisites & apply required patches

* Latest AD patch

* Patches for Rapid clone

- Prepare the target node


- Run adpreclone.pl on source

db-tier: $ perl adpreclone.pl dbTier

apps-tier: $ perl adpreclone.pl appsTier

- Enable backup mode for db

sql> alter database begin backup;

- copy all source node files & dirs to target

1. db-tier:
scp -r db node53:/u01

(or)

tar zcvf - db | ssh node53:('cd /u01;tar zxvf -)

2. apps-tier:

scp -r apps inst node53:/u02

(or)
tar zcvf - apps inst | ssh node53:('cd /u02;tar zxvf -)

- End backup & take backup of control file:

sql> alter database end backup;


sql> alter database backup controlfile to trace as '/u01/trace.sql';

- Copy the backup controlfile & archives to target

- Configure the target node:(post step)


-----------------------------------
- Run adcfgclone on db tier
node 53] $ perl adcfgclone.pl dbTechstack (on db-tier)

Logfile: $ORACLE_HOME/appsutil/clone/bin/cloneContext_<timestamp>.log

$ORACLE_HOME/appsutil/log/<context_name>/ApplyDBTier_<timestamp>.log

- Create control file:


/u01

$ vi trace.sql
dgg. . create controlfile SET database "CLONE" RESETLOGS
d(shift)gg. create set utf8
/u01/prod/apps_st/data

- remove old controlfile:


$ cd /db/apps_st/data
$ rm -rvf cntr*

- create init file:

$ export ORACLE_SID=clone
sql> startup nomount;
sql> @trace.sql;
sql> recover database using backup controlfile until cancel;
sql> alter database open resetlogs:

- chk listener status:


- update library file:

$ cd /db/tech_st/10.2.0/appsutil/install/SID_node/adupdlib.sql (chk
the permission)
sql>@?/appsutil/install/SID_node/adupdlib.sql

- Add tempfile to TEMPORARY Table Space:

sql>select tablespace_name,file_name from dba_temp_files;


sql> select * from database_property where
property_name='default_temp_tablespace';
sql> select tablespace_name from dba_tablespaces;

sql> alter tablespace temp1 add tempfile


'/u01/db/apps_st/data/temp01.dbf' size 50m;
sql>alter database default temporary tablespace temp1;

- Run adcfgclone on db tier:

$ perl adcfgclone.pl dbconfig

- Run adcfgclone on APPS tier

$ perl adcfgclone.pl appsTier

- profile option name change:

system administrator/profile/system

site name devclone of prod


se

You might also like