Installing Oracle Database 11g R2 on Linux with ASM

In this guide i am going to cover Oracle Database 11g R2 installation on Linux with ASM.

Automatic Storage Management (ASM) is a feature that has be introduced in Oracle 10g to simplify the storage of Oracle datafiles, controlfiles, logfiles and backups. ASM will be used as the file system and volume manager for Oracle Database files (data, online redo logs, control files, archived redo logs), and the Fast Recovery Area. In this case, i'm going install GI first ,then Database software and Database instance.  In another blog , i will discuss, how to install Grid Infrastructure (GI) into the existing Database system.

Steps to setup action plan:

1. Creating virtual hard disks in VMware for ASM disks

2. Installing Oracle Enterprise Linux

3. Creating recommended OS groups and user for Grid Infrastructure

4. Configure and checking few basic files from root user

5. Creating login scripts for grid and oracle users

6. Installing Oracle ASM packages

7. Creating ASM disk volumes

8. Downloading and installing Oracle Grid Infrastructure software

9. Creating ASM disk groups

10. Installing Oracle database software and create database instance

Step-01: Creating virtual hard disks in VMware for ASM disks

1. CRSDISK1 (2 GB) – for CRSVOL1 disk where Cluster Ready Services (CRS) files will be stored. CRS provides many system management services and interacts with the vendor clusterware to coordinate cluster membership information.

2. DATADISK1 (20 GB) – disk for DATAVOL1 disk. Here database will keep all datafiles, control files, log files …

3. FRADISK1 (10 GB) – disk for FRAVOL1 disk for database Fast Recovery Area (FRA) files. For example: database backup files, copy of database control files.

Open virtual machine properties window and use wizard to create new virtual hard disks:

Virtual Disk Creation Snapshots

Once virtual hard disks have been created power on virtual machine and let the Oracle Linux start.

Step-02: Installing Oracle Enterprise Linux 5.4

Installation of the Oracle Linux in VMware environment has been described in the following article: Installing Oracle Linux in VMware virtual machine

Once we have Oracle Linux up and running we have to shut it down and create virtual hard disks which will be used for ASM disk groups.

Normally it would be a kind of SAN storage for example, attached to the Linux OS, sometimes several disks visible as multipath devices or raw devices.

However in the end it’s always a set of available disks mounted and accessible for Linux OS like a normal physical disk drives.

Step-03: Creating recommended OS groups and user for Grid Infrastructure

Create user grid and directories

User oracle, group oinstall, dba are ready created by oracle-rdbms-server-11gr2-preinstall:

[root@asmdb ~]# id oracle

uid=500(oracle) gid=501(oinstall) groups=501(oinstall),500(dba)

[root@asmdb ~]# id grid

id: grid: No such user

[root@asmdb ~]#

Add this new groups:

[root@asmdb ~]# groupadd oper

[root@asmdb ~]# groupadd asmadmin

[root@asmdb ~]# groupadd asmdba

[root@asmdb ~]# groupadd asmoper

Create new user grid:

[root@asmdb ~]# useradd -g oinstall -G asmadmin,asmdba,asmoper,dba -c "Grid Infrastructure Owner" grid

Modify user oracle:

 [root@asmdb ~]# usermod -G dba,oper,asmdba -c "Database Owner" oracle

Result:

[root@asmdb ~]# id grid

uid=501(grid) gid=501(oinstall) groups=501(oinstall),500(dba),503(asmadmin),504(asmdba),505(asmoper)

[root@asmdb ~]# id oracle

uid=500(oracle) gid=501(oinstall) groups=501(oinstall),500(dba),502(oper),504(asmdba)

Note: User grid must be put on secondary group dba and user oracle must be put on secondary group asmdba 

Create directories for grid:

[root@asmdb ~]# mkdir -p /u01/app/grid

[root@asmdb ~]# mkdir -p /u01/app/grid/product/11.2.0/grid

[root@asmdb ~]# chown -R grid:oinstall /u01/app/grid

[root@asmdb ~]# chmod -R 775 /u01

