Skip Headers
Oracle® Database Appliance Getting Started Guide
Release 2.10 for Linux x86-64

E22692-36
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Preparing to Deploy Oracle Database Appliance

This chapter provides a checklist of tasks that you must complete before deploying software on Oracle Database Appliance. The chapter is divided into two sections:

  1. Tasks that you might optionally complete before delivery of Oracle Database Appliance (Section 1: Pre-Delivery Tasks)

  2. Tasks that you require access to Oracle Database Appliance after physically installing the system at your site (Section 2: Installation and Configuration Tasks).

See Also:

Section 1: Pre-Delivery Tasks

This section covers the following tasks that you might complete before taking delivery of Oracle Database Appliance:

Registering Your Support Identifier on My Oracle Support

Add your hardware Support Identifier (SI) to your My Oracle Support account profile. Your hardware SI is supplied when you purchase Oracle Database Appliance. If you have acquired new software licenses, then you must also register your new software SIs. The SI registration process can take up to 24 hours to complete.

Note:

You cannot obtain support or software from Oracle without registered SIs.

Planning Oracle Database Appliance Configuration Options

You can deploy Oracle Database Appliance either as a bare metal or a virtualized system. For bare metal installations, decide how many CPU cores to enable and what database configuration options you need, if any. For Oracle Database Appliance Virtualized Platform installations, there are a number of additional options to consider. See the following sections to plan your system appropriately:

  • Selecting Oracle Database Appliance Virtualized Platform Options

    This section describes the use of options such as shared disks and virtual local area networks. The section is relevant for Oracle Database Appliance Virtualized Platform.

  • Selecting Database Configuration Options

    This section describes the use of single instance, Oracle Real Application Clusters (RAC), and Oracle RAC One Node databases and sizing templates to configure your initial database. The section is relevant if you plan to configure an initial database during deployment on bare metal or virtualized systems.

  • Sizing ODA_BASE on Oracle Database Appliance Virtualized Platform

    This section describes the selection of an appropriate domain size for an initial database on Oracle Database Appliance Virtualized Platform. The section is not relevant for bare metal installations.

Selecting Oracle Database Appliance Virtualized Platform Options

Before you implement virtual machines, you must decide how and where they will run. Based on your requirements, you might provide high-availability options, reduce interference between competing virtual machines for CPU and network access, and provide more storage space and enable automatic startup for virtual machines. Some of these options require additional network configuration outside of the Oracle Database Appliance servers.

By default, you have one local repository on each node and the maximum size is dependent on the hardware:

  • 350 GB on Oracle Database Appliance X4-2 Virtualized Platform

  • 350 GB on Oracle Database Appliance X3-2 Virtualized Platform

  • 250 GB on Oracle Database Appliance Virtualized Platform.

When you create virtual machines in the default repositories, the virtual machines can only run on the node where they are located and therefore have no failover capability.

To obtain the most flexible shared machine environment, use a shared disk system with Virtual Local Area Networks (VLANs). Shared disks provide high-availability options and reduce the use of internal storage. VLANs help you partition traffic on your networks.

When you use shared disks, the repositories that you create reside on your shared storage, consuming space in one or both Oracle Automatic Storage Management (Oracle ASM) disk groups, DATA and RECO. On shared disks, virtual machines can start automatically whenever the repository becomes available, can run on a preferred node, and can start or failover to the other node if the preferred node is unavailable.

Oracle Database Appliance Virtualized Platform supports multiple VLANs on the same network interface card (NIC) port. Each VLAN is essentially an independent logical network operating with other VLANs over the same physical connection. Use VLANs to minimize the number of required physical connections and NICs while concurrently separating traffic. Each VLAN is assigned a distinct VLAN identification (ID). An attached VLAN switch uses VLAN IDs to segregate traffic among the different VLANs operating on the same link. When a VLAN is configured, the VLAN functions exactly like a separate physical connection.

Note:

Virtual LANs need to be configured in the physical switches before you use them.

Selecting Database Configuration Options

This section contains the following tasks:

Before continuing, you might want to print the checklist tables found in the About Checklist Tables section of this chapter. Use the checklists to record decisions and information that you collect for your planned Oracle Database Appliance configuration.

Selecting Database Deployment Options

Oracle Appliance Manager installs the Oracle Database software on mirrored disks that are internal to Oracle Database Appliance. During the initial deployment with the Oracle Appliance Manager configurator, you might create a database or defer database creation to a later time. If you plan to create an initial database during deployment, prepare to select one of the following options:

  • Enterprise Edition: Oracle Database 11g Release 2 Enterprise Edition (no automated failover), with the following characteristics:

    • Single-instance Oracle Database Enterprise Edition home

    • Oracle Database software installation on both nodes through the use of internally mirrored disks

  • Oracle Real Application Clusters (Oracle RAC) One Node: Oracle RAC One Node 11g Release 2, with the following characteristics:

    • Oracle RAC One Node has a designated Oracle Database Appliance home node

    • Oracle RAC One Node software installed on both servers

    • Automated failover

    • Enterprise Edition license required

    • Oracle RAC One Node license on each server required

      Exception: If you designate one server as a backup server, then you can use that server without a license in accordance with the 10-day rule

      See Also:

      Oracle Software Investment Guide for information about the 10-day rule, which is available from the following URL:

      http://www.oracle.com/us/corporate/pricing/sig-070616.pdf

  • Oracle RAC: Oracle Real Application Clusters 11g Release 2, with the following characteristics:

    • Oracle RAC home

    • Oracle RAC software installed on both servers

    • Enterprise Edition license required

    • Oracle RAC license on each server required (not eligible for the 10-day rule)

Selecting Database Templates

Oracle Database Appliance software includes preconfigured templates that incorporate Oracle best practices with optimization for different classes of databases. Each database class has different workload profiles and performance characteristics based on the following:

  • memory requirements, calculated from the System Global Area (SGA) plus Program Global Area (PGA) sizes

  • processing requirements, calculated from the number of processes

  • logging requirements, based on log buffer size and online redo log size

Not all templates are supported on every type of Oracle Database Appliance hardware are different.

When selecting a template, use the following table to match your database values with the smallest template that can support those values. If you are planning to run multiple databases, then use the sum of their values to find the correct template. Also check that your required template is available on your system, by confirming that there is an "X" in the V1 column for original Oracle Database Appliance hardware, in the X3-2 column for Oracle Database Appliance X3-2 hardware, and in the X4-2 column for Oracle Database Appliance X4-2 hardware.

Table 2-1 Database Template Names and Characteristics

Template Name SGA Size (G-Bytes) PGA Size (G-Bytes) Process Count Log Buffer Size (M-Bytes) Online Redo Log Size (G-Bytes) V1 X3-2 X4-2

Very Very Small

2

1

200

16

1

X

X

X

Very Small

4

2

200

16

1

X

X

X

Small

8

4

400

16

1

X

X

X

Medium

16

8

800

32

2

X

X

X

Large

24

12

1200

64

4

X

X

X

Extra Large

48

24

2400

64

4

X

X

X

Extra Extra Large

64

32

3200

64

4

 

X

X

Extra Extra Extra Large

96

48

4800

64

4

   

X


Note:

Oracle strongly recommends that you use these templates because they implement best practices and are configured specifically for Oracle Database Appliance.

Use either Oracle Appliance Manager or Oracle Database Configuration Assistant (DBCA) to create databases on Oracle Database Appliance. The templates are available in both utilities.

See Also:

Appendix C, "Database Sizing for Oracle Database Appliance" for information to help you choose the appropriate template for your system

Sizing ODA_BASE on Oracle Database Appliance Virtualized Platform

If you are planning to deploy your databases on Oracle Database Appliance Virtualized Platform, then read this section to help you size your ODA_BASE. The function of ODA_BASE is to provide memory and computing power for the Oracle Grid Infrastructure and Oracle Databases that you create, either during deployment or later, on your system.

Oracle Database Appliance Virtualized Platform architecture prevents the operating system and user domains from compromising database performance because they cannot access the computing resources assigned to ODA_BASE. Oracle strongly recommends that you use the Oracle Database Appliance Virtualized Platform templates to set the size for your ODA_BASE. See the appropriate table and the related text below for the available templates on your version of Oracle Database Appliance.

The following table shows the core count and RAM memory size available for sizing ODA_BASE on Oracle Database Appliance X4-2. The table does not include information about related database templates because even the smallest core count can accommodate two very small databases. To determine which combinations of database classes run in an ODA_BASE with a specific core count, you need the sum of the PGA and SGA sizes of each database. Find these sizes in the list of Database Templates for Oracle Database Appliance X4-2 in the Selecting Database Templates section.

