Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.1

Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC [ID 760637.1] Modified 01-APR-2009 View Change log Type WHITE PAPER Status PUBLISHED

Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC
April 2009

NOTE: These instructions provide a manual method of cloning Oracle Applications Release 11i utilizing the Real Applications Cluster option in Oracle Database versions 10g and or 11g. . These steps should not be used for 11i configurations in which Oracle Database version 9i has been enabled to utilize the RAC option. For 11i with 9i RAC, please see the Advanced Cloning section of document 230672.1. The below steps assume and require a high degree of familiarity with Oracle Applications AD Utilities, RapidClone, Autconfig, Recovery Manager and SQL*Plus.

This document describes the process of manualy cloning an Oracle Applications Release 11i system when configured to use the Real Applications Cluster option present in Oracle Database versions 10g and 11g . The most current version of this note is document 760637.1 on OracleMetaLink. A FAQ is also available in document 216664.1 on OracleMetaLink.

Note: Rapid Clone is currently not supported on Windows Itanium, Windows x86-64 (EM64T) and HP OpenVMS Alpha. Attention: Windows users. This document typically uses UNIX syntax when specifying directories; Please substitute the appropriate Windows syntax Section 1: Manual RAC Cloning Process Overview Outline of steps which are detailed further within this document

1 of 26

7/22/2010 1:51 PM

Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.1

Section 2: Source System Prerequisites & Restrictions The pre-requisite patch levels, configuration and restrictions to be confirmed before proceding further. Section 3: Target System Prerequisites Target system infrastructure which must be in place before attempts to lone 11i RAC with 10g or 11g DB. Section 4: Source System Technology Stack Archive Creation Creating an archive of the RAC enabled RDBMS $ORACLE_HOME. Section 5: Source System Database Image Creation Using RMAN on the Source RAC node to create an "image". Section 6: Target System Database Technology Stack Restore and Configuration Using RapidClone to configure the un-archived Target System Technology Stack Section 7: Target System Database Image Restore Using RMAN on the Target System to restore the original Database to this new host environment. Section 8: Target System Secondary Node Technology Stack Restore and Configuration Using RapidClone to configure the un-archived Secondary Target System Technology Stack Section 9: Applications Tier Cloning and Configuration Prepare Source Apps Node, copy to Target System Apps Node and run RapidClone. Appendix A: Example init.ora and listener.ora files To be used during Sections 7 and 8 restore and DB techstack configuration.

Conventions: Convention Source system Target system APPLMGR SOURCE System TARGET System ORACLE_HOME NEW_ORACLE_HOME ORACLE Meaning Applications system being cloned. Applications system being created as a copy of the source. User which owns the applications file system (APPL_TOP and application tier technology stack) The original RAC System which is to be cloned to new TARGET hosts. The new RAC System which will be created as a result of following the steps provided within this document. Refers to the SOURCE System $ORACLE_HOME Refers to the TARGET System new $ORACLE_HOME which will be created at the time of RAC node recovery and MUST be the same on each TARGET System node. User which owns the database file system (RDBMS ORACLE_HOME and database files). 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>.

CONTEXT_NAME

2 of 26

7/22/2010 1:51 PM

3 of 26 7/22/2010 1:51 PM . The source system must remain in a running and active state during database Image creation. Target System verification of pre-requisites (Cluster Manager. Do not type the angle brackets. Cloning Oracle Applications Release 11i with Rapid Clone. Substitute a value for the variable text. Autoconfig. Text enclosed in angle brackets represents a variable. shared disk access & user account setup) Target System Technology Stack cloning & configuration using RapidClone Target System configuration file adjustments Target System Database image restore via RMAN Secondary Target System node Technology Stack cloning & configuration using RapidClone Secondary Target System configuration file adjustments Running Autoconfig on Primary and Secondary Target System nodes Source to Target Applications Node cloning with RapidClone These steps will not necessarily be presented in the above order when detailed below.1.oracle. Section 1: Manual RAC Cloning Process Overview At a high level. as described in OracleMetaLink document 230672. Type this command exactly as shown.1 Monospace Text <> Represents command line text.1 Pre-Requisites: This document is only for use in RAC-To-RAC cloning of a source Oracle E-Business Suite Release 11i RAC system to a target Oracle E-Business Suite RAC system. Familiar with Oracle Database Server 10g. The steps described in this note are for use by accomplished Applications and Database Administrators. as well as the steps required to convert from a single instance Oracle E-Business Suite installation to a RAC-enabled one. Section 2: Source System Pre-requisites & Restrictions 2. Experienced in the use of of RapidClone. who should be: Familiar with the principles of cloning an Oracle E-Business Suite system.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support. the manual 11i RAC cloning with 10g or 11g detailed below is comprised of the following steps: Source System verification of pre-requisites and restrictions Source System preclone tasks using RapidClone Source System Technology Stack archive creation Source System datafile backup set (image) creation Transfer of Technology Stack archive and Database image files to target RAC nodes.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. and AD utilities. and have at least a basic knowledge of Oracle Real Application Clusters (Oracle RAC).

