manually cloning oracle applications release 11i with 10g or 11g rac [id 760637.1]

Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC [ID 760637.1]

Modified 01-APR-2009 Type WHITE PAPER Status PUBLISHED

View Change log

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 enabledto utilize the RAC option. For 11i with 9i RAC, please see the Advanced Cloning section of document230672.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 configuredto use the Real Applications Cluster option present in Oracle Database versions 10g and 11g . The most currentversion of this note is document 760637.1 on OracleMetaLink. A FAQ is also available in document 216664.1 onOracleMetaLink.

Note: Rapid Clone is currently not supported on Windows Itanium, Windows x86-64 (EM64T) and HP OpenVMSAlpha.

Attention: Windows users. This document typically uses UNIX syntax when specifying directories; Please substitutethe appropriate Windows syntax

Section 1: Manual RAC Cloning Process OverviewOutline of steps which are detailed further within this document

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

1 of 26 7/22/2010 1:51 PM

Section 2: Source System Prerequisites & RestrictionsThe pre-requisite patch levels, configuration and restrictions to be confirmed before proceding further.Section 3: Target System PrerequisitesTarget 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 CreationCreating an archive of the RAC enabled RDBMS $ORACLE_HOME.Section 5: Source System Database Image CreationUsing RMAN on the Source RAC node to create an "image".Section 6: Target System Database Technology Stack Restore and ConfigurationUsing RapidClone to configure the un-archived Target System Technology StackSection 7: Target System Database Image RestoreUsing 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 ConfigurationUsing RapidClone to configure the un-archived Secondary Target System Technology StackSection 9: Applications Tier Cloning and ConfigurationPrepare Source Apps Node, copy to Target System Apps Node and run RapidClone.Appendix A: Example init.ora and listener.ora filesTo be used during Sections 7 and 8 restore and DB techstack configuration.

Conventions:

Convention Meaning

Source system Applications system being cloned.

Target system Applications system being created as a copy of the source.

APPLMGRUser which owns the applications file system (APPL_TOPand application tier technology stack)

SOURCE SystemThe original RAC System which is to be cloned to newTARGET hosts.

TARGET SystemThe new RAC System which will be created as a result offollowing the steps provided within this document.

ORACLE_HOME Refers to the SOURCE System $ORACLE_HOME

NEW_ORACLE_HOMERefers to the TARGET System new $ORACLE_HOMEwhich will be created at the time of RAC node recovery andMUST be the same on each TARGET System node.

ORACLEUser which owns the database file system (RDBMSORACLE_HOME and database files).

CONTEXT_NAME

The CONTEXT_NAME variable refers to the name of theApplications Context file. For systems installed with RapidInstall 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>.


2 of 26 7/22/2010 1:51 PM

Monospace TextRepresents command line text. Type this command exactlyas shown.

< >Text enclosed in angle brackets represents a variable.Substitute a value for the variable text. Do not type theangle brackets.

Section 1: Manual RAC Cloning Process Overview

At a high level, the manual 11i RAC cloning with 10g or 11g detailed below is comprised of the following steps:

Source System verification of pre-requisites and restrictionsSource System preclone tasks using RapidCloneSource System Technology Stack archive creationSource System datafile backup set (image) creationTransfer of Technology Stack archive and Database image files to target RAC nodes.Target System verification of pre-requisites (Cluster Manager, shared disk access & user account setup)Target System Technology Stack cloning & configuration using RapidCloneTarget System configuration file adjustmentsTarget System Database image restore via RMANSecondary Target System node Technology Stack cloning & configuration using RapidCloneSecondary Target System configuration file adjustmentsRunning Autoconfig on Primary and Secondary Target System nodesSource to Target Applications Node cloning with RapidClone

These steps will not necessarily be presented in the above order when detailed below.

Section 2: Source System Pre-requisites & Restrictions

2.1 Pre-Requisites:

This document is only for use in RAC-To-RAC cloning of a source Oracle E-Business Suite Release 11i RACsystem to a target Oracle E-Business Suite RAC system.The steps described in this note are for use by accomplished Applications and Database Administrators, whoshould be:

Familiar with the principles of cloning an Oracle E-Business Suite system, as described inOracleMetaLink document 230672.1, Cloning Oracle Applications Release 11i with Rapid Clone.Familiar with Oracle Database Server 10g, and have at least a basic knowledge of Oracle RealApplication Clusters (Oracle RAC).Experienced in the use of of RapidClone, Autoconfig, and AD utilities, as well as the steps required toconvert from a single instance Oracle E-Business Suite installation to a RAC-enabled one.

The source system must remain in a running and active state during database Image creation.


