RAPID CLONE

PRECLONE STEPS

DATABASE TIER:

[oracle2@apps VISION_apps]$ perl adpreclone.pl dbTier
Running Rapid Clone with command...
perl /appscoe2/appscoe/visiondb/9.2.0/appsutil/bin/adclone.pl java=/appscoe2/appscoe/visiondb/9.2.0/appsoui/jre/1.3.1 mode=stage stage=/appscoe2/appscoe/visiondb/9.2.0/appsutil/clone component=dbTier method=CUSTOM dbctx=/appscoe2/appscoe/visiondb/9.2.0/appsutil/VISION_apps.xml showProgress

Beginning database tier Stage - Fri Aug 25 16:57:34 2006
APPS Password : apps
Log file located at /appscoe2/appscoe/visiondb/9.2.0/appsutil/log/VISION_apps/StageDBTier_08250457.log
Completed Stage...
Fri Aug 25 17:13:46 2006

APPS TIER:

[oracle2@apps VISION_apps]$ perl adpreclone.pl appsTier
Running Rapid Clone with command...
perl /appscoe2/appscoe/visionappl/ad/11.5.0/bin/adclone.pl java=/appscoe2/appscoe/visionora/iAS/appsoui/jre/1.3.1 mode=stage stage=/appscoe2/appscoe/visioncomn/clone component=appsTier method=CUSTOM appctx=/appscoe2/appscoe/visionappl/admin/VISION_apps.xml showProgress

Beginning application tier Stage - Fri Aug 25 17:21:45 2006
Log file located at /appscoe2/appscoe/visionappl/admin/VISION_apps/log/StageAppsTier_08250521.log
Completed Stage...
Fri Aug 25 17:29:48 2006

Now all the tops need to be manually copied from the source system to the destination system
And they need to be renamed. Say if we are cloning dev from prod, then prodappl, prodcomn etc need to be renamed as devappl, devcomn etc.
mv prodappl devappl

POST CLONE:

DATABASE TIER:

[oracle3@apps bin]$ perl adcfgclone.pl dbTier
Enter the APPS password [APPS]:
apps

First Creating a new context file for the cloned system.
The program is going to ask you for information about the new system:


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 instance is a Real Application Cluster (RAC) instance (y/n) [n]:n

Target System database name [VISION]:CLONE

Target system RDBMS ORACLE_HOME directory [/appscoe2/appscoe/visiondb/9.2.0]:/appscoe3/appsclone/clonedb/9.2.0

Target system utl_file accessible directories list [/usr/tmp]:

Number of DATA_TOP's on the target system [1]:1

Target system DATA_TOP 1 [/appscoe2/appscoe/visiondata]:/appscoe3/appsclone/clonedata

Do you want to preserve the Display set to apps:0.0 (y/n) [y] ?:y

Clone Context uses the same port pool mechanism as the Rapid Install
Once you choose a port pool, Clone Context will validate the port availability.

Enter the port pool number [0-99]:
10

Checking the port pool 10
done: Port Pool 10 is free
Database port is 1531

Creating the new Database Context file from :
/appscoe2/appscoe/visiondb/9.2.0/appsutil/template/adxdbctx.tmp

The new database context file has been created :
/appscoe3/appsclone/clonedb/9.2.0/appsutil/CLONE_apps.xml

Log file located at /appscoe3/appsclone/clonedb/9.2.0/appsutil/clone/bin/CloneContext_08271007.log

Running Rapid Clone with command:
perl /appscoe3/appsclone/clonedb/9.2.0/appsutil/clone/bin/adclone.pl java=/appscoe3/appsclone/clonedb/9.2.0/appsutil/clone/bin/../jre mode=apply stage=/appscoe3/appsclone/clonedb/9.2.0/appsutil/clone/bin/.. component=dbTier method=CUSTOM dbctxtg=/appscoe3/appsclone/clonedb/9.2.0/appsutil/CLONE_apps.xml showProgress contextValidated=true

Beginning database tier Apply - Sun Aug 27 10:09:36 2006
Log file located at /appscoe3/appsclone/clonedb/9.2.0/appsutil/log/CLONE_apps/ApplyDBTier_08271009.log
Completed Apply...
Sun Aug 27 10:12:57 2006

Beginning APPSDB_CLONE registration to central inventory...

