eBS4Dummies: October 2009

For cloning Oracle applications i used to references:
1.http://advait.wordpress.com/2008/01/14/cloning-oracle-application-11i-instance/

2 .Oracle Metalink link for procedure:
Subject:Cloning Oracle Applications Release 11i with Rapid Clone
Doc ID: 230672.1 Type: WHITE PAPER
Modified Date:06-AUG-2009 Status: PUBLISHED

Cloning Oracle Application 11i InstanceFiled under: Oracle Applications 11i — advait @ 8:24 am

Introduction
This section will cover the detailed steps required for cloning an 11i instance. Cloning an instance is creating a duplicate of the instance. But this definition is not exactly true, because during cloning we change various details like hostname, SID etc and configure the system as per these new values. But if we see the application data and other techstack versions are exactly same as source instance.

Need for Cloning
Some time situations arise where we have to clone our application system. For example, if we have a production instance and we want to create a test instance or a debug instance, then in that case we can just make a duplicate of production instance by cloning. Test instance is usually used when we want to test some patches before applying into production so as to avoid any unknown downtime for production system. Also some times we face issues in production and we want to reproduce the same error in test and get it fixed in test. Such kind of situations demands test instance.
This post is based on Metalink note ID 230672.1
Environment Information
My environment is 11.5.10.CU2. Database version is 9.2.0.6.
Further details about OA Framework version etc can be seen using following URL
http://ioversonas2.interoliva.local:8000/OA_HTML/OAInfo.jsp
OA Framework Version InformationOA Framework Version 11.5.10.2CU.
MDS Version 9.0.5.4.81 (build 481)
UIX Version 2.2.18
BC4J Version 9.0.3.13.51

Ioversonas2:8000(IOSADESA)
OA Framework Version InformationOA Framework Version 11.5.10.6RUP.
MDS Version 9.0.5.4.89 (build 560)
UIX Version 2.2.24.2
BC4J Version 9.0.3.9

The process There are 2 major methods for cloning an application system.
1) Cloning Oracle application without rapid clone.
Cloning Oracle Applications Release 11i was originally published in conjunction with Release 11.5.5 and is applicable for all 11i releases up to 11.5.5 that are not AutoConfig enabled.
2) Cloning Oracle application using Rapidclone technology
Cloning Oracle Applications Release 11i with Rapid Clone is applicable for all 11i systems that have migrated to AutoConfig and enabled Rapid Clone. This method contains steps to install AutoConfig and Rapid Clone.
Rapid Clone is the new cloning utility introduced in Release 11.5.8. Rapid Clone leverages the new installation and configuration technology utilized by Rapid Install. See OracleMetaLink Note 230672.1 (Cloning Oracle Applications 11i with Rapid Clone) for instructions on installing and enabling Rapid Clone.
Also there is one more method for cloning Oracle application with autoconfig, but this has been fully replaced by Cloning Oracle application using Rapidclone technology and is no longer supported by Oracle.
We will first discuss the method for cloning an Oracle Application with rapidclone.
With the flexible and sophisticated architecture of Oracle Applications Release 1i, simply copying all of the components will not provide you with a working applications system. For instance, there are numerous configuration files in your file system that must be modified based upon the physical topology. In addition, the Rapid Install installation process utilizes Oracle Universal Installer (OUI), which writes key information about the installation to a binary registry file. When you copy the system to a target location, you invalidate the binary registry file. Consequently, you will not be able to apply patches to the OUI-based
components.
Cloning the application system using rapid clone involves 3 major steps.
1. Preparing the Source System
2. Copy the file System to target location
3. Configuring the target system

Preparing The source file system
Preparing The source file system actually contains 2 sub steps.
1. Checking the pre-requisites patches
2. Preparing the source system for cloning.
We will start with checking the pre-requisites for cloning.
1) Make sure that patch 2115451 is applied to the application system. This will create the neccessary perl script. In our case the version of application is 11.5.10CU2, so this patch was already applied.
2) Apply the latest AD Minipack (Apply patch 4712852 (AD.I.4) or higher).
Check the current AD level of your application.
SQL> select PATCH_LEVEL from fnd_product_installations
2 where PATCH_LEVEL like ‘%AD%’;
PATCH_LEVEL
——————————
11i.AD.I.2

