AutoConfig Does Not Populate tnsnames.ora With FNDSM Entries For All The Nodes In A Multi-Node Environment
Last updated on SEPTEMBER 06, 2016
Applies to:Oracle Applications Technology Stack - Version 220.127.116.11 to 12.1.3 [Release 11.5.10 to 12.1]
Oracle Applications Manager - Version 18.104.22.168 to 12.1.3 [Release 11.5.10 to 12.1]
Oracle Concurrent Processing - Version 22.214.171.124 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 27-Jun-2013***
As part of the post-cloning process or sometimes to remove the non-existent node information from the FND_NODES table, we need to clean it via the API FND_CONC_CLONE.SETUP_CLEAN.
After that when AutoConfig is run to populate the FND_NODES table on a multi-node environment, it does not populate tnsnames.ora file with the respective FNDSM entries for all the nodes.
When AutoConfig is run on the first node, the FND_NODES table obviously does not contain the details for the other nodes. So obviously, the tnsnames.ora will contain FNDSM entry for the first node only.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms