For Full Step-By-Step Cloning of R12.2. Here is the link
Note: This is just an Overview of R12.2 Cloning
In R12.2 Oracle RapidClone uses native Fusion Middleware tools to clone Weblogic Server and Oracle HTTP Server homes.
No Longer we need to copy the FMW Home Files, FMW is automatically packaged into clone directoy during adpreclone execution.
In R12.2 Database Cloning remains the same.
when we run adpreclone.pl appsTier on the application Tier it creates Stage under $COMM_TOP/clone has WLS will be automatically packaged in this directory
Prepare the Source System Application Tier for cloning Log on to the “Run Edition File System” in the Source System as the APPLMGR
user, and run the following commands on each Node that contains an APPL_TOP:
$ cd <INST_TOP>/admin/scripts
$ perl adpreclone.pl appsTier
You can use the following command to confirm that the environment variable FILE_EDITION points to the Run Edition File System:
$ echo $FILE_EDITION
It should return the value:
run
user, and run the following commands on each Node that contains an APPL_TOP:
$ cd <INST_TOP>/admin/scripts
$ perl adpreclone.pl appsTier
You can use the following command to confirm that the environment variable FILE_EDITION points to the Run Edition File System:
$ echo $FILE_EDITION
It should return the value:
run
As of Release 12.2, the adpreclone.pl process on the Application Tier creates a complete compressed archive of the Oracle Fusion Middleware and its components as follows:
• A compressed archive of the Oracle WebLogic Server home, Oracle WebTier Utilities home, Oracle Common Utilities home and the Oracle
E-Business Suite home:
<COMMON_TOP>/clone/FMW/FMW_Home.jar
• A compressed archive of the Oracle E-Business Suite Weblogic domain:
<COMMON_TOP>/clone/FMW/WLS/EBSdomain.jar
• The Oracle E-Business Suite Weblogic domain’s configuration template:
<COMMON_TOP>/clone/FMW/WLS/plan/moveplan.xml
• A compressed archive of the Oracle Web Tier/Oracle HTTP Server configuration instance:<COMMON_TOP>/clone/FMW/OHS/ohsarchive.jar
• A compressed archive of the Oracle WebLogic Server home, Oracle WebTier Utilities home, Oracle Common Utilities home and the Oracle
E-Business Suite home:
<COMMON_TOP>/clone/FMW/FMW_Home.jar
• A compressed archive of the Oracle E-Business Suite Weblogic domain:
<COMMON_TOP>/clone/FMW/WLS/EBSdomain.jar
• The Oracle E-Business Suite Weblogic domain’s configuration template:
<COMMON_TOP>/clone/FMW/WLS/plan/moveplan.xml
• A compressed archive of the Oracle Web Tier/Oracle HTTP Server configuration instance:<COMMON_TOP>/clone/FMW/OHS/ohsarchive.jar
• The Oracle HTTP Server configuration instance’s configuration template:
<COMMON_TOP>/clone/FMW/OHS/moveplan.xml
<COMMON_TOP>/clone/FMW/OHS/moveplan.xml
Copy the Application Tier file system from the Source “Run Edition File System” to the Target “Run Edition File System”
Log on to “Run Edition File System” in the Source System Application Tier nodes as the APPLMGR user.
Copy the following Application Tier directories from the Source Node to the Target “Run Edition File System” Application Tier Node:
• <APPL_TOP>
• <COMMON_TOP>
• <OracleAS Tools 10.1.2 ORACLE_HOME>
The same Operating System user must own both the Run Edition and Patch Edition File Systems.
Warning: In Release 12.2, you can set the base directory to any desired location. However, the subdirectory structure cannot be changed because of dependencies on both the WLS domain and the dual file system required for online patching. Also, the base directory must be the same across all nodes in multi-node configurations.
Log on to “Run Edition File System” in the Source System Application Tier nodes as the APPLMGR user.
Copy the following Application Tier directories from the Source Node to the Target “Run Edition File System” Application Tier Node:
• <APPL_TOP>
• <COMMON_TOP>
• <OracleAS Tools 10.1.2 ORACLE_HOME>
The same Operating System user must own both the Run Edition and Patch Edition File Systems.
Warning: In Release 12.2, you can set the base directory to any desired location. However, the subdirectory structure cannot be changed because of dependencies on both the WLS domain and the dual file system required for online patching. Also, the base directory must be the same across all nodes in multi-node configurations.
Dual File System Directory Structure In Release 12.2, the following directory structure exists to allocate the Run Edition and Patch Edition File Systems:
Note: Please note that <s_base> and <sid> are user-defined values.
• <s_base>/<sid>/fs1 (for example, /u01/122/prod/fs1)
• <s_base>/<sid>/fs2 (for example, /u01/122/prod/fs2)
Two environment variables, $RUN_BASE and $PATCH_BASE, store these locations. The function (RUN or PATCH) of these two file systems is not static, and their values switch every time when a cutover phase is complete. As Clone would create a replica of the Source Node, if the Source “Run Edition File System” is the first file system (fs1), the Target “Run Edition File System” would also be the first file system (fs1). Similarly, if the Source “Run Edition File System” is the second file system (fs2), then the Target “Run Edition File System” would also be the second file system (fs2). Therefore, when you perform a cloning task, you always clone and copy the Source “Run Edition File System” to create the Target “Run Edition File System”, but the directory location of the “Run Edition File System” can be pointing either to <s_base>/<sid>/fs1 or <s_base>/<sid>/fs2 based on the Source “Run Edition File System” base directory.
Note: Please note that <s_base> and <sid> are user-defined values.
• <s_base>/<sid>/fs1 (for example, /u01/122/prod/fs1)
• <s_base>/<sid>/fs2 (for example, /u01/122/prod/fs2)
Two environment variables, $RUN_BASE and $PATCH_BASE, store these locations. The function (RUN or PATCH) of these two file systems is not static, and their values switch every time when a cutover phase is complete. As Clone would create a replica of the Source Node, if the Source “Run Edition File System” is the first file system (fs1), the Target “Run Edition File System” would also be the first file system (fs1). Similarly, if the Source “Run Edition File System” is the second file system (fs2), then the Target “Run Edition File System” would also be the second file system (fs2). Therefore, when you perform a cloning task, you always clone and copy the Source “Run Edition File System” to create the Target “Run Edition File System”, but the directory location of the “Run Edition File System” can be pointing either to <s_base>/<sid>/fs1 or <s_base>/<sid>/fs2 based on the Source “Run Edition File System” base directory.
When copying the files, use the values of $RUN_BASE and $PATCH_BASE variables to determine if the “Run Edition File System” should be copied to fs1 or fs2. For example,
• The Source “Run Edition File System” has the following values:
• $RUN_BASE=/u01/122/prod/fs2
• $PATCH_BASE =/u01/122/prod/fs1
• The Target <s_base> directory will be /d05/test. In this situation, copy the Source “Run Edition File System” into the Target
/d05/test/fs2 directory to initially act as “Run Edition File System” and into the Target /d05/test/fs1 to act as “Patch Edition File System”.
• The Source “Run Edition File System” has the following values:
• $RUN_BASE=/u01/122/prod/fs2
• $PATCH_BASE =/u01/122/prod/fs1
• The Target <s_base> directory will be /d05/test. In this situation, copy the Source “Run Edition File System” into the Target
/d05/test/fs2 directory to initially act as “Run Edition File System” and into the Target /d05/test/fs1 to act as “Patch Edition File System”.
Configure the Target System Application Tier server nodes
1. Log on to the “Run Edition File System” in the Target System as the APPLMGR user and enter the following commands:
$ cd <COMMON_TOP>/clone/bin
$ perl adcfgclone.pl appsTier
At the prompt, “Target System Base Directory”, enter the location of the base directory. For example: /u02/r122.
2. Run adpreclone.pl on the “Run Edition File System” in the Target System.
1. Log on to the “Run Edition File System” in the Target System as the APPLMGR user and enter the following commands:
$ cd <COMMON_TOP>/clone/bin
$ perl adcfgclone.pl appsTier
At the prompt, “Target System Base Directory”, enter the location of the base directory. For example: /u02/r122.
2. Run adpreclone.pl on the “Run Edition File System” in the Target System.
Copy Oracle E-Business Suite application directories from the “Run Edition File System” to the “Patch Edition File System” in the Target System.
Note: Make sure you pay attention to symbolic links under <OracleAS Tools 10.1.2 ORACLE_HOME> and <COMMON_TOP> directories when copying files.
4. Log on to the “Patch Edition File System” in the Target System as the APPLMGR user and enter the following commands:
$ cd <COMMON_TOP>/clone/bin
$ perl adcfgclone.pl appsTier
The “Patch Edition File System” must be aware of the location of the “Run Edition File System” that will be configured in the next step. At the prompt, “Location of Run System Context File”, enter the absolute path to the Context File for the “Run Edition File System” that was created in the previous step. For example:
/u02/r122/fs1/inst/apps/PROD_atgserver/appl/admin/PROD_atgserver.xml.
Note: Make sure you pay attention to symbolic links under <OracleAS Tools 10.1.2 ORACLE_HOME> and <COMMON_TOP> directories when copying files.
4. Log on to the “Patch Edition File System” in the Target System as the APPLMGR user and enter the following commands:
$ cd <COMMON_TOP>/clone/bin
$ perl adcfgclone.pl appsTier
The “Patch Edition File System” must be aware of the location of the “Run Edition File System” that will be configured in the next step. At the prompt, “Location of Run System Context File”, enter the absolute path to the Context File for the “Run Edition File System” that was created in the previous step. For example:
/u02/r122/fs1/inst/apps/PROD_atgserver/appl/admin/PROD_atgserver.xml.
What Happens when we run adcfgclone.pl appsTier in R12.2
On the Target Node(RUN Edition FS)
RUN adcfgclone.pl appsTier on RUN EDITION of FS(as we have two file system in R12.2) Once it starts running
It creates context file based on the inputs that we provide,
It Unpackage OHS and WLS then
register/relinks OHs
Configure OH
Configure APPL_TOP
Creates INST_TOP
Starts The Processes.
On the Target Node (The Patch Edition FS)
RUN adcfgclone.pl appsTier on PATCH EDITION of FS
It creates context file based on the inputs that we provide,
It Unpackage OHS and WLS then
Register/relinks OHs
Configure OH
Configure APPL_TOP
Creates INST_TOP
No comments:
Post a Comment