Time Required: 60 minutes
- Oracle 11gR2 Database software
Next we are going to install the Oracle Database 11gR2 software.
This is the last part of our ten-part process of installing a two node RAC on VMware Workstation 8.
To begin, download the zip file from the Oracle software download website and unzip on Orpheus. Make sure you are logged into Orpheus as the oracle user so that oracle owns the unzipped files.
There are two zip files for 11gR2 Linux 64-bit called linux.x64_11gR2_database_1of2.zip and linux.x64_11gR2_database_2of2.zip.
Unlike with older released where each file would be unzipped into a different directory, with 11g both zip files need to unzipped into the same directory. If you fail to do this the install will fail with a spectacularly unhelpful error message about half way through.
Having unzipped the files, we should have a directory called database. It is important to be logged into Orpheus through the VM desktop and not through a non graphical interface such as Putty or SecureCRT. You may also use a tool such as VNC.
Change into the database directory and we will find a script called runInstaller.
We will launch this script as follows:
[oracle@orpheus database]$ ./runInstaller &
This will start the graphical installer and present the following menu:
Since this is not production I leave the email address blank and uncheck I wish to receive security updates via My Oracle Support. The installer demands confirmation of this stance before proceeding to the next screen.
Select Create and configure a database
At the next screen select Server Class
At the next screen select Real Application Clusters database installation and ensure both Orpheus and Eurydice are checked.
At the next screen select Advanced install
At the next screen select the languages you want to install. Since I am happy with just English I will just click Next
At the next screen select Enterprise Edition (4.29GB).
At the next screen choose where to install the Oracle Base and the Database home. The Base should match the same one you used in Part IX. Unlike the Grid install, the database home is fine being installed under the base directory structure.
At the next screen select General Purpose/Transaction Processing.
At the next screen you get to name your new database. I have chosen to name my database amore, after the spirit that guides Orpheus and Eurydice out of Hades. Since I choose to use a domain name of hadesnet my fully qualified database name is amore.hadesnet.
At the next screen we can set the memory size and management, the characterset, security policies and sample schemas of the new database. I choose all defaults but I do choose to install the sample schemas.
At the next screen select Use Database Control for database management.
At the next screen select Automatic Storage Management, and enter the password you set for the ASM database back in Part IX.
At the next screen select Do not enable automatic backups.
At the next screen select the DATA disk group for the new database.
At the next screen select Use the same passwords for all accounts and enter a password to use. Since this is for demo purposes I choose something very simple like oracle. The installer will object but you can override it and continue.
At the next screen we get to set the OS groups for the OSDBA and OSPER privileged functions. In this case I simply use DBA for both.
At the next screen you can review the settings you have provided. If everything looks good then you can select Finish
The installer process will now install the database software on all nodes.
After the software install completes the DBCA tool launches to create our sample database.
When the DBCA tool completes it will offer the ability to set passwords and unlock accounts.
At the conclusion of the install process, the installer prompts to execute root.sh scripts on all nodes. Open a terminal window and log in as root to execute the scripts:
[root@orpheus grid]# cd /u01/app/oracle/product/11.2.0/dbhome_1 [root@orpheus dbhome_1]# ./root.sh Running Oracle 11g root.sh script... The following environment variables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /u01/app/oracle/product/11.2.0/dbhome_1 Enter the full pathname of the local bin directory: [/usr/local/bin]: The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n) [n]: y Copying dbhome to /usr/local/bin ... The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n) [n]: y Copying oraenv to /usr/local/bin ... The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n) [n]: y Copying coraenv to /usr/local/bin ... Entries will be added to the /etc/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root.sh script. Now product-specific root actions will be performed. Finished product-specific root actions. [root@orpheus dbhome_1]#
Repeat the process on Eurydice. Then press OK
The final screen shows us the URL of the Enterprise Manager interface. Click Close to complete the install.
The process is now complete. Congratulations if you made it this far. I don’t know about you, but I am certainly ready for a drink!
|Article Quick Navigation|
|Previous Step||Main Index||Next Step|