Autoconfig in r12.2

[Sri]

Dear erman,

Is the below holds true?if yes, what is the correct order to execute autoconfig in 5 node environment with shared appltop 2 node for pcp and rest of 3 nodes for web services.

Lets assume that there are 2 Concurrent Manager (CM) nodes called ‘Node A’ and ‘Node B’.
The FND_NODES table is cleaned via the API FND_CONC_CLONE.SETUP_CLEAN as part of post clone.
1. When AutoConfig is run on Node A:
a. FND_NODES is populated with Node A information.
b. tnsnames.ora file on Node A will have an FNDSM entry for that node only, as the application has no information for Node B yet.
2. When AutoConfig is run on Node B:
a. FND_NODES is populated with Node B information.
b. tnsnames.ora file on Node B will have FNDSM entries for Node A as well as Node B.
In order to have a FNDSM entry for Node B in the tnsnames.ora file of Node A, AutoConfig has to be run again on Node A, because the application now has the information about Node B.

Thank you

[ErmanArslansOracleBlog]

There is a rule called 2n-1.

If you have a multi node EBS apps tier, AutoConfig has to be run '2n - 1' times. In other words;   for an application which has 'n' number of application nodes, AutoConfig has to be run '2n - 1' times so that the tnsnames.ora file on each node has FNDSM entries for all the other nodes.

Read this -> https://ermanarslan.blogspot.com/2018/08/ebs-migration-2-interesting-problems-2.html

and this -> Reference: AutoConfig Does Not Populate tnsnames.ora With FNDSM Entries For All The Nodes In A Multi-Node Environment (Doc ID 1358073.1)

[ErmanArslansOracleBlog]

So, also "There is no need to run AutoConfig twice on the node where AutoConfig was run last during the first phase."

But, remember -> This is a one-time activity to populate FND_NODES with information for all the nodes. When you need to populate the FND_NODES.

This means, after populating the FND_NODES properly (for instance after cloning) by following the 2n-1 rule , you are okay.
For future autoconfig taks, you just need to run AutoConfig once on each node.

[ErmanArslansOracleBlog]

And this rule is related with the Service Manager.
So, you need to follow this rule on the nodes where your Service Manager is running.

As I understand from your statement, you have only 2 nodes for CM and probably you have 2 nodes for FNDSM.

This means, you need to execute the autoconfig in the following order;

cmnode1
cmnode2
cmnode1

But, again this is only for one time!

[Sri]

Dear erman,

Thanks for the update.But if you have 4 nodes,2 for CM and 2 for webnodes,is there any specific order for autoconfig,something like to  execute last on web nodes as these will have web profiles to get updated at site level.

Please clarify

Thank you

[ErmanArslansOracleBlog]

This 2n-1 is about FNDSM and it is about populating FND_NODES when it is empty.
 
As for your Web node-related question,  read -> After a multi Nodes installation running Autoconfig On Concurrent Node Updates Web Related Values (Doc ID 1447216.1)

Finally, as for the order of running autoconfig; my answer is -> There is no order for running AutoConfig on application nodes. Autoconfig on application nodes can even be executed in parallel. (ex: adconfig.pl contextfile=$CONTEXT_FILE -parallel )