3 Using Oracle Exadata Deployment Assistant

Oracle Exadata Deployment Assistant creates the Oracle Exadata Rack configuration file. The file automates the installation process. The utility is available from My Oracle Support. Refer to My Oracle Support note 888828.1 for additional information.

Note:

For ease of reading, the name "Oracle Exadata Rack" is used when information refers to both Oracle Exadata Database Machine and Oracle Exadata Storage Expansion Rack.

3.1 Overview of Oracle Exadata Deployment Assistant

Use the deployment assistant to create the configuration file for Oracle Exadata Rack. The deployment assistant is used for Oracle Exadata Database Machine, Zero Data Loss Recovery Appliance, and Oracle SuperCluster.

Before Oracle Exadata Rack arrives:

  1. Work with your network and database administrators to evaluate the current network settings, such as current IP address use and network configuration.

  2. Define the settings for Oracle Exadata Rack, such as network configuration and backup method.

  3. Run the deployment assistant, and select the type of system. Options are Oracle Exadata Database Machine, Zero Data Loss Recovery Appliance, and Oracle SuperCluster.

    Note:

    All fields in the deployment assistant are required unless otherwise indicated.

  4. Generate the configuration file.

Oracle Exadata Deployment Assistant has two main phases:

In phase 1, the customer provides naming, DNS, NTP, and networking details. This information is collected using the Oracle Exadata Deployment Assistant user interface. A configuration file is generated.

In phase 2, the configuration file is pushed to the database node, and the validation and installation is completed.

Accessibility Note: If you are using Oracle Exadata Deployment Assistant with assistive technology (for accessibility) on Windows, you need to enable Java Access Bridge.

3.1.1 Considerations when Using Oracle Exadata Deployment Assistant

Review this information when using Oracle Exadata Deployment Assistant (OEDA).

Note the following when using Oracle Exadata Deployment Assistant:

  • Oracle Exadata Rack ships with the Oracle Linux operating system installed on the database servers, with the Oracle Linux as the default.

  • The rack name is used to generate host names for network interfaces for all systems. For example, a value of dm01 results in database server host names of dm01db01, dm01db02, dm01db03, and so on, and Exadata Storage Server host names of dm01cel01, dm01cel02, dm01cel03, and so on.

    In a multi-rack configuration, each Oracle Exadata Rack name should be a unique name that identifies the machine. Oracle recommends using dm01 for the first Oracle Exadata Rack, dm02 for the second, dm03 for the third, and so on. Up to eighteen Oracle Exadata Racks can be cabled together without additional Sun Datacenter InfiniBand Switch 36 switches.

  • The backup method information is used to size the Oracle Automatic Storage Management (Oracle 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 Rack mean database backups are 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) is 40% and 60%, respectively.

    • Backups external to Oracle Exadata Rack mean database backups are created on disk or tape media that is external to currently deployed Oracle Exadata Database Machine, and not on existing 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 do not reserve additional space in the RECO disk group when using Oracle Exadata Deployment Assistant.

      When choosing this option, the FRA internal to Oracle Exadata Rack contains 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) is 80% and 20%, respectively.

  • Oracle recommends the use of high redundancy disk groups for mission critical applications. The location of the backup files depends on the backup method. To reserve more space for the DATA disk group, choose external backups. This is especially important when the RECO disk group is high redundancy. The following table shows the backup options and settings.

    Table 3-1 Protection Levels and Backup Methods

    Description DATA Group Contains... RECO Group Contains... Oracle ASM Redundancy Level for DATA Disk Group Oracle ASM Redundancy Level for RECO Disk Group

    High Redundancy for ALL

    Data files

    Temporary files

    Online redo logs

    Control file

    Archive logs

    Flashback log files

    High

    High

    High Redundancy for DATA

    Data files

    Online redo logs

    Control file.

    Archive logs

    Temporary files

    Flashback log files

    High

    Normal

    High Redundancy for Log and RECO

    Data files

    Temporary files

    Online redo logs

    Control file

    Archive logs

    Flashback log files

    Normal

    High

    Normal Redundancy

    Data files

    Temporary files

    Online redo logs

    Control file

    Online redo logs

    Archive logs

    Flashback log files

    Normal

    Normal

  • A valid time zone name is required for Oracle Exadata Database Machine installation. Time zone data provided with Oracle Exadata Database Machine and Oracle 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.

3.1.2 Using Oracle Exadata Deployment Assistant on Systems with Non-Default root Passwords

Starting with the November 2016 release, Oracle Exadata Deployment Assistant supports deployment on Exadata environments that already have non-default root passwords. You can perform the deployment without having to change the root password back to the default. In earlier releases, OEDA expected the root password to be the default on all the servers in an Exadata environment.

With the new non-default password feature, root passwords can be same or different and/or non-default on each node in a rack. If non-default passwords are already set, add the "-p" option to the existing command line options when you start up OEDA. For example:

./install.sh -cf <config.xml> -s 1 -p

The "-p" option causes OEDA to prompt for the root password. Make sure you enter the correct password because an incorrect password will disable root login for 5 minutes by default, and after 5 failed login attempts, the server will be locked down.

If you want to change the root password on database and storage servers, use the changePassword.sh utility included with OEDA. It is located in the same directory as install.sh.

The following example changes the root password:

./changePassword.sh -cf <config.xml> -userName root

The utility will prompt for the current root password and will allow password changes of any users in the rack. Note that this option assumes that the storage servers are not locked down.

3.2 OEDA Graphical User Interface

When you run the config.sh program, it starts the OEDA graphical user interface.

The OEDA GUI walks you through several configuration details screens, where you provide information about how your Exadata system should be configured.

3.2.1 Using Oracle Exadata Deployment Assistant

Use the deployment assistant for initial configuration, and when adding to an existing deployment. You can import an existing configuration when adding new racks or components.

Have the following available before running the deployment assistant:

  • IP addresses

  • Machine names

  • DNS information

  • NTP information for the rack

The following buttons are available on each Oracle Exadata Deployment Assistant page:

  • Help: View context-sensitive help.

  • Import: Import an existing configuration file. The file format is XML.

  • Back: View the previous page.

  • Next: View the next page.

  • Cancel: Cancel the configuration process.

The following procedure describes how to use the deployment assistant:

Notes:

Explanations for each field on the pages are provided in the other sections of this chapter.

  1. Ensure the machine that is used to run Oracle Exadata Deployment Assistant has Oracle JRE 1.6 or later.

    Accessibility Note: For screen reader and screen magnifier users: Accessibility testing is conducted only on the Windows platform. The JRE version must be 1.7.0_80 for the Java Access Bridge to function correctly with the assistive technology such as JAWS and ZoomText. JRE 1.7.0_80 is shipped with Oracle Exadata Deployment Assistant for Windows in the November 2015 release.

  2. Copy the operating system-specific directory to the machine that will run Oracle Exadata Deployment Assistant. The following directories are available:

    linux-x64
    macos-x64
    solaris-sparcv9
    solaris-x64
    windows-i586
    

    Note:

    • The deployment assistant is available in the directory of the latest Bundle Patch.

    • The operating system-specific directory should match the operating system of the machine that will run the deployment assistant.

  3. Start the deployment assistant using one of the following commands:

    • On Linux, Apple, or UNIX:

      ./config.sh
      
    • On Microsoft Windows:

      ./config.cmd
      

    The Oracle Exadata Deployment Assistant window appears.

  4. Click Next.

  5. Enter the customer details on the Customer Details page, and click Next.

  6. Select the hardware for the deployment on the Hardware Selection page, and click Next.

  7. Enter the customer information on the Define Customer Network page, and click Next.

  8. Enter the information for the management network on the Administration Network page, and click Next.

    Note:

    To change the default names of the administration network, click Modify. After changing the fields, click Save to save the changes.

  9. Enter the client network information on the Client Ethernet Network page, and click Next.

    Note:

    To change the default names of the client network, click Modify. After changing the fields, click Save to save the changes.

  10. Enter the InfiniBand information on the InfiniBand Network page, and click Next.

    Note:

    To change the default names of the InfiniBand network, click Modify. After changing the fields, click Save to save the changes.

  11. (Optional) Enter the backup information on the Backup Network page, and click Next.

    Note:

    To change the default names of the backup network, click Modify. After changing the fields, click Save to save the changes.

  12. Enter the operating system information on the Identify Compute Node Base OS configuration page, and click Next.

  13. Review, and edit the information for the management and private networks, and click Next.

  14. Define the clusters on the Define Clusters page for each cluster, and click Next.

  15. Review and edit the cluster information for each cluster, and click Next.

  16. (Optional) Enter the e-mail alert information on the Cell Alerting page, and click Next.

  17. (Optional) Enter the Oracle Configuration Manager information on the Oracle Configuration Manager page, and click Next.

  18. (Optional) Enter the Auto Service Request (ASR) information on the Auto Service Request page, and click Next.

  19. (Optional) Enter the Oracle Enterprise Manager Grid Control information on the Grid Control Agent page, and click Next.

  20. (Optional) Enter additional information about the deployment in the text field. Information entered in the field appears at the bottom of the InstallationTemplate.html file.

  21. Click Next to create the configuration file.

  22. Enter a file name, and click OK to create the file, or Cancel to not create the file.

  23. Copy the configuration files to a directory in the /u01 directory, such as the /u01/oeda directory, on the first database server in Oracle Exadata Rack.

    The file is located in the /tmp/OneCommand directory on Linux, Apple, and UNIX systems, and the drive:\OneCommand directory on Microsoft Windows systems. The drive depends on the where deployment assistant was run on the Microsoft Windows system.

See Also:

"Running Oracle Exadata Deployment Assistant on Windows" in Oracle Exadata System Software User's Guide

3.2.2 Customer Details Configuration Page

Define the customer information on this page. Table 3-2 lists the customer details fields.

Note:

The domain specified on this page is used as the domain for all networks. If different domains are used for the client and backup networks, then specify the administration network on this page. The client and backup networks can be changed on the Review and Edit SCAN, Client, VIP and Optional Backup Networks page.

Table 3-2 Customer Details Page

Customer Details Field Description

Customer name

Identifies the customer.

Note:

The name can contain any alphanumeric characters, including spaces.

The field cannot be empty.

Application

Identifies the application used with the rack.

Network Domain Name

Identifies the network domain.

Note:

Use lowercase letters for the name.

Name Prefix

Defines the prefix for network interfaces.

Note:

The prefix can contain any alphanumeric character.

The prefix cannot contain spaces.

The maximum length is 20 characters.

The field cannot be empty.

The default is dm01.

Example:

A value of dm01 results in a database server host name of dm01db01, and a storage server host name of dm01cel01.

Region

Sets the region for the rack.

Note:

Select a region from the list.

Timezone

Sets the time zone where the rack will be installed.

Note:

The time zones shown are based on the selected region.

3.2.3 Hardware Selection Configuration Page

Select your hardware from the list on the left. The list on the right contains the hardware for your environment.

3.2.4 Rack Details Configuration Page

Click the check box if you want to include a spine switch as part of the rack configuration. Do this for each rack that will have a spine switch.

3.2.5 Customer Network Configuration Page

Table 3-3 lists the number of required IP addresses for the customer network.

Table 3-3 Customer Network Configuration Page

Customer Details Field Description

Bonded/Non-Bonded

Identifies type of network bonding.

Note: The Admin and InfiniBand networks are non-bonded networks.

This field is not available on X7 systems.

Subnet Mask

Sets the IP address mask for the subnet.

Gateway

Sets the IP address for the gateway.

Client or Backup Network Format

Selects the Ethernet cards, based on cable type.

Options prior to X7-2:

  • 1/10 GbE Base-T when using copper cables

  • 10 GbE Optical when using fiber optic cables

Note: The Admin network uses 1/10 GbE Base-T Ethernet cables. The network format for the private network is InfiniBand.

Options for X7-2 Systems:

On X7-2 systems, there are 3 available formats for client and backup networks.

  • RJ45/SFP28 Combined on Motherboard

    • RJ45 10 GBit

    • SFP28 10 GBit

    • SFP28 25GBit

  • SFP28 PCI Dual Port Card

    • SFP28 10 GBit

    • SFP28 25GBit

  • RJ45 PCI Quad Port Card (extra cost option)

Options for X7-8 Systems:

On X7-8 systems, there are 2 available formats for client and backup networks:

  • RJ45 on Motherboard

  • SFP28 PCI Dual Port Cards

    • SFP28 10 GBit

    • SFP28 25GBit

If you select one of the SFP28 network types on X7-2 or X7-8 systems, you must additionally specify whether to use 10 GBit or 25 GBit connections.

Available Network

Enables an additional subnet for backup, replication, or data recovery.

Note: This subnet is optional.

Advanced Options

Click this button to display VLAN options.

VLAN ID

This field is displayed only when the Advanced Options button is clicked.

For the Admin network, the VLAN ID is a numeric value between 1 and 4079. If this field is empty, then VLAN is not enabled.

For the Client network, the VLAN ID is a numeric value between 1 and 4095. You also need to select the "Bonded" option to enable VLAN. If the VLAN ID field is empty, then VLAN is not enabled.

For the Backup network, the VLAN ID is a numeric value between 1 and 4095. If the VLAN ID field is empty, then VLAN is not enabled. If the Backup network uses VLAN, then the Client network must also be configured to use VLAN. You also need to select the "Bonded" option for the Backup network to enable VLAN.

If the backup network shares the same cable as the client network, ensure that:

  • the "Share Client Network ports" box is selected, and

  • the "Network Format" is the same type for both client and backup networks.

Note that for all networks, the customer is responsible for configuring VLAN on the switch.

Note:

Each IP address pool should consist of consecutive IP addresses. If consecutive IP addresses are not available, then modify the IP addresses at the end of the Oracle Exadata Deployment Assistant process.

3.2.6 Administration Network Configuration Page

