Installing 10gR2 Database Software

Thursday Jul 20th 2006 by Tarry Singh

Part 14 of RACing ahead with Oracle on VMware covers the database software only installation and the listener setup.

A Brief Pep talk: How does virtualization change the Oracle ballgame

I keep getting offers all the time--contracts in which I have to install databases (RAC or Standard) for clients. Every time, I have to go through the rigmarole of preparing and then installing the database. It is good, it pays me well per hour, but is it smart? I don’t think so. VMware’s virtualization with VI3 changes all that.

I know I have mentioned it, but writing this article made me think about it again. Just imagine I create an Oracle template for Solaris 10, Redhat, SuSe, Centos, Windows and I am done. All I have to do is to deploy the template on the client site. I am done in no time. My client saves money, I save time and have time left to attend to more clients. Saving cash and improving the cash flow process can change and accelerate the pace of adoption. Such marketbusting strategies complemented with breakthrough technologies like those offered by VMware are especially needed in today’s world.

Getting on with Installing database

The previous article discussed the Clusterware installation. Here we will cover installing the database only software. This means that we will do the DBCA and the rest later. Before you run the runInstaller, check the following:

Login as root and run xhost command as root This is to allow for X Server connections (remote connections). Then make sure to be logged in as Oracle user with the oracle user account:

# xhost +
access control disabled, clients can connect from any host
# su - oracle

Also, go ahead and verify the environment variables on all candidate nodes.

$ env | grep ORA

Similarly, go ahead and do the same on all the nodes.

OK now we are all set, so go to your installation folder. In our case, it was the orasoft, and do the following.

$ /u01/app/oracle/orasoft/database/runInstaller

You can also flag it with –ignoreSysprereqs if you have RAM limitations on your physical box. The prerequisites check does often complain (as you will see later on my installation) if you want to install your RAC on a laptop with 1G memory, for instance.

Database Only Installation

Welcome, click on next:

Select the installation type--here we go ahead and take the whole Enterprise Edition. These days its just one cd. I remember back in 7/8 days, it used to be ¾ cds. Click on next:

Specify Home Details. We will pick the default chosen by the installer, but you can pick anything, especially when you have company specific installation guidelines.

Specify Hardware Cluster Installation Mode. Here the cluvfy (in the background) picks up all the available machines. Hoes it do it? You guessed it right. It was your clusterware (meaning all the clusterware daemons), which was running. It goes without saying that you need to check that your clusterware is running before you start with the installer. Check all the machines. Note that you can also carry out a non-cluster installation. Click on next:

Product-Specific Prerequisite Checks. This is what I mentioned; as you can see, my swap was the problem. I had little space on my disk as well but never mind, we will ignore it for installation purposes. Click on next:

Select the Configuration Option. We choose database software only. We will do the database installation later on. Click on next:

You are presented with a summary. All seems fine. Click on install:

Installation progresses. This may take some time, but usually in a few minutes, you are all set.

I personally like to check the progress and occasionally I check the log file too, to see if everything is going as planned.

The installation process completes and you are prompted to run the root.sh script. Do not forget to run the root.sh script on ALL NODES! Start with the node you ran the installation on. Navigate to the directory where it is located and run root.sh. You must be logged in as root in a new console to do this.

AS you can see, it sets the Owner and Home variables. The local/bin path name is usually default but do check with your sysadmin to see if it fits according to your company installation guidelines. It also creates the oratab file. Click OK only after having done the same on ALL NODES.

Now go ahead and do the same on all nodes. After you are done, you can exit your GUI.

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.


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

Mobile Site | Full Site