Skip to main content

How to clone oracle apps using simple step by step

Cloning Oracle apps R12

I am Sunny Thakur working as Oracle apps DBA from last 3 years. I worked on many oracle product like  weblogic , OBIEE, Oracle apps and oracle database, ORACLE RMA etc. but I like Oracle apps most. I love to work on oracle apps.

You can also see my previous blog about patching oracle apps here .

The truth about oracle apps is it was a hot technology, it is hot and will remain hot. So for fresher's I will highly recommend oracle apps to take as primary skill :). 

So today I am sharing my knowledge with you guys about how to clone a oracle apps .
Cloning is not very easy to perform. You have to have full knowledge of oracle apps and database also. I will also discuss with you about the common errors that we face while cloning.

Please follow the following steps carefully to clone your system .

STEP  1 :-- Stay calm !!!

Yes, while cloning don't panic at all. I know when you clone your application for first time there is some fear in mind So Please be relax and stay calm.

Now Come to business, Cloning is very simple task . So first question is in mind is :-

Why we need to clone or when to clone oracle apps.
Answer is very simple, We do cloning to replicate our existing system to the UAT or DEV for our developers for testing purpose or if you migrating to new H/W.

STEP 2:-- Prepare your self :)

Yes, Before perform the cloning prepare your self, Do study and if you find this blog I don't think you have to go anywhere :).


NOTE:-- We have oracle apps R12. on Linux and having enough space to take backup. So please first of all make sure you have enough space in your source system(which server you want to clone) . Main objective is to save the time. I am assuming that we have system where we create the UAT for first time.

Preparations :--

If you search for cloning you will find following steps:-

1. PREREQUISITE TASKS
2. PREPARE SOURCE SYSTEM
3. COPY SOURCE TO TARGET
4. CONFIGURE TARGET
5. FINISHING TASKS

PREREQUISITE TASKS :--

Run Autoconfig on both APPLICATION & DB

It is main and very important part of cloning. I am assuming that we have enough space in our source system. First we have to run Auto-config on both application and database servers. For running autoconfig on apps tier we have to shutdown the application, only application not database.
Steps to run Autoconfig on apps tier are as follow:--
1.   Run the environment of oracle apps.
2. Go to $ADMIN_SCRIPTS_HOME then run adstpall.sh to stop the application.
3. In the same directory you will find the script adautocfg.sh .Run this script, it will prompt fro the password. And will take some time to complete.  
4. After successfully completion of the adautocfg.sh on application tier, We have to run the same on the database tier.
5.   Go to the database tier and run .env file from $ORACLE_HOME.
6.  Go to  $ORACLE_HOME/appsutil/scripts/$CONTEXT_NAME and run adautocgf.sh .
7. Now we have successfully run the autoconfig on both tiers.

You can restore your applied autoconfig .
1. Go to $APPL_TOP>/admin//out/MMDDhhmm
2. Run  restore.sh

Run Preclone  on both APPLICATION & DB

On the DB server:

1. go to  cd $ORACLE_HOME/appsutil/scripts/
2 . run perl adpreclone.pl dbTier

On the APPS server:

 1. cd $ADMIN_SCRIPTS_HOME
 2 perl adpreclone.pl appsTier

NOTE:- NOW SHUTDOWN THE DATABASE AND TAKE BACKUP OF BOTH DB & APPS

COPY SOURCE TO TARGET

Copy all the directory to new target system e.g. we have /u01 for database tier and /u02 for apps tier.
then you can use "tar " command to create a zip and send this to target system.
After sending the all the drives to target system and unzip by creating the same directory structure.  

CONFIGURE TARGET 


We first clone the database but first check the permission on the directories . We have to give full permission to user.

On the target Database system

1. Go to $ORACLE_HOME/appsutil/clone/bin
2. Run perl adcfgclone.pl dbTier 
  
Give the inputs that are required. You can change the name, port number, and location of your db tier.

After successful clone of db please check the lsnrctl that everything is running fine.

On the target apps system

1. Go to $COMMON_TOP/clone/bin
2. Run perl adcfgclone.pl appsTier
It will ask you for many inputs. you can change the port also from here.


After completing the cloning process. just check your concurrent manger. and If needed then run cmclean.sql to clean your node.   


FINISHING TASKS

Happy cloning :)


Please update with doubts. I will update this blog. Thanks for your time.












Comments

Post a Comment

Popular posts from this blog

DBA_SCHEDULER_JOB_RUN_DETAILS and PURGE_LOG

How to purge DBA_SCHEDULER_JOB_RUN_DETAILS? Manually deleting from DBA_SCHEDULER_JOB_RUN_DETAILS is not recommended by oracle.DBA_SCHEDULER_JOB_RUN_DETAILS is a view that is using two master tables (scheduler$_job_run_details and scheduler$_event_log) and display the information about jobs history. As there is one procedure named PURGE_LOG and Oracle have Scheduler for this procedure. It will purges all rows in the job log that are older than 30 days.This is the default behavior of this procedure. You can change this to any number of days you want by setting the attribute "SET_SCHEDULER_ATTRIBUTE". e.g. exec DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('log_history','15'); It will purge all logs older than 15days and it will maintain the history of 15days. But If you want manually purge these logs, you can use below solution:- exec DBMS_SCHEDULER.PURGE_LOG(log_history => 15, which_log => 'JOB_LOG'); It will purge all entries from the jog log that are o...
Post a Comment
Read more

ORA-02051 Another Session Or Branch In Same Transaction Failed

ORA-02051 Another Session Or Branch In Same Transaction Failed (Doc ID 2253226.1)          SYMPTOMS for ORA-02051 Another Session Or Branch In Same Transaction Failed. Database performance is slow and caused   the transactions ORA-02051 another session or branch in same transaction failed or finalized CAUSE for ORA-02051 Another Session Or Branch In Same Transaction Failed. Session transactions branches caused the issue Excessive Waits On The Event "Global transaction acquire instance locks" SOLUTION Please use below sql and identified underscore parameter values for ORA-02051 Another Session Or Branch In Same Transaction Failed : SQL> select a.ksppinm "Parameter", b.ksppstvl "Session Value",c.ksppstvl "Instance Value"  FROM x$ksppi a,x$ksppcv b, x$ksppsv c  WHERE a.indx = b.indx AND a.indx = c.indx AND a.ksppinm LIKE '/_%' escape '/'  AND (a.ksppinm like '%clusterwide_global%' or a.ksppinm like '%disable_autotune_...
Post a Comment
Read more

ORA-65016: FILE_NAME_CONVERT must be specified

ORA-65016: FILE_NAME_CONVERT must be specified I just started working on 12C version of oracle database.It's new to me and facing many problems. Error code: ORA-65016: FILE_NAME_CONVERT must be specified Description:"ORA-65016: FILE_NAME_CONVERT must be specified" normally occurs when you create a PDB.I will explain later what is a PDB. Cause and solution :  ORA-65016: FILE_NAME_CONVERT must be specified caused when Data files, and possibly other files, needed to be copied as a part of creating a pluggable database.Enable OMF or define PDB_FILE_NAME_CONVERT system parameter before issuing CREATE PLUGGABLE DATABASE statement, or specify FILE_NAME_CONVERT clause as a part of the statement and make sure the path you are giving to convert the file exists. I think if you are creating the PDB's using GUI then you will not face this error "ORA-65016: FILE_NAME_CONVERT must be specified". If you creating ODB using script and you have gave a wrong path then may you f...
2 comments
Read more