B Installation Information

This appendix contains information about Oracle Exadata Storage Server installation. Refer to this installation information if the Oracle Exadata Storage Server hardware and software are not already installed.

B.1 Installation of Oracle Exadata Storage Server

This section describes the installation process for a storage server.

B.1.1 Installing Oracle Exadata Storage Server Hardware

Use these steps to complete the hardware installation necessary for standalone Oracle Exadata Storage Servers connecting to Oracle Exadata Database Machine.

  1. Unpack, situate, and set up the storage server.
  2. Read the printed vendor documentation supplied with the storage servers.
  3. Connect the management and Integrated Lights Out Manager (ILOM) Ethernet ports to the management network.
  4. Connect the RDMA Network Fabric ports of the Oracle Exadata Storage Server to the RDMA Network Fabric network of Oracle Exadata Database Machine.


    Both the Oracle Exadata Database Machine and additional Oracle Exadata Storage Servers must use the same type of RDMA Network Fabric.
  5. Attach a computer or terminal to one of the new storage servers so you can configure the cell as described in Configuring Oracle Exadata System Software for Your Location. You must configure each new cell.
  6. Connect the power supply on the new storage servers.
  7. Power on the storage servers.
  8. Assign IP addresses for the network interconnections of the new storage servers.

B.1.2 Installing the Oracle Exadata System Software on a Cell

This procedure describes how to install the Oracle Exadata System Software on an Oracle Exadata Storage Server.

  1. Power on the Oracle Exadata Storage Server to boot its operating system.
  2. Log in to the Oracle Exadata Storage Server with super user (root) privileges.


    If you do not have the password for the root user, then contact Oracle Support Services.

  3. Change the root password on the cell.
  4. Verify that the Oracle Exadata Storage Server meets the software requirements.
  5. Copy the self-extracting binary to the Oracle Exadata Storage Server, if necessary.

    You can use the ftp command to copy the binary to the Oracle Exadata Storage Server from a network location, or you can copy the binary from a portable storage device.

  6. Install the self-extracting binary on the Oracle Exadata Storage Server if it is not already installed.
  7. Review the /opt/oracle/cell/.install_log.txt file to verify that the installation completed correctly. The installation process adds two new users, celladmin and cellmonitor. The celladmin user should be used to run all services on the cell. The cellmonitor user is for monitoring purposes.
  8. After successful installation of the Oracle Exadata System Software, follow the instructions at "Preparing the Servers".

Related Topics

B.1.3 Updates Made During Installation

Changes that are made to snmpd files during installation include the following:

  • Updates to the public community string

  • New entries for trapdestination

  • Updates to the kernel configuration files (limits for aio, udprecv, and number of open files)

B.1.4 Online Documentation

The documentation can be found online at https://docs.oracle.com/.

B.2 Background Processes in the Oracle Exadata Storage Server Environment

The background processes for the database and Oracle ASM instance for an Oracle Exadata Storage Server environment are the same as other environments, except for the following background processes:

B.2.1 diskmon Process

The diskmon process is a fundamental component of Oracle Exadata System Software, and is responsible for implementing I/O fencing. The process is located on the database server host computer, and is part of Oracle Clusterware Cluster Ready Services (CRS). This process is important for Oracle Exadata System Software and should not be modified.

The log files for diskmon are located in the $CRS_HOME/log/hostname/diskmon directory.

See Also:

B.2.2 XDMG Process

The XDMG (Exadata Automation Manager) process initiates automation tasks used for monitoring storage. This background process monitors all configured Oracle Exadata Storage Servers for state changes, such as replaced disks, and performs the required tasks for such changes. Its primary task is to watch for inaccessible disks and cells, and to detect when the disks and cells become accessible. When the disks and cells are accessible, the XDMG process initiates the ASM ONLINE process, which is handled by the XDWK background process. The XDMG process runs in the Oracle ASM instances.

B.2.3 XDWK Process

The XDWK (Exadata Automation Worker) process performs automation tasks by requested by the XDMG background process. The XDWK process begins when asynchronous actions, such as ONLINE, DROP or ADD for an Oracle ASM disk are requested by the XDMG process. The XDWK process stops after 5 minutes of inactivity. The XDWK process runs in the Oracle ASM instances.