Each database server and Exadata Storage Server has two network interfaces for administration. One network provides management access to the operating system through the Ethernet interface, and the other network provides access to the Integrated Lights Out Manager (ILOM) through the ILOM Ethernet interface.

The following table lists the administration network fields. Sample host name formats are shown, based on the prefix entered on the Customer Details page. To modify the name formats, click Modify.

Table 3-4 Administration Network Page

Administration Network Field Description

Starting IP Address for Pool

Assigns the starting IP address for the administration network port of the servers, and switches.

Note: These addresses are also assigned to the ILOM ports on the database and storage servers.

The pool should consist of consecutive IP addresses. If consecutive IP addresses are not available, then specific IP addresses can be modified during the configuration process.

Pool Size

Defined by the hardware selection.

Ending IP Address for Pool

Defined by the starting IP address and the pool size.

Is the default gateway for database servers

Specifies that the gateway IP address is the default gateway for the database servers.

Note: This option is not usually selected for the database servers.

Defines the Hostname for the Compute Nodes

Select this option if the adapter name defines the host names for the database servers.

Note: This option is usually selected for the database servers.

3.2.6.1 Modifying the Default Administration Network Host Names

Default administration network host names are usually changed to meet corporate naming standards or compatibility with existing systems. Table 3-5 lists the administration network format mask fields.

Note:

  • Oracle recommends using the same starting IDs for the servers and server ILOMs.

  • All fields must be filled in.

  • The percent signs (%) in the names are replaced by the numbers entered into the Starting ID fields.

Table 3-5 Administration Network Format Masks Page

Administration Network Format Masks Field Description

Compute Node Name

Sets the administration name for the first database server in this rack.

Note:

The name contains alphanumeric characters.

Compute Node Starting ID

Defines the starting numeric ID for the first database server in this rack.

Compute ILOM Name

Sets the administration name for the first database server ILOM in this rack.

Note:

The name contains alphanumeric characters.

Compute ILOM Starting ID

Defines the starting numeric ID for the first database server ILOM in this rack.

Note:

Cell Node Name

Sets the administration name for the first Exadata Storage Server in this rack.

Note:

The name contains alphanumeric characters.

Cell Node Starting ID

Defines the starting numeric ID for the first Exadata Storage Server in this rack.

Note:

Cell Node ILOM

Sets the administration name for the first Exadata Storage Server ILOM in this rack.

Note:

The name contains alphanumeric characters.

Cell ILOM Starting ID

Defines the starting numeric ID for the first Exadata Storage Server ILOM in this rack.

Note:

Cisco Switch

Sets the administration name for the Cisco switch in this rack.

Note:

The name contains alphanumeric characters.

KVM Switch

Sets the administration name for the KVM switch in this rack.

Note:

The name contains alphanumeric characters.

PDU-A

Sets the administration name for PDU-A (power distribution unit A) in this rack.

Note:

The name contains alphanumeric characters.

PDU-B

Sets the administration name for PDU-B in this rack.

Note:

The name contains alphanumeric characters.

InfiniBand Spine

Sets the administration name for the InfiniBand spine switch in this rack.

Note:

The name contains alphanumeric characters.

InfiniBand Leaf

Sets the administration name for the first InfiniBand leaf switch in this rack.

Note:

The name contains alphanumeric characters.

InfiniBand Leaf

Sets the administration name for the second InfiniBand leaf switch in this rack.

Note:

The name contains alphanumeric characters.

3.2.7 Client Ethernet Configuration Page

Applications access the database through the client Ethernet network using Single Client Access Name (SCAN) and Oracle RAC Virtual IP (VIP) addresses.

If VLAN tagging is to be used, then it must be enabled by the customer after the initial deployment. See the My Oracle Support notes for details.

The following table lists the client network fields. Sample database client name formats are based on the prefix entered on the Customer Details page. To modify the name formats, click Modify.

Table 3-6 Client Ethernet Page

Client Ethernet Field Description

Starting IP Address for Pool

Assigns the starting IP address for the client network port of the servers, and switches.

Note: These addresses are also assigned to the ILOM ports on the database and storage servers.

The pool should consist of consecutive IP addresses. If consecutive IP addresses are not available, then specific IP addresses can be modified during the configuration process.

Pool Size

Defined by the hardware selection.

Ending IP Address for Pool

Defined by the starting IP address and the pool size.

Is the default gateway for database servers

Specifies that the gateway IP address is the default gateway for the database servers.

Note: This option is usually selected for the database servers.

Defines the Hostname for the Compute Nodes

Specifies that the adapter name defines the host names for the database servers.

Note: This option is not usually selected for the database servers.

3.2.7.1 Modifying the Default Client Ethernet Network Names

Default client network names are usually changed to meet corporate naming standards or compatibility with existing systems. The following table lists the client network format mask fields.

Note:

  • All fields must be filled in.

  • The percent signs (%) in the names are replaced by the numbers entered into the Starting ID fields.

Table 3-7 Client Network Format Masks Page

Client Network Format Masks Field Description

Client Access Name

Assigns the client access name for this rack.

Note: The name contains alphanumeric characters.

Client Access Starting ID

Assigns the starting numeric ID for the client access name in this rack.

VIP Name

Assigns the VIP name for this rack.

Note: The name contains alphanumeric characters.

VIP Starting ID

Sets the starting numeric ID for the VIP name in this rack.

SCAN Details

Assigns the SCAN name for this rack.

Note: The name contains alphanumeric characters.

3.2.8 InfiniBand Network Configuration Page

The InfiniBand network is the private network between database servers and storage servers. The following table lists the InfiniBand network fields.

Note:

Sample name formats are based on the prefix entered on the Customer Details page. To modify the name formats, click Modify.

Table 3-8 InfiniBand Network Page

InfiniBand Network Field Description

Starting IP Address for Pool

Assigns the starting IP address for the private network port.

Note: The pool should consist of consecutive IP addresses. If consecutive IP addresses are not available, then specific IP addresses can be modified during the configuration process.

Pool Size

Defined by the hardware selection.

Ending IP Address for Pool

Defined by the starting IP address and the pool size.

3.2.8.1 Modifying the Default InfiniBand Network Names

The following table lists the InfiniBand network format mask fields.

Note:

The percent signs (%) in the names are replaced by the numbers entered into the Starting ID fields.

Table 3-9 Private (IB) Network Format Masks Page

Private (IB) Network Format Masks Field Description

Compute Private Name

Sets the InfiniBand access name for the database servers.

Note: The name contains alphanumeric characters.

This field cannot be empty.

Compute Private Starting ID

Sets the starting ID for the InfiniBand access name for the database servers.

Note: The ID contains numeric characters.

This field cannot be empty.

Cell Private Name

Sets the InfiniBand access name for the storage servers.

Note: The name contains alphanumeric characters.

This field cannot be empty.

Cell Private Starting ID

Sets the starting ID for the InfiniBand access name for the storage servers.

Note: The ID contains numeric characters.

This field cannot be empty.

3.2.9 Backup Network Configuration Page

The following table lists the backup network fields.

Note:

Sample name formats are based on the prefix entered on the Customer Details page. To modify the name formats, click Modify.

Table 3-10 Backup/Data Guard Ethernet Network Page

Backup/Data Guard Ethernet Network Field Description

Starting IP Address for Pool

Assigns starting IP address for the backup network.

Note: The pool should consist of consecutive IP addresses. If consecutive IP addresses are not available, then IP addresses can be modified during the configuration process.

Pool Size

Defined by the hardware selection.

Ending IP Address for Pool

Defined by the starting IP address and the pool size.

Related Topics

3.2.9.1 Modifying the Default Backup Network Name

The following table lists the backup network format mask fields.

Note:

The percent signs (%) in the names are replaced by the numbers entered into the Starting ID fields.

Table 3-11 Backup Network Format Masks Page

Backup Network Format Masks Field Description

Name

Sets the name for the backup access network.

Note: The name contains alphanumeric characters.

This field cannot be empty.

Starting ID

Sets the starting ID for the database servers in this rack.

Note: The ID contains numeric characters.

This field cannot be empty.

3.2.10 Identify Compute Node OS and Enable Capacity-on-Demand Configuration Page

Operating system configuration is based on processor type. Oracle Exadata Racks with Intel processors support Oracle Linux.

Click Enable Capacity-on-Demand to reduce the initial number of active cores on the servers, and then set the number of active cores.

3.2.11 Review and Edit Management and Private Networks

Review and update entries for the node specific data for the Management, ILOM, and private networks for the compute nodes, storage cells, and the switches used in the rack.

To check the validity of the network configuration data, click the Lookup IP button. OEDA will highlight fields in red if:
  • The IP address or host name could not be resolved through DNS lookup

  • The user input differs from what is the DNS and the fields were edited to match the DNS

If you go back and make changes to any of the previous configuration pages, click Re-Generate Data on this page, and then click Next.

Accessibility note for screen reader users: The Lookup IP button in this screen provides no feedback to a screen reader user once it is activated. The node names are checked using DNS lookup when this button is activated and any node name that cannot be resolved will have an asterisk prefixed to the name of the field. You may hear the word "star" in front of such fields.

For screen magnifier users: There is text above the Lookup IP button that indicates that fields with an asterisk indicate node names that could not be resolved through DNS lookup. Such fields also have a red box around them. The Lookup IP also highlights the field in red if the user input differs from what is found in DNS.

3.2.12 Define Clusters

More than one cluster can be defined for Oracle Exadata Rack environments. Larger environments support multiple clusters. Each cluster requires a minimum of two physical database servers, and three Exadata Cells.

If one cluster is used, then click All to move all components to the cluster. If more then one cluster is used, then enter the number of clusters. For each cluster, select its subtab, then select the components for the cluster, and then click Add.

3.2.13 Define Clusters Details

The following table lists the cluster fields. Most fields are filled in based on earlier configuration pages.

Table 3-12 Cluster Configuration Page

OS Field Description

Cluster name

Assigns the cluster name.

Note: The name can contain alphanumeric characters, periods (.), and hyphens (-). The name must start with an alphanumeric character.

This field cannot be empty.

Prefix

Assigns the prefix for the cluster.

DNS

Sets the DNS IP Address.

Note: At least one IP address must be entered.

NTP

Sets the NTP IP Address.

Note: At least one IP address must be entered.

Domain Name

Sets the cluster domain name.

Region

Sets the region for the cluster.

Timezone

Sets the time zone for the cluster.

Role Separated

Allows the responsibilities and privileges to be separated by role.

Note: Providing system privileges for the storage tier using the SYSASM privilege instead of the SYSDBA privilege provides a clear division of responsibility between Oracle ASM administration and database administration.

When used with Oracle ASM and database-scoped security, role separation helps to prevent different databases using the same storage from accidentally overwriting each other's files.

User name

Sets the user name for the database owner.

This option is not available if using role-separated authentication.

User ID

Assigns the database owner ID.

This option is not available if using role-separated authentication.

User base

Sets the database directory.

This option is not available if using role-separated authentication.

DBA Group name

Sets the DBA group name.

This option is not available if using role-separated authentication.

DBA Group ID

Assigns the DBA group ID.

This option is not available if using role-separated authentication.

Grid ASM Home OS User

Sets the Oracle ASM owner name. The default value is grid. This is the user that owns the Oracle Grid Infrastructure installation.

This option is available when using role-separated authentication.

Grid ASM Home OS User ID

Assigns Oracle ASM owner ID. The default value is 1000.

This option is available when using role-separated authentication.

Grid ASM Home base

Sets the Oracle grid infrastructure directory. The default value is /u01/app/grid.

This option is available when using role-separated authentication.

ASM DBA Group

Sets the Oracle ASM DBA group name. The default value is asmdba.

Membership in this group enables access to the files managed by Oracle ASM.

This option is available when using role-separated authentication.

ASM DBA Group ID

Assigns the Oracle ASM DBA group ID. The default value is 1004.

This option is available when using role-separated authentication.

ASM Home Oper Group

Sets the Oracle ASM operator group name. The default value is asmoper.

This group of operating system users has a limited set of Oracle instance administrative privileges including starting up and stopping the Oracle ASM instance.

This option is available when using role-separated authentication.

ASM Home Oper Group ID

Assigns the Oracle ASM operator group ID. The default value is 1005.

This option is available when using role-separated authentication.

ASM Home Admin Group

Sets the Oracle ASM administration group name. The default value is asmadmin.

This group uses SQL to connect to an Oracle ASM instance as SYSASM using operating system authentication. The SYSASM privileges permit mounting and dismounting of disk groups, and other storage administration tasks. SYSASM privileges provide no access privileges on an Oracle Database instance.

This option is available when using role-separated authentication.

ASM Home Admin Group ID

Assigns the Oracle ASM administration group ID. The default value is 1006.

This option is available when using role-separated authentication.

RDBMS Home OS User

Sets the Oracle Database installation owner name. The default value is oracle.

This option is available when using role-separated authentication.

RDBMS Home OS User ID

Assigns the Oracle Database installation owner ID. The default value is 1001.

This option is available when using role-separated authentication.

RDBMS Home base

Sets the Oracle Database installation directory. The default value is /u01/app/oracle.

This option is available when using role-separated authentication.

RDBMS DBA Group

Sets the DBA group name. The default value is dba.

This option is available when using role-separated authentication.

RDBMS DBA Group ID

Assigns the DBA group ID. The default value is 1002.

This option is available when using role-separated authentication.

RDBMS Home Oper Group

Sets the Oracle Database operator group name. The default value is racoper.

This option is available when using role-separated authentication.

RDBMS Home Oper Group ID

Assigns the Oracle Database operator group ID. The default value is 1003.

This option is available when using role-separated authentication.

OINSTALL group

Sets the Oracle Inventory group name. The default value is oinstall.

OINSTALL Group ID

Assigns the Oracle Inventory group ID. The default value is 1001.

Inventory Location

Sets the Oracle inventory (oraInventory) directory path. The default value is /u01/app/oraInventory.

Grid Infrastructure Home