[root@asmdb ~]# mkdir -p /softgrid

[root@asmdb ~]# chown -R grid:oinstall /softgrid

[root@asmdb ~]# chmod -R 775 /softgrid

Create directories for oracle:

[root@asmdb ~]# mkdir -p /u01/app/oracle

[root@asmdb ~]# mkdir -p /u01/app/oracle/product/11.2.0/db_1

[root@asmdb ~]# chown -R oracle:oinstall /u01/app/oracle  

[root@asmdb ~]# chmod -R 775 /u01

[root@asmdb ~]# mkdir -p /softdb

[root@asmdb ~]# chown -R grid:oinstall /softdb

[root@asmdb ~]# chmod -R 775 /softdb

Set the password for new grid account:

[root@asmdb ~]# passwd grid

Changing password for user grid.

New UNIX password:

BAD PASSWORD: it is too short

Retype new UNIX password:

passwd: all authentication tokens updated successfully.

Set the password for oracle account:

[root@asmdb ~]# passwd oracle

Changing password for user oracle.

New UNIX password:

BAD PASSWORD: it is based on a dictionary word

Retype new UNIX password:

passwd: all authentication tokens updated successfully.

Step-04: Configure and checking few basic files from root user

Adjust /etc/hosts file:

[root@asmdb softgrid]# cat /etc/hosts

# Do not remove the following line, or various programs

# that require network functionality will fail.

127.0.0.1        localhost.localdomain localhost

#::1            localhost6.localdomain6 localhost6

192.168.7.151 asmdb.aibl.com asmdb

If you have not used the "oracle-validated" package to perform all prerequisites, you will need to manually perform the following setup tasks.Oracle recommend the following minimum parameter settings.

fs.suid_dumpable = 1

fs.aio-max-nr = 1048576

fs.file-max = 6815744

kernel.shmall = 2097152

kernel.shmmax = 536870912

kernel.shmmni = 4096

kernel.sem = 250 32000 100 128

net.ipv4.ip_local_port_range = 9000 65500

net.core.rmem_default = 262144

net.core.rmem_max = 4194304

net.core.wmem_default = 262144

net.core.wmem_max = 1048586

The current values can be tested using the following command.

/sbin/sysctl -a | grep <param-name>

Add or amend the following lines in the "/etc/sysctl.conf" file.

[root@asmdb softgrid]# vi /etc/sysctl.conf

kernel.shmall = 1073741824

fs.file-max = 6815744

kernel.msgmni = 2878

kernel.sem = 250 32000 100 142

kernel.shmmni = 4096

net.core.rmem_default = 262144

# For 11g recommended value for net.core.rmem_max is 4194304

net.core.rmem_max = 4194304

# For 10g uncomment the following line, comment other entries for this parameter and re-run sysctl -p

# net.core.rmem_max=2097152

net.core.wmem_default = 262144

net.core.wmem_max = 1048586

fs.aio-max-nr = 3145728

net.ipv4.ip_local_port_range = 1024 65000

Run the following command to change the current kernel parameters.

/sbin/sysctl –p

[root@asmdb softgrid]#  /sbin/sysctl –p

net.ipv4.ip_forward = 0

net.ipv4.conf.default.rp_filter = 1

net.ipv4.conf.default.accept_source_route = 0

kernel.sysrq = 1

kernel.core_uses_pid = 1

net.ipv4.tcp_syncookies = 1

kernel.msgmnb = 65536

kernel.msgmax = 8192

kernel.shmmax = 4398046511104

kernel.shmall = 1073741824

fs.file-max = 6815744

kernel.msgmni = 2878

kernel.sem = 250 32000 100 142

kernel.shmmni = 4096

net.core.rmem_default = 262144

net.core.rmem_max = 4194304

net.core.wmem_default = 262144

net.core.wmem_max = 1048586

fs.aio-max-nr = 3145728

net.ipv4.ip_local_port_range = 1024 65000

Add the following lines to the "/etc/security/limits.conf" file.

[root@asmdb softgrid]# vi  /etc/security/limits.conf

