oci logo
Oracle Cloud Infrastructure v0.6.0, Jan 23 23

oci.Database.getCloudAutonomousVmCluster

This data source provides details about a specific Cloud Autonomous Vm Cluster resource in Oracle Cloud Infrastructure Database service.

Gets information about the specified Autonomous Exadata VM cluster in the Oracle cloud. For Exadata Cloud@Custustomer systems, see GetAutonomousVmCluster .

Example Usage

using System.Collections.Generic;
using Pulumi;
using Oci = Pulumi.Oci;

return await Deployment.RunAsync(() => 
{
    var testCloudAutonomousVmCluster = Oci.Database.GetCloudAutonomousVmCluster.Invoke(new()
    {
        CloudAutonomousVmClusterId = oci_database_cloud_autonomous_vm_cluster.Test_cloud_autonomous_vm_cluster.Id,
    });

});
package main

import (
	"github.com/pulumi/pulumi-oci/sdk/go/oci/Database"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := Database.GetCloudAutonomousVmCluster(ctx, &database.GetCloudAutonomousVmClusterArgs{
			CloudAutonomousVmClusterId: oci_database_cloud_autonomous_vm_cluster.Test_cloud_autonomous_vm_cluster.Id,
		}, nil)
		if err != nil {
			return err
		}
		return nil
	})
}
package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Database.DatabaseFunctions;
import com.pulumi.oci.Database.inputs.GetCloudAutonomousVmClusterArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        final var testCloudAutonomousVmCluster = DatabaseFunctions.getCloudAutonomousVmCluster(GetCloudAutonomousVmClusterArgs.builder()
            .cloudAutonomousVmClusterId(oci_database_cloud_autonomous_vm_cluster.test_cloud_autonomous_vm_cluster().id())
            .build());

    }
}
import pulumi
import pulumi_oci as oci

test_cloud_autonomous_vm_cluster = oci.Database.get_cloud_autonomous_vm_cluster(cloud_autonomous_vm_cluster_id=oci_database_cloud_autonomous_vm_cluster["test_cloud_autonomous_vm_cluster"]["id"])
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";

const testCloudAutonomousVmCluster = oci.Database.getCloudAutonomousVmCluster({
    cloudAutonomousVmClusterId: oci_database_cloud_autonomous_vm_cluster.test_cloud_autonomous_vm_cluster.id,
});
variables:
  testCloudAutonomousVmCluster:
    fn::invoke:
      Function: oci:Database:getCloudAutonomousVmCluster
      Arguments:
        cloudAutonomousVmClusterId: ${oci_database_cloud_autonomous_vm_cluster.test_cloud_autonomous_vm_cluster.id}

Using getCloudAutonomousVmCluster

Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.

function getCloudAutonomousVmCluster(args: GetCloudAutonomousVmClusterArgs, opts?: InvokeOptions): Promise<GetCloudAutonomousVmClusterResult>
function getCloudAutonomousVmClusterOutput(args: GetCloudAutonomousVmClusterOutputArgs, opts?: InvokeOptions): Output<GetCloudAutonomousVmClusterResult>
def get_cloud_autonomous_vm_cluster(cloud_autonomous_vm_cluster_id: Optional[str] = None,
                                    opts: Optional[InvokeOptions] = None) -> GetCloudAutonomousVmClusterResult
def get_cloud_autonomous_vm_cluster_output(cloud_autonomous_vm_cluster_id: Optional[pulumi.Input[str]] = None,
                                    opts: Optional[InvokeOptions] = None) -> Output[GetCloudAutonomousVmClusterResult]
func GetCloudAutonomousVmCluster(ctx *Context, args *GetCloudAutonomousVmClusterArgs, opts ...InvokeOption) (*GetCloudAutonomousVmClusterResult, error)
func GetCloudAutonomousVmClusterOutput(ctx *Context, args *GetCloudAutonomousVmClusterOutputArgs, opts ...InvokeOption) GetCloudAutonomousVmClusterResultOutput

> Note: This function is named GetCloudAutonomousVmCluster in the Go SDK.

