Owners Manual

Dell Integrated Systems for Oracle Database 2.0 - Owner’s Guide 1.1

To supplement the Oracle Database 12c preinstall RPM, a customized Dell deployment

utility is also used. This utility builds on top of the preinstall RPM, and takes extra steps to

ensure that the environment is set up properly. Some of the steps include:

 Disable SELinux (optional)

 Create additional users/groups/permissions for Oracle’s Grid infrastructure

 Create base directories and permissions for the Grid/Database installation

 Install the necessary RPMs needed for Oracle Database 12c

The Oracle Database 12c preinstall RPM and the Dell deployment utility are preinstalled on

the database servers in the DISOD solution rack. More information regarding these utilities

can be viewed at http://en.community.dell.com/techcenter/enterprise-

solutions/w/oracle_solutions/4957.oracle-database-deployment-automation

4.2.3 Shared storage volume partitions

DAAD is not a traditional spinning disk-based storage, but is an extremely fast all-flash

based storage array. There are no performance implications on putting all Oracle database

functions across only two ASM disk groups―one for OCR and Voting Disks (VDs), and the

other for data files, Flash Recovery Area (FRA), REDO log files, and so on. As a result, the

storage volumes that are preconfigured and assigned to the database nodes are

prepartitioned at the OS level and presented as raw disks for these various Oracle

Database functions.

Two partitions are created on each storage volume―one of 15 GB disk size and the other

spanning rest of the drive. The disk size of the second partition depends on the capacity of

DAAD storage array that is used in the backend. For DAAD nodes with a total disk capacity

of 12.8 TB, the second partition is of size 1.485 TB; and, for DAAD nodes with a total disk

capacity of 25.6 TB, the second partition is of size 2.985 TB. Thus, taking a 2×2

configuration as an example that has one DAAD HA pair, DISOD solution provides and is

configured with the following shared storage volumes or partitions at the database node

level:

1. Eight 15 GB partitions or disks, for a total of 120 GB, three of which are to be used

for OCR and Voting Disks, and the remaining are free to be used as extra storage.

2. Eight partitions or disks of size either 1.485 TB or 2.985 TB, for a total of either

11.88 TB or 23.88 TB, that are available for data files, FRA, REDO log files, and so

on.

The total quantity of each of the above two partitions depends on the total number of

DAAD HA pairs that are used in the backend. To get the total quantity and the total size of

usable storage capacity, multiply the above numbers by the total number of DAAD HA

pairs. For example, for two DAAD HA pairs in the backend, a total of sixteen 15 GB

partitions will be available, and a total of sixteen second partition that are to be used for

data files, REDO log files, and so on will be available.

NOTE: Though DISOD provides at least eight partitions or disks for OCR and VDs, it is

recommended to create its ASM diskgroup with Normal Redundancy. DAAD’s HA feature