日志

Cloning Oracle Applications Release 11i with Rapid Clone

热度 1已有 1218 次阅读2008/1/4 15:02

Cloning creates an identical copy of an existing Oracle Applications system. There are various reasons for cloning an Oracle Applications system such as:

Creating a copy of the production system for testing updates.
Migrating an existing system to new hardware.
Creating a stage area to reduce patching downtime.

This document describes the process of cloning an Oracle Applications Release 11i system. The most current version of this note is document 230672.1 on OracleMetaLink. A FAQ is also available in document 216664.1 on OracleMetaLink.

Attention: Windows NT/2000 users. This document typically uses UNIX syntax when specifying directories; Please substitute the appropriate Windows syntax.

Section 1: Prerequisites
Tasks to perform. before using Rapid Clone.
Section 2: Clone Oracle Applications 11i
Tasks to prepare, copy, configure, and verify a cloned Applications System.
Section 3: Finishing Tasks
Tasks to complete the cloning process.
Section 4: Advanced Cloning Methods
Tasks for advanced options such as refreshing and multi-node cloning.

Conventions

	Convention	Meaning
	Source system	Applications system being cloned.
	Target system	Applications system being created as a copy of the source.
	APPLMGR	User which owns the applications file system (APPL_TOP and application tier technology stack)
	ORACLE	User which owns the database file system (RDBMS ORACLE_HOME and database files).
	CONTEXT_NAME	The CONTEXT_NAME variable refers to the name of the Applications Context file. For systems installed with Rapid Install 11.5.8 or earlier, this value will typically be set to <SID>. For new AutoConfig or Rapid Clone customers, CONTEXT_NAME will be set to <SID>_<HOSTNAME>.
	`Monospace Text`	Represents command line text. Type this command exactly as shown.
	< >	Text enclosed in angle brackets represents a variable. Substitute a value for the variable text. Do not type the angle brackets.

Section 1: Prerequisites

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

Verify source and target nodes software versions
In addition to the Oracle Applications software requirements (see Installing Oracle Applications Release 11i Part No. B10638-01), the following software component versions must exist on the source and/or target nodes. The location column indicates the node where the software component must be present.

Software	Minimum Version	Location	Details

Oracle Universal Installer	2.1.0.17	All source system nodes	Included in all 11.5.7 and later Rapid Install environments. If on an earlier release, or source system contains an ORACLE_HOME not installed with the Rapid Install, apply patch 2949808.
Perl	5.005	Source and target database nodes	You can use the Perl shipped with iAS1022 and RDBMS 9i or download it from Perl.com. Perl must be in the PATH before cloning.
JRE	1.1.8	Source database node	If the RDBMS ORACLE_HOME was not installed using Rapid Install, install JRE 1.1.8 into the <RDBMS ORACLE_HOME>/jre/1.1.8 directory.
JRE	1.3.1	Source database node	Windows users only: install JRE 1.3.1 into the <RDBMS ORACLE_HOME>/jre/1.3.1 directory. See Appendix A for installation instructions.
JDK	1.3.1	Target middle-tier applications nodes	Refer to Upgrading to JDK 1.3 with Oracle Applications 11i on OracleMetaLink for instructions.
Zip	2.3	All source nodes	Download from InfoZip. Zip must be in your PATH for cloning.

Windows users only:
Apply patch 2237858 to enable long file names support.
Apply the Rapid Clone patch
Update the Oracle Applications file system with the Rapid Clone files by applying patch 3130740 to all application tier server nodes.
Setup Rapid Clone on the Applications Tier

If the source Applications system was created with Rapid Install version 11.5.5 or earlier and has not been migrated to AutoConfig, follow the instructions Migrating to AutoConfig on the Applications Tier in document 165195.1 on OracleMetaLink).
All users must run AutoConfig on the Applications Tier (see section 5: Maintaining System Configurations in document 165195.1 on OracleMetaLink).

Setup Rapid Clone on the Database Tier
Implement AutoConfig in the RDBMS ORACLE_HOME (Follow the instructions in section Migrating to AutoConfig on the Database Tier in document 165195.1 on OracleMetaLink). Section 4 step 1 of the AutoConfig document must be followed for all versions of Rapidinstall and everytime Rapid Clone patch is applied.

Section 2: Clone Oracle Applications 11i

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. Rapid Clone will not change the source system configuration.

There are three phases to the cloning process:

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

Prepare the source system database tier for cloning
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

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 <COMMON_TOP>/admin/scripts/<CONTEXT_NAME>

perl adpreclone.pl appsTier

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 tier files are owned by the ORACLE user.

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:

<APPL_TOP>
<OA_HTML>
<OA_JAVA>
<COMMON_TOP/util>
<COMMON_TOP/clone>
<806 ORACLE_HOME>
<iAS ORACLE_HOME>

Copy the database tier file system
Log on to the source system database node as the ORACLE user.

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 up the source Applications system database and application tier processes

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)

Configure the target system database server
Log on to the target system as the ORACLE user and type the following commands to configure and start the database:

cd <RDBMS ORACLE_HOME>/appsutil/clone/bin

perl adcfgclone.pl dbTier

Configure the target system application tier server nodes
Log on to the target system as the APPLMGR user and type the following commands:

cd <COMMON_TOP>/clone/bin

perl adcfgclone.pl appsTier

Attention: Windows user only: add <806 ORACLE_HOME>\bin to the system path before running this step.

Section 3: Finishing Tasks

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

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.
Update printer settings
If the new cloned system needs to utilize different printers, update the target system with the new printer settings now.
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.