Oracle Exadata Database Machine

Configuration Worksheets 11g Release 2 (11.2)

E16099-13 July 2011

This document is designed to help define the Oracle Exadata Database Machine configuration settings for your environment. Working with the network and database administrators, evaluate the current environmental settings, such as current IP address use and network configuration. Next, define the settings for Oracle Exadata Database Machine, such as network configuration and backup method. This document includes the configuration worksheets for Oracle Exadata Database Machine, as well as links to the owners guide. The owners guide contains additional information for each configuration worksheet, and site requirements for Oracle Exadata Database Machine. The information is used to create the Oracle Exadata Database Machine Installation Template. It is important to complete the worksheets, and provide them to your Oracle representative prior to installation. All information is required unless otherwise indicated. The Installation Template will be used to complete installation and configuration of your Oracle Exadata Database Machine. Site-specific adjustments to the Installation Template must be made in consultation with your Oracle representative. This document includes the following topics:

Overview of the Network Configuration Process Default Oracle Environment Settings General Configuration Worksheet (Required) Network Configuration Worksheets Oracle Configuration Manager Configuration Worksheets (Recommended) Auto Service Request Configuration Worksheet (Recommended) Oracle Enterprise Manager Grid Control Configuration Worksheets (Recommended) Cell Alert Delivery Configuration Worksheet (Optional) Sample Installation Template with Channel Bonding Sample Installation Template without Channel Bonding Documentation Accessibility

Notes:

Complete the configuration worksheets early in the process, and prior to receiving your Oracle Exadata Database Machine so that site-specific adjustments to the Installation Template do not delay installation. If you have purchased more than one Oracle Exadata Database Machine and you do not plan to cable them together, then you must complete one set of worksheets for each Oracle Exadata Database Machine.

Overview of the Network Configuration Process

The following procedure describes the network configuration process:
1. 2. 3. 4.

Read this document and the owners guide to understand the networking requirements and guidelines. Identify your current management network. Identify your current client access network. Decide if channel bonding will be used to access the client access network. Oracle recommends bonding the client access network to provide higher availability for client connections to the database.
See Also: Oracle Exadata Database Machine Owner's Guide for information about channel bonding

5.

Determine if you need to connect any additional networks.

See Also: Oracle Exadata Database Machine Owner's Guide for information about additional networks

6.

Determine if you will connect multiple Oracle Exadata Database Machines, or segregate Oracle Exadata Database Machine into clusters. If you plan do to either of these, then contact your Oracle representative. Determine which OS owner mode to use. The options are Standard OS Authentication (Table 1) and Role Separated Authentication (Table 2). Determine the operating system to be installed on the database servers. Fill out the configuration worksheets, and supply the completed configuration worksheets to your Oracle representative. The information provided by you will be used to generate the Installation Template. Installation Template is provided by your Oracle representative based on the worksheets completed in step 9.
Note: Inform your Oracle representative if there are any site-specific adjustments.

7. 8. 9.

10. Verify the Installation Template that will be used during initial configuration. The

11. Configure your existing network to use the new IP addresses and host names

supplied on the Installation Template in your existing networks.

See Also: Oracle Exadata Database Machine Owner's Guide for information about DNS configuration
12. Review the network and IP address requirements, and the Installation Template to

understand the network connections necessary.

See Also: Oracle Exadata Database Machine Owner's Guide for information about network and IP address requirements
13. Run the network connections to the planned Oracle Exadata Database Machine

location.
14. Inform your Oracle representative when you have completed these steps.

Your site is now ready to receive your Oracle Exadata Database Machine.

Default Oracle Environment Settings

Table 1 lists the default settings when selecting Standard OS Authentication for the OS owner used during installation to create the Oracle software environment. These default settings are in addition to the information in the configuration worksheets.
Table 1 Oracle Environment Default Settings when Using Standard OS Authentication
Default Setting

Oracle Database Item Oracle Inventory group name Oracle Inventory group identifier DBA group name DBA group identifier Oracle software owner user name Oracle software owner user identifier Oracle software owner default password Oracle base directory (ORACLE_BASE) Oracle inventory directory Grid infrastructure home directory Database name Database character set Database national character set Database block size

oinstall 1001 dba 1002 o11gdb 1000

welcome /u01/app/oracle /u01/app/oraInventory /u01/app/11.2.0/grid

dbm
AL32UTF81 AL16UTF161 8192

Table 1 (Cont.) Oracle Environment Default Settings when Using Standard OS

Oracle Database Item ASM disk groups Default Setting DATA for the default data file location RECO for the fast recovery area Note: Default DATA and RECO disk group size depends on the type of system, the type of disk drives, and the type of backup. Exadata Smart Flash Cache Starting IP address for InfiniBand private network2 Subnet mask for InfiniBand network2
1

All flash disks are configured as flash cache 192.168.10.1 255.255.252.0

The default database created during installation uses Unicode database character set AL32UTF8, and national character set AL16UTF16. Oracle recommends Unicode for all new deployments. To use a different database character set or national character set after installation, run Database Configuration Assistant (DBCA) to create a new database using the desired character set, and to delete the default database. All InfiniBand addresses must be in the same subnet, with a minimum subnet mask of 255.255.252.0 (or /22). The subnet mask chosen should be wide enough to accommodate possible future expansion of the Oracle Exadata Database Machine and InfiniBand network.

Table 2 lists the default settings when selecting Role Separated Authentication for the OS owner used during installation to create the Oracle software environment. These default settings are in addition to the information in the configuration worksheets.
Table 2 Oracle Environment Default Settings when Using Role Separated Authentication
Default Setting