3 of 26 7/22/2010 1:51 PM

The addition of database RAC nodes (beyond the assumed secondary node) is, from the RapidCloneperspective, easily handled. However, the Clusterware software stack and cluster-specific configuration mustbe in place first, to allow RapidClone to configure the database technology stack properly.Details such as operating system configuration of mount points, installation and configuration of ASM, OCFS2,NFS or other forms of clustered file systems are not covered in this document.Oracle Clusterware installation and component service registration are not covered in this document.Oracle Real Application Clusters Setup and Configuration Guide 10g Release 2 (10.2) is a useful referencewhen planning to set up Oracle Real Application Clusters and shared devices.

It is required that the source system Application Node (Applications Middle Tier Node) be updated with the mostcurrent AD, ADX, TXK and RapidClone patches (along with ALL necessary pre-requisite patches) as noted in withinSection 1 of document 230672.1.

It is assumed that the RDBMS $ORACLE_HOME (being of version 10g or 11g) already has been upgraded to containSun JRE 1.3.1 or higher.

Warning: After applying any new Rapid Clone, AD, ADX or TXK (AutoConfig) patches, the ORACLE_HOME(s) on the

source system must be updated with the files included in those patches.

To synchronize the Rapid Clone and AutoConfig files within the RDBMS ORACLE_HOME using the admkappsutil.pl

utility, refer to OracleMetaLink Note 165195.1, Using AutoConfig to Manage System Configurations in Oracle E-Business

Suite Release 12, and follow the instructions in section “System Configuration and Maintenance”, subsection “Patching

AutoConfig”.

2.2 Restrictions:

Before using RapidClone to create a clone of an Oracle E-Business Suite Release 11i RAC technology stack, youshould be aware of the following restrictions and limitations:

This RAC-To-RAC cloning procedure may only be used on Oracle Database versions 10g and 11gThe final cloned RAC environment (a.k.a. target system) will different from the source system in the followingways:

Use the Oracle Managed Files option for datafile names.Contain the same number of redo log threads as the source system.Have all datafiles located under a single "DATA_TOP" location.Contain only a single control file, without any of the extra copies that the DBA typically expects.

During the cloning process, no allowance is made for the use of a Flash Recovery Area (FRA). If an FRA needsto be configured on the target system, it must be done manually.At the conclusion of the cloning process, the final cloned Oracle RAC environment will use a pfile (parameterfile) instead of an spfile. For proper CRS functionality, you should create an spfile and locate it in a shared


4 of 26 7/22/2010 1:51 PM

storage location that is accessible to both Oracle RAC nodes.Besides ASM and OCFS2, only NetApp branded devices (certified NFS clustered file systems) have beenconfirmed to work at present. While other certified clustered file systems should work for RAC-To-RAC cloning,shared storage combinations not specifically mentioned in this the article are not guaranteed to work, and willtherefore only be supported on a best-efforts basis.

Section 3: Target System Pre-requisites

Target 11i RAC system configuration requirements:

1. User Equivalence between Oracle RAC Nodes

Set up ssh and rsh user equivalence (that is, without password prompting) between primary and secondary targetOracle RAC nodes. This is described in Oracle® Database Oracle Clusterware and Oracle Real Application ClustersInstallation Guide 10g Release 2 (10.2), with the required steps being listed in Section 2.4.7, "Configuring SSH on AllCluster Nodes".

2. Install Cluster Manager

Install Oracle Cluster Manager, and update the version to match that of the source system database. For example, ifthe original source system database is 10.2.0.3, Cluster Manager must also be patched to the 10.2.0.3 level.

Note: For detailed instructions regarding the installation and usage of Oracle’s Clusterware software as it relates toOracle Real Applications Clusters, see the following article: Oracle Database Oracle Clusterware and Oracle RealApplication Clusters Administration and Deployment Guide10g Release 2 (10.2).

3. Verify Shared Mount Points or Disks

Ensure that all shared disk sub-systems are fully and properly configured: they need to have adequate space, bewritable by the future oracle software owner, and be accessible from both primary and secondary nodes.


5 of 26 7/22/2010 1:51 PM

Note: For details on configuring ASM, OCFS, and NFS with NetApp Filer, see the following articles:

Oracle Database Administrator's Guide 10g Release 2(10.2) contains details on creating the ASMinstances. For ASM best practices, refer to Automatic Storage Management Technical Best Practices. Oracle Cluster File System User’s Guide contains details on installing and configuring OCFS2. ForOCFS best practices, refer to Linux OCFS - Best Practices. Linux/NetApp RHEL/SUSE Setup Recommendations for NetApp Filer Storage contains details specificto Linux NFS mount options and please see Configuring Network Appliance's NetApp To Work WithOracle for details on where to find NetApp co-authored articles related to using NetApp-brandeddevices with Oracle products.

