• Domain Name: This field is set to the domain name of the management network where the Database Machine resides.
• Region: This field is set to the geographic region where the database machine resides
• Region: This field is set to the geographic region where the database machine resides.
• Time Zone: This field is set to the time zone where the database machine resides.
• NameServer: Use these fields to identify up to four DNS servers in the network where the Database Machine resides. While it is possible to implement Database Machine without DNS, Oracle recommends that DNS should be used in conjunction with Database Machine.
• NTP Time Server: Use these fields to identify up to four NTP time servers in the network NTP Time Server: Use these fields to identify up to four NTP time servers in the network where the Database Machine resides. NTP services are a mandatory requirement for Database Machine. NTP provides coordinated timing which synchronizes services across Database Machine. Without NTP, a lack of coordination can lead to database nodes being evicted from the cluster or Exadata cells being excluded from the storage pool. NTP
services also ensure that the timestamps written to the various log files are coordinated across Database Machine. Note that the Cluster Time Synchronization Service (CTSS) introduced in Oracle Clusterware11g Release 2 cannot be used to provide time services to introduced in Oracle Clusterware11g Release 2 cannot be used to provide time services to Exadata cells, hence it is not used for Database Machine.
• First Management/ILOM IP address [eth0]: Set this field to the first IP address in the range of IP addresses allocated for the management network. When this field is set, the
Configuration Worksheet sequentially allocates IP addresses for each network interface as shown in the Specific Network Information section of the example worksheet. You can change the default addressing policy by changing values in the Specific Network
Information section of the worksheet or you can change individual addresses by modifying Information section of the worksheet or you can change individual addresses by modifying the addresses generated after you click the Generate button (discussed later in the
lesson). Beware that if you modify the default addressing policy you must ensure that the resulting addresses are valid and there are no duplicates.
• First Client Access IP address [eth1]: Set this field to the first IP address in the range of IP addresses allocated for the client access network. When this field is set, the Configuration Worksheet sequentially allocates IP addresses for each network interface as shown in the Specific Network Information section of the example worksheet. You can change the default addressing policy by changing values in the Specific Network Information section of the worksheet or you can change individual addresses by modifying the addresses generated after you click the Generate button (discussed later). Beware that if you modify the default addressing policy you must ensure that the resulting addresses are valid and there are no duplicates.
In this example all the other fields contain default values. Other fields that might typically be set In this example all the other fields contain default values. Other fields that might typically be set to non-default values include:
• Cell Disk Size: Set this field to 600G for systems with high performance disks or 2TB for systems with high capacity disks.
• Backup requirements: Select from one of the available options (Tape backup, Disk backup only, Both Disk and Tape backup). This setting influences the default size of the ASM disk groups that are configured later in the worksheet.
• Subnet Mask: If the default values are not suitable, the various subnet mask fields should be adjusted to reflect the network where the Database Machine resides.
• Gateway: If the default values are not suitable, the various gateway fields should be adjusted to reflect the network where the Database Machine resides.
Configuration Worksheet Example
Configuration Worksheet Example (Continued)
Following on from the previous slide, this slide shows an example of the second portion of a completed Configuration Worksheet In this part of the Configuration Worksheet the following
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.
completed Configuration Worksheet. In this part of the Configuration Worksheet the following fields are set to non-default values:
• Email To Notification Address, Email From Notification Address, Email From Name, Email Server, Notify via Email: This group of fields are set to facilitate email notification of Exadata cell alerts. Depending on the email server setup you may also need to set other fields in the SMTP and SNMP Details section of the worksheet. Exadata cell alerts can also be delivered via SNMP however this option is not configured in the example.
• Number of Diskgroups: Set this field to a non-zero value to configure ASM disk groups.
By default, a setting of 2 results in the creation of disk groups named DATA and RECO as shown in the slide. This section of the Configuration Worksheet is described in greater detail on the next slide.
• Number of Databases: Set this field to a non-zero value to create databases on the Database Machine. The example in the slide shows the default settings for one database.
database
Exadata and Database Machine Administration Workshop 9 - 9
Configuration Worksheet Example (Continued)
Note the limited set of database configuration attributes that are available in the Configuration Worksheet. Using the Configuration Worksheet you cannot set many common database attributes, such as database character set for example. The default common database attributes, such as database character set for example. The default database created during installation uses Unicode database character set AL32UTF8.
Oracle recommends Unicode for all new deployments. To use a different database
character set after installation, or to create databases with other non-default attributes, run Database Configuration Assistant (DBCA) to delete the default database, and to create a new database using the desired settings.
Note also that if you do not specify any databases in the Configuration Worksheet, the configuration programs will not install the Oracle Database software on the Database configuration programs will not install the Oracle Database software on the Database Machine. Therefore it is highly recommended that you specify at least one database in the Configuration Worksheet, which can be deleted later if it is not required.
Configuring ASM Disk Groups
Configuring ASM Disk Groups with Configuration Worksheet
The slide illustrates how ASM disk groups are configured using the Configuration Worksheet.
B d f lt ASM di k fi d i th C fi ti W k h t t i d
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.
By default, ASM disk groups configured using the Configuration Worksheet are striped across every disk in every Exadata cell in the Database Machine. The worksheet allows you to specify a range of cells to limit the striping to all the disks those cells. However, you cannot specify a subset of disks within Exadata cells using the Configuration Worksheet. The policy of striping disk groups across all the available disks is recommended by default. Deviating from this policy is recommended only where data isolation is required; such as in
circumstances where security policies govern that data in different databases must be stored
h i ll t di k
on physically separate disks.
Regardless of how many disk groups are specified in the Configuration Worksheet, a disk group named SYSTEMDG is always created. The primary purpose of the SYSTEMDG disk group is to store the shared clusterware files; Oracle Cluster Registry (OCR) and voting disks. The SYSTEMDGdisk group occupies a grid disk that consumes approximately 29 Gigabytes on every disk except the first two disks in each cell. On the first two disks (numbered 0 and 1) in each cell, approximately 29 Gigabytes is used to store the System Area, which contains the , pp y g y y , OS image, swap space, Exadata software binaries, metric and alert repository and various other configuration and metadata files.
Exadata and Database Machine Administration Workshop 9 - 11