Saturday, June 6, 2009

Cloning R12 with Rapid Clone

Section 1: Prerequisites

Before cloning, prepare the source system by applying any required patches and running AutoConfig.

1. Verify OS requirements on Target System
Document 405565.1.

2. Verify source and target nodes software versions

3. Apply the latest AD patch
Refer to OracleMetaLink to obtain the latest AD patch available.

4. Apply the latest AutoConfig Template patch
Refer to Document 387859.1 in OracleMetaLink for details of the latest AutoConfig Template rollup patch.

5. Apply the latest Rapid Clone patches
Update the Oracle Applications file system with the latest Rapid Clone files by applying patches to all Applications nodes:

Warning: If new Rapid Clone or AutoConfig updates are applied to the system, steps 6, 7 and 8 below must be executed again in order to apply the new files into the Database Node.

6. Run AutoConfig on the Application Tiers
Follow the steps under section " Run AutoConfig on the Application Tiers " in OracleMetaLink Document 387859.1 to Run AutoConfig on all application tier nodes.

7. Synchronize appsutil on the Database Tier Nodes
Follow the steps under section "Copy AutoConfig to the RDBMS ORACLE_HOME" in OracleMetaLink Document 387859.1 to copy AutoConfig and Rapid Clone files to each database node via the admkappsutil.pl utility.

8. Run AutoConfig on the Database Tier
Follow the steps under section "Run AutoConfig on the Database Tier" in OracleMetaLink Document 387859.1 to Run AutoConfig on the database tier nodes.

9. Maintain Snapshot information
Log in to each Applications Node as the APPLMGR user, and run "Maintain Snapshot information" in AD Administration.
See Oracle Applications Maintenance Utilities for more information.

Section 2: Clone Oracle Applications Release 12

Use Rapid Clone to create template files for cloning on the source system. After the source system is copied to the target, Rapid Clone updates these templates to contain the new target system configuration settings.

Note: Rapid Clone never changes the source system configuration.

There are three phases to the cloning process:

1. Prepare the Source System
Execute the following commands to prepare the source system for cloning.

1. Prepare the source system database node for cloning
Log on to the source system as the ORACLE user. and run the following commands:
cd /appsutil/scripts/
perl adpreclone.pl dbTier

2. 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:
cd /admin/scripts
perl adpreclone.pl appsTier

Warning: If new Rapid Clone or AutoConfig updates are applied to the system, adpreclone.pl must be executed again on the dbTier and on the appsTier in order to apply the new files into the clone directory structures that will be used during the cloning configuration stage.

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.

1. Copy the application tier file system
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:


Tech Stack


2. Copy the database node file system
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: UNIX/Linux users should ensure that the symbolic links (soft links) are preserved when copying.
On most UNIX platforms, this can be accomplished with cp -RH command.
Please check the Unix man pages for the exact parameters for the cp command on your platform.

For example:
cd /target_dest_dir/db
cp -RH /source_dir/db/* .

Alternatively, the "tar" command can be used to compress the directories into a temporary staging area.
If you are using this command, take into consideration that you may have to use the -h option to follow symbolic links as on some platforms, following symbolic links is not the default behavior.

# 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.)

1. Configure the target system database server
Log on to the target system as the ORACLE user and enter the following commands to configure and start the database:
cd /appsutil/clone/bin
perl adcfgclone.pl dbTier

2. Configure the target system application tier server nodes
Log on to the target system as the APPLMGR user and type the following commands:
cd /clone/bin
perl adcfgclone.pl appsTier

Section 3: Finishing Tasks

This section lists tasks that may be necessary, depending on your implementation and the intended use of the cloned system.

1. Update profile options

2. Update printer settings

3. Update Workflow configuration settings

4. Verify the APPLCSF variable setting

5. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS

No comments:

Post a Comment