Table 2-2 Core Count and RAM Size for Selecting Database Templates on Oracle Database Appliance X4-2 Virtualized Platform

Core Count (each node) RAM Size (in Gigabytes)

2

32

4

64

6

96

8

128

10

160

12

192

14

224

16

244

24

244


The following table shows the core count and RAM memory size available for sizing ODA_BASE on Oracle Database Appliance X3-2. The table does not include information about related database templates because even the smallest core count can accommodate two very small databases. To determine which combinations of database classes run in an ODA_BASE with a specific core count, you need the sum of the SGA and PGA sizes for each database. Find these sizes in the list of Database Templates for Oracle Database Appliance X3-2 in the Selecting Database Templates section.

Table 2-3 Core Count and RAM Size for Selecting Database Templates on Oracle Database Appliance X3-2 Virtualized Platform

Core Count (each node) RAM Size (in Gigabytes)

2

32

4

64

6

96

8

128

10

160

12

192

14

224

16

244


The following table shows the core count and RAM memory size available for sizing ODA_BASE on Oracle Database Appliance. The table also lists the equivalent Database Template for each core size so that, if you are only deploying one database, you would select the core count that matches your database requirements.

Table 2-4 Matching Database Templates to Core Count and RAM Size on Oracle Database Appliance Virtualized Platform

Core Count (each node) RAM Size (in Gigabytes) Related Database Template

2

16

Very Very Small

2

16

Very Small

4

32

Small

6

48

Medium

8

64

Large

10

80

Extra Large

12

88

Extra Extra Large


If you only plan to deploy one Oracle Database, use a template for your ODA_BASE that has the same name as the template you choose for your Oracle Database. However, you do not have to select database templates with the same size category as the ODA_BASE template. For example, use a small ODA_BASE template to host two very small databases and a large ODA_BASE template to host either one large with one small database or one medium database with one small and two very small databases. When choosing your template sizes, note that the total requirements for your selected database templates must not exceed the capacity of your ODA_BASE template.

Gathering System Requirement Information

The first part of this section, About Checklist Tables, explains the information you need to collect before deploying Oracle Database Appliance. Included in About Checklist Tables are four tables that you can print and use to enter values as you find and finalize them. The second part of this section, Collecting Additional Configuration Information, describes additional information that you should collect from your storage and network managers.

About Checklist Tables

If you wish, print the checklist tables that match your system and use them to help you record progress and save information that you gather for your system requirements.

Checklist for System Details

The following table is a checklist for system information that you will need. Use the first column (the Value column) to record the selected values as you work through the checklist.

Table 2-5 Checklist for System Details Configuration

System Information Description Value

System Name

Provide the name for the cluster running on Oracle Database Appliance. This name is also used as the default root word for Oracle Database Appliance network addresses. The name should comply with the host name specifications described in the RFC 952 standard. For example, the name should be alphanumeric and not begin with a numeral.

_______________________

Region

Select the region where you plan to operate the Oracle Database Appliance system.

_______________________

Timezone

Select the time zone where you plan to operate the Oracle Database Appliance system.

_______________________

Database Deployment

Select the type of deployment option that you intend to operate from the following choices:

  • Oracle Database Enterprise Edition (EE)

  • Oracle RAC One Node

  • Oracle Real Application Clusters (Oracle RAC)

_______________________


Note:

Do not use a host name with more than 13 characters. Although the total length of the host name can be 15 characters, Oracle Appliance Manager appends two additional characters, -c,to your host name. Additionally, Oracle recommends that you use all lower case characters for the host name.

Checklist for Custom Node Network Address Configuration

By default, names for network interfaces are derived from the Oracle Database Appliance system name, which you provide during installation. Also by default, the addresses for the public IP addresses are assigned in sequence from the address that you provide for the public IP address for Node 0.

The following table lists the minimum number of IP addresses required for Oracle Database Appliance and the default network addresses when applicable.

Table 2-6 Minimum IP Address Requirements for Oracle Database Appliance

Type Bare Metal Minimum IP Address Counts and Default Values Virtualized Platform Minimum IP Address Counts and Default Values

Host IP

2

2

Private IP

4

192.168.16.24

192.168.16.25

192.168.17.24

192.168.17.25

2

192.168.16.27

192.168.16.28

Dom0 IP

Not Applicable

2

192.168.16.24

192.168.16.25

RAC VIP

2

2

SCAN

2

2

Oracle ILOM IP

2

2

User Virtual Machine IP

Not Applicable

At least 1 for each Virtual Machine


Ensure that the names and addresses that you provide for configuration are configured in your Domain Name System (DNS) servers. With Patch Set 1 and later, the addresses that you provide are configured in the /etc/hosts file to provide IP name and address resolution, even if a DNS server is not available.

If you are deploying Oracle Database Appliance X4-2, then you have the option to connect to either a copper or a fiber public network. Ensure that your network planning is based on the correct type of public network.

Oracle recommends using a DNS server so that you can use the features of Single Client Access Name (SCAN). If you deploy without a DNS server but later create a DNS server and add SCAN, then you must specify additional VIP addresses as described in Oracle Database Appliance Release Notes for Linux x86-64.

See Also:

The section "Checklist for Network Administration Configuration" for more information about SCAN.

To perform a Custom configuration and select IP addresses yourself, use the following table to help you configure network addresses for the required Oracle Database Appliance system addresses. Obtain the fully qualified domain name (full name and IP address) for the network addresses in the following table. Use the Check column to mark items that you have completed and the Your Custom Value column to record any non-default values that you plan to use as you work through the checklist.

Table 2-7 Checklist for Network Address Configuration

Required Information Default Value Your Custom Value (if applicable) Check When Done

Domain Name

None

_____________________________________

___________

DNS Servers (primary, secondary, tertiary)

None.

_____________________________________

___________

Subnet

All network addresses assigned to Oracle Database Appliance must be on the same subnet

By default, if you enter an IP address for the Node 0 public IP address, the other IP addresses for Oracle Database Appliance are entered in the sequence node0 public, node 1 public, node 0 VIP, node 1 VIP, and SCAN addresses.

_____________________________________

___________

Oracle ILOM SP host name for Node 0 (optional)

systemname1-ilom

_____________________________________

___________

Oracle ILOM SP host name for Node 1 (optional)

systemname2-ilom

_____________________________________

___________

Single Client Access Name (SCAN)

A SCAN is a virtual IP name used for the cluster. Configure the SCAN on your DNS server to resolve to two IP addresses in random order.

systemname-scan

____________________________________

___________

Node 0 Public IP address

systemname1

____________________________________

___________

Node 0 Virtual IP public IP address

systemname1-vip

_____________________________________

___________

Node 1 Public IP address

systemname2

_____________________________________

___________

Node 1 Virtual IP public IP address

systemname2-vip

_____________________________________

___________

Netmask

255.255.252.0

_____________________________________

___________

Gateway

None

_____________________________________

___________


Note:

A correctly configured Oracle Database Appliance requires at least six public addresses on the same subnet for the nodes: A public and a virtual IP name and address for each node, and two addresses that resolve to the SCAN for the cluster.

All names must conform to the RFC 952 standard, which permits alphanumeric characters and hyphens ("-"), but does not allow underscores ("_").

Provide an IP address for the public interface for each node. This interface is bond0, or Eth1 on Oracle Database Appliance Virtualized Platform, (a bond of Eth2 and Eth3), which is used for the host IP address for the node.

If you select a Custom installation, then provide names and addresses for the following optional interfaces that you need:

  • bond1 (Ethernet bond)

  • bond2 (Ethernet bond)

  • xbond0 (for high capacity transfers, such as backups)

Use bond1 and bond2 for management, backup, disaster recovery, or other options where you require a network interface. Be prepared to provide a netmask and a gateway for each interface as both are required when configuring network connections for Oracle Database Appliance.

Checklist for System Administration Configuration

Ensure that you have the information listed in the following table. Use the Check column to mark items that you have completed and the Value column to record any non-default values that you plan to use as you work through the checklist.

Table 2-8 Checklist for System Configuration Information

Required Information Value Check When Done

Oracle Database Appliance Server name

_____________________________________________________________

_________

Oracle Database Appliance Server domain name

_____________________________________________________________

__________

Public Gateway address

_____________________________________________________________

__________

Domain Name System (DNS) server addresses

_____________________________________________________________

__________

Network Time Protocol (NTP) Server addresses

