1. If
your target server holds at least one Oracle Apps R12.1.3 instance, you can
skip for any OS patch or software requirement section. As the server is running
a Oracle Apps instance, we can assume the server has all the
mandatory OS patch
and required software. Else look into the metalink for platform specific
requirements.
2. Apply
Latest AD patch
Check
whether AD patch version is atleast R12.AD.B.3. You can check that using
following query.
SELECT patch_level FROM fnd_product_installations WHERE patch_level LIKE'R12.AD%'
If it is
below that level apply patch 9239089.
3. Apply
the latest AutoConfig template patch
Update
the Oracle Applications file system with the AutoConfig files by applying the
latest AutoConfig Template patch (Patch 9386653 for 12.0.X customers and Patch
8919489 for 12.1.X customers) to all application tier nodes in the Applications
instance. You can check whether this patch is already there or not in your
system by the following sql.
SELECT * FROM ad_applied_patches WHERE patch_name = '8919489'
9833058:R12.OAM.B
HOT CLONE FAILS WITH ORA-00201 DURING RECOVERY MANAGER
12404574:R12.OAM.B
ORACLE_HOME REGISTRATION DOES NOT HAPPEN WITH CENTRAL INVENTORY ON LOZ
12598630:R12.OAM.B
R12.1 ONE-OFF FOR S_DB_LISTENER BUG 12362010
5. Run
AutoConfig on the application tiers
Follow
the steps under section " Run AutoConfig on the Application Tiers "
in My Oracle Support Knowledge Document 387859.1 to run AutoConfig on all
application tier nodes.
6.
Synchronize appsutil on the database tier nodes
Follow
the steps under section "Copy AutoConfig to the RDBMS ORACLE_HOME" in
My Oracle Support Knowledge Document 387859.1 to copy AutoConfig and Rapid
Clone files to each database node via the admkappsutil.pl utility.
7. Run
AutoConfig on the database tier
Follow
the steps under section "Run AutoConfig on the Database Tier" in My
Oracle Support Knowledge Document 387859.1 to run AutoConfig on the database
tier nodes.
8.
Maintain Snapshot Information
Log in to
each application tier node as the APPLMGR user, and run "Maintain Snapshot
Information" in AD Administration. To update the snapshot, please select
the following options "Update Current View Snapshot" and "Update
Complete APPL_TOP".
Cloning
Steps
9.
Prepare the source system
Execute
the following commands to prepare the source system for cloning.
Prepare
the source system database tier for cloning
Log on to
the source system as the ORACLE user, and run the following commands.
$ cd
[RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]
$ perl
adpreclone.pl dbTier b.
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
[INST_TOP]/admin/scripts
$ perl
adpreclone.pl appsTier
10.
Shutdown the source system. Copy full directory "apps" and
"db" from source system to target system. Use the following command
for copy.
$ cp
-RH
11.
Configure the target system
Run the
following commands to configure the target system. You will be prompted for
specific target system values such as SID, paths, and ports.
a.Configure
the target system database server
Log on to
the target system as the ORACLE user and enter the following commands.
$ cd
[RDBMS ORACLE_HOME]/appsutil/clone/bin
$ perl
adcfgclone.pl dbTier b.Configure the target system application tier server
nodes
Log on to
the target system as the APPLMGR user and enter the following commands:
No comments:
Post a Comment