ORACLE_HOME NAME : APPSDB_CLONE
ORACLE_HOME PATH : /appscoe3/appsclone/clonedb/9.2.0
Using Inventory location in /etc/oraInst.loc
Log file located at /etc/oraInventory/logs/OracleHomeCloner_08271012.log
AC-00002: Error: Unable to create log file - /etc/oraInventory/logs/OracleHomeCloner_08271012.log
AC-00002: Error: Unable to create log file - /etc/oraInventory/logs/OracleHomeCloner_08271012.log
Exception in thread "main" java.lang.RuntimeException: AC-00002: Unable to create log file - /etc/oraInventory/logs/OracleHomeCloner_08271012.log
Raised by oracle.apps.ad.util.LogFile
at oracle.apps.ad.util.LogFile.appendLogFile(LogFile.java:356)
at oracle.apps.ad.util.LogFile.log(LogFile.java:233)
at oracle.apps.ad.util.LogFile.info(LogFile.java:212)
at oracle.apps.ad.clone.util.OracleHomeCloner.registerOracleHome(OracleHomeCloner.java:307)
at oracle.apps.ad.clone.util.OracleHomeCloner.registerOracleHome(OracleHomeCloner.java:165)
at oracle.apps.ad.clone.util.OracleHomeCloner.main(OracleHomeCloner.java:1122)

ERROR: Registration Failed... Please check log file.

You can rerun this registration with the following script:
/appscoe3/appsclone/clonedb/9.2.0/appsutil/out/CLONE_apps/regOUI_APPSDB_CLONE.sh

Starting database listener for CLONE:
Running:
/appscoe3/appsclone/clonedb/9.2.0/appsutil/scripts/CLONE_apps/addlnctl.sh start CLONE

You are running addlnctl.sh version 115.6

Logfile: /appscoe3/appsclone/clonedb/9.2.0/appsutil/log/CLONE_apps/addlnctl.txt

Starting listener process CLONE ...


Listener CLONE has already been started.


addlnctl.sh: exiting with status 0

Due to this error, this code was required to be rerun again.

[oracle3@apps CLONE_apps]$ ./regOUI_APPSDB_CLONE.sh
Using Inventory location in /etc/oraInst.loc
Log file located at /etc/oraInventory/logs/OracleHomeCloner_08271148.log
ORACLE_HOME /appscoe3/appsclone/clonedb/9.2.0 was registered successfully.
ERRORCODE = 0 ERRORCODE_END

APPS TIER:

[oracle3@apps bin]$ perl adcfgclone.pl appsTier
Enter the APPS password [APPS]:
apps

First Creating a new context file for the cloned system.
The program is going to ask you for information about the new system:


Provide the values required for creation of the new APPL_TOP Context file.

Do you want to use a virtual hostname for the target node (y/n) [n] ?:n

Target system database SID [VISION]:CLONE

Target system database server node [apps]:

Target system database domain name [tcs.com]:

Does the target system have more than one application tier server node (y/n) [n] ?:n

Is the target system APPL_TOP divided into multiple mount points (y/n) [n] ?:n

Target system APPL_TOP mount point [/appscoe2/appscoe/visionappl]:/appscoe3/appsclone/cloneappl

Target system COMMON_TOP directory [/appscoe2/appscoe/visioncomn]:/appscoe3/appsclone/clonecomn

Target system 8.0.6 ORACLE_HOME directory [/appscoe2/appscoe/visionora/8.0.6]:/appscoe3/appsclone/cloneora/8.0.6

Target system iAS ORACLE_HOME directory [/appscoe2/appscoe/visionora/iAS]:/appscoe3/appsclone/cloneora/iAS

Do you want to preserve the Display set to apps:0.0 (y/n) [y] ?:y

Clone Context uses the same port pool mechanism as the Rapid Install
Once you choose a port pool, Clone Context will validate the port availability.

Enter the port pool number [0-99]:
10

Checking the port pool 10
done: Port Pool 10 is free
Web Listener port is 8010
Complete port information available at /appscoe3/appsclone/cloneappl/admin/out/CLONE_apps/portpool.lst

UTL_FILE_DIR on database tier consists of the following directories.

1. /usr/tmp
2. /usr/tmp
3. /appscoe3/appsclone/clonedb/9.2.0/appsutil/outbound/CLONE_apps
4. /usr/tmp
Choose a value which will be set as APPLPTMP value on the target node [1]:1

Creating the new APPL_TOP Context file from :
/appscoe2/appscoe/visionappl/ad/11.5.0/admin/template/adxmlctx.tmp

The new APPL_TOP context file has been created :
/appscoe3/appsclone/cloneappl/admin/CLONE_apps.xml

Log file located at /appscoe3/appsclone/clonecomn/clone/bin/CloneContext_08271201.log

