Adopting Exadata to Improve BI Solution Performance

Probably the most important thing will be their code: make sure that it employs set base (as opposed to row by row) processing, parallelism, compression, bulk direct path loading, and transformation techniques vs DML.

EHCC greatly assists with processing of data.

Infiniband also helps with the transfer of data as well - not just between the database nodes and Exadata storage cells but also when ingesting the data from the sources as well (i.e. the data warehouse is not a bottleneck).

Backup and recovery is faster which means unlike many data warehouses which their DR plan mainly consist of complete reload from sources, this provides a true DR and even better DR via data guard than simply "rebuild".

Unanticipated queries where you do not have cubes or views developed aren't such an issue either. Exadata is able to address the unanticipated ones. And these can be the most valuable ones too - new questions that result in more improvement over previous ways.

Network Requirements for Oracle Exadata Database Machine

Oracle Exadata Database Machine includes database servers, Exadata Storage Servers, as well as equipment to connect the servers to your network. The network connections allow the servers to be administered remotely, and clients to connect to the database servers.

Each Oracle Exadata Database Machine X2-2 database server consists of the following network components and interfaces:

• 4 embedded 1 GbE ports (NET0, NET1, NET2, and NET3)
• 1 dual-port QDR (40 Gb/s) InfiniBand Host Channel Adapter (HCA) (BONDIB0)
• 1 Ethernet port for Sun Integrated Lights Out Manager (ILOM)
• 1 dual-port 10 GbE PCIe 2.0 network card with Intel 82599 10 GbE controller (only in Sun Fire X4170 M2 Oracle Database Servers)

Each Exadata Storage Server consists of the following network components and interfaces:

• 1 embedded 1 GbE port (NET0)
• 1 dual-port QDR InfiniBand Host Channel Adapter (HCA) (BONDIB0)
• 1 Ethernet port for Sun Integrated Lights Out Manager (ILOM)

Each Oracle Exadata Database Machine X2-2 database server has three 1 GbE ports and two 10 GbE ports available for additional connectivity.

Additional configuration, such as defining multiple VLANs or enabling routing, may be required for the switch to operate properly in your environment and is beyond the scope of the installation service.

To deploy Oracle Exadata Database Machine ensure that you meet the minimum network requirements There are up to 5 networks for Oracle Exadata Database Machine. Each network must be on a distinct and separate subnet from the others. The network descriptions are as follows:

Management network: This required network connects to your existing management network, and is used for all components of Oracle Exadata Database Machine. It connects the servers, ILOM, and switches connected to the Ethernet switch in the rack.

Client access network: This required network connects the database servers to your existing client network and is used for client access to the database servers. Applications access the database through this network using SCAN and Oracle RAC VIP addresses. Database servers support channel bonding to provide higher bandwidth or availability for client connections to the database. Oracle recommends channel bonding for the client access network. Channel bonding on Oracle Exadata Database Machine X2-2 bonds NET1 and NET2.

Additional networks (optional): Database servers may be configured to connect to one or two additional existing networks through the NET2 and NET3 ports on Oracle Exadata Database Machine X2-2 racks. If channel bonding is used for the client access network, then only one additional port (NET3) is available on Oracle Exadata Database Machine X2-2 racks.

InfiniBand private network: This network connects the database servers and Exadata Storage Servers using the InfiniBand switches on the rack and the BONDIB0 interface. Oracle Database uses this network for Oracle RAC cluster interconnect traffic and for accessing data on Exadata Storage Servers. This non-routable network is fully contained in Oracle Exadata Database Machine, and does not connects to your existing network. This network is automatically configured during installation.

Network Diagram for Oracle Exadata Database Machine X2-2 when Using Channel Bonding (NET1 and NET2)

Network Diagram for Oracle Exadata Database Machine X2-2 when Not Using Channel Bonding

References
Oracle Exadata Database Machine Owner's Guide 11g Release 2

Database Machine and Exadata Storage Server 11g Release 2 Supported Versions

Recommended bundle patches, named Quarterly Database Patch for Exadata (QDPE), will be released quarterly, aligned with and including the database Critical Patch Update (CPU) and Patch Set Update (PSU) releases. QDPE releases are targeted for planned grid infrastructure and database patching activities and are the only patch bundles that will be applied by most customers.

All bundle patches are cumulative, as in previous releases.

There are different types of patches for Exadata Database Machine, as listed below:

Exadata Storage Server
Database Server
Oracle Database Server
OS and firmware
InfiniBand switch
Additional components

In 11.2.3.1.0 and above, we use the yum procedure to update the DB server.


References:
MOS Note ID 1244344.1 - Exadata V2 Starter Kit
MOS Note ID 1187674.1 - Information Center: Oracle Exadata Database Machine
MOS Note ID 888828.1 - Database Machine and Exadata Storage Server 11g Release 2 Supported Versions
MOS Note ID 1262380.1 - Exadata Patching Overview and Patch Testing Guidelines