Pre Clone Steps

The Action Plan involved applying a Patch followed by the Pre clone steps to
Update the database codes...

As per my understanding the pre clone steps have been run and most of the code levels have been updated.

As customer wanted a new patch which involves autoconfig run (Implying template file changes)
the pre clone run was also suggested.

Steps
=============
Update all database tier nodes with the code level-->

1. On the Application Tier (as the APPLMGR user):
Source the environment variables for Oracle ApplicationsUNIX:. .//APPS.env
Run AutoConfig on the APPL_TOP
Execute admkappsutil.pl utility to create the file appsutil.zipperl /bin/admkappsutil.pl
This will create appsutil.zip in $APPL_TOP/admin/out

2. On the Database Tier (as the ORACLE user):
Source the environment variables for RDBMS ORACLE_HOME
UNIX:cd . .//.env

Copy or FTP the appsutil.zip file to the Uncompress appsutil.zip under the cd unzip -o appsutil.zip
Run AutoConfig on the

Pre clone-->
3. Re-run adpreclone.pl on the dbTier and appsTier
wrning:Since new updates included on this patch have been applied to the system,
Adpreclone must be executed again in order to apply them into the clonedirectory structures used during cloning.
perl adpreclone.pl dbTier
perl adpreclone.pl appsTier

Note few points we found
Preclone step 3 is self explanory for my understanding of the Action plan....
and the preclone run finished much too faster in almost 2 minutes both db & the 3 mts.
(usualy we know how long it runs --implying preclone after its first run will automatically pick
only those codes updated recently and update the stage area)
&
we can run the adpreclone online and all services can be brought up after the autoconfig run to sync the Db & MTs.

Will be interested for Ur views and Hope u guys can add More information***