Sets the Grid Infrastructure database release and the directory path. The default value is /u01/app/release_number/grid.

Database Home Location

Sets the Oracle Database release and the directory path. The default value is /u01/app/oracle/product/release_number/dbhome_1.

Software Languages

Defines the languages installed for the database. The default value is English (en).

Diskgroup Layout

Sets the disk group layout. The options are:

  • 80% 20% for DATA and RECO when using external backups.

  • 40% 60% for DATA and RECO when using internal backups.

The disk group layout options with sparse disk group are:

  • 72% 18% 10% for DATA, RECO, and SPARSE when using external backups.

  • 34% 56% 10% for DATA, RECO, and SPARSE when using internal backups.

Note: On X7 systems, you cannot specify any sizes for the DBFS_DG.

Virtual Guest Size

Sets the size of a virtual guest. The options are Small, Medium, and Large.

You can use the sliders to customize the definitions of small, medium, and large for your environment.

Guest Image Version

Sets the image version for virtual guests. The options are default and 12.1.2.*.*. Selecting the default option sets the guest image version to match dom0's image version.

Note: The guest image version needs to be the same as or earlier than dom0's image version.

DBFS DiskGroup

Sets the DBFS disk group name.

Note: This field does not exist for X7 systems.

DATA Disk Group

Sets the DATA disk group name, redundancy and size. The redundancy options are NORMAL and HIGH.

Note: Oracle recommends the use of HIGH redundancy disk groups for mission critical applications.

RECO Disk Group

Sets the RECO name, redundancy and size. The redundancy options are NORMAL and HIGH.

Note: Oracle recommends the use of HIGH redundancy disk groups for mission critical applications.

Sparse Disk Group

Sets the sparse disk group name, redundancy, and size. The redundancy options are NORMAL and HIGH.

Click the Advanced Options button, and then select Enable Sparse Disk Group.

Note: To create a sparse disk group, the version of Grid Infrastructure needs to be 12.1.0.2 BP5 or later.

Database name

Sets the database name.

Block size

Sets the database block size. The default value is 8192.

To use a different block size, select the block size from the list

Database Type

Defines the type of workload that runs on the database.

The options are OLTP for online transaction processing, and DW for data warehouse.

Base Adapter

Sets the physical network for the client network. The default value is client.

Note: Oracle recommends using the default.

Domain

Defined on the Customer Details page.

Start IP

Defined on the Customer Details page.

Pool Size

Defined on the Customer Details page.

Gateway IP

Defined on the Customer Details page.

VLAN ID

Specifies a VLAN tag on a per cluster basis. This is a numeric value between 1 and 4095.

Name Mask

Defined on the Customer Details page.

Start Id

Defined on the Customer Details page.

VIP Name mask

Defined on the Customer Details page.

Start Id

Defined on the Customer Details page.

SCAN Name

Defined on the Customer Details page.

Base Adapter

Sets the backup network. The options are Not in use, and Backup.

Domain

Defined on the Customer Details page.

Start IP

Defined on the Customer Network page.

Pool size

Defined on the Customer Network page.

Name mask

Defined on the Customer Network page.

Start Id

Defined on the Customer Network page.

See Also:

3.2.13.1 Configuring Automatic Cluster File System (ACFS)

Note:

Automatic Cluster File System (ACFS) requires Grid Infrastructure 12.1.0.2 or later.

To configure ACFS during software deployment, perform these steps:

  1. On the "Define Clusters Details" page, click the Advanced Options button.

  2. In the pop-up window, select Enable ACFS Configuration, and click OK.

  3. Click the Configure ACFS button in the Disk Group Details pane, which opens a pop-up window.

  4. Select Enable ACFS for Disk Group.

  5. In the Disk Group dropdown, select the disk group in which you would like to create ACFS.

  6. For ACFS Volume Name, accept the default volume name, or enter a new ACFS volume name.

    The volume name must be between 1 and 11 alphanumeric characters, and must start with an alphabetic character.

  7. For ACFS Volume Size, enter the desired size of the ACFS volume.

  8. For ACFS Mount Point, accept the default mount point, or enter a new ACFS mount point.

3.2.14 Review and Edit SCAN, Client, VIP and Optional Backup Networks

Review and update entries for the clusters and client network, then click Re-Generate Data, and then click Next.

Note:

The domain specified on Customer Details page is used as the domain for all networks. If different domains are used for the client and backup networks, then specify those domains on this page.

3.2.15 Cell Alerting Configuration Page

Cell alert delivery may be configured during or after installation.

Cell alerts can be delivered using Simple Mail Transfer Protocol (SMTP), Simple Network Management Protocol (SNMP), or both. The following table lists the cell alert configuration options.

Table 3-13 Cell Alerting Configuration Page

Cell Alerting Field Description

Enable Email Alerting

Enables cell alerts to be delivered automatically.

Recipients Addresses

Sets the e-mail addresses for the recipients of the cell alerts. Multiple addresses can be entered in the dialog box. The number of e-mail addresses is shown.

SMTP Server

Sets the SMTP e-mail server used to send alert notifications

Example: mail.example.com

Uses SSL

Enables Secure Socket Layer (SSL) security when sending alert notifications.

Port

Sets the SMTP e-mail server port used to send alert notifications

Example: 25 or 465

Name

Sets the SMTP e-mail user name that appears in the alert notifications.

Example: Oracle Exadata Database Machine

Email Address

Sets the SMTP e-mail address that sends alert notifications.

Example: dm01@example.com

Enable SNMP Alerting

Enables using SNMP to deliver alerts.

SNMP Server

Sets the SNMP server host name.

Example: snmp.example.com

Note: Additional SNMP targets may be defined after installation. Refer to Oracle Exadata System Software User's Guide.

Port

Sets the SNMP server port. The default value is 162.

Community

Sets the SNMP server community. The default value is public.

3.2.16 Platinum Configuration Page

Oracle Platinum Service provides enhanced support at no additional cost for qualified engineered systems. This is a connected service and requires Oracle Advanced Support Gateway (OASG) to be provisioned within the environment. The configuration for OASG is defined with the user information that is used by the Platinum Service monitoring agent. The following table lists the Oracle Platinum Service configuration options.

Table 3-14 Platinum Configuration Page.

Platinum Field Description

Capture data for Platinum configuration

Enables collection of Oracle Platinum Service configuration.

Customer Name

Defined on the Customer Details page. This field can be edited.

Note: The customer name must match the My Oracle Support portrait name.

CSI

Sets the hardware customer support identifier (CSI) for the system.

My Oracle Support email

Sets the e-mail address for access to the system CSI.

Use Existing Gateway

Enables use of an existing OASG gateway.

Gateway Machine Description

Describes the gateway system, such as Oracle Exadata Database Machine X4-2.

Platinum Gateway Hostname

Sets the OASG host name. Name format is ct-customer_name-2_digit_number.

Primary IP Address

Sets the primary IP address for OASG.

Subnet Mask

Sets the subnet mask for the OASG primary network.

VPN

Sets the VPN connection type for access to the gateway from Oracle Continuously Connected Network (OCCN). SSL is the default method.

Note: Oracle recommends using Secure Socket Layer (SSL).

Gateway to Exadata Link

Defines the OASG location in the network.

Note: Oracle recommends using DMZ as the connection.

Static Routes

Lists the number of static routes. Click Modify to change the routes for the gateway.

Static Routes: Destination Network

This field is available after clicking Modify.

Defines the remote network for the router. Network format is CIDR format, such as 192.0.2.1/255.

Static Routes: Gateway IP

This field is available after clicking Modify.

Defines the remote network gateway IP address. The address must be in the OASG primary IP subnet.

Gateway machine has an ILOM

Specifies that OASG is an Oracle system with an ILOM service processor.

ILOM IP Address

Sets the ILOM IP address.

Subnet Mask

Sets the ILOM subnet mask.

Gateway IP Address

Sets the OASG ILOM primary subnet gateway.

HTTP Proxy Required

Enables a proxy service for OASG to connect to the required Oracle sites.

Proxy Hostname

Sets the proxy host name used to connect to Oracle sites.

Port

Sets the proxy port number.

HTTP Proxy Requires Authentication

Enables authentication for the proxy network traffic.

Proxy Username

Sets the OASG user name to connect to the proxy. The password is provided by the Oracle engineer during installation.

Agent OS User name

Sets the user name for the Platinum agent. The default name is orarom.

Allow Agent sudo privileges

Allows the Agent OS user sudo privileges. Selecting this option allows Oracle service engineers to collect logs and other information for a service request.

Agent OS Group name

Sets the Platinum group name. The default name is orarom. The messages file on Linux systems is changed to allow the Platinum agent the ability to read the file.

Agent OS Group ID

Assigns the Agent group ID. The default ID is 1010.

Agent OS User home

Sets the home directory for the Platinum agent user.

Agent Software home

Sets the home directory for the software agent.

Agent Port

Sets the port number for the Platinum agent. The default port is 1830.

SNMP Community string

Sets the SNMP trap community string.

3.2.17 Auto Service Request Configuration Page

Auto Service Request (ASR) is designed to automatically open service requests when specific Oracle Exadata Rack hardware faults occur. The following table lists the ASR configuration options.

Table 3-15 Auto Service Request Configuration Page

Auto Service Request Field Description

Enable Auto Service Request

Enables ASR.

ASR Manager Hostname

Sets the ASR server host name.

Note: Oracle recommends a standalone server that has connectivity to the rack.

ASR Technical Contact Name

Sets the technical contact name for the rack.

Technical Contact Email

Sets the e-mail address of the technical contact for the rack.

My Oracle Support Account Name

Sets the My Oracle Support account name.

HTTP Proxy used in upload to ASR

Enables an HTTP proxy to upload to ASR.

HTTP Proxy Host

Sets the proxy server host name.

Proxy Port

Sets the HTTP proxy server port number. The default is 80.

HTTP Proxy requires authentication

Enables HTTP proxy server authentication.

HTTP Proxy User

Sets the proxy server user name.

3.2.18 Oracle Configuration Manager Configuration Page

Oracle Configuration Manager is used to collect configuration information and upload it to the Oracle repository. The following table lists the Oracle Configuration Manager configuration options.

Table 3-16 Oracle Configuration Manager Configuration Page

Oracle Configuration Manager Field Description

Enable Oracle Configuration Manager

Enables Oracle Configuration Manager to collect configuration information.

Receive updates via MOS

Enables My Oracle Support updates to be received automatically.

MOS Email Address

Sets the My Oracle Support address to receive My Oracle Support updates.

Access Oracle Configuration Manager via Support Hub

Enables Support Hub to access Oracle Configuration Manager.

Oracle Support Hub allows Oracle Configuration Manager instances to connect to a single internal port (the Support Hub), and upload configuration data. This eliminates the need for each individual Oracle Configuration Manager instance in the database servers to access the Internet.

Support Hub Hostname

Sets the Support Hub server host name.

Hub User name

Sets the Support Hub operating system user name.

HTTP Proxy used in upload to Oracle Configuration Manager

Enables an HTTP proxy to upload configuration information to the Oracle repository.

HTTP Proxy Host

Enables the HTTP proxy server to connect to Oracle. The proxy server may be between the following:

  • Database servers and Oracle (applicable when you do not have Oracle Support Hub)

  • Database servers and Support Hub (applicable when you have only Oracle Support Hub)

  • Support Hub and Oracle

If passwords are needed, then provide them during installation.

Example:

[proxy_user@]proxy_host[:proxy_port]

The proxy_host and proxy_port entries are optional.

Proxy Port

Sets the HTTP proxy server port number. The default is 80.

HTTP Proxy requires authentication

Enables HTTP proxy authentication.

HTTP Proxy User

Sets the HTTP proxy server user name.

3.2.19 Grid Control Agent Configuration Page

Oracle Enterprise Manager Grid Control is used to monitor Oracle Exadata Rack. Oracle Enterprise Manager Grid Control installs agents on the database servers and points the agents to an existing Oracle Enterprise Manager Grid Control environment, or installs a new Oracle Enterprise Manager Grid Control infrastructure on a separate host.

Table 3-17 lists the Oracle Enterprise Manager Grid Control configuration options.

Table 3-17 Oracle Enterprise Manager Grid Control Configuration Page

Oracle Enterprise Manager Grid Control Field Description

Enable Oracle Enterprise Manager Grid Control Agent

Enables Oracle Enterprise Manager Grid Control to monitor the rack.

EM Home Base Location

Sets the base directory for the agents installed on the database servers.

OMS Hostname

Sets the host name for the Oracle Enterprise Manager Grid Control repository.

OMS HTTPS Upload Port

Sets the port Oracle Enterprise Manager Grid Control agent should use to upload information.

Note:

The default is 4900.

3.3 OEDA Command Line Interface

When you run the oedacli program, it starts the OEDA command line interface.

3.3.1 About the OEDA Command Line Interface

The primary goal of oedacli is to assist in completing various Exadata life cycle management tasks.

The OEDA command-line interface is a new interface that allows you to update an existing es.xml file. These updates are called Actions. An Action is a single atomic task. You can use the command line interface to perform any of the following tasks:

  • Add node to or remove node from a Virtual Cluster on Exadata

  • Add database home to or remove database home from physical cluster

  • Add or remove Storage cell

  • Resize Oracle ASM disk groups

  • Add or remove additional Databases

  • Add or remove additional database homes to an Oracle VM cluster

An Action can have many sub commands, however most actions are single commands. Examples of multi-command steps are - CLONE GUEST and CLONE CELL

oedacli has two operating modes:

  • Edit mode

    • Used against an es.xml file before you run the install.sh command steps

    • Used to edit an XML file, for example to add a second Database Home, then save the XML file

    • Can be used as a logical XML editor for the es model prior to deployment

  • Deploy mode

    • Used to edit an es.xml file after you have run the install.sh command steps

    • Can be used to Clone Oracle VM Guests or grow or shrink Oracle ASM Disk groups

    • Has a smaller list of supported changes than Edit mode

    • Can be used as a logical XML editor and deployment tool after the initial deployment

