Cold Cloning Steps (Multi User & Single Node)
Step:-1
Prepare the Source System for database tier and application tier
Execute the following commands to prepare the Source System for cloning:
Note: Ensure all the processes in the Source System are up before proceeding with the following two steps.
Prepare the Source System database tier for cloning
Log on to the Source System as the DB_user.
Source the Database tier environment file.
Execute the following commands:
$ cd <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>
$ perl adpreclone.pl dbTier
Step:-2
Prepare the Source System application tier for cloning
Log on to the primary node of the Source System as the apps_user.
Source the environment file of the Run Edition File system.
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
Execute the following commands:
$ cd <INST_TOP>/admin/scripts
$ perl adpreclone.pl appsTier
Note: If you apply a new Rapid Clone or AutoConfig update to the system, you must execute adpreclone.pl again on the database tier and applications tier to apply the new files into the clone directory structures to be used during the cloning configuration stage. Furthermore, if you patch Oracle Fusion Middleware or make configuration changes to the Oracle E-Business Suite WebLogic Domain, you must execute adpreclone.pl again on the applications tier to rebuild the Oracle Fusion Middleware home.
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 Web Tier 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
Shut down the application processes (Windows platform only)
Log on to Run Edition File System in the Source System as the apps_user, and shut down all the application processes.
Step:-3
Copy both database tier and application tier nodes from the Source System to the Target System
Copy the application tier file system from the Source node to the Target node by executing the following steps in the order listed. Ensure the application tier files copied to the Target System are owned by the Target apps_user, and that the database node files are owned by the Target oracle user.
Note: In the copying tasks below, UNIX users should ensure that the symbolic links (soft links) are preserved when copying. On most UNIX platforms, you can accomplish this with the cp -RH command. Consult the UNIX man page for the cp command to check the parameters available on your platform.
For example:
$ scp -r /source_dest_dir/db 192.168.1.100-(target):/u01/
Alternatively, you can use the tar command to compress the directories into a temporary staging area. UNIX users should ensure that the symbolic links (soft links) are preserved when compressing. On most UNIX platforms, this is the default behavior of the tar command. Consult the UNIX man page for the tar command to check the parameters available on your platform.
In addition, verify the permissions of the executables under ORACLE_HOME/bin that can potentially be owned by root, such as nmo, nmhs, and nmb.
Copy the database node file system
Log on to the Source System database node as the oracle user, and then:
Perform a normal shut down of the Source System database.
Copy the database (.dbf) files from the Source System to the Target System.
Copy the Source System database ORACLE_HOME to the Target System.
Start the Source applications system database and application tier processes.
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 apps_user.
Copy the following application tier directories from the Source Node to the Target Run Edition File System application tier node:
WHAT NEEDS TO BE COPIED
----------------------------
Choose only RUN FILE SYSTEM for copying
<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.
Note: 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 support the Run Edition and Patch Edition File Systems:
Note: <s_base> and <sid> are user-defined values.
<s_base>/<sid>/fs1 (for example, /u02/apps/fs1)
<s_base>/<sid>/fs2 (for example, /u02/apps/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 cut over phase is complete.
Note: As Rapid Clone will 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 will 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 will 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.
The Source Run Edition File System has the following values:
$RUN_BASE=/u02/apps/fs2
$PATCH_BASE=/u02/apps/fs1
The Target <s_base> directory will be /d05/test. Copy the Source Run Edition File System into the Target /d05/test/fs2 directory to initially act as Run Edition File System.
Step:-4
Configure the Target System
Run the following commands to configure the Target System. You will be prompted for specific Target System values such as SID, paths, and ports.
Configure the Target System Database Tier
Log on to the Target System as the oracle user and enter the following commands:
$ cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
$ perl adcfgclone.pl dbTier
Login with DB_User
Step:-5
Step:-1
Prepare the Source System for database tier and application tier
Execute the following commands to prepare the Source System for cloning:
Note: Ensure all the processes in the Source System are up before proceeding with the following two steps.
Prepare the Source System database tier for cloning
Log on to the Source System as the DB_user.
Source the Database tier environment file.
Execute the following commands:
$ cd <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>
$ perl adpreclone.pl dbTier
Step:-2
Prepare the Source System application tier for cloning
Log on to the primary node of the Source System as the apps_user.
Source the environment file of the Run Edition File system.
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
Execute the following commands:
$ cd <INST_TOP>/admin/scripts
$ perl adpreclone.pl appsTier
Note: If you apply a new Rapid Clone or AutoConfig update to the system, you must execute adpreclone.pl again on the database tier and applications tier to apply the new files into the clone directory structures to be used during the cloning configuration stage. Furthermore, if you patch Oracle Fusion Middleware or make configuration changes to the Oracle E-Business Suite WebLogic Domain, you must execute adpreclone.pl again on the applications tier to rebuild the Oracle Fusion Middleware home.
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 Web Tier 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
Shut down the application processes (Windows platform only)
Log on to Run Edition File System in the Source System as the apps_user, and shut down all the application processes.
Step:-3
Copy both database tier and application tier nodes from the Source System to the Target System
Copy the application tier file system from the Source node to the Target node by executing the following steps in the order listed. Ensure the application tier files copied to the Target System are owned by the Target apps_user, and that the database node files are owned by the Target oracle user.
Note: In the copying tasks below, UNIX users should ensure that the symbolic links (soft links) are preserved when copying. On most UNIX platforms, you can accomplish this with the cp -RH command. Consult the UNIX man page for the cp command to check the parameters available on your platform.
For example:
$ scp -r /source_dest_dir/db 192.168.1.100-(target):/u01/
Alternatively, you can use the tar command to compress the directories into a temporary staging area. UNIX users should ensure that the symbolic links (soft links) are preserved when compressing. On most UNIX platforms, this is the default behavior of the tar command. Consult the UNIX man page for the tar command to check the parameters available on your platform.
In addition, verify the permissions of the executables under ORACLE_HOME/bin that can potentially be owned by root, such as nmo, nmhs, and nmb.
Copy the database node file system
Log on to the Source System database node as the oracle user, and then:
Perform a normal shut down of the Source System database.
Copy the database (.dbf) files from the Source System to the Target System.
Copy the Source System database ORACLE_HOME to the Target System.
Start the Source applications system database and application tier processes.
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 apps_user.
Copy the following application tier directories from the Source Node to the Target Run Edition File System application tier node:
WHAT NEEDS TO BE COPIED
----------------------------
Choose only RUN FILE SYSTEM for copying
<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.
Note: 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 support the Run Edition and Patch Edition File Systems:
Note: <s_base> and <sid> are user-defined values.
<s_base>/<sid>/fs1 (for example, /u02/apps/fs1)
<s_base>/<sid>/fs2 (for example, /u02/apps/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 cut over phase is complete.
Note: As Rapid Clone will 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 will 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 will 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.
The Source Run Edition File System has the following values:
$RUN_BASE=/u02/apps/fs2
$PATCH_BASE=/u02/apps/fs1
The Target <s_base> directory will be /d05/test. Copy the Source Run Edition File System into the Target /d05/test/fs2 directory to initially act as Run Edition File System.
Step:-4
Configure the Target System
Run the following commands to configure the Target System. You will be prompted for specific Target System values such as SID, paths, and ports.
Configure the Target System Database Tier
Log on to the Target System as the oracle user and enter the following commands:
$ cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
$ perl adcfgclone.pl dbTier
Login with DB_User
[root@sujeet /]# su ora-db
[ora-db@sujeet /]$ cd /u01/db/11.2.0/appsutil/clone/bin/
[ora-db@sujeet bin]$ perl adcfgclone.pl dbTier
Copyright (c) 2011 Oracle Corporation
Redwood Shores, California, USA
Oracle E-Business Suite Rapid Clone
Version 12.2
adcfgclone Version 120.63.12020000.7.1202010.2
Enter the APPS password : ******
Running:
Target System Hostname (virtual or normal) [sujeet] : sujeet
Target System Database SID : Airtel
Target System Base Directory : /u01/db
Target System utl_file_dir Directory List : /tmp
Number of DATA_TOP's on the Target System [1] :
Target System DATA_TOP Directory 1 [/data01/PRE/db/data] : /u01/db/data
Target System RDBMS ORACLE_HOME Directory [/u01/db/11.2.0] :
Do you want to preserve the Display [test:0.0] (y/n) : n
Target System Display [sujeet:0.0] :
Do you want the target system to have the same port values as the source system (y/n) [y] ? : n
Target System Port Pool [0-99] : 15
APPS Password : Log file located at /u01/db/11.2.0/appsutil/log/Airtel_sujeet/ApplyDBTier_06232239.log
\ 50% completed
Completed Apply...
Tue Jun 23 22:48:04 2015
Starting database listener for Airtel:
Running:
/u01/db/11.2.0/appsutil/scripts/Airtel_sujeet/addlnctl.sh start Airtel
Logfile: /u01/db/11.2.0/appsutil/log/Airtel_sujeet/addlnctl.txt
You are running addlnctl.sh version 120.4
Starting listener process Airtel ...
Listener Airtel has already been started.
addlnctl.sh: exiting with status 0
addlnctl.sh: check the logfile /u01/db/11.2.0/appsutil/log/Airtel_sujeet/addlnctl.txt for more information ...
[ora-db@sujeet bin]$
[ora-db@sujeet 11.2.0]$ . Airtel_sujeet.env
[ora-db@sujeet 11.2.0]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Tue Jun 23 23:06:27 2015
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL>
SQL> select * from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE 11.2.0.3.0 Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
Step:-5
Configure the Target System application tier server nodes
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
[root@sujeet /]# su applchintels <application_User>
[applmgr@sujeet /]$ cd /apps_base/apps/fs1/EBSapps/comn/clone/bin
RUN perl adcfgclone.pl appsTier
Step:-6
[applmgr@sujeet bin]$ perl adcfgclone.pl appsTier
Copyright (c) 2011 Oracle Corporation
Redwood Shores, California, USA
Oracle E-Business Suite Rapid Clone
Version 12.2
adcfgclone Version 120.63.12020000.41
Enter the APPS password : *************
Running:
Enter the Weblogic AdminServer password : *********
Running:
Do you want to add a node (yes/no) [no] : no
Running:
Target System File Edition type [run] : run
Provide the values required for creation of the new APPL_TOP Context file.
Target System Hostname (virtual or normal) [sujeet] : sujeet
Target System Database SID : Airtel
Target System Database Server Node [sujeet] :
Target System Database Domain Name [sujeet.com] :
Target System Base Directory : /u02/apps
Target System Base Directory set to /u02/apps
Target System Current File System Base set to /u02/apps/fs1
Target System Other File System Base set to /u02/apps/fs2
Target System Fusion Middleware Home set to /u02/apps/fs1/FMW_Home
Target System Web Oracle Home set to /u02/apps/fs1/FMW_Home/webtier
Target System Appl TOP set to /u02/apps/fs1/EBSapps/appl
Target System COMMON TOP set to /u02/apps/fs1/EBSapps/comn
Target System Instance Home Directory [u02/apps] :
Target System Instance Top set to /u02/apps/fs1/inst/apps/Airtel_sujeet
Do you want to preserve the Display [test:0.0] (y/n) : n
Target System Display [sujeet:0.0] :
Target System Root Service [enabled] :
Target System Web Administration [enabled] :
Target System Web Entry Point Services [enabled] :
Target System Web Application Services [enabled] :
Target System Batch Processing Services [enabled] :
Target System Other Services [enabled] :
Do you want the target system to have the same port values as the source system (y/n) [y] ? : n
Target System Port Pool [0-99] : 11
Checking the port pool 11
UTL_FILE_DIR on database tier consists of the following directories.
1. /usr/tmp
2. /tmp
3. /u01/db/11.2.0/appsutil/outbound/Airtel_sujeet
4. /usr/tmp
Choose a value which will be set as APPLPTMP value on the target node [1] : 1
100% completed
Completed Apply...
Thu Jun 25 17:56:34 2015
Executing command: /u02/apps/fs1/EBSapps/10.1.2/bin/sqlplus @/u02/apps/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql/truncate_ad_nodes_config_status.sql
Do you want to startup the Application Services for PREPROD? (y/n) [n] : y
Step:-7
RUN adpreclone on TARGET RUN FILESYSTEM
[applmgr@sujeet ~]$ cd /u02/apps/fs1/EBSapps/appl
[applmgr@sujeet appl]$ . Airtel_sujeet.env
[applmgr@sujeet appl]$ cd $ADMIN_SCRIPTS_HOME
[applmgr@sujeet scripts]$ perl adpreclone.pl appsTier
Copyright (c) 2011, 2014 Oracle Corporation
Redwood Shores, California, USA
Oracle E-Business Suite Rapid Clone
Version 12.2
Enter the APPS User Password: *******
Enter the Weblogic AdminServer password : *******
/ 20% completed
Completed Stage...
Step:-8
SHUTDOWN THE APPLICATION which is running on RUN FILESYSTEM
[applmgr@sujeet scripts]$ ./adstpall.sh apps/apps
You are running adstpall.sh version 120.22.12020000.7
Enter the WebLogic Server password: ********
[applmgr@sujeet scripts]$ ps -ef |grep FNDLIBR
503 25991 4863 0 20:52 pts/1 00:00:00 grep FNDLIBR
Step:-9
COPY THE TARGET RUN FILESYSTEM to TARGET PATCH FILESYSTEM
----------------------------------------------------------------
/u02/apps/fs2/<----Here We need to copy EBSapps from /u02/apps/fs1/
[applmgr@sujeet fs2]$ cd /u02/apps/fs1/
[applmgr@sujeet fs1]$ cp -r EBSapps/ /u02/apps/fs2/
Check EBSapps properly copy or not?
Go to FS2 location and check it.
[applmgr@sujeet ~]$ cd /u02/apps/fs2
[applmgr@sujeet fs2]$ ll
total 4
drwxr-xr-x 4 applmgr dba 4096 Jun 25 20:55 EBSapps
[applmgr@sujeet fs2]$ du -sh EBSapps/
30G EBSapps/
Step:-10
UNSET the application Enviroment.Previously we have executed env.
[applmgr@sujeet~]$ vi .bash_profile
Before we run adcfgclone.pl dont run any env's, Directly go to
/u02/apps/fs2/EBSapps/comn/clone/bin/ and execute adcfgclone.pl
Step:-11
Once Finished copying START CONFIGURING TARGET PATCH FILESYSTEM
---------------------------------------------------------------------
[applmgr@sujeet ~]$ cd /u02/apps/fs2/EBSapps/comn/clone/bin
[applmgr@sujeet bin]$ perl adcfgclone.pl appsTier
Copyright (c) 2011 Oracle Corporation
Redwood Shores, California, USA
Oracle E-Business Suite Rapid Clone
Version 12.2
adcfgclone Version 120.63.12020000.41
Enter the APPS password : *******
Running:
Enter the Weblogic AdminServer password : *********
Do you want to add a node (yes/no) [no] : no
Running:
Target System File Edition type [run] : patch
Enter the full path of Run File System Context file : /u02/apps/fs1/inst/apps/Airtel_sujeet/appl/admin/Airtel_sujeet.xml
Provide the values required for creation of the new APPL_TOP Context file.
Target System Fusion Middleware Home set to /u02/apps/fs2/FMW_Home
Target System Web Oracle Home set to /u02/apps/fs2/FMW_Home/webtier
Target System Appl TOP set to /u02/apps/fs2/EBSapps/appl
Target System COMMON TOP set to /u02/apps/fs2/EBSapps/comn
Target System Instance Top set to /u02/apps/fs2/inst/apps/Airtel_sujeet
Target System Port Pool [0-99] : 12
UTL_FILE_DIR on database tier consists of the following directories.
1. /usr/tmp
2. /tmp
3. /u01/db/11.2.0/appsutil/outbound/PREPROD_chintels
4. /usr/tmp
Choose a value which will be set as APPLPTMP value on the target node [1] :
| 100% completed
Completed Apply...
Thu Jun 25 22:04:38 2015
Looking for incomplete CLONE record in ad_adop_session_patches table
The CLONE record status is no rows selected
Step:-12
Once we are done with everything. Start the application Tier using adstral.sh
This time set the env to RUN File System
[applmgr@sujeet ~]$ . .bash_profile
[applmgr@sujeet ~]$ cd $ADMIN_SCRIPTS_HOME
[applmgr@sujeet scripts]$ pwd
/u02/apps/fs1/inst/apps/Airtel_sujeet/admin/scripts
[applmgr@sujeet scripts]$ ./adstrtal.sh apps/apps
Enter the Weblogic AdminServer password : *********
[applmgr@sujeet scripts]$ ps -ef|grep FNDLIBR
503 20958 20953 0 22:23 pts/1 00:00:00 FNDLIBR
503 21212 21118 0 22:24 ? 00:00:00 FNDLIBR
Now Database & Application is UP & Running..
Step:-13
Open Login page.
URL:- 192.168.1.100:8011
*******************************END**********************************************
No comments:
Post a Comment