For proper CRS functionality. Details such as operating system configuration of mount points.3. ADX or TXK (AutoConfig) patches. the ORACLE_HOME(s) on the source system must be updated with the files included in those patches. At the conclusion of the cloning process.1 The addition of database RAC nodes (beyond the assumed secondary node) is.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support. Oracle Real Application Clusters Setup and Configuration Guide 10g Release 2 (10. from the RapidClone perspective. Contain the same number of redo log threads as the source system. It is assumed that the RDBMS $ORACLE_HOME (being of version 10g or 11g) already has been upgraded to contain Sun JRE 1. Warning: After applying any new Rapid Clone. During the cloning process. 2. the Clusterware software stack and cluster-specific configuration must be in place first. it must be done manually. NFS or other forms of clustered file systems are not covered in this document. Have all datafiles located under a single "DATA_TOP" location. Contain only a single control file. TXK and RapidClone patches (along with ALL necessary pre-requisite patches) as noted in within Section 1 of document 230672. subsection “Patching AutoConfig”. without any of the extra copies that the DBA typically expects.2) is a useful reference when planning to set up Oracle Real Application Clusters and shared devices. to allow RapidClone to configure the database technology stack properly. no allowance is made for the use of a Flash Recovery Area (FRA). It is required that the source system Application Node (Applications Middle Tier Node) be updated with the most current AD. and follow the instructions in section “System Configuration and Maintenance”. you should be aware of the following restrictions and limitations: This RAC-To-RAC cloning procedure may only be used on Oracle Database versions 10g and 11g The final cloned RAC environment (a. target system) will different from the source system in the following ways: Use the Oracle Managed Files option for datafile names. However.1.2 Restrictions: Before using RapidClone to create a clone of an Oracle E-Business Suite Release 11i RAC technology stack.1 or higher.1. If an FRA needs to be configured on the target system. AD.k. easily handled. ADX.a. To synchronize the Rapid Clone and AutoConfig files within the RDBMS ORACLE_HOME using the admkappsutil. Oracle Clusterware installation and component service registration are not covered in this document. installation and configuration of ASM.oracle. refer to OracleMetaLink Note 165195. you should create an spfile and locate it in a shared 4 of 26 7/22/2010 1:51 PM . Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12.pl utility.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. the final cloned Oracle RAC environment will use a pfile (parameter file) instead of an spfile. OCFS2.

3 level. 2. Verify Shared Mount Points or Disks Ensure that all shared disk sub-systems are fully and properly configured: they need to have adequate space. and update the version to match that of the source system database. Cluster Manager must also be patched to the 10.2.3. This is described in Oracle® Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide 10g Release 2 (10. without password prompting) between primary and secondary target Oracle RAC nodes. be writable by the future oracle software owner. Note: For detailed instructions regarding the installation and usage of Oracle’s Clusterware software as it relates to Oracle Real Applications Clusters. if the original source system database is 10.7. User Equivalence between Oracle RAC Nodes Set up ssh and rsh user equivalence (that is. and be accessible from both primary and secondary nodes.0.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. shared storage combinations not specifically mentioned in this the article are not guaranteed to work.0.2). Section 3: Target System Pre-requisites Target 11i RAC system configuration requirements: 1. While other certified clustered file systems should work for RAC-To-RAC cloning. only NetApp branded devices (certified NFS clustered file systems) have been confirmed to work at present.4. 3. and will therefore only be supported on a best-efforts basis. Besides ASM and OCFS2. with the required steps being listed in Section 2. 5 of 26 7/22/2010 1:51 PM . "Configuring SSH on All Cluster Nodes".oracle. Install Cluster Manager Install Oracle Cluster Manager.1 storage location that is accessible to both Oracle RAC nodes. see the following article: Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide10g Release 2 (10.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.2). For example.2.

sh cd $ORACLE_HOME/appsutil/scripts/<CONTEXT_NAME>/ perl adpreclone.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support. 4. refer to Linux OCFS . refer to Automatic Storage Management Technical Best Practices.oracle. For ASM best practices. Linux/NetApp RHEL/SUSE Setup Recommendations for NetApp Filer Storage contains details specific to Linux NFS mount options and please see Configuring Network Appliance's NetApp To Work With Oracle for details on where to find NetApp co-authored articles related to using NetApp-branded devices with Oracle products.1 Note: For details on configuring ASM. cd $ORACLE_HOME/appsutil/scripts/<CONTEXT_NAME>/ ./adautocfg.Best Practices. This should not be a problem if runcluvfy.sh from the Oracle Clusterware software stage area was executed without error prior to CRS installation.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. it is strongly recommended that a separate $ORACLE_HOME be installed for ASM management. Section 4: Source System Technology Stack Archive Creation 1.pl dbTier 6 of 26 7/22/2010 1:51 PM . OCFS. whatever the the location of your ASM listener configuration. Oracle Cluster File System User’s Guide contains details on installing and configuring OCFS2. and NFS with NetApp Filer. Note: For ASM target deployments. see the following articles: Oracle Database Administrator's Guide 10g Release 2(10. public and VIP (Clusterware) Interconnects. Verify Network Layer Interconnects Ensure that the network layer is properly defined for private. This listener name (LISTENER_<HOSTNAME>) will be specified and used later by AutoConfig for the RAC-enabled Oracle E-Business Suite database listener. For OCFS best practices. Run adutoconfig and adpreclone on all Database instances. and it is required to change the default listener configuration via the netca executable. The ASM default listener name (or service name) must not be of the form “LISTENER_<HOSTNAME>”.2) contains details on creating the ASM instances.