oracle   soft   nofile    131072

oracle   hard   nofile    131072

oracle   soft   nproc    131072

oracle   hard   nproc    131072

oracle   soft   core    unlimited

oracle   hard   core    unlimited

oracle   soft   memlock    50000000

oracle   hard   memlock    50000000

oracle   soft    stack   10240

grid soft nproc 2047

grid hard nproc 16384

grid soft nofile 1024

grid hard nofile 65536

Add or edit the following line in the /etc/pam.d/login file, if it does not exist:

[root@asmdb softgrid]# vi  /etc/pam.d/login

session required pam_limits.so

For the Bourne, Bash, or Korn shell, add the following lines to the /etc/profile file by running the following command:

[root@asmdb softgrid]# cat  /etc/profile

if [ \$USER = "oracle" ] || [ \$USER = "grid" ]; then

if [ \$SHELL = "/bin/ksh" ]; then

ulimit -p 16384

ulimit -n 65536

else

ulimit -u 16384 -n 65536

fi

umask 022

fi

Step-05: Creating login scripts for grid and oracle users

Login script for an oracle user:

Switch to an oracle user and edit .bash_profile file

[root@asmdb oracle]# su oracle

[oracle@asmdb ~]$ cd /home/oracle/

[oracle@asmdb ~]$ vi .bash_profile # .bash_profile

# Get the aliases and functions

if [ -f ~/.bashrc ]; then

        . ~/.bashrc

fi

# User specific environment and startup programs

PATH=$PATH:$HOME/bin

export PATH

# Oracle Settings

TMP=/tmp; export TMP

TMPDIR=$TMP; export TMPDIR

ORACLE_HOSTNAME=asmdb.aibl.com; export ORACLE_HOSTNAME

ORACLE_UNQNAME=testdb; export ORACLE_UNQNAME

ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE

ORACLE_HOME=$ORACLE_BASE/product/11.2.0/db_1; export ORACLE_HOME

ORACLE_SID=testdb; export ORACLE_SID

PATH=/usr/sbin:$PATH; export PATH

PATH=$ORACLE_HOME/bin:$PATH; export PATH

LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH

CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH

[oracle@asmdb ~]$ . ./.bash_profile

Login script for a grid user:

Switch to an oracle user and edit .bash_profile file

[oracle@asmdb ~]$ su grid

Password:

[grid@asmdb oracle]$

[grid@asmdb oracle]$ cd /home/grid/

[grid@asmdb ~]$ vi  .bash_profile

# .bash_profile

# Get the aliases and functions

if [ -f ~/.bashrc ]; then

        . ~/.bashrc

fi

# User specific environment and startup programs

PATH=$PATH:$HOME/bin

export PATH

# Oracle Settings

TMP=/tmp; export TMP

TMPDIR=$TMP; export TMPDIR

ORACLE_HOSTNAME=asmdb.aibl.com; export ORACLE_HOSTNAME

ORACLE_UNQNAME=+ASM; export ORACLE_UNQNAME

ORACLE_BASE=/u01/app/grid; export ORACLE_BASE

ORACLE_HOME=$ORACLE_BASE/product/11.2.0/grid; export ORACLE_HOME

ORACLE_SID=+ASM; export ORACLE_SID

PATH=/usr/sbin:$PATH; export PATH

PATH=$ORACLE_HOME/bin:$PATH; export PATH

LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH

CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH

[grid@asmdb ~]$ . ./.bash_profile

Step-06: Installing Oracle ASM packages and create ASM disk groups

[root@asmdb Desktop]# ls -1 oracleasm-*

oracleasm-2.6.18-238.el5-2.0.5-1.el5.x86_64.rpm

oracleasm-support-2.1.7-1.el5.x86_64.rpm

[root@asmdb Desktop]# rpm -Uvh oracleasm-support-2.1.7-1.el5.x86_64.rpm

[root@asmdb Desktop]# rpm -Uvh oracleasm-2.6.18-238.el5-2.0.5-1.el5.x86_64.rpm

One more package we have to install is oracleasmlib:

