Professional Documents
Culture Documents
Page 1 of 7
">
Cloning Oracle Applications Release 12 with Rapid Clone [ID 406982.1] Modified 26-DEC-2011 Type BULLETIN Status PUBLISHED
In This Document
Section 1: Prerequisite Tasks Section 2: Cloning Tasks Section 3: Finishing Tasks Section 4: Advanced Cloning Options
Terminology
Cloning is the process used to create a copy of an existing Oracle Applications system. There are various scenarios for cloning an Oracle Applications system, including: Standard cloning - Making a copy of an existing Oracle Applications system, for example a copy of a production system to test updates. System scale-up - Adding new machines to an Oracle Applications system to provide the capacity for processing an increased workload. System transformations - Altering system data or file systems, including actions such as platform migration, data scrambling, and provisioning of high availability architectures. Patching and upgrading - Delivering new versions of Applications components, and providing a mechanism for creating rolling environments to minimize downtime. An important principle in Oracle Applications cloning is that the system is cloned, rather than the topology. Producing an exact copy of the patch level and data is much more important than c copy of the topology, as a cloned system must be able to provide the same output to the end user as the source system. However, while a cloned system need not have the full topology of it have available to it all the topology components that are available to the source. Note: The Cloning methodology posted on this document requires full Autoconfig compliance. Conventions used in this document include the following: Term or Usage Source system Target system APPLMGR ORACLE Meaning or Action Oracle Applications system being cloned. Oracle Applications system being created as a copy of the source. User that owns the application tier file system (APPL_TOP and application tier technology stack). User that owns the database tier file system (RDBMS ORACLE_HOME and database files).
CONTEXT_NAME The CONTEXT_NAME variable refers to the name of the Applications context file. By default, CONTEXT_NAME is [SID]_[HOSTNAME].
Monospace Text
Represents command line text. Type this command exactly as shown. Text enclosed in brackets represents a variable. Substitute a value for the variable text. Do not type the brackets.
[]
2. Verify source and target system software components and versions In addition to the Oracle Applications software requirements (see Oracle Applications Installation Guide: Using Rapid Install), the following software component versions must exist on nodes as applicable. The 'Location' column indicates the node where the software component must reside.
Comments Download from InfoZip. Zip must be in your $PATH. If using files bigger than 2Gb, you should use InfoZip ZIP 3.0 or highe Download from InfoZip. Unzip must be in your $PATH. If using files bigger than 2Gb, you should use InfoZip UNZIP 5.52 o The required operating system utilities for your platform must be in your $PATH when running adcfgclone.pl. For example, on UNIX. Refer to Oracle Applications Installation Guide: Using Rapid Install (see Footnote 1)
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLET... 30/05/2012
Page 2 of 7
Perl
5.x
Use the Perl shipped with OracleAS 10.1.3 and Database 10g, or download it from Perl.com. Perl must be in your $PATH, must be set correctly before cloning.
Footnote 1 This is the Release 12.1.1 version; versions for earlier releases are also available from the Oracle E-Business Suite Online Documentation Library 3. Apply the latest AD patch Refer to My Oracle Support to obtain the latest AD patch. At the time of writing this note, the following patches were available: For Release 12.0: Apply patches as listed in Table 2.a.
4. Apply the latest AutoConfig template patch Update the Oracle Applications file system with the latest AutoConfig template files by applying the TXK AutoConfig Template Rollup patch to all application tier server nodes. Refer to Knowledge Document 387859.1 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 the following patches to all Applications nodes. For Release 12.0: Apply patches as listed in Table 3.a.
Warning: Failing to use the latest code may jeopardize the success of the clone. If new Rapid Clone or AutoConfig updates are applied to the system, steps 6, 7, and 8 below must in order to apply the new files to the database node.
6. Run AutoConfig on the application tiers Follow the steps under section " Run AutoConfig on the Application Tiers " in My Oracle Support Knowledge 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 My Oracle Support Knowledge Document 387859.1 to copy AutoConfig and Rapid Clone files to via the admkappsutil.pl utility.
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLET... 30/05/2012
Page 3 of 7
8. Run AutoConfig on the database tier Follow the steps under section "Run AutoConfig on the Database Tier" in My Oracle Support Knowledge Document 387859.1 to run AutoConfig on the database tier nodes. 9. Maintain Snapshot Information Log in to each application tier node as the APPLMGR user, and run "Maintain Snapshot Information" in AD Administration. To update the snapshot, please select the following options View Snapshot" and "Update Complete APPL_TOP". Note: If a snapshot was never created for that APPL_TOP, you will need to create a new one before proceeding with the clone. Refer to Oracle Applications Maintenance Utilities fo (this is the Release 12.1 version; versions for earlier releases are also available from the Oracle E-Business Suite Online Documentation Library).
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 [INST_TOP]/admin/scripts $ perl adpreclone.pl appsTier
Note: 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 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 t are owned by the target APPLMGR user, and that the database node files are owned by the target ORACLE user.
Note: In the copying tasks below, UNIX/Linux users should ensure that the symbolic links (soft links) are preserved when copying. On most UNIX platforms, this can be accomplishe command. Consult the UNIX man page for the cp command to check the parameters available 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. UNIX/Linux users should ensure that the symbolic links (soft links) are prese compressing. On most UNIX platforms, this is the default behavior of tar command. Consult the UNIX man page for the tar command to check the parameters available on your pla Additionally, verify the permissions of the executables under ORACLE_HOME/bin that can potentially be owned by root (i.e. nmo, nmhs, nmb, etc).
a. Copy the application tier file system Log on to the source system application tier nodes as the APPLMGR user and shut down the application tier server processes. Copy the following application tier directories fro the target application tier node: [APPL_TOP] [COMMON_TOP] Applications Technology Stack: [OracleAS Tools ORACLE_HOME] [OracleAS Web IAS_ORACLE_HOME] b. Copy the database node file system Log on to the source system database node as the ORACLE user, and then: 1. 2. 3. 4. 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
3. Configure the target system Run the following commands to configure the target system. You will be prompted for specific target system values such as SID, paths, and ports. a. Configure the target system database server Log on to the target system as the ORACLE user and enter the following commands:
$ 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 enter the following commands:
$ cd [COMMON_TOP]/clone/bin $ perl adcfgclone.pl appsTier
Note: If you are cloning between different versions of the Operating System (e.g. Linux 5 to Linux 4) it is recommended that you relink the AD_TOP product binaries using [adrelinkn followed by APPL_TOP executables with adadmin.
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLET... 30/05/2012
Page 4 of 7
WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE WF_ITEM_ATTRIBUTE_VALUES WF_SYSTEMS WF_SYSTEMS WF_AGENTS FND_FORM_FUNCTIONS FND_FORM_FUNCTIONS TEXT_VALUE GUID NAME ADDRESS WEB_HOST_NAME
WEB_AGENT_NAME Update to point at the new PL/SQL listener name. Update with the correct path to the logfile directory. Update with the new directory path 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 a suitable directory. To m value of the s_applcsf variable in the context file and then 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 do 6. Re-Implement SSL and SSO configuration If the Source System was SSL or SSO enabled, and the Target is wished to be SSL or SSO enabled, then reconfigure the Target by following the SSL/SSO documentation. Otherwise wished to be non-SSL or non-SSO, then follow the same SSL/SSO documentation to undo the SSL/SSO setup.
b. Configure the target system application tier server nodes by logging on to the target system as the APPLMGR user and entering the following commands:
$ cd [COMMON_TOP]/clone/bin $ perl adcfgclone.pl appsTier [APPL_TOP target context file] Where APPL_TOP target context file is [INST_TOP]/appl/admin/[Target CONTEXT_NAME].xml
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLET... 30/05/2012
Page 5 of 7
Carry out these steps on all source and target nodes. 2. Carry out the previously-described cloning tasks. Prepare, copy and configure the cloned Applications system. When creating more than one application tier node on the target system, follow these steps: 1. Perform a full clone (Prepare, copy and configure steps) of the database node and primary application tier node. 2. To add shared application tier nodes on the target system, follow the instructions in My Oracle Support Knowledge Document 384248.1, Section 4: Adding a node to a Shared A System. 3. To add non-shared application tier nodes, execute the copy and configure steps as on the primary node. 4. Specify the services to start on each target Applications tier node when responding to the prompts during the configuration step. 3. Perform the required finishing tasks
Note: After adding new nodes, refer to My Oracle Support Knowledge Document 380489.1 for details of how to set up load balancing.
Note: If SQL*Net Access security is enabled in the existing system, you first need to authorize the new node to access the database through SQL*Net. See the Oracle Applications Manag instructions on how to accomplish this.
3. Create the target database control files manually In this step, you copy and recreate the database using your preferred method, such as RMAN restore, Flash Copy, Snap View, or Mirror View. 4. Start the target database in open mode 5. Run the library update script against the database
$ cd [RDBMS ORACLE_HOME]/appsutil/install/[CONTEXT NAME] $ sqlplus "/ as sysdba" @adupdlib.sql [libext] Where [libext] should be set to 'sl' for HP-UX, 'so' for any other UNIX platform, or 'dll' for Windows.
6. Configure the target database The database must be running and open before performing this step.
$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin $ perl adcfgclone.pl dbconfig [Database target context file] Where Database target context file is: [RDBMS ORACLE_HOME]/appsutil/[Target CONTEXT_NAME].xml.
Note: The dbconfig option will configure the database with the required settings for the new target, but it will not recreate the control files.
Change Log
Date Description Removed duplicated patch. Added Patch 12598630:R12.OAM.B. Added relink recommendation when cloning between slightly different OS versions.
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLET... 30/05/2012
Page 6 of 7
Further clarified SSL/SSO considerations in Section 3, Step 6. Further clarified tar considerations in Section 2, Step 2.
Added a note for Autoconfig requirement. Added note for patch reinforcement.
Added Patch 9833058 for 12.0 and 12.1 on Section 1, Step 5 Clarified AD Patches for 12.0 and 12.1
Addressed general formatting issues Added clarifications for versions of ZIP and UNZIP in Section 1 Added additional step for SSL/SSO in Section 3 Replaced Rapid Clone Consolidated Patch with 8360494 (JAN/2010) Removed other patches since they are now included in 8360494
Restructured document.
Moved Appendix A into the Advanced Cloning Options and added some more details.
Added Patch 7699109 on Section 1, Step 5. Added Clarification for RUP2 or higher.
Replaced Rapid Clone Consolidated Patch with 6776948 (Jul 2008). Removed Patch 6854328 since its included on 6776948 (Jul 2008).
Removed Rapid Clone restriction for RAC-enabled Systems in Section 4, Steps 4 and 5. Added reference to Document 559518.1 for RAC cloning instructions. Added tracking bug number 7276544 to add a node on an existing RAC system without cloning. Added tracking bug number 7275583 to add a node while cloning a RAC system.
Added Unzip 5.52 to Section 1, Step 2. Included Patch 6854328 for Windows 64-bit in Section 5, Step 5. Fixed post patch steps on note box.
Minor layout changes. Added requirement to apply the latest AD Patch. Added clarification to backup the context file when refreshing a target system on 4.1. Included step to verify OS requirements.
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLET... 30/05/2012
Page 7 of 7
Removed Windows desupport notice. Added Warning to re-run post-clone steps after patching the system.
Removed reference to HP OpenVMS Alpha since this is not a certified or supported platform for any tier with Release 12.
Added note that using Rapid Clone on Windows is not currently supported.
My Oracle Support Knowledge Document 406982.1 by Oracle E-Business Suite Development Copyright 2007, 2009, 2010, 2011 Oracle and/or its affiliates. All rights reserved.
Related
Products Oracle E-Business Suite > Applications Technology > Lifecycle Management > Oracle Applications Manager Keywords $PERL5LIB; ADADDNODE.PL; ADCFGCLONE.PL; ADMKAPPSUTIL.PL; ADPRECLONE.PL; APPL_TOP; AUTOCONFIG; CLONE; CONTEXT; E-BUSINESS; LIBRARY; LOGFILE; M PERMISSION; R12.1; SOURCE; UNZIP Errors ORA-201
Back to top Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLET... 30/05/2012