Running Rapid Clone with command:
perl /appscoe3/appsclone/clonecomn/clone/bin/adclone.pl java=/appscoe3/appsclone/clonecomn/clone/bin/../jre mode=apply stage=/appscoe3/appsclone/clonecomn/clone/bin/.. component=appsTier method=CUSTOM appctxtg=/appscoe3/appsclone/cloneappl/admin/CLONE_apps.xml showProgress contextValidated=true

Beginning application tier Apply - Sun Aug 27 12:04:22 2006
Log file located at /appscoe3/appsclone/cloneappl/admin/CLONE_apps/log/ApplyAppsTier_08271204.log
Completed Apply...
Sun Aug 27 12:11:45 2006

Beginning APPSIAS_CLONE registration to central inventory...

ORACLE_HOME NAME : APPSIAS_CLONE
ORACLE_HOME PATH : /appscoe3/appsclone/cloneora/iAS
Using Inventory location in /etc/oraInst.loc
Log file located at /etc/oraInventory/logs/OracleHomeCloner_08271211.log
ORACLE_HOME /appscoe3/appsclone/cloneora/iAS was registered successfully.

Starting application Services for CLONE:
Running:
/appscoe3/appsclone/clonecomn/admin/scripts/CLONE_apps/adstrtal.sh APPS/

Oracle Apps 11i: Creating a RMAN Clone Database and Apps 11i on a New Host

Oracle Apps 11i: Creating a RMAN Clone Database and Apps 11i on a New Host

Database & Apps 11i Cloning and Multi Node to Single Node Cloning

Database & Apps 11i Cloning and Multi Node to Single Node Cloning

Copy AutoConfig to the RDBMS ORACLE_HOME
Update the RDBMS ORACLE_HOME file system with the AutoConfig files by performing the following steps:

On the Application Tier (as the APPLMGR user):

Log in to the APPL_TOP environment (source the environment file)
Create appsutil.zip file
perl /bin/admkappsutil.pl
This will create appsutil.zip in $APPL_TOP/admin/out.

On the Database Tier (as the ORACLE user):

Copy or FTP the appsutil.zip file to the
cd
unzip -o appsutil.zip

Generate your Database Context File
If your Applications system was created with the Release 11.5.9 Rapid Install or later, go to Task 3 in this section.
If your Applications system was created with the Release 11.5.8 Rapid Install or earlier, execute the following commands to create your Database Context File:

On UNIX
cd
. .env
cd /appsutil/bin
perl adbldxml.pl tier=db appsuser= appspasswd=


On Windows
Source the cmd Window using \.cmd
cd /d \appsutil\bin
perl adbldxml.pl tier=db appsuser= appspasswd=

Generate and Apply AutoConfig Configuration files

Attention: This step performs the conversion to AutoConfig. Once completed, the previous configuration will not be available.

Attention: The database server and the database listener must remain available during the AutoConfig run. All the other database tier services should be shut down.
Execute the following commands:
On UNIX
cd /appsutil/bin
adconfig.sh contextfile= appspass=

On Windows
cd /d \appsutil\bin
adconfig.cmd contextfile= appspass=

Warning: Running AutoConfig on the database node will update the RDBMS network listener file. Be sure to review the configuration changes from step 3. The new AutoConfig network listener file supports the use of IFILE to allow for values to be customized or added as needed.

Note: Running AutoConfig on the database tier will NOT overwrite any existing init.ora file. If no init.ora file exists in your instance, AutoConfig will generate an init.ora file for you.

Prepare the source system database tier for cloning
Log on to the source system as the ORACLE user and run the following commands:
cd /appsutil/scripts/
perl adpreclone.pl dbTier

APPLICATION TIER CLONING

Find or generate your Oracle Applications Context File
Look for the following file in the APPL_TOP:

/admin/.xml

On UNIX
cd /bin
perl adbldxml.pl tier=apps appsuser= appspasswd=

On Windows
cd /d \bin
perl adbldxml.pl tier=apps appsuser= appspasswd=

Generate and Apply AutoConfig Configuration files

Execute the following command:
On UNIX
/bin/adconfig.sh contextfile= appspass=

On Windows
\bin\adconfig.cmd contextfile= appspass=

Prepare the source system application tier for cloning

Log on to the source system as the APPLMGR user and run the following commands on each node that contains an APPL_TOP:
cd /admin/scripts/
perl adpreclone.pl appsTier

Copy the application tier file system
Log on to the source system application tier nodes as the APPLMGR user.
Shut down the application tier server processes
Copy the following application tier directories from the source node to the target application tier node:





/util
/clone
/_pages (when this directory exists)
<806>


