This is one of the most usual tasks given to Apps DBA and from my past exp., DBA's spend more than 70% of time in Cloning.
Cloning Oracle Apps 11i is done through a tool given by Oracle known as RAPID CLONE and it is very easy to use but it does not do all the bits....
When u clone the env, there is a ref of the source env in the database in FND_NODES tables , thus after clone if u visit the OAM page , u will see both source nodes and target nodes . Also u will be some concurrent managers which have got ref to source nodes.
If u want to get rid of the source nodes , Do the following :Follow the Rapid clone document (Metalink note : 230672.1)
- Prepare the Source System ( Pre Clone Steps )
- Copy the Source System to the Target System
- Configure the Target System
o Configure the target system database server
o After the database is created ,connect as apps and execute the following
EXEC FND_CONC_CLONE.SETUP_CLEAN;
Commit;
o Above cmd will clean the FND_NODES table and does something more than that i.e.
c lear the concurrent manager tables etc.
o Run the autoconfig.sh again on the database tier
And there after follow the doc Metalink note: 230672.1
3 comments:
good one. will it resolve after cloning issues. if not plz send after cloning issues u have faced with brief description.
Hi,
I have done the Database Refresh of development instance from the
production by copying all the datafiles, recreating control file and opening database in resetlogs.
Now I just want to know, which all tables, and files we should manually update ?
Please help me .
The package fnd_conc_clone.setup_clean is meant to drop topology of Apps and when you run AutoConfig it will populate with all the information. The package drops not only fnd_nodes but other Apps tables also releated to Apps configuration like tns entries, Oracle Homes ...etc
Post a Comment