R12.2 Update "Site Name" as Postclone Step
Updating the Sitename in 11i was easy. We could modify the parameter with a SQL script in a set of postclone scripts, and it would be updated for good until we cloned again, as that profile option determined the sitename.
Now in R12.2, sitename is controlled by s_sitename in the $CONTEXT_FILE, and it is set to the instance name when rapid clone is run.
Why Does ADOP Change the Site Name of the E-Business Suite? (Doc ID 2002220.1) | |
Our context files are not shared, so having two application nodes and two concurrent management nodes, we now have four locations that have to be updated as a postclone step. This took no effort at all in 11i, and now can be quite time consuming for R12.2.