Oracle Database Item Grid infrastructure user name Grid infrastructure identifier RAC home user name RAC home identifier Oracle inventory group name Oracle inventory identifier RAC home DBA group name RAC home DBA group identifier RAC home OPER group name RAC home OPER group identifier ASM DBA group name ASM DBA group identifier ASM OPER group name ASM OPER group identifier ASM ADMIN group name

ogrid 1000 o11gdb 1001 oinstall 1001 dba 1002 racoper 1003 asmdba 1004 asmoper 1005 asmadmin

Table 2 (Cont.) Oracle Environment Default Settings when Using Role Separated
Oracle Database Item ASM ADMIN group identifier Oracle software owner default password Grid infrastructure home base directory Oracle database home base directory (ORACLE_BASE) Oracle home directory (ORACLE_HOME) Oracle Inventory directory Grid infrastructure home directory Database name Database character set Database national character set Database block size ASM disk groups Default Setting

1006
welcome /u01/app/grid /u01/app/oracle /u01/app/oracle/product/11.2.0/dbhome_1 /u01/app/oraInventory /u01/app/11.2.0/grid

dbm
AL32UTF81 AL16UTF161 8192 DATA for the default data file location RECO for the fast recovery area Note: Default DATA and RECO disk group size depends on the type of system, the type of disk drives, and the type of backup.

Exadata Smart Flash Cache Starting IP address for InfiniBand private network2 Subnet mask for InfiniBand network2
1

All flash disks are configured as flash cache 192.168.10.1 255.255.252.0

The default database created during installation uses Unicode database character set AL32UTF8, and national character set AL16UTF16. Oracle recommends Unicode for all new deployments. To use a different database character set or national character set after installation, run Database Configuration Assistant (DBCA) to create a new database using the desired character set, and to delete the default database. All InfiniBand addresses must be in the same subnet, with a minimum subnet mask of 255.255.252.0 (or /22). The subnet mask chosen should be wide enough to accommodate possible future expansion of the Oracle Exadata Database Machine and InfiniBand network.

See Also:

Oracle Database Installation Guide 11g Release 2 (11.2) for Linux for additional information about the Oracle Database default settings Oracle Database Globalization Support Guide for additional information about using Unicode and selecting a proper database character set.

General Configuration Worksheet (Required)

Table 3 is the general configuration worksheet. All information in the worksheet is required. When filling out the worksheet, note the following items:

Oracle Exadata Database Machine ships with both Linux operating system and Solaris operating system installed on the database servers, with Linux operating system as the default. The Solaris operating system can be chosen and configured during initial configuration. The Oracle Exadata Database Machine name is used to generate host names for network interfaces for all systems. For example, a value of dm01 will result in a database server host name of dm01db01, and a storage server host name of dm01cel01. See "Sample Installation Template with Channel Bonding" on page 1-17 for an example of the Installation Template. The backup method information is used to size the ASM disk groups created during installation. The amount of usable disk space varies depending on the backup method. The backup methods are as follows: Backups internal to Oracle Exadata Database Machine indicates database backups will be created only on disk in the Fast Recovery Area (FRA). In addition to the database backups, there are other objects such as Archived Redo Logs and Flashback Log Files stored in the FRA. The division of disk space between the DATA disk group and the RECO disk group (the FRA) will be 40% and 60%, respectively. Backups external to Oracle Exadata Database Machine indicates database backups will be created on disk or tape media that is external to Oracle Exadata Database Machine, and not on Exadata Storage Servers. If you are performing backups to disk storage external to Oracle Exadata Database Machine, such as to additional dedicated Exadata Storage Servers, an NFS server, virtual tape library or tape library, then select this option. When choosing this option, the FRA internal to Oracle Exadata Database Machine will contain objects such as archived redo log files and flashback log files. The division of disk space between the DATA disk group and the RECO disk group (the FRA) will be 80% and 20%, respectively.

The protection level varies depending on the choice of backup method. Oracle recommends the use of high redundancy disk groups for mission critical applications. High Redundancy for ALL: This protection level is only applicable when the backup location is external to Oracle Exadata Database Machine. Both the DATA disk group and RECO disk group are configured with Oracle ASM high redundancy. The DATA disk group contains data files, temporary files, online redo logs, and control file. The RECO disk group contains archive logs, and flashback log files. High Redundancy for DATA: This protection level is applicable when the backup location is internal or external to Oracle Exadata Database Machine. The DATA disk group is configured with Oracle ASM high redundancy, and the RECO disk group is configured with Oracle ASM normal redundancy. The DATA disk group contains data files, temporary files, online redo logs, and control file. The RECO disk group contains archive logs, and flashback log files. High Redundancy for Log and RECO: This protection level is only applicable when the backup location is external to Oracle Exadata Database Machine. The

DATA disk group is configured with Oracle ASM normal redundancy, and the RECO disk group is configured with Oracle ASM high redundancy. The DATA disk group contains the data files and temporary files. The RECO disk group contains online redo logs, control file, archive logs, and flashback log files. Normal Redundancy: This protection level is applicable when the backup location is internal or external to Oracle Exadata Database Machine. The DATA Disk Group and RECO disk group are configured with Oracle ASM normal redundancy. The DATA disk group contains data files, temporary files, online redo logs, and control file. The RECO disk group contains archive logs, and flashback log files.
See Also: Oracle Exadata Storage Server Software User's Guide for information about maximum availability