SQL>shutdown immediate Startup primary instance in mount mode.. please add them now. SQL>startup mount SQL>alter database archivelog.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. Section 5: Source System RAC Database Image Creation Source 11i RAC DB image creation: Turn on archive log mode if not already enabled. copy it to a safe location for transfer later. add the below parameters to the ifile. enabled archive logging.dbf' Set the parameter cluser_database=false in the primary instance pfile $ORACLE_HOME/dbs /init<instance1>. Using zip or tar. tar -cvzf racdb_techstack.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.ora cluster_database=false Shutdown all RAC instances gracefully.ora.).oracle. and then recreate the spfile on the shared storage area. Enable ARCHIVE LOG MODE in 10g or 11g (if not already enabled). This step is not optional as successful RAC Cloning depends with 11i and 10G DB requires the use of RMAN which will not be able to execute if ARCHIVE LOG MODE is not enabled before hand. These steps assume the use of a pfile. The database can remain up and active during this process. 1. Create an archive of the primary database instance $ORACLE_HOME technology stack. it will be necessary to first create a pfile from the existing spfile. 7 of 26 7/22/2010 1:51 PM . LOG_ARCHIVE_DEST_1='LOCATION=/<shared_storage or ASM +DISKGROUP>/<SID>/archivelog' LOG_ARCHIVE_FORMAT='%t_%s_%r. If using an spfile.tgz <DATABASE TOP LEVEL DIRECTORY> Once the archive of the database technology stack has been created. navigate to the database $ORACLE_HOME and then backup one directory (cd $ORACLE_HOME/. If the following parameters do not yet exist in the ifile $ORACLE_HOME/dbs/<sid>_hostname_ifile.1 2.

as follows: 8 of 26 7/22/2010 1:51 PM . do the following using SQL*Plus or RMAN to show the locations of the archive logs.ora.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. Edit the ifile $ORACLE_HOME/dbs/<sid>_hostname_ifile.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support. It will then be necessary to correct the RMAN archive log “manifest”.dbf' Start up the secondary nodes. you must ensure that RMAN has a properly maintained list of valid archive logs located exclusively in the shared storage area.oracle. To confirm RMAN knows only of your archive logs located on the shared disk storage area. SQL>startup 2. If using an spfile. Confirm the database controlfile(s) and archive log file locations on shared storage If the source system was not previously in archive log mode.1 SQL>alter database open. but it has recently been enabled. SQL>shutdown immediate Reset the parameter cluster_database=true in the primary instance pfile $ORACLE_HOME/dbs /init<instance1>. SQL>archive log list If the output shows a local disk location. or if the source system parameter ARCHIVE_LOG_LIST was at some point set to any local disk directory location. change this location appropriately. and it was already updated on the primary node. SQL>startup Confirm ARCHIVE LOG MODE is enabled: SQL>select log_mode from v$database. this step is not needed on the secondary nodes. and back up or relocated any archive log files to the shared storage area. cluster_database=true Start up the primary instance one last time for all required changes to take affect.ora on the secondary nodes. Shutdown primary instance again. LOG_ARCHIVE_DEST_1='LOCATION=/<shared_storage or ASM +DISKGROUP>/<SID>/archivelog' LOG_ARCHIVE_FORMAT='%t_%s_%r.

SQL>select 'exit' from dual. SQL>select 'backup as backupset tag ''RapidClone_RAC'' database format \ ''<your location>/data/stage/%U''. SQL>select 'configure maxsetsize to '||round((max(bytes)/1024/1024) + 200)||'m.' \ from dba_data_files. special mount option MUST be used depending on OS platform in order to successfully create a copy of the current controlfile via RMAN. SQL>select 'backup as backupset tag ''RapidClone_RAC'' archivelog all format \ ''<your location>/data/stage/%U''. assuming you have relocated or removed any locally stored archive logs. Create an RMAN backup of the running and accessible database as follows: Execute the following select statements as sysdba to build an RMAN backup script (each select should be on a single line): Note: On slower systems.' from dual.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.' \ from dual.oracle. It is essential to carry out the above steps (if applicable) before you continue with the Oracle E-Business Suite Release 11i RAC cloning procedure.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.1 RMAN>crosscheck archivelog all.ctl''.' from dual. you will need to correct the invalid or “expired” archive logs as follows: RMAN>delete expired archivelog all. SQL>select 'backup tag ''RapidClone_RAC'' as copy current controlfile format \ ''<your location>/data/stage/backup_controlfile.rman SQL>select 'configure device type disk parallelism 5 backup type to backupset. the parallelism number in the script below should be reduced. 3.' from dual. Review the output archive log file locations and. 9 of 26 7/22/2010 1:51 PM . Note: If <your location> as shown below is an NFS mount point. SQL>set echo off pages 0 feed off linesize 5000 TRIM on TRIMS on sqlp # SQL>spool <your location>/11i_10grac_backup.

log 5. In this directory. Choose a suitable location. There is no need to transfer the RMAN backup set files created above to any other target system nodes. place this software archive in the directory you wish.tgz) to the target nodes After the "stage" creation is completed.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. along with the "backup_controlfile. 4.oracle. The number of files present will depend on the source system configuration. Section 6: Target System Database Technology Stack Restore and Configuration 6. Execute the RMAN script to create a database "stage" or "image" rman target / nocatalog @<absolute path to script>/11i_10grac_backup. Create a pairsfile for new pimary target system node Create a simple text file named pairsfile. tar -xvzf racdb_techstack. you will find several 2GB (or larger) RMAN backup/image files. The same location or top level directories should be chosen to unarchive the technology stack into. Transfer the RMAN backup set files and the $ORACLE_HOME archive (racdb_techstack. These files will have names like "1jj9c44g_1_1".txt with your favorite editor with the contents as shown: s_undo_tablespace=UNDOTBS1 s_dbClusterInst=2 10 of 26 7/22/2010 1:51 PM .1 SQL>spool off.tgz 2.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support. These RMAN backup set files should be placed into a temporary holding area on ONLY the primary target node.1 Target 11i RAC DB Technology Stack Restore: 1. and rename the extracted top-level directory name to something meaningful on the new primary target system node. SQL>exit. Clone the primary source DB node to the new primary target system node. These files. navigate to <stage location>/data/stage. The source system $ORACLE_HOME archive should now be transferred to ALL secondary target system RAC nodes (to become instances) upon which you will be configuring the new RDBMS $ORACLE_HOME. This location will ultimately be removed after successful target instance creation.rman > 11i_10gRAC_backup.ctl". will need to be transferred to the primary target system upon which you wish to create the new primary Oracle RAC instance. Uncompress archived (tar'd or zip'd) ORACLE_HOME copied from the source system to the new primary target node.

