FNDSM Entries missing in tnsnames.ora after running autoconfig.   Leave a comment

Cloning Issue:

While cloning we always have this issue on our non-prod environments, as we have two concurrent manager nodes.

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.

I hope this is clear!

Advertisements

Posted October 5, 2013 by balaoracledba.com in Cloning, Issues

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: