First of all following pre-requisites must be checked at the Operating System level.



Packages

SUNWarc

SUNWbtool

SUNWcsl

SUNWhea

SUNWi15cs

SUNWi1cs

SUNWi1of

SUNWlibC

SUNWlibm

SUNWlibms

SUNWsprot

SUNWtoo

SUNWuiu8

SUNWulcf

SUNWxwfnt

Patches

• 125100-04 or higher
• 120473-05 or higher
• 127111-02 or higher
• 137111-04 or higher

Kernel parameters in /etc/system

rlim_fd_max                                     65536

noexec_user_stack                        1

semsys:seminfo_semmni            100

semsys:seminfo_semmsl             256

shmsys:shminfo_shmmax           4294967295

shmsys:shminfo_shmmni            100

ulimit Value Settings

Verify that the owner of the Oracle Application Server and Oracle Database server file systems have the following ‘ulimit’ values:

• time (seconds) = unlimited
• file (blocks) = unlimited
• data (kbytes) = unlimited
• stack (kbytes) = unlimited
• memory (kbytes) = unlimited
• coredump (blocks) = unlimited
• nofiles (descriptors) = 65536

Java requirements

JDK 6 (bundled with R12, no need to manually install)

Operating system utilities

• ar
• ld
• make
• X Display Server
• ldd
• gcc
• g++

Next step is to create required users.

groupadd dba

useradd -g dba oradev

useradd -g dba appldev

passwd oradev

New Password:

Re-enter new Password:

passwd: password successfully changed for oradev

passwd appldev

New Password:

Re-enter new Password:

passwd: password successfully changed for appldev

Now let’s create required directories as root.

mkdir /u01

mkdir /u01/oracle

mkdir /u01/oracle/ERPDEV

mkdir /u01/oracle/ERPDEV/db

mkdir /u01/oracle/ERPDEV/apps

chown oradev:dba /u01

chown oradev:dba /u01/oracle

chown oradev:dba /u01/oracle/ERPDEV

chown oradev:dba /u01/oracle/ERPDEV/db

chown appldev:dba /u01/oracle/ERPDEV/apps

Create Staging area or else you can directly install from DVDs but you may need to switch DVDs during the installation.

Here we have created Staging directory as /u01/R12stage/

There are multiple ways for creating staging areas. The simplest method is to copy all DVD contents to Staging directory in following subfolders.

startCD,  oraDB, oraAppDB, oraApps, oraAS,  NLS-<Language> (if installing NLS)

Or else you can use adautostg.pl to create a staging area automatically.

ORATraining Tip: Execute the following to avoid unexpected errors during the installation since we are doing multiuser installation.
chmod 777 /tmp

ORATraining tip: Sometimes it has been noticed on some Solaris based installation that installation will throw following error.

/u01/R12stage/startCD/Disk1/rapidwiz/rapidwiz: whoami: not found

Execute the following before starting the installation to avoid the issue.

export PATH=$PATH:/usr/ucb/

Starting the installation:

cd /u01/R12stage/startCD/Disk1/rapidwiz

./rapidwiz

ORATraining tip: You can also execute directly with the path like “/u01/R12stage/startCD/Disk1/rapidwiz/rapidwiz/rapidwiz” to avoid selecting DVDs at the end of every component installation.

ORATraining Tip: Sometimes you may encounter following error after starting the installation.

/u01/R12stage/startCD/Disk1/rapidwiz/rapidwiz: /tmp/RapidInstall/bin/runWizard.sh: cannot execute

Execute the following to fix this if you encounter the same.

chmod 777 /u01/R12stage/startCD/Disk1/rapidwiz/bin

Welcome Screen:

Do not change anything in this screen unless you are upgrading existing Oracle Applications release. Express release will go with many default parameters and skip certain steps but not recommended for an Apps DBA.

Keep these blank if installing on test machine. This can always be filled later. You will need a valid CSI number and associated email id for this.

