Cloning Oracle Applications Release 12 with Rapid Clone
Section 1: Prerequisites (First time only)
1. Run AutoConfig on the Application Tiers
Run AutoConfig on all application tier nodes. Use the adautocfg.sh command. All scripts listed below are located in <INST_TOP>/admin/scripts.
Platform
|
Functionality
|
Command
|
UNIX
|
Start Applications services
|
adstrtal.sh
|
Stop Applications services
|
adstpall.sh
|
|
Run AutoConfig
|
adautocfg.sh
|
Attention: The database server and the database listener must remain available during the AutoConfig run. Only the application tier servers should be shut down.
Note: Running AutoConfig may change your existing environment files. After running AutoConfig, you should always set the environment before you run any Applications utilities, in order to apply the changed environment variables.
2. Synchronize appsutil on the Database Tier Nodes
Update the RDBMS ORACLE_HOME file system with the AutoConfig files by performing the following steps:
· On the application tier (as the APPLMGR user):
o Log in to the APPL_TOP environment (source the environment file)
o Create appsutil.zip file
perl <AD_TOP>/bin/admkappsutil.pl
o This will create appsutil.zip in <INST_TOP>/admin/out
· On the database tier (as the ORACLE user):
o Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>
o cd <RDBMS ORACLE_HOME>
o unzip -o appsutil.zip
3. Run AutoConfig on the Database Tier
Run AutoConfig on the database tier nodes. Use the adautocfg.sh/.cmd command. All the scripts listed below are located in
<RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>.
Platform
|
Functionality
|
Command
|
UNIX
|
Start database listener process
|
addlnctl.sh start <SID> |
Start database process
|
addbctl.sh start |
|
Stop database listener process
|
addlnctl.sh stop <SID> |
|
Stop database process
|
addbctl.sh stop |
|
Run AutoConfig
|
adautocfg.sh |
Attention: The database server and the database listener must remain available during the AutoConfig run. All the other database tier services should be shut down.
Note: Running AutoConfig may change your existing environment files. After running AutoConfig, you should always set the environment before you run any Applications utilities, in order to apply the changed environment variables.
4. Maintain Snapshot information
Log in to each Applications Node as the APPLMGR user, and run "Maintain Snapshot information" in AD Administration (adadmin).
Run adadmin à Select option 2 à Select option 5 à Select option 2 à Select option 1
Section 2: Clone Oracle Applications Release 12
1. Prepare the Source System
Execute the following commands to prepare the source system for cloning.
Execute the following commands to prepare the source system for cloning.
a. Prepare the source system database node for cloning
Log on to the source system as the ORACLE user. and run the following commands:
Log on to the source system as the ORACLE user. and run the following commands:
cd <RDBMS
ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>perl adpreclone.pl dbTier
NOTE:
First set the environment variable
. /oracle/db/tech_st/10.2.0/PROD_devdb.env
Then
cd $ORACLE_HOME/appsutil/scripts/PROD_devapps/
perl adpreclone.pl dbTier
b. Prepare the source system application tier for cloning
Log on to the source system as the APPLMGR user, and run the following commands on each node that contains an APPL_TOP:
Log on to the source system as the APPLMGR user, and run the following commands on each node that contains an APPL_TOP:
cd
<INST_TOP>/admin/scriptsperl adpreclone.pl appsTier
NOTE:
First set the environment variable
. /oracle/apps/apps_st/appl/PROD_devapps.env
Then
cd $
INST_TOP/admin/scriptsperl
adpreclone.pl appsTier
2. Copy the Source System to the Target System
Copy the application tier file system from the source Applications system 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 APPLMGR user, and that the database node files are owned by the target ORACLE user.
Copy the application tier file system from the source Applications system 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 APPLMGR user, and that the database node files are owned by the target ORACLE user.
a. Copy the application tier file system
Log on to the source system application tier nodes as the APPLMGR user.
Log on to the source system application tier nodes as the APPLMGR user.
§ Shut down the application tier server processes
§ Copy the following application tier directories from the source node to the target application tier node:
§
<APPL_TOP>
§
<COMMON_TOP>
§ Tech Stack
Note: Restore the backup of source Apps on target Apps.
b. Copy the database node file system
Log on to the source system database node as the ORACLE user, and then:
Log on to the source system database node as the ORACLE user, and then:
§ Perform a normal shutdown of the source system database
§ Copy the database (DBF) files from the source to the target system
§ Copy the source database ORACLE_HOME to the target system
§ Start the source Applications system database and application tier processes
Note: Copy and Restore the backup of source DB on target DB.
From source system e.g., PRODDB:
scp 01_BACKUP_PRODDB.tar.gz oracle@172.16.35.9:/oracle/01_BACKUP_PRODDB.tar.gz
From target system e.g., DEVDB
tar -xzf /oracle/01_BACKUP_PRODAPPS.tar.gz
Same for APPS node.
- Configure the Target System
Execute the following commands to configure the target system. You will be prompted for the target system specific values (SID, paths, ports, etc.)
NOTE:
[oracle@testdb ~]$ cd $ORACLE_HOME
[oracle@testdb ~]$ cd appsutil/clone/bin
[oracle@testdb ~]$ perl adcfgclone.pl dbTier
Enter the APPS user password: apps
Enter the APPS password: apps
Provide the values required for creation of the new Database Context file.
Target hostname (virtual or normal) [testdb]: --enter target db hostname)
Target instance is a Real Application Cluster (RAC) instance (y/n) [n]: --if no RAC then press enter
Target System database name: PROD --enter your SID name
Target system base directory for source homes:/oracle --enter base directory of your apps installation
Target system utl_file accessible directories list: /usr/tmp -- enter utl_file directories seperated by space
Number of DATA_TOP's on the target system [4]: -- accepted the default value (db_sys_files, db_log_files, db_dat_files, db_ndx_files)
Target system DATA_TOP 1:/oracle/db/apps_st/data --enter path of DATA_TOP
Target system DATA_TOP 2:/oracle/db/apps_st/data --enter path of DATA_TOP
Target system DATA_TOP 3:/oracle/db/apps_st/data --enter path of DATA_TOP
Target system DATA_TOP 4:/oracle/db/apps_st/data --enter path of DATA_TOP
Target system RDBMS ORACLE_HOME directory:/oracle/db/tech_st/10.2.0 -- enter ORACLE_HOME path
Do you want to preserve the Display set to null (y/n) [y] ?: --press enter
Do you want the the target system to have the same port values as the source system (y/n) [y] ?: --press enter
[oracle@testapps ~]$ cd $COMMON_TOP
[oracle@testapps comn]$ cd clone/bin/
[oracle@testapps bin]$ perl adcfgclone.pl appsTier
Enter the APPS user password: apps
Enter the APPS password: apps
Provide the values required for creation of the new APPL_TOP Context file.
Target hostname (virtual or normal) [testapps]: --enter target apps hostname
Target system database SID: PROD --enter SID
Target system database server node [testapps]:testdb --enter target db hostname
Target system base directory for source homes:/oracle --enter base directory of your db installation
Target system base directory for instance homes [/oracle/inst]: --press enter
Do you want to preserve the Display set to testapps:0.0 (y/n) [y] ?: --press enter
Do you want the the target system to have the same port values as the source system (y/n) [y] ?: --press enter
UTL_FILE_DIR on database tier consists of the following directories.
1. /usr/tmp
2. /oracle/db/tech_st/10.2.0/appsutil/jre
3. /oracle/db/tech_st/10.2.0/appsutil/jre/bin/java
4. /oracle/db/tech_st/10.2.0/appsutil/outbound/PROD_proddb
5. /usr/tmp
Choose a value which will be set as APPLPTMP value on the target node [1]: --press enter (/usr/tmp)
Section 3: Finishing Tasks (If Required)
This section lists tasks that may be necessary, depending on your implementation and the intended use of the cloned system.
1. Update profile options
Rapid Clone updates only site level profile options. If any other profile options are set to instance specific values, you must update them manually.
Rapid Clone updates only site level profile options. If any other profile options are set to instance specific values, you must update them manually.
2. Update printer settings
If the new cloned system needs to utilize different printers, update the target system with the new printer settings now.
If the new cloned system needs to utilize different printers, update the target system with the new printer settings now.
3. Update Workflow configuration settings
Cloning an Oracle Applications instance will not update the host and instance specific information used by Oracle Workflow. Review the following tables and columns to verify there is no instance specific data in the Workflow configuration on the target system.
Cloning an Oracle Applications instance will not update the host and instance specific information used by Oracle Workflow. Review the following tables and columns to verify there is no instance specific data in the Workflow configuration on the target system.
Table Name
|
Column Name
|
Column Value Details
|
WF_NOTIFICATION_ATTRIBUTES
|
TEXT_VALUE
|
Value starts with http://<old web host> : Update to new web host
|
WF_ITEM_ATTRIBUTE_VALUES
|
TEXT_VALUE
|
Value starts with "http://<old web host> : Update to new web host
|
WF_SYSTEMS
|
GUID
|
Create a new system defined as the new global database name using the Workflow Administrator Web Applications responsibility.
|
WF_SYSTEMS
|
NAME
|
Value needs to be replaced with the database global name
|
WF_AGENTS
|
ADDRESS
|
Update database link with the new database global name.
|
FND_FORM_FUNCTIONS
|
WEB_HOST_NAME
|
Update with the new web host name
|
FND_FORM_FUNCTIONS
|
WEB_AGENT_NAME
|
Update to point at the new PLSQL listener name
|
FND_CONCURRENT_REQUESTS
|
LOGFILE_NAME
|
Update with the correct path to the logfile directory
|
FND_CONCURRENT_REQUESTS
|
OUTFILE_NAME
|
Update with the new directory path on the target system
|
4. Verify the APPLCSF variable setting
Source the APPS environment and review that the variable APPLCSF (identifying the top-level directory for concurrent manager log and output files) points to a suitable directory. To modify it, change the value of the
Source the APPS environment and review that the variable APPLCSF (identifying the top-level directory for concurrent manager log and output files) points to a suitable directory. To modify it, change the value of the
s_applcsf variable in the context file and then run AutoConfig.
5. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS
If the target system is in a different domain name than the source system and SESSION_COOKIE_DOMAIN was not null in the source system, update that value to reflect the new domain name.
If the target system is in a different domain name than the source system and SESSION_COOKIE_DOMAIN was not null in the source system, update that value to reflect the new domain name.
Reference: Metalink Note 406982.1 and 387859.1
Please Subscribe my blog Qamar Zahoor, YouTube Channel YouTube, Join the Facebook group
Please Subscribe my blog Qamar Zahoor, YouTube Channel YouTube, Join the Facebook group
Facebook Group and do follow on Twitter Twitter to get knowledge of Oracle EBS, Database, Ecommerce, Amazon, Ebay and Digital Marketing. Keep learning.
Good Information Qamar, Thank you.
ReplyDeleteMy client wants us to implement SSOgen SPGateway with Azure ADFS for EBS 12.2:
1.Oracle EBS SSO Integrations
2.SSOgen SPGateway for Oracle EBS
Any recommendations please?