_____________________________________________________________

__________

Subnet Mask

_____________________________________________________________

__________

Oracle Integrated Lights Out Manager (Oracle ILOM) local serial console

_____________________________________________________________

__________

Oracle ILOM Assigned server SP address for Node 0

_____________________________________________________________

__________

Oracle ILOM Assigned server SP address for Node 1

_____________________________________________________________

__________

Oracle ILOM host name configured for Node 0

_____________________________________________________________

__________

Oracle ILOM host name configured for Node 1

_____________________________________________________________

__________

Network cables are connected to all IP address ports as listed in the adjacent value column

Two Ethernet ports, configured as bond0 (or Eth1 for Oracle Database Appliance Virtualized Platform), for public network access, connected to a public network switch

_____________________________________________________________

Two Ethernet ports, configured as bond1 (or Eth2 for Oracle Database Appliance Virtualized Platform), for public network access, connected to a public network switch.

_____________________________________________________________

Two Ethernet ports, configured as bond2 (or Eth3 for Oracle Database Appliance Virtualized Platform), for public network access, connected to a public network switch.

_____________________________________________________________

Two Ethernet ports, configured as xbond0 (or Eth4 for Oracle Database Appliance Virtualized Platform) for public network access for 10-GbE infrastructure (optional), connected to a public network switch.

_____________________________________________________________

One Ethernet port (NET MGT) for connection to Oracle ILOM software (optional), connected to a public network switch

_____________________________________________________________

One serial management port (SER MGT) for local Oracle ILOM interface, connected to a terminal or terminal emulator

_____________________________________________________________

__________


Note:

If you define a fiber public network connection, then bond0 is configured on PCIe boards.

Questions to Ask Your Oracle Database Appliance Administrator

  1. Is a network time protocol (NTP) service configured for each server, so that the local system time for each server is synchronized?

    If you have NTP servers, and you want to synchronize time between Oracle Database Appliance nodes using NTP, then be prepared to provide the addresses for the servers. Otherwise, the Oracle Grid Infrastructure software provides time synchronization between nodes using Cluster Time Synchronization Service (CTSS).

  2. Are the public IP address cables plugged in to redundant switches to avoid a single point of failure for the cluster?

  3. What root password should you use for Oracle Database Appliance? Root passwords should comply with your system security requirements.

Collecting Additional Configuration Information

You should be aware of the information included in this section. You might want to share this information with other system administrators to ensure the suitability of the environment in which you are planning to deploy Oracle Database Appliance.

Checklist for Storage Configuration

Storage administration is integrated into Oracle Database Appliance. No additional storage configuration is required.

Oracle Database Appliance includes integrated storage for operational files (operating system, Oracle Grid Infrastructure home, Oracle Database homes, tools), user data (database files), and log files (database redo logs). Operational files are stored on mirrored internal system disks in each server. Data and database redo log files are stored on disks as follows:

  • On Oracle Database Appliance X4-2 and Oracle Database Appliance X3-2, data files are stored in the storage shelf and the optional storage expansion shelf

  • On Oracle Database Appliance X4-2 and Oracle Database Appliance X3-2, database redo log files are stored on solid-state drives (SSDs) in the storage shelf and the optional storage expansion shelf

  • On Oracle Database Appliance, data and database redo log files are stored in the shared storage bay

Note:

Disk hardware capacity is measured using 1 KB = 1,000 bytes whereas software storage requirements are based on 1 KB = 1,024 bytes. This means that a disk with a rated capacity of 900 GB has only about 860 GB of space for software storage.

Checklist for Network Administration Configuration

Before configuring DNS names and addresses, ensure that all network names conform with the RFC 952 standard, which permits alphanumeric characters and hyphens ("-"), but does not allow underscores ("_").

Review the following table to ensure that your network administrator reserves at least the minimum number of IP addresses required for Oracle Database Appliance. The table also includes default IP addresses, where applicable.

Table 2-9 IP Address Requirements

Type Bare Metal Minimum IP Address Count Virtualized Platform Minimum IP Address Count

Host IP

2

2 (for ODA_BASE)

Private IP

4

192.168.16.24

192.168.16.25

192.168.17.24

192.168.17.25

4

192.168.16.24 (for Dom0)

192.168.16.25 (for ODA_BASE)

192.168.16.27

192.168.16.28

Dom0 IP

0

2

RAC VIP

2

2

SCAN IP

2

2

Oracle ILOM IP

2

2

User Virtual Machines

0

At least 1 for each VM


Confirm with your network administrator that the addresses that you configured for Oracle Database Appliance meet these three criteria:

  1. They are static IP addresses.

  2. They are on the same subnet as all other IP addresses, virtual IP (VIP) addresses (used for Real Application Clusters communication), and SCAN addresses.

  3. They include the following:

  • One public IP address configured on the DNS server for each node and resolvable to that node before installation.

  • A VIP address for each node configured on the DNS server that is not currently in use.

  • SCANs for Oracle Database Appliance with the following characteristics:

    • Configured on the DNS server before installation so that the two IP addresses are associated with the name provided as the SCAN, and both addresses are returned in random order to the requester by the DNS server

    • Configured on the DNS server before installation to resolve to addresses that are not currently in use

    • Have names that do not begin with a numeral

Caution:

Do not change the IP addresses and subnet for the private network.

Note:

Configuring SCANs in a Network Information Service (NIS) is not supported.

See Also:

Single Client Access Name (SCAN), a technical paper on Oracle Technology Network, for a comprehensive introduction to SCAN:

http://www.oracle.com/technetwork/database/clustering/overview/scan-129069.pdf

Using Oracle Appliance Manager Configurator

The standalone Oracle Appliance Manager configurator is a Java-based tool that enables you to generate your deployment plan and validate your network settings before the actual deployment. Download and run the configurator on a local client system which can be a Windows, Linux, or UNIX system.

At the end of a configurator session, save your deployment plan in a configuration file. When you are ready to deploy, copy this configuration file to Oracle Database Appliance and run the online Oracle Appliance Manager configurator to import and deploy your saved plan. You can also print the file's content and use the printout as a checklist for setting up your external network configuration.

Prior to saving your configuration file, Oracle recommends that you test your network settings. However, this will only work correctly if your client system is connected to same network that you will use for Oracle Database Appliance.

To run the configurator:

  1. Download the standalone Oracle Appliance Manager configurator that matches your version of Oracle Database Appliance. All versions of the configurator are available from the Overview page at the following URL:

    http://www.oracle.com/technetwork/server-storage/engineered-systems/database-appliance/index.html
    

    Note:

    If your Oracle Database Appliance is already available and you are familiar with the configuration options, then you can run the online configurator from Node 1 of Oracle Database Appliance and complete the deployment in a single session. However, you must first configure an initial network and install either the End-User Bundle or configure ODA_BASE. These steps are covered in Chapter 3.
  2. Start the configurator using the command config.bat on a Windows client, or the command ./config.sh on a Linux or UNIX client. The Oracle Appliance Manager Welcome page appears.

    Description of oam_welcome.png follows
    Description of the illustration oam_welcome.png

    Click Next.

  3. On the Configuration Type page, select the options for configuration type, environment, and hardware. You can optionally load an existing configuration file by clicking Browse.

    Description of oam_configtype.png follows
    Description of the illustration oam_configtype.png

    Oracle recommends the typical configuration except for SAP databases and applications, in which case select SAP Application. Choose the Custom option to configure additional or alternate network interfaces or to override the default values for one or more of the following:

    • Database block size, language, territory, backup file location, or disk redundancy level for the DATA and RECO disk groups

    • Oracle Integrated Lights Out Manager (Oracle ILOM) server

    • Oracle Auto Service Request (Oracle ASR) configuration

    • Oracle Cloud File System file system and size

    • Network Time Protocol service server

    To see the default values for your version of Oracle Database Appliance before choosing the Typical or Custom option, run the configurator using the Custom option.

    If you are installing Oracle Database Appliance Virtualized Platform, then select Virtualized Platform, or leave the default value, Bare Metal, as the environment option. If you are installing on X3-2 or X4-2 hardware, then select ODA-X3-2 or ODA-X4-2 respectively, or leave the default value, ODA V1, as the hardware option.

    The Browse option is not useful during the initial run because there are no configuration files to load.

    In this example, Typical, Virtualized Platform, and ODA-X4-2 are the selected options.

    Note:

    The SAP Application option is only valid with the Bare Metal option.

    Click Next.

  4. On the System Information page, provide the system name, and select the correct value from the lists for your region and time zone.

    In the Database Deployment field, select the type of database deployment that you want:

    • Oracle Database Enterprise Edition (no Oracle RAC)

    • Oracle RAC One Node

    • Oracle RAC

    In the New Root Password and New Root Password (confirm) fields, enter a new password for the root user. This password is encrypted in the configuration file and will be temporarily decrypted to reset the password during deployment.

    Description of oam_sysinfo.png follows
    Description of the illustration oam_sysinfo.png

    Click Next.

  5. On the Network Information page, provide your domain name, DNS server addresses, public and VIP addresses for your two nodes, SCAN name and addresses, and Netmask and Gateway addresses.

    Description of oam_gennet.png follows
    Description of the illustration oam_gennet.png

    As you enter data on this page, some fields will automatically fill with values derived from earlier entries. For example, if the address that you provide for the Node 0 public IP address is 192.0.2.18, then the node addresses are assigned as follows:

    • Node 0 public IP address: 192.0.2.18

    • Node 1 public IP address: 192.0.2.19

    • Node 0 virtual IP (VIP) address: 192.0.2.20

    • Node 1 virtual IP (VIP) address: 192.0.2.21

    • SCAN addresses (two addresses resolving to the SCAN VIP name): 192.0.2.22, 192.0.2.23

    See Also:

    "Checklist for Custom Node Network Address Configuration" earlier in this chapter for information about requirements for nonstandard public IP addresses

    Click Next.

  6. On the Database Information page, select whether you want to create an initial database. If you check the box to create a database, then you can also check the box to create Oracle Enterprise Manager Control and provide your database details. These details include the database name, which you must enter, and the database configuration template and the database language, both of which you select from the available values. (See "Selecting Database Templates" for guidelines to help you choose the appropriate template.) However, if you do not want to create an initial database, then do not check the Create Initial Database check box.

    Description of oam_dbinfo.png follows
    Description of the illustration oam_dbinfo.png

    Click Next.

  7. On the Network Validation page, either validate the network settings and save the validation output in a file or bypass the validation step by selecting the Skip Network Validations check box.

    Description of oam_netval.png follows
    Description of the illustration oam_netval.png

    Oracle recommends that you validate your network before deploying your configuration. However, unless you are running Oracle Appliance Manager configurator on server attached to the network subnet configured for your appliance, the validation will fail. In such a case, select Skip Network Validations check box, and then click Next to proceed to the next page. If you run the validation, then review the results. After you review the results, if you are ready to proceed, then click Next. If the validation fails, then save the validation output to review these results with your network administrator. To save the configuration information that you have entered and correct the network addresses later, select Skip Network Validations and click Next to continue to the next page.

  8. On the Summary page, review the configuration options that you have selected. Click Save to save the configuration file, or click Back to modify your selections.

    You can print the contents of the configuration file and use the printout to review your configuration entries for deployment planning purposes. You might also use the configuration file during the actual deployment, as described in "Task 5: Deploy Your Configuration (All Platform Deployments)".

    Description of oam_summary.png follows
    Description of the illustration oam_summary.png

    If you are running the configurator on Oracle Database Appliance and have completed the preliminary steps to configure your initial network and install the End-User Bundle or deploy ODA_BASE, then you can click Install to deploy the configuration that you just created. If you are not ready to complete the deployment, then first click Save and then click Finish. Remember the name and location of the file you save as you might wish to copy the file to your Oracle Database Appliance, as described in Chapter 3, "Deploying Oracle Software on Oracle Database Appliance." If you need to make corrections before deployment, then rerun the standalone Oracle Appliance Manager configurator, load your configuration file, make the changes, and save the file again.

Section 2: Installation and Configuration Tasks

This section covers the following tasks that you must complete before deploying Oracle Database Appliance software (which is described in Chapter 3, "Deploying Oracle Software on Oracle Database Appliance"):

Caution:

Electronic equipment is susceptible to damage by static electricity. Use a grounded antistatic wrist strap, foot strap, or equivalent safety equipment to prevent electrostatic damage (ESD) when you install or service the system.

Attaching Cables and Peripherals to Oracle Database Appliance X4-2

This section describes the cabling of Oracle Database Appliance X4-2 and has five parts outlined below.

Complete the first three parts to add the interconnect between Oracle Database Appliance X4-2 nodes, to attach the nodes to the database storage, and to connect peripheral devices. Complete the cabling in fourth and fifth parts only when your system includes a storage expansion shelf.

Attaching Interconnect Cables to Oracle Database Appliance X4-2

Connect the two nodes of your Oracle Database Appliance X4-2 with one of the pairs of the interconnect cables included in your shipment. One pair of interconnects are copper Cat-6 cables with RJ45 connectors and the other pair are twinax cables with SFP+ connectors. One cable in each pair has a green sheath or green labels at each end, the other cable in each pair has a yellow sheath or yellow labels at each end. Determine which pair you need and install them as follows:

  • If the connections from Oracle Database Appliance X4-2 to your public network require copper cables, then use the twinax pair for the node interconnects. To install the twinax interconnect cables, see Figure 2-1 and the related instructions. In this case, discard the supplied copper interconnect cables (or use them for something else).

  • If the connections from Oracle Database Appliance X4-2 to your public network require fiber cables, then use the copper Cat-6 pair for the node interconnects. To install the copper interconnect cables, see Figure 2-2 and the related instructions. In this case, discard the supplied twinax interconnect cables (or use them for something else).

Figure 2-1 Oracle Database Appliance X4-2 with Interconnect Cabling When Using Copper Cable Connections to Public Networks

Description of Figure 2-1 follows
Description of "Figure 2-1 Oracle Database Appliance X4-2 with Interconnect Cabling When Using Copper Cable Connections to Public Networks"

The preceding figure shows where to connect the provided twinax cables for the Oracle Database Appliance X4-2 interconnects when you plan to use copper cables for you public network. If you are able to distinguish colors, then match the cables with the green and yellow sheaths or labels with the colored lines shown in the illustration. You can also match the cable color labels to the background colors of the socket identification labels. If you are unable to use color coding, then use the callout numbers from the figure to follow the instructions. The interconnect cables are interchangeable, so you can safely ignore the color coding.

The interconnect cables plug into the PCIe3 connection strip with the label number ”1,” which is the PCIe3 strip at the left side of the back panel. Plug one end of the green cable, callout 1, into the NET 0 socket in the connection strip on Node 0, and plug the other end into the NET 0 socket on Node 1. Similarly, plug one end of the yellow cable, callout 2, into the NET 1 socket in the connection strip on Node 0, and plug the other end into the NET 1 socket on Node 1.

Figure 2-2 Oracle Database Appliance X4-2 with Interconnect Cabling When Using Fiber Cables for Public Networks

Description of Figure 2-2 follows
Description of "Figure 2-2 Oracle Database Appliance X4-2 with Interconnect Cabling When Using Fiber Cables for Public Networks"

The preceding figure shows where to connect the provided Cat-6 cables for the X4-2 interconnects when you plan to use fiber cables for you public network. If you are able to distinguish colors, then match the cables with the green and yellow sheaths or labels with the colored lines shown in the illustration. If you are unable to use color coding, then use the callout numbers from the figure to follow the instructions. The interconnect cables are interchangeable, so you can safely ignore the color coding.

The interconnect cables plug into the four-socket connection strip labeled 100 - 10 GbE, shown in the insert in the preceding figure. Plug one end of the green cable, callout 1, into the Net 1 socket of the connection strip on Node 0, and plug the other end into the Net 1 socket on Node 1. Similarly, plug one end of the yellow cable, callout 2, into the Net 0 socket of the connection strip on Node 0, and plug the other end into the Net 0 socket of the connection strip on Node 1.

Attaching Cables to Oracle Database Appliance X4-2 Storage Shelf

Use the following illustration to guide you as you insert the supplied cables into Oracle Database Appliance X4-2 with a single storage shelf. If you are able to distinguish colors, then match the labels at the ends of each cable with the colored line shown in the following illustration. Also match the cable colors to the background colors of the socket identification labels. For additional guidance and for help if you are unable to use color coding, use the callout numbers described in Table 2-10 to complete the cabling for Oracle Database Appliance X4-2 with a single storage shelf. Because all cables with the same terminations are interchangeable, you can safely ignore the color coding.

Figure 2-3 Oracle Database Appliance X4-2 Cables for Storage Shelf

Description of Figure 2-3 follows
Description of "Figure 2-3 Oracle Database Appliance X4-2 Cables for Storage Shelf"

