Exadata

00Overview

Provision and manage Oracle's Exadata Database Service on Dedicated Infrastructure straight from a flow — stand up cloud Exadata infrastructure and the VM clusters that run on it, then rename, scale, move between compartments or tear them down. Scale a cluster out or in by adding and removing VMs, activate installed storage, and inspect the underlying DB servers and DB nodes, starting, stopping or rebooting individual nodes on demand. Schedule and adjust the maintenance runs that apply Oracle's Release Updates, and read back capacity, spare resources and lifecycle state so a flow can check the ground truth before it acts.

Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.

01Connecting Exadata

1. Pick how the node authenticates in the Authentication field: Connect Oracle Cloud (recommended) uses a managed connection an admin sets up once, while API signing key (advanced) lets you supply signing-key credentials directly on the node.
2. For Connect Oracle Cloud, an admin first sets up the managed connection once under Flomation Environments, supplying your Tenancy OCID and Region; Flomation then walks through creating a dedicated, least-privilege Oracle Cloud user and registering its API signing key for you, so no key material is handled by hand.
3. Back in Flomation, once the connection is created, select it in the node's Oracle Cloud connection field; if it was only just set up, allow a minute or two for the new signing key to become active in Oracle Cloud before the first run.
4. For the API signing key (advanced) path instead, sign in to the Oracle Cloud Console, open Profile → My profile → API keys → Add API key, let Oracle generate the pair and download the private key (a .pem file), then copy the Configuration file preview values into the node's Tenancy OCID, User OCID, Key Fingerprint and Region (a plain identifier such as uk-london-1).
5. For the Compartment OCID — required by the list and create actions — open Identity & Security → Compartments and copy the OCID of the compartment whose Exadata resources you want to work with.
6. Store the downloaded private key as a Flomation environment secret (for example exadata_secret) and select it in the node's Private Key (PEM) field; if the key is passphrase-protected, add the passphrase as a secret too and pick it in Private Key Passphrase.

02Cloud

OCI Exadata: Add Storage Capacity

oracle/exadata/cloud_exadata_infrastructure_add_storage · Action

Activate 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.

Returns: tool_result, infrastructure, id, lifecycle_state, work_request_id, success, error

OCI Exadata: Move Cloud Exadata Infrastructure to Compartment

oracle/exadata/cloud_exadata_infrastructure_change_compartment · Action

Move a cloud Exadata infrastructure rack into a different compartment — an asynchronous move returning a work-request id to track.

Returns: tool_result, id, destination_compartment_id, work_request_id, success, error

OCI Exadata: Create Cloud Exadata Infrastructure

oracle/exadata/cloud_exadata_infrastructure_create · Action

Provision 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.

Returns: tool_result, infrastructure, id, lifecycle_state, work_request_id, success, error

OCI Exadata: Delete Cloud Exadata Infrastructure

oracle/exadata/cloud_exadata_infrastructure_delete · Action

Tear down a cloud Exadata infrastructure by OCID. Asynchronous — returns a work-request id you can poll to confirm the teardown.

Returns: tool_result, id, work_request_id, success, error

OCI Exadata: Get Cloud Exadata Infrastructure

oracle/exadata/cloud_exadata_infrastructure_get · Action

Fetch a single cloud Exadata infrastructure by OCID — its shape, compute/storage server counts, capacity and lifecycle state.

Returns: tool_result, infrastructure, id, lifecycle_state, success, error

OCI Exadata: List Cloud Exadata Infrastructures

oracle/exadata/cloud_exadata_infrastructure_list · Action

List the cloud Exadata infrastructures in a compartment. Walks pagination up to a safe cap.

Returns: tool_result, infrastructures, count, truncated, success, error

OCI Exadata: Get Unallocated Resources

oracle/exadata/cloud_exadata_infrastructure_unallocated_resources_get · Action

Report the spare capacity of a cloud Exadata infrastructure — unallocated local storage, OCPUs, memory and Exadata storage still available.

Returns: tool_result, id, display_name, local_storage_gb, ocpus, memory_gb, exadata_storage_tb, success, error

OCI Exadata: Update Cloud Exadata Infrastructure

oracle/exadata/cloud_exadata_infrastructure_update · Action

Update a cloud Exadata infrastructure by OCID — rename it, or scale its compute and storage server counts.

Returns: tool_result, infrastructure, id, lifecycle_state, work_request_id, success, error

OCI Exadata: Add VM to Cloud VM Cluster

oracle/exadata/cloud_vm_cluster_add_vm · Action

Scale 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.

Returns: tool_result, vm_cluster, id, lifecycle_state, work_request_id, success, error

OCI Exadata: Move Cloud VM Cluster to Compartment

oracle/exadata/cloud_vm_cluster_change_compartment · Action

Move a cloud VM cluster and its dependent resources to another compartment — asynchronous, returns a work-request id to track.

Returns: tool_result, id, destination_compartment_id, work_request_id, success, error

OCI Exadata: Create Cloud VM Cluster

oracle/exadata/cloud_vm_cluster_create · Action

Provision 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.

Returns: tool_result, vm_cluster, id, lifecycle_state, work_request_id, success, error

OCI Exadata: Delete Cloud VM Cluster

oracle/exadata/cloud_vm_cluster_delete · Action