Edit mode workflow

  1. When the command line interface starts, it has no target es.xml file to work on, so you first load an es.xml file.

    LOAD FILE name=es.xml
    
  2. Modify an in-memory version of the es.xml. Specify the additional actions to perform during deployment. For example, to clone an Oracle VM guest to a new guest:

    clone guest srcname=asd
    set privnet name1='test08adm01-priv1',ip1='192.168.216.102',name2='testadm01-priv2',ip2='192.168.216.103'
    set parent name='test08adm01a'
    set adminnet name='test08adm01vm02',ip='10.128.218.70'
    set clientnet name='test08client01vm02',ip='10.128.196.63'
    set vipnet name='test08client01vm02-vip',ip='10.128.196.71'
    
  3. After you have provided all the commands for an action, save the action to a list of actions to be processed within the command line interface. At this point, the data in the es.xml file is not yet updated.

    SAVE ACTION
    
  4. Merge the actions into the main body of the in-memory copy of the es.xml using the FORCE keyword.

    MERGE ACTIONS FORCE
    
  5. Save the memory copy of the es.xml, overwriting the input file or writing to a new file that you specify.

    SAVE FILE [name=new_es.xml]
    

Deploy mode workflow

  1. When the command line interface starts, it has no target es.xml file to work on, so you first load an es.xml file.

    LOAD FILE name=es.xml
    
  2. Modify an in-memory version of the es.xml. Specify the actions to perform.

  3. After you have provided all the commands for an action, save the action to a list of actions to be processed within the command line interface. At this point, the data in the es.xml file is not yet updated.

    SAVE ACTION
    
  4. Merge the actions into the main body of the in-memory copy of the es.xml.

    MERGE ACTIONS
    
  5. Deploy the actions into the main body of the es.xml file. This step will perform the specified actions such as creating the new Oracle VM guest.

    DEPLOY ACTIONS
    
  6. Save the memory copy of the es.xml, overwriting the input file or writing to a new file that you specify.

    SAVE FILE [name=new_es.xml]
    

3.3.2 Starting the OEDACLI Utility

Starting with August 2017 Release of Oracle Exadata Deployment Assistant (OEDA), a command-line utility — oedacli — can be used for various routine tasks on Exadata.

Prerequisites

To use oedacli, you must meet the following requirements:

  • Download the August 2017 release or later of OEDA. The August 2017 release of OEDA is only supported on Oracle Linux.

  • Have the original OEDA configuration XML file used for deployment

  • Use the default password on the nodes in the cluster (for the root, oracle and grid users)

Note:

If your environment does not use the default passwords for the specified users, then refer to My Oracle Support Doc ID 2163751.1.

File Path

The directory that contains the unzipped files from the OEDA download. For example /u01/joc/linux-x64.

Syntax

./oedacli

Usage Notes

To display the help output, use one of the following:

  • HELP

  • HELP command name

3.3.2.1 Displaying Help Output for OEDACLI

You can display syntax help for the OEDACLI utility using the HELP command.

Example 3-1 Help Output for OEDACLI

This example shows the help output listing the available objects and command for the OEDACLI 18c (18.1.0) release:

oedacli> HELP
 HELP [topic]
   Available Objects:
 ACFSVOLUME
        LIST ACFSVOLUMES
 CELL
        LIST CELLS
 CLUSTER
        LIST CLUSTERS
 DISKGROUP
        LIST DISKGROUPS
 DATABASE
        LIST DATABASES
 DATABASEHOME
        LIST DATABASEHOMES
 DOM0
        LIST DOM0S
 GUEST
        CLONE GUEST
        DELETE GUEST
        LIST GUESTS
 ILOM
        LIST ILOMS
 MACHINE
        LIST MACHINES
 NETWORK
        LIST NETWORKS
 SCAN
        LIST SCANS
 SWITCH
        LIST SWITCHES
 VIP
        LIST VIPS
 CLI COMMANDS
        LOAD FILE
        SAVE FILE
        SAVE FILES
        LIST XMLACTIONS
        SAVE ACTION
        MERGE ACTIONS
        DEPLOY ACTIONS

3.3.2.2 Displaying Help Output for an OEDACLI Command

This example shows the help output listing the OEDACLI ALTER DATABASE command.

Example 3-2 Help Output for the OEDACLI ALTER DATABASE command

This example shows how to display the syntax for the ALTER DATABASE command of OEDACLI. The help output is shown for the 18c (18.1.0) release.

oedacli> HELP ALTER DATABASE
 Usage:
 ALTER DATABASE
  BLOCKSIZE = <blocksize> |
  CHARSET = <characterset> |
  DATADG = <datadg> |
  DBLANG = <dblang> |
  DBNAME = <dbname> |
  DBTEMPLATE = <dbtemplate> |
  DBTYPE = <dbtype> |
  HOSTNAMES = <hostnames> |
  RECODG = <recodg>
 WHERE
  ID = <databaseid> |
  CLUSTERNUMBER = <clusternumber> DATABASENAME = <databasename> |
  CLUSTERNAME = <clustername> DATABASENAME = <databasename> |
  CLUSTERID = <clusterid> DATABASENAME = <databasename>
 
 Purpose:
   Alters an existing database
 Arguments:
   <blocksize>    :  Default: 8192,  not required for PDB
   <characterset> :  Default: AL32UTF8,  not required for PDB
   <datadg>       : *The DATA diskgroup, not required for PDB
   <dblang>       :  Default: all_langs, not required for PDB
   <dbname>       : *Database name
   <dbtemplate>   :  Default: ADMIN, otherwise ADMIN or DW, not required for PDB
   <dbtype>       :  Default: normal DB, otherwise CDB or PDB
   <hostnames>    :  Default:  list of nodes from db home
   <recodg>       : *The RECO diskgroup, not required for PDB
 Where:
   <databaseid>    : The es xml id of the database
   <clusternumber> : The cluster number in the es xml, starting at 1
   <clustername>   : The name of the cluster
   <clusterid>     : The es xml id of the cluster
   <databasename>  : The name of the database in the cluster

3.3.3 OEDACLI Command Reference

These OEDACLI commands are arranged by the object they act upon.

3.3.3.1 OEDACLI Commands

These commands are used to interact with OEDACLI, to load and save files, and to merge, save, and deploy actions.
3.3.3.1.1 LOAD FILE
Use this command to load an engineered system XML file (es.xml) into OEDACLI memory for editing.

Syntax

 LOAD FILE NAME=filename

Arguments

  • NAME : Specifies the name of an existing engineered system XML file

Example 3-3 Loading a File into OEDACLI for Editing

oedacli> LOAD FILE NAME=Oracle-test12.xml 
SUCCESS - file loaded OK 
Customer : testadm01 - Oracle
3.3.3.1.2 SAVE ACTION
Use this command to save the current action to engineered system XML memory copy.

Syntax

SAVE ACTION [FORCE]

Arguments

Specify FORCE if the action should be auto-merged into the engineered system model.

Note:

The engineered system configuration should be saved as a file using a subsequent SAVE FILE command.
3.3.3.1.3 MERGE ACTIONS
Use this command to merge the current actions into the other actions in the Engineered System model.

Syntax

MERGE ACTIONS [FORCE]

Arguments

Specify FORCE if you do not want this action to be processed by a DEPLOY ACTIONS command.

3.3.3.1.4 DEPLOY ACTIONS
Use this command to execute all actions from the Actions section of the engineered systems XML file.

Syntax

DEPLOY ACTIONS

Example 3-4 Deploying the Actions to Add a Database

oedacli> DEPLOY ACTIONS 
Deploying Action ID : 4 add database dbname='testdb' DATADG='DATAC1' RECODG='
RECOC1' where DBHOMEID='c0_databaseHome' 
Deploying ADD DATABASE 
Running datapatch on database 'testdb' 
Done... 
Done
3.3.3.1.5 SAVE FILE
Use this command to save a current set of actions to a new engineered system XML file.

Syntax

SAVE FILE [ NAME=filename ]

Arguments

The optional argument, NAME, is used to specify the name of a new engineered system XML file. If you do not specify the NAME argument, then this command overwrites the source file.

3.3.3.1.6 SAVE FILES
Use this command to generate a new set of configuration files from OEDA.

Syntax

SAVE FILES LOCATION = dirname

Arguments

The LOCATION argument specifies the directory in which the new file set will be created.

Usage Notes

If the specified directory does not exist, it will be created.

3.3.3.1.7 LIST XMLACTIONS
This command lists the current actions created by OEDACLI.

Syntax

LIST XMLACTIONS

3.3.3.2 ACFSVOLUME

You can add, alter, delete, or list Oracle ACFS volumes.
3.3.3.2.1 ADD ACFSVOLUME
This command adds Oracle ASM Cluster File System (Oracle ACFS) volumes.

Syntax

ADD ACFSVOLUME
   VOLUMENAME = volume_name |
   VOLUMESIZE = volume_size |
   MOUNTPATH = mountpath 
WHERE
 DISKGROUPID = diskgroup_id |
 CLUSTERNUMBER = cluster_number DISKGROUPNAME = diskgroup_name |
 CLUSTERNAME = cluster_name DISKGROUPNAME diskgroup_name |
 CLUSTERID = cluster_id DISKGROUPNAME = diskgroup_name 

Arguments

You can specify the following attributes for the new Oracle ACFS volume:

  • VOLUMENAME : Specifies a unique name for the new volume

  • VOLUMESIZE : A number that specifies the size of the new volume in GB

  • MOUNTPATH : Specifies the file system mount path for the new volume

The following arguments are available in the WHERE clause:

  • DISKGROUPID : Specifies the es.xml ID for the container disk group

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • DISKGROUPNAME : Specifies the name of the container disk group

3.3.3.2.2 ALTER ACFSVOLUME
This command alters an existing Oracle ASM Cluster File System (Oracle ACFS) volume.

Syntax

ALTER ACFSVOLUME
   VOLUMENAME = volume_name |
   VOLUMESIZE = volume_size |
   MOUNTPATH = mountpath 
WHERE
 ID = acfs_volume_id |
 DISKGROUPID = diskgroup_id VOLUMENAME = volume_name|
 CLUSTERNUMBER = cluster_number DISKGROUPNAME = diskgroup_name VOLUMENAME = volume_name|
 CLUSTERNAME = cluster_name DISKGROUPNAME diskgroup_name VOLUMENAME = volume_name|
 CLUSTERID = cluster_id DISKGROUPNAME = diskgroup_name VOLUMENAME = volume_name

Arguments

You can modify the following attributes of the Oracle ACFS volume:

  • VOLUMENAME : Specifies a new, unique volume name

  • VOLUMESIZE : A number that specifies the new size of the volume in GB

  • MOUNTPATH : Specifies the new file system mount path for the volume

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID for an existing Oracle ACFS volume

  • DISKGROUPID : Specifies the es.xml ID for the container disk group

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • DISKGROUPNAME : Specifies the name of the container disk group

  • VOLUMENAME : Specifies the name of the existing Oracle ACFS volume

3.3.3.2.3 DELETE ACFSVOLUME
This command deletes an existing Oracle ASM Cluster File System (Oracle ACFS) volume.

Syntax

DELETE ACFSVOLUME
WHERE
 ID = acfs_volume_id |
 DISKGROUPID = diskgroup_id VOLUMENAME = volume_name|
 CLUSTERNUMBER = cluster_number DISKGROUPNAME = diskgroup_name VOLUMENAME = volume_name|
 CLUSTERNAME = cluster_name DISKGROUPNAME diskgroup_name VOLUMENAME = volume_name|
 CLUSTERID = cluster_id DISKGROUPNAME = diskgroup_name VOLUMENAME = volume_name

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID for the Oracle ACFS volume

  • DISKGROUPID : Specifies the es.xml ID for the container disk group

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • DISKGROUPNAME : Specifies the name of the container disk group

  • VOLUMENAME : Specifies the name of the existing Oracle ACFS volume

3.3.3.2.4 LIST ACFSVOLUME
This command lists the Oracle ASM Cluster File System (Oracle ACFS) volumes.

Syntax

LIST ACFSVOLUMES
WHERE
 ID = id |
 DISKGROUPID = diskgroup_id |
 CLUSTERNUMBER = cluster_number [DISKGROUPNAME = diskgroup_name] |
 CLUSTERNAME = cluster_name [DISKGROUPNAME diskgroup_name] |
 CLUSTERID = cluster_id [DISKGROUPNAME = diskgroup_name]

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID for the Oracle ACFS volume

  • DISKGROUPID : Specifies the es.xml ID for the container disk group

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • DISKGROUPNAME : Specifies the name of the container disk group

Usage Notes

There is no WHERE clause that will list all the Oracle ACFS volumes in the es.xml file.

Examples

(Optional) List and briefly describe the examples for executing the command here.

Example 3-5 Example Title

(Optional) Describe the example here.

Enter the example code here.

Example 3-6 Example Title

(Optional) Describe the example here.

Enter the example code here.

3.3.3.3 CELL

You can clone, delete, or list Oracle Exadata storage cells.
3.3.3.3.1 CLONE CELL
This command clones an existing storage cell.

Syntax

CLONE CELL SRCNAME = source_cell
  SET ADMINNET NAME=admin_name,IP=IP_admin
  SET PRIVNET NAME1=priv_name_1,IP1=priv_ip1,NAME2=priv_name_2,IP2=priv_ip2
  SET ILOMNET NAME=ilom_name,IP=ilom_ip
  SET RACK NUM=rack_number,ULOC=ulocation

Arguments

SRCNAME is used to specify the name of an existing cell from which the new cell is derived.

The following arguments are available in the SET clauses:

  • ADMINNET : Specifies the DNS name (admin_name) with an optional domain name and the IP address to be used for the admin network.

  • PRIVNET : Specifies the name with an optional domain name and the IP address to be used for the first and second private networks.

  • ILOMNET : Specifies the DNS name with an optional domain name and the IP address to be used for the ILOM network.

  • RACK : Specifies the rack number in a multi-rack configuration, where 1 is the first rack, and the physical Ulocation (slot) of the cell in that rack.