Note: For ASM target deployments, it is strongly recommended that a separate $ORACLE_HOME be installedfor ASM management, whatever the the location of your ASM listener configuration, and it is required tochange the default listener configuration via the netca executable.The ASM default listener name (or service name) must not be of the form “LISTENER_<HOSTNAME>”. Thislistener name (LISTENER_<HOSTNAME>) will be specified and used later by AutoConfig for the RAC-enabledOracle E-Business Suite database listener.

4. Verify Network Layer Interconnects

Ensure that the network layer is properly defined for private, public and VIP (Clusterware) Interconnects. This shouldnot be a problem if runcluvfy.sh from the Oracle Clusterware software stage area was executed without error prior toCRS installation.

Section 4: Source System Technology Stack Archive Creation

1. Run adutoconfig and adpreclone on all Database instances.

cd $ORACLE_HOME/appsutil/scripts/<CONTEXT_NAME>/

./adautocfg.sh

cd $ORACLE_HOME/appsutil/scripts/<CONTEXT_NAME>/

perl adpreclone.pl dbTier


6 of 26 7/22/2010 1:51 PM

2. Create an archive of the primary database instance $ORACLE_HOME technology stack.

Using zip or tar, navigate to the database $ORACLE_HOME and then backup one directory (cd$ORACLE_HOME/..). The database can remain up and active during this process.

tar -cvzf racdb_techstack.tgz <DATABASE TOP LEVEL DIRECTORY>

Once the archive of the database technology stack has been created, copy it to a safe location for transferlater.

Section 5: Source System RAC Database Image Creation

Source 11i RAC DB image creation:

Turn on archive log mode if not already enabled. This step is not optional as successful RAC Cloning depends with 11iand 10G DB requires the use of RMAN which will not be able to execute if ARCHIVE LOG MODE is not enabledbefore hand.

1. Enable ARCHIVE LOG MODE in 10g or 11g (if not already enabled).

If the following parameters do not yet exist in the ifile $ORACLE_HOME/dbs/<sid>_hostname_ifile.ora,please add them now.

These steps assume the use of a pfile. If using an spfile, it will be necessary to first create a pfile fromthe existing spfile, add the below parameters to the ifile, enabled archive logging, and then recreate thespfile on the shared storage area.

LOG_ARCHIVE_DEST_1='LOCATION=/<shared_storage or ASM +DISKGROUP>/<SID>/archivelog'

LOG_ARCHIVE_FORMAT='%t_%s_%r.dbf'

Set the parameter cluser_database=false in the primary instance pfile $ORACLE_HOME/dbs/init<instance1>.ora

cluster_database=false

Shutdown all RAC instances gracefully.

SQL>shutdown immediate

Startup primary instance in mount mode.

SQL>startup mountSQL>alter database archivelog;


7 of 26 7/22/2010 1:51 PM

SQL>alter database open;

Shutdown primary instance again.

SQL>shutdown immediate

Reset the parameter cluster_database=true in the primary instance pfile $ORACLE_HOME/dbs/init<instance1>.ora.

cluster_database=true

Start up the primary instance one last time for all required changes to take affect.

SQL>startup

Confirm ARCHIVE LOG MODE is enabled:

SQL>select log_mode from v$database;

Edit the ifile $ORACLE_HOME/dbs/<sid>_hostname_ifile.ora on the secondary nodes. If using anspfile, and it was already updated on the primary node, this step is not needed on the secondarynodes.

LOG_ARCHIVE_DEST_1='LOCATION=/<shared_storage or ASM +DISKGROUP>/<SID>/archivelog'

LOG_ARCHIVE_FORMAT='%t_%s_%r.dbf'

Start up the secondary nodes.

SQL>startup

2. Confirm the database controlfile(s) and archive log file locations on shared storage

If the source system was not previously in archive log mode, but it has recently been enabled, or if thesource system parameter ARCHIVE_LOG_LIST was at some point set to any local disk directorylocation, you must ensure that RMAN has a properly maintained list of valid archive logs locatedexclusively in the shared storage area.

To confirm RMAN knows only of your archive logs located on the shared disk storage area, dothe following using SQL*Plus or RMAN to show the locations of the archive logs.

SQL>archive log list

If the output shows a local disk location, change this location appropriately, and back up or relocated anyarchive log files to the shared storage area. It will then be necessary to correct the RMAN archive log“manifest”, as follows:


8 of 26 7/22/2010 1:51 PM

RMAN>crosscheck archivelog all;

