This chapter provides information about optimizing communications between Oracle Exadata Database Machine and Oracle Big Data Appliance. It contains the following sections:
Sockets Direct Protocol (SDP) is a standard communication protocol for clustered server environments, providing an interface between the network interface card and the application. By using SDP, applications place most of the messaging burden upon the network interface card, which frees the CPU for other tasks. As a result, SDP decreases network latency and CPU utilization, and thereby improves performance.
This chapter describe how you can configure Oracle Exadata Database Machine to use SDP over InfiniBand to communicate with Oracle Big Data Appliance.
Oracle Big Data Appliance and Oracle Exadata Database Machine racks must be cabled together using InfiniBand cables. The IP addresses must be unique across all racks and use the same subnet for the InfiniBand network.
See Also:
Oracle Big Data Appliance Owner's Guide about multirack cabling
Oracle Big Data Appliance Configuration Worksheets about IP addresses and subnets
The following procedure describes how to enable SDP on database nodes in an Oracle Exadata Database Machine running Oracle Linux.
To enable SDP on Oracle Exadata Database Machine:
Open /etc/infiniband/openib.conf file in a text editor, and add the following line:
set: SDP_LOAD=yes
Save these changes and close the file.
To enable both SDP and TCP, open /etc/ofed/libsdp.conf in a text editor, and add the use both rule:
use both server * : use both client * :
Save these changes and close the file.
Open /etc/modprobe.conf file in a text editor, and add this setting:
options ib_sdp sdp_zcopy_thresh=0 recv_poll=0
Save these changes and close the file.
Replicate these changes across all servers in the Oracle Exadata Database Machine rack.
Restart all database nodes for the changes to take effect.
If you have multiple Oracle Exadata Database Machine racks, then repeat these steps on all of them.
The following procedure explains how to configure a JDBC client to use SDP.
To enable SDP support for JDBC:
Configure the database to support InfiniBand, as described in the Oracle Database Net Services Administrator's Guide. Ensure that you set the protocol to SDP.
Set the LD_PRELOAD environment variable to libsdp.so before starting the Java virtual machine. This example uses the Bash shell:
export LD_PRELOAD="libsdp.so"
The following steps are an alternative to setting LD_PRELOAD:
In the JDBC URL, replace TCP protocol with SDP protocol. For example:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=sdp)(HOST=xxx.x.x.x)(PORT=1522))(CONNECT_DATA=(SERVICE_NAME=myservice)))
Open DOMAIN_HOME/bin/startWebLogic.sh in a text editor and make the following change:
Locate this line in the file:
. ${DOMAIN_HOME}/bin/setDomainEnv.sh $*
Add this property immediately after the previous line:
JAVA_OPTIONS="${JAVA_OPTIONS} -Djava.net.preferIPv4Stack=true -Doracle.net.SDP=true"
Save and close the file.
To add a listener for the Oracle Big Data Appliance connections coming in on the InfiniBand network, first add a network resource for the InfiniBand network with virtual IP addresses.
Note:
This example lists two nodes for an Oracle Exadata Database Machine quarter rack. If you have an Oracle Exadata Database Machine half or full rack, you must repeat node-specific lines for each node in the cluster.Edit /etc/hosts on each node in the Exadata rack to add the virtual IP addresses for the InfiniBand network. Make sure that these IP addresses are not in use. For example:
# Added for Listener over IB 192.168.10.21 dm01db01-ibvip.example.com dm01db01-ibvip 192.168.10.22 dm01db02-ibvip.example.com dm01db02-ibvip
As the root user, create a network resource on one database node for the InfiniBand network. For example:
# /u01/app/grid/product/11.2.0.2/bin/srvctl add network -k 2 -S 192.168.10.0/255.255.255.0/bondib0
Verify that the network was added correctly with one of the following commands:
# /u01/app/grid/product/11.2.0.2/bin/crsctl stat res -t | grep net ora.net1.network ora.net2.network -- Output indicating new Network resource
or
# /u01/app/grid/product/11.2.0.2/bin/srvctl config network -k 2 Network exists: 2/192.168.10.0/255.255.255.0/bondib0, type static -- Output indicating Network resource on the 192.168.10.0 subnet
Add the virtual IP addresses on the network created in Step 2, for each node in the cluster:
# srvctl add vip -n dm01db01 -A dm01db01-ibvip/255.255.255.0/bondib0 -k 2 # srvctl add vip -n dm01db02 -A dm01db02-ibvip/255.255.255.0/bondib0 -k 2
As the oracle user, who owns Grid Infrastructure Home, add a listener for the virtual IP addresses created in Step 4.
# srvctl add listener -l LISTENER_IB -k 2 -p TCP:1522,/SDP:1522
For each database that will accept connections from the middle tier, modify the listener_networks init parameter to allow load balancing and failover across multiple networks (Ethernet and InfiniBand). You can either enter the full TNSNAMES syntax in the initialization parameter or create entries in tnsnames.ora in the $ORACLE_HOME/network/admin directory. The TNSNAMES.ORA entries must exist in GRID_HOME. The following example first updates tnsnames.ora.
Complete this step on each node in the cluster with the correct IP addresses for that node. LISTENER_IBREMOTE should list all other nodes that are in the cluster. DBM_IB should list all nodes in the cluster.
Note:
TheTNSNAMES entry is only read by the database instance on startup, if you modify the entry that is referred to by any init.ora parameter (LISTENER_NETWORKS), you must restart the instance or issue an ALTER SYSTEM SET LISTENER_NETWORKS command for the modifications to take affect by the instance.DBM = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = dm01-scan)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = dbm) )) DBM_IB = (DESCRIPTION = (LOAD_BALANCE=on) (ADDRESS = (PROTOCOL = TCP)(HOST = dm01db01-ibvip)(PORT = 1522)) (ADDRESS = (PROTOCOL = TCP)(HOST = dm01db02-ibvip)(PORT = 1522)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = dbm) )) LISTENER_IBREMOTE = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = dm01db02-ibvip.mycompany.com)(PORT = 1522)) )) LISTENER_IBLOCAL = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = dm01db01-ibvip.mycompany.com)(PORT = 1522)) (ADDRESS = (PROTOCOL = SDP)(HOST = dm01db01-ibvip.mycompany.com)(PORT = 1522)) )) LISTENER_IPLOCAL = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = dm0101-vip.mycompany.com)(PORT = 1521)) )) LISTENER_IPREMOTE = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = dm01-scan.mycompany.com)(PORT = 1521)) ))
Connect to the database instance as sysdba.
Modify the listener_networks init parameter:
SQL> alter system set listener_networks=
'((NAME=network2) (LOCAL_LISTENER=LISTENER_IBLOCAL)
(REMOTE_LISTENER=LISTENER_IBREMOTE))',
'((NAME=network1)(LOCAL_LISTENER=LISTENER_IPLOCAL)
(REMOTE_LISTENER=LISTENER_IPREMOTE))' scope=both;
Restart LISTENER_IB to implement the modification in Step 7:
# srvctl stop listener -l LISTENER_IB # srvctl start listener -l LISTENER_IB
After you complete the previous procedures, you are ready to configure Oracle Exadata Database Machine to use InfiniBand to communicate with Oracle Big Data Appliance. Otherwise, the default network is Ethernet.
To configure Oracle Exadata Database Machine to use InfiniBand:
If you have not done so already, install a CDH client on Oracle Exadata Database Machine. See "Providing Remote Client Access to CDH."
Obtain a list of host names and InfiniBand IP addresses for all Oracle Big Data Appliance servers.
An Oracle Big Data Appliance rack can have 6, 12, or 18 servers.
Log in to Oracle Exadata Database Machine with root privileges.
Edit /etc/hosts on Oracle Exadata Database Machine and add the Oracle Big Data Appliance host names and InfiniBand IP addresses. The following example shows the sequential IP numbering:
192.168.8.1 bda1node01.example.com bda1node01 192.168.8.2 bda1node02.example.com bda1node02 192.168.8.3 bda1node03.example.com bda1node03 192.168.8.4 bda1node04.example.com bda1node04 192.168.8.5 bda1node05.example.com bda1node05 192.168.8.6 bda1node06.example.com bda1node06
Check /etc/nsswitch.conf for a line like the following:
hosts: files dns
Ensure that the line does not reverse the order (dns files); if it does, your additions to /etc/hosts will not be used. Edit the file if necessary.