Getting Oracle ASMLib via the Unbreakable Linux Network

We do not have ULN access right now.

Getting ASMLib Without a ULN Subscription

Non-subscribers are free to use the similar package built for RHEL on their Enterprise Linux machines.

Go to Oracle Technology Network and download oracleasmlib package from RHEL 5 section:

oracleasmlib-2.0.4-1.el5.x86_64.rpm

copy package to oracle server into /tmp directory and install it:

[root@asmdb Desktop]# rpm -Uvh oracleasmlib-2.0.4-1.el5.x86_64.rpm

UPDATE:

If missing the unixODBC package (32bit) also has to be installed:

[root@asmdb Desktop]# rpm -Uvh unixODBC-2.2.11-10.el5.i386.rpm

Configuring and load the ASM kernel module (as the “root” user):

[root@asmdb Desktop]# /usr/sbin/oracleasm configure -i

Configuring the Oracle ASM library driver.

This will configure the on-boot properties of the Oracle ASM library

driver.  The following questions will determine whether the driver is

loaded on boot and what permissions it will have.  The current values

will be shown in brackets ('[]').  Hitting <ENTER> without typing an

answer will keep that current value.  Ctrl-C will abort.

Default user to own the driver interface []: grid

Default group to own the driver interface []: asmadmin

Start Oracle ASM library driver on boot (y/n) [n]: y

Scan for Oracle ASM disks on boot (y/n) [y]: y

Writing Oracle ASM library driver configuration: done

The script completes the following tasks:

Creates the /etc/sysconfig/oracleasm configuration file

Creates the /dev/oracleasm mount point

Mounts the ASMLib driver file system

Enter the following command to load the oracleasm kernel module:

[root@asmdb Desktop]# /usr/sbin/oracleasm init

Creating /dev/oracleasm mount point: /dev/oracleasm

Loading module "oracleasm": oracleasm

Mounting ASMlib driver filesystem: /dev/oracleasm

Step-07: Creating ASM disk volumes

Let’s take a look at the available disks in Oracle Linux (remember we have created three additional disks for ASM)

[root@asmdb Desktop]# fdisk -l

Disk /dev/sda: 42.9 GB, 42949672960 bytes

255 heads, 63 sectors/track, 5221 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System

/dev/sda1   *           1          13      104391   83  Linux

/dev/sda2              14        5221    41833260   8e  Linux LVM

Disk /dev/sdb: 2147 MB, 2147483648 bytes

255 heads, 63 sectors/track, 261 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System

/dev/sdb1               1         261     2096451   83  Linux

Disk /dev/sdc: 21.4 GB, 21474836480 bytes

255 heads, 63 sectors/track, 2610 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System

/dev/sdc1               1        2610    20964793+  83  Linux

Disk /dev/sdd: 10.7 GB, 10737418240 bytes

255 heads, 63 sectors/track, 1305 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System

/dev/sdd1               1        1305    10482381   83  Linux

We’ve got three new disks available for ASM disks:

Disk /dev/sdb: 2147 MB

Disk /dev/sdc: 21.4 GB

Disk /dev/sdd: 10.7 GB

First we have to create partitions to be able to use those disks as ASM disks;

[root@asmdb ~]# ls /dev/sd*

/dev/sda  /dev/sda1  /dev/sda2  /dev/sdb  /dev/sdc  /dev/sdd

[root@asmdb ~]#

[root@asmdb ~]# fdisk /dev/sdb

Command (m for help): n

Command action

   e   extended

   p   primary partition (1-4)

p

Partition number (1-4): 1

First cylinder (1-261, default 1): 1

Last cylinder or +size or +sizeM or +sizeK (1-261, default 261): 261

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

Syncing disks.

[root@asmdb ~]#

[root@asmdb ~]# fdisk /dev/sdc

The number of cylinders for this disk is set to 2610.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): n

Command action

   e   extended

   p   primary partition (1-4)

p

Partition number (1-4): 1

First cylinder (1-2610, default 1): 1