public static class GetCloudAutonomousVmCluster 
{
    public static Task<GetCloudAutonomousVmClusterResult> InvokeAsync(GetCloudAutonomousVmClusterArgs args, InvokeOptions? opts = null)
    public static Output<GetCloudAutonomousVmClusterResult> Invoke(GetCloudAutonomousVmClusterInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetCloudAutonomousVmClusterResult> getCloudAutonomousVmCluster(GetCloudAutonomousVmClusterArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
  function: oci:Database/getCloudAutonomousVmCluster:getCloudAutonomousVmCluster
  arguments:
    # arguments dictionary

The following arguments are supported:

CloudAutonomousVmClusterId string

The Cloud VM cluster OCID.

CloudAutonomousVmClusterId string

The Cloud VM cluster OCID.

cloudAutonomousVmClusterId String

The Cloud VM cluster OCID.

cloudAutonomousVmClusterId string

The Cloud VM cluster OCID.

cloud_autonomous_vm_cluster_id str

The Cloud VM cluster OCID.

cloudAutonomousVmClusterId String

The Cloud VM cluster OCID.

getCloudAutonomousVmCluster Result

The following output properties are available:

AutonomousDataStorageSizeInTbs double

The data disk group size allocated for Autonomous Databases, in TBs.

AvailabilityDomain string

The name of the availability domain that the cloud Autonomous VM cluster is located in.

AvailableAutonomousDataStorageSizeInTbs double

The data disk group size available for Autonomous Databases, in TBs.

AvailableContainerDatabases int

The number of Autonomous Container Databases that can be created with the currently available local storage.

AvailableCpus double

CPU cores available for allocation to Autonomous Databases.

CloudAutonomousVmClusterId string
CloudExadataInfrastructureId string

The OCID of the cloud Exadata infrastructure.

ClusterTimeZone string

The time zone of the Cloud Autonomous VM Cluster.

CompartmentId string

The OCID of the compartment.

CpuCoreCount int

The number of CPU cores on the cloud Autonomous VM cluster.

CpuCoreCountPerNode int

The number of OCPU cores enabled per VM cluster node.

DataStorageSizeInGb double

The total data storage allocated, in gigabytes (GB).

DataStorageSizeInTbs double

The total data storage allocated, in terabytes (TB).

DbNodeStorageSizeInGbs int

The local node storage allocated in GBs.

DbServers List<string>
DefinedTags Dictionary<string, object>

Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.

Description string

User defined description of the cloud Autonomous VM cluster.

DisplayName string

The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.

Domain string

The domain name for the cloud Autonomous VM cluster.

FreeformTags Dictionary<string, object>

Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}

Hostname string

The hostname for the cloud Autonomous VM cluster.

Id string

The OCID of the Cloud Autonomous VM cluster.

LastMaintenanceRunId string

The OCID of the last maintenance run.

LastUpdateHistoryEntryId string

The OCID of the last maintenance update history. This value is updated when a maintenance update starts.

LicenseModel string

The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of BRING_YOUR_OWN_LICENSE.

LifecycleDetails string

Additional information about the current lifecycle state.

MaintenanceWindowDetails List<GetCloudAutonomousVmClusterMaintenanceWindowDetail>
MaintenanceWindows List<GetCloudAutonomousVmClusterMaintenanceWindow>

The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.

MemoryPerOracleComputeUnitInGbs int

The amount of memory (in GBs) enabled per each OCPU core.

MemorySizeInGbs int

The memory allocated in GBs.

NextMaintenanceRunId string

The OCID of the next maintenance run.

NodeCount int

The number of database servers in the cloud VM cluster.

NsgIds List<string>

The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:

  • A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
OcpuCount double

The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.

ReclaimableCpus double

CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.

Shape string

The model name of the Exadata hardware running the cloud Autonomous VM cluster.

State string

The current state of the cloud Autonomous VM cluster.

SubnetId string

The OCID of the subnet the cloud Autonomous VM Cluster is associated with.

TimeCreated string

The date and time that the cloud Autonomous VM cluster was created.

TimeUpdated string

The last date and time that the cloud Autonomous VM cluster was updated.

TotalContainerDatabases int

The total number of Autonomous Container Databases that can be created with the allocated local storage.

AutonomousDataStorageSizeInTbs float64

The data disk group size allocated for Autonomous Databases, in TBs.

AvailabilityDomain string

The name of the availability domain that the cloud Autonomous VM cluster is located in.

AvailableAutonomousDataStorageSizeInTbs float64

The data disk group size available for Autonomous Databases, in TBs.

AvailableContainerDatabases int

The number of Autonomous Container Databases that can be created with the currently available local storage.

AvailableCpus float64

CPU cores available for allocation to Autonomous Databases.

CloudAutonomousVmClusterId string
CloudExadataInfrastructureId string

The OCID of the cloud Exadata infrastructure.

ClusterTimeZone string

The time zone of the Cloud Autonomous VM Cluster.

CompartmentId string

The OCID of the compartment.

CpuCoreCount int

The number of CPU cores on the cloud Autonomous VM cluster.

CpuCoreCountPerNode int

The number of OCPU cores enabled per VM cluster node.

DataStorageSizeInGb float64

The total data storage allocated, in gigabytes (GB).

DataStorageSizeInTbs float64

The total data storage allocated, in terabytes (TB).

DbNodeStorageSizeInGbs int

The local node storage allocated in GBs.

DbServers []string
DefinedTags map[string]interface{}

Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.

Description string

User defined description of the cloud Autonomous VM cluster.

DisplayName string

The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.

Domain string

The domain name for the cloud Autonomous VM cluster.

FreeformTags map[string]interface{}

Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}

Hostname string

The hostname for the cloud Autonomous VM cluster.

Id string

The OCID of the Cloud Autonomous VM cluster.

LastMaintenanceRunId string

The OCID of the last maintenance run.

LastUpdateHistoryEntryId string

The OCID of the last maintenance update history. This value is updated when a maintenance update starts.

LicenseModel string

The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of BRING_YOUR_OWN_LICENSE.

LifecycleDetails string

Additional information about the current lifecycle state.

MaintenanceWindowDetails []GetCloudAutonomousVmClusterMaintenanceWindowDetail
MaintenanceWindows []GetCloudAutonomousVmClusterMaintenanceWindow

The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.

MemoryPerOracleComputeUnitInGbs int

The amount of memory (in GBs) enabled per each OCPU core.

MemorySizeInGbs int

The memory allocated in GBs.

NextMaintenanceRunId string

The OCID of the next maintenance run.

NodeCount int

The number of database servers in the cloud VM cluster.

NsgIds []string

The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:

  • A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
OcpuCount float64

The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.

ReclaimableCpus float64

CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.

Shape string

The model name of the Exadata hardware running the cloud Autonomous VM cluster.

State string

The current state of the cloud Autonomous VM cluster.

SubnetId string

The OCID of the subnet the cloud Autonomous VM Cluster is associated with.

TimeCreated string

The date and time that the cloud Autonomous VM cluster was created.

TimeUpdated string

The last date and time that the cloud Autonomous VM cluster was updated.

TotalContainerDatabases int

The total number of Autonomous Container Databases that can be created with the allocated local storage.

autonomousDataStorageSizeInTbs Double

The data disk group size allocated for Autonomous Databases, in TBs.

availabilityDomain String

The name of the availability domain that the cloud Autonomous VM cluster is located in.

availableAutonomousDataStorageSizeInTbs Double

The data disk group size available for Autonomous Databases, in TBs.

availableContainerDatabases Integer

The number of Autonomous Container Databases that can be created with the currently available local storage.

availableCpus Double

CPU cores available for allocation to Autonomous Databases.

cloudAutonomousVmClusterId String
cloudExadataInfrastructureId String

The OCID of the cloud Exadata infrastructure.

clusterTimeZone String

The time zone of the Cloud Autonomous VM Cluster.

compartmentId String

The OCID of the compartment.

cpuCoreCount Integer

The number of CPU cores on the cloud Autonomous VM cluster.

cpuCoreCountPerNode Integer

The number of OCPU cores enabled per VM cluster node.

dataStorageSizeInGb Double

The total data storage allocated, in gigabytes (GB).

dataStorageSizeInTbs Double

The total data storage allocated, in terabytes (TB).

dbNodeStorageSizeInGbs Integer

The local node storage allocated in GBs.

dbServers List<String>
definedTags Map<String,Object>

Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.

description String

User defined description of the cloud Autonomous VM cluster.

displayName String

The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.

domain String

The domain name for the cloud Autonomous VM cluster.

freeformTags Map<String,Object>

Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}