pl utility as follows: perl adclonectx. Create Context File for primary target system node Execute the following command to create a new context file. Do you want to use a virtual hostname for the target node (y/n) [n] ?:n Target hostname [stargate]:sg1 11 of 26 7/22/2010 1:51 PM .xml> \ template=<NEW ORACLE_HOME>/appsutil/template/adxdbctx.txt \ Where: Parameter contextfile template pairsfile Usage Full Path to the old Source RAC Database Context File.pl \ contextfile=<PATH to ORIGINAL Source RAC contextfile. Full Path to the existing Database Context file template. additional undo tablespaces and log threads must be added manually. In order to avoid potential confusion. Note: Adding (scaling-up) or removing (scaling-down) the number database instances is not covered in this document at this time.1 s_db_oh=<new_oh_loc> Where s_undo_tablespace represents the initial target system undo tablespace and where s_dbClusterInst represents the total number of instances present in the cluster. you will be present with the following questions [sample answers provided]: Provide the values required for creation of the new Database Context file. When cloning a source 11i E-Business Suite with 10g (or 11g) RAC enabled. provide careful answers to the prompted questions: Navigate to <NEW_ORACLE_HOME>/appsutil/clone/bin.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.oracle.tmp \ pairsfile=<NEW ORACLE_HOME>/appsutil/clone/pairsfile. This new text file file should be placed into the <NEW_ORACLE_HOME>/appsutils/clone location. as an example. 3. Run the adclonectx.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. the source and target system must have the same number of database instances other wise. Full Path to the pairsfile created on last step. These two parameters values will need to be altered on secondary nodes but can not be different values from those present on the source system RAC environment.

-If cloning a context on a machine where the ports are taken and you do not \ want to shutdown the services at this point. Do you want the inputs to be validated (y/n) [n] ?: Target instance is a Real Application Cluster (RAC) instance (y/n) [y]: Current node is the first node in an N Node RAC Cluster (y/n)[n]:y Target System database name [prod]:thor Do you want to preserve the port values from the source system on the target \ system (y/n) [y] ?:n Clone Context uses the same port pool mechanism as the Rapid Install Enter the port pool number [0-99]: 67 Database port is 1588 Provide information for the Node 1 (current node): Host name [stargate]:sg1 Virtual Host name [null]:sg1-vip Instance number [1]: Private interconnect name [stargate]:sg1-priv Provide information for the Node 2: Host name [asgard]:alphasite Virtual Host name [null]:alphasite-vip Instance number [2]: Private interconnect name [asgard]:alphasite-priv 12 of 26 7/22/2010 1:51 PM . However you might choose not to validate your inputs under following \ circumstances: -If cloning a context on source system for a remote system.oracle. -If cloning a context but the database it needs to connect is not available.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.1 It is recommended that your inputs are validated by the program.

Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support. database name.0/db_1/appsutil/outbound/prod_rac]: /usr/tmp Number of DATA_TOP's on the target system [3]:1 Target system DATA_TOP 1:/knowledge_repository Do you want to preserve the Display set to :0. that any path differences between the Source and Target Systems are understood and accounted for. Edit the newly generated contextfile.oracle. if uncertain. \ /u01/app/oracle/product/10.1 Target system quorum disk location required for cluster manager and node monitor \ []:/foo Target system cluster manager service port [9998]: Oracle OS User [fifthrace]: Oracle OS Group [alliance]: Target system utl_file accessible directories list [/usr/tmp. Please be sure if comparisons are made.xml (of the form <newsid_hostname>.2. 4.0 (y/n) [y] ?: Perl executable location is set to: /usr/bin/perl New context path and file name [/s1/asgard_homeworld/racdb/appsutil/thor1_sg1.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.tmp Note: It is of critical importance that the correct values are selected above.xml]: Creating the new Database Context file from : /s1/asgard_homeworld/racdb/appsutil/template/adxdbctx. and names as shown: s_instLocalListener value should be LISTENER_<NEW_SID> s_instRemoteListener value should be LISTENERS_<GLOBAL_DBNAME> s_dbGlnam value should be <GLOBAL DBNAME> and not a sid name 13 of 26 7/22/2010 1:51 PM ./usr/tmp. carefully review the newly written context file and compare it with values selected during the Source System migration to RAC (as per OracleMetalink Note 362135.1).xml) to review or change the following remote and local listener.