Ioversonas2 (IOSADESA)
PATCH_LEVEL
------------------------------
11i.AD.I.6

The latest version of this AD patch is now 11i.AD.I.5. But atleast make the version to 11i.AD.I.4 as mentioned in metalink note ID 230672.1
3) Apply the latest Autoconfig patch to the application. As per the note ID 165195.1 the latest patch for autoconfig is 5985992(JUL/AUG 2007). Please carry out the post install steps properly as mentioned in the README.txt present in the patch directory.
4) Next step is to check if the latest rapid clone patches are applied or not. As per the metalink note ID 230672.1 the latest rapid clone patches are
* 3453499 (11i.ADX.F)
* 5225940 (Post ADX.F Fixes)
* 5972212 (For SLES 10)
SQL> select count(*) from ad_bugs
2 where bug_number = ‘3453499′;
COUNT(*)
———-
1
Ioversonas2 (IOSADESA)
COUNT(*)
———-
1
SQL> select count(*) from ad_bugs
2 where bug_number = ‘5225940′;

COUNT(*)
———-
1
Ioversonas2 (IOSADESA)
COUNT(*)
———-
1

Third patch is required only if the application is on SLES linux. NO
5) Run Autoconfig on Application tier as well as on database tier. Make sure you did not encounter any error.

Section 3: Maintaining System Configuration
This section describes how to apply latest AutoConfig patch and manage your Oracle Applications Release 11i if your Instance is AutoConfig enabled. In addition to re-configuring your system, AutoConfig can be used to review changes made to the configuration files, to start and stop Applications processes and to start and stop Database processes.

1. Commands to maintain System Configurations on the Database Tier
All scripts listed below are located in
/oracle/iosadesadb/10.2.0/appsutil/scripts/IOSADESA_ioversondb2/adautocfg.sh
Platform Functionality Command
UNIX Start Database listener process addlnctl.sh start SID
Start Database process addbctl.sh start
Stop Database listener process addlnctl.sh stop SID
Stop Database process addbctl.sh stop
Run AutoConfig adautocfg.sh
Windows Start Database listener process addlnctl.cmd start SID
Start Database process addbctl.cmd start
Stop Database listener process addlnctl.cmd stop SID
Stop Database process addbctl.cmd stop
Run AutoConfig adautocfg.cmd
Note: Running AutoConfig might change your existing environment files. After running AutoConfig, you should always set the environment before you run any Applications utilities in order to apply the changed environment variables.
[oracle@ioversondb2 IOSADESA_ioversondb2]$ ./adautocfg.sh
Enter the APPS user password:
The log file for this session is located at: /oracle/iosadesadb/10.2.0/appsutil/log/IOSADESA_ioversondb2/09291835/adconfig.log

AutoConfig is configuring the Database environment...

AutoConfig will consider the custom templates if present.
Using ORACLE_HOME location : /oracle/iosadesadb/10.2.0
Classpath : /oracle/iosadesadb/10.2.0/jdk/jre/lib/rt.jar:/oracle/iosadesadb/10.2.0/jdk/lib/dt.jar:/oracle/iosadesadb/10.2.0/jdk/lib/tools.jar:/oracle/iosadesadb/10.2.0/jdbc/lib/ojdbc14.jar:/oracle/iosadesadb/10.2.0/appsutil/java/xmlparserv2.zip:/oracle/iosadesadb/10.2.0/appsutil/java:/oracle/iosadesadb/10.2.0/jlib/netcfg.jar:/oracle/iosadesadb/10.2.0/jlib/ldapjclnt10.jar
Using Context file : /oracle/iosadesadb/10.2.0/appsutil/IOSADESA_ioversondb2.xml
Context Value Management will now update the Context file

Updating Context file...COMPLETED

Attempting upload of Context file and templates to database...COMPLETED

Updating rdbms version in Context file to db102
Updating rdbms type in Context file to 64 bits
Configuring templates from ORACLE_HOME ...

AutoConfig completed successfully.

3. Commands to maintain System Configurations on the Application Tier
All scripts listed below are located in
COMMON_TOP/admin/scripts/CONTEXT_NAME.
/u02/oracle/iosadesacomn/admin/scripts/IOSADESA_ioversonas2/adautocfg.sh