No not change anything in this screen unless you are restarting a failed installation or installing on secondary nodes in case of multinode installation.

Select a port pool here. All default ports will be added by a number selected in port pool and those ports will be assigned accordingly. For example with port pool 10, default ports will change as follows.

Web Server port will become 8010 (8000 + 10)

Forms port will become 9010 (9000 + 10)

Reports port will become 7010 (7000 + 10)

and so on..

res://ieframe.dll/acr_depnx_error.htm#<domain>,http://<server>:<port>/forms/frmservlet?config=<config>

It displays following error.

Internet explorer has closed this webpage to help protect your computer

A malfunctioning or malicious add-on has caused Internet Explorer to close this webpage.

Solution:

Goto Internet Explorer -> Tools -> Internet Options -> Advanced -> Scroll down to Security -> Uncheck “Enable memory protection to help mitigate online attacks*”

Close all browser windows and restart the browser. The issue should have been fixed

Edit: Alternatively you can use either of following 2 alternate solutions.

Alternate 2:

Open registry using start->Run->regedit->ok

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main

On the right hand side you will see a DWORD key called DEPOff. IF this is set to value 0, just change it to 1 and close registry editor.

Restart Internet Explorer and check if the problem has been fixed or not.

Alternate 3:

Right click on My Computer->Properties (or start->Run->sysdm.cpl->ok)

Click on “Advanced” Tab. Click on “Settings” button next to Performance.

Click on last tab “Data Execution Prevention”

Select Second option and then select “Internet Explorer” from the bottom pan.

(If “Internet Explorer” is not already present there then just click on “Add” and then select “c:\Program Files\Internet Explorer\iexplore.exe”)

Click OK and restart internet explorer. The problem should have been fixed.

This is the working fix for the issue.

Solution-1:

1) Take backup of jvm.dll located at c:\Program Files\Oracle\JInitiator 1.3.1.21\bin\hotspot directory.
2) Copy jvm.dll from C:\Program Files\Java\jre1.6.0_07\bin\client (or whichever highest version of jre you have) to c:\Program Files\Oracle\JInitiator 1.3.1.21\bin\hotspot
3) Clear browser cache and also Oracle Jar cache (Remove all files from c:\documents and settings\<username>\Oralce Jar cache)
4) Close all the browsers and restart

Enjoy !! The issue should have been resolved now !

Solution-2:

In case if you are unable to find the jvm.dll in that location or if the above solution didn’t work for you, you can download the working jvm.dll from this link.