hostname String

The hostname for the cloud Autonomous VM cluster.

id String

The OCID of the Cloud Autonomous VM cluster.

lastMaintenanceRunId String

The OCID of the last maintenance run.

lastUpdateHistoryEntryId String

The OCID of the last maintenance update history. This value is updated when a maintenance update starts.

licenseModel String

The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of BRING_YOUR_OWN_LICENSE.

lifecycleDetails String

Additional information about the current lifecycle state.

maintenanceWindowDetails List<GetCloudAutonomousVmClusterMaintenanceWindowDetail>
maintenanceWindows List<GetCloudAutonomousVmClusterMaintenanceWindow>

The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.

memoryPerOracleComputeUnitInGbs Integer

The amount of memory (in GBs) enabled per each OCPU core.

memorySizeInGbs Integer

The memory allocated in GBs.

nextMaintenanceRunId String

The OCID of the next maintenance run.

nodeCount Integer

The number of database servers in the cloud VM cluster.

nsgIds List<String>

The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:

  • A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
ocpuCount Double

The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.

reclaimableCpus Double

CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.

shape String

The model name of the Exadata hardware running the cloud Autonomous VM cluster.

state String

The current state of the cloud Autonomous VM cluster.

subnetId String

The OCID of the subnet the cloud Autonomous VM Cluster is associated with.

timeCreated String

The date and time that the cloud Autonomous VM cluster was created.

timeUpdated String

The last date and time that the cloud Autonomous VM cluster was updated.

totalContainerDatabases Integer

The total number of Autonomous Container Databases that can be created with the allocated local storage.

autonomousDataStorageSizeInTbs number

The data disk group size allocated for Autonomous Databases, in TBs.

availabilityDomain string

The name of the availability domain that the cloud Autonomous VM cluster is located in.

availableAutonomousDataStorageSizeInTbs number

The data disk group size available for Autonomous Databases, in TBs.

availableContainerDatabases number

The number of Autonomous Container Databases that can be created with the currently available local storage.

availableCpus number

CPU cores available for allocation to Autonomous Databases.

cloudAutonomousVmClusterId string
cloudExadataInfrastructureId string

The OCID of the cloud Exadata infrastructure.

clusterTimeZone string

The time zone of the Cloud Autonomous VM Cluster.

compartmentId string

The OCID of the compartment.

cpuCoreCount number

The number of CPU cores on the cloud Autonomous VM cluster.

cpuCoreCountPerNode number

The number of OCPU cores enabled per VM cluster node.

dataStorageSizeInGb number

The total data storage allocated, in gigabytes (GB).

dataStorageSizeInTbs number

The total data storage allocated, in terabytes (TB).

dbNodeStorageSizeInGbs number

The local node storage allocated in GBs.

dbServers string[]
definedTags {[key: string]: any}

Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.

description string

User defined description of the cloud Autonomous VM cluster.

displayName string

The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.

domain string

The domain name for the cloud Autonomous VM cluster.

freeformTags {[key: string]: any}

Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}

hostname string

The hostname for the cloud Autonomous VM cluster.

id string

The OCID of the Cloud Autonomous VM cluster.

lastMaintenanceRunId string

The OCID of the last maintenance run.

lastUpdateHistoryEntryId string

The OCID of the last maintenance update history. This value is updated when a maintenance update starts.

licenseModel string

The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of BRING_YOUR_OWN_LICENSE.