Review the output archive log file locations and, assuming you have relocated or removed anylocally stored archive logs, you will need to correct the invalid or “expired” archive logs as follows:

RMAN>delete expired archivelog all;

It is essential to carry out the above steps (if applicable) before you continue with the Oracle E-BusinessSuite Release 11i RAC cloning procedure.

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

Note: On slower systems, the parallelism number in the script below should be reduced.

Note: If <your location> as shown below is an NFS mount point, special mount option MUSTbe used depending on OS platform in order to successfully create a copy of the currentcontrolfile via RMAN.

SQL>set echo off pages 0 feed off linesize 5000 TRIM on TRIMS on sqlp #

SQL>spool <your location>/11i_10grac_backup.rman

SQL>select 'configure device type disk parallelism 5 backup type to backupset;' \from dual;

SQL>select 'configure maxsetsize to '||round((max(bytes)/1024/1024) + 200)||'m;' \from dba_data_files;

SQL>select 'backup as backupset tag ''RapidClone_RAC'' database format \''<your location>/data/stage/%U'';' from dual;

SQL>select 'backup as backupset tag ''RapidClone_RAC'' archivelog all format \''<your location>/data/stage/%U'';' from dual;

SQL>select 'backup tag ''RapidClone_RAC'' as copy current controlfile format \''<your location>/data/stage/backup_controlfile.ctl'';' from dual;

SQL>select 'exit' from dual;


9 of 26 7/22/2010 1:51 PM

SQL>spool off;

SQL>exit;

4. Execute the RMAN script to create a database "stage" or "image"

rman target / nocatalog @<absolute path to script>/11i_10grac_backup.rman > 11i_10gRAC_backup.log

5. Transfer the RMAN backup set files and the $ORACLE_HOME archive (racdb_techstack.tgz) to the target

nodes

After the "stage" creation is completed, navigate to <stage location>/data/stage. In this directory, you will find several2GB (or larger) RMAN backup/image files. These files will have names like "1jj9c44g_1_1". The number of filespresent will depend on the source system configuration. These files, along with the "backup_controlfile.ctl", will need tobe transferred to the primary target system upon which you wish to create the new primary Oracle RAC instance.

These RMAN backup set files should be placed into a temporary holding area on ONLY the primary targetnode. This location will ultimately be removed after successful target instance creation. There is no need totransfer the RMAN backup set files created above to any other target system nodes. The source system $ORACLE_HOME archive should now be transferred to ALL secondary target system RACnodes (to become instances) upon which you will be configuring the new RDBMS $ORACLE_HOME, place thissoftware archive in the directory you wish. The same location or top level directories should be chosen tounarchive the technology stack into.

Section 6: Target System Database Technology Stack Restore and Configuration

6.1 Target 11i RAC DB Technology Stack Restore:

1. Clone the primary source DB node to the new primary target system node.

Uncompress archived (tar'd or zip'd) ORACLE_HOME copied from the source system to the new primary targetnode. Choose a suitable location, and rename the extracted top-level directory name to something meaningful on thenew primary target system node.

tar -xvzf racdb_techstack.tgz

2. Create a pairsfile for new pimary target system node

Create a simple text file named pairsfile.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

s_db_oh=<new_oh_loc>

Where s_undo_tablespace represents the initial target system undo tablespace and where s_dbClusterInst represents the totalnumber of instances present in the cluster. These two parameters values will need to be altered on secondary nodesbut can not be different values from those present on the source system RAC environment.

Note: Adding (scaling-up) or removing (scaling-down) the number database instances is notcovered in this document at this time.

When cloning a source 11i E-Business Suite with 10g (or 11g) RAC enabled, the source andtarget system must have the same number of database instances other wise, additional undotablespaces and log threads must be added manually.

This new text file file should be placed into the <NEW_ORACLE_HOME>/appsutils/clone location.

3. Create Context File for primary target system node

Execute the following command to create a new context file, provide careful answers to the prompted questions:

Navigate to <NEW_ORACLE_HOME>/appsutil/clone/bin. Run the adclonectx.pl utility as follows:

perl adclonectx.pl \contextfile=<PATH to ORIGINAL Source RAC contextfile.xml> \template=<NEW ORACLE_HOME>/appsutil/template/adxdbctx.tmp \pairsfile=<NEW ORACLE_HOME>/appsutil/clone/pairsfile.txt \

Where:

Parameter Usage

contextfile Full Path to the old Source RAC Database Context File.

template Full Path to the existing Database Context file template.

pairsfile Full Path to the pairsfile created on last step.

In order to avoid potential confusion, as an example, you will be present with the following questions [sample answersprovided]:

