It is possible to automate the cloning process in Oracle E-Business Suite 12.2. This presentation discusses how to accomplish that and gives some warnings about when it is not possible to run a clone.
For OAUG members, the slides and a recording of the presentation are available on www.oaug.org.
Handwritten Text Recognition for manuscripts and early printed texts
Automating Your Clone in E-Business Suite R12.2
1. Session
ID:
Prepared by:
Automating Your Clone in E-
Business Suite R12.2
Best of Collaborate
22-AUG-2017
Best of Collaborate
Michael Brown, BlueStar
@MichaelBrownOrg
This could be a single node.
Starting with the target machine(s) up and running and configured to run the EBS/DB and prepared source
DB Oracle Home is copied
Database is copied (there may have been a configuration step here, but will be discussed later)
Configure the database tier. You now have a working copy of the database.
Copy the apps tier (copy could actually be concurrent with other copies). It is not needed until after the target db is configured.
Configure the applications on the target
You now are running a copy of the source system.
There are some extra steps involved when cloning 12.2. I will attempt to point these out throughout the presentation.
This can be a major impact on how your business is currently run.
I have started using ADZDSHOWED.sql because this should continue to work even if Oracle changes the codes in ad_adop_sessions, although I may have to worry about them changing PATCH as the edition name. Every time you update the AD/TXK patches, make sure your method of detection still works.
Can normally skip unless configuration changes have been made, e.g. patches.
I always run on apps tier
12.2 change is because of WLS
DB Oracle Home is copied
Configure the Oracle Home
Don’t expect to be able to shutdown for clones. Bad idea to shutdown regularly in any case
Get a working database up using the newly configured oracle home
Configure the database tier. You now have a working copy of the database.
Single Sign On will not configure correctly without adupdlib
We did a little handwaving at this point, so let’s talk about how you get this clone done.
Headless can just automatically catalog the backup location or can use a catalog connection.
If this works, you know you can restore your source in a disaster
rman handles creating the control file as well as restoring and recovering the database
initDEV.ora.dup means it will be saved as I like it for cloning
You can just do file copies when in backup mode, but if you are using copies, really should switch to rman
This is instead of
We will go into more detail when we talk about automating the process
Copy the apps tier (copy could actually be concurrent with other copies). It is not needed until after the target db is configured.
cp –RH preserves links on most Unix systems. rsync is my tool of choice (rsync uses ssh by default on most current Linux releases)
Suggestion NFS mount from the database node to the applications node
I disable all alerts, put concurrent requests on hold except for a defined set of users. JAR files will still be signed correctly if using the same code signing certificate, but you must put it back in place in the $INST_TOP (both tiers or run FS_CLONE)
This needs to be run on the source before cloning to the target
12.2 replaces this with just the instance name as part of configuring the apps tier. You need to run this as a post apps tier clone step if you want the source to be kept
You can copy what you need or use disk technology to get it all and then cleanup