3.3.3.3.2 DELETE CELL
This command deletes an existing storage cell.

Syntax

DELETE CELL WHERE SRCNAME = cell_host_name

Arguments

SRCNAME is used to specify the host name of an existing cell that you want to remove.

3.3.3.3.3 LIST CELLS
This command lists the storage cells.

Syntax

LIST CELLS

3.3.3.4 CLUSTER

You can alter or list the Oracle RAC Clusters on the Oracle Exadata Database Machine.
3.3.3.4.1 ALTER CLUSTER
This command alters attributes for an existing Oracle RAC Cluster.

Syntax

ALTER CLUSTER { CLUSTERNAME = cluster_name | GIVERSION = grid_version |
   GIHOMELOC = grid_home_location | INVLOC = inventory_location|
   BASEDIR = oracle_base_directory |  PATCHLIST = patch_list }
WHERE
   CLUSTERNUMBER = cluster_number |
   CLUSTERNAME = cluster_name |
   CLUSTERID = cluster_id 

Arguments

You can modify the following attributes of the Oracle RAC Cluster:

  • CLUSTERNAME : Specifies a new, unique name for the cluster

  • GIVERSION : Specifies the clusterware version, including the bundle patch, for example 12.1.0.2.170418

  • GIHOMELOC : Specifies a new path for the Grid home

  • INVLOC : Specifies a new path for the inventory

  • BASEDIR : Specifies a new path for the Oracle base directory

  • PATCHLIST : Specifies a full list of patches separated by commas and enclosed in single quotes. By default, this is derived from the bundle patch specified by GIVERSION.

The following arguments are available in the WHERE clause:

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

3.3.3.4.2 LIST CLUSTERS
This command lists the existing Oracle RAC clusters.

Syntax

LIST CLUSTERS
 [ WHERE
   CLUSTERNUMBER = cluster_number |
   CLUSTERNAME = cluster_name |
   CLUSTERID = cluster_id ]

Arguments

The following arguments are available in the WHERE clause:

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

Usage Notes

The WHERE clause is optional.

3.3.3.5 DISKGROUP

You can add, alter, delete, or list the Oracle ASM disk groups.
3.3.3.5.1 ADD DISKGROUP
This command adds an Oracle ASM disk group.

Syntax

ADD DISKGROUP 
   [ ACFSNAME=acfs_name ]
   [ ACFSPATH=acfs_path ]
   [ ACFSSIZE=acfs_size ]
   [ CELLLIST='cell_list' ]
   DISKGROUPNAME=diskgroup_name 
   DISKGROUPSIZE=diskgroup_size
   [ OCRVOTE=ocr_voting_disks_included ] 
   [ QUORUMDISK=quorum_disks_included ]
   REDUNDANCY=redundancy_level
   SLICESIZE=slice_size 
   [ SPARSE=sparse ]
   [ SPARSEVIRTUALSIZE=sparse_virtual_size ]
   [ TYPE = diskgroup_type [ DATABASENAME = database_name ]]
WHERE
   CLUSTERNUMBER = cluster_number |
   CLUSTERNAME = cluster_name |
   CLUSTERID = cluster_id 

Arguments

You can specify the following attributes for the new Oracle ASM disk group:

  • ACFSNAME : Specifies the name for the Oracle ACFS volume on this diskgroup

  • ACFSPATH : Specifies the path for the Oracle ACFS file system

  • ACFSSIZE : Specifies the size for the Oracle ACFS volume on this diskgroup

  • CELLLIST : A comma separated list of cells for this disk group, enclosed in single quotes

  • DISKGROUPNAME : (Mandatory) Specifies the name of the disk group

  • DISKGROUPSIZE : (Mandatory) Specifies the size of the disk group

  • OCRVOTE : A boolean variable, where TRUE indicates the disk group should store the OCR and voting disks for the cluster.

  • QUORUMDISK : A boolean variable, where TRUE indicates the disk group requires a quorum

  • REDUNDANCY : (Mandatory) Specifies the redundancy level for the disk group. The accepted values are NORMAL or HIGH.

  • SLICESIZE : (Mandatory) Specifies the slice size on disk for each grid disk for this disk group.

  • SPARSE : A boolean variable, where TRUE indicates this should be sparse disk group.

  • SPARSEVIRTUALSIZE : Specifies the sparse virtual size.

  • TYPE : Specifies the diskgroup type, which can be DATA, RECO, DBFS or OTHER. The default value is OTHER. If you want the database to use this disk group, then the type must be set to DATA or RECO.

  • DATABASENAME : Specifies the name of the target database for disk groups of type DATA or RECO.

The following arguments are available in the WHERE clause:

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

3.3.3.5.2 ALTER DISKGROUP
This command alters attributes for an existing Oracle ASM disk group.

Syntax

ALTER DISKGROUP {
   ACFSNAME=acfs_name| 
   ACFSPATH=acfs_path |
   ACFSSIZE=acfs_size |
   CELLLIST='cell_list' |
   DISKGROUPNAME=diskgroup_name | 
   DISKGROUPSIZE=diskgroup_size |
   OCRVOTE=ocr_voting_disks_included | 
   QUORUMDISK=quorum_disks_included |
   REDUNDANCY=redundancy_level |
   SLICESIZE=slice_size |
   SPARSE=sparse |
   SPARSEVIRTUALSIZE=sparse_virtual_size }
WHERE {
   ID = diskgroup_id|
   CLUSTERNUMBER = cluster_number DISKGROUPNAME = diskgroup_name|
   CLUSTERNAME = cluster_name DISKGROUPNAME = diskgroup_name|
   CLUSTERID = cluster_id DISKGROUPNAME = diskgroup_name }

Arguments

You can modify the following attributes of an Oracle ASM disk group:

  • ACFSNAME : Specifies a new name for the Oracle ACFS volume on this diskgroup

  • ACFSPATH : Specifies the new path for the Oracle ACFS file system

  • ACFSSIZE : Specifies a new size for the Oracle ACFS volume on this diskgroup

  • CELLLIST : A comma separated list of cells for this disk group, enclosed in single quotes

  • DISKGROUPNAME : Specifies a new name for the disk group

  • DISKGROUPSIZE : Specifies a new size for the disk group

  • OCRVOTE : A boolean variable, where TRUE indicates the disk group should store the OCR and voting disks for the cluster.

  • QUORUMDISK : A boolean variable, where TRUE indicates the disk group requires a quorum

  • REDUNDANCY : Specifies the redundancy level for the disk group. The accepted values are NORMAL or HIGH.

  • SLICESIZE : Specifies the slice size on disk for each grid disk for this disk group.

  • SPARSE : A boolean variable, where TRUE indicates this should be sparse disk group.

  • SPARSEVIRTUALSIZE : Specifies the sparse virtual size.

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID for the disk group

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • DISKGROUPNAME : Specifies the name of the disk group

Usage Notes

If you modify the redundancy, the volume size will be maintained, however the slice size will be recalculated.

Example 3-7 Resizing an Oracle ASM Diskgroup Using OEDACLI

This example shows how to resize an existing Oracle ASM disk group using OEDACLI.

  1. Load the OEDA XML configuration file.

    oedacli> LOAD FILE NAME=Oracle-test.xml 
    SUCCESS - file loaded OK 
    Customer : ora07adm01 - Oracle
    
  2. Use the command LIST DISKGROUPS to view the disk group details.

    oedacli> LIST DISKGROUPS
    version : "PhysicalLayoutLegacy" 
    diskGroupName : "DBFS_DG" 
    redundancy : "NORMAL" 
    sliceSize : "default" 
    machines : 
    machine : 
    ... 
    ... 
    cellDisks : "ALL" 
    diskGroupSize : "436G" 
    ocrVote : "true" 
    quorumDisk : "false" 
    id : "c0_dbfsdg" 
    version : "PhysicalLayoutLegacy" 
    diskGroupName : "DATAC1" 
    redundancy : "NORMAL" 
    sliceSize : "2953G" 
    machines : 
    .. 
    .. 
    cellDisks : "ALL" 
    diskGroupSize : "53154G" 
    ocrVote : "false" 
    quorumDisk : "false" 
    id : "c0_datadg" 
    version : "PhysicalLayoutLegacy" 
    diskGroupName : "RECOC1" 
    redundancy : "NORMAL" 
    sliceSize : "ALL" 
    machines : 
    .. 
    .. 
    cellDisks : "ALL" 
    diskGroupSize : "13284G" 
    ocrVote : "false" 
    quorumDisk : "false" 
    id : "c0_recodg"
    
  3. Create an action for resizing the disk group.

    oedacli> ALTER DISKGROUP DISKGROUPSIZE='2500G' WHERE CLUSTERNUMBER=1 DISKGROUPN
    AME='DATAC1'
    
  4. Save the action.

    oedacli> SAVE ACTION
    
  5. Merge all actions.

    oedacli> MERGE ACTIONS
    processMerge 
    processMergeActions 
    Merging Action : alter diskgroup diskgroupsize='2500G' where diskgroupname='DAT
    AC1' clusternumber=1 
    Merging ALTER DISKGROUP
    Action Validated and Merged OK
    
  6. Deploy the actions.

    oedacli> DEPLOY ACTIONS 
    Deploying Action ID : 3 alter diskgroup diskgroupsize='2500G' where diskgroupna
    me='DATAC1' 
    Deploying ALTER DISKGROUP 
    Deploying Action ID : 4 alter diskgroup diskgroupsize='2500G' where diskgroupna
    me='DATAC1' clusternumber=1 
    Deploying ALTER DISKGROUP 
    Validating ASM Disk status.. 
    Disks in ASM Disk Group DATAC1 have valid status 
    Shrinking Disk Group size to 2500 GB 
    Resizing ASM Disk Group.. 
    Checking Reblance operations in disk group DATAC1 
    Rebalance operations completed in disk group DATAC1 
    Original Grid Disk Size 2953 GB, new size 138 GB on node1celadm02.us.oracle.com 
    Original Grid Disk Size 2953 GB, new size 138 GB on node1celadm03.us.oracle.com 
    Original Grid Disk Size 2953 GB, new size 138 GB on node1celadm01.us.oracle.com 
    Updated/New Disk Group size 2484 GB, original size 53154 GB. 
    Done... 
    Done
    
3.3.3.5.3 ALTER DISKGROUPS
This command alters disk group sizing attributes for existing Oracle ASM disk groups.

Syntax

ALTER DISKGROUPS 
   DATASPLIT=data_split_percent 
   RECOSPLIT=reco_split_percent
   DATAREDUNDANCY=data_redundancy_level
   RECOREDUNDANCY=reco_redundancy_level 
   SPLITDISK=percent_of_cell_disk
WHERE
   DATADG = data_diskgroup
   RECODG = reco_diskgroup 
   CLUSTERNAME = cluster_name | CLUSTERNUMBER = cluster_number | 
      CLUSTERID = cluster_id 

Arguments

You can modify the following sizing attributes of the DATA and RECO Oracle ASM disk groups:

  • DATASPLIT : Specifies a percentage of the Oracle ASM volume allocated to the DATA disk group

  • RECOSPLIT : Specifies a percentage of the Oracle ASM volume allocated to the RECO disk group

  • DATAREDUNDANCY : Specifies the redundancy level for the DATA disk group. The accepted values are NORMAL or HIGH.

  • RECOREDUNDANCY : Specifies the redundancy level for the RECO disk group. The accepted values are NORMAL or HIGH.

  • SPLITDISK : Specifies the percentage of the cell disk to allocate to the DATA and RECO disk groups. The specified value must be less an integer between 1 and 100.

The following arguments are available in the WHERE clause:

  • DATADG : Specifies the name of the DATA disk group in the cluster

  • RECODG : Specifies the name of the RECO disk group in the cluster

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

3.3.3.5.4 DELETE DISKGROUP
This command deletes an existing Oracle ASM disk group.

Syntax

DELETE DISKGROUP 
WHERE
   ID = diskgroup_id|
   CLUSTERNUMBER = cluster_number DISKGROUPNAME = diskgroup_name|
   CLUSTERNAME = cluster_name DISKGROUPNAME = diskgroup_name|
   CLUSTERID = cluster_id DISKGROUPNAME = diskgroup_name

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID for the disk group

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • DISKGROUPNAME : Specifies the name of the disk group

3.3.3.5.5 LIST DISKGROUPS
This command lists the existing Oracle ASM disk groups.

Syntax

LIST DISKGROUPS 
[ WHERE
   ID = diskgroup_id|
   CLUSTERNUMBER = cluster_number |
   CLUSTERNAME = cluster_name |
   CLUSTERID = cluster_id ]

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID for the disk group

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • DISKGROUPNAME : Specifies the name of the disk group

3.3.3.6 DATABASE

You can add, alter, delete, or list the Oracle databases.
3.3.3.6.1 ADD DATABASE
This command adds an Oracle database, or a CDB or PDB to an existing CDB.

Syntax

