Post Clone
Steps In Oracle Applications
The cloning
process has traditionally been a manual process performed by DBAs. This process
involves copying over the database files – preferably using RMAN DB duplicate,
the tech stack, and the application tier to the non-production servers,
converting them to DEV or TEST, and then performing a number of post clone
steps such as disabling workflow emails from going to end users, scrambling
financial information, updating the clone date and the instance name within the
apps heading, editing the custom top, changing passwords, and others. Depending upon the size and configuration the
cloning process can take from 12 hours to 48 hours on average.
The number
of post clone steps can get to be quite numerous and even with the best of
documented procedures; one or two steps can easily be missed.
Note:- the following is a list of steps in one
particular cloning environment, It may vary based on environment.
1. Once the
cloned database is renamed, add all the temp datafiles to the TEMP tablespace.
2. All key
passwords need to be updated from their production values to the appropriate
values for the DEV environment. (ie: sys,system, sysadmin,apps)
3. Custom
database directories need to be re-created with the correct paths for the DEV
server.
4. Specific
Profile options need to be re-defined – like the apps heading naming the
instance and the date stamp of the clone.
5.
End-dating specific users so that only the desired developers have access to
the instance.
6.
Removing/scrambling specific private HR data.
7. Nulling
out specific email addresses to prevent workflow from emailing end-users from
the DEV instance.
8. Putting a
hold on all regularly scheduled production concurrent requests in the DEV
instance.
9. Updating
all profile option values, swapping out the prod instance name for the DEV
instance name. Additional updates for the server names also run.
10. Updates
for all custom environment code paths and settings.
11. Updates
for any and all printer setting changes.