lifecycleDetails string

Additional information about the current lifecycle state.

maintenanceWindowDetails GetCloudAutonomousVmClusterMaintenanceWindowDetail[]
maintenanceWindows GetCloudAutonomousVmClusterMaintenanceWindow[]

The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.

memoryPerOracleComputeUnitInGbs number

The amount of memory (in GBs) enabled per each OCPU core.

memorySizeInGbs number

The memory allocated in GBs.

nextMaintenanceRunId string

The OCID of the next maintenance run.

nodeCount number

The number of database servers in the cloud VM cluster.

nsgIds string[]

The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:

  • A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
ocpuCount number

The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.

reclaimableCpus number

CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.

shape string

The model name of the Exadata hardware running the cloud Autonomous VM cluster.

state string

The current state of the cloud Autonomous VM cluster.

subnetId string

The OCID of the subnet the cloud Autonomous VM Cluster is associated with.

timeCreated string

The date and time that the cloud Autonomous VM cluster was created.

timeUpdated string

The last date and time that the cloud Autonomous VM cluster was updated.

totalContainerDatabases number

The total number of Autonomous Container Databases that can be created with the allocated local storage.

autonomous_data_storage_size_in_tbs float

The data disk group size allocated for Autonomous Databases, in TBs.

availability_domain str

The name of the availability domain that the cloud Autonomous VM cluster is located in.

available_autonomous_data_storage_size_in_tbs float

The data disk group size available for Autonomous Databases, in TBs.

available_container_databases int

The number of Autonomous Container Databases that can be created with the currently available local storage.

available_cpus float

CPU cores available for allocation to Autonomous Databases.

cloud_autonomous_vm_cluster_id str
cloud_exadata_infrastructure_id str

The OCID of the cloud Exadata infrastructure.

cluster_time_zone str

The time zone of the Cloud Autonomous VM Cluster.

compartment_id str

The OCID of the compartment.

cpu_core_count int

The number of CPU cores on the cloud Autonomous VM cluster.

cpu_core_count_per_node int

The number of OCPU cores enabled per VM cluster node.

data_storage_size_in_gb float

The total data storage allocated, in gigabytes (GB).

data_storage_size_in_tbs float

The total data storage allocated, in terabytes (TB).

db_node_storage_size_in_gbs int

The local node storage allocated in GBs.

db_servers Sequence[str]
defined_tags Mapping[str, Any]

Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.

description str

User defined description of the cloud Autonomous VM cluster.

display_name str

The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.

domain str

The domain name for the cloud Autonomous VM cluster.

freeform_tags Mapping[str, Any]

Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}

hostname str

The hostname for the cloud Autonomous VM cluster.

id str

The OCID of the Cloud Autonomous VM cluster.

last_maintenance_run_id str

The OCID of the last maintenance run.

last_update_history_entry_id str

The OCID of the last maintenance update history. This value is updated when a maintenance update starts.

license_model str

The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of BRING_YOUR_OWN_LICENSE.

lifecycle_details str

Additional information about the current lifecycle state.

maintenance_window_details GetCloudAutonomousVmClusterMaintenanceWindowDetail]
maintenance_windows GetCloudAutonomousVmClusterMaintenanceWindow]

The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.

memory_per_oracle_compute_unit_in_gbs int

The amount of memory (in GBs) enabled per each OCPU core.

memory_size_in_gbs int

The memory allocated in GBs.

next_maintenance_run_id str

The OCID of the next maintenance run.

node_count int

The number of database servers in the cloud VM cluster.

nsg_ids Sequence[str]

The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:

  • A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
ocpu_count float

The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.

reclaimable_cpus float

CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.

shape str

The model name of the Exadata hardware running the cloud Autonomous VM cluster.

state str

The current state of the cloud Autonomous VM cluster.

subnet_id str

The OCID of the subnet the cloud Autonomous VM Cluster is associated with.

time_created str

The date and time that the cloud Autonomous VM cluster was created.

time_updated str

The last date and time that the cloud Autonomous VM cluster was updated.

total_container_databases int