Last cylinder or +size or +sizeM or +sizeK (1-2610, default 2610): 2610

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

Syncing disks.

[root@asmdb ~]#

[root@asmdb ~]# fdisk /dev/sdd

The number of cylinders for this disk is set to 1305.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): n

Command action

   e   extended

   p   primary partition (1-4)

p

Partition number (1-4): 1

First cylinder (1-1305, default 1): 1

Last cylinder or +size or +sizeM or +sizeK (1-1305, default 1305): 1305

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

Syncing disks.

Creating ASM disks:

 [root@asmdb Desktop]# /usr/sbin/oracleasm createdisk CRSVOL1 /dev/sdb1

Writing disk header: done

Instantiating disk: done

[root@asmdb Desktop]# /usr/sbin/oracleasm createdisk DATAVOL1 /dev/sdc1

Writing disk header: done

Instantiating disk: done

 [root@asmdb Desktop]# /usr/sbin/oracleasm createdisk FRAVOL1 /dev/sdd1

Writing disk header: done

Instantiating disk: done

List ASM disks:

 [root@asmdb Desktop]# /usr/sbin/oracleasm listdisks

CRSVOL1

DATAVOL1

FRAVOL1

Test disks discovery (oracle-discovery is being used by the oracle database creation assistant (dbca))

[root@asmdb Desktop]# oracleasm-discover

Using ASMLib from /opt/oracle/extapi/64/asm/orcl/1/libasm.so

[ASM Library - Generic Linux, version 2.0.4 (KABI_V2)]

Discovered disk: ORCL:CRSVOL1 [4192902 blocks (2146765824 bytes), maxio 512]

Discovered disk: ORCL:DATAVOL1 [41929587 blocks (21467948544 bytes), maxio 512]

Discovered disk: ORCL:FRAVOL1 [20964762 blocks (10733958144 bytes), maxio 512]

Step-08: Downloading and installing Oracle Grid Infrastructure

Download Oracle Database 11g R 2 Grid Infrastructure (11.2.0.3.0) for Linux x86 –

Linux_11gR2_grid.zip

Copy linux.x64_11gR2_grid.zip to oracle server into /softgrid directory using, for example WinSCP

Run Xming server on your localhost to be able to display GUI Oracle Installer

login as a grid user using putty with Xming configuration enabled unzip linux.x64_11gR2_grid.zip package to /home/grid/stage directory and run the Oracle Universal Installer:

[grid@asmdb /]$ unzip /softgrid/linux.x64_11gR2_grid.zip

[grid@asmdb /]$ cd /softgrid/grid_11.2.3.0

[grid@asmdb /]$ ./runInstaller

Starting Oracle Universal Installer...

Checking Temp space: must be greater than 120 MB. Actual 15673 MB Passed

Checking swap space: must be greater than 150 MB. Actual 3999 MB Passed

Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed

Preparing to launch Oracle Universal Installer from /tmp/OraInstall2022-01-11_10-65-27AM. Please wait ...

Oracle Grid Infrastructure installation window will popup…

Grid Installation Snapshots…

At this moment we have Oracle AMS instance and related services up and running:

[grid@asmdb /]$ ps -ef | grep grid

root      1018   884  0 23:58 pts/1    00:00:00 su grid

grid      1019  1018  0 23:58 pts/1    00:00:00 bash

grid      1046  1019  0 23:59 pts/1    00:00:00 ps -ef

grid      1047  1019  0 23:59 pts/1    00:00:00 grep grid

grid      2402     1  0 Nov19 ?        00:00:06 /u01/app/grid/product/11.2.0/grid/bin/ohasd.bin reboot

grid      2965     1  0 Nov19 ?        00:06:01 /u01/app/grid/product/11.2.0/grid/bin/oraagent.bin

grid      2978     1  0 Nov19 ?        00:00:21 /u01/app/grid/product/11.2.0/grid/bin/tnslsnr LISTENER -inherit

grid      2991     1  0 Nov19 ?        00:00:01 /u01/app/grid/product/11.2.0/grid/bin/evmd.bin

