4.3.15.2 ALTER EXASCALECLUSTER

This command alters an existing Exascale cluster.

Syntax

ALTER EXASCALECLUSTER
   [ NAME = newexascaleclustername ]
   [ MODE = deploymentmode ]
   [ VIP = newersvip ]
   [ IP = newersip ]
   [ RESTNETWORKID = newersnetworkid ]
   [ BSWHAVIPIPS = bswhavipips ]
   [ BSWHAVIPNETMASK = bswhavipnetmask ] 
   [ ADDCELLS = 'addcells' | DROPCELLS = 'dropcells' ]
WHERE
   NAME = exascaleclustername
   [ STEPNAME = stepname ]

Arguments

  • NAME: Changes the name of the Exascale cluster.
  • MODE: Specifies the Exascale cluster deployment mode.
  • VIP: Specifies the DNS name for the virtual IP (VIP) interface that provides access to Exascale control services (also known as Exascale RESTful Services or ERS).
  • IP: Specifies the IP address for the ERS VIP.
  • RESTNETWORKID: Specifies the ERS network ID.
  • BSWHAVIPIPS: Specifies a comma-separated list of IP addresses to use for the Exascale Block Store Worker (BSW) virtual IP (VIP) interfaces.
  • BSWHAVIPNETMASK: Specifies the netmask to use for the BSW VIPs.

  • ADDCELLS: Specifies a comma-separated list of cells to add to the Exascale cluster. The list must be enclosed in single quotes.

  • DROPCELLS: Specifies a comma-separated list of cells to drop from the Exascale cluster. The list must be enclosed in single quotes.

The following arguments are available in the WHERE clause:

  • NAME: Specifies the name for the Exascale cluster that you want to alter.

  • STEPNAME: Specifies one of the following steps for an ADDCELLS or DROPCELLS operation:

    • CONFIG_CELL

    • CONFIG_COMPUTES

    For an ADDCELLS operation, the steps are performed in the listed order. For a DROPCELLS operation, the steps are performed in the reverse order.

Usage Notes

  • Do not specify the Exascale cluster deployment mode using any value other than onPremises. All other values are reserved for Oracle internal use.

  • The network interface specified by VIP and IP is associated with a highly-available virtual IP (VIP) network interface, which provides a consistent network end point for Exascale control services. The VIP is hosted by one of the Exadata storage servers, which also runs a front-end ERS instance. If the storage server or ERS instance becomes unavailable, then the VIP moves to another server hosting a front-end ERS instance.

Parent topic: EXASCALECLUSTER