The total number of Autonomous Container Databases that can be created with the allocated local storage.

autonomousDataStorageSizeInTbs Number

The data disk group size allocated for Autonomous Databases, in TBs.

availabilityDomain String

The name of the availability domain that the cloud Autonomous VM cluster is located in.

availableAutonomousDataStorageSizeInTbs Number

The data disk group size available for Autonomous Databases, in TBs.

availableContainerDatabases Number

The number of Autonomous Container Databases that can be created with the currently available local storage.

availableCpus Number

CPU cores available for allocation to Autonomous Databases.

cloudAutonomousVmClusterId String
cloudExadataInfrastructureId String

The OCID of the cloud Exadata infrastructure.

clusterTimeZone String

The time zone of the Cloud Autonomous VM Cluster.

compartmentId String

The OCID of the compartment.

cpuCoreCount Number

The number of CPU cores on the cloud Autonomous VM cluster.

cpuCoreCountPerNode Number

The number of OCPU cores enabled per VM cluster node.

dataStorageSizeInGb Number

The total data storage allocated, in gigabytes (GB).

dataStorageSizeInTbs Number

The total data storage allocated, in terabytes (TB).

dbNodeStorageSizeInGbs Number

The local node storage allocated in GBs.

dbServers List<String>
definedTags Map<Any>

Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.

description String

User defined description of the cloud Autonomous VM cluster.

displayName String

The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.

domain String

The domain name for the cloud Autonomous VM cluster.

freeformTags Map<Any>

Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}

hostname String

The hostname for the cloud Autonomous VM cluster.

id String

The OCID of the Cloud Autonomous VM cluster.

lastMaintenanceRunId String

The OCID of the last maintenance run.

lastUpdateHistoryEntryId String

The OCID of the last maintenance update history. This value is updated when a maintenance update starts.

licenseModel String

The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of BRING_YOUR_OWN_LICENSE.

lifecycleDetails String

Additional information about the current lifecycle state.

maintenanceWindowDetails List<Property Map>
maintenanceWindows List<Property Map>

The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.

memoryPerOracleComputeUnitInGbs Number

The amount of memory (in GBs) enabled per each OCPU core.

memorySizeInGbs Number

The memory allocated in GBs.

nextMaintenanceRunId String

The OCID of the next maintenance run.

nodeCount Number

The number of database servers in the cloud VM cluster.

nsgIds List<String>

The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:

  • A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
ocpuCount Number

The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.

reclaimableCpus Number

CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.

shape String

The model name of the Exadata hardware running the cloud Autonomous VM cluster.

state String

The current state of the cloud Autonomous VM cluster.

subnetId String

The OCID of the subnet the cloud Autonomous VM Cluster is associated with.

timeCreated String

The date and time that the cloud Autonomous VM cluster was created.

timeUpdated String

The last date and time that the cloud Autonomous VM cluster was updated.

totalContainerDatabases Number

The total number of Autonomous Container Databases that can be created with the allocated local storage.

Supporting Types

GetCloudAutonomousVmClusterMaintenanceWindow

CustomActionTimeoutInMins int

Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).

DaysOfWeeks List<GetCloudAutonomousVmClusterMaintenanceWindowDaysOfWeek>

Days during the week when maintenance should be performed.

HoursOfDays List<int>

The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are

  • 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
IsCustomActionTimeoutEnabled bool

If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.

IsMonthlyPatchingEnabled bool

If true, enables the monthly patching option.

LeadTimeInWeeks int

Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.

Months List<GetCloudAutonomousVmClusterMaintenanceWindowMonth>

Months during the year when maintenance should be performed.

PatchingMode string

Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.

Preference string

The maintenance window scheduling preference.

WeeksOfMonths List<int>

Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.

CustomActionTimeoutInMins int

Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).

DaysOfWeeks []GetCloudAutonomousVmClusterMaintenanceWindowDaysOfWeek

Days during the week when maintenance should be performed.

HoursOfDays []int

The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are

  • 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
IsCustomActionTimeoutEnabled bool

If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.

IsMonthlyPatchingEnabled bool