A valid time zone name is required for Oracle Exadata Database Machine installation. Time zone data provided with Oracle Exadata Database Machine and Oracle Enterprise Linux comes from the zoneinfo database. A valid time zone name is suitable as a value for the TZ environment variable consisting of form Area/Location. For example, a valid entry is America/New_York. Invalid entries are EST, EDT, UTC-5, and UTC-4. For a list of time zone names, refer to the zone.tab file in the zoneinfo database available in the public domain at ftp://elsie.nci.nih.gov/pub/

Table 3
Item

General Configuration Worksheet

Entry Description and Example The operating system for the database servers. Valid value: Linux or Solaris This name is the basis for all host names generated during installation. Select a value of 4 characters or fewer. Example: dm01

Operating system

Linux

Oracle Exadata Database Machine name

XGEP

Type of system

X2-2 Quarter Rack

Type of Oracle Exadata Database Machine being installed at your site. Valid values: X2-2 Full Rack, X2-2 Half Rack, X2-2 Quarter Rack, or X2-8 Full Rack

Disk type

High Performance

Type of hard disks in Oracle Exadata Database Machine. Valid values: High Performance or High Capacity Country where Oracle Exadata Database Machine will be installed. Example: United States

Country

Mxico

Table 3 (Cont.) General Configuration Worksheet

Item Time zone name Entry Description and Example Time zone name where Oracle Exadata Database Machine will be installed. Example: America/Los_ Angeles Workload type

Mexico/General

OLTP

Type of workload that will mainly be running on the database. Valid values: DW or OLTP

Backup method

Type of database backups for Oracle Exadata Database Backups external to Oracle Exadata Database Machine Machine. Valid values: Backups internal to Oracle Exadata Database Machine, and backups external to Oracle Exadata Database Machine

Protection level

High for DATA

Type of protection level for Oracle ASM disk groups.

Network Configuration Worksheets

The following networks are used with Oracle Exadata Database Machine:

Management network Client access network InfiniBand private network Additional networks (optional)

The InfiniBand private network is a non-routable network fully contained in Oracle Exadata Database Machine, and does not connect to your existing network. This network is automatically configured during installation. Prior to filling out the network configuration worksheets, refer to Oracle Exadata Database Machine Owner's Guide for a description of each network, and the IP address requirements specific to each type of Oracle Exadata Database Machine.
Note:

All networks must be on distinct and separate subnets from each other. All IP addresses must be statically-assigned IP addresses, not dynamically-assigned (DHCP) addresses.

This section contains the following worksheets:

General Network Configuration Worksheet (Required) Management Network Configuration Worksheet (Required) Client Access Network Configuration Worksheet (Required)

Additional Network NET2 Configuration Worksheet (Optional) Additional Network NET3 Configuration Worksheet (Optional) Power Distribution Unit Configuration Worksheet (Optional)
Note: The 10 Gigabit Ethernet (GbE) card in the rack can be used for the client access network, or a network connected to a media server for backups. Oracle does not configure this network as part of the deployment.

See Also: Oracle Exadata Database Machine Owner's Guide for additional information about network requirements

General Network Configuration Worksheet (Required)

Table 4 is the general network configuration worksheet.
Table 4
Item Domain name

General Network Configuration Worksheet

Entry Description and Example Company network domain name. Example: example.com

IP address of the name server

IP address of one or more network name servers. Example: 10.25.45.123, 10.25.45.125 Note: If you do not use DNS, then enter None.

IP address of the Network Time Protocol (NTP) time server

IP address of one or more network time servers. Example: 10.25.45.127

Management Network Configuration Worksheet (Required)

The management network is used for administrative work for all components of Oracle Exadata Database Machine. It connects the NET0 network interface on all servers, Integrated Lights Out Manager (ILOM), and switches to the Cisco Catalyst 4948 Ethernet switch in the rack. The Cisco Catalyst 4948 Ethernet switch supplied with Oracle Exadata Database Machine is minimally configured during installation. The minimal configuration disables IP routing, and sets the following:

Host name IP address Subnet mask Default gateway Domain name Name server

NTP server Time Time zone