Run the adclone. init<NEW_SID>. The file should be placed into the <NEW_ORACLE_HOME>/dbs directory and contain the values as shown in the example file in Appendix A below.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. perl adclone.loc in the target system $ORACLE_HOME Create a directory under the $ORACLE_HOME location to store inventory information. 4.ora. Carefully review the newly generated configuration files for any potential inconsistencies.pl \ java=<NEW_ORACLE_HOME>/appsutil/clone/jre> \ component=dbTechStack \ mode=apply \ stage=<NEW_ORACLE_HOME>/appsutil/clone \ method=CUSTOM \ dbctxtg=<Full Path to the new Target Context Files> \ showProgress contextValidated=true 3.oracle.ora Confirm the desired control file name and location. cd <NEW_ORACLE_HOME>/ mkdir oraInventory Create or update the existing oraInst.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.tmp file This init<NEW_SID>. correct these values within the context file and again run adclone.tmp will be used only during the RMAN restore in Section 7 below.ora file may require adjustment depending on the target system database size and available host resources. Edit the oraInst.ora <NEW_SID>_APPS_BASE.1 6. The values within the temporary init. Create a temporary init<NEW_SID>.ora. 14 of 26 7/22/2010 1:51 PM .loc file in the target system $ORACLE_HOME with the following: inventory_loc=<NEW_ORACLE_HOME>/oraInventory inst_group=<dba group> 2.2 Target 11i RAC DB Technology Stack Configuration: 1. If changes are required.pl to propagate the required values to the associated configuration files.pl utility as follows: Navigate to <NEW_ORACLE_HOME>/appsutil/clone/bin.

' from v$datafile. select 'set newname for tempfile '||file#||' to NEW. but will be modified and used in subsequent steps.ctl'. non-temporary init<new_sid>.' from v$tempfile.' from dual.1 Restore Control File 1.rman startup nomount pfile=<NEW_ORACLE_HOME>/dbs/init<NEW_SID>. alter database mount. Create a sql script which will build the main RMAN script to restore the database.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.ora. File contents of restore-rac2. Create an RMAN script to restore the control file onto target system File contents of restore-rac1.' from dual.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. select 'restore database.1 Note: Be certain to keep and maintain the recently generated. Section 7: Target System Database Image Restore 7.sql connect / as sysdba set echo off pages 0 feed off sqlp # spool restore-rac2. select 'set newname for datafile '||file#||' to NEW.rman select 'catalog start with ''<Temporary Stage Area>'' NOPROMPT. The generated init<new_sid>.ora file will not immediately be used during the RMAN restore process. 15 of 26 7/22/2010 1:51 PM .ora file located in the Target System $ORACLE_HOME/dbs direcotry.tmp restore controlfile from '<Temporary Stage Area>/data/stage/backup_controlfile. rman target / nocatalog @restore-rac1. Please do not confuse the generated and tempoary init.rman > restore-rac1.oracle.log 7.2 Restore Database 1. Run the control file restore script. exit 2.ora files during the RMAN processes to come in Section 7 below. select 'RUN { ' from dual.

sqlplus "/as sysdba" @restore-rac-logfile. shutdown and startup the restored database. select '} ' from dual. sqlplus "/as sysdba" @restore-rac21. Run the script restore-rac-logfile.rman sqlplus "/as sysdba" @restore-rac2. select 'switch tempfile all. Run the sql script which will build restore-rac2. rman target / nocatalog @restore-rac2.rman > restore-rac2.' from dual.sql 7. select 'recover database. spool off exit 5. File contents of restore-rac3. 4.rman alter database open resetlogs. spool off exit 2. select 'exit' from dual.sql 3. File contents of restore-rac21.' from dual.sql connect / as sysdba set echo off pages 0 feed off linesize 5000 TRIM on TRIMS on sqlp # spool restore-rac-logfile. Create the following RMAN script to reset the logs. Run the main database restore script.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.' from dual. 16 of 26 7/22/2010 1:51 PM .Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.sql.sql. Run the script restore-rac21. select 'alter database rename file '''||member||''' to '||'''<shared_storage_loc>/datafile/'|| REGEXP_REPLACE(''||member||''.oracle. they can be safely ignored. Create a sql script which will build another sql script to rename the DB log files. select 'exit' from dual.log If RMAN-03002 and RMAN-06054 errors are present.'.sql 6.1 select 'switch datafile all.sql select 'connect /as sysdba' from dual.' from v$logfile.sql This script will create another script named restore-rac-logfile.*/') ||'''.