If true, enables the monthly patching option.

LeadTimeInWeeks int

Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.

Months []GetCloudAutonomousVmClusterMaintenanceWindowMonth

Months during the year when maintenance should be performed.

PatchingMode string

Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.

Preference string

The maintenance window scheduling preference.

WeeksOfMonths []int

Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.

customActionTimeoutInMins Integer

Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).

daysOfWeeks List<GetCloudAutonomousVmClusterMaintenanceWindowDaysOfWeek>

Days during the week when maintenance should be performed.

hoursOfDays List<Integer>

The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are

  • 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
isCustomActionTimeoutEnabled Boolean

If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.

isMonthlyPatchingEnabled Boolean

If true, enables the monthly patching option.

leadTimeInWeeks Integer

Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.

months List<GetCloudAutonomousVmClusterMaintenanceWindowMonth>

Months during the year when maintenance should be performed.

patchingMode String

Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.

preference String

The maintenance window scheduling preference.

weeksOfMonths List<Integer>

Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.

customActionTimeoutInMins number

Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).

daysOfWeeks GetCloudAutonomousVmClusterMaintenanceWindowDaysOfWeek[]

Days during the week when maintenance should be performed.

hoursOfDays number[]

The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are

  • 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
isCustomActionTimeoutEnabled boolean

If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.

isMonthlyPatchingEnabled boolean

If true, enables the monthly patching option.

leadTimeInWeeks number

Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.

months GetCloudAutonomousVmClusterMaintenanceWindowMonth[]

Months during the year when maintenance should be performed.

patchingMode string

Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.

preference string

The maintenance window scheduling preference.

weeksOfMonths number[]

Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.

custom_action_timeout_in_mins int

Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).

days_of_weeks GetCloudAutonomousVmClusterMaintenanceWindowDaysOfWeek]

Days during the week when maintenance should be performed.

hours_of_days Sequence[int]

The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are

  • 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
is_custom_action_timeout_enabled bool

If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.

is_monthly_patching_enabled bool

If true, enables the monthly patching option.

lead_time_in_weeks int

Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.

months GetCloudAutonomousVmClusterMaintenanceWindowMonth]

Months during the year when maintenance should be performed.

patching_mode str

Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.

preference str

The maintenance window scheduling preference.

weeks_of_months Sequence[int]

Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.

customActionTimeoutInMins Number

Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).

daysOfWeeks List<Property Map>

Days during the week when maintenance should be performed.

hoursOfDays List<Number>

The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are

  • 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
isCustomActionTimeoutEnabled Boolean

If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.

isMonthlyPatchingEnabled Boolean

If true, enables the monthly patching option.

leadTimeInWeeks Number

Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.

months List<Property Map>

Months during the year when maintenance should be performed.

patchingMode String

Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.

preference String

The maintenance window scheduling preference.

weeksOfMonths List<Number>

Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.

GetCloudAutonomousVmClusterMaintenanceWindowDaysOfWeek

Name string

Name of the month of the year.

Name string

Name of the month of the year.

name String

Name of the month of the year.

name string

Name of the month of the year.

name str

Name of the month of the year.

name String

Name of the month of the year.

GetCloudAutonomousVmClusterMaintenanceWindowDetail

CustomActionTimeoutInMins int

Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).

DaysOfWeeks List<GetCloudAutonomousVmClusterMaintenanceWindowDetailDaysOfWeek>

Days during the week when maintenance should be performed.

HoursOfDays List<int>

The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are

  • 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
IsCustomActionTimeoutEnabled bool

If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.

IsMonthlyPatchingEnabled bool

If true, enables the monthly patching option.

LeadTimeInWeeks int

Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.

Months List<GetCloudAutonomousVmClusterMaintenanceWindowDetailMonth>

Months during the year when maintenance should be performed.

PatchingMode string

Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.

Preference string

The maintenance window scheduling preference.

WeeksOfMonths List<int>

Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.

CustomActionTimeoutInMins int

Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).

DaysOfWeeks []GetCloudAutonomousVmClusterMaintenanceWindowDetailDaysOfWeek

