Steps to Clean Nonexistent Nodes or IP Addresses from FND_NODES

After completing the ADCLONE process, or implementing Autoconfig,
the FND system tables have incorrect values.

If a clone was done, the OAM Dashboard reflects the target machine name and the
source machine name although the source machine is no longer being used.

In some cases, there are IP addresses from nonexistent machines in FND_NODES.
The Nodes in the OAM Dashboard are retrieved from the FND_NODES table. Further
investigation showed that the FND_NODES table had both node names and node_modes
'O' as activated.
ie:

SQL> select node_name "Node Name", node_mode "Mode", support_cp "C",
support_web "W", support_admin "A", support_forms "F"
from FND_NODES;

NODE_NAME N S S S S
------------------------------ - - - - -
TARGET O Y Y Y Y
SOURCE O Y Y Y Y


NOTE:
=====
Do not directly Delete from FND_NODES table because the
'support_' columns will be affected and will not
incorporate the correct information througout in OAM.

The data cleanup issues with cloning that surface in the OAM UI have been fixed in the latest
cloning patches.

1) Retrieve the latest patch for the cloning tools.
(Currently TXK AUTOCONFIG ROLLUP PATCH Q (JUL/AUG 2007) 5985992)

2) After applying the above patch to the system that is to
be cleaned, run the following in SQL*Plus:
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;

3) Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers,
to repopulate the required system tables.
Note that step two will delete all data from system tables
such as FND_NODES, FND_OAM_CONTEXT_FILES, etc. The correct
information for the current system will be repopulated when
AutoConfig is run.