Oracle RAC 12.2 on VMware Workstation – Post 4: Oracle Database Installation and DBCA

This post is also available in:

Series: Oracle RAC 12.2- Complete Installation on VMware Workstation

📌 About this series: This guide covers Oracle RAC 12c, which is out of support. The goal is to document learning and revisit concepts- not to recommend this version for production. Read the full context in the series overview →

📋 This series- Oracle RAC 12.2 on VMware Workstation:

⚙️ Prerequisite: Post 3 completed – Grid Infrastructure installed and cluster with two active nodes (crsctl stat res -t clean).

Install Oracle Database Software 12.2

Prepare the Installer

cd /u01/stage
unzip -q /u01/stage/linuxx64_12201_database.zip

cd /u01/stage
unzip -q /u01/stage/linuxx64_12201_database.zip

After unzipping, the /u01/stage/database/ directory is created with the installer.

orclrac2 doesn’t need to unzip – the OUI copies binaries automatically over SSH.

Run the Database OUI

ssh -X oracle@192.168.15.170

su - oracle
db_env
cd /u01/stage/database
./runInstaller

ssh -X [email protected]

su - oracle
db_env
cd /u01/stage/database
./runInstaller

Step 1- Configure Security Updates

• Uncheck update notifications – click Next and confirm

Step 2- Installation Option: Install database software only

Step 3- Grid Installation Options: Oracle Real Application Clusters database installation

Step 4- Nodes Selection: check orclrac1 and orclrac2

Step 5- Database Edition: Enterprise Edition

Step 6- Installation Location:

Step 7- Operating System Groups:

Step 8- Prerequisite Checks– see Known Errors section

Step 9- Summary → Install

Run root.sh

Can be run on both nodes simultaneously:

/u01/app/oracle/product/12.2.0/dbhome_1/root.sh

/u01/app/oracle/product/12.2.0/dbhome_1/root.sh

Create the RAC Database (DBCA)

ssh -X oracle@192.168.15.170

su - oracle
db_env
dbca

ssh -X [email protected]

su - oracle
db_env
dbca

All 16 DBCA Screens

Step 1- Database Operation: Create a database

Step 2- Creation Mode: Advanced Configuration

Step 3- Deployment Type:

Admin Managed: the DBA controls which nodes run the database. Custom Database: fully manual configuration- more educational.

Step 4- Nodes Selection: orclrac1 and orclrac2

Step 5- Database Identification:

SID Prefix ORCL automatically generates ORCL1 on orclrac1 and ORCL2 on orclrac2.

Step 6- Storage Option:

Step 7- Fast Recovery Option:

34000 MB ensures the size fits within the available space of the +FRA disk group (40 GB). Archive Log Mode is configured automatically by DBCA.

Step 8- Database Options:

Step 9- Configuration Options:

Memory tab:

Do not use AMM in RAC– it uses HugePages inefficiently.

Sizing tab:

Block size cannot be changed after database creation.

Character sets tab:

AL32UTF8 cannot be changed after database creation without rebuilding or migrating.

Connection mode tab: Dedicated Server Mode

Sample schemas tab: unchecked

Step 10- Management Options:

Step 11- User Credentials:

• Use the same administrative password for all accounts
• Password: Welcome1

Step 12- Creation Option: Create database ✅ checked

Step 13- Prerequisite Checks: see Known Errors

Step 14- Summary → Finish

Step 15- Progress Page: wait for completion

Step 16- Finish → Close

Known Errors

Swap Size / NTP / Clock Synchronization- Failed or Warning

Cause: Same checks as Grid. If swap and chrony were configured correctly in Post 2, these checks should pass. If they still fail, close the OUI, confirm chronyc sources, and reopen.

Temporary fix: Check Ignore All and proceed- does not affect database functionality.

resolv.conf overwritten after reboot

Symptom: resolv.conf Integrity check fails in the Database OUI after a reboot.

lsattr /etc/resolv.conf
chattr +i /etc/resolv.conf

lsattr /etc/resolv.conf
chattr +i /etc/resolv.conf

[DBT-06604] Fast Recovery Area- insufficient free space

Symptom: DBCA reports that +FRA does not have enough space for the configured size.

Cause: The configured FRA size exceeds the available space in the disk group.

Fix: Reduce the Fast Recovery Area size in Step 7 to a value below the available free space in +FRA. Use 34000 MB to ensure a safe margin.

Next Up

In Post 5 we’ll validate the complete environment and have a quick reference for day-to-day commands.