The cables shown in the preceding figure and described in the following table are included with each shipped Oracle Database Appliance X4-2. These cables are all black, but have colored labels at each end that match the references to cable colors in the text and the label colors on the back panels.

Note:

The back panel of each node contains three PCIe generation 3 terminal slots, with two sockets in each slot. The PCIe slots are labeled "X PCIe3," where "X" is the PCIe slot number. Table 2-10 identifies these slots as PCIe slot 1, PCIe slot 2, and PCIe slot 3, which matches the numbers on the labels reading from left to right. The storage shelf back panel has two IO modules, one located above the other. Each IO module has three ports, numbered 0, 1, and 2. Table 2-10 identifies these ports as either ”top” or ”bottom” ports, for ports in the upper and in the lower IO module respectively.

Table 2-10 Description of Callouts for Cabling Oracle Database Appliance X4-2 with Single Storage Shelf

Callout Number from Figure 2-3 Description

1

Dark red SAS cable:

  • From: Node 1, PCIe slot 2, SAS1

  • To: Storage shelf, top I/O port 1

2

Dark blue SAS cable:

  • From: Node 0, PCIe slot 2, SAS0

  • To: Storage shelf, top I/O port 0

3

Light blue SAS cable:

  • From: Node 0, PCIe slot 3, SAS1

  • To: Storage shelf, bottom I/O port 0

4

Light red SAS cable:

  • From: Node 1, PCIe slot 3, SAS0

  • To: Storage shelf, bottom I/O port 1


See Also:

Oracle Database Owner's Guide for details about cabling with the supplied Cable Management Arm.

Oracle Database Appliance X4-2 can be shipped with double the amount of database storage in a storage expansion shelf. You might also obtain a storage expansion shelf at a later time, if required, to supplement your original storage shelf. Use the instructions in Adding Storage Expansion Shelf to Oracle Database Appliance X4-2 andAttaching Cables to Oracle Database Appliance X4-2 Storage Expansion Shelf if you need to add a storage expansion shelf to an existing system.

Attaching Peripheral Devices to Oracle Database Appliance X4-2

Oracle Database Appliance X4-2 is not equipped with devices for human interaction, such as a monitor or keyboard. To log in directly (not through a network), attach a monitor to the graphics card port and a keyboard and a mouse to the USB ports on Node 0. See callout 1 for the keyboard and mouse inputs and callout 2 for the monitor input in the following figure.

Figure 2-4 Peripheral Device Connections for Oracle Database Appliance X4-2 (Node 0)

Description of Figure 2-4 follows
Description of "Figure 2-4 Peripheral Device Connections for Oracle Database Appliance X4-2 (Node 0)"

Adding Storage Expansion Shelf to Oracle Database Appliance X4-2

If you originally deploy Oracle Database Appliance X4-2 with only one storage shelf, then you can add storage expansion shelf at any time without having to shut down your databases or applications.

Tip:

Oracle recommends that you add the storage expansion shelf when you have relatively little activity on your databases. As soon as Oracle Database Appliance recognizes the new storage, ASM automatically rebalances the disk groups, which might degrade database performance until the operation completes.

After you obtain a storage expansion shelf, follow these steps to install and deploy the unit.

  1. Physically locate the storage expansion shelf below Oracle Database Appliance X4-2, if possible, or else close enough to connect the provided cables.

    Note:

    The storage expansion shelf normally sits at the bottom of Oracle Database Appliance, beneath the storage shelf. However, because racks should always be provisioned from the bottom up, that space might be unavailable. In these cases, to avoid re-rackmounting the entire system, position the storage expansion shelf above the server nodes or even in a different, but adjacent, rack.
  2. The extension storage shelf is installed in exactly the same manner as the original storage shelf. For detailed instructions about applying the supplied label and mounting the unit into a rack, see Chapter 4 (Installing the System into a Rack) of the Oracle Database Appliance Owner's Guide.

  3. Install the supplied cables as described in the following section, Attaching Cables to Oracle Database Appliance X4-2 Storage Expansion Shelf, or as shown on the Oracle Database Appliance Setup Poster.

    Caution:

    Incorrect connections can cause data loss when adding a storage expansion shelf to Oracle Database Appliance with existing databases.
  4. Attach the supplied power cords as explained later in this chapter, in the section Attaching Electrical Power Cords and Turning On Oracle Database Appliance for the First Time.

    Caution:

    Do Not turn on the power until you have added the cables as described in the following section, Attaching Cables to Oracle Database Appliance X4-2 Storage Expansion Shelf.

Note:

Oracle recommends that you do not remove a storage expansion shelf from Oracle Database Appliance, whether the shelf was installed during the initial setup or added later.

Attaching Cables to Oracle Database Appliance X4-2 Storage Expansion Shelf

Use the following illustration to guide you as you insert the required cables into the storage expansion shelf of Oracle Database Appliance X4-2. The cables for the original storage shelf are included in the illustration for reference. If you are able to distinguish colors, then match the colors of the labels at the ends of each cable with the colored line shown in the following illustration. Also match the cable colors to the background colors of the socket identification labels. If you are unable to use color coding, then use the callout numbers described in Table 2-11 to complete the cabling of the storage expansion shelf. Because all cables with the same terminations are interchangeable, you can safely ignore the color coding.

Figure 2-5 Oracle Database Appliance X4-2 Cables for Storage Expansion Shelf

Description of Figure 2-5 follows
Description of "Figure 2-5 Oracle Database Appliance X4-2 Cables for Storage Expansion Shelf"

The cables shown in the preceding figure and described in the following table are included with each shipped Oracle Database Appliance X4-2 storage expansion shelf. These cables are all black, but have colored labels at each end that match the references to cable colors in the text and the label colors on the back panels.

Note:

The back panel of each node contains three PCIe generation 3 terminal slots, with two sockets in each slot. The PCIe slots are labeled "X PCIe3," where "X" is the PCIe slot number. Table 2-13 identifies these slots as PCIe slot 1, PCIe slot 2, and PCIe slot 3, which matches the numbers on the labels reading from left to right. The storage expansion shelf back panel has two IO modules, one located above the other. Each IO module has three ports, numbered 0, 1, and 2. Table 2-13 identifies these ports as either "top" or "bottom" ports, for ports in the upper and in the lower IO module respectively.

Table 2-11 Description of Callouts for Cabling Oracle Database Appliance X4-2 Storage Expansion Shelf

Callout Number from Figure 2-5 Description

1

Dark red SAS cable:

  • From: Node 0, PCIe slot 2, SAS1

  • To: Storage expansion shelf, top I/O port 1

2

Dark blue SAS cable:

  • From: Node 1, PCIe slot 2, SAS0

  • To: Storage expansion shelf, top I/O port 0

3

Light blue SAS cable:

  • From: Node 1, PCIe slot 3, SAS1

  • To: Storage expansion shelf, bottom I/O port 0

4

Light red SAS cable:

  • From: Node 0, PCIe slot 3, SAS0

  • To: Storage expansion shelf, bottom I/O port 1


See Also:

Oracle Database Owner's Guide for details about cabling with the supplied Cable Management Arm.

Attaching Cables and Peripherals to Oracle Database Appliance X3-2

This section describes the cabling of Oracle Database Appliance X3-2 and has four parts that are outlined below.

Complete instructions in the first two parts to provide the interconnect between Oracle Database Appliance X3-2 nodes, to attach the nodes to the database storage, and to connect peripheral devices. Complete the third and fourth parts only when your system includes a storage expansion shelf.

Attaching Cables to Oracle Database Appliance X3-2 with a Single Storage Shelf

Use the following illustration to guide you as you insert the supplied cables into Oracle Database Appliance X3-2 with a single storage shelf. If you are able to distinguish colors, then match cable colors (for the green and yellow cables), or the labels at the ends of each cable, with the colored line shown in the following illustration. Also match the cable colors to the background colors of the socket identification labels. If you are unable to use color coding, then use the callout numbers described in Table 2-12 to complete the cabling for Oracle Database Appliance X3-2 with a single storage shelf. Because all cables with the same terminations are interchangeable, you can safely ignore the color coding.

Figure 2-6 Oracle Database Appliance X3-2 Interconnects and Cables for Single Storage Shelf

Description of Figure 2-6 follows
Description of "Figure 2-6 Oracle Database Appliance X3-2 Interconnects and Cables for Single Storage Shelf"

The cables shown in the preceding figure and described in the following table are included with each shipped Oracle Database Appliance X3-2. Other than the green and yellow interconnect cables, the cables are all black, but have colored labels at each end that match the references to cable colors in the text and the label colors on the back panels.