Additional configuration, such as defining multiple virtual local area networks (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. If additional configuration is needed, then your network administrator must perform the necessary configuration steps during installation of Oracle Exadata Database Machine. Table 5 is the management network configuration worksheet.
Table 5
Item Starting IP address

Management Network Configuration Worksheet

Entry Description and Example First IP address in the sequential range used for management/network interfaces. This network must be distinct from all other networks on Oracle Exadata Database Machine. Example: 10.204.74.100

Subnet mask

Subnet mask for the management network. Example: 255.255.248.0

Gateway IP address

Gateway IP address for the management network. Example: 10.204.72.1

Client Access Network Configuration Worksheet (Required)

The client access network is used for client access to the database servers. Table 6 is the client access network configuration worksheet.
Table 6
Item Client access network Will channel bonding be used?

Client Access Network Configuration Worksheet

Entry Description and Example The default network is 1 GbE. Valid values: 1 GbE or 10 GbE Channel bonding uses NET1 and NET2 ports to provide higher availability for client connections to the database. Note: Oracle recommends channel bonding be used to provide higher availability. Valid values: yes or no

1 GbE

Yes

10

Table 6 (Cont.) Client Access Network Configuration Worksheet

Item Starting IP address Entry Description and Example First IP address in the sequential range used for client access network interfaces. This network must be distinct from all other networks on Oracle Exadata Database Machine. Example: 172.16.10.100 Subnet mask Subnet mask for client access network. Example: 255.255.252.0 Gateway IP address Gateway IP address for the client access network. Example: 172.16.8.1

Additional Network NET2 Configuration Worksheet (Optional)

This is an optional network. Table 7 is the additional network NET2 configuration worksheet.
Note: If channel bonding is used for the client access network, then this worksheet is not needed because this network interface is unavailable for configuration.

Oracle recommends channel bonding to provide higher availability for client connections to the database.

Table 7
Item

Additional Network NET2 Configuration Worksheet

Entry Description and Example First IP address in the sequential range used for additional network NET2 interfaces. This network must be distinct from all other networks on Oracle Exadata Database Machine. Example: 10.201.21.100

Starting IP address

Subnet mask

Subnet mask for the additional network NET2. Example: 255.255.252.0

Gateway IP address

Gateway IP address for the additional network NET2. Example: 10.201.20.1

Network host name suffix

Suffix appended to host names to identify the NET2 network. Example: bck

11

Additional Network NET3 Configuration Worksheet (Optional)

This is an optional network. Table 8 is the additional network NET3 configuration worksheet.
Table 8
Item Network specification

Additional Network NET3 Configuration Worksheet

Entry Description and Example The default network is 1 GbE. 10 GbE can be used if it is not used for the client access network. First IP address in the sequential range used for additional network NET3 interfaces. This network must be distinct from all other networks on Oracle Exadata Database Machine. Example: 10.202.46.100

1 GbE

Starting IP address

Subnet mask

Subnet mask for the additional network NET3. Example: 255.255.252.0

Gateway IP address

Gateway IP address for the additional network NET3. Example: 10.202.44.1

Network host name suffix

Suffix appended to host names to identify the NET3 network. Example: dr

Power Distribution Unit Configuration Worksheet (Optional)

This is an optional set of network connections to the power distribution units (PDUs) in the rack. Table 9 is the PDU configuration worksheet.
Table 9
Item Monitor PDU over network PDU-A IP address [eth0] PDU-B IP address [eth0]

Power Distribution Unit Configuration Worksheet

Entry Description and Example The PDU can be monitored over the network. IP address for PDU-A in the rack. IP address for PDU-B in the rack.

Yes

Oracle Configuration Manager Configuration Worksheets (Recommended)

Oracle Configuration Manager can be configured for use with Oracle Exadata Database Machine. Table 10 is the Oracle Configuration Manager worksheet.

12

See Also: Oracle Configuration Manager Support for Sun Oracle Database Machine
Table 10
Item My Oracle Support e-mail address

Oracle Configuration Manager Configuration Worksheet

Entry Description and Example Provide your e-mail address to be informed of security issues, install the product, and initiate configuration manager. Easier for you to use your My Oracle Support e-mail address/user name. I wish to recieve security updates via My Oracle Support. We will need your My Oracle Support password at installation time. Do not provide the password now. See Also: Oracle support policies at http://www.oracle.com/us/ support/policies/index.ht ml

Support Hub host name

The host name for Support Hub server if you want use Support Hub1. See Also: Oracle Configuration Manager Manager Companion Distribution Guide

Support Hub user name

The operating system user name for Support Hub server, if you want to use Support Hub. The proxy server to connect to Oracle. The proxy may be between the following:

Proxy servers for connectivity to Oracle

Database servers and Oracle2 Database servers and Support Hub3 Support Hub and Oracle3

Example: [proxy_ user@]proxy_host[:proxy_ port] The proxy_host and proxy_ port entries are optional. Note: If passwords are needed, then provide them during installation.

13

2 3

Oracle Support Hub allows Oracle Configuration Manager instances to connect to a single internal port (the Support Hub), and upload configuration data, eliminating the need for each individual Oracle Configuration Manager instance in the database servers to access the Internet. Applicable when you do not have Oracle Support Hub. Applicable when you only have Oracle Support Hub.

Auto Service Request Configuration Worksheet (Recommended)

Auto Service Request (ASR) can be installed and configured for use with Oracle Exadata Database Machine. Table 11 is the Auto Service Request worksheet.
Table 11
Item Enable ASR Install ASR Host name for ASR Manager

Auto Service Request Configuration Worksheet

Entry Description and Example Enable ASR for use with Oracle Exadata Database Machine. Install ASR for use with Oracle Exadata Database Machine The host name of the server for ASR. Note: Oracle recommends a standalone server that has connectivity to Oracle Exadata Database Machine.

First and last name of technical contact for ASR

The name of the person responsible as the technical contact for Oracle Exadata Database Machine. The e-mail address of the person responsible as technical contact for Oracle Exadata Database Machine. The Sun Online Account (SOA) name.

E-mail address of technical contact for ASR

Sun Online Account name Will a proxy server be used with ASR Manager? Proxy server address used with ASR Proxy server port Will the SOA and proxy server passwords available at time of installation?

Yes

A proxy server can be used for direct load to the Internet. The address of the proxy server. The port used by the proxy server.

Yes

The SOA and proxy server passwords are needed at installation time.

Oracle Enterprise Manager Grid Control Configuration Worksheets (Recommended)

A new or existing installation of Oracle Enterprise Manager Grid Control can be used with Oracle Exadata Database Machine.

14

See Also:

Oracle Exadata Database Machine Owner's Guide for information about installing Oracle Enterprise Manager Grid Control My Oracle Support note 1110675.1 ARU 13647201 for the scripts

Table 12 is the worksheet for a new installation of Oracle Enterprise Manager Grid Control.
Table 12 New Installation of Oracle Enterprise Manager Grid ControlConfiguration Worksheet
Item Will Oracle Enterprise Manager Grid Control be a new installation? Entry Description and Example Oracle Enterprise Manager Grid Control can install agents on Oracle Exadata Database Machine database servers and point the agents to an existing Oracle Enterprise Manager Grid Control environment, or install a new Oracle Enterprise Manager Grid Control infrastructure on a separate host. The password used for secure communication between OMS and the agent. Note: This password only applicable when pointing the agents to an existing Oracle Enterprise Manager Grid Control environment. Host name for Oracle Enterprise Manager Grid Control repository Port for upload The host name where Oracle Enterprise Manager Grid Control repository will be installed. The port the Oracle Enterprise Manager Grid Control agent should use to upload information. The base directory for the agents installed on the Oracle Exadata Database Machine database servers.

YES

Oracle Management Service (OMS) password

Oracle Enterprise Manager Grid Control base directory

Table 13 is the worksheet when using an existing installation of Oracle Enterprise Manager Grid Control.
Table 13 Existing Installation of Oracle Enterprise Manager Grid Control Configuration Worksheet
Item URL for Oracle Enterprise Manager Grid Control Entry Description and Example The URL for Oracle Enterprise Manager Grid Control.

15

Table 13 (Cont.) Existing Installation of Oracle Enterprise Manager Grid Control Configuration Worksheet
Item Agent password for initial connection Entry Description and Example The agent password for the first connection.

Cell Alert Delivery Configuration Worksheet (Optional)

Cell alerts can be delivered by way of Simple Mail Transfer Protocol (SMTP), Simple Network Management Protocol (SNMP), or both. Cell alert delivery may be configured during or after installation. To have cell alert delivery configured during installation, complete Table 14. Configuration is optional, but recommended.
Table 14
Item smtpServer

Cell Alert Delivery Configuration Worksheet

Entry Description and Example SMTP e-mail server used to send alert notifications. Example: mail.example.com

smtpPort

SMTP e-mail server port used to send alert notifications. Example: 25 or 465

smtpUseSSL

Yes

Specification to use Secure Socket Layer (SSL) security when sending alert notifications. Valid values: yes or no

smtpToAddr

Address to send e-mail messages. It can be a comma-delimited list to allow multiple subscribers to alerts. Example: "all-admins@example.com, john.doe@example.com"

smtpFromAddr

SMTP e-mail address that sends alert notifications. Example: dm01@example.com

smtpFrom

SMTP e-mail user name that appears in alert notifications. Example: "Oracle Exadata Database Machine"

smtpUser

User name used for SMTP authentication. This parameter requires a value if the e-mail server requires a user name and password to send e-mail. Example: john.doe@example.com

16

Table 14 (Cont.) Cell Alert Delivery Configuration Worksheet

Item smtpPwd Entry Description and Example Password used for SMTP authentication. This parameter requires a value if your e-mail server requires a user name and password to send e-mail messages. Example: password snmpSubscriber Host, optional port, and optional community that subscribe to the SNMP alert notifications. The default port is 162. The default community is public. Example: snmp.example.com,162,public Note: Additional SNMP targets may be defined after installation. Refer to Oracle Exadata Storage Server Software User's Guide for additional information.

Sample Installation Template with Channel Bonding

The following is an example of a completed Installation Template for Oracle Exadata Database Machine in which the client access network uses channel bonding. General Information Oracle Exadata Database Machine name: Type of System: Disk Type: Country: Time Zone Name: Backup Method: Default Oracle Environment Settings Oracle Inventory group name: Oracle Inventory group identifier: DBA group name: DBA group identifier: OPER group name: OPER group identifier: Oracle software owner user name: Oracle software owner user identifier: oinstall 1001 dba 1002 dba 1002 oracle 1000 dm01 Full rack 600G United States (US) America/Los_Angeles Tape only

17

Oracle software owner default password: Oracle base directory (ORACLE_BASE): Oracle Inventory directory: Grid infrastructure home directory: Database name: ASM disk groups: DATA size: RECO for the fast recovery area: RECO size: Exadata Smart Flash Cache: General Network Configuration Domain Name: IP address of name server(s): IP addr of the NTP server(s): example.com

welcome /u01/app/oracle /u01/app/oraInventory /u01/app/11.2.0/grid dbm 2 33.5T 16.9T All flash disks

(10.25.45.123, 10.25.45.125) (10.25.45.127)

Management Network Configuration All IP addresses and corresponding host names should be registered in DNS Starting IP Address: Subnet Mask: Gateway: Total IP addresses: Network connection requirements: 10.204.74.100 255.255.248.0 10.204.72.1 51 1 Ethernet connection for the Ethernet switch in the rack to connect to the existing management network 1 Ethernet connection for the KVM switch to connect to the existing management network 2 Ethernet connections for the PDUs (one connection per PDU) to connect to the existing management network Server Components
Rack U Location U41 U39 U37 NET0 IP Address 10.204.74.121 10.204.74.120 10.204.74.119 ILOM IP Address 10.204.74.143 10.204.74.142 10.204.74.141

Component

NET0 Name

ILOM Name dm01cel14-ilom dm01cel13-ilom dm01cel12-ilom

Exadata dm01cel14 Storage Server Exadata dm01cel13 Storage Server Exadata dm01cel12 Storage Server

18

Rack U Location U35 U33 U31 U29 U28 U27 U26 U25 U19 U18 U17 U16 U14 U12 U10 U8 U6 U4 U2

Component

NET0 Name

NET0 IP Address 10.204.74.118 10.204.74.117 10.204.74.116 10.204.74.115 10.204.74.107 10.204.74.106 10.204.74.105 10.204.74.104 10.204.74.103 10.204.74.102 10.204.74.101 10.204.74.100 10.204.74.114 10.204.74.113 10.204.74.112 10.204.74.111 10.204.74.110 10.204.74.109 10.204.74.108

ILOM Name dm01cel11-ilom dm01cel10-ilom dm01cel09-ilom dm01cel08-ilom dm01db08-ilom dm01db07-ilom dm01db06-ilom dm01db05-ilom dm01db04-ilom dm01db03-ilom dm01db02-ilom dm01db01-ilom dm01cel07-ilom dm01cel06-ilom dm01cel05-ilom dm01cel04-ilom dm01cel03-ilom dm01cel02-ilom dm01cel01-ilom

ILOM IP Address 10.204.74.140 10.204.74.139 10.204.74.138 10.204.74.137 10.204.74.129 10.204.74.128 10.204.74.127 10.204.74.126 10.204.74.125 10.204.74.124 10.204.74.123 10.204.74.122 10.204.74.136 10.204.74.135 10.204.74.134 10.204.74.133 10.204.74.132 10.204.74.131 10.204.74.130

Exadata dm01cel11 Storage Server Exadata dm01cel10 Storage Server Exadata dm01cel09 Storage Server Exadata dm01cel08 Storage Server Database server Database server Database server Database server Database server Database server Database server Database server dm01db08 dm01db07 dm01db06 dm01db05 dm01db04 dm01db03 dm01db02 dm01db01

Exadata dm01cel07 Storage Server Exadata dm01cel06 Storage Server Exadata dm01cel05 Storage Server Exadata dm01cel04 Storage Server Exadata dm01cel03 Storage Server Exadata dm01cel02 Storage Server Exadata dm01cel01 Storage Server

Switch Components
Rack U Location U24 U23

Component InfiniBand Switch Ethernet Switch

Admin Name dm01sw-ib3 dm01sw-ip

Admin IP Address 10.204.74.148 10.204.74.145

19

Rack U Location U21 U20 U1

Component KVM Switch InfiniBand Switch InfiniBand Spine Switch

Admin Name dm01sw-kvm dm01sw-ib2 dm01sw-ib1

Admin IP Address 10.204.74.144 10.204.74.147 10.204.74.146

Client Access Network Configuration All IP addresses and corresponding host names should be registered in DNS Starting IP Address: Subnet Mask: Gateway: Total IP addresses: Channel Bonding in Use: Network connection requirements: SCAN Name: SCAN IP addresses: Client Access Components
Rack U Location U28 U27 U26 U25 U19 U18 U17 U16 eth1 IP address 172.16.10.107 172.16.10.106 172.16.10.105 172.16.10.104 172.16.10.103 172.16.10.102 172.16.10.101 172.16.10.100 VIP IP address 172.16.10.115 172.16.10.114 172.16.10.113 172.16.10.112 172.16.10.111 172.16.10.110 172.16.10.109 172.16.10.108

172.16.10.100 255.255.252.0 172.16.8.1 19 Yes 16 Ethernet connections to connect database servers NET1 and NET2 ports to the client access network dm01-scan (172.16.10.116, 172.16.10.117, 172.16.10.118)

Component Database server Database server Database server Database server Database server Database server Database server Database server

eth1 name dm0108 dm0107 dm0106 dm0105 dm0104 dm0103 dm0102 dm0101

VIP name dm0108-vip dm0107-vip dm0106-vip dm0105-vip dm0104-vip dm0103-vip dm0102-vip dm0101-vip

Additional Network NET2 Configuration Unavailable for configuration because a bonded network configuration is used for the client access network

20

Additional Network NET3 Configuration All IP addresses and corresponding host names should be registered in DNS Starting IP Address: Subnet Mask: Gateway: Total IP addresses: Network connection requirements: 10.201.46.100 255.255.252.0 10.202.44.1 8 8 Ethernet connections to connect database servers to additional network NET3

Additional Network NET3 Components

Rack U Location U28 U27 U26 U25 U19 U18 U17 U16 Component Database server Database server Database server Database server Database server Database server Database server Database server NET2 Name dm0108-dr dm0107-dr dm0106-dr dm0105-dr dm0104-dr dm0103-dr dm0102-dr dm0101-dr NET2 IP Address 10.201.46.107 10.201.46.106 10.202.46.105 10.202.46.104 10.202.46.103 10.202.46.102 10.202.46.101 10.202.46.100

Private InfiniBand Network Configuration Starting IP Address: Subnet Mask: Network connection requirements: InfiniBand Components
Rack U Location U41 U39 U37 U35 U33 U31 Component Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server BOND0 Name dm01cel14-priv dm01cel13-priv dm01cel12-priv dm01cel11-priv dm01cel10-priv dm01cel09-priv BOND0 IP Address 192.168.10.22 192.168.10.21 192.168.10.20 192.168.10.19 192.168.10.18 192.168.10.17

192.168.10.1 255.255.248.0 None, the InfiniBand network is fully contained within Oracle Exadata Database Machine

21

Rack U Location U29 U28 U27 U26 U25 U19 U18 U17 U16 U14 U12 U10 U8 U6 U4 U2

Component Exadata Storage Server Database server Database server Database server Database server Database server Database server Database server Database server Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server

BOND0 Name dm01cel08-priv dm01db08-priv dm01db07-priv dm01db06-priv dm01db05-priv dm01db04-priv dm01db03-priv dm01db02-priv dm01db01-priv dm01cel07-priv dm01cel06-priv dm01cel05-priv dm01cel04-priv dm01cel03-priv dm01cel02-priv dm01cel01-priv

BOND0 IP Address 192.168.10.16 192.168.10.8 192.168.10.7 192.168.10.6 192.168.10.5 192.168.10.4 192.168.10.3 192.168.10.2 192.168.10.1 192.168.10.15 192.168.10.14 192.168.10.13 192.168.10.12 192.168.10.11 192.168.10.10 192.168.10.9

Cell Alert Delivery Configuration SMTP Notification Email Server: Port: Use SSL: To Address: Enabled mail.example.com 465 Yes all-admins@example.com john.doe@example.com From Address: From Name: Auth User: Auth Password: SNMP Notification SNMP Server: SNMP Port: dm01@example.com DBM dm01 john.doe@example.com password Enabled snmp.example.com 162

22

Sample Installation Template without Channel Bonding

The following is an example of a completed Installation Template for Oracle Exadata Database Machine in which the client access network does not use channel bonding. General Information Oracle Exadata Database Machine name: Type of System: Disk Type: Country: Time Zone Name: Backup Method: Default Oracle Environment Settings Oracle Inventory group name: Oracle Inventory group identifier: DBA group name: DBA group identifier: OPER group name: OPER group identifier: Oracle software owner user name: Oracle software owner user identifier: Oracle software owner default password: Oracle base directory (ORACLE_BASE): Oracle Inventory directory: Grid infrastructure home directory: Database name: ASM disk groups: DATA size: RECO for the fast recovery area: RECO size: Exadata Smart Flash Cache: General Network Configuration Domain Name: IP address of name server(s): IP addr of the NTP server(s): example.com (10.25.45.123, 10.25.45.125) (10.25.45.127) 16.9T All flash disks oinstall 1001 dba 1002 dba 1002 oracle 1000 welcome /u01/app/oracle /u01/app/oraInventory /u01/app/11.2.0/grid dbm 2 33.5T dm01 Full rack 600G United States (US) America/Los_Angeles Tape only

23

Management Network Configuration All IP addresses and corresponding host names should be registered in DNS Starting IP Address: Subnet Mask: Gateway: Total IP addresses: Network connection requirements: 10.204.74.100 255.255.248.0 10.204.72.1 51 1 Ethernet connection for the Ethernet switch in the rack to connect to the existing management network 1 Ethernet connection for the KVM switch to connect to the existing management network 2 Ethernet connections for the PDUs (one connection per PDU) to connect to the existing management network Server Components
Rack U Location U41 U39 U37 U35 U33 U31 U29 U28 U27 U26 U25 U19 U18 U17 NET0 IP Address 10.204.74.121 10.204.74.120 10.204.74.119 10.204.74.118 10.204.74.117 10.204.74.116 10.204.74.115 10.204.74.107 10.204.74.106 10.204.74.105 10.204.74.104 10.204.74.103 10.204.74.102 10.204.74.101 ILOM IP Address 10.204.74.143 10.204.74.142 10.204.74.141 10.204.74.140 10.204.74.139 10.204.74.138 10.204.74.137 10.204.74.129 10.204.74.128 10.204.74.127 10.204.74.126 10.204.74.125 10.204.74.124 10.204.74.123

Component

NET0 Name

ILOM Name dm01cel14-ilom dm01cel13-ilom dm01cel12-ilom dm01cel11-ilom dm01cel10-ilom dm01cel09-ilom dm01cel08-ilom dm01db08-ilom dm01db07-ilom dm01db06-ilom dm01db05-ilom dm01db04-ilom dm01db03-ilom dm01db02-ilom

Exadata dm01cel14 Storage Server Exadata dm01cel13 Storage Server Exadata dm01cel12 Storage Server Exadata dm01cel11 Storage Server Exadata dm01cel10 Storage Server Exadata dm01cel09 Storage Server Exadata dm01cel08 Storage Server Database server Database server Database server Database server Database server Database server Database server dm01db08 dm01db07 dm01db06 dm01db05 dm01db04 dm01db03 dm01db02

24

Rack U Location U16 U14 U12 U10 U8 U6 U4 U2

Component Database server

NET0 Name dm01db01

NET0 IP Address 10.204.74.100 10.204.74.114 10.204.74.113 10.204.74.112 10.204.74.111 10.204.74.110 10.204.74.109 10.204.74.108

ILOM Name dm01db01-ilom dm01cel07-ilom dm01cel06-ilom dm01cel05-ilom dm01cel04-ilom dm01cel03-ilom dm01cel02-ilom dm01cel01-ilom

ILOM IP Address 10.204.74.122 10.204.74.136 10.204.74.135 10.204.74.134 10.204.74.133 10.204.74.132 10.204.74.131 10.204.74.130

Exadata dm01cel07 Storage Server Exadata dm01cel06 Storage Server Exadata dm01cel05 Storage Server Exadata dm01cel04 Storage Server Exadata dm01cel03 Storage Server Exadata dm01cel02 Storage Server Exadata dm01cel01 Storage Server

Switch Components
Rack U Location U24 U23 U21 U20 U1

Component InfiniBand Switch Ethernet Switch KVM Switch InfiniBand Switch InfiniBand Spine Switch

Admin Name dm01sw-ib3 dm01sw-ip dm01sw-kvm dm01sw-ib2 dm01sw-ib1

Admin IP Address 10.204.74.148 10.204.74.145 10.204.74.144 10.204.74.147 10.204.74.146

Client Access Network Configuration All IP addresses and corresponding host names should be registered in DNS Starting IP Address: Subnet Mask: Gateway: Total IP addresses: Channel Bonding in Use: Network connection requirements: SCAN Name: SCAN IP addresses: 172.16.10.100 255.255.252.0 172.16.8.1 19 No 8 Ethernet connections to connect database servers NET1 port to the client access network dm01-scan (172.16.10.116, 172.16.10.117, 172.16.10.118)

25

Client Access Components

Rack U Location U28 U27 U26 U25 U19 U18 U17 U16 eth1 IP address 172.16.10.107 172.16.10.106 172.16.10.105 172.16.10.104 172.16.10.103 172.16.10.102 172.16.10.101 172.16.10.100 VIP IP address 172.16.10.115 172.16.10.114 172.16.10.113 172.16.10.112 172.16.10.111 172.16.10.110 172.16.10.109 172.16.10.108

Component Database server Database server Database server Database server Database server Database server Database server Database server

eth1 name dm0108 dm0107 dm0106 dm0105 dm0104 dm0103 dm0102 dm0101

VIP name dm0108-vip dm0107-vip dm0106-vip dm0105-vip dm0104-vip dm0103-vip dm0102-vip dm0101-vip

Additional Network NET2 Configuration

Note: If you choose to not use channel bonding, then NET2 would include values similar to the following values.

All IP addresses and corresponding host names should be registered in DNS Starting IP Address: Subnet Mask: Gateway: Total IP addresses: Network connection requirements: 10.201.21.100 255.255.252.0 10.201.20.1 8 8 Ethernet connections to connect database servers to additional network NET2

Additional Network NET2 Components

Note: If you choose to not use channel bonding, then NET2 would include values similar to the following values.

Rack U Location U28 U27 U26

Component Database server Database server Database server

NET2 Name dm0108-bck dm0107-bck dm0106-bck

NET2 IP Address 10.201.21.107 10.201.21.106 10.201.21.105

26

Rack U Location U25 U19 U18 U17 U16

Component Database server Database server Database server Database server Database server

NET2 Name dm0105-bck dm0104-bck dm0103-bck dm0102-bck dm0101-bck

NET2 IP Address 10.201.21.104 10.201.21.103 10.201.21.102 10.201.21.101 10.201.21.100

Additional Network NET3 Configuration All IP addresses and corresponding host names should be registered in DNS Starting IP Address: Subnet Mask: Gateway: Total IP addresses: Network connection requirements: 10.201.46.100 255.255.252.0 10.202.44.1 8 8 Ethernet connections to connect database servers to additional network NET3

Additional Network NET3 Components

Rack U Location U28 U27 U26 U25 U19 U18 U17 U16 Component Database server Database server Database server Database server Database server Database server Database server Database server NET2 Name dm0108-dr dm0107-dr dm0106-dr dm0105-dr dm0104-dr dm0103-dr dm0102-dr dm0101-dr NET2 IP Address 10.201.46.107 10.201.46.106 10.202.46.105 10.202.46.104 10.202.46.103 10.202.46.102 10.202.46.101 10.202.46.100

Private InfiniBand Network Configuration Starting IP Address: Subnet Mask: Network connection requirements: InfiniBand Components
Rack U Location U41 Component Exadata Storage Server BOND0 Name dm01cel14-priv BOND0 IP Address 192.168.10.22

192.168.10.1 255.255.248.0 None, the InfiniBand network is fully contained within Oracle Exadata Database Machine

27

Rack U Location U39 U37 U35 U33 U31 U29 U28 U27 U26 U25 U19 U18 U17 U16 U14 U12 U10 U8 U6 U4 U2

Component Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server Database server Database server Database server Database server Database server Database server Database server Database server Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server Exadata Storage Server

BOND0 Name dm01cel13-priv dm01cel12-priv dm01cel11-priv dm01cel10-priv dm01cel09-priv dm01cel08-priv dm01db08-priv dm01db07-priv dm01db06-priv dm01db05-priv dm01db04-priv dm01db03-priv dm01db02-priv dm01db01-priv dm01cel07-priv dm01cel06-priv dm01cel05-priv dm01cel04-priv dm01cel03-priv dm01cel02-priv dm01cel01-priv

BOND0 IP Address 192.168.10.21 192.168.10.20 192.168.10.19 192.168.10.18 192.168.10.17 192.168.10.16 192.168.10.8 192.168.10.7 192.168.10.6 192.168.10.5 192.168.10.4 192.168.10.3 192.168.10.2 192.168.10.1 192.168.10.15 192.168.10.14 192.168.10.13 192.168.10.12 192.168.10.11 192.168.10.10 192.168.10.9

Cell Alert Delivery Configuration SMTP Notification Email Server: Port: Use SSL: To Address: Enabled mail.example.com 465 Yes all-admins@example.com john.doe@example.com

28

From Address: From Name: Auth User: Auth Password: SNMP Notification SNMP Server: SNMP Port:

dm01@example.com DBM dm01 john.doe@example.com password Enabled snmp.example.com 162

Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc. Access to Oracle Support Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Oracle Exadata Database Machine Configuration Worksheets, 11g Release 2 (11.2) E16099-13 Copyright 2009, 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

29

30