ORACLE CLOUD

Exadata actions

27 actions you can wire into a flow, alongside everything else in the Oracle Cloud integration.

Every Exadata action

  • OCI Exadata: Add Storage CapacityActivate the storage servers already installed on a cloud Exadata infrastructure so their capacity becomes available to VM clusters. Asynchronous: poll Get Cloud Exadata Infrastructure until AVAILABLE.
  • OCI Exadata: Add VM to Cloud VM ClusterScale a cloud VM cluster out by adding virtual machines: one per supplied ExaDB-D DB server OCID. Asynchronous, poll Get Cloud VM Cluster until AVAILABLE.
  • OCI Exadata: Create Cloud Exadata InfrastructureProvision cloud Exadata infrastructure: the dedicated rack of compute and storage servers a VM cluster runs on. Pick the shape and the number of compute and storage servers to scale it. Asynchronous, poll Get Cloud Exadata Infrastructure until AVAILABLE.
  • OCI Exadata: Create Cloud VM ClusterProvision a cloud VM cluster on existing Exadata infrastructure: the database VMs that host your Oracle databases. Give it a subnet, a backup subnet, a hostname, an SSH key, a CPU core count and a Grid Infrastructure version. Asynchronous, poll Get Cloud VM Cluster until AVAILABLE.
  • OCI Exadata: Create Maintenance RunSchedule a maintenance run for an Exadata resource: the window in which Oracle applies the latest Release Update. Give it the target resource OCID, an RFC3339 scheduled time, and optionally a rolling or non-rolling patching mode.
  • OCI Exadata: DB Node ActionStart, stop or reset a database node (one of the VMs in a VM cluster). SOFTRESET does a graceful OS reboot; RESET is a hard power-cycle. Asynchronous: poll Get DB Node until the state settles.
  • OCI Exadata: Delete Cloud Exadata InfrastructureTear down a cloud Exadata infrastructure by OCID. Asynchronous: returns a work-request id you can poll to confirm the teardown.
  • OCI Exadata: Delete Cloud VM ClusterTerminate a cloud VM cluster by OCID. Asynchronous: returns a work-request id; poll until the cluster is gone.
  • OCI Exadata: Get Cloud Exadata InfrastructureFetch a single cloud Exadata infrastructure by OCID: its shape, compute/storage server counts, capacity and lifecycle state.
  • OCI Exadata: Get Cloud VM ClusterFetch a single cloud VM cluster by OCID: its shape, host, CPU cores, listener port and lifecycle state.
  • OCI Exadata: Get DB NodeFetch a single Exadata DB node by OCID: its hostname, DB system, fault domain and lifecycle state.
  • OCI Exadata: Get DB ServerFetch a single Exadata infrastructure DB server by OCID: its shape, CPU/memory capacity and lifecycle state.
  • OCI Exadata: Get Maintenance RunFetch a single Exadata maintenance run by OCID: its maintenance type, target resource, schedule and lifecycle state.
  • OCI Exadata: Get Unallocated ResourcesReport the spare capacity of a cloud Exadata infrastructure: unallocated local storage, OCPUs, memory and Exadata storage still available.
  • OCI Exadata: Get VM Cluster IORM ConfigFetch the I/O Resource Management (IORM) configuration for a cloud VM cluster: its objective, lifecycle state and per-database share plans.
  • OCI Exadata: List Cloud Exadata InfrastructuresList the cloud Exadata infrastructures in a compartment. Walks pagination up to a safe cap.
  • OCI Exadata: List Cloud VM ClustersList the cloud VM clusters in a compartment, optionally narrowed to one cloud Exadata infrastructure. Walks pagination up to a safe cap.
  • OCI Exadata: List DB NodesList the DB nodes of a cloud VM cluster (or DB system) in a compartment. Walks pagination up to a safe cap.
  • OCI Exadata: List DB ServersList the database servers on a cloud Exadata infrastructure. Walks pagination up to a safe cap.
  • OCI Exadata: List Maintenance RunsList the maintenance runs in a compartment, optionally filtered to one target resource. Walks pagination up to a safe cap.
  • OCI Exadata: Move Cloud Exadata Infrastructure to CompartmentMove a cloud Exadata infrastructure rack into a different compartment: an asynchronous move returning a work-request id to track.
  • OCI Exadata: Move Cloud VM Cluster to CompartmentMove a cloud VM cluster and its dependent resources to another compartment: asynchronous, returns a work-request id to track.
  • OCI Exadata: Remove VM from Cloud VM ClusterRemove one or more DB servers' virtual machines from a cloud VM cluster: asynchronous, returns the cluster in UPDATING plus a work-request id.
  • OCI Exadata: Update Cloud Exadata InfrastructureUpdate a cloud Exadata infrastructure by OCID: rename it, or scale its compute and storage server counts.
  • OCI Exadata: Update Cloud VM ClusterRename a cloud VM cluster or scale its total CPU core count. Asynchronous: poll Get Cloud VM Cluster until it settles back to AVAILABLE.
  • OCI Exadata: Update DB NodeUpdate a database node (one of the VMs in a VM cluster) by OCID: set its freeform tags. Asynchronous, poll Get DB Node until the state settles.
  • OCI Exadata: Update Maintenance RunModify a scheduled Exadata maintenance run: reschedule it, enable or skip it, start patching now, or switch its patching mode.

Also in Oracle Cloud

Put Exadata in a flow

These actions sit on the same canvas as every other integration, so a Exadata step can follow a form, a schedule or a message without any glue code.