use of EXEC FND_CONC_CLONE.SETUP_CLEAN

Cloning of Oracle Application

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
Note:

Be careful not to run this on production, it cleans out all printer  definitions, previsously executed requests logs and outputs. It is okay to run  only on the freshly created environment.

And there after follow the doc Metalink note: 230672.1

--------------------------------

APPS - how to cleanup FND_NODES table to clear corrupted setup  ## ## before cleanup ##  13:42:56 APPS@XTPR:host01> r   1  select node_name, node_mode, support_cp,   2          support_web, support_admin, support_forms   3*         from FND_NODES  NODE_NAME                      N S S S S ------------------------------ - - - - - HOST01                         O Y N Y N MIDTIER01                      O N Y N Y APPSERVER21                    N Y N Y   <-- bogust host APPSERVER22                    N Y N Y   <-- bogust host APPSERVER23                    N Y N Y   <-- bogust host AUTHENTICATION                 O N N N N  6 rows selected.    ## ## Cleanup ##  13:42:58 APPS@XTPR:host01> EXEC FND_CONC_CLONE.SETUP_CLEAN;  PL/SQL procedure successfully completed.  13:44:12 APPS@XTPR:host01> commit;  Commit complete.  ## ## After cleanup ##  13:44:47 APPS@XTPR:host01> r   1  select node_name, node_mode, support_cp,   2          support_web, support_admin, support_forms   3*         from FND_NODES  no rows selected  ## ## Run AutoConfig ##  ## BE tier $AD_TOP/bin/adconfig.sh contextfile=$APPL_TOP/admin/XTPR_host01.xml appspass=   ## MT tier $AD_TOP/bin/adconfig.sh contextfile=$APPL_TOP/admin/XTPR_midtier01.xml appspass=   ## ## After AutoConfig runs ##  13:58:15 APPS@XTPR:host01> r   1  select node_name, node_mode, support_cp,   2          support_web, support_admin, support_forms   3*         from FND_NODES  NODE_NAME                      N S S S S ------------------------------ - - - - - MIDTIER01                      O N Y N Y AUTHENTICATION                 O N N N N HOST01                         O Y N Y N  3 rows selected.

Source :--http://karmadba.blogspot.com/2007/04/cloning-of-oracle-application.html

http://kb.dbatoolz.com/tp/1179.apps_-_how_to_cleanup_fnd_nodes_table_to_clear_corrupted_setup.html