Oracle DBA Scripts

Cloning an Oracle Applications System

Simply copying all the Oracle Applications components will not provide a working duplicate Oracle Applications system. Many configuration files in the system and configuration information in the database must be modified based on the system configuration. Typically, you create a clone of an Oracle Applications system because you want to:

■ Create a copy of a production system for testing updates

■ Create a staged system to reduce patching downtime

The Oracle Applications cloning methodology uses AutoConfig with Rapid Clone to configure the duplicate system. There are prerequisite steps before running Rapid Clone, and some finishing steps after running Rapid Clone to complete the process.

The complete list of steps is included in this section.

Perform Prerequisite Tasks

Prepare the source system by applying patches and running AutoConfig.

1. Verify source and target node software versions. In addition to the software requirements listed in Installing Oracle Applications, the following software component versions must exist on the source nodes. The location column indicates the node where the software component must be present (see TABLE-1).

2. Run AutoConfig on the application tier server nodes.

3. Run AutoConfig on the database tier.

Clone Oracle Applications 11i

In this action you will prepare the source system for cloning, copy the source system to the target system, and configure the target system.

Prepare the source system

Complete these steps to prepare the source system for cloning.

1. Prepare the source system database tier. 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

2. Prepare the source system application tier.

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 targetnode by completing the following steps in the order listed. Be sure 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.

1. Copy the application tier file system.

Log on to the source system application tier node as the applmgr user. Then, do thefollowing:

■ Shut down the application tier server processes

■ Copy the following application tier directories from the source node to the target application tier node, retaining the original directory structure:

– {APPL_TOP}

– {OA_HTML}

– {OA_JAVA}

– {COMMON_TOP/util}

– {COMMON_TOP/clone}

– {COMMON_TOP/_pages} (when the directory exists)

– {806 ORACLE_HOME}

– {iAS ORACLE_HOME}

2. Copy the database tier file system.

Log on to the source system database tier node as the oracle user. Then, do the following:

■ Perform a normal shutdown of the source system database

■ Copy the database (DBF) files from the source system to the target system

■ Copy the source database ORACLE_HOME to the target system

■ Start the source Applications system database and application tier processes

Configure the target system

Run the following commands to configure the target system:

1. 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

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 {COMMON_TOP}/clone/bin

perl ./adcfgclone.pl appsTier

Finish the Cloning Process

Complete the steps in this section if they apply to your implementation or to the way you intend to use 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.

2. Update printer settings.If the new cloned system will use different printers from the source system, update the new system with the new printer settings.

3. Update Workflow configuration settings. Cloning an Oracle Applications instance does 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. (see TABLE-2)

4. Verify the APPLCSF variable setting.

Set the Applications environment and ensure that the variable APPLCSF(identifying the top-level directory for concurrent manager log and output files) points to an acceptable directory. To modify it, change the value of s_applcsf in the context file and run AutoConfig.

5. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS.

Note: For Windows users only: add {806 ORACLE_HOME}\bin to the system path before performing this step.

.

6. Reboot the target machine (Windows only).

Software	Minimum Version	Location	Details
JRE(Windows)	1.3.1	Source database node	Install JRE 1.3.1 into the {RDBMS ORACLE_HOME}/jre/1.3.1 directory.
Zip	2.3	All source nodes	Download from InfoZip. Zip must be in your PATH for cloning.

(TABLE-1 - ^) (TABLE-2 - v)

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	Replace value with the new 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 log file directory.
FND_CONCURRENT_REQUESTS	OUTFILE_NAME	Update with the new directory path on the target system