REM
REM FILENAME
REM   cmclean.sql
REM DESCRIPTION
REM   Clean out the concurrent manager tables
REM NOTES
REM   Usage: sqlplus <apps_user/apps_passwd> @cmclean
REM
REM
REM   $Id: cmclean.sql,v 1.4 2001/04/07 15:55:07 pferguso Exp $
REM
REM
REM +==============================+
set verify off;
set head off;
set timing off
set pagesize 1000
column manager format a20 heading ‘Manager short name’
column pid heading ‘Process id’
column pscode format a12 heading ‘Status code’
column ccode format a12 heading ‘Control code’
column request heading ‘Request ID’
column pcode format a6 heading ‘Phase’
column scode format a6 heading ‘Status’
WHENEVER SQLERROR EXIT ROLLBACK;
DOCUMENT
WARNING : Do not run this script without explicit instructions
from Oracle Support
*** Make sure that the managers are shut down     ***
*** before running this script                    ***
*** If the concurrent managers are NOT shut down, ***
*** exit this script now !!                       ***
#
accept answer prompt ‘If you wish to continue type the word ”dual”: ‘
set feed off
select null from &answer;
set feed on
REM     Update process status codes to TERMINATED
prompt
prompt  ————————————————————————
prompt  — Updating invalid process status codes in FND_CONCURRENT_PROCESSES
set feedback off
set head on
break on manager
SELECT  concurrent_queue_name manager,
concurrent_process_id pid,
process_status_code pscode
FROM    fnd_concurrent_queues fcq, fnd_concurrent_processes fcp
WHERE   process_status_code not in (‘K’, ‘S’)
AND     fcq.concurrent_queue_id = fcp.concurrent_queue_id
AND     fcq.application_id = fcp.queue_application_id;
set head off
set feedback on
UPDATE  fnd_concurrent_processes
SET     process_status_code = ‘K’
WHERE   process_status_code not in (‘K’, ‘S’);
REM     Set all managers to 0 processes
prompt
prompt  ————————————————————————
prompt  — Updating running processes in FND_CONCURRENT_QUEUES
prompt  — Setting running_processes = 0 and max_processes = 0 for all managers
UPDATE  fnd_concurrent_queues
SET     running_processes = 0, max_processes = 0;
REM     Reset control codes
prompt
prompt  ————————————————————————
prompt  — Updating invalid control_codes in FND_CONCURRENT_QUEUES
set feedback off
set head on
SELECT  concurrent_queue_name manager,
control_code ccode
FROM    fnd_concurrent_queues
WHERE   control_code not in (‘E’, ‘R’, ‘X’)
AND     control_code IS NOT NULL;
set feedback on
set head off
UPDATE  fnd_concurrent_queues
SET     control_code = NULL
WHERE   control_code not in (‘E’, ‘R’, ‘X’)
AND     control_code IS NOT NULL;
REM     Also null out target_node for all managers
UPDATE  fnd_concurrent_queues
SET     target_node = null;
REM     Set all ‘Terminating’ requests to Completed/Error
REM     Also set Running requests to completed, since the managers are down
prompt
prompt  ————————————————————————
prompt  — Updating any Running or Terminating requests to Completed/Error
set feedback off
set head on
SELECT  request_id request,
phase_code pcode,
status_code scode
FROM    fnd_concurrent_requests
WHERE   status_code = ‘T’ OR phase_code = ‘R’
ORDER BY request_id;
set feedback on
set head off
UPDATE  fnd_concurrent_requests
SET     phase_code = ‘C’, status_code = ‘E’
WHERE   status_code =’T’ OR phase_code = ‘R’;
REM     Set all Runalone flags to ‘N’
REM     This has to be done differently for Release 10
prompt
prompt  ————————————————————————
prompt  — Updating any Runalone flags to ‘N’
prompt
set serveroutput on
set feedback off
declare
c         pls_integer := dbms_sql.open_cursor;
upd_rows  pls_integer;
vers      varchar2(50);
tbl       varchar2(50);
col       varchar2(50);
statement varchar2(255);
begin
select substr(release_name, 1, 2)
into   vers
from fnd_product_groups;
if vers >= 11 then
tbl := ‘fnd_conflicts_domain’;
col := ‘runalone_flag’;
else
tbl := ‘fnd_concurrent_conflict_sets’;
col := ‘run_alone_flag’;
end if;
statement := ‘update ‘ || tbl || ‘ set ‘ || col || ‘=”N” where ‘ || col || ‘ = ”Y”’;
dbms_sql.parse(c, statement, dbms_sql.native);
upd_rows := dbms_sql.execute(c);
dbms_sql.close_cursor(c);
dbms_output.put_line(‘Updated ‘ || upd_rows || ‘ rows of ‘ || col || ‘ in ‘ || tbl || ‘ to ”N”’);
end;
/

prompt

prompt  ————————————————————————

prompt  Updates complete.
prompt  Type commit now to commit these updates, or rollback to cancel.
prompt  ————————————————————————

prompt

set feedback on

REM  <= Last REM statment —————————————————–