Provide the values required for creation of the new Database 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

It is recommended that your inputs are validated by the program.However you might choose not to validate your inputs under following \ circumstances: -If cloning a context on source system for a remote system. -If cloning a context on a machine where the ports are taken and you do not \ want to shutdown the services at this point. -If cloning a context but the database it needs to connect is not available.

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]:67Database 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

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,/usr/tmp, \/u01/app/oracle/product/10.2.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.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.xml]:

Creating the new Database Context file from :/s1/asgard_homeworld/racdb/appsutil/template/adxdbctx.tmp

Note: It is of critical importance that the correct values are selected above; if uncertain, carefully review the newlywritten context file and compare it with values selected during the Source System migration to RAC (as perOracleMetalink Note 362135.1). Please be sure if comparisons are made, that any path differences between theSource and Target Systems are understood and accounted for.

4. Edit the newly generated contextfile.xml (of the form <newsid_hostname>.xml) to review or change the

following remote and local listener, database name, 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

6.2 Target 11i RAC DB Technology Stack Configuration:

1. Edit the oraInst.loc in the target system $ORACLE_HOME

Create a directory under the $ORACLE_HOME location to store inventory information.

cd <NEW_ORACLE_HOME>/

mkdir oraInventory

Create or update the existing oraInst.loc file in the target system $ORACLE_HOME with the following:

inventory_loc=<NEW_ORACLE_HOME>/oraInventoryinst_group=<dba group>

2. Run the adclone.pl utility as follows:

Navigate to <NEW_ORACLE_HOME>/appsutil/clone/bin.

perl adclone.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. Carefully review the newly generated configuration files for any potential inconsistencies.

init<NEW_SID>.ora<NEW_SID>_APPS_BASE.ora

Confirm the desired control file name and location. If changes are required, correct these values within the context fileand again run adclone.pl to propagate the required values to the associated configuration files.

4. Create a temporary init<NEW_SID>.ora.tmp file

This init<NEW_SID>.ora.tmp will be used only during the RMAN restore in Section 7 below. The file should be placedinto the <NEW_ORACLE_HOME>/dbs directory and contain the values as shown in the example file in Appendix Abelow.

The values within the temporary init.ora file may require adjustment depending on the target system database size andavailable host resources.


14 of 26 7/22/2010 1:51 PM

Note: Be certain to keep and maintain the recently generated, non-temporary

init<new_sid>.ora file located in the Target System $ORACLE_HOME/dbs direcotry. Thegenerated init<new_sid>.ora file will not immediately be used during the RMAN restoreprocess, but will be modified and used in subsequent steps.

Please do not confuse the generated and tempoary init.ora files during the RMANprocesses to come in Section 7 below.

Section 7: Target System Database Image Restore

7.1 Restore Control File

1. Create an RMAN script to restore the control file onto target system

File contents of restore-rac1.rman

startup nomount pfile=<NEW_ORACLE_HOME>/dbs/init<NEW_SID>.ora.tmprestore controlfile from '<Temporary Stage Area>/data/stage/backup_controlfile.ctl';

alter database mount;exit

2. Run the control file restore script.

rman target / nocatalog @restore-rac1.rman > restore-rac1.log

7.2 Restore Database

1. Create a sql script which will build the main RMAN script to restore the database.

File contents of restore-rac2.sql

connect / as sysdbaset echo off pages 0 feed off sqlp #spool restore-rac2.rmanselect 'catalog start with ''<Temporary Stage Area>'' NOPROMPT;' from dual;select 'RUN { ' from dual;select 'set newname for datafile '||file#||' to NEW;' from v$datafile;select 'set newname for tempfile '||file#||' to NEW;' from v$tempfile;select 'restore database;' from dual;


15 of 26 7/22/2010 1:51 PM

select 'switch datafile all;' from dual;select 'switch tempfile all;' from dual;select 'recover database;' from dual;select '} ' from dual;select 'exit' from dual;spool offexit

2. Run the sql script which will build restore-rac2.rman

sqlplus "/as sysdba" @restore-rac2.sql

3. Run the main database restore script.


If RMAN-03002 and RMAN-06054 errors are present, they can be safely ignored.

4. Create a sql script which will build another sql script to rename the DB log files.

File contents of restore-rac21.sql

connect / as sysdbaset echo off pages 0 feed off linesize 5000 TRIM on TRIMS on sqlp #spool restore-rac-logfile.sqlselect 'connect /as sysdba' from dual;select 'alter database rename file '''||member||''' to '||'''<shared_storage_loc>/datafile/'||REGEXP_REPLACE(''||member||'','.*/') ||''';' from v$logfile;select 'exit' from dual;spool offexit

