Scribd
Upload
196 views3 pages

Cold Clone Process Overview

The document describes the steps to perform a cold clone of a production Oracle E-Business Suite system to create a test instance. It involves using utilities like adpreclone.pl and adcfgclone.pl to clone the database and application tiers, copying the file systems, and configuring the target system by changing hostnames, SIDs, and other parameters. Finally, it discusses some post-clone steps to configure the test instance, including modifying profile options and putting pending requests on hold.

Uploaded by

Kishore Adikar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
196 views3 pages

Cold Clone Process Overview

The document describes the steps to perform a cold clone of a production Oracle E-Business Suite system to create a test instance. It involves using utilities like adpreclone.pl and adcfgclone.pl to clone the database and application tiers, copying the file systems, and configuring the target system by changing hostnames, SIDs, and other parameters. Finally, it discusses some post-clone steps to configure the test instance, including modifying profile options and putting pending requests on hold.

Uploaded by

Kishore Adikar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

PRD - TEST

RapidClone Utility
------------------

Cold Cloning
-----------

PROD
----

Prepare the source system (System can be up)

1> cd $ORACLE_HOME/appsutil/scripts/VIS_erp
perl [Link] dbTier - clone (required information about the source -
context file, templates )

Clone folder location - $ORACLE_HOME/appsutil/clone

2> cd $ADMIN_SCRIPTS_HOME
perl [Link] appsTier - clone (required information of the source -
context file )

Clone folder location - $COMMON_TOP/clone

oraprod
applprod

tar ball - vnc session - scp - cannot be run in background

Copy the source system to the target system

shutdown application, database - copy the entire application and database


from source to target (inst_top - don't copy)

cd $ADMIN_SCRIPTS_HOME
sh [Link] apps/apps

cd $ORACLE_HOME

lsnrctl stop VIS


sqlplus "/as sysdba"
shutdown immediate

-- We can assume that we have copied the filesystem from production to non
production system then we need to follow below steps
-- IF required u can change the permissions of the db + apps

Once the copy is done - bring up the production

oratest
appltest

Configure target system


------------------------
cd $ORACLE_HOME/appsutil/clone/bin
perl [Link] dbTier - hostname, SID, port, where are your
datafiles ....recreate the control file - brings up the database
cd $COMMON_TOP/clone/bin
- DEV
perl [Link] appsTier- hostname,port, APPL_TOP, common_top, 10.1.2,
10.1.3 - creates a new context file - bring up the application

Web browser -

Finishing Tasks

varies from client to client -

5 minutes

Site%Name - profile - "TEST - Clone of PROD as 04-jun-2014"


Custom_top changes
PRoduction password - FNDCPASS (autoconfig on dbTier and appsTier) -
apps/apps - sysadmin/sysadmin

4 hours - Post clone steps - workflow, payment configuration , customization

-- Keeping all the pending (normal/standby/scheduled) requests are on hold

UPDATE apps.fnd_concurrent_requests SET hold_flag = 'Y' WHERE phase_code = 'P' AND


status_code in ('I','Q','F');
commit;

update applsys.fnd_profile_option_values
set profile_option_value=(select 'TEST Instance. Copy of PROD as of '||
to_char(max(actual_completion_date),'MM/DD/YYYY HH24:MI')
from applsys.fnd_concurrent_requests) where level_id=10001 and
(application_id,profile_option_id) in (select
fpo.application_id,fpo.profile_option_id from applsys.fnd_profile_options
fpo,applsys.fnd_profile_options_tl fpt where
fpo.profile_option_name=fpt.profile_option_name and
fpt.user_profile_option_name='Site Name');
commit;

Common questions

Powered by AI

Updating the 'hold_flag' for concurrent requests is a control measure that ensures no new processes are executed before final verification of the cloned environment. By setting the 'hold_flag' to 'Y' for requests in particular statuses ('P', 'I', 'Q', 'F'), administrators can prevent the inadvertent execution of application-specific or batch jobs that could produce unexpected results or load the system incorrectly. This step is crucial for maintaining system stability during the post-cloning phase.

Once the source system data is copied, configuring the target system involves running scripts to set up both the database and application tiers. Specifically, execute 'perl adcfgclone.pl dbTier' to configure the database tier by specifying hostname, SID, and port, and to recreate control files which bring up the database. Similarly, execute 'perl adcfgclone.pl appsTier' in the $COMMON_TOP/clone/bin directory for application tier configuration. This includes setting parameters such as hostname, port, and APPL_TOP, creating a new context file, and starting the application services.

Stopping the application and the database before copying ensures the integrity and consistency of the data being transferred. Running applications might have active processes that can alter data, leading to inconsistencies or corruption in the copied system. By shutting down services, we ensure that the data is static and unchanged during the copy process, thus maintaining the integrity of the target system.

Post-clone tasks, including updating the 'Site Name' in the database, are critical for ensuring the cloned system reflects its new environment and does not interfere with production settings. Changing the 'Site Name' helps identify the environment correctly as a clone, preventing users from confusing it with the production environment. It also helps in maintaining unique profiles and ensuring configurations such as workflow and payment settings are appropriate for the non-production instance.

The command 'perl adpreclone.pl dbTier' is used to prepare the database tier of the source system for cloning. This script gathers necessary information such as the context file and templates, and places them in the clone folder location, which is $ORACLE_HOME/appsutil/clone. This step is crucial for creating an exact copy of the database configuration on the target system.

You might also like