Platform Functionality Command
UNIX Start Applications processes adstrtal.sh
Stop Applications processes adstpall.sh
Run AutoConfig adautocfg.sh
Windows Start Applications processes adstrtal.cmd
Stop Applications processes adstpall.cmd
Run AutoConfig adautocfg.cmd
Note: Running AutoConfig might change your existing environment files. After running AutoConfig, you should always set the environment before you run any Applications utilities in order to apply the changed environment variables.

[applmgr@ioversonas2 IOSADESA_ioversonas2]$ ./adautocfg.sh
Enter the APPS user password :

The log file for this session is located at: /u02/oracle/iosadesaappl/admin/IOSADESA_ioversonas2/log/09291811/adconfig.log

AutoConfig is configuring the Applications environment...

AutoConfig will consider the custom templates if present.
Using APPL_TOP location : /u02/oracle/iosadesaappl
Classpath : /u02/oracle/iosadesacomn/util/java/1.4/j2sdk1.4.2_04/jre/lib/rt.jar:/u02/oracle/iosadesacomn/util/java/1.4/j2sdk1.4.2_04/lib/dt.jar:/u02/oracle/iosadesacomn/util/java/1.4/j2sdk1.4.2_04/lib/tools.jar:/u02/oracle/iosadesacomn/java/appsborg2.zip:/u02/oracle/iosadesacomn/java

Using Context file : /u02/oracle/iosadesaappl/admin/IOSADESA_ioversonas2.xml

Context Value Management will now update the Context file

Updating Context file...COMPLETED

Attempting upload of Context file and templates to database...COMPLETED

Configuring templates from all of the product tops...
Configuring AD_TOP........COMPLETED
Configuring FND_TOP.......COMPLETED
Configuring ICX_TOP.......COMPLETED
Configuring IEO_TOP.......COMPLETED
Configuring ABM_TOP.......COMPLETED
Configuring ECX_TOP.......COMPLETED
Configuring BIS_TOP.......COMPLETED
Configuring GL_TOP........COMPLETED
Configuring AMS_TOP.......COMPLETED
Configuring CCT_TOP.......COMPLETED
Configuring WSH_TOP.......COMPLETED
Configuring CLN_TOP.......COMPLETED
Configuring OKE_TOP.......COMPLETED
Configuring OKL_TOP.......COMPLETED
Configuring OKS_TOP.......COMPLETED
Configuring CSF_TOP.......COMPLETED
Configuring XNC_TOP.......COMPLETED
Configuring IGS_TOP.......COMPLETED
Configuring IBY_TOP.......COMPLETED
Configuring PA_TOP........COMPLETED
Configuring JTF_TOP.......COMPLETED
Configuring MWA_TOP.......COMPLETED
Configuring CN_TOP........COMPLETED
Configuring CSI_TOP.......COMPLETED
Configuring WIP_TOP.......COMPLETED
Configuring CSE_TOP.......COMPLETED
Configuring EAM_TOP.......COMPLETED
Configuring IMT_TOP.......COMPLETED
Configuring FTE_TOP.......COMPLETED
Configuring ONT_TOP.......COMPLETED
Configuring AR_TOP........COMPLETED
Configuring AHL_TOP.......COMPLETED
Configuring OZF_TOP.......COMPLETED
Configuring IES_TOP.......COMPLETED
Configuring CSD_TOP.......COMPLETED
Configuring IGC_TOP.......COMPLETED

AutoConfig completed successfully.

Completing till this step concludes that this environment can be now rapid cloned. We have all latest AD patches and autoconfig patches applied to the environment and also we have all latest rapid clone patches applied to the environment. Now next step is the actual preparation step for cloning the instance. Stay tuned !!

Preparing the source system for cloning
In this step we will prepare the source file system for cloning. This involves gathering the required configuration information. In a broad way this step will create the staged clone directory which will be having the driver files and configuration file of the source.
6) According to metalink note ID 230672.1, preparing the source system consists of preparing the database side and preparing the appltop side. We need to run adpreclone.pl script on both database side and appltop side. Lets check the details.
6a) Running adpreclone on database side.
cd /oracle/iosadesadb/10.2.0/appsutil/scripts/IOSADESA_ioversondb2
[oracle@ioversondb2 IOSADESA_ioversondb2]$./adpreclone.pl dbTier pwd=apps