Days during the week when maintenance should be performed.

HoursOfDays []int

The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are

  • 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
IsCustomActionTimeoutEnabled bool

If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.

IsMonthlyPatchingEnabled bool

If true, enables the monthly patching option.

LeadTimeInWeeks int

Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.

Months []GetCloudAutonomousVmClusterMaintenanceWindowDetailMonth

Months during the year when maintenance should be performed.

PatchingMode string

Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.

Preference string

The maintenance window scheduling preference.

WeeksOfMonths []int

Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.

customActionTimeoutInMins Integer

Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).

daysOfWeeks List<GetCloudAutonomousVmClusterMaintenanceWindowDetailDaysOfWeek>

Days during the week when maintenance should be performed.

hoursOfDays List<Integer>

The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are

  • 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
isCustomActionTimeoutEnabled Boolean

If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.

isMonthlyPatchingEnabled Boolean

If true, enables the monthly patching option.

leadTimeInWeeks Integer

Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.

months List<GetCloudAutonomousVmClusterMaintenanceWindowDetailMonth>

Months during the year when maintenance should be performed.

patchingMode String

Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.

preference String

The maintenance window scheduling preference.

weeksOfMonths List<Integer>

Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.

customActionTimeoutInMins number

Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).

daysOfWeeks GetCloudAutonomousVmClusterMaintenanceWindowDetailDaysOfWeek[]

Days during the week when maintenance should be performed.

hoursOfDays number[]

The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are

  • 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
isCustomActionTimeoutEnabled boolean

If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.

isMonthlyPatchingEnabled boolean

If true, enables the monthly patching option.

leadTimeInWeeks number

Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.

months GetCloudAutonomousVmClusterMaintenanceWindowDetailMonth[]

Months during the year when maintenance should be performed.

patchingMode string

Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.

preference string

The maintenance window scheduling preference.

weeksOfMonths number[]

Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.

custom_action_timeout_in_mins int

Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).

days_of_weeks GetCloudAutonomousVmClusterMaintenanceWindowDetailDaysOfWeek]

Days during the week when maintenance should be performed.

hours_of_days Sequence[int]

The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are

  • 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
is_custom_action_timeout_enabled bool

If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.

is_monthly_patching_enabled bool

If true, enables the monthly patching option.

lead_time_in_weeks int

Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.

months GetCloudAutonomousVmClusterMaintenanceWindowDetailMonth]

Months during the year when maintenance should be performed.

patching_mode str

Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.

preference str

The maintenance window scheduling preference.

weeks_of_months Sequence[int]

Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.

customActionTimeoutInMins Number

Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).

daysOfWeeks List<Property Map>

Days during the week when maintenance should be performed.

hoursOfDays List<Number>

The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are

  • 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
isCustomActionTimeoutEnabled Boolean

If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.

isMonthlyPatchingEnabled Boolean

If true, enables the monthly patching option.

leadTimeInWeeks Number

Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.

months List<Property Map>

Months during the year when maintenance should be performed.

patchingMode String

Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.

preference String

The maintenance window scheduling preference.

weeksOfMonths List<Number>

Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.

GetCloudAutonomousVmClusterMaintenanceWindowDetailDaysOfWeek

Name string

Name of the month of the year.

Name string

Name of the month of the year.

name String

Name of the month of the year.

name string

Name of the month of the year.

name str

Name of the month of the year.

name String

Name of the month of the year.

GetCloudAutonomousVmClusterMaintenanceWindowDetailMonth

Name string

Name of the month of the year.

Name string

Name of the month of the year.

name String

Name of the month of the year.

name string

Name of the month of the year.

name str

Name of the month of the year.

name String

Name of the month of the year.

GetCloudAutonomousVmClusterMaintenanceWindowMonth

Name string

Name of the month of the year.

Name string

Name of the month of the year.

name String

Name of the month of the year.

name string

Name of the month of the year.

name str

Name of the month of the year.

name String

Name of the month of the year.

Package Details

Repository
oci pulumi/pulumi-oci
License
Apache-2.0
Notes

This Pulumi package is based on the oci Terraform Provider.