rman > restore-rac3.tmp. if the db_name parameters value was db_name=TEST and the new target system global database name is PRODCRP.5 Open Database and reset the log files. Note: Do not shutdown or restart the Database. rman target / nocatalog @restore-rac3.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.3 Change the DBNAME and DBID Note: After this step. Run the final RMAN restore scripts. the restored database will be shutdown.oracle. EOF 7. 7.tmp prior to renaming the DBID and DBNAME in the next step.ora. rman target / <<EOF startup mount pfile=<NEW_ORACLE_HOME>/dbs/init<NEW_SID>. For example.tmp file used during the earlier steps of the RMAN restore as follows: Change the db_name value FROM the Source System Global Database Name TO the new Target System Global Database Name.log 9. nid target=/ dbname=<new target db_name as defined in new context file> 7.tmp EOF 7.ora.1 shutdown normal startup mount pfile=<NEW_ORACLE_HOME>/dbs/init<NEW_SID>.3 after making the db_name parameter change in the temporary init.ora.6 Modify the <NEW_SID>_APPS_BASE. the db_name=PRODCRP should be the value present in the temporary init<NEW_SID>.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. temporary init<NEW_SID>. Make certain to provide the full path to the restored control file and it's new name 17 of 26 7/22/2010 1:51 PM . you must update this parameters as it currently exists within the <NEW_SID>_APPS_BASE.tmp 8.ora file and correct the control_file parameter value. Edit the hand made.ora.4 Restart Database for first time after name and id change.ora. sqlplus or rman can be used here: rman target / <<EOF alter database open resetlogs. Modify the temporary init<NEW_SID>.ora file before the Database is shutdown and restarted in the following step. procede to step 7. Because Autoconfig does not allow for values to be directly specified for the control_files location.ora.

9 Create a temporary listener. Source the newly generate environment file in the <NEW_ORACLE_HOME> directory.10 Start the newly defined listener and run Autoconfig 1.7 Shutdown and restart the Database to begin using the Autoconfig generated configuration files.oracle. With the configuration files updated. This tempoary listener. <new_sid>_<hostname>.1 (if applicable).ora files. cd <NEW_ORACLE_HOME> .Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support. the database restored and renamed.ora file will be used only during Autoconfig such that connectivity to the newly restored and renamed target system database instance can be connected to updated with appropriate node information as well as to generate proper RAC specific listener.SETUP_CLEAN 7. The listener.ora and tnsnames.ora file should be placed into the <NEW_ORACLE_HOME>/network/admin/<CONTEXT_NAME> directory and contain the values as shown in the example file in Appendix A below.env 18 of 26 7/22/2010 1:51 PM .com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. 7. and other source system specific data which remain in the newly cloned and renamed database Execute the following package to clean up legacy source system information: sqlplus apps/<passwd> exec FND_CONC_CLONE.8 Clean up legacy System Level profile options. sqlplus or rman can be used here: rman target / <<EOF shutdown immediate EOF sqlplus or rman can be used here: rman target / <<EOF startup EOF 7. we need to do a shutdown and startup to cut over to using the proper configuration files. WF data.ora file to be used during Autoconfig execution in the next step. 7.

ora generated from Autoconfig contains an ifile parameter.tgz 8. and rename the extracted top-level directory name to something meaningful which matches the location and naming convention chosen on the primary target system node. Inspect the following files to confirm expected values are present./adautocfg. After validating the configuration files and starting and stopping the instance and listener several times to confirm expected operation.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.ctl' from \ pfile='<NEW_ORACLE_HOME>/dbs /init<NEW_SID>. cd $ORACLE_HOME/appsutil/scripts/<context_name>/ .2 Create a pairsfile for new secondary target system node Create a simple text file named pairsfile. init<NEW_SID>.sh 4.11 Create an spfile on the shared storage location if desired.1 Clone the primary source DB node to the new secondary target system node. Choose a suitable location. lsnrctl start listener_<hostname> 3. Remeber that the current init. Confirm no errors occurred during Autoconfig execution by reviewing the provided log.1 2. 5. If you wish to use archive logging. Run Autoconfig.ora tnsnames. create an spfile from the pfile(s) current being used. enable such parameters in the ifile before creating the spfile. tar -xvzf racdb_techstack.ora <NEW_SID>_APPS_BASE.ora 7. Uncompress archived (tar'd or zip'd) ORACLE_HOME copied from the source system to this new secondary target node(s).Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.txt with your favorite editor with the contents as shown: 19 of 26 7/22/2010 1:51 PM . Start the TNS Listener created by hand from the provided example in Appendix A.ora' Section 8: Target System Secondary Node Technology Stack Restore & Configuration Target 11i RAC DB Technology Stack Restore [Secondary Nodes]: 8. SQL>create pfile='<shared storage loc>/spfile_<global_dbname>.ora listener.oracle.