CONCSUB <APPS username>/<APPS password>
<responsibility application short name>
<responsibility name>
<username>
[WAIT=N|Y|<n seconds>]
CONCURRENT
<program application short name>
<program name>
[PROGRAM_NAME="<description>"]
[REPEAT_TIME=<resubmission time>]
[REPEAT_INTERVAL= <number>]
[REPEAT_INTERVAL_UNIT=< resubmission unit>]
[REPEAT_INTERVAL_TYPE=< resubmission type>]
[REPEAT_END=<resubmission end date and time>]
[NLS_LANGUAGE=<language of the request>]
[NLS_TERRITORY=<territory of the request>]
[START=<date>]
[IMPLICIT=< type of concurrent request>
[<parameter 1> ... <parameter n>]

Examples:

Active Users
CONCSUB apps/[apps_pwd] SYSADMIN “System Administrator” SYSADMIN WAIT=N CONCURRENT FND FNDSCURS

Prints Environment Variables
CONCSUB apps/[apps_pwd] SYSADMIN “System Administrator” SYSADMIN WAIT=N CONCURRENT FND FNDPRNEV APPL_TOP

Table Name: FND_CONCURRENT_REQUESTS

Column Name: PHASE_CODE
 

 
Table Name: FND_CONCURRENT_REQUESTS

Column Name: STATUS_CODE
 

/*+ hint(argument) */

/*+ hint(argument-1 argument-2) */

All hints except /*+ rule */ cause the CBO to be used. Therefore, it is good practise to analyze the underlying tables if hints are used (or the query is fully hinted.

There should be no schema names in hints. Hints must use aliases if alias names are used for table names. So the following is wrong:

select /*+ index(scott.emp ix_emp) */ from scott.emp emp_alias

better:

select /*+ index(emp_alias ix_emp) */ … from scott.emp emp_alias

Why using hints

It is a perfect valid question to ask why hints should be used. Oracle comes with an optimizer that promises to optimize a query’s execution plan. When this optimizer is really doing a good job, no hints should be required at all.

Sometimes, however, the characteristics of the data in the database are changing rapidly, so that the optimizer (or more accuratly, its statistics) are out of date. In this case, a hint could help.

It must also be noted, that Oracle allows to lock the statistics when they look ideal which should make the hints meaningless again.

Hint categories

Hints can be categorized as follows:

• Hints for Optimization Approaches and Goals,
• Hints for Access Paths, Hints for Query Transformations,
• Hints for Join Orders,
• Hints for Join Operations,
• Hints for Parallel Execution,
• Additional Hints

Documented Hints

Hints for Optimization Approaches and Goals

• ALL_ROWS
  One of the hints that ‘invokes’ the Cost based optimizer
  ALL_ROWS is usually used for batch processing or data warehousing systems.
• FIRST_ROWS
  One of the hints that ‘invokes’ the Cost based optimizer
  FIRST_ROWS is usually used for OLTP systems.
• CHOOSE
  One of the hints that ‘invokes’ the Cost based optimizer
  This hint lets the server choose (between ALL_ROWS and FIRST_ROWS, based on statistics gathered.
• RULE
  The RULE hint should be considered deprecated as it is dropped from Oracle9i2.

See also the following initialization parameters: optimizer_mode, optimizer_max_permutations, optimizer_index_cost_adj, optimizer_index_caching and

Hints for Access Paths

• CLUSTER
  Performs a nested loop by the cluster index of one of the tables.
• FULL
  Performs full table scan.
• HASH
  Hashes one table (full scan) and creates a hash index for that table. Then hashes other table and uses hash index to find corresponding records. Therefore not suitable for < or > join conditions.
• ROWID
  Retrieves the row by rowid
• INDEX
  Specifying that index index_name should be used on table tab_name: /*+ index (tab_name index_name) */
  Specifying that the index should be used the the CBO thinks is most suitable. (Not always a good choice).
  Starting with Oracle 10g, the index hint can be described: /*+ index(my_tab my_tab(col_1, col_2)) */. Using the index on my_tab that starts with the columns col_1 and col_2.
• INDEX_ASC
• INDEX_COMBINE
• INDEX_DESC
• INDEX_FFS
• INDEX_JOIN
• NO_INDEX
• AND_EQUAL
  The AND_EQUAL hint explicitly chooses an execution plan that uses an access path that merges the scans on several single-column indexes

Hints for Query Transformations

• FACT
  The FACT hint is used in the context of the star transformation to indicate to the transformation that the hinted table should be considered as a fact table.
• MERGE
• NO_EXPAND
• NO_EXPAND_GSET_TO_UNION
• NO_FACT
• NO_MERGE
• NOREWRITE
• REWRITE
• STAR_TRANSFORMATION
• USE_CONCAT

Hints for Join Operations

• DRIVING_SITE
• HASH_AJ
• HASH_SJ
• LEADING
• MERGE_AJ
• MERGE_SJ
• NL_AJ
• NL_SJ
• USE_HASH
• USE_MERGE
• USE_NL

Hints for Parallel Execution

• NOPARALLEL
• PARALLEL
• NOPARALLEL_INDEX
• PARALLEL_INDEX
• PQ_DISTRIBUTE

Additional Hints

• ANTIJOIN
• APPEND
  If a table or an index is specified with nologging, this hint applied with an insert statement produces a direct path insert which reduces generation of redo.
• BITMAP
• BUFFER
• CACHE
• CARDINALITY
• CPU_COSTING
• DYNAMIC_SAMPLING
• INLINE
• MATERIALIZE
• NO_ACCESS
• NO_BUFFER
• NO_MONITORING
• NO_PUSH_PRED
• NO_PUSH_SUBQ
• NO_QKN_BUFF
• NO_SEMIJOIN
• NOAPPEND
• NOCACHE
• OR_EXPAND
• ORDERED
• ORDERED_PREDICATES
• PUSH_PRED
• PUSH_SUBQ
• QB_NAME
• RESULT_CACHE (Oracle 11g)
• SELECTIVITY
• SEMIJOIN
• SEMIJOIN_DRIVER
• STAR
  The STAR hint forces a star query plan to be used, if possible. A star plan has the largest table in the query last in the join order and joins it with a nested loops join on a concatenated index. The STAR hint applies when there are at least three tables, the large table’s concatenated index has at least three columns, and there are no conflicting access or join method hints. The optimizer also considers different permutations of the small tables.
• SWAP_JOIN_INPUTS
• USE_ANTI
• USE_SEMI

Undocumented hints:

• BYPASS_RECURSIVE_CHECK
  Workaraound for bug 1816154
• BYPASS_UJVC
• CACHE_CB
• CACHE_TEMP_TABLE
• CIV_GB
• COLLECTIONS_GET_REFS
• CUBE_GB
• CURSOR_SHARING_EXACT
• DEREF_NO_REWRITE
• DML_UPDATE
• DOMAIN_INDEX_NO_SORT
• DOMAIN_INDEX_SORT
• DYNAMIC_SAMPLING
• DYNAMIC_SAMPLING_EST_CDN
• EXPAND_GSET_TO_UNION
• FORCE_SAMPLE_BLOCK
• GBY_CONC_ROLLUP
• GLOBAL_TABLE_HINTS
• HWM_BROKERED
• IGNORE_ON_CLAUSE
• IGNORE_WHERE_CLAUSE
• INDEX_RRS
• INDEX_SS
• INDEX_SS_ASC
• INDEX_SS_DESC
• LIKE_EXPAND
• LOCAL_INDEXES
• MV_MERGE
• NESTED_TABLE_GET_REFS
• NESTED_TABLE_SET_REFS
• NESTED_TABLE_SET_SETID
• NO_FILTERING
• NO_ORDER_ROLLUPS
• NO_PRUNE_GSETS
• NO_STATS_GSETS
• NO_UNNEST
• NOCPU_COSTING
• OVERFLOW_NOMOVE
• PIV_GB
• PIV_SSF
• PQ_MAP
• PQ_NOMAP
• REMOTE_MAPPED
• RESTORE_AS_INTERVALS
• SAVE_AS_INTERVALS
• SCN_ASCENDING
• SKIP_EXT_OPTIMIZER
• SQLLDR
• SYS_DL_CURSOR
• SYS_PARALLEL_TXN
• SYS_RID_ORDER
• TIV_GB
• TIV_SSF
• UNNEST
• USE_TTT_FOR_GSETS

This document is divided into the following sections:

• Section 1: Terminology
• Section 2: Supported Scenarios
• Section 3: References

The most up-to-date version of this document can be obtained in Note 783188.1.

Section 1: Terminology

Cloning an Oracle E-Business Suite system that uses an Oracle Real Application Clusters (Oracle RAC) enabled database involves numerous different technology components and steps, and would therefore be a complex, error-prone process if carried out manually.

To speed up, simplify, and enhance reliability of the process, Oracle offers the following tools for use in cloning RAC Enabled Oracle E-Business Suite systems:

• Rapid Clone – Command-line tool
• Oracle Application Management Pack for Oracle E-Business Suite (AMP) – GUI-based tool used for automated end-to-end cloning

This document provides details of the RAC scenarios that are currently certified for cloning using these tools. Other scenarios are planned as shown.

Note: Scenarios not shown are not supported.

Section 2: Supported Scenarios

The following table illustrates the various cloning permutations that exist with different versions of Oracle E-Business Suite and its components, operating system software, and the cloning tools available.

Key:

N/A = Not Applicable
TBD = To Be Decided

• 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 is based on Oracle Metalink document 230672.1 (cloning an Oracle Applications Release 11i system).

• 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

Section 1: Prerequisites

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

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

2. Windows users only:
Apply patch 2237858 to enable long file names support.

3. Apply the Rapid Clone patch
Update the Oracle Applications file system with the Rapid Clone files by applying the patch 3453499 (11i.ADX.F) to all application tier server nodes.

4. Setup Rapid Clone on the Applications Tier

• a. 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).
• b. All users must run AutoConfig on the Applications Tier (see section 5: Maintaining System Configurations in document 165195.1 on OracleMetaLink).

5. 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). Follow steps 1 and 4 of Section 5 in the AutoConfig document for all versions of RapidInstall and every time you apply a new version of the Rapid Clone patch.

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:

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

•a. 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

•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:
cd <COMMON_TOP>/admin/scripts/<CONTEXT_NAME>
perl 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 tier files are owned by the ORACLE user.

•a. 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>
• <OA_JRE_TOP>
• <COMMON_TOP>/util
• <COMMON_TOP>/clone
• <COMMON_TOP>/_pages(when this directory exists)
• <806 ORACLE_HOME>
• <iAS ORACLE_HOME>

•b. 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

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

•a. 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

•b. 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

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

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.

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 an acceptable directory. To modify it, change the value of s_applcsf in the contextfile and 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.

6. Windows users only reboot the target machine
Once cloning is completed reboot to enable the services.

Section 4: Advanced Cloning Options

This section describes advanced cloning procedures.

1. Refreshing a target system
You may need to refresh the target system periodically to synchronize it with changes from the source.

To refresh the target system, perform the following steps as described in previous sections:

• a. Prepare the Source System
• b. Copy the Source System to the Target System
• o Copy the application tier file system if the APPL_TOP, 806 ORACLE_HOME, or iAS ORACLE_HOME needs to be refreshed. Copy the portion of the application tier file system which has been updated.
• o Copy the database tier file system if the RDBMS ORACLE_HOME or the database needs to be refreshed. If refreshing the database, the ORACLE_HOME should be refreshed at the same time.
• c. Configure the Target System
  Specify the existing target system context file when running adcfgclone.pl commands:
• o perl adcfgclone.pl dbTier <Database target context file>
  where database context file is:
  <RDBMS ORACLE_HOME>/appsutil/<Target CONTEXT_NAME>.xml
• o perl adcfgclone.pl appsTier <Appltop target context file>
  where appltop context file is:
  <APPL_TOP>/admin/<Target CONTEXT_NAME>.xml
• d. Finishing Tasks

2. Cloning a single-node system to a multi-node system
This procedure allows the original single-node system to be cloned into a multi-node system. An Applications system comprises five server types:

• o Database server (database tier)
• o Forms server (application tier)
• o Web server (application tier)
• o Concurrent Processing server (application tier)
• o Administration server (application tier)

During the single-node to multi-node cloning process, each of these servers can be placed on its own node, resulting in a multi-node target system.

• f. Perform prerequisites
  Perform these steps on all source and target nodes.
• g. Clone Oracle Applications 11i
  Prepare, copy and configure the cloned Applications System. When creating more than one application tier server node from a single node system, the copy and configure steps must be performed on each target node. You can specify the server type for each target node while answering the prompts during the configuration step.
  The database ORACLE_HOME and database only need to be copied to the node on which the database will be run.
• h. Finishing Tasks

3. Cloning a multi-node system to a multi-node system with same number of nodes
A multi-node system can be cloned provided the number of nodes and distribution of servers in the target system matches that of the source system.

To clone a multi-node system to a multi-node system, perform the cloning process on each node. For example, if the source system contains three nodes, perform the cloning process three times.

• o Clone source system node 1 to target system node 1.
• o Clone source system node 2 to target system node 2.
• o Clone source system node 3 to target system node 3.

4. Adding a new node to an existing system
You can use Rapid Clone to clone a node and add it to the existing Application System. The new node will run the same or a subset of the server types running on the source node. Follow the instructions in the Application Tier part of Clone Oracle Applications 11i:

• o Prepare the source system, copy it to the new node and configure it.
• o After adcfgclone.pl completes, source the Applications environment and run the following commands on the target system:
• o cd <COMMON_TOP>/clone/bin
• o perl adaddnode.pl

5. Reducing the number of nodes of a multi-node system (merge APPL_TOP)
You can use Rapid Clone to clone a multi-node system to a single-node system (or a multi-node system with fewer nodes) by merging the APPL_TOPs filesystem together. Follow the procedure for Merging existing APPL_TOPs in document 233428.1 on OracleMetaLink.

6. Cloning a RAC system
You can use Rapid Clone to clone a RAC system. While cloning, you have the possibility to remove or add nodes to the cluster in the target RAC system. To clone a RAC system, perform the following tasks:

• a. Verify the prerequisites
• o Apply TXK patch 3571388 (AutoConfig support for Oracle RAC instances)
• o Migrate the source system cluster ORACLE_HOMES to AutoConfig as documented in document 165195.1 on OracleMetaLink
• b. Prepare the Source System
  Choose one of the ORACLE_HOMEs on the source cluster. This ORACLE_HOME will be used as a master to create all the target cluster system ORACLE_HOME. Run “perl adpreclone.pl dbTier” on it.

• b. Copy the Source System to the Target Syste
  • Copy the master ORACLE_HOME from the source system to each node that will compose the target cluster. For example, if your source RAC system had 2 nodes, and you want to clone it to a 3 node target RAC system, you should copy the source master ORACLE_HOME to the 3 nodes on the target system
  • o Copy the database files from the source to target system.
• c. Configure the Target System
  • o Log on to any ORACLE_HOME in the target cluster and run
  • o adcfgclone.pl dbTier

This step configures the first node of the target system RAC cluster and recreates the database control files. The prompts, however, will gather information about every node in the target RAC cluster and the data will be re-used when configuring each subsequent node in the next step.

o For each remaning RDBMS ORACLE_HOME in the target system, run the following command as the ORACLE file system owner:

• § adcfgclone.pl dbTier
• o If your database is version 10g or higher, run the following commands to register the database and the instance to the cluster manager .
• § srvctl add database -d <database_name> -o <oracle_home>
• § srvctl add instance -d <database_name>
-i <instance_name> -n <host_name>

• d. Clone the application tier
  Follow the steps in section 2 to prepare, copy and configure the application tier. When prompted for the database SID, specify any one of the RAC service names.

7. Adding a node to an existing RAC Cluster
You can use Rapid Clone to add one or several nodes to an existing RAC Cluster. Perform the following tasks:

• a. Choose any one of the ORACLE_HOMEs in the existing cluster and run “perl adpreclone.pl dbTier” on it. This ORACLE_HOME will be used as a master to create the additional node(s).
• b. Copy the master ORACLE_HOME filesystem to the new node(s).
• c. Reconfigure the RAC Cluster to include the new node(s):
• o Log on to the new node, or any one of the new nodes if adding more than one, and run the following command:
• § cd /appsutil/clone/bin
• § perl adcfgclone.pl dbTier

• o When instructed so by the previous step, log on to every node from the original cluster and run the following command on each of them:
• § cd /appsutil/clone/bin
• § perl adcfgclone.pl addracnode <context file>
• o Go back to the first node and complete adcfgclone.pl
• o If you are adding more than one node to the original cluster, log on to each of the remaining new nodes and run
• § cd /appsutil/clone/bin
• § perl adcfgclone.pl dbTier

8. Cloning a Shared File System
You can use Rapid Clone to clone a shared APPL_TOP system. Since all the nodes share a unique APPL_TOP you only need to fully clone one of the source system nodes to its target machine and add more nodes directly sharing the APPL_TOP on the target system. Choose one of the shared APPL_TOP nodes on source system (the rest of this section will refer to it as Node A) and perform the following tasks:

• a. Perform prerequisites
  Perform these steps on Node A and and every target nodes.
• b. Clone Oracle Applications 11i
  Perform a full clone (Prepare, copy and configure steps) of the Database Tier and Node A (Application tier).
• c. Add the shared file system nodes to the target system
  On the target system, follow the instructions for adding a node to a shared APPL_TOP system in document 233428.1 on OracleMetalink and add more nodes sharing the target system APPL_TOP to match the source system topology.

Appendix A: Install JRE 1.3.1 into RDBMS ORACLE_HOME

Windows customers will need to perform the following steps:

• Download JRE 1.3.1 from Sun Microsystems.
• Run the install executable
• When prompted for the location to install jre, click browse and enter the location:
  <RDBMS ORACLE_HOME>jre1.3.1
• Accept the default installation options.

JRE 1.3.1 will be installed into the <RDBMS ORACLE_HOME>jre1.3.1 directory.

Appendix B: Recreating database control files manually in Rapid Clone.

This Appendix documents the steps to allow manual creation of the target database control files within the Rapid Clone process. Examples of when to use this method are for databases on raw partitions or hot backup cloning. Replace section 2.3a (Configure the target system database server) with the following steps:

• Log on to the target system as the ORACLE user
• Configure the <RDBMS ORACLE_HOME>
• o cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
• o perl adcfgclone.pl dbTechStack
• Create the target database control files manually
• Start the target system database in open mode
• Run the library update script against the database
• o cd <RDBMS ORACLE_HOME>/appsutil/install/<CONTEXT NAME>
• o sqlplus "/ as sysdba" @adupdlib.sql <libext>
  where <libext> is “sl” for HP-UX, “so” for any other UNIX platform and not required for Windows.
• Configure the target database (the database must be open)
• o cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
• o perl adcfgclone.pl dbconfig <target context file>
  where target context file is:

<RDBMS ORACLE_HOME>/appsutil/<Target CONTEXT_NAME>.xml