Note:

The back panel of each node contains three PCIe generation 3 terminal slots, with two sockets in each slot. The PCIe slots are labeled "X PCIe3," where "X" is the PCIe slot number. Table 2-12 identifies these slots as PCIe slot 1, PCIe slot 2, and PCIe slot 3, which matches the numbers on the labels reading from left to right. The storage shelf back panel has two IO modules, one located above the other. Each IO module has three ports, numbered 0, 1, and 2. Table 2-12 identifies these ports as either ”top” or ”bottom” ports, for ports in the upper and in the lower IO module respectively.

Table 2-12 Description of Callouts for Cabling Oracle Database Appliance X3-2 With SIngle Storage Shelf

Callout Number from Figure 2-6 Description

1

Dark blue SAS cable:

  • From: Node 0, PCIe slot 2, SAS0

  • To: Storage shelf, top I/O port 0

2

Light blue SAS cable:

  • From: Node 0, PCIe slot 3, SAS1

  • To: Storage shelf, bottom I/O port 0

3

Dark red SAS cable:

  • From: Node 1, PCIe slot 2, SAS1

  • To: Storage shelf, top I/O port 1

4

Light red SAS cable:

  • From: Node 1, PCIe slot 3, SAS0

  • To: Storage shelf, bottom I/O port 1

5

Green copper cable:

  • From: Node 0, PCIe slot 1, NET0

  • To: Node 1, PCIe slot 1, NET0

6

Yellow copper cable:

  • From: Node 0, PCIe slot 1, NET1

  • To: Node 1, PCIe slot 1, NET1


See Also:

Oracle Database Owner's Guide for details about cabling with the supplied Cable Management Arm.

Oracle Database Appliance X3-2 can be shipped with double the amount of database storage in a storage expansion shelf. You might also obtain a storage expansion shelf at a later time, if required, to supplement your original storage shelf. Use the instructions in the sections Adding Storage Expansion Shelf to Oracle Database Appliance X3-2 andAttaching Cables to Oracle Database Appliance X3-2 Storage Expansion Shelf if you need to add a storage expansion shelf to an existing system.

Attaching Peripheral Devices to Oracle Database Appliance X3-2

Oracle Database Appliance X3-2 is not equipped with devices for human interaction, such as a monitor or keyboard. To log in directly (not through a network), attach a monitor to the graphics card port and a keyboard and a mouse to the USB ports on Node 0. See callout 1 for the keyboard and mouse inputs and callout 2 for the monitor input in the following figure.

Figure 2-7 Peripheral Device Connections for Oracle Database Appliance X3-2 (Node 0)

Description of Figure 2-7 follows
Description of "Figure 2-7 Peripheral Device Connections for Oracle Database Appliance X3-2 (Node 0)"

Adding Storage Expansion Shelf to Oracle Database Appliance X3-2

If you originally deploy Oracle Database Appliance X3-2 with only one storage shelf, then you might add storage expansion shelf at any time without having to shut down your databases or applications.

Tip:

Oracle recommends that you add the storage expansion shelf when you have relatively little activity on your databases. As soon as Oracle Database Appliance recognizes the new storage, ASM automatically rebalances the disk groups, which might degrade database performance until the operation completes.

After you obtain a storage expansion shelf, follow these steps to install and deploy the unit.

  1. Physically locate the storage expansion shelf below your Oracle Database Appliance X3-2, if possible, or else close enough to connect the provided cables.

    Note:

    The storage expansion shelf normally sits at the bottom of Oracle Database Appliance, beneath the storage shelf. However, because racks should always be provisioned from the bottom up, that space might be unavailable. In these cases, to avoid re-rackmounting the entire system, position the storage expansion shelf above the server nodes or even in a different, but adjacent, rack.
  2. The extension storage shelf is installed in exactly the same manner as the original storage shelf. For detailed instructions about applying the supplied label and mounting the unit into a rack, see Chapter 10 (Installing Oracle Database Appliance X3-2 into a Rack) of the Oracle Database Appliance Owner's Guide.

  3. Install the supplied cables as described in the following section, Attaching Cables to Oracle Database Appliance X3-2 Storage Expansion Shelf, or as shown on the Oracle Database Appliance Setup Poster.

    Caution:

    Incorrect connections can cause data loss when adding a storage expansion shelf to Oracle Database Appliance with existing databases.
  4. Attach the supplied power cords as explained later in this chapter, in the section Attaching Electrical Power Cords and Turning On Oracle Database Appliance for the First Time.

    Caution:

    Do Not turn on the power until you have added the cables as described in the following section, Attaching Cables to Oracle Database Appliance X3-2 Storage Expansion Shelf.

Note:

Oracle recommends that you do not remove a storage expansion shelf from Oracle Database Appliance, whether the shelf was installed during the initial setup or added later.

Attaching Cables to Oracle Database Appliance X3-2 Storage Expansion Shelf

Use the following illustration to guide you as you insert the required cables into the storage expansion shelf of Oracle Database Appliance X3-2. The cables for the two nodes and the original storage shelf are included in the illustration for reference. If you are able to distinguish colors, then match the colors of the labels at the ends of each cable with the colored line shown in the following illustration. Also match the cable colors to the background colors of the socket identification labels. If you are unable to use color coding, then use the callout numbers described in Table 2-13 to complete the cabling of the storage expansion shelf. Because all cables with the same terminations are interchangeable, you can ignore the color coding.

Figure 2-8 Oracle Database Appliance X3-2 Cables for Storage Expansion Shelf

Description of Figure 2-8 follows
Description of "Figure 2-8 Oracle Database Appliance X3-2 Cables for Storage Expansion Shelf"

The cables shown in the preceding figure and described in the following table are included with each shipped Oracle Database Appliance X3-2 storage expansion shelf. These cables are all black, but have colored labels at each end that match the references to cable colors in the text and the label colors on the back panels.

Note:

The back panel of each node contains three PCIe generation 3 terminal slots, with two sockets in each slot. The PCIe slots are labeled "X PCIe3," where "X" is the PCIe slot number. Table 2-13 identifies these slots as PCIe slot 1, PCIe slot 2, and PCIe slot 3, which matches the numbers on the labels reading from left to right. The storage expansion shelf back panel has two IO modules, one located above the other. Each IO module has three ports, numbered 0, 1, and 2. Table 2-13 identifies these ports as either "top" or "bottom" ports, for ports in the upper and in the lower IO module respectively.

Table 2-13 Description of Callouts for Cabling Oracle Database Appliance X3-2 Storage Expansion Shelf

Callout Number from Figure 2-8 Description

7

Dark blue SAS cable:

  • From: Node 1, PCIe slot 2, SAS0

  • To: Storage expansion shelf, top I/O port 0

8

Light blue SAS cable:

  • From: Node 1, PCIe slot 3, SAS1

  • To: Storage expansion shelf, bottom I/O port 0

9

Dark red SAS cable:

  • From: Node 0, PCIe slot 2, SAS1

  • To: Storage expansion shelf, top I/O port 1

10

Light red SAS cable:

  • From: Node 0, PCIe slot 3, SAS0

  • To: Storage expansion shelf, bottom I/O port 1


See Also:

Oracle Database Owner's Guide for details about cabling with the supplied Cable Management Arm.

Attaching Electrical Power Cords and Turning On Oracle Database Appliance for the First Time

When you are ready to start up Oracle Database Appliance for the first time, complete the steps to attach the power cables and turn on the system. Use the instructions in the section or sections that apply to your version of Oracle Database Appliance.

Attaching Electrical Power Cords to Oracle Database Appliance X4-2

Use the callouts in following illustration (of the Oracle Database Appliance X4-2 back panels) and the following table as guides to insert the supplied power cords into Oracle Database Appliance X4-2. Ensure that the electrical outlets providing the power are grounded before plugging in the power cords.

Figure 2-9 Oracle Database Appliance X4-2 Power Cord Connections

Description of Figure 2-9 follows
Description of "Figure 2-9 Oracle Database Appliance X4-2 Power Cord Connections"

If you only use a single AC circuit, connect both power cords for each component to that circuit. However, to maintain N+1 power supply redundancy, use two separate AC circuits. Then, for both nodes and the storage shelf or shelves, connect one power cord from each AC circuit into each component. See the following table, where the two separate AC circuits are denoted by AC1 and AC2, for the recommended power connections as identified by the callouts in the preceding figure.

Caution:

Before you insert any power cables, ensure that the power supply On/Off switch on the storage shelf is in the Off position. If a storage expansion shelf is installed, then ensure that the power supply switches on both storage shelves are in the Off position.

Table 2-14 Electrical Power Cord Connections for Oracle Database Appliance X4-2

Callout Number from Figure 2-9 Component AC Circuit

1

Node 1

AC1

2

Node 0

AC1

3

Node 1

AC2

4

Node 0

AC2

5

Storage expansion shelf (Not required for single storage shelf implementations)

AC1

6

Storage shelf

AC1

7

Storage shelf

AC2

8

Storage expansion shelf (Not required for single storage shelf implementations)

AC2


See Also:

Oracle Database Owner's Guide for details about cabling with the supplied Cable Management Arm.

Attaching Electrical Power Cords to Oracle Database Appliance X3-2

Use the callouts in following illustration (of the Oracle Database Appliance X3-2 back panels) and the following table as guides to insert the supplied power cords into Oracle Database Appliance X3-2 . Ensure that the electrical outlets providing the power are grounded before plugging in the power cords.

Figure 2-10 Oracle Database Appliance X3-2 Power Cord Connections

Description of Figure 2-10 follows
Description of "Figure 2-10 Oracle Database Appliance X3-2 Power Cord Connections"

If you only use a single AC circuit, connect both power cords for each component to that circuit. However, to maintain N+1 power supply redundancy, use two separate AC circuits. Then, for both nodes and the storage shelf or shelves, connect one power cord from each AC circuit into each component. See the following table, where the two separate AC circuits are denoted by AC1 and AC2, for the recommended power connections as identified by the callouts in the preceding figure.

Caution:

Before you insert any power cables, ensure that the power supply On/Off switch on the storage shelf is in the Off position. If a storage expansion shelf is installed, then ensure that the power supply switches on both storage shelves are in the Off position.

Table 2-15 Electrical Power Cord Connections for Oracle Database Appliance X3-2

Callout Number from Figure 2-10 Component AC Circuit

1

Node 1

AC1

2

Node 0

AC1

3

Node 1

AC2

4

Node 0

AC2

5

Storage expansion shelf (Not required for single storage shelf implementations)

AC1

6

Storage shelf

AC1

7

Storage shelf

AC2

8

Storage expansion shelf (Not required for single storage shelf implementations)

AC2


See Also:

Oracle Database Owner's Guide for details about cabling with the supplied Cable Management Arm.

Turning On Oracle Database Appliance X4-2 for the First Time

This section is divided into two parts:

The steps in both parts must be completed before you configure your newly-installed Oracle Database Appliance X4-2 with the desired software. Before continuing, ensure that all of the required power cables are attached to both Oracle Database Appliance X4-2 nodes and to the storage shelf, and, if installed, to the storage expansion shelf. For details on attaching power cables, see Attaching Electrical Power Cords to Oracle Database Appliance X4-2.

Note:

You might notice that the two nodes appear to be running as soon as you attach the power cords because the fans are turned on and the front panel LEDs start to blink. However, to properly start the system processors, you must complete the steps in the Turning On System Processors section.

Turning On System Processors

  1. Switch the storage shelf power supply On/Off switches to the ”On” position.

    Each storage shelf has a two power switches, one located on the right side and one on the left side of the rear panel.

    The disks begin to initialize and the power supply LEDs light up green. This can take several minutes.

  2. If a storage expansion shelf is installed, switch the two storage expansion shelf power supply switches to the ”On” position.

    The disks begin to initialize and the power supply LEDs light up green. This can take several minutes.

    Wait for the storage units and server nodes to complete their initialization steps, indicated by the green SP LEDs on the front of the nodes staying on instead of blinking (see callout 1 in the following figure).

    Figure 2-11 Front of Oracle Database Appliance X4-2: Power Panel

    Description of Figure 2-11 follows
    Description of "Figure 2-11 Front of Oracle Database Appliance X4-2: Power Panel"

    Note:

    Do not apply main power to the server nodes until the storage shelves are fully initialized.
  3. For each server node:

    • Push the recessed Power button on the node's front panel (see callout 2 in the preceding figure).

    • Wait for several minutes until for the green Power OK LED on the node's front panel (see callout 3 in the preceding figure) to stay on instead of blinking.

      Note:

      Do not repeatedly push the power button (see callout 2 in the preceding figure).
    • Oracle Database Appliance X4-2 is ready for use as soon as the green Power OK LEDs (see callout 3 in the preceding figure) on the front of both system nodes remain steadily on.

  4. When the system is ready, you must record the the type of public network to which you will attach Oracle Database Appliance X4-2, as described in the following section, Defining Your Public Network Option.

Defining Your Public Network Option

After you turn on Oracle Database Appliance X4-2 for the first time, a short script runs on each node. Use the attached keyboard to answer questions that the script displays on the local monitor. First, define your system's public connection type by responding to the following:

Do you want to use Fiber or Copper card for public network? Please Choose [C]opper or [F]iber.

If you are connecting to a copper public network, which means you should have cabled Oracle Database Appliance X4-2 as in Figure 2-1, then enter C. If you are connecting to a fiber public network, which means you should have cabled Oracle Database Appliance X4-2 as in Figure 2-2, then enter F. The script then prompts you to confirm your choice.

If you make a mistake or need to change your public network choice later, reconfigure your system by running the script /opt/oracle/oak/lib/setupX4network.pl as the root user on both nodes.

WARNING:

If you have already deployed the End-User Bundle (for a Bare Metal installation) or the ODA_BASE template (for a Virtualized Platform installation), then you will need to redeploy that software after running the setupX4network.pl procedure.

Turning On Oracle Database Appliance X3-2 for the First Time

Before continuing with the following steps, ensure that all of the required power cables are attached to both Oracle Database Appliance X3-2 nodes and to the storage shelf, and, if installed, to the storage expansion shelf. For details on attaching power cables, see Attaching Electrical Power Cords to Oracle Database Appliance X3-2.

Note:

You might notice that the two nodes appear to be running as soon as you attach the power cords because the fans are turned on and the front panel LEDs start to blink. However, to properly start the system processors, you must complete the steps in this section.
  1. Switch the storage shelf power supply On/Off switches to the ”On” position.

    Each storage shelf has a two power switches, one located on the right side and one on the left side of the rear panel.

    The disks begin to initialize and the power supply LEDs light up green. This can take several minutes.

  2. If a storage expansion shelf is installed, switch the two storage expansion shelf power supply switches to the ”On” position.

    The disks begin to initialize and the power supply LEDs light up green. This can take several minutes.

    Wait for the storage units and server nodes to complete their initialization steps, indicated by the green SP LEDs on the front of the nodes staying on instead of blinking (see callout 1 in the following figure).

    Figure 2-12 Front of Oracle Database Appliance X3-2: Power Panel

    Description of Figure 2-12 follows
    Description of "Figure 2-12 Front of Oracle Database Appliance X3-2: Power Panel"

    Note:

    Do not apply main power to the server nodes until the storage shelves are fully initialized.
  3. For each server node:

    • Push the recessed Power button on the node's front panel (see callout 2 in the preceding figure).

    • Wait for several minutes until for the green Power OK LED on the node's front panel (see callout 3 in the preceding figure) to stay on instead of blinking.

      Note:

      Do not repeatedly push the power button (Figure 2-12, callout 2).
    • Oracle Database Appliance X3-2 is ready for use as soon as the green Power OK LEDs (see callout 3 in the preceding figure) on the front of both system nodes remain steadily on.

Attaching Electrical Power Cords and Turning On Oracle Database Appliance for the First Time

Before turning on Oracle Database Appliance, insert the supplied power cords into the rear panel of each node. The power sockets are at the lower left corner of the rear panels. Ensure that the electrical outlets providing the power are grounded before plugging in the power cords.

When you plug the connected power cords into the AC outlets, the system boots into standby power mode. In standby power mode, the service processor is active but the host is off. Confirm when a node is in standby power mode by observing the following conditions:

  • The service processor (SP) status LED on the server node front panel lights green and goes from slow blink to steady on (see callout 1 in the following figure)

  • The power OK LED on the server node front panel lights green and goes to standby blink (see callout 3 in the following figure). This might take up to 5 minutes.

Figure 2-13 Front of Oracle Database Appliance: Power Panel

Description of Figure 2-13 follows
Description of "Figure 2-13 Front of Oracle Database Appliance: Power Panel"

To apply main power to a node, wait for the node to attain standby power mode and then push the recessed power button (see callout 2 in the preceding figure). While the node is booting, the power OK LED (callout 3 in the preceding figure) blinks. The power OK LED stops blinking and stays on when the node is operational.

