ORACLE CLOUD
MySQL HeatWave actions
17 actions you can wire into a flow, alongside everything else in the Oracle Cloud integration.
Every MySQL HeatWave action
- OCI MySQL: Add HeatWave ClusterAttach a HeatWave cluster to a MySQL DB system for in-memory analytics. Returns a work-request id: poll until the cluster is ACTIVE.
- OCI MySQL: Change DB System CompartmentAttempt to move a MySQL HeatWave DB system to another compartment: reports that OCI provides no such operation for DB systems.
- OCI MySQL: Create BackupTake an on-demand backup of a MySQL HeatWave DB system. Returns the backup in a CREATING state plus a work-request id: poll Get Backup until ACTIVE.
- OCI MySQL: Create DB SystemProvision a MySQL HeatWave DB system in a compartment: pick the shape, subnet and admin credentials. Returns a work-request id; the DB system starts in a CREATING state, so poll Get DB System until ACTIVE.
- OCI MySQL: Delete BackupDelete a MySQL HeatWave backup by its OCID. Returns a work-request id: poll the work request until it completes to confirm removal.
- OCI MySQL: Delete DB SystemDelete a MySQL HeatWave DB system by its OCID. Asynchronous: it moves to DELETING and returns a work-request id to poll.
- OCI MySQL: Delete HeatWave ClusterDelete the HeatWave cluster attached to a MySQL DB system. Returns a work-request id: poll it until the removal completes.
- OCI MySQL: Get BackupFetch a single MySQL HeatWave backup by its OCID: its type, source DB system, size and lifecycle state.
- OCI MySQL: Get ConfigurationFetch a single MySQL HeatWave configuration by its OCID: its shape, type and lifecycle state.
- OCI MySQL: Get DB SystemFetch a single MySQL HeatWave DB system by its OCID: its shape, version, endpoints and lifecycle state.
- OCI MySQL: Get HeatWave ClusterFetch the HeatWave cluster attached to a MySQL DB System: its shape, node count and lifecycle state.
- OCI MySQL: List BackupsList the MySQL HeatWave backups in a compartment. Optionally filter by DB system, exact display name or lifecycle state. Walks pagination up to a safe cap.
- OCI MySQL: List ConfigurationsList the MySQL configurations in a compartment. Optionally filter by exact display name, type (DEFAULT or CUSTOM) or shape name. Walks pagination up to a safe cap.
- OCI MySQL: List DB SystemsList the MySQL HeatWave DB systems in a compartment. Optionally filter by exact display name or lifecycle state. Walks pagination up to a safe cap.
- OCI MySQL: Start DB SystemStart a stopped MySQL HeatWave DB system by its OCID. Asynchronous: returns a work-request id you can poll until the DB system is ACTIVE.
- OCI MySQL: Stop DB SystemStop a running MySQL HeatWave DB system by its OCID, choosing the InnoDB shutdown mode. Asynchronous: returns a work-request id you can poll until the DB system is INACTIVE.
- OCI MySQL: Update DB SystemPartially update a MySQL HeatWave DB system: change only the display name or description you supply; blank fields are left unchanged. Asynchronous: returns a work-request id to poll.
Also in Oracle Cloud
API Gateway18 actionsAutonomous Database24 actionsBastion10 actionsBlock Volumes69 actionsCertificates20 actionsCloud Guard20 actionsCompute17 actionsContainer Engine44 actionsData Catalog26 actionsData Flow20 actionsDNS54 actionsDocument Understanding12 actionsEmail19 actionsEvents6 actionsExadata27 actionsFile Storage49 actionsFunctions15 actionsGenerative AI14 actionsIdentity90 actionsLanguage16 actionsLoad Balancer61 actionsLogging17 actionsMonitoring15 actionsNetwork Load Balancer33 actionsNetworking62 actionsNoSQL Database16 actionsNotifications16 actionsObject Storage15 actionsQueue19 actionsSpeech13 actionsStreaming30 actionsVault50 actionsVision10 actionsVulnerability Scanning19 actionsWeb Application Acceleration13 actionsWeb Application Firewall17 actions
Put MySQL HeatWave in a flow
These actions sit on the same canvas as every other integration, so a MySQL HeatWave step can follow a form, a schedule or a message without any glue code.