Terminate a cloud VM cluster by OCID. Asynchronous — returns a work-request id; poll until the cluster is gone.

Returns: tool_result, id, work_request_id, success, error

OCI Exadata: Get Cloud VM Cluster

oracle/exadata/cloud_vm_cluster_get · Action

Fetch a single cloud VM cluster by OCID — its shape, host, CPU cores, listener port and lifecycle state.

Returns: tool_result, vm_cluster, id, lifecycle_state, success, error

OCI Exadata: Get VM Cluster IORM Config

oracle/exadata/cloud_vm_cluster_iorm_config_get · Action

Fetch the I/O Resource Management (IORM) configuration for a cloud VM cluster — its objective, lifecycle state and per-database share plans.

Returns: tool_result, lifecycle_state, objective, db_plans, success, error

OCI Exadata: List Cloud VM Clusters

oracle/exadata/cloud_vm_cluster_list · Action

List the cloud VM clusters in a compartment, optionally narrowed to one cloud Exadata infrastructure. Walks pagination up to a safe cap.

Returns: tool_result, vm_clusters, count, truncated, success, error

OCI Exadata: Remove VM from Cloud VM Cluster

oracle/exadata/cloud_vm_cluster_remove_vm · Action

Remove one or more DB servers' virtual machines from a cloud VM cluster — asynchronous, returns the cluster in UPDATING plus a work-request id.

Returns: tool_result, vm_cluster, id, lifecycle_state, work_request_id, success, error

OCI Exadata: Update Cloud VM Cluster

oracle/exadata/cloud_vm_cluster_update · Action

Rename a cloud VM cluster or scale its total CPU core count. Asynchronous — poll Get Cloud VM Cluster until it settles back to AVAILABLE.

Returns: tool_result, vm_cluster, id, lifecycle_state, work_request_id, success, error

03Db

OCI Exadata: DB Node Action

oracle/exadata/db_node_action · Action

Start, 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.

Returns: tool_result, db_node, id, lifecycle_state, work_request_id, success, error

OCI Exadata: Get DB Node

oracle/exadata/db_node_get · Action

Fetch a single Exadata DB node by OCID — its hostname, DB system, fault domain and lifecycle state.

Returns: tool_result, db_node, id, lifecycle_state, success, error

OCI Exadata: List DB Nodes

oracle/exadata/db_node_list · Action

List the DB nodes of a cloud VM cluster (or DB system) in a compartment. Walks pagination up to a safe cap.

Returns: tool_result, db_nodes, count, truncated, success, error

OCI Exadata: Update DB Node

oracle/exadata/db_node_update · Action

Update 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.

Returns: tool_result, db_node, id, lifecycle_state, work_request_id, success, error

OCI Exadata: Get DB Server

oracle/exadata/db_server_get · Action

Fetch a single Exadata infrastructure DB server by OCID — its shape, CPU/memory capacity and lifecycle state.

Returns: tool_result, db_server, id, lifecycle_state, success, error

OCI Exadata: List DB Servers

oracle/exadata/db_server_list · Action

List the database servers on a cloud Exadata infrastructure. Walks pagination up to a safe cap.

Returns: tool_result, db_servers, count, truncated, success, error

04Maintenance

OCI Exadata: Create Maintenance Run

oracle/exadata/maintenance_run_create · Action

Schedule 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.

Returns: tool_result, maintenance_run, id, lifecycle_state, success, error

OCI Exadata: Get Maintenance Run

oracle/exadata/maintenance_run_get · Action

Fetch a single Exadata maintenance run by OCID — its maintenance type, target resource, schedule and lifecycle state.

Returns: tool_result, maintenance_run, id, lifecycle_state, success, error

OCI Exadata: List Maintenance Runs

oracle/exadata/maintenance_run_list · Action

List the maintenance runs in a compartment, optionally filtered to one target resource. Walks pagination up to a safe cap.

Returns: tool_result, maintenance_runs, count, truncated, success, error

OCI Exadata: Update Maintenance Run

oracle/exadata/maintenance_run_update · Action

Modify a scheduled Exadata maintenance run — reschedule it, enable or skip it, start patching now, or switch its patching mode.

Returns: tool_result, maintenance_run, id, lifecycle_state, success, error

05Notes & Limitations

Behaviours and constraints worth knowing before you build with these nodes.

• Provisioning and scaling actions run asynchronously — each returns a work-request id and leaves the resource in a transitional state, so poll the matching Get action until its lifecycle_state reads AVAILABLE before a later step depends on it, and teardown actions likewise return a work-request id you can poll until the resource is gone.
• Create and Delete on cloud Exadata infrastructure stand up and tear down a dedicated rack of physical compute and storage servers and carry the cost that comes with dedicated hardware, so treat them as high-impact operations rather than routine steps.
• Add Storage only activates storage servers already installed in the rack, making existing capacity available to VM clusters rather than expanding the rack beyond the servers it was built with.
• List actions walk paginated results only up to a fixed safety cap, so in a very large compartment the returned set can be truncated rather than exhaustive.
• This node manages Exadata Database Service on Dedicated Infrastructure only — it does not cover Autonomous Database on Exadata, Exadata Cloud@Customer or Exadata Database Service on Exascale Infrastructure.
• A newly added API signing key can take a minute or two to become active in Oracle Cloud, so a run attempted immediately after connecting may fail authentication until the key propagates.