Copy the database tier file system
Log on to the source system database node as the ORACLE user.
Perform a normal shutdown of the source system database
Copy the database (DBF) files from the source to the target system
Copy the source database ORACLE_HOME to the target system
Start up the source Applications system database and application tier processes

POST CLONING

Configure the target system database server
Log on to the target system as the ORACLE user and type the following commands to configure and start the database:

cd /appsutil/clone/bin
perl adcfgclone.pl dbTier

Configure the target system application tier server nodes
Log on to the target system as the APPLMGR user and type the following commands:

cd /clone/bin
perl adcfgclone.pl appsTier

Multi Node to Single Node Cloning

With Oracle Applications 11.5.10 the ability to clone from a multi node to a single node system using rapid clone has now been certified.

This is accomplished by the Shared APPL_TOP and Merging APPL_TOP features.

In this post i am listing out the steps to perform a multi note to a single node cloning from scratch. The information mentioned here is the steps which i have used and found them to be successful for a more elaborate explanation you might want to refer to the metalink note Sharing the Application Tier File System in Oracle E-Business Suite 11i (233428.1).

Source System here refers to the multi node system to be cloned
Target System refers to the newly to be created single node system
Applications Version 11.5.10
Operating System Linux ES 4

The following Steps are required to be performed on the source system
1. Apply application tier patches using adpatch

Apply patch 4038964Apply patch 4175764
Both the above patches are include in the consolidated update 2 or CU2 so in case you are on 11.5.10.2 or later you can ignore this step.

2. Maintain snapshot information

Log in as the applications user on each application tier node and run 'Maintain Snapshot Information' by using adadmin.

3. Merge existing APPL_TOPs

Log in to the primary node of your application tier as the application user user and run:
$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]$ perl adpreclone.pl appsTier merge
This will prompt you with option to merge secondary nodes
Now log in as the applications user to each of the secondary application tier nodes being merged and run:
$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]$ perl adpreclone.pl appltop merge

4. Prepare the source system database tier.
Log on to the database tier of the source system as the oracle user and run the following commands:
$ cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]$ perl adpreclone.pl dbTier
With this all the pre clone tasks on the source system have been completed.
The next set of tasks are required to be carried out on the target system that is the system on which you wish to place the merged single node instance.

1. Create OS user accounts

Create a OS user account for your applications
$ useradd -g dba -d [home_directory] -p password username
Similarly create a OS user account for your database

2. Modify the orainventory to reflect the new location

$ vi /etc/oraInst.loc

3. Copy the following application tier directories

Copy the following application tier directories from the primary node of your source system to the target application tier node, retaining the original directory structure:
– [APPL_TOP]– [OA_HTML]– [OA_JAVA]– [COMMON_TOP/util]– [COMMON_TOP/clone>– [806 ORACLE_HOME]– [iAS ORACLE_HOME]

4. Copy the required files for merging

Log in as the applications user to each of the secondary source nodes and recursively copy:
directory [COMMON_TOP]/clone/appl- to -directory [COMMMON_TOP]/clone/appl on the target system node
Before proceeding with the next steps you must shutdown your oracle applications services and the database on the source system

5. Copy the database tier file system

Log on to the source system as the database user
Copy the database (DBF) files from the source to the target systemCopy the source database ORACLE_HOME to the target system
After this you can now startup the database and applications services on your source system and release it for use.

6. Configure the target system database server

Log on to the target system as the database user and type the following commands to configure and start the database:
$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin$ perl adcfgclone.pl dbTier
This will prompt for new ORACLE_SID,ORACLE_HOME,Port Pool,JAVA_TOP and DATA_TOP give the appropriate values matching your target system
Once successful this should start your database and listener

7. Configure the application tier server nodes

The database and its listener should remain up before executing the next set of commands.Log in to the merged APPL_TOP node as the applications user and execute the following commands:
$ cd [COMMON_TOP]/clone/bin$ perl adcfgclone.pl appsTier
This will prompt you new port pool for applictaion tier services as well as new APPLTOP,COMMON_TOP,ORACLE_HOME and IAS_TOP
Successful completion of this task will bring up your application tier services on the target or the cloned node.

8. Post Clone Tasks

Log in to the target system application tier node as the APPLMGR user.Run the following tasks in adadmin for all products:o generate JAR fileso generate message fileso relink executableso copy files to destination

9. Clean up of the target system

Remove the temporary directory [COMMON_TOP]/clone/appl to reduce disk space usage.
Note: The version of Oracle Applications used is 11.5.10 and the operating system is Linux ES 4