8. Answer the presented prompts as in done earlier in Section 7 above. carefully review the newly written context file and compare it with values selected during the primary target instance context file generation.tmp \ pairsfile=<NEW ORACLE_HOME>/appsutil/clone/pairsfile. Run the adclonectx.3 Create Context File for secondary target system node Execute the following command to create a new context file.xml> \ template=<NEW ORACLE_HOME>/appsutil/template/adxdbctx. Full Path to the pairsfile created on last step. making allowances for the fact that this is the secondary instance and a different hostname and instance #. Note: It is of critical importance that the correct values are during the context file interview phase.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.xml (of the form <newsid_hostname>.4 Edit the newly generated contextfile. 8.pl \ contextfile=<PATH to Target System Primary RAC Node contextfile. This new text file file should be placed into the <NEW_ORACLE_HOME>/appsutil/clone location. and names as shown: s_instLocalListener value should be LISTENER_<NEW_SID> s_instRemoteListener value should be LISTENERS_<GLOBAL_DBNAME> s_dbGlnam value should be <GLOBAL DBNAME> and not a sid name 20 of 26 7/22/2010 1:51 PM . provide careful answers to the prompted questions: Navigate to <NEW_ORACLE_HOME>/appsutil/clone/bin.oracle. Please be sure if comparisons are done. database name.1 s_undo_tablespace=UNDOTBS2 s_dbClusterInst=2 s_db_oh=<NEW_ORACLE_HOME> Where s_undo_tablespace represents the secondary target instance undo tablespace and where s_dbClusterInst represents the total number of instances present in the cluster.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.txt \ Where: Parameter contextfile template pairsfile Usage Full Path to the old Source RAC Database Context File. that path differences between the primary target instance and secondary target instance are accounted for.pl utility as follows: perl adclonectx. Full Path to the existing Database Context file template.xml) to review or change the following remote and local listener. if uncertain about what values to provide.

Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support. The listener. 8. Source the newly generate environment file in the <NEW_ORACLE_HOME> directory. <new_sid>_<hostname>. Start the TNS Listener created by hand from the provided example in Appendix A.ora file and correct the control_file parameter value.ora file should be placed into the <NEW_ORACLE_HOME>/network/admin /<CONTEXT_NAME> directory and contain the values as shown in the example file in Appendix A below.oracle. 1. cd <NEW_ORACLE_HOME> .com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.6 Create a temporary listener.ora files. Because Autoconfig does not allow for values to be directly specified for the control_files location.env 2. you must update this parameters as it currently exists within the <NEW_SID>_APPS_BASE. perl adclone.ora file will be used only during Autoconfig such that connectivity to the newly restored and renamed target system database instance can be connected to updated with appropriate node information as well as to generate proper RAC specific listener. 8. Modify the <NEW_SID>_APPS_BASE.pl utility as follows: Navigate to <NEW_ORACLE_HOME>/appsutil/clone/bin.8 Run Autoconfig.ora file before the Database can be started in the following step.pl \ java=<NEW_ORACLE_HOME>/appsutil/clone/jre> \ component=dbTechStack \ mode=apply \ stage=<NEW_ORACLE_HOME>/appsutil/clone \ method=CUSTOM \ dbctxtg=<Full Path to the new Target Context Files> \ showProgress contextValidated=true 8. Execute Autoconfig.1 8.ora file to be used during Autoconfig execution in the next steps. Make certain to provide the full path to the restored control file as it exists on the shared storage location.5. This tempoary listener. 21 of 26 7/22/2010 1:51 PM . 1.7 Start the newly defined listener and start the secondary instance.ora and tnsnames. Run the adclone. lsnrctl start listener_<hostname> 3.

Inspect the following files to confirm expected values are present./adautocfg.ora <NEW_SID>_APPS_BASE. you must repeat Sections 8.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.3 for all subsequent nodes. Confirm no errors occurred during Autoconfig execution by reviewing the provided log. 3.ora tnsnames. such that listener load balancing can occur.ora (as the FND_NODES table did not contain the second node hostname until AutoConfig was run on the secondary target RAC node). Section 9: Applications Tier Cloning and Configuration The target system Applications Tier may be located in any one of these locations: 22 of 26 7/22/2010 1:51 PM .ora.9 Carry Out Target System (Primary Node) Final Oracle RAC Configuration Tasks Recreate TNSNAMES and LISTENER.ora 8.ora and tnsnames. cd $ORACLE_HOME/appsutil/scripts/<CONTEXT_NAME> .sh 2.sh Note: This execution of AutoConfig on the primary target RAC Node 1 will add the second RAC Node connection information to the first node's tnsnames. Login again to the target primary node (Node 1) and run AutoConfig to perform the final Oracle RAC configuration and create new listener.ora listener.2 and 8. If you have more than two nodes in your new target system cluster.oracle. init<NEW_SID>.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.1 cd $ORACLE_HOME/appsutil/scripts/<context_name>/ .ORA again on the primary target node./adautocfg.

