After setting up a taf service in one of my rac environments i checked if the (local) listener that was configured for the database was showing the services as to be expected. Much to my surprise that was not the case. So puzzled as i was ( after all this was not the first rac I build) I went on to a hunt to find what was going on. In this blog is my share my steps / thoughts how i came to the happy end that of course was out there waiting for me.
In the last quarter of 2012 i have set up a 4 Node Real Application Cluster on Linux which was great to do as always. In day-to-day business I had lost track of this environment which in itself is not that bad of course. However this week I needed the environment as a preparation for patching so it would be mandatory to check with opatch last patch installed in the grid infra structure and in the rdbms homes that have been set up on those boxes. Well it was to be expected that other dbas would work on those boxes, maybe / likely might have installed new patches so it was really like getting back together with old friends to see what was under the hood.
Well it was a bit of disappointment that the inventory destination (/opt/oracle/orInventory) was simply empty . Opatch did not like it either cause it exited with a returncode 73. But then again on the bright side this meant i could take note of the necessary steps performed and turn it into a blog.
Sometimes it is almost funny how old habits indeed seldom die. At the Customers site where I am working there still seems to be a culture in which it is not that common to use Gui solutions offered by Oracle to do day-to-day jobs. In Dutch there is an expression telling unknown things makes things disliked. Well this week i came across nice behavior of the NETCA tool in an environment where Grid Infrastructure 22.214.171.124 is running and I must say I really liked it.
My environment is a four Node Cluster on Redhat Linux 5.5, my Grid Infra structure is 126.96.36.199.0.