MOS Note: Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)
Pre-requisite Tasks
Run AutoConfig on the application tier
sh $ADMIN_SCRIPTS_HOME/adautocfg.sh
Run AutoConfig on the database tier
cd $ORACLE_HOME/appsutil/scripts
sh adautocfg.sh
Prepare the Source System database tier for cloning
1. Log on to the Source System as the oracle user.
2. Source the Database tier environment file.
3. Execute the following commands:
$ cd/appsutil/scripts/
$ perl adpreclone.pl dbTier
Prepare the Source System application tier for cloning
1. Log on to the primary node of the Source System as the applmgr user.
2. 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
3. Execute the following commands:
$ cd/admin/scripts
$ perl adpreclone.pl appsTier
Database Tier Clone
Copy the database node file system
1. Copy the database (.dbf) files from the Source System to the Target System.
2. Copy the redo log files from the Source System to the Target System
3. Copy the Source System database ORACLE_HOME to the Target System
Configure the Target System database server
Log on to the Target System as the oracle user and enter the following commands:
$ cd/appsutil/clone/bin
$ perl adcfgclone.pl dbTier
Application Tier Clone
Copy the application tier file system from the Source 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:
cd $COMMON_TOP/clone/bin or if it doesn’t exit go to the FS1.
mv FMW_Home FMW_Home_bak on both FS.
Verify /etc/oraInst.loc points to correct folder
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/clone/bin
$ perl adcfgclone.pl appsTier dualfs
Select No for starting up the services.
Finishing Tasks
update the profile values. replace source information with target details.
Change apps/sysadmin password
FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS newpsswd
FNDCPASS apps/apps 0 Y system/manager USER SYSADMIN newpsswd
Note: if you change apps password, then perform the below:
Start AdminServer using the $INST_TOP/admin/scripts/adadminsrvctl.sh script. Do not start any other application tier services.
Change the “apps” password in WLS Datasource as follows:
Log in to WLS Administration Console.
Click Lock & Edit in Change Center.
In the Domain Structure tree, expand Services, then select Data Sources
On the “Summary of JDBC Data Sources” page, select EBSDataSource
On the “Settings for EBSDataSource” page, select the Connection Pool tab
Enter the new password in the “Password” field.
Enter the new password in the “Confirm Password” field.
Click Save.
Click Activate Changes in Change Center.
Check whether you are able to connect to db using apps
sqlplus apps/ from application tier.
Before Starting all the services. Run Autoconfig.
cd $ADMIN_SCRIPTS_HOME
sh adautocfg.sh
Now start the services
Perform Sanity check
Pre-requisite Tasks
Run AutoConfig on the application tier
sh $ADMIN_SCRIPTS_HOME/adautocfg.sh
Run AutoConfig on the database tier
cd $ORACLE_HOME/appsutil/scripts
sh adautocfg.sh
Prepare the Source System database tier for cloning
1. Log on to the Source System as the oracle user.
2. Source the Database tier environment file.
3. Execute the following commands:
$ cd
$ perl adpreclone.pl dbTier
Prepare the Source System application tier for cloning
1. Log on to the primary node of the Source System as the applmgr user.
2. 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
3. Execute the following commands:
$ cd
$ perl adpreclone.pl appsTier
Database Tier Clone
Copy the database node file system
1. Copy the database (.dbf) files from the Source System to the Target System.
2. Copy the redo log files from the Source System to the Target System
3. Copy the Source System database ORACLE_HOME to the Target System
Configure the Target System database server
Log on to the Target System as the oracle user and enter the following commands:
$ cd
$ perl adcfgclone.pl dbTier
Application Tier Clone
Copy the application tier file system from the Source 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:
cd $COMMON_TOP/clone/bin or if it doesn’t exit go to the FS1.
mv FMW_Home FMW_Home_bak on both FS.
Verify /etc/oraInst.loc points to correct folder
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
$ perl adcfgclone.pl appsTier dualfs
Select No for starting up the services.
Finishing Tasks
update the profile values. replace source information with target details.
Change apps/sysadmin password
FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS newpsswd
FNDCPASS apps/apps 0 Y system/manager USER SYSADMIN newpsswd
Note: if you change apps password, then perform the below:
Start AdminServer using the $INST_TOP/admin/scripts/adadminsrvctl.sh script. Do not start any other application tier services.
Change the “apps” password in WLS Datasource as follows:
Log in to WLS Administration Console.
Click Lock & Edit in Change Center.
In the Domain Structure tree, expand Services, then select Data Sources
On the “Summary of JDBC Data Sources” page, select EBSDataSource
On the “Settings for EBSDataSource” page, select the Connection Pool tab
Enter the new password in the “Password” field.
Enter the new password in the “Confirm Password” field.
Click Save.
Click Activate Changes in Change Center.
Check whether you are able to connect to db using apps
sqlplus apps/
Before Starting all the services. Run Autoconfig.
cd $ADMIN_SCRIPTS_HOME
sh adautocfg.sh
Now start the services
Perform Sanity check
No comments:
Post a Comment