Owners Manual

Dell Integrated Systems for Oracle Database 2.0 - Owner’s Guide 1.1
30
Minimum DISOD configuration contains at least one DAAD HA pair because DISOD
supports only clustered DAAD nodes. The cluster names of each DAAD HA pair and the
individual hostnames of each DAAD node within that HA pair are preconfigured from
factory. The first DAAD HA pair is assigned the cluster name fcion1 and the individual
DAAD nodes within that HA pair are assigned the hostnames fcion1a and fcion1b.
Similarly, the second DAAD HA pair is assigned the cluster name fcion2 and the individual
DAAD nodes within that HA pair are assigned the hostnames fcion2a and fcion2b. This
naming convention is followed for all the DAAD clusters or HA pairs in the DISOD solution
rack.
Volumes and volume names on the DAAD nodes are preconfigured from factory. Eight
volumes are created within each DAAD HA pair. These eight volumes are given the
following local names:
v_a1
v_a2
v_b1
v_b2
v_c1
v_c2
v_d1
v_d2
The full name of each volume is defined as the ‘cluster name + the local name’. For
example, the eight volumes of the first cluster array (fcion1) are preconfigured as:
fcion1_v_a1
fcion1_v_a2
fcion1_v_b1
fcion1_v_b2
fcion1_v_c1
fcion1_v_c2
fcion1_v_d1
fcion1_v_d2
Eight volumes are created per DAAD HA pair and assigned to the database nodes for
Oracle database usage. So, the total number of volumes preconfigured and presented to
the database nodes is the number of DAAD HA pairs times eight.
Total number of volumes for Oracle database = Number of DAAD HA pairs × 8
Depending on the capacity flavor of the DAAD nodes within each HA pair, the size of the
volumes assigned to the database nodes is as under:
 Each volume is of size 1.5 TB in case of the 12.8 TB-based DAAD HA pairs
 Each volume is of size 3 TB in case of the 25.6 TB-based DAAD HA pairs
For more information about how these volumes are configured on the database nodes,
see the 4.2.3 Shared storage volume partitions section.