Cloning Oracle Applications Release 11i

Cloning Oracle Applications Release 11i with Rapid Clone 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/appsutil/scripts/ 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 /admin/scripts/ 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. Copy the application tier file system Log on to the source system application tier nodes as the APPLMGRuser.  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>

/util /clone /_pages (when this directory exists) <806 ORACLE_HOME> Copy the database tier file system : Log on to the source system database node as the ORACLE user.  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 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 /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 /clone/bin perl adcfgclone.pl appsTier Finishing Tasks : Update profile options Update printer settings Update workflow configuration settings Verify the APPLCSF variable setting  Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS    

Cloning Oracle Applications Release 11i with Rapid Clone(Singlenode to Multinode) This procedure allows the original single-node system to be cloned into a multi-node system. 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. 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. 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/appsutil/scripts/ 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 /admin/scripts/ 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. Copy the application tier file system Log on to the source system application tier nodes as the APPLMGRuser.  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> /util /clone /_pages (when this directory exists) <806 ORACLE_HOME> Copy the database tier file system : Log on to the source system database node as the ORACLE user.  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 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 /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 /clone/bin perl adcfgclone.pl appsTier

Finishing Tasks : Update profile options Update printer settings Update workflow configuration settings Verify the APPLCSF variable setting  Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS    

Cloning Oracle Applications Release 11i with Rapid Clone (Multinode to Multinode) 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 o Clone source system node 2 to target system node o Clone source system node 3 to target system node The database server node must be cloned first :

Manual Clone without autoconfig : The AD cloning utility in preclone mode: · Shuts down any running services on the current node · Saves the configuration files from the APPL_TOP · Saves the configuration files from the COMMON_TOP · Removes APPL_TOP, JAVA_TOP, and OA_HTML directory contents. 

Remove the database files from the target systemAs you will be using copies of the database files from the source system, the database files created by Rapid Install for the target system can be removed. Use the database server process control script (addbctl.sh) to shutdown the database of the target system. Delete all of the database files (*.dbf files) from the target system.

 Copy the source system database To copy the source system database to the target system, perform the followingsteps.  On the source system database, create a list of datafiles and online redo log files of your source system database by issuing an "alter database

backup controlfile to trace" command in the source system database. Examine the resultant trace file located in the user_dump_dest directory.  Perform a normal shutdown of the source system database.  Perform a cold backup of the source system database.  Log on to the target system as the oracle user and set the database environment using the database environment file. The environment file for the database server is located in the database server ORACLE_HOME, and is called <SID>.env (UNIX or Linux) or <SID>.cmd (Windows).  Copy the database files to the target system. Identify the new mount points for the database files and copy the database files from the backup of the source system to the new target system.  Verify the target system init.ora parameters. You may have updated the database initialization file in your source system. Verify that the parameter changes are reflected in the init.ora of your target system. Check all parameters, especially the location of your control files and the names of your rollback segments.  Create a new control file. To create new control files: o Update the trace file from step a) with SID and mount point informationpertinent for the target system and use it to create a control file creation script. o Start up the target system instance, but do not mount or open the Database. o Create a new control file for the database using the control file creation script. Specify the RESETLOGS option if the database SID was renamed. Otherwise, use the NORESETLOGS option.  Open the database. If RESETLOGS was specified when creating the control file, use ALTER DATABASE OPEN RESETLOGS, else use ALTER DATABASE OPEN.  Reset the database identifier (required for Oracle Recovery Managerusers) If you use Oracle Recovery Manager (RMAN) with Oracle Applications, you must reset the database identifier (DBID) with a unique ID. RMAN requires that each database instance have a unique DBID. As the target system database files are copied directly from the source system, they retain the source system DBID.

The DBID is stored in the generic file header of the control file, datafiles, temp files and online log files. To reset the DBID in all of these locations perform the following steps: Cleanly shut down the database Start the instance and mount the database, but leave it closed Cleanly shut down the database Start the instance and mount the database, but leave it closed

· 

Update the GLOBAL_NAME (conditionally required) If the database name was changed, perform this command in SQL*Plus as the SYSTEM user to change the GLOBAL_NAME in the database: SQL> alter database rename global_name \ to

Copy the source system files To copy the source APPL_TOP, OA_HTML, and JAVA_TOP directories to the target system, perform the following steps:  Verify that all users have logged off the source system and that all Applications server processes have been shut down.  Log on as the applmgr user on the target system.  Copy the source APPL_TOP, OA_HTML, and JAVA_TOP. Copy these directory trees from each node of the source system to each corresponding node of the new target system. If your target system is on the same machine as your source system or the disks are NFS mounted, you can copy an entire directory tree at once. Replace the target system configuration In the “Prepare the target system” section, the configuration specific to the target system was saved before replacing files with those from the source system. Perform the following steps to re-implement the saved configuration on the target system: Run the AD cloning utility Log on as the applmgr user, do not run or execute the Applications environment setup file, and run the AD cloning utility in postclone mode to configure the target system. The AD cloning utility is located in the AD_TOP/bin directory. Note: The AD cloning utility will prompt you for the SYSTEM and APPS

passwords when running in postclone mode. The AD cloning utility in postclone mode will: · · · · · ·

Configure the database profiles Replace the configuration files associated with the APPL_TOP Replace the configuration files associated with the COMMON_TOP Generate the database security (DBC) file Update the interMedia shared library path Startup the services for this node When cloning a multi-node system, repeat the steps in this section on each node in your system.