As a part of standards every (RAC) database has its own listener in my projects. This week i was asked to alter the local listener to a different port to keep it similar to a specific port that I used on other database(s) in that project.
Technically this was Of course a little effort 2 be made to keep everybody happy.
I altered my listener.ora (yup still an old-fashioned kind of guy) manually and I stopped and started the listener:
srvctl start listener -l listener_mydb1
srvctl status listener -l listener_mydb1
And in the database i had altered the local_listener too to show new ports well. And of course I altered the tnsnames entry too. So I had it all covered i thought. That was only until the moment that I checked the listener for that database for its status. And much to my surprise I saw this.
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.
General: Configuring Active/Passive Clustering for Oracle Database ( Single Instance in Crs)
The Oracle database can easily be configured to use the Cluster ware framework for high availability.
Using Grid Infrastructure to protect a database resource is a very cost-effective way of setting up an Active/passive cluster. As an added advantage, using only one vendor’s software stack to implement the cluster can make troubleshooting easier. Staff already familiar with RAC will easily be able to set up and run this configuration because it uses a same software stack: all commands and log files are in familiar locations, and troubleshooting does not rely on the input from other teams.
To set up an active/passive cluster with 11g Release 2, you need to initially install Grid Infrastructure on all nodes of the cluster. Grid Infrastructure will give the user with a cluster logical volume manager: ASM. If for some reason another file system is required, you can choose the supported cluster file systems, including ACFS. Using a cluster file system that is mounted concurrently to both cluster nodes offers the advantage of not having to remount the database files and binaries in case of a node failure. Some configurations we saw suffered from extended fail over periods caused by required file system checks before the file system could be remounted.
On top of the Grid Infrastructure build, you do a local installation of the RDBMS. It is important that you do not choose a cluster installation when prompted so; otherwise, you risk violating your license agreement with Oracle.