Chapter 2. Reference Architecture Environment
This section focuses on the components used during the deployment of Oracle Database 12c Release 2 with Oracle Automatic Storage Management (ASM) on Red Hat Enterprise Linux 7 x86_64 in this reference architecture.
2.1. Reference Architecture Overview
A pictorial representation of the environment used in this reference environment is shown in Figure 2.1, “Reference Architecture Overview”
Figure 2.1. Reference Architecture Overview

2.2. Network Topology
The network topology in this reference environment consists of two public switches, and two iSCSI storage switches. Public Switch A and Public Switch B, with a link aggregation that connect them together creating a single logical switch. Ethernet device em1 on the server connects to Public Switch A, while Ethernet device em2 on the server connects to Public Switch B. Ethernet devices em1 and em2 are bonded together as a bond device, bond0, providing high availability for the public network traffic. Figure 2.2, “Network Bonding” shows the pictorial representation of the two public switches connecting to the server and the Ethernet bonding of device em1 and em2 as part of the bond0 device. iSCSI Switch A and iSCSI Switch B also use a link aggregation that connects them together creating a single logical switch. Ethernet device em3 on the server connects to iSCSI Switch A and em4 on the server connects to iSCSI Switch B. It is recommended that em3 and em4 be 10GB Network cards for better performance when accessing the storage. Figure 2.3, “iSCSI Switch Connectivity” shows a pictorial representation of the connectivity of the Ethernet devices to the iSCSI switches.
Figure 2.2. Network Bonding

Figure 2.3. iSCSI Switch Connectivity

2.3. Hardware Details
The following are the hardware requirements to properly install Oracle Database 12c Release 2 on a x86_64 system:
- Minimum of 8 GB of RAM for the installation of Oracle Grid Infrastructure
- Minimum of 1 GB of RAM for the installation of Oracle Database, however 2 GB of memory or more is recommended
- Minimum of 1 Network Interface Card (NIC), however 2 NICs are recommended for high availability (HA) as used in the reference environment
- Red Hat Enterprise Linux 7 with kernel 3.10.0-123.el7.x86_64 or higher
- Console access that supports 1024 x 768 for the Oracle Universal Installer (OUI)
Table 2.1, “Server Details” specifies the hardware for the server within this reference environment. This hardware meets the minimum requirements for properly installing Oracle Database 12c Release 2 on a x86_64 system.
Table 2.1. Server Details
| Server Hardware | Specifications |
| Oracle Database 12c Release 2 Standalone Server (db-oracle-node1) [1 x PowerEdge M520] | Red Hat Enterprise Linux 7 3.10.0-514.el7.x86_64 |
| 2 socket, 8 core, 16 threads, Intel® Xeon® CPU E5-2450 0 @ 2.10GHz | |
| 96 GB of memory, DDR3 16384 MB @ 1600 Mhz DIMMs | |
| 2x NetXtreme BCM5720 Gigabit Ethernet PCIe for public network traffic | |
| 2x NetXtreme II BCM57810 10 Gigabit Ethernet for iSCSI network traffic |
Table 2.2, “Switch Details” specifies the switches within this reference environment.
Table 2.2. Switch Details
| Switch Hardware | |
| 2 x Dell PowerConnect M6348 | 2 x Dell PowerConnect M8024-k |
Table 2.3, “Storage Details” specifies the storage within this reference environment.
Table 2.3. Storage Details
| Storage Hardware |
| Dell Equallogic PS Array |
2.4. File System Layout & Disk Space Details
The following is the disk space requirements for properly installing Oracle Database 12c Release 2 software for this reference environment.
Table 2.4. Disk Space Requirements
| Software | Disk Space |
| Oracle Grid Infrastructure Home (includes software files) | 12 GB |
| Oracle Database Home Enterprise Edition (includes software files and data files) | 12 GB |
| /tmp | 1 GB |
The actual amount of disk space consumed for Oracle Grid Infrastructure Home and Oracle Database Home Enterprise Edition may vary.
Table 2.5, “File System Layout” specifies the file system layout for the server used in this reference environment. The layout ensures the disk space requirements to properly install the Oracle Grid Infrastructure and Oracle Database software for Oracle Database 12c Release 2
Table 2.5. File System Layout
| File System Layout | Disk Space Size |
| / | 15 GB |
| /boot | 250 MB |
| /home | 8 GB |
| /tmp | 4 GB |
| /u01 | 50 GB |
| /usr | 5 GB |
| /var | 8 GB |
While the size of the Oracle data files varies for each solution, the following are the Oracle data file sizes for this reference environment.
Table 2.6. Oracle Data File Sizes for Reference Architecture
| Volume | Volume Size | RAID Group Type | Redundancy |
| Database Volume 1 (db1) | 100 GB | RAID 10 | External |
| Database Volume 2 (db2) | 100 GB | RAID 10 | External |
| Fast Recovery Area (fra) | 200 GB | RAID 5 | External |
| Oracle Redo Log Volume (redo) | 10 GB | RAID 1 | External |
2.5. Swap Space
Swap space is determined by the amount of RAM found within the system. The following table displays the swap space recommendation. This reference environment allocates 16 GB of RAM for swap space.
Table 2.7. Recommended Swap Space
| RAM | Swap Space |
| 2 GB up to 16 GB | Equal to the size of RAM |
| Greater than 16 GB | 16 GB of RAM |
When calculating swap space, ensure not to include RAM assigned for hugepages. More information on hugepages can be found in Section 4.5, “Enabling HugePages”
2.6. Security: Firewall Settings
Red Hat Enterprise Linux 7 introduces the dynamic firewall daemon, firewalld. firewalld provides a dynamically managed firewall with support for network/firewall zones to define the trust level of network connections or interfaces1. firewalld is the default firewall service in Red Hat Enterprise Linux 7, however, iptables service is still available. It is important to note that with the iptables service, every single change means flushing all the old rules and reading all of the new rules from the /etc/sysconfig/iptables while the firewalld there is no re-creating of all the rules; only the differences are applied. Consequently, firewalld can change the setting during runtime without existing connections being lost2. For the purposes of this reference architecture, firewalld is used and is the preferred method of implementing firewall rules. This section focuses on providing the details required to run firewall-cmd successfully for an Oracle Database environment. Table 2.8, “Firewall Settings” lists the enabled ports in this reference environment.
1: Linux man pages - man (1) firewalld
2: 4.5.3 Comparison of firewalld to system-config-firewalld and iptables
Table 2.8. Firewall Settings
| Port | Protocol | Description |
| 22 | TCP | Secure Shell (SSH) |
| 443 | TCP | Hypertext Transfer Protocol over SSL/TLS (HTTPS) |
| 1521 | TCP | Oracle Transparent Network Substrate (TNS) Listener default port |
| 5500 | TCP | EM Express 12c default port |
2.7. Security: SELinux
Starting with Oracle 11g Release 2 version 11.2.0.3, SELinux is supported for Oracle database environments. The system in this reference environment runs with SELinux enabled and set to ENFORCING mode.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.