Configuring Oracle Integrated Lights Out Manager

Configure Oracle Integrated Lights Out Manager (Oracle ILOM) to manage Oracle Database Appliance independently of the operating system. Although not required, Oracle ILOM provides alternate ways to restart and troubleshoot Oracle Database Appliance.

To configure Oracle ILOM, you will need:

  • a name and IP address for each of the two nodes

  • a password to replace the default Oracle ILOM password

  • access to a management network through an assigned netmask

  • an Ethernet cable connected from each node of Oracle Database Appliance, using the nodes' NET MGT ports, into the management network

See also:

Chapter 2, "Overview of Oracle Database Appliance"in Oracle Database Appliance Owner's Guide for details about the port used for ILOM on your platform.

In the default configuration, Dynamic Host Configuration Protocol (DHCP) is enabled in Oracle ILOM and the DHCP server automatically assigns network settings to each node. To determine the IP address or host name assigned by the DHCP server, to the nodes, use the network tools provided with the DHCP server.

If you do not use DHCP, then use the custom option in Oracle Database Appliance Manager configurator to assign IP addresses and host names to Oracle ILOM when you deploy your database.

Note:

Until you complete Oracle Database Appliance configuration, as described in Chapter 3, you will not be able to access Oracle ILOM unless DCHP is enabled.

To connect to the Oracle ILOM, use one of the following two methods:

  1. Log in using a web interface by completing these steps:

    1. Using a client system's browser, enter the IP address or host name assigned by DHCP into the browser address field and press Enter.

    2. At the login page, enter the default user name, root and the default password, changeme.

      The Oracle ILOM web interface appears.

  2. Log in using a command line interface (CLI) by completing these steps:

    1. Using a client system, establish a secure shell (SSH) connection by entering the following on the command line:

      ssh -l root sp_ip_address

      where sp_ip_address is the IP address assigned by DHCP.

    2. Enter the default user name, root, and the default password, changeme.

      The Oracle ILOM CLI prompt appears.

Configuring an Initial Network

The following two tasks complete the preparations to download the files you need deploy Oracle Database Appliance:

Attaching Public Network Connections to Oracle Database Appliance X4-2

Connect cables between your public gateway and Oracle Database Appliance X4-2 using bond0, the public interface.

If you are connecting to a fiber public network, which means you should have cabled Oracle Database Appliance X4-2 as inFigure 2-2, then connect the cables to the NET 0 or the NET 1 sockets in the PCIe3 connection strip with the label number ”1,” (which is the PCIe3 strip at the left side of the back panel) on Node 0. These sockets are labeled 1 and 2 in the following figure.

Figure 2-14 Public Network Connections for Oracle Database Appliance X4-2

Description of Figure 2-14 follows
Description of "Figure 2-14 Public Network Connections for Oracle Database Appliance X4-2"

If you are connecting Oracle Database Appliance X4-2 to a copper public network, which means you should have installed your interconnect cables as shown in Figure 2-1, then connect the cables to the Net 0 or Net 1 sockets in the connection strip labeled 100 - 10 GbE on Node 0. These sockets are labeled 3 and 4 in the preceding figure.

Once you are connected, activate the X Window System by entering the following command from your terminal interface:

# startx 

Alternatively, use Oracle Integrated Lights Out Manager (Oracle ILOM) to launch a local or remote host console session. See the section Configuring Oracle Integrated Lights Out Manager, earlier in this chapter, for details about Oracle ILOM connections to Oracle Database Appliance.

Attaching Public Network Connections on Oracle Database Appliance X3-2

Connect Ethernet cables between your public gateway and Node 0 of Oracle Database Appliance X3-2 using ports Eth2/Eth3 (bond0, the public interface). See callouts 1 and 2 in Figure 2-15 for reference.

Figure 2-15 Oracle Database Appliance X3-2 Public Network Connections (Node 0)

Description of Figure 2-15 follows
Description of "Figure 2-15 Oracle Database Appliance X3-2 Public Network Connections (Node 0)"

Once you are connected, activate the X Window System by entering the following command from your terminal interface:

# startx 

Alternatively, use Oracle Integrated Lights Out Manager (Oracle ILOM) to launch a local or remote host console session. See the section Configuring Oracle Integrated Lights Out Manager, earlier in this chapter, for details about Oracle ILOM connections to Oracle Database Appliance.

Attaching Public Network Connections on Oracle Database Appliance

Connect Ethernet cables between your public gateway and Node 0 of Oracle Database Appliance using ports Eth2/Eth3 (bond0, the public interface). See callout 3 in Figure 2-16 for reference.

Figure 2-16 Oracle Database Appliance Public Network Connections (Node 0)

Description of Figure 2-16 follows
Description of "Figure 2-16 Oracle Database Appliance Public Network Connections (Node 0)"

Once you are connected, activate the X Window System by entering the following command from your terminal interface:

# startx 

Alternatively, use Oracle Integrated Lights Out Manager (Oracle ILOM) to launch a local or remote host console session. See the section Configuring Oracle Integrated Lights Out Manager, earlier in this chapter, for details about Oracle ILOM connections to Oracle Database Appliance.

Configuring Initial Network Connection

To manage your Oracle Database Appliance deployment across a network, you need to configure an initial network connection by completing Steps 1 through 3. You use this network to transfer deployment software to to Oracle Database Appliance. If you have physical access to your Oracle Database Appliance, then you can download deployment software to USB storage that you plug into the system, in which case you do not need an initial network.

Note:

An initial network configuration will be replaced during the final image deployment.
  1. Log in as root, password welcome1, and change directory to /opt/oracle/oak/bin/. If you are configuring the network on Oracle Database Appliance Virtualized Platform, then login to Dom0 to complete this step.

  2. Oracle recommends that you perform a validity check of the cables before you perform any other actions on Oracle Database Appliance X3-2 and Oracle Database Appliance X4-2 bare metal configurations. (For Virtualized Platform installations, the check is performed after deploying the system as described in Chapter 3). Perform this check by running the oakcli validate -c storageTopology command. For more details, see the section ”Cabling Validation Command” in Chapter 7.

  3. Run the command oakcli configure firstnet to configure the initial network. You might need to refer to data that you collected on the work sheets in the first section of this chapter for some of the required values. Use the global option by accepting the default value in the first prompt and then provide the required data for the remaining prompts. You do not need to enter anything to accept the default values that are shown in square brackets at the end of prompts.

    The following is an example is from Oracle Database Appliance Virtualized Platform but shows the key features of the dialog no matter which system you are using. In this example, default values are always selected and values that you need to provide when running the command shown in italic font.

    /opt/oracle/oak/bin/oakcli configure firstnet
    Configure the network for the node(s)(local, global) [global]:
    The network configuration for both nodes:
    Domain Name:  your organization domain name
    DNS Server(s):  Primary Dns Server:  your primary DNS server
                    Secondary Dns Server:  your secondary DNS server
                    Tertiary Dns Server:  your tertiary DNS server
    Node Name       Host Name
    0               your Node 0 host name
    1               your Node 1 host name
    Choose the network interface to configure (net1, net2, net3, net4) [net1]:
    Configure DHCP on net1 (yes/no) [no]:
    You have chosen static configuration on net1
    Enter the IP address for net1 on Node 0: your Node 0 IP address
    Enter the IP address for net1 on Node 1: your Node 1 IP address
    Netmask for net1: your netmask
    Gateway Address for net1 [<Gateway IP>]:
    Plumbing the IPs now on Node 0 …
    ::::::::::::::::::::::::::::::::::::::::::::::::::
    Plumbing the IPs now on Node 1 …
    ::::::::::::::::::::::::::::::::::::::::::::::::::
    

In the preceding example, the prompt for the net1 gateway address includes a default value, shown as <Gateway IP>. The program derives this gateway address using values from previous entries. You should accept this value unless your network administrator has provided a specific address that differs from the derived address.

Note:

Oracle recommends using the oakcli configure firstnet command only one time on Oracle Database Appliance. Subsequent use after configuring the initial network can cause unpredictable changes to your network settings.

Validating Oracle Appliance Manager Software Version

Before deploying Oracle Database Appliance, as described in Chapter 3, you should have the current version of the Oracle Appliance Manager software installed. Run the following command to find the installed version:

oakcli show version

to confirm that you have version 2.10.0.0.0. If you have an earlier version, then see the My Oracle Support Note 888888.1 (at https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=888888.1) for information on how to re-image your system with the current version.