grid      2995     1  0 Nov19 ?        00:00:01 /u01/app/grid/product/11.2.0/grid/bin/cssdagent

grid      3019     1  0 Nov19 ?        00:00:00 /u01/app/grid/product/11.2.0/grid/bin/ocssd.bin

grid      3051  2991  0 Nov19 ?        00:00:00 /u01/app/grid/product/11.2.0/grid/bin/evmlogger.bin -o /u01/app/grid/product/11.2.0/grid/evm/log/evmlogger.info -l /u01/app/grid/product/11.2.0/grid/evm/log/evmlogger.log

grid      3122     1  0 Nov19 ?        00:00:01 asm_pmon_+ASM

grid      3124     1  0 Nov19 ?        00:00:00 asm_psp0_+ASM

grid      3126     1  0 Nov19 ?        00:00:03 asm_vktm_+ASM

grid      3130     1  0 Nov19 ?        00:00:00 asm_gen0_+ASM

grid      3132     1  0 Nov19 ?        00:00:00 asm_diag_+ASM

grid      3134     1  0 Nov19 ?        00:00:17 asm_dia0_+ASM

grid      3136     1  0 Nov19 ?        00:00:00 asm_mman_+ASM

grid      3138     1  0 Nov19 ?        00:00:00 asm_dbw0_+ASM

grid      3140     1  0 Nov19 ?        00:00:00 asm_lgwr_+ASM

grid      3142     1  0 Nov19 ?        00:00:00 asm_ckpt_+ASM

grid      3144     1  0 Nov19 ?        00:00:00 asm_smon_+ASM

grid      3146     1  0 Nov19 ?        00:00:08 asm_rbal_+ASM

grid      3148     1  0 Nov19 ?        00:00:03 asm_gmon_+ASM

grid      3150     1  0 Nov19 ?        00:00:00 asm_mmon_+ASM

grid      3152     1  0 Nov19 ?        00:00:00 asm_mmnl_+ASM

grid      3154     1  0 Nov19 ?        00:00:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))

grid      3165     1  0 Nov19 ?        00:00:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))

grid      3168     1  0 Nov19 ?        00:00:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))

grid      6049     1  0 Nov19 ?        00:00:00 oracle+ASM_asmb_testdb (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))

grid     11073     1  0 Nov21 ?        00:00:00 oracle+ASM_o001_testdb (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))

Step-09: Creating ASM disk groups for Oracle database installation

Next we are going to configure ASM disk groups for Oracle Database installation (+FRA and +DATA)

Again, as a grid user run asmca (ASM Configuration Assistant)

[grid@asmdb /]$ asmca

ASMCA Snapshots…

Step-10: Installing Oracle database software and create database instance choosing ASM disks for data storage

First we are going to install Oracle Database software only.

How to get Oracle Database Installation packages has been described in this article: Installing Oracle Database 11g R2 on Linux

Assuming that oracle installation software has been downloaded and unzipped into /softdb/database_11gR2/database_11gR2 directory run the Oracle Universal Installer as an oracle user:

[oracle@asmdb /]$ cd /softdb/database_11gR2/database_11gR2/

[oracle@asmdb /]$ ./runInstaller

Starting Oracle Universal Installer...

Checking Temp space: must be greater than 120 MB. Actual 12488 MB Passed

Checking swap space: must be greater than 150 MB. Actual 3978 MB Passed

Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed

Preparing to launch Oracle Universal Installer from /tmp/OraInstall2042-03-11_12-67-50AM. Please wait ...

Oracle Installation Snapshots…

Once the Oracle Software has been installed we can run dbca (Database Creation Assistant) to create a database with ASM

As an oracle user run dbca and follow database creation wizard:

[oracle@asmdb /]$ dbca

Hint: Pay attention to database control file location in initialization parameter configuration step (place control files on ASM disks +DATA and copy on +FRA):

Database Installation Snapshots…

Once new database has been created we can use sqlplus to connect to a database or open Enterprise Manager Database Control in our favorite web browser (https://192.168.7.151:1158/em)