ADD DATABASE 
   [ BLOCKSIZE = blocksize ]
   [ CHARSET = database_character_set
   DATADG = data_diskgroup
   [ DBLANG = database_language ]
   DBNAME = database_name
   [ DBTEMPLATE = database_template ] 
   [ DBTYPE = database_type ]
   [ HOSTNAMES = 'host_names' ] 
   RECODG = reco_diskgroup
WHERE
   { DBHOMEID = database_home_id |
   CLUSTERNUMBER = cluster_number DBHOMELOC = database_home_location |
   CLUSTERNAME = cluster_name DBHOMELOC = database_home_location |
   CLUSTERID = cluster_id DBHOMELOC = database_home_location |
   CLUSTERNUMBER = cluster_number CDBNAME = container_database_name |
   CLUSTERNAME = cluster_name CDBNAME = container_database_name |
   CLUSTERID = cluster_id CDBNAME = container_database_name }

Arguments

You can specify the following attributes for the new Oracle database:

  • BLOCKSIZE : Specifies the block size for the new database. The default value is 8192. This argument is not required for pluggable databases.

  • CHARSET : Specifies the character set to use for the new database. The default value is AL32UTF8. This argument is not required for pluggable databases.

  • DATADG : (Mandatory) Specifies the name of the DATA disk group for the new database. This argument is not required for pluggable databases.

  • DBLANG : Specifies the language to use for the new database. The default value is all_langs. This argument is not required for pluggable databases.

  • DBNAME : (Mandatory) Specifies the name of the new database.

  • DBTEMPLATE : Specifies the template to use when creating the new database, ADMIN or DW. The default value is ADMIN. This argument is not required for pluggable databases.

  • DBTYPE : Specifies the type of database to create. The accepted values are normal DB, CDB, or PDB. The default value is normal DB.

  • HOSTNAMES : Specifies a comma-separated list of host names on which the database should run. The default value is the list of nodes registered with the database home.

  • RECODG : (Mandatory) Specifies the name of the RECO disk group for the new database. This argument is not required for pluggable databases.

The following arguments are available in the WHERE clause:

  • DBHOMEID : Specifies the es.xml ID of the database home.

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • DBHOMELOCATION : Specifies the path for the target database home.

  • CDBNAME : Specifies the database name for the container database. This argument is required only when DBTYPE is set to PDB.

Example 3-8 Adding a New Oracle Database Using OEDACLI

This example shows how to add a new database to the configuration.

  1. Load the OEDA XML configuration file.

    oedacli> LOAD FILE NAME=Oracle-test.xml 
    SUCCESS - file loaded OK 
    Customer : ora07adm01 - Oracle
    
  2. Use the command LIST DATABASEHOMES to identify the databasehome_id associated with the target database home. This database home will be used to create the new database.

    oedacli> LIST DATABASEHOMES
    version : "CloneInstall" 
    cluster : 
    id : "c0_clusterHome" 
    databaseHomeName : "c0_DbHome_0" 
    databaseSwOwner : "c0_oracle" 
    databaseVersion : "12.2.0.1.170718" 
    databaseHomeLoc : "/u01/app/oracle/product/12.2.0.1/dbhome_1" 
    inventoryLocation : "/u01/app/oraInventory" 
    language : "all_langs" 
    machines : 
    machine : ... 
    ... 
    patches : 
    patch : 
    patchNumber : "26133434" 
    basedir : "/u01/app/oracle" 
    useZfs : "false" 
    id : "c0_databaseHome1"
    
  3. Create an action for creating the new database. You must provide a name for the new database, and the names of the DATA and RECO disk groups that the new database should use. Also, use the ID retrieved in the previous step to specify the Oracle Home in which to create this database.

    oedacli> ADD DATABASE DBNAME='testdb' DATADG='DATAC1' RECODG='RECOC1' 
    WHERE DBHOMEID='c0_databaseHome'
    
  4. Save the action.

    oedacli> SAVE ACTION
    
  5. Merge all actions.

    oedacli> MERGE ACTIONS
    processMerge 
    processMergeActions 
    Merging Action : add database dbname='testdb' DATADG='DATAC1' RECODG='RECOC1' 
    where DBHOMEID='c0_databaseHome' 
    Merging ADD DATABASE 
    Action Validated and Merged OK
    
  6. Save the action to a new Engineered Systems XML configuration file.

    oedacli> SAVE FILE NAME ='cli-test-2databases.xml' 
    File : cli-test-2databases.xml saved OK
    
  7. Deploy the actions.

    oedacli> DEPLOY ACTIONS 
    Deploying Action ID : 4 add database dbname='testdb' DATADG='DATAC1' RECODG='
    RECOC1' where DBHOMEID='c0_databaseHome' 
    Deploying ADD DATABASE 
    Running datapatch on database 'testdb' 
    Done... 
    Done
    
3.3.3.6.2 ALTER DATABASE
This command alters an existing Oracle database.

Syntax

ALTER DATABASE 
   [ BLOCKSIZE = blocksize ]
   [ CHARSET = database_character_set
   DATADG = data_diskgroup
   [ DBLANG = database_language ]
   DBNAME = database_name
   [ DBTEMPLATE = database_template ] 
   [ DBTYPE = database_type ]
   [ HOSTNAMES = 'host_names' ] 
   RECODG = reco_diskgroup
WHERE
   ID = database_id |
   CLUSTERNUMBER = cluster_number DATABASENAME = database_name |
   CLUSTERNAME = cluster_name DATABASENAME = database_name |
   CLUSTERID = cluster_id DATABASENAME = database_name 

Arguments

You can modify the following attributes for the Oracle database:

  • BLOCKSIZE : Specifies the new block size for the database. The default value is 8192. This argument is not required for pluggable databases.

  • CHARSET : Specifies the new character set to use for the database. The default value is AL32UTF8. This argument is not required for pluggable databases.

  • DATADG : (Mandatory) Specifies the name of the DATA disk group for the database. This argument is not required for pluggable databases.

  • DBLANG : Specifies the new language to use for the database. The default value is all_langs. This argument is not required for pluggable databases.

  • DBNAME : (Mandatory) Specifies the name of the database.

  • DBTEMPLATE : Specifies the template to use when creating the database, ADMIN or DW. The default value is ADMIN. This argument is not required for pluggable databases.

  • DBTYPE : Specifies the type of database to create. The accepted values are normal DB, CDB, or PDB. The default value is normal DB.

  • HOSTNAMES : Specifies a comma-separated list of host names on which the database should be created. The default value is the list of nodes registered with the database home.

  • RECODG : (Mandatory) Specifies the name of the RECO disk group for the database. This argument is not required for pluggable databases.

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID of the database

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • DATABASENAME : Specifies the name of the database in the cluster

3.3.3.6.3 DELETE DATABASE
This command deletes an existing Oracle database.

Syntax

DELETE DATABASE 
WHERE
   ID = database_id |
   CLUSTERNUMBER = cluster_number DATABASENAME = database_name |
   CLUSTERNAME = cluster_name DATABASENAME = database_name |
   CLUSTERID = cluster_id DATABASENAME = database_name 

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID of the database

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • DATABASENAME : Specifies the name of the database in the cluster

Example 3-9 Deleting an Oracle Database Using OEDACLI

This example shows how to delete an existing database from the configuration.

  1. Load the OEDA XML configuration file.

    oedacli> LOAD FILE NAME=Oracle-test.xml  
    SUCCESS - file loaded OK  
    Customer : ora07adm01 - Oracle
    
  2. List the databases contained in the XML configuration file, so that you can identify the database ID associated with the database you want to delete.

    oedacli> LIST DATABASES
    version : "2" 
    databaseOwner : "c0_oracle" 
    databaseSid : "dbm01" 
    databaseBlockSize : "8192" 
    characterset : "AL32UTF8" 
    databaseHome : 
    id : "c0_databaseHome" 
    machines : 
    machine : 
    ..... 
    ..... 
    diskGroups : 
    diskGroup : 
    id : "c0_datadg" 
    id : "c0_recodg" 
    id : "c0_dbm01" 
    ..... 
    ..... 
    databaseHome : 
    id : "c0_databaseHome3" 
    machines : 
    machine : 
    .... 
    .... 
    databaseTemplate : "OLTP" 
    databaseStyle : "ADMIN" 
    language : "all_langs" 
    diskGroups : 
    diskGroup : 
    id : "c0_datadg" 
    id : "c0_recodg" 
    id : "c0_testdb01" 
    
  3. Create an action to delete the target database. Use the database id identified in the previous step

    oedacli> delete database where id='c0_testdb01'
    
  4. Save the action.

    oedacli> SAVE ACTION
    
  5. Merge all actions.

    oedacli> MERGE ACTIONS 
    processMerge  
    processMergeActions  
    Merging Action : delete database where id='c0_testdb01'  
    Merging DELETE DATABASE  
    Action Validated and Merged OK
    
  6. Deploy the actions into the current configuration.

    oedacli> DEPLOY ACTIONS 
    Deploying Action ID : 1 delete database where id='c0_testdb01' 
    Deploying DELETE DATABASE 
    Deleting database testdb 
    Done... 
    Done
    
3.3.3.6.4 LIST DATABASES
This command lists the existing Oracle databases.

Syntax

LIST DATABASES 
[ WHERE
   ID = database_id |
   CLUSTERNUMBER = cluster_number  |
   CLUSTERNAME = cluster_name  |
   CLUSTERID = cluster_id  ] 

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID of the database

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

3.3.3.7 DATABASE HOME

You can add, alter, delete, or list the Oracle database homes.
3.3.3.7.1 ADD DATABASEHOME
This command adds an Oracle database home to an existing cluster.

Syntax

ADD DATABASEHOME 
   OWNER = owner DBVERSION = version
   DBHOMELOC = database_home_path [DBHOMENAME = database_home_name] 
   [INVLOC = inventory_location] [DBLANG = database_language]
   [MACHINELIST = 'machine_list'] [PATCHLIST = 'patch_list']
   [BASEDIR = base_directory] [VOLUMESIZE = volume_size]
WHERE
   { CLUSTERNUMBER = cluster_number | CLUSTERNAME = cluster_name |
     CLUSTERID = cluster_id }

Arguments

You can specify the following attributes for the new Oracle database home:

  • OWNER : (Mandatory) Specifies the operating system user that owns the Oracle home.

  • DBVERSION : (Mandatory) Specifies the version of the software in the database home, including the bundle patch, for example 12.1.0.2.170418.

  • DBHOMELOC : (Mandatory) Specifies the file system path for the new Oracle database home directory.

  • DBHOMENAME : Specifies the name of the new database home. The default value is the standard template name, for example, dbhome_1.

  • INVLOC : Specifies the location of the Oracle inventory directory. The default value is derived from the cluster home.

  • DBLANG : Specifies the language to use with the Oracle home. The default value is all_langs.

  • MACHINELIST : Specifies a list of nodes to create the Oracle home on. The default value is list of nodes registered with the Grid home.

  • PATCHLIST : Specifies a comma-separated list of patches for the database home. The default value is derived from DBVERSION.

  • BASEDIR : Specifies the location of the Oracle Base directory. The default value is derived from OWNER.

  • VOLUMESIZE : Specifies the size of the home directory volume. The default value is 50 GB. This argument is applicable only for database homes for Oracle VM clusters.

The following arguments are available in the WHERE clause:

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

Example 3-10 Adding a Database Home to a Deployment using OEDACLI

This example shows how to add a new Oracle home. dbversion should specify both the base version and the target Bundle Patch version. In this example, we are setting up a new Oracle database home with 12.1.0.2 DBBP 170418. The software will be installed under /u01/app/oracle/product/12.1.0.2/dbhome_2.

./oedacli

oedacli> LOAD FILE NAME=Oracle-test12.xml
SUCCESS - file loaded OK 
Customer : ora07adm01 - Oracle

oedacli> ADD DATABASEHOME OWNER='oracle' DBVERSION='12.1.0.2.170418' DBHOMELOC='/u0
1/app/oracle/product/12.1.0.2/dbhome_2' WHERE CLUSTERNUMBER=1

oedacli> SAVE ACTION

oedacli> MERGE ACTIONS
processMerge 
processMergeActions 
Merging Action : add databasehome owner='oracle' dbversion='12.1.0.2.170418' 
dbhomeloc='/u01/app/oracle/product/12.1.0.2/dbhome_2' where clusternumber=1 
Merging ADD DATABASEHOME 
Action Validated and Merged OK

oedacli> DEPLOY ACTIONS
Deploying Action ID : 1 add databasehome owner='oracle' dbversion='12.1.0.2.170418'
 dbhomeloc='/u01/app/oracle/product/12.1.0.2/dbhome_2' where clusternumber=1 
Deploying ADD DATABASEHOME 
Checking local files.. 
Required files are: 
SUCCESS: Required file /scratch/cpabba/Oeda/main/linux-x64/WorkDir/p26022196_121020
_Linux-x86-64.zip exists... 
SUCCESS: Required file /scratch/cpabba/Oeda/main/linux-x64/WorkDir/p26027162_121020
_Linux-x86-64.zip exists... 
SUCCESS: Required file /scratch/cpabba/Oeda/main/linux-x64/WorkDir/p6880880_122010_
Linux-x86-64.zip exists... 
SUCCESS: Required file /scratch/cpabba/Oeda/main/linux-x64/WorkDir/linuxamd64_12102
_database_2of2.zip exists... 
SUCCESS: Required file /scratch/cpabba/Oeda/main/linux-x64/WorkDir/linuxamd64_12102
_database_1of2.zip exists... 
Copying required files... 
Checking status of remote files... 
Checking status of existing files on remote nodes... 
Getting status of local files... 
Copying file: linuxamd64_12102_database_1of2.zip to node node1adm01.us.oracle.com 
Copying file: linuxamd64_12102_database_2of2.zip to node node1adm01.us.oracle.com 
Copying file: p26022196_121020_Linux-x86-64.zip to node node1adm01.us.oracle.com 
Copying file: p26027162_121020_Linux-x86-64.zip to node node1adm01.us.oracle.com 
Copying file: p26022196_121020_Linux-x86-64.zip to node node1adm02.us.oracle.com 
Copying file: p26027162_121020_Linux-x86-64.zip to node node1adm02.us.oracle.com 
Completed copying files... 
Extracting files... 
Completed extracting files... 
Validating nodes for database readiness... 
Installing database software ... 
Running database installer on node node1adm01.us.oracle.com ... Please wait... 
After running database installer... 
Patching... 
Done... 
Done
3.3.3.7.2 ALTER DATABASEHOME
This command alters an existing Oracle database home.

Syntax

ALTER DATABASEHOME 
   OWNER = owner |
   DBVERSION = version |
   DBHOMELOC = database_home_path | 
   DBHOMENAME = database_home_name |
   INVLOC = inventory_location |
   DBLANG = language |
   MACHINELIST = 'machine_list' |
   PATCHLIST = 'patch_list'  |
   BASEDIR = base_directory 
WHERE
   ID = database_home_id | 
   CLUSTERNUMBER = cluster_number DBHOMELOC = database_home_path |
   CLUSTERNAME = cluster_name DBHOMELOC = database_home_path |
   CLUSTERID = cluster_id DBHOMELOC = database_home_path 

Arguments

You can modify the following attributes for the Oracle database home:

  • OWNER : Specifies the operating system user that owns the Oracle home.

  • DBVERSION : Specifies the version of the software in the database home, including the bundle patch, for example 12.1.0.2.170418.

  • DBHOMELOC : Specifies the file system path for the new Oracle database home directory.

  • DBHOMENAME : Specifies the new name of the database home. The database home name must be unique within a cluster.

  • INVLOC : Specifies the location of the Oracle inventory directory.

  • DBLANG : Specifies the supported languages for the Oracle home.

  • MACHINELIST : Specifies a list of nodes. The nodes must exist within the cluster.

  • PATCHLIST : Specifies a comma-separated, custom list of patches for the database home.

  • BASEDIR : Specifies the location of the Oracle Base directory.

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID for the database home

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • DBHOMELOC : Specifies the path for the database home directory.

3.3.3.7.3 DELETE DATABASEHOME
This command removes an existing Oracle database home.

Syntax

DELETE DATABASEHOME 
WHERE
   ID = database_home_id | 
   CLUSTERNUMBER = cluster_number DBHOMELOC = database_home_path |
   CLUSTERNAME = cluster_name DBHOMELOC = database_home_path |
   CLUSTERID = cluster_id DBHOMELOC = database_home_path 

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID for the database home

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • DBHOMELOC : Specifies the path for the database home directory.

Usage Notes

The database home you are deleting must not contain any dependent databases.

Example 3-11 Removing an Existing Oracle Database Home

This example shows how to delete an existing Oracle Database home directory.

oedacli> LOAD FILE NAME=Oracle-test12.xml 
SUCCESS - file loaded OK 
Customer : ora07adm01 - Oracle

oedacli> DELETE DATABASEHOME WHERE id='c0_databaseHome1' 

oedacli> SAVE ACTION 

oedacli> MERGE ACTIONS 
processMerge 
processMergeActions 
Merging Action : delete databasehome where id='c0_databaseHome1' 
Merging DELETE DATABASEHOME 
Action Validated and Merged OK 

oedacli> DEPLOY ACTIONS 
Deploying Action ID : 3 delete databasehome where id='c0_databaseHome1' 
Deploying DELETE DATABASEHOME 
Validating Oracle home.. 
Deinstalling database home c0_DbHome_1 
Unmounting file system.. 
Updating /etc/fstab entries... 
Done... 
Done
3.3.3.7.4 LIST DATABASEHOMES
This command lists the existing Oracle database homes.

Syntax

LIST DATABASEHOMES
[ WHERE
    ID = database_home_id | 
    CLUSTERNUMBER = cluster_number NAME = database_home_name |
    CLUSTERNAME = cluster_name NAME = database_home_name |
    CLUSTERID = cluster_id NAME = database_home_name ]

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID for the target database home

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • NAME : Specifies the name of the target database home

3.3.3.8 ES

You can alter a limited number of attributes of an engineered system.
3.3.3.8.1 ALTER ES

This command alters the attributes of an engineered system.

Syntax

ALTER ES 
   PAAS = 'pass_mode' |
   CUSTOMERNAME = customer_name |
   CUSTOMERDEPT = customer_dept 

Arguments

You can modify the following attributes for the engineered system:

  • PAAS : A boolean value, TRUE or FALSE, which specifies whether to enable PaaS mode.

  • CUSTOMERNAME : Specifies the customer name.

  • CUSTOMERDEPT : Specifies the customer department.

3.3.3.9 GUEST

You can clone or delete an Oracle VM guest.
3.3.3.9.1 CLONE GUEST
This command clones an existing Oracle VM guest.

Syntax

CLONE GUEST SRCNAME = source_guest
  SET PARENT NAME=parent_name
  SET ADMINNET NAME=admin_name,IP=IP_admin
  SET PRIVNET NAME1=priv_name_1,IP1=priv_ip1,NAME2=priv_name_2,
    IP2=priv_ip2 [ SET INTERCONNECT NAME1=priv_name_1,IP1=priv_ip1,
    NAME2=priv_name_2, IP2=priv_ip2 ]
  SET CLIENTNET NAME=client_name,IP=client_ip
  SET VIPNET NAME=vip_name,IP=vip_ip

Arguments

SRCNAME is used to specify the name of an existing DomU from which the new DomU is derived.

The following arguments are available in the SET clauses:

  • PARENT : Specifies the host name of the Dom0 use to host this new guest

  • ADMINNET : Specifies the DNS name with an optional domain name and the IP address to be used for the admin network

  • PRIVNET : Specifies the DNS name with an optional domain name and the IP address to be used for the first and second private networks

  • INTERCONNECT : Specifies the DNS name with an optional domain name and the IP address to be used for the first and second private interconnects

  • CLIENTNET : Specifies the DNS name with an optional domain name and the IP address to be used for the client network

  • VIPNET : Specifies the DNS name with an optional domain name and the IP address to be used for the VIP network

Usage Notes

The SET INTERCONNECT clause is only required if the compute nodes are configured with InfiniBand security (PKEYS).

3.3.3.9.2 DELETE GUEST
This command deletes an existing Oracle VM guest, removing the instance, home, and Oracle Clusterware from the cluster.

Syntax

DELETE GUEST WHERE SRCNAME = node_name

Arguments

SRCNAME is used to specify the host name of an existing DomU that you want to delete.

3.3.3.10 ILOM

You can alter or list the ILOMS in the loaded es.xml file.
3.3.3.10.1 ALTER ILOM
This command alters attributes of an ILOM.

Syntax

ALTER ILOM { DNSSERVERS='dns_servers' | NTPSERVERS= 'ntp_servers' |
   TIMEZONE = timezone } 
WHERE { 
   ID = ilom_id | 
   HOSTNAME = hostname |
   ILOMNAME = ilom_hostname } 

Arguments

You can specify the following attributes for the ILOM:

  • DNSSERVERS : Specifies a comma-separated list of DNS servers that is enclosed in single quotes.

  • NTPSERVERS : Specifies a comma-separated list of NTP servers that is enclosed in single quotes.

  • TIMEZONE : Specifies a valid time zone for the ILOM.

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID for the target ILOM

  • HOSTNAME : Specifies the current host name of the target machine

  • ILOMNAME : Specifies the current host name of the ILOM

3.3.3.10.2 LIST ILOMS
This command lists the ILOMs in the es.xml file.

Syntax

LIST ILOMS 
[ WHERE { 
   ID = ilom_id | 
   HOSTNAME = hostname |
   ILOMNAME = ilom_hostname } ] 

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID for the target ILOM

  • HOSTNAME : Specifies the current host name of the target machine

  • ILOMNAME : Specifies the current host name of the ILOM

Usage Notes

If you do not specify a WHERE clause, then this command lists all the ILOMs in the es.xml file.

3.3.3.11 MACHINE

You can alter or list the machines in the es.xml file.
3.3.3.11.1 ALTER MACHINE
This command alters attributes of a compute node or storage cell in an engineered system.

Syntax

ALTER MACHINE { DNSSERVERS='dns_servers' | GATEWAYADAPTER=gateway_adapter | 
   HOSTNAMEADAPTER=hostname_adapter | NTPSERVERS= 'ntp_servers' |
   TIMEZONE = timezone } 
WHERE { 
   ID = machine_id | 
   HOSTNAME = hostname |
   CLUSTERNUMBER = cluster_number COMPUTENUMBER = compute_number |
   CLUSTERNUMBER = cluster_number STORAGENUMBER = storage_number |
   CLUSTERNAME = cluster_name COMPUTENUMBER = compute_number |
   CLUSTERNAME = cluster_name STORAGENUMBER = storage_number |
   CLUSTERID = cluster_id COMPUTENUMBER = compute_number |
   CLUSTERID = cluster_id STORAGENUMBER = storage_number } 

Arguments

You can specify the following attributes for the machine:

  • DNSSERVERS : Specifies a comma-separated list of DNS servers that is enclosed in single quotes.

  • GATEWAYADAPTER : Specifies the network adapter to use as the machine gateway. Valid values are ADMIN or CLIENT.

  • HOSTNAMEADAPTER : Specifies the network adapter to use as the host name. Valid values are ADMIN or CLIENT.

  • NTPSERVERS : Specifies a comma-separated list of NTP servers that is enclosed in single quotes.

  • TIMEZONE : Specifies a valid time zone for the machine.

The following arguments are available in the WHERE clause:

  • ID : Specifies the es.xml ID for the target machine

  • HOSTNAME : Specifies the current host name of the target machine

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • COMPUTENUMBER : Specifies the compute node number in the cluster, starting at 1

  • STORAGENUMBER : Specifies the storage cell number in the cluster, starting at 1

3.3.3.11.2 LIST MACHINES
This command lists the machine available in the es.xml file for an engineered system.

Syntax

LIST MACHINES  
{ WHERE  
   TYPE = type |
   ID = machine_id [ TYPE = type ] | 
   CLUSTERNUMBER = cluster_number [ TYPE = type ] |
   CLUSTERNAME = cluster_name [ TYPE = type ] |
   CLUSTERID = cluster_id [ TYPE = type ] }

Arguments

The following arguments are available in the WHERE clause:

  • TYPE : Specifies the machine type. The valid values are COMPUTE, CELL, STORAGE, DOM0, GUEST, or DOMU.

  • ID : Specifies the es.xml ID for an individual machine

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

Usage Notes

If you do not specify a WHERE clause, then this command lists all the machines defined in the es.xml file.

3.3.3.12 NETWORK

You can add, alter, delete, or list the networks defined in the XML configuration file.
3.3.3.12.1 ADD NETWORK
This command adds a network record to a machine in the existing configuration.

Syntax

ADD NETWORK 
   NETWORKTYPE=network_type HOSTNAME=hostname IP=ip_addr 
   NETMASK=netmask DOMAINNAME=domain_name MASTER=master 
   [ GATEWAY=gateway] [ SSHENABLED=ssh_enabled ] [ MAC=mac_addr ]
   [ NICSPEED=nic_speed [ SLAVE='slave'] [ PKEY=pkey ] 
   [ PKEYNAME=pkey_name ] [ STATUS = status ] [ LACP=lacp ]
   [ VLANID=vlan_id ] [ NATHOSTNAME=nat_host_name ] [ NATIP=nat_ip_addr ]
   [ NATDOMAINNAME=nat_domain_name ] [ NATNETMASK=nat_mask ] 
WHERE {
   HOSTNAME = hostname | 
   CLUSTERNAME = cluster_name COMPUTENUMBER=compute_number | 
   CLUSTERNAME = cluster_name STORAGENUMBER=storage_number | 
   CLUSTERNUMBER = cluster_number COMPUTENUMBER=compute_number |
   CLUSTERNUMBER = cluster_number STORAGENUMBER=storage_number }  

Arguments

You can specify the following attributes when adding a network:

  • NETWORKTYPE : (Mandatory) Specifies the type of network, which can be ADMIN, CLIENT, BACKUP, PRIVATE, OTHER, INGESTVIP, REPLICATIONVIP, or ILOM.

  • HOSTNAME : (Mandatory) Specifies the short host name for the network

  • IP : (Mandatory) Specifies the IP address of the network

  • NETMASK : (Mandatory) Specifies the netmask of the network

  • DOMAINNAME : (Mandatory) Specifies the domain name of the network

  • MASTER : (Mandatory) Specifies the master adapter name

  • GATEWAY : Specifies the network subnet gateway

  • SSHENABLED : A Boolean variable where TRUE indicates SSH should be enabled for this adapter

  • MAC : Specifies the MAC address

  • NICSPEED : (Only for X7 2 socket compute nodes), either 10000 or 25000

  • SLAVE : Specifies a space-separated list of slave devices for a bonded network, enclosed in single quotes

  • PKEY : (For Private networks only) Specifies the pkey

  • PKEYNAME : (For Private networks only) Specifies the pkey name

  • STATUS : Specifies the status of the network

  • LACP : A Boolean variable where TRUE indicates that LACP should be enabled

  • VLANID : Specifies the VLAN Id if network is a VLAN network and not private

  • NATHOSTNAME : Specifies the NAT host name

  • NATIP : Specifies the NAT IP address

  • NATDOMAINNAME : Specifies the NAT domain name

  • NATNETMASK : Specifies the NAT netmask

The following arguments are available in the WHERE clause:

  • HOSTNAME : Specifies the host name for an existing compute node

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of an existing cluster

  • COMPUTENUMBER : Specifies the number of an existing compute node in the cluster, starting at 1

  • STORAGENUMBER : Specifies the umber of an existing storage cell in the cluster, starting at 1

3.3.3.12.2 ALTER NETWORK
This command modifies a network record for a machine in the existing configuration.

Syntax

ALTER NETWORK { 
   [ HOSTNAME=hostname ] [ IP=ip_addr ] [ NETMASK=netmask ]
   [ DOMAINNAME=domain_name] [ MASTER=master] [ GATEWAY=gateway] 
   [ SSHENABLED=ssh_enabled ] [ MAC=mac_addr ] [ NICSPEED=nic_speed]
   [ SLAVE='slave'] [ PKEY=pkey ] [ PKEYNAME=pkey_name ]
   [ STATUS = status ] [ LACP=lacp ] [ VLANID=vlan_id ]
   [ NATHOSTNAME=nat_host_name ] [ NATIP=nat_ip_addr ]
   [ NATDOMAINNAME=nat_domain_name ] [ NATNETMASK=nat_mask ] } 
WHERE {
   ID = network_id |  
   NETWORKHOSTNAME = network_hostname | 
   NATHOSTNAME = nat_hostname |
   HOSTNAME = hostname NETWORKTYPE = network_type [PRIVATEID=private_id]|
   CLUSTERNAME = cluster_name { COMPUTENUMBER=compute_number | STORAGENUMBER=storage_number }
     NETWORKTYPE = network_type [PRIVATEID=private_id] | 
   CLUSTERNUMBER = cluster_number { COMPUTENUMBER=compute_number | STORAGENUMBER=storage_number }
     NETWORKTYPE = network_type [PRIVATEID=private_id] }

Arguments

You can specify the following attributes when altering a network:

  • HOSTNAME : Specifies the short host name for the network

  • IP : Specifies the IP address of the network

  • NETMASK : Specifies the netmask of the network

  • DOMAINNAME : Specifies the domain name of the network

  • MASTER : Specifies the master adapter name

  • GATEWAY : Specifies the network subnet gateway

  • SSHENABLED : A Boolean variable where TRUE indicates SSH should be enabled for this adapter

  • MAC : Specifies the MAC address

  • NICSPEED : (Only for X7 2 socket compute nodes), either 10000 or 25000

  • SLAVE : Specifies a space-separated list of slave devices for a bonded network, enclosed in single quotes

  • PKEY : (For Private networks only) Specifies the pkey

  • PKEYNAME : (For Private networks only) Specifies the pkey name

  • STATUS : Specifies the status of the network

  • LACP : A Boolean variable where TRUE indicates that LACP should be enabled

  • VLANID : Specifies the VLAN Id if network is a VLAN network and not private

  • NATHOSTNAME : Specifies the NAT host name

  • NATIP : Specifies the NAT IP address

  • NATDOMAINNAME : Specifies the NAT domain name

  • NATNETMASK : Specifies the NAT netmask

The following arguments are available in the WHERE clause:

  • ID : Specifies the ID for the target network in the XML configuration file.

  • NETWORKHOSTNAME : Specifies the host name for an network object, not the machine host name

  • NATHOSTNAME : Specifies the NAT host name for an existing compute node

  • HOSTNAME : Specifies the host name for an existing compute node

  • NETWORKTYPE : Specifies the type of network, which can be ADMIN, CLIENT, BACKUP, PRIVATE, OTHER, INGESTVIP, REPLICATIONVIP, or ILOM.

  • PRIVATEID : Specifies the ID of the private network

  • CLUSTERNUMBER : Specifies the cluster number in the XML configuration file, starting at 1

  • CLUSTERNAME : Specifies the name of an existing cluster

  • COMPUTENUMBER : Specifies the number of an existing compute node in the cluster, starting at 1

  • STORAGENUMBER : Specifies the number of an existing storage cell in the cluster, starting at 1

3.3.3.12.3 DELETE NETWORK
This command removes a network record for a machine.

Syntax

DELETE NETWORK 
WHERE {
   ID = network_id |  
   HOSTNAME = network_hostname NETWORKTYPE = network_type | 
   CLUSTERNAME = cluster_name { COMPUTENUMBER=compute_number | 
     STORAGENUMBER=storage_number } NETWORKTYPE = network_type |
   CLUSTERNUMBER = cluster_number { COMPUTENUMBER=compute_number | 
     STORAGENUMBER=storage_number } NETWORKTYPE = network_type |
   CLUSTERID = cluster_id { COMPUTENUMBER=compute_number | 
     STORAGENUMBER=storage_number } NETWORKTYPE = network_type }

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the ID for the network object in the XML configuration file.

  • HOSTNAME : Specifies the host name for an existing compute node

  • NETWORKTYPE : Specifies the type of network, which can be ADMIN, CLIENT, BACKUP, PRIVATE, OTHER, INGESTVIP, REPLICATIONVIP, or ILOM.

  • CLUSTERNAME : Specifies the name of an existing cluster

  • CLUSTERNUMBER : Specifies the cluster number in the XML configuration file, starting at 1

  • CLUSTERID : Specifies the cluster ID in the XML configuration file

  • COMPUTENUMBER : Specifies the number of an existing compute node in the cluster, starting at 1

  • STORAGENUMBER : Specifies the number of an existing storage cell in the cluster, starting at 1

3.3.3.12.4 LIST NETWORKS
This command lists the network details.

Syntax

LIST NETWORKS 
[ WHERE {
   ID = network_id |  
   HOSTNAME = network_hostname [ NETWORKTYPE = network_type ] | 
   CLUSTERNAME = cluster_name { COMPUTENUMBER=compute_number | 
     STORAGENUMBER=storage_number } [ NETWORKTYPE = network_type ] |
   CLUSTERNUMBER = cluster_number { COMPUTENUMBER=compute_number | 
     STORAGENUMBER=storage_number } [ NETWORKTYPE = network_type ] }   CLUSTERID = cluster_ID { COMPUTENUMBER=compute_number | 
     STORAGENUMBER=storage_number } [ NETWORKTYPE = network_type ] } ]

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the ID for the network object in the XML configuration file.

  • HOSTNAME : Specifies the host name for an existing compute node

  • NETWORKTYPE : Specifies the type of network, which can be ADMIN, CLIENT, BACKUP, PRIVATE, or ILOM.

  • CLUSTERNAME : Specifies the name of an existing cluster

  • CLUSTERNUMBER : Specifies the cluster number in the XML configuration file, starting at 1

  • CLUSTERID : Specifies the cluster ID in the XML configuration file

  • COMPUTENUMBER : Specifies the number of an existing compute node in the cluster, starting at 1

  • STORAGENUMBER : Specifies the number of an existing storage cell in the cluster, starting at 1

3.3.3.13 SCAN

You can add, alter, delete, or list the SCANs for a cluster.
3.3.3.13.1 ADD SCAN
This command adds a SCAN to the an individual cluster.

Syntax

ADD SCAN SCANNAME=scan_name [ SCANPORT=scan_port ] SCANIPS='scan_ip_addrs'
WHERE
 {   CLUSTERNAME = cluster_name |
     CLUSTERNUMBER = cluster_number |
     CLUSTERID = cluster_id }

Arguments

You can specify the following attributes for the new SCAN:

  • SCANNAME : Specifies the DNS name for the SCAN

  • SCANPORT : Specifies the port for the SCAN. The default value is 1521.

  • SCANIPS : A comma-separated list of IP addresses for the SCAN, enclosed in single quotes.

The following arguments are available in the WHERE clause:

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERNUMBER : Specifies the cluster number in the XML configuration file, starting at 1

  • CLUSTERID : Specifies the ID of the cluster in the XML configuration file

3.3.3.13.2 ALTER SCAN
This command modifies the attributes of a SCAN for an individual cluster.

Syntax

ALTER SCAN { SCANNAME=scan_name | SCANPORT=scan_port | SCANIPS='scan_ip_addrs' }
 WHERE
 {   CLUSTERNAME = cluster_name |
     CLUSTERNUMBER = cluster_number |
     CLUSTERID = cluster_id }

Arguments

You can modify the following attributes for the SCAN:

  • SCANNAME : Specifies the DNS name for the SCAN

  • SCANPORT : Specifies the port for the SCAN.

  • SCANIPS : A comma-separated list of IP addresses for the SCAN, enclosed in single quotes.

The following arguments are available in the WHERE clause:

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERNUMBER : Specifies the cluster number in the XML configuration file, starting at 1

  • CLUSTERID : Specifies the ID of the cluster in the XML configuration file

3.3.3.13.3 DELETE SCAN
This command removes a SCAN for an individual cluster.

Syntax

DELETE SCAN 
 WHERE
 {   CLUSTERNAME = cluster_name |
     CLUSTERNUMBER = cluster_number |
     CLUSTERID = cluster_id }

Arguments

The following arguments are available in the WHERE clause:

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERNUMBER : Specifies the cluster number in the XML configuration file, starting at 1

  • CLUSTERID : Specifies the ID of the cluster in the XML configuration file

3.3.3.13.4 LIST SCANS
This command lists the SCAN details for all clusters or for an individual cluster.

Syntax

LIST SCANS 
[ WHERE
 {   SCANID = scan_id | 
     CLUSTERNAME = cluster_name |
     CLUSTERNUMBER = cluster_number |
     CLUSTERID = cluster_id } ]

Arguments

The following arguments are available in the WHERE clause:

  • SCANID : Specifies the ID of the SCAN object in the XML configuration file

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERNUMBER : Specifies the cluster number in the XML configuration file, starting at 1

  • CLUSTERID : Specifies the ID of the cluster in the XML configuration file

Usage Notes

If you do not specify a WHERE clause, then this command lists details about all the SCANS for all the clusters in the XML configuration file.

3.3.3.14 SWITCH

You can alter or list the switches.
3.3.3.14.1 ALTER SWITCH
This command alters attributes of an individual switch.

Syntax

ALTER SWITCH { DNSSERVERS='dns_servers' | NTPSERVERS= 'ntp_servers' |
   TIMEZONE = timezone } 
WHERE { 
   ID = switch_id | 
   HOSTNAME = switch_name }

Arguments

You can modify the following attributes for a switch:

  • DNSSERVERS : Specifies a comma-separated list of DNS servers that is enclosed in single quotes.

  • NTPSERVERS : Specifies a comma-separated list of NTP servers that is enclosed in single quotes.

  • TIMEZONE : Specifies a valid time zone for the switch.

The following arguments are available in the WHERE clause:

  • ID : Specifies the switch ID in the XML configuration file

  • HOSTNAME : Specifies the host name of the switch

3.3.3.14.2 LIST SWITCHES
This command lists the switch details for all switches or for an individual switch.

Syntax

LIST SWITCHES 
[ WHERE { 
   ID = switch_id | 
   HOSTNAME = switch_name } ]

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the switch ID in the XML configuration file

  • HOSTNAME : Specifies the host name of the switch

Usage Notes

If you do not specify a WHERE clause, then this command lists the details for all switches.

3.3.3.15 VIP

You can add, alter, delete, or list the VIPs for the clusters.
3.3.3.15.1 ADD VIP
This command adds a VIP for an individual node in a cluster.

Purpose

This command does not add additional VIPs. You should only use this command after previously issuing a DELETE VIP command.

Syntax

ADD VIP NAME=vip_name DOMAINNAME=domain_name IP=vip_ip_addr 
WHERE { 
   HOSTNAME = hostname |
   CLUSTERNAME = cluster_name COMPUTENUMBER = compute_number |
   CLUSTERNUMBER = cluster_number COMPUTENUMBER = compute_number |
   CLUSTERID = cluster_id COMPUTENUMBER = compute_number }

Arguments

You can specify the following attributes when adding a VIP:

  • NAME : Specifies the short DNS name for the VIP

  • DOMAINNAME : Specifies the domain name for the VIP

  • IP : Specifies the IP address for the VIP

The following arguments are available in the WHERE clause:

  • HOSTNAME : Specifies the host name for the compute node in the cluster

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • COMPUTENUMBER : Specifies the compute node number in the cluster, starting at 1

Usage Notes

When adding a VIP to a compute node, the node must not already have a VIP defined.

3.3.3.15.2 ALTER VIP
This command alters the attributes of a VIP for an individual node in a cluster.

Syntax

ALTER VIP { NAME=vip_name | DOMAINNAME=domain_name | 
   IP=vip_ip_addr } 
WHERE { 
   HOSTNAME = hostname |
   CLUSTERNAME = cluster_name COMPUTENUMBER = compute_number |
   CLUSTERNUMBER = cluster_number COMPUTENUMBER = compute_number |
   CLUSTERID = cluster_id COMPUTENUMBER = compute_number }

Arguments

You can modify the following attributes for the VIP:

  • NAME : Specifies the short DNS name for the VIP

  • DOMAINNAME : Specifies the domain name for the VIP

  • IP : Specifies the IP address for the VIP

The following arguments are available in the WHERE clause:

  • HOSTNAME : Specifies the host name for the compute node in the cluster

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

  • COMPUTENUMBER : Specifies the compute node number in the cluster, starting at 1

3.3.3.15.3 DELETE VIP
This command removes a VIP from an individual node in a cluster.

Syntax

DELETE VIP  
WHERE { 
   ID = vip_id |
   HOSTNAME = hostname |
   CLUSTERNAME = cluster_name COMPUTENUMBER = compute_number |
   CLUSTERNUMBER = cluster_number COMPUTENUMBER = compute_number |
   CLUSTERID = cluster_id COMPUTENUMBER = compute_number }

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the ID for the VIP in the XML configuration file

  • HOSTNAME : Specifies the host name for the compute node in the cluster

  • CLUSTERNUMBER : Specifies the cluster number in the XML configuration file, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the ID of the cluster in the XML configuration file

  • COMPUTENUMBER : Specifies the compute node number in the cluster, starting at 1

3.3.3.15.4 LIST VIPS
This command lists the VIPs for all clusters or for an individual node in a cluster.

Syntax

LIST VIPS  
[ WHERE { 
   HOSTNAME = hostname |
   CLUSTERNAME = cluster_name [ COMPUTENUMBER = compute_number ] |
   CLUSTERNUMBER = cluster_number [ COMPUTENUMBER = compute_number ] |
   CLUSTERID = cluster_id [ COMPUTENUMBER = compute_number ] }

Arguments

The following arguments are available in the WHERE clause:

  • ID : Specifies the ID for the VIP in the XML configuration file

  • HOSTNAME : Specifies the host name for the compute node in the cluster

  • CLUSTERNUMBER : Specifies the cluster number in the XML configuration file, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the ID of the cluster in the XML configuration file

  • COMPUTENUMBER : Specifies the compute node number in the cluster, starting at 1

Usage Notes

If you do not specify a WHERE clause, then this command lists the VIPs for all clusters.