HP InfiniBand Solution for Oracle RAC Environments white paper

representative in order to gather the needed patches and information necessary to enable uDAPL and

OCFS support.

Verifying that the uDAPL protocol is being used for inter-node communication

Once all of the Oracle software components have been successfully installed and a database has

been created, the alert log can be examined to determine if the instance is using uDAPL for inter-

instance communication. The alert log should contain output similar to the following:

db_name = orcl

open_cursors = 300

pga_aggregate_target = 25165824

Mon Dec 6 11:58:42 2004

cluster interconnect IPC version: Oracle UDAPL Jul 1 2004 06:25:39

IPC Vendor 1 proto 1 Version 1.0

PMON started with pid=2, OS id=28186

DIAG started with pid=3, OS id=28191

LMON started with pid=4, OS id=28197

The cluster interconnect IPC version field indicates which protocol is being used across the

interconnect.

Alternatively, the following procedure can be used to determine if the database instance is using

uDAPL:

• Open a sqlplus session and connect as sysdba.

10. Enter the following commands at the sqlplus prompt

Oradebug setmypid

Oradebug ipc

11. Check the location specified in the user_dump_directory initialization parameter for the latest .trc

file.

Once the system has successfully been configured to use the uDAPL protocol, the installation is

complete.

Conclusion

Due to its architecture, an Oracle RAC requires a high performance interconnect to achieve high

levels of scalability. The HP InfiniBand products can be deployed to provide an Oracle Real

Application Cluster with a high bandwidth, low-latency interconnect.

Oracle Real Application Cluster environments have a reputation of being difficult to integrate and

deploy successfully. The HP Parallel Database Cluster kit and accompanying fixed price service can

greatly reduce the complexity involved in deploying an Oracle RAC system.