[oracle@ioversondb2 IOSADESA_ioversondb2]$ ./adpreclone.pl dbTier pwd=apps
Running Rapid Clone with command...
perl /oracle/iosadesadb/10.2.0/appsutil/bin/adclone.pl java=/oracle/iosa desadb/10.2.0/jdk mode=stage stage=/oracle/iosadesadb/10.2.0/appsutil/clone comp onent=dbTier method=CUSTOM dbctx=/oracle/iosadesadb/10.2.0/appsutil/IOSADESA_iov ersondb2.xml pwd=apps showProgress
Beginning database tier Stage - Tue Sep 29 18:49:58 2009
Log file located at /oracle/iosadesadb/10.2.0/appsutil/log/IOSADESA_ioversondb2/ StageDBTier_09291849.log
Completed Stage...
Tue Sep 29 18:52:11 2009
Completed running perl /oracle/iosadesadb/10.2.0/appsutil/bin/adclone.pl java=/oracle/iosadesadb/10.2.0/jdk mode=stage stage=/oracle/iosadesadb/10.2.0/appsutil/ clone component=dbTier method=CUSTOM dbctx=/oracle/iosadesadb/10.2.0/IOSADESA_ioversondb2.xml pwd=apps showProgress ...

When we run this command on the database side following things happens.
Techstack:
It will create following directories in the ORACLE_HOME/appsutil/clone
drwxr-xr-x 4 oracle01 oinstall 1024 Dec 31 02:00 jlib
drwxr-xr-x 5 oracle01 oinstall 96 Dec 31 02:00 db
drwxr-xr-x 5 oracle01 oinstall 96 Dec 31 02:00 data

“db” will contain the techstack information, “data” will contain the information related to datafiles and required for cloning.
Creates driver files at ORACLE_HOME/appsutil/driver/instconf.drv
Converts inventory from binary to xml, the xml file is located at $ORACLE_HOME/appsutil/clone/context/db/SCMIDC_ap101fam.xml

Prepare database for cloning:
This includes creating database control file script and datafile location information file at
$ORACLE_HOME/appsutil/template
-rwxr-xr-x 1 oracle01 oinstall 4826 Dec 31 02:00 adcrdbclone.sql
-rwxr-xr-x 1 oracle01 oinstall 4508 Dec 31 02:00 dbfinfo.lst
Generates database creation driver file at ORACLE_HOME/appsutil/clone/data/driver
bash-2.05$ ls -rlt
-rw-r–r– 1 oracle01 oinstall 794 Dec 31 02:00 data.drv
Copy JDBC Libraries at ORACLE_HOME/appsutil/clone/jlib/classes12.jar and appsoui

6b) Running adpreclone on appltop side
cd /u02/oracle/iosadesacomn/admin/scripts/IOSADESA_ioversonas2
[applmgr@ioversonas2 IOSADESA_ioversonas2]$ ./adpreclone.pl appsTier pwd=apps

perl /u02/oracle/iosadesaappl/ad/11.5.0/bin/adclone.pl java=/u02/oracle/iosadesacomn/util/java/1.4/j2sdk1.4.2_04 mode=stage stage=/u02/oracle/iosadesacomn/clone component=appsTier method=CUSTOM appctx=/u02/oracle/iosadesaappl/admin/IOSADESA_ioversonas2.xml pwd=apps showProgress
Beginning application tier Stage - Tue Sep 29 18:34:18 2009
Log file located at /u02/oracle/iosadesaappl/admin/IOSADESA_ioversonas2/log/StageAppsTier_09291834.log
Completed Stage...
Tue Sep 29 18:37:23 2009
Completed running perl /u02/oracle/iosadesaappl/ad/11.5.0/bin/adclone.pl java=/u02/oracle/iosadesacomn/util/java/1.4/j2sdk1.4.2_04 mode=stage stage=/u02/oracle/iosadesacomn/clone component=appsTier method=CUSTOM appctx=/u02/oracle/iosadesaappl/admin/IOSADESA_ioversonas2.xml pwd=apps showProgress ...
This will create stage directory at $COMMON_TOP/clone. This goes into two stages
Techstack:
Creates template files for
Oracle_iAS_Home/appsutil/template
Oracle_806_Home/appsutil/template
Creates Techstack driver files for
Oracle_iAS_Home/appsutil/driver/instconf.drv
Oracle_806_Home/appsutil/driver/instconf.drv
APPL_TOP preparation:
-It will create application top driver file
$COMMON_TOP/clone/appl/driver/appl.drv
-Copy JDBC libraries
$COMMON_TOP/clone/jlib/classes111.zip

