Installing the Listener
The DBCA needs the listener process so you need to configure that before
running DBCA. I usually use the same node to start the Network Configuration
Assistant (netca). This you have to do on ONE NODE only. All the changes are
replicated to the other nodes. Make sure to check the environment variables. If
your environment variables aren’t (for whatever reason) set properly, your
attempt to run netca will fail.
Starting up the netca is easy. While logged in with your. oracle user account do the following:
$ netca &
Choose "Cluster configuration", click on next:
You will see all the available nodes. (Again having your clusterware running
is crucial, or else you won’t see them all). Click "select all nodes" and then
click on next:
You are presented with several options. We will go ahead and configure
Listener. Click on next:
Click "Add" and click on next:
You get a default option "LISTENER" but you can choose whatever name you
like. Click on next:
Here we pick TCP and click on next:
You can choose other port numbers as well but we will stick to the default
port 1521. Click on next:
Select "No" when prompted to configure another listener, and Click on next:
I think it is crucial to also talk about issues like these. I guess the
cluster may have gotten out of sync (lack of adequate resources?) and I got
this error. I tried again and it was fine.
Click on next:
We will also configure the "Naming Methods configuration", Click on next:
I kept Local Naming on top, Click on next:
Click on next:
Click on Finish and we are all set for DBCA.
Conclusion:
Here we did
the database software only installation and the listener setup. I know it seems
easy but I have received (and keep getting more) emails on how things don’t
work. I do try to address those issues from users on my OraclePerf blog. I will be blogging
more about oracle performance and other trouble shooting issues. In the next article,
we will continue with the database creation.
»
See All Articles by Columnist Tarry Singh
» 
