This content has been marked as final. Show 3 replies
After upgrading some of our databases to 11.2 which used to be on different machines onto the same new host we realised that one of them had had valid node checking setting with invited nodes list in sqlnet.ora.
Is it possible that we keep this setting for the instance and keep others outside this configuration?
And the use of valid_node and invited_node is pretty lame to begin with. I've always wondered why oracle implemented that in their sqlnet layer at all, since the proper place to do ip filtering is at the router.
So now you have to ask yourself why one instance -- and not the others -- was using it in the first place. The solution to your dilemma will hinge on the answer to that question. It could be that doing IP filtering for a particular instance was valid. However, the decision to do it at the tns layer was wrong-headed, and then moving that instance to a host with other instances who have different requirements only compounded the original error.
Srini Chavali wrote:I'm afraid that solution will just did the hole even deeper. He'd then have to run two listeners, which brings another load of problems and complexity to the table. Yes, it could be made to work, but is really just compounding a fundamental error.
One option you have is to create a separate ORACLE_HOME for this one instance - use the clone capabilities in OUI
As Ed noted, better and more robust alternatives exist