Copy the file System to target location

Once the application system is prepared for cloning. Next thing that you have to do is to bring down database and listener as well (complete application system is down) and copy the whole application to the location, where you want to create a clone.
You need to copy the following components.

Note: Unix/Linux users, make sure that the softlinks are preserved when copying.

On Application side:

:/u02/oracle/iosadesaappl
Cd $APPL_TOP
Su(pasar a root)
cp -R -f --reply=yes * /u02/oracle/iosatestappl
cd /u02/oracle/iosatestappl
chown –R appltest *

: /u02/oracle/iosadesacomn/html
cp -R -f --reply=yes html /u02/oracle/iosatestcomn/
cd /u02/oracle/iosatestcomn
chown –R appltest html

: /u02/oracle/iosadesacomn/java
Cd /u02/oracle/iosadesacomn/java
cp -R -f --reply=yes * /u02/oracle/iosatestcomn/java

: /u02/oracle/iosadesacomn/util/java/1.4/j2sdk1.4.2_04

/util /u02/oracle/iosadesacomn/util
/clone /u02/oracle/iosadesacomn/clone
/_pages (when this directory exists)
<806> <- Se refiere al directorio 8.0.6 que cuelga de $ORACLE_HOME : /u02/oracle/iosadesaora/8.0.6 : /u02/oracle/iosadesaora/iAS
On Database side (Do a proper shutdown of database (immediate)):
copy DBF files
Su
Cd /u02/oracle/iosadesadata
cp -R -f --reply=yes * /u02/oracle/iosatestdata
cd /u02/oracle/iosatestdata
chwon –R oratest *

copy ORACLE_HOME : /oracle/iosadesadb/10.2.0
Configuring the target system
Once all the copy is done on the target system, you can start your source application system for normal use.
Target system can be configured as given below.
On database side:
cd $ORACLE_HOME/appsutils/clone/bin
perl adcfgclone.pl dbTier

ERROR 1:
Subject: Perl adcfgclone.pl Dbtier Fails with RC-50013 while running instconf.drv
Doc ID: 390302.1 Type: PROBLEM
Modified Date: 21-NOV-2008 Status: PUBLISHED
Cause
The source instance has files that adpreclone flags as 'autoconfigable' but in reality they are not.
So adpreclone.pl adds these files into the instconf.drv. Then when adcfgclone.pl is run on
target it looks for the template file to instantiate for these files and since there isn't a
template file adcfgclone.pl fails.
Solution
To implement the solution, please execute the following steps:
If you are not able to determine which files are causing the issue as per Note 307954.1
then do the following steps

1. Backup file instconf.drv to instconf.drv.old
2. Rename instconf.drv.new to instconf.drv
(This file instconf.drv.new was created during autoconfig phase and is located in same directory \appsutil\driver)
3. Re-try adcfgclone.pl dbtier
ERROR 2 :
Subject:Error Occurred In Applydatabase Rc-50004 on adcfgclone on DB tier
Doc ID: 360343.1 Type: PROBLEM
Modified Date: 05-OCT-2008 Status: MODERATED