5. Run the script restore-rac21.sql.

sqlplus "/as sysdba" @restore-rac21.sql

This script will create another script named restore-rac-logfile.sql

6. Run the script restore-rac-logfile.sql.

sqlplus "/as sysdba" @restore-rac-logfile.sql

7. Create the following RMAN script to reset the logs, shutdown and startup the restored database.

File contents of restore-rac3.rman

alter database open resetlogs;


16 of 26 7/22/2010 1:51 PM

shutdown normalstartup mount pfile=<NEW_ORACLE_HOME>/dbs/init<NEW_SID>.ora.tmp

8. Run the final RMAN restore scripts.


9. Modify the temporary init<NEW_SID>.ora.tmp.

Edit the hand made, temporary init<NEW_SID>.ora.tmp file used during the earlier steps of the RMAN restore asfollows:

Change the db_name value FROM the Source System Global Database Name TO the new Target System GlobalDatabase Name.

For example, if the db_name parameters value was db_name=TEST and the new target system global databasename is PRODCRP, the db_name=PRODCRP should be the value present in the temporary init<NEW_SID>.ora.tmpprior to renaming the DBID and DBNAME in the next step.

Note: Do not shutdown or restart the Database, procede to step 7.3 after making the db_name parameter change inthe temporary init.ora.

7.3 Change the DBNAME and DBID

Note: After this step, the restored database will be shutdown.

nid target=/ dbname=<new target db_name as defined in new context file>

7.4 Restart Database for first time after name and id change.

rman target / <<EOFstartup mount pfile=<NEW_ORACLE_HOME>/dbs/init<NEW_SID>.ora.tmpEOF

7.5 Open Database and reset the log files.

sqlplus or rman can be used here:

rman target / <<EOFalter database open resetlogs;EOF

7.6 Modify the <NEW_SID>_APPS_BASE.ora file and correct the control_file parameter value.

Because Autoconfig does not allow for values to be directly specified for the control_files location, you must updatethis parameters as it currently exists within the <NEW_SID>_APPS_BASE.ora file before the Database is shutdownand restarted in the following step. 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

(if applicable).

7.7 Shutdown and restart the Database to begin using the Autoconfig generated configuration files.

With the configuration files updated, the database restored and renamed, we need to do a shutdown and startup tocut over to using the proper configuration files.


rman target / <<EOFshutdown immediateEOF


rman target / <<EOFstartupEOF

7.8 Clean up legacy System Level profile options, WF data, 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.SETUP_CLEAN

7.9 Create a temporary listener.ora file to be used during Autoconfig execution in the next step.

This tempoary listener.ora file will be used only during Autoconfig such that connectivity to the newly restored andrenamed target system database instance can be connected to updated with appropriate node information as well asto generate proper RAC specific listener.ora and tnsnames.ora files.

The listener.ora file should be placed into the <NEW_ORACLE_HOME>/network/admin/<CONTEXT_NAME> directoryand contain the values as shown in the example file in Appendix A below.

7.10 Start the newly defined listener and run Autoconfig

1. Source the newly generate environment file in the <NEW_ORACLE_HOME> directory.

cd <NEW_ORACLE_HOME>

. <new_sid>_<hostname>.env


18 of 26 7/22/2010 1:51 PM

2. Start the TNS Listener created by hand from the provided example in Appendix A.

lsnrctl start listener_<hostname>

3. Run Autoconfig.

cd $ORACLE_HOME/appsutil/scripts/<context_name>/

./adautocfg.sh

4. Confirm no errors occurred during Autoconfig execution by reviewing the provided log.

5. Inspect the following files to confirm expected values are present.

init<NEW_SID>.ora<NEW_SID>_APPS_BASE.oralistener.oratnsnames.ora

7.11 Create an spfile on the shared storage location if desired.

After validating the configuration files and starting and stopping the instance and listener several times to confirmexpected operation, create an spfile from the pfile(s) current being used. Remeber that the current init.ora generatedfrom Autoconfig contains an ifile parameter. If you wish to use archive logging, enable such parameters in the ifilebefore creating the spfile.

SQL>create pfile='<shared storage loc>/spfile_<global_dbname>.ctl' from \ pfile='<NEW_ORACLE_HOME>/dbs

/init<NEW_SID>.ora'

Section 8: Target System Secondary Node Technology Stack Restore & Configuration

Target 11i RAC DB Technology Stack Restore [Secondary Nodes]:

8.1 Clone the primary source DB node to the new secondary target system node.

Uncompress archived (tar'd or zip'd) ORACLE_HOME copied from the source system to this new secondary targetnode(s). Choose a suitable location, and rename the extracted top-level directory name to something meaningfulwhich matches the location and naming convention chosen on the primary target system node.

tar -xvzf racdb_techstack.tgz

8.2 Create a pairsfile for new secondary target system node

Create a simple text file named pairsfile.txt with your favorite editor with the contents as shown:


19 of 26 7/22/2010 1:51 PM

s_undo_tablespace=UNDOTBS2

s_dbClusterInst=2s_db_oh=<NEW_ORACLE_HOME>

Where s_undo_tablespace represents the secondary target instance undo tablespace and where s_dbClusterInst represents thetotal number of instances present in the cluster.

This new text file file should be placed into the <NEW_ORACLE_HOME>/appsutil/clone location.

8.3 Create Context File for secondary target system node

Execute the following command to create a new context file, provide careful answers to the prompted questions:

Navigate to <NEW_ORACLE_HOME>/appsutil/clone/bin. Run the adclonectx.pl utility as follows:

perl adclonectx.pl \contextfile=<PATH to Target System Primary RAC Node contextfile.xml> \template=<NEW ORACLE_HOME>/appsutil/template/adxdbctx.tmp \pairsfile=<NEW ORACLE_HOME>/appsutil/clone/pairsfile.txt \

Where:

Parameter Usage

contextfile Full Path to the old Source RAC Database Context File.

template Full Path to the existing Database Context file template.

pairsfile Full Path to the pairsfile created on last step.

Answer the presented prompts as in done earlier in Section 7 above, making allowances for the fact that this is thesecondary instance and a different hostname and instance #.

Note: It is of critical importance that the correct values are during the context file interview phase; if uncertain aboutwhat values to provide, carefully review the newly written context file and compare it with values selected during theprimary target instance context file generation. Please be sure if comparisons are done, that path differences betweenthe primary target instance and secondary target instance are accounted for.

8.4 Edit the newly generated contextfile.xml (of the form <newsid_hostname>.xml) to review or change the following

remote and local listener, database name, 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

8.5. Run the adclone.pl utility as follows:

Navigate to <NEW_ORACLE_HOME>/appsutil/clone/bin.

perl adclone.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.6 Create a temporary listener.ora file to be used during Autoconfig execution in the next steps.

This tempoary listener.ora file will be used only during Autoconfig such that connectivity to the newlyrestored and renamed target system database instance can be connected to updated with appropriatenode information as well as to generate proper RAC specific listener.ora and tnsnames.ora files.

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

8.7 Start the newly defined listener and start the secondary instance.

1. Source the newly generate environment file in the <NEW_ORACLE_HOME> directory.

cd <NEW_ORACLE_HOME>

. <new_sid>_<hostname>.env

2. Start the TNS Listener created by hand from the provided example in Appendix A.

lsnrctl start listener_<hostname>

3. Modify the <NEW_SID>_APPS_BASE.ora file and correct the control_file parameter value.

Because Autoconfig does not allow for values to be directly specified for the control_files location, youmust update this parameters as it currently exists within the <NEW_SID>_APPS_BASE.ora file beforethe Database can be started in the following step. Make certain to provide the full path to the restoredcontrol file as it exists on the shared storage location.

8.8 Run Autoconfig.

1. Execute Autoconfig.


21 of 26 7/22/2010 1:51 PM

cd $ORACLE_HOME/appsutil/scripts/<context_name>/

./adautocfg.sh

2. Confirm no errors occurred during Autoconfig execution by reviewing the provided log.

3. Inspect the following files to confirm expected values are present.

init<NEW_SID>.ora<NEW_SID>_APPS_BASE.oralistener.oratnsnames.ora

8.9 Carry Out Target System (Primary Node) Final Oracle RAC Configuration Tasks

Recreate TNSNAMES and LISTENER.ORA again on the primary target node.

Login again to the target primary node (Node 1) and run AutoConfig to perform the final Oracle RAC configuration andcreate new listener.ora and tnsnames.ora (as the FND_NODES table did not contain the second node hostname untilAutoConfig was run on the secondary target RAC node).

cd $ORACLE_HOME/appsutil/scripts/<CONTEXT_NAME>

./adautocfg.sh

Note: This execution of AutoConfig on the primary target RAC Node 1 will add the second RAC Nodeconnection information to the first node's tnsnames.ora, such that listener load balancing can occur. If you havemore than two nodes in your new target system cluster, you must repeat Sections 8.2 and 8.3 for allsubsequent nodes.

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

Primary target database nodeSecondary target database nodeAn independent machine, running neither of the target system RAC nodesShared between two or more machines

Because of the complexities which might arise, it is strongly suggested that the applications tier should initially beconfigured to connect to a single database instance. After proper configuration with one of the two target system RACnodes has been achieved, context variable changes can be made such that JDBC and TNS Listener load balancing areenabled.

9.1 Clone the Applications Tier

In order to clone the applications tier, follow the standard steps for the applications node posted on Sections 2 OracleMetalink document 230672.1, Cloning Oracle Applications Release 11i with Rapid Clone. This includesadpreclone steps, copy the bits to the target, configuration portion, and finishing tasks steps.

Note: On the applications tier, during the adcfgclone.pl execution, you will be asked for a database to whichthe applications tier services should connect to. Enter the information specific to a single target system RACnode (such as the primary node). On successful completion of this step, the applications node services will bestarted, and you should be able to log in and use the new target system Applications system.

9.2 Configure Application Tier JDBC and Listener Load Balancing

Reconfigure the applications node context variables such that database listener/instance load balancing can occur.

Note: Only after successfully associating the new Target System Application Node / Tier with one of the twoTarget System database instances, should SQL*Net and JDBC Listener Load Balancing be attempted.

Please refer to OracleMetaLink document 362135.1, section 3.11 for specific details on how to enables JDBC andSQL*Net Listener Load Balancing for the 11i Applications Node in a RAC enabled environment.

Appendix A: Example init.ora and listener.ora file

The below temporary init<new_sid>.ora.tmp file should be used only during Section 7: Target System Database ImageRestore on the primary target node during RMAN restore. Be sure to read the comments in this sample files before


23 of 26 7/22/2010 1:51 PM

choosing appropriate values.

Temporary init<new_sid>.ora.tmp contents:

## Source System Global Database Name...NOT A SID NAMEdb_name=OLDGLDB## New Target System Global Database Name...NOT A SID NAMEdb_unique_name=NEWGLDB## The number of DB files available to RMAN, set to appropriate valuedb_files = 4096## The location to which the shared dbf (datafiles) will be written. This## location should be the mount point to which both target RAC nodes can## read and write file to. +ASM_DISK_GROUP, NFS or OCFS disks## Note that RMAN will create a sub-directory under this location with the## NEW GLOBAL Database name in UPPER case.db_create_file_dest=+ASM_DSKGRP1## RMAN will place the archive logs in this location and it should be## located on shared storage, accessible from both RAC nodesdb_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 neededdb_recovery_file_dest_size=300g## The location & name to which the "new" Target System control file## will be restored to...Set to desired location...must be on shared## storage location access by both Target System RAC nodescontrol_files=+ASM_DSKGRP1/<UPPER_CASE_NEWGLDB/controlfile_<NEWGLDB>.ctl## Tempoary SGA TARGET size, set to appropriate value as neededsga_target=1g## Tempoary SGA MAX size, set to appropriate value as neededsga_max_size=2g## Tempoary number for OPEN CURSORS, set to appropriate value as neededopen_cursors=1000## Parameter should ONLY be present when DB Version is 11g...DO NOT## USE THIS PARAMETER if DB Version is 10g!!compatible=11.1.0

The below tempoary listener.ora should be used only during Section 7: Target System Database Image Restore onthe primary target node during Autoconfig.

Temporary listener.ora content:

LISTENER_<hostname> =(DESCRIPTION_LIST =(DESCRIPTION =


24 of 26 7/22/2010 1:51 PM

(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = <context value for s_virtual_hostname>)(PORT = <context value fors_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> = 0CONNECT_TIMEOUT_LISTENER_<hostname> = 10TRACE_LEVEL_LISTENER_<hostname> = OFF

LOG_DIRECTORY_LISTENER_<hostname> = <NEW_DATABASE_HOME>/network/adminLOG_FILE_LISTENER_<hostname> = <new_sid>TRACE_DIRECTORY_LISTENER_<hostname> = <NEW_DATABASE_HOME>/network/adminTRACE_FILE_LISTENER_<hostname> = <new_sid>ADMIN_RESTRICTIONS_LISTENER_<hostname> = OFF

Change Log

Date Description

April 01, 2009Clarifications in preparation for GA as provided by members of OSS & firsthand testing.

March 25, 2009 Several small formatting changes and elaboration of provided commands

Mar 16, 2009 Minor syntax corrections and additions to Conventions table

Mar 07, 2009 Publishing Review

Jan 20, 2009 Initial Posting


25 of 26 7/22/2010 1:51 PM

Nov 09, 2008 First Draft

Note 760637.1 by Oracle Applications DevelopmentCopyright © 2009 Oracle CorporationLast updated: March 10, 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

manually cloning oracle applications release 11i with 10g or 11g rac [id 760637.1]

Documents