Oracle name resolution on servers with multiple SIDs

[Former Member]

On servers with multiple SIDs we have a principle that we run only one listener on the server which is always running from the highest version of oracle. During upgrade process we are sometimes getting into issues regarding Oracle names resolution because resources working on upgrade sometimes make mistake in determining proper SID from which listener is running resulting in problems with oracle connectivity (they edit listener.ora and tnsnames.ora in wrong location - ORACLE_HOME). I am interested if there is recommendation for better setup on servers running different SIDs?

I have received comment from my customer that this can be solved by having central location of listener.ora and tnsnames.ora where these files would be maintained, while all SIDs would have soft links from their $ORACLE_HOME/network/admin to this central location.

[former_member204746]

your customer is right,

if on unix, you can create a symbolic link like this:

mv $ORACLE_HOME[2]/network/admin $ORACLE_HOME[2]/network/admin.old

ln -s $ORACLE_HOME/network/admin $ORACLE_HOME[2]/network/admin

replace $ORACLE_HOME[2] with the one you DO NOT want to use.