This will use the templates and driver files those where created while running adpreclone.pl on source system and has been copied to target system.
Following scripts are run by adcfgclone.pl for configuring techstack
• adchkutl.sh — This will check the system for ld, ar, cc, and make versions.
• adclonectx.pl — This will clone the context file. Because when we copy the application files from source system to target system, we also copy the context file. But this context file wont be of use here. So we need to create a new context file as per the details of this instance. Here hostname, ports and other details will change.
• runInstallConfigDriver — located in $Oracle_Home/appsutil/driver/instconf.drv
• Relinking $Oracle_Home/appsutil/install/adlnkoh.sh — This will relink ORACLE_HOME
For data on database side, following scripts are run
• Driver file $Oracle_Home/appsutil/clone/context/data/driver/data.drv
• Create database adcrdb.zip
• Autoconfig is run
• 7 Control file creation adcrdbclone.sql
On Application Side:
COMMON_TOP/clone/bin/perl adcfgclone.pl appsTier
[appltest@ioversonas2 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 [IOSADESA]:IOSATEST

Target system database server node [ioversondb2]:ioversondb2

Target system database domain name [interoliva.local]:interoliva.local

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

Does the target system application tier utilize multiple domain names (y/n) [n] ?:n

Target system concurrent processing node [ioversonas2]:ioversonas2

Target system administration node [ioversonas2]:ioversonas2

Target system forms server node [ioversonas2]:ioversonas2

Target system web server node [ioversonas2]:ioversonas2

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

Target system APPL_TOP mount point [/u02/oracle/iosadesaappl]:/u02/oracle/iosatestappl

Target system COMMON_TOP directory [/u02/oracle/iosadesacomn]:/u02/oracle/iosatestcomn

Target system 8.0.6 ORACLE_HOME directory [/u02/oracle/iosadesaora/8.0.6]:/u02/oracle/iosatestcomn/8.0.6
RC-00002: Warning: Directory /u02/oracle/iosatestcomn/8.0.6 not found.

Target system 8.0.6 ORACLE_HOME directory [/u02/oracle/iosadesaora/8.0.6]:/u02/oracle/iosatestora/8.0.6

Target system iAS ORACLE_HOME directory [/u02/oracle/iosadesaora/iAS]:/u02/oracle/iosatestora/iAS

Do you want to preserve the Display set to :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]:
12[IMPORTANT: it's the port for connecting to OAS, in my case 8012]

Checking the port pool 12
done: Port Pool 12 is free

Complete port information available at /u02/oracle/iosatestappl/admin/out/IOSATEST_ioversonas2/portpool.lst

Verifying Database Connection...
RC-40201: Unable to connect to Database IOSATEST.

Enter the Database listener port [1521]:

Database Connection on Port 1521: Successful

UTL_FILE_DIR on database tier consists of the following directories.

1. /usr/tmp
2. /oracle/iosatestdb/10.2.0/appsutil/outbound/IOSATEST_ioversondb2
3. /oracle/iosatestdb/10.2.0/appsutil/outbound/IOSATEST_ioversondb2
4. /usr/tmp
Choose a value which will be set as APPLPTMP value on the target node [1]:1

Backing up /u02/oracle/iosatestappl/admin/IOSATEST_ioversonas2.xml to /u02/oracle/iosatestappl/admin/IOSATEST_ioversonas2.xml0.bak

Creating the new APPL_TOP Context file from :
/u02/oracle/iosadesaappl/ad/11.5.0/admin/template/adxmlctx.tmp

The new APPL_TOP context file has been created :
/u02/oracle/iosatestappl/admin/IOSATEST_ioversonas2.xml

Log file located at /tmp/CloneContext_1006012659.log

Running Rapid Clone with command:
perl /u02/oracle/iosatestcomn/clone/bin/adclone.pl java=/u02/oracle/iosatestcomn/clone/bin/../jre/jre mode=apply stage=/u02/oracle/iosatestcomn/clone/bin/.. component=appsTier method=CUSTOM appctxtg=/u02/oracle/iosatestappl/admin/IOSATEST_ioversonas2.xml showProgress contextValidated=true

No write permissions to the Inventory pointed by /u02/oracle/iosatestora/iAS/oraInst.loc: /u02/oracle/iosadesaora/iAS/oraInventory
Rapid Clone needs to be able to write to the inventory

Please run the script /tmp/orainstRoot.sh as root(soluciona el problema y después volver a ejecutar adcfgclone.pl appsTier)
Restart adclone.pl after performing required corrections.

ERROR: Failed to execute /u02/oracle/iosatestcomn/clone/bin/adclone.pl

Following scripts are run by adcfgclone.pl
Creates context file for target adclonectx.pl
Run driver files
$ORACLE_HOME/appsutil/driver/instconf.drv
$IAS_ORACLE_HOME/appsutil/driver/instconf.drv
Relinking of Oracle Home
$ORACLE_HOME/bin/adlnk806.sh
$IAS_ORACLE_HOME/bin/adlnkiAS.sh
At the end it will run the driver file $COMMON_TOP/clone/appl/driver/appl.drv and then runs autoconfig.

eBS4Dummies

Wednesday, October 14, 2009

Maintaining System Configuration:Start,Stop database and tier process

Cloning Oracle Applications Release 11i with Rapid Clone

Followers

Blog Archive

About Me