Thursday, May 20, 2010

Rapid Clone for Single Node - Linux

The Basic Steps for Cloning

After installing the Rapid Clone and AutoConfig patches, you are ready to clone an instance. There are ten basic steps involved. I have outlined them below:

1. Run system configuration on the Application tier:
/admin/scripts//adautocfg.sh
Use the APPS password when prompted.

2. Run system configuration on the database tier:
/appsutil//scripts/adautocfg.sh
Use the APPS password when prompted.

3. Copy AutoConfig to the RDBMS ORACLE_HOME:
Apply patch 2952369 to acquire adchkcfg utility.
Create appsutil.zip file by: perl /bin/admkappsutil.pl.
Copy appsutil.zip file to the
unzip -o appsutil.zip

4. Generate the database context file:
cd /appsutil/bin
adbldxml.sh tier=database appsuser= appspasswd=
Output log is written to: $ORACLE_HOME/appsuti/out//cfgcheck.txt

5. Generate and apply AutoConfig configuration file:
cd /appsutil/bin
adconfig.sh contextfile= appspass=

6. Prepare for source database clone:
cd /appsutil/scrips/
./perl adpreclone.pl dbTier

7. Prepare for source application clone:
cd /admin/scripts/
./perl adpreclone.pl appsTier

8. Copy the application tier file system:
Logon to the source system as APPLMGR and shut down the server processes.
Copy the following application directories from the source to the target node/file system:

APPL-TOP
OA_HTML
OA_JAVA
COMMON_TOP/util
COMMON_TOP/clone
806 ORACLE_HOME
iAS ORACLE_HOME

Shut down the source database and copy it to the target node/file system.
Restart the source database and source application server processes.

9. Configure the target system database sever:
cd /appsutil/clon/bin
./perl adcfgclone.pl dbTier

10. Configure the target system application tier:
cd /clone/bin
./perl adcfgclone.pl appsTier

Note: These steps are for a single node install. If you are using Oracle Workflow, you must update wf_notification_attributes and wf_item_attribute_values.

Version 2.1.0.17 of the Oracle Universal Installer and Perl 5.005 should be installed and included in your path. Be sure to review your install logs after cloning to make sure there are no errors. After you have verified connectivity in the cloned environment, have a user navigate through the system to verify the clone is functional and complete.

No comments:

Post a Comment

Search This Blog