context variable changes can be made such that JDBC and TNS Listener load balancing are enabled.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637. Appendix A: Example init.1 Primary target database node Secondary target database node An independent machine.1 Clone the Applications Tier In order to clone the applications tier. Cloning Oracle Applications Release 11i with Rapid Clone.1.ora. Please refer to OracleMetaLink document 362135. and you should be able to log in and use the new target system Applications system. Note: Only after successfully associating the new Target System Application Node / Tier with one of the two Target System database instances. you will be asked for a database to which the applications tier services should connect to.ora file The below temporary init<new_sid>. section 3. the applications node services will be started. 9. Be sure to read the comments in this sample files before 23 of 26 7/22/2010 1:51 PM . and finishing tasks steps. should SQL*Net and JDBC Listener Load Balancing be attempted.ora and listener. it is strongly suggested that the applications tier should initially be configured to connect to a single database instance.11 for specific details on how to enables JDBC and SQL*Net Listener Load Balancing for the 11i Applications Node in a RAC enabled environment. After proper configuration with one of the two target system RAC nodes has been achieved.2 Configure Application Tier JDBC and Listener Load Balancing Reconfigure the applications node context variables such that database listener/instance load balancing can occur. Enter the information specific to a single target system RAC node (such as the primary node). running neither of the target system RAC nodes Shared between two or more machines Because of the complexities which might arise.1.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support. during the adcfgclone.tmp file should be used only during Section 7: Target System Database Image Restore on the primary target node during RMAN restore. 9. follow the standard steps for the applications node posted on Sections 2 OracleMetalink document 230672. Note: On the applications tier. configuration portion. This includes adpreclone steps. copy the bits to the target.pl execution. On successful completion of this step.oracle.

. set to appropriate value as needed sga_target=1g ## Tempoary SGA MAX size.ctl ## Tempoary SGA TARGET size.. accessible from both RAC nodes db_recovery_file_dest=+ASM_DSKGRP1 ## The amount of space available for RMAN to use to write archive logs ## Set to a more appropriate value as needed db_recovery_file_dest_size=300g ## The location & name to which the "new" Target System control file ## will be restored to...0 The below tempoary listener.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.ora.. +ASM_DISK_GROUP.1. db_create_file_dest=+ASM_DSKGRP1 ## RMAN will place the archive logs in this location and it should be ## located on shared storage.must be on shared ## storage location access by both Target System RAC nodes control_files=+ASM_DSKGRP1/<UPPER_CASE_NEWGLDB/controlfile_<NEWGLDB>.1 choosing appropriate values.NOT A SID NAME db_unique_name=NEWGLDB ## The number of DB files available to RMAN. set to appropriate value db_files = 4096 ## The location to which the shared dbf (datafiles) will be written.Set to desired location.. set to appropriate value as needed sga_max_size=2g ## Tempoary number for OPEN CURSORS.NOT A SID NAME db_name=OLDGLDB ## New Target System Global Database Name... Temporary init<new_sid>. NFS or OCFS disks ## Note that RMAN will create a sub-directory under this location with the ## NEW GLOBAL Database name in UPPER case.ora should be used only during Section 7: Target System Database Image Restore on the primary target node during Autoconfig. set to appropriate value as needed open_cursors=1000 ## Parameter should ONLY be present when DB Version is 11g.tmp contents: ## Source System Global Database Name.. Temporary listener.ora content: LISTENER_<hostname> = (DESCRIPTION_LIST = (DESCRIPTION = 24 of 26 7/22/2010 1:51 PM .DO NOT ## USE THIS PARAMETER if DB Version is 10g!! compatible=11..oracle. This ## location should be the mount point to which both target RAC nodes can ## read and write file to.

2009 March 25. 2009 Jan 20. Several small formatting changes and elaboration of provided commands Minor syntax corrections and additions to Conventions table Publishing Review Initial Posting 25 of 26 7/22/2010 1:51 PM . 2009 Mar 07. 2009 Mar 16.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support.com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.1 (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = <context value for s_virtual_hostname>)(PORT = <context value for s_dbport>)(IP = FIRST))) (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = <context value for s_dbport>)(IP = FIRST))) (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC<new_sid>))) ) ) SID_LIST_LISTENER_<hostname> = (SID_LIST = (SID_DESC = (ORACLE_HOME = <NEW_DATABASE_HOME>)(SID_NAME = <new_sid>)) (SID_DESC = (SID_NAME = PLSExtProc)(ORACLE_HOME = <NEW_DATABASE_HOME>)(PROGRAM = extproc)) ) STARTUP_WAIT_TIME_LISTENER_<hostname> = 0 CONNECT_TIMEOUT_LISTENER_<hostname> = 10 TRACE_LEVEL_LISTENER_<hostname> = OFF LOG_DIRECTORY_LISTENER_<hostname> = <NEW_DATABASE_HOME>/network/admin LOG_FILE_LISTENER_<hostname> = <new_sid> TRACE_DIRECTORY_LISTENER_<hostname> = <NEW_DATABASE_HOME>/network/admin TRACE_FILE_LISTENER_<hostname> = <new_sid> ADMIN_RESTRICTIONS_LISTENER_<hostname> = OFF Change Log Date April 01.oracle. 2009 Description Clarifications in preparation for GA as provided by members of OSS & first hand testing.

1 Nov 09. 2008 First Draft Note 760637.oracle.1 by Oracle Applications Development Copyright © 2009 Oracle Corporation Last updated: March 10.Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC https://support. 2009 Related Products Oracle E-Business Suite > Applications Technology > Lifecycle Management > Oracle Applications Manager Keywords EBS Back to top 26 of 26 7/22/2010 1:51 PM .com/CSP/main/article?cmd=show&type=NOT&doctype=KB&id=760637.

Sign up to vote on this title
UsefulNot useful