Oracle Cloud Infrastructure v2.33.0 published on Thursday, May 1, 2025 by Pulumi
oci.Database.getCloudAutonomousVmCluster
Explore with Pulumi AI
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
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testCloudAutonomousVmCluster = oci.Database.getCloudAutonomousVmCluster({
    cloudAutonomousVmClusterId: testCloudAutonomousVmClusterOciDatabaseCloudAutonomousVmCluster.id,
});
import pulumi
import pulumi_oci as oci
test_cloud_autonomous_vm_cluster = oci.Database.get_cloud_autonomous_vm_cluster(cloud_autonomous_vm_cluster_id=test_cloud_autonomous_vm_cluster_oci_database_cloud_autonomous_vm_cluster["id"])
package main
import (
	"github.com/pulumi/pulumi-oci/sdk/v2/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: testCloudAutonomousVmClusterOciDatabaseCloudAutonomousVmCluster.Id,
		}, nil)
		if err != nil {
			return err
		}
		return nil
	})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Oci = Pulumi.Oci;
return await Deployment.RunAsync(() => 
{
    var testCloudAutonomousVmCluster = Oci.Database.GetCloudAutonomousVmCluster.Invoke(new()
    {
        CloudAutonomousVmClusterId = testCloudAutonomousVmClusterOciDatabaseCloudAutonomousVmCluster.Id,
    });
});
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(testCloudAutonomousVmClusterOciDatabaseCloudAutonomousVmCluster.id())
            .build());
    }
}
variables:
  testCloudAutonomousVmCluster:
    fn::invoke:
      function: oci:Database:getCloudAutonomousVmCluster
      arguments:
        cloudAutonomousVmClusterId: ${testCloudAutonomousVmClusterOciDatabaseCloudAutonomousVmCluster.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 LookupCloudAutonomousVmCluster(ctx *Context, args *LookupCloudAutonomousVmClusterArgs, opts ...InvokeOption) (*LookupCloudAutonomousVmClusterResult, error)
func LookupCloudAutonomousVmClusterOutput(ctx *Context, args *LookupCloudAutonomousVmClusterOutputArgs, opts ...InvokeOption) LookupCloudAutonomousVmClusterResultOutput> Note: This function is named LookupCloudAutonomousVmCluster 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)
public static Output<GetCloudAutonomousVmClusterResult> getCloudAutonomousVmCluster(GetCloudAutonomousVmClusterArgs args, InvokeOptions options)
fn::invoke:
  function: oci:Database/getCloudAutonomousVmCluster:getCloudAutonomousVmCluster
  arguments:
    # arguments dictionaryThe following arguments are supported:
- CloudAutonomous stringVm Cluster Id 
- The Cloud VM cluster OCID.
- CloudAutonomous stringVm Cluster Id 
- The Cloud VM cluster OCID.
- cloudAutonomous StringVm Cluster Id 
- The Cloud VM cluster OCID.
- cloudAutonomous stringVm Cluster Id 
- The Cloud VM cluster OCID.
- cloud_autonomous_ strvm_ cluster_ id 
- The Cloud VM cluster OCID.
- cloudAutonomous StringVm Cluster Id 
- The Cloud VM cluster OCID.
getCloudAutonomousVmCluster Result
The following output properties are available:
- AutonomousData doubleStorage Percentage 
- The percentage of the data storage used for the Autonomous Databases in an Autonomous VM Cluster.
- AutonomousData doubleStorage Size In Tbs 
- 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.
- AvailableAutonomous doubleData Storage Size In Tbs 
- The data disk group size available for Autonomous Databases, in TBs.
- AvailableContainer intDatabases 
- 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.
- CloudAutonomous stringVm Cluster Id 
- CloudExadata stringInfrastructure Id 
- The OCID of the cloud Exadata infrastructure.
- ClusterTime stringZone 
- The time zone of the Cloud Autonomous VM Cluster.
- CompartmentId string
- The OCID of the compartment.
- ComputeModel string
- The compute model of the Cloud Autonomous VM Cluster. ECPU compute model is the recommended model and OCPU compute model is legacy. See Compute Models in Autonomous Database on Dedicated Exadata #Infrastructure for more details.
- CpuCore intCount 
- The number of CPU cores on the cloud Autonomous VM cluster.
- CpuCore intCount Per Node 
- The number of CPU cores enabled per VM cluster node.
- CpuPercentage double
- The percentage of total number of CPUs used in an Autonomous VM Cluster.
- DataStorage doubleSize In Gb 
- The total data storage allocated, in gigabytes (GB).
- DataStorage doubleSize In Tbs 
- The total data storage allocated, in terabytes (TB).
- DbNode intStorage Size In Gbs 
- The local node storage allocated in GBs.
- DbServers List<string>
- The list of OCIDs of the Db servers.
- Dictionary<string, string>
- 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.
- ExadataStorage doubleIn Tbs Lowest Scaled Value 
- The lowest value to which exadataStorage (in TBs) can be scaled down.
- Dictionary<string, string>
- 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.
- IsMtls boolEnabled Vm Cluster 
- Enable mutual TLS(mTLS) authentication for database at time of provisioning a VMCluster. This is applicable to database TLS Certificates only. Default is TLS
- LastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- LastUpdate stringHistory Entry Id 
- 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 services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Oracle Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null. It is already set at the Autonomous Exadata Infrastructure level. When provisioning an [Autonomous Database Serverless] (https://docs.oracle.com/en/cloud/paas/autonomous-database/index.html) database, if a value is not specified, the system defaults the value to BRING_YOUR_OWN_LICENSE. Bring your own license (BYOL) also allows you to select the DB edition using the optional parameter.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- MaintenanceWindow List<GetDetails Cloud Autonomous Vm Cluster Maintenance Window Detail> 
- MaintenanceWindows List<GetCloud Autonomous Vm Cluster Maintenance Window> 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- MaxAcds intLowest Scaled Value 
- The lowest value to which maximum number of ACDs can be scaled down.
- MemoryPer intOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per OCPU or ECPU.
- MemorySize intIn Gbs 
- The memory allocated in GBs.
- NextMaintenance stringRun Id 
- The OCID of the next maintenance run.
- NodeCount int
- The number of database servers in the cloud VM cluster.
- NonProvisionable intAutonomous Container Databases 
- The number of non-provisionable Autonomous Container Databases in an Autonomous 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.
- OcpusLowest intScaled Value 
- The lowest value to which ocpus can be scaled down.
- ProvisionableAutonomous intContainer Databases 
- The number of provisionable Autonomous Container Databases in an Autonomous VM Cluster.
- ProvisionedAutonomous intContainer Databases 
- The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- ProvisionedCpus double
- The number of CPUs provisioned in an Autonomous VM Cluster.
- ReclaimableCpus double
- For Autonomous Databases on Dedicated Exadata Infrastructure:- These are the CPUs that continue to be included in the count of CPUs 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 CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
 
- ReservedCpus double
- The number of CPUs reserved in an Autonomous VM Cluster.
- ScanListener intPort Non Tls 
- The SCAN Listener Non TLS port. Default is 1521.
- ScanListener intPort Tls 
- The SCAN Listenenr TLS port. Default is 2484.
- SecurityAttributes Dictionary<string, string>
- Security Attributes for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {"Oracle-ZPR": {"MaxEgressCount": {"value": "42", "mode": "audit"}}}
- 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.
- TimeDatabase stringSsl Certificate Expires 
- The date and time of Database SSL certificate expiration.
- TimeOrds stringCertificate Expires 
- The date and time of ORDS certificate expiration.
- TimeUpdated string
- The last date and time that the cloud Autonomous VM cluster was updated.
- TotalAutonomous doubleData Storage In Tbs 
- The total data disk group size for Autonomous Databases, in TBs.
- TotalContainer intDatabases 
- The total number of Autonomous Container Databases that can be created with the allocated local storage.
- TotalCpus double
- The total number of CPUs in an Autonomous VM Cluster.
- AutonomousData float64Storage Percentage 
- The percentage of the data storage used for the Autonomous Databases in an Autonomous VM Cluster.
- AutonomousData float64Storage Size In Tbs 
- 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.
- AvailableAutonomous float64Data Storage Size In Tbs 
- The data disk group size available for Autonomous Databases, in TBs.
- AvailableContainer intDatabases 
- 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.
- CloudAutonomous stringVm Cluster Id 
- CloudExadata stringInfrastructure Id 
- The OCID of the cloud Exadata infrastructure.
- ClusterTime stringZone 
- The time zone of the Cloud Autonomous VM Cluster.
- CompartmentId string
- The OCID of the compartment.
- ComputeModel string
- The compute model of the Cloud Autonomous VM Cluster. ECPU compute model is the recommended model and OCPU compute model is legacy. See Compute Models in Autonomous Database on Dedicated Exadata #Infrastructure for more details.
- CpuCore intCount 
- The number of CPU cores on the cloud Autonomous VM cluster.
- CpuCore intCount Per Node 
- The number of CPU cores enabled per VM cluster node.
- CpuPercentage float64
- The percentage of total number of CPUs used in an Autonomous VM Cluster.
- DataStorage float64Size In Gb 
- The total data storage allocated, in gigabytes (GB).
- DataStorage float64Size In Tbs 
- The total data storage allocated, in terabytes (TB).
- DbNode intStorage Size In Gbs 
- The local node storage allocated in GBs.
- DbServers []string
- The list of OCIDs of the Db servers.
- map[string]string
- 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.
- ExadataStorage float64In Tbs Lowest Scaled Value 
- The lowest value to which exadataStorage (in TBs) can be scaled down.
- map[string]string
- 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.
- IsMtls boolEnabled Vm Cluster 
- Enable mutual TLS(mTLS) authentication for database at time of provisioning a VMCluster. This is applicable to database TLS Certificates only. Default is TLS
- LastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- LastUpdate stringHistory Entry Id 
- 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 services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Oracle Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null. It is already set at the Autonomous Exadata Infrastructure level. When provisioning an [Autonomous Database Serverless] (https://docs.oracle.com/en/cloud/paas/autonomous-database/index.html) database, if a value is not specified, the system defaults the value to BRING_YOUR_OWN_LICENSE. Bring your own license (BYOL) also allows you to select the DB edition using the optional parameter.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- MaintenanceWindow []GetDetails Cloud Autonomous Vm Cluster Maintenance Window Detail 
- MaintenanceWindows []GetCloud Autonomous Vm Cluster Maintenance Window 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- MaxAcds intLowest Scaled Value 
- The lowest value to which maximum number of ACDs can be scaled down.
- MemoryPer intOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per OCPU or ECPU.
- MemorySize intIn Gbs 
- The memory allocated in GBs.
- NextMaintenance stringRun Id 
- The OCID of the next maintenance run.
- NodeCount int
- The number of database servers in the cloud VM cluster.
- NonProvisionable intAutonomous Container Databases 
- The number of non-provisionable Autonomous Container Databases in an Autonomous 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.
- OcpusLowest intScaled Value 
- The lowest value to which ocpus can be scaled down.
- ProvisionableAutonomous intContainer Databases 
- The number of provisionable Autonomous Container Databases in an Autonomous VM Cluster.
- ProvisionedAutonomous intContainer Databases 
- The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- ProvisionedCpus float64
- The number of CPUs provisioned in an Autonomous VM Cluster.
- ReclaimableCpus float64
- For Autonomous Databases on Dedicated Exadata Infrastructure:- These are the CPUs that continue to be included in the count of CPUs 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 CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
 
- ReservedCpus float64
- The number of CPUs reserved in an Autonomous VM Cluster.
- ScanListener intPort Non Tls 
- The SCAN Listener Non TLS port. Default is 1521.
- ScanListener intPort Tls 
- The SCAN Listenenr TLS port. Default is 2484.
- SecurityAttributes map[string]string
- Security Attributes for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {"Oracle-ZPR": {"MaxEgressCount": {"value": "42", "mode": "audit"}}}
- 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.
- TimeDatabase stringSsl Certificate Expires 
- The date and time of Database SSL certificate expiration.
- TimeOrds stringCertificate Expires 
- The date and time of ORDS certificate expiration.
- TimeUpdated string
- The last date and time that the cloud Autonomous VM cluster was updated.
- TotalAutonomous float64Data Storage In Tbs 
- The total data disk group size for Autonomous Databases, in TBs.
- TotalContainer intDatabases 
- The total number of Autonomous Container Databases that can be created with the allocated local storage.
- TotalCpus float64
- The total number of CPUs in an Autonomous VM Cluster.
- autonomousData DoubleStorage Percentage 
- The percentage of the data storage used for the Autonomous Databases in an Autonomous VM Cluster.
- autonomousData DoubleStorage Size In Tbs 
- 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.
- availableAutonomous DoubleData Storage Size In Tbs 
- The data disk group size available for Autonomous Databases, in TBs.
- availableContainer IntegerDatabases 
- 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.
- cloudAutonomous StringVm Cluster Id 
- cloudExadata StringInfrastructure Id 
- The OCID of the cloud Exadata infrastructure.
- clusterTime StringZone 
- The time zone of the Cloud Autonomous VM Cluster.
- compartmentId String
- The OCID of the compartment.
- computeModel String
- The compute model of the Cloud Autonomous VM Cluster. ECPU compute model is the recommended model and OCPU compute model is legacy. See Compute Models in Autonomous Database on Dedicated Exadata #Infrastructure for more details.
- cpuCore IntegerCount 
- The number of CPU cores on the cloud Autonomous VM cluster.
- cpuCore IntegerCount Per Node 
- The number of CPU cores enabled per VM cluster node.
- cpuPercentage Double
- The percentage of total number of CPUs used in an Autonomous VM Cluster.
- dataStorage DoubleSize In Gb 
- The total data storage allocated, in gigabytes (GB).
- dataStorage DoubleSize In Tbs 
- The total data storage allocated, in terabytes (TB).
- dbNode IntegerStorage Size In Gbs 
- The local node storage allocated in GBs.
- dbServers List<String>
- The list of OCIDs of the Db servers.
- Map<String,String>
- 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.
- exadataStorage DoubleIn Tbs Lowest Scaled Value 
- The lowest value to which exadataStorage (in TBs) can be scaled down.
- Map<String,String>
- 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.
- isMtls BooleanEnabled Vm Cluster 
- Enable mutual TLS(mTLS) authentication for database at time of provisioning a VMCluster. This is applicable to database TLS Certificates only. Default is TLS
- lastMaintenance StringRun Id 
- The OCID of the last maintenance run.
- lastUpdate StringHistory Entry Id 
- 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 services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Oracle Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null. It is already set at the Autonomous Exadata Infrastructure level. When provisioning an [Autonomous Database Serverless] (https://docs.oracle.com/en/cloud/paas/autonomous-database/index.html) database, if a value is not specified, the system defaults the value to BRING_YOUR_OWN_LICENSE. Bring your own license (BYOL) also allows you to select the DB edition using the optional parameter.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- maintenanceWindow List<GetDetails Cloud Autonomous Vm Cluster Maintenance Window Detail> 
- maintenanceWindows List<GetCloud Autonomous Vm Cluster Maintenance Window> 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maxAcds IntegerLowest Scaled Value 
- The lowest value to which maximum number of ACDs can be scaled down.
- memoryPer IntegerOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per OCPU or ECPU.
- memorySize IntegerIn Gbs 
- The memory allocated in GBs.
- nextMaintenance StringRun Id 
- The OCID of the next maintenance run.
- nodeCount Integer
- The number of database servers in the cloud VM cluster.
- nonProvisionable IntegerAutonomous Container Databases 
- The number of non-provisionable Autonomous Container Databases in an Autonomous 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.
- ocpusLowest IntegerScaled Value 
- The lowest value to which ocpus can be scaled down.
- provisionableAutonomous IntegerContainer Databases 
- The number of provisionable Autonomous Container Databases in an Autonomous VM Cluster.
- provisionedAutonomous IntegerContainer Databases 
- The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- provisionedCpus Double
- The number of CPUs provisioned in an Autonomous VM Cluster.
- reclaimableCpus Double
- For Autonomous Databases on Dedicated Exadata Infrastructure:- These are the CPUs that continue to be included in the count of CPUs 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 CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
 
- reservedCpus Double
- The number of CPUs reserved in an Autonomous VM Cluster.
- scanListener IntegerPort Non Tls 
- The SCAN Listener Non TLS port. Default is 1521.
- scanListener IntegerPort Tls 
- The SCAN Listenenr TLS port. Default is 2484.
- securityAttributes Map<String,String>
- Security Attributes for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {"Oracle-ZPR": {"MaxEgressCount": {"value": "42", "mode": "audit"}}}
- 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.
- timeDatabase StringSsl Certificate Expires 
- The date and time of Database SSL certificate expiration.
- timeOrds StringCertificate Expires 
- The date and time of ORDS certificate expiration.
- timeUpdated String
- The last date and time that the cloud Autonomous VM cluster was updated.
- totalAutonomous DoubleData Storage In Tbs 
- The total data disk group size for Autonomous Databases, in TBs.
- totalContainer IntegerDatabases 
- The total number of Autonomous Container Databases that can be created with the allocated local storage.
- totalCpus Double
- The total number of CPUs in an Autonomous VM Cluster.
- autonomousData numberStorage Percentage 
- The percentage of the data storage used for the Autonomous Databases in an Autonomous VM Cluster.
- autonomousData numberStorage Size In Tbs 
- 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.
- availableAutonomous numberData Storage Size In Tbs 
- The data disk group size available for Autonomous Databases, in TBs.
- availableContainer numberDatabases 
- 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.
- cloudAutonomous stringVm Cluster Id 
- cloudExadata stringInfrastructure Id 
- The OCID of the cloud Exadata infrastructure.
- clusterTime stringZone 
- The time zone of the Cloud Autonomous VM Cluster.
- compartmentId string
- The OCID of the compartment.
- computeModel string
- The compute model of the Cloud Autonomous VM Cluster. ECPU compute model is the recommended model and OCPU compute model is legacy. See Compute Models in Autonomous Database on Dedicated Exadata #Infrastructure for more details.
- cpuCore numberCount 
- The number of CPU cores on the cloud Autonomous VM cluster.
- cpuCore numberCount Per Node 
- The number of CPU cores enabled per VM cluster node.
- cpuPercentage number
- The percentage of total number of CPUs used in an Autonomous VM Cluster.
- dataStorage numberSize In Gb 
- The total data storage allocated, in gigabytes (GB).
- dataStorage numberSize In Tbs 
- The total data storage allocated, in terabytes (TB).
- dbNode numberStorage Size In Gbs 
- The local node storage allocated in GBs.
- dbServers string[]
- The list of OCIDs of the Db servers.
- {[key: string]: string}
- 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.
- exadataStorage numberIn Tbs Lowest Scaled Value 
- The lowest value to which exadataStorage (in TBs) can be scaled down.
- {[key: string]: string}
- 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.
- isMtls booleanEnabled Vm Cluster 
- Enable mutual TLS(mTLS) authentication for database at time of provisioning a VMCluster. This is applicable to database TLS Certificates only. Default is TLS
- lastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- lastUpdate stringHistory Entry Id 
- 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 services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Oracle Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null. It is already set at the Autonomous Exadata Infrastructure level. When provisioning an [Autonomous Database Serverless] (https://docs.oracle.com/en/cloud/paas/autonomous-database/index.html) database, if a value is not specified, the system defaults the value to BRING_YOUR_OWN_LICENSE. Bring your own license (BYOL) also allows you to select the DB edition using the optional parameter.
- lifecycleDetails string
- Additional information about the current lifecycle state.
- maintenanceWindow GetDetails Cloud Autonomous Vm Cluster Maintenance Window Detail[] 
- maintenanceWindows GetCloud Autonomous Vm Cluster Maintenance Window[] 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maxAcds numberLowest Scaled Value 
- The lowest value to which maximum number of ACDs can be scaled down.
- memoryPer numberOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per OCPU or ECPU.
- memorySize numberIn Gbs 
- The memory allocated in GBs.
- nextMaintenance stringRun Id 
- The OCID of the next maintenance run.
- nodeCount number
- The number of database servers in the cloud VM cluster.
- nonProvisionable numberAutonomous Container Databases 
- The number of non-provisionable Autonomous Container Databases in an Autonomous 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.
- ocpusLowest numberScaled Value 
- The lowest value to which ocpus can be scaled down.
- provisionableAutonomous numberContainer Databases 
- The number of provisionable Autonomous Container Databases in an Autonomous VM Cluster.
- provisionedAutonomous numberContainer Databases 
- The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- provisionedCpus number
- The number of CPUs provisioned in an Autonomous VM Cluster.
- reclaimableCpus number
- For Autonomous Databases on Dedicated Exadata Infrastructure:- These are the CPUs that continue to be included in the count of CPUs 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 CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
 
- reservedCpus number
- The number of CPUs reserved in an Autonomous VM Cluster.
- scanListener numberPort Non Tls 
- The SCAN Listener Non TLS port. Default is 1521.
- scanListener numberPort Tls 
- The SCAN Listenenr TLS port. Default is 2484.
- securityAttributes {[key: string]: string}
- Security Attributes for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {"Oracle-ZPR": {"MaxEgressCount": {"value": "42", "mode": "audit"}}}
- 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.
- timeDatabase stringSsl Certificate Expires 
- The date and time of Database SSL certificate expiration.
- timeOrds stringCertificate Expires 
- The date and time of ORDS certificate expiration.
- timeUpdated string
- The last date and time that the cloud Autonomous VM cluster was updated.
- totalAutonomous numberData Storage In Tbs 
- The total data disk group size for Autonomous Databases, in TBs.
- totalContainer numberDatabases 
- The total number of Autonomous Container Databases that can be created with the allocated local storage.
- totalCpus number
- The total number of CPUs in an Autonomous VM Cluster.
- autonomous_data_ floatstorage_ percentage 
- The percentage of the data storage used for the Autonomous Databases in an Autonomous VM Cluster.
- autonomous_data_ floatstorage_ size_ in_ tbs 
- 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_ floatdata_ storage_ size_ in_ tbs 
- The data disk group size available for Autonomous Databases, in TBs.
- available_container_ intdatabases 
- 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_ strvm_ cluster_ id 
- cloud_exadata_ strinfrastructure_ id 
- The OCID of the cloud Exadata infrastructure.
- cluster_time_ strzone 
- The time zone of the Cloud Autonomous VM Cluster.
- compartment_id str
- The OCID of the compartment.
- compute_model str
- The compute model of the Cloud Autonomous VM Cluster. ECPU compute model is the recommended model and OCPU compute model is legacy. See Compute Models in Autonomous Database on Dedicated Exadata #Infrastructure for more details.
- cpu_core_ intcount 
- The number of CPU cores on the cloud Autonomous VM cluster.
- cpu_core_ intcount_ per_ node 
- The number of CPU cores enabled per VM cluster node.
- cpu_percentage float
- The percentage of total number of CPUs used in an Autonomous VM Cluster.
- data_storage_ floatsize_ in_ gb 
- The total data storage allocated, in gigabytes (GB).
- data_storage_ floatsize_ in_ tbs 
- The total data storage allocated, in terabytes (TB).
- db_node_ intstorage_ size_ in_ gbs 
- The local node storage allocated in GBs.
- db_servers Sequence[str]
- The list of OCIDs of the Db servers.
- Mapping[str, str]
- 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.
- exadata_storage_ floatin_ tbs_ lowest_ scaled_ value 
- The lowest value to which exadataStorage (in TBs) can be scaled down.
- Mapping[str, str]
- 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.
- is_mtls_ boolenabled_ vm_ cluster 
- Enable mutual TLS(mTLS) authentication for database at time of provisioning a VMCluster. This is applicable to database TLS Certificates only. Default is TLS
- last_maintenance_ strrun_ id 
- The OCID of the last maintenance run.
- last_update_ strhistory_ entry_ id 
- 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 services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Oracle Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null. It is already set at the Autonomous Exadata Infrastructure level. When provisioning an [Autonomous Database Serverless] (https://docs.oracle.com/en/cloud/paas/autonomous-database/index.html) database, if a value is not specified, the system defaults the value to BRING_YOUR_OWN_LICENSE. Bring your own license (BYOL) also allows you to select the DB edition using the optional parameter.
- lifecycle_details str
- Additional information about the current lifecycle state.
- maintenance_window_ Sequence[Getdetails Cloud Autonomous Vm Cluster Maintenance Window Detail] 
- maintenance_windows Sequence[GetCloud Autonomous Vm Cluster Maintenance Window] 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- max_acds_ intlowest_ scaled_ value 
- The lowest value to which maximum number of ACDs can be scaled down.
- memory_per_ intoracle_ compute_ unit_ in_ gbs 
- The amount of memory (in GBs) enabled per OCPU or ECPU.
- memory_size_ intin_ gbs 
- The memory allocated in GBs.
- next_maintenance_ strrun_ id 
- The OCID of the next maintenance run.
- node_count int
- The number of database servers in the cloud VM cluster.
- non_provisionable_ intautonomous_ container_ databases 
- The number of non-provisionable Autonomous Container Databases in an Autonomous 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.
- ocpus_lowest_ intscaled_ value 
- The lowest value to which ocpus can be scaled down.
- provisionable_autonomous_ intcontainer_ databases 
- The number of provisionable Autonomous Container Databases in an Autonomous VM Cluster.
- provisioned_autonomous_ intcontainer_ databases 
- The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- provisioned_cpus float
- The number of CPUs provisioned in an Autonomous VM Cluster.
- reclaimable_cpus float
- For Autonomous Databases on Dedicated Exadata Infrastructure:- These are the CPUs that continue to be included in the count of CPUs 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 CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
 
- reserved_cpus float
- The number of CPUs reserved in an Autonomous VM Cluster.
- scan_listener_ intport_ non_ tls 
- The SCAN Listener Non TLS port. Default is 1521.
- scan_listener_ intport_ tls 
- The SCAN Listenenr TLS port. Default is 2484.
- security_attributes Mapping[str, str]
- Security Attributes for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {"Oracle-ZPR": {"MaxEgressCount": {"value": "42", "mode": "audit"}}}
- 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_database_ strssl_ certificate_ expires 
- The date and time of Database SSL certificate expiration.
- time_ords_ strcertificate_ expires 
- The date and time of ORDS certificate expiration.
- time_updated str
- The last date and time that the cloud Autonomous VM cluster was updated.
- total_autonomous_ floatdata_ storage_ in_ tbs 
- The total data disk group size for Autonomous Databases, in TBs.
- total_container_ intdatabases 
- The total number of Autonomous Container Databases that can be created with the allocated local storage.
- total_cpus float
- The total number of CPUs in an Autonomous VM Cluster.
- autonomousData NumberStorage Percentage 
- The percentage of the data storage used for the Autonomous Databases in an Autonomous VM Cluster.
- autonomousData NumberStorage Size In Tbs 
- 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.
- availableAutonomous NumberData Storage Size In Tbs 
- The data disk group size available for Autonomous Databases, in TBs.
- availableContainer NumberDatabases 
- 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.
- cloudAutonomous StringVm Cluster Id 
- cloudExadata StringInfrastructure Id 
- The OCID of the cloud Exadata infrastructure.
- clusterTime StringZone 
- The time zone of the Cloud Autonomous VM Cluster.
- compartmentId String
- The OCID of the compartment.
- computeModel String
- The compute model of the Cloud Autonomous VM Cluster. ECPU compute model is the recommended model and OCPU compute model is legacy. See Compute Models in Autonomous Database on Dedicated Exadata #Infrastructure for more details.
- cpuCore NumberCount 
- The number of CPU cores on the cloud Autonomous VM cluster.
- cpuCore NumberCount Per Node 
- The number of CPU cores enabled per VM cluster node.
- cpuPercentage Number
- The percentage of total number of CPUs used in an Autonomous VM Cluster.
- dataStorage NumberSize In Gb 
- The total data storage allocated, in gigabytes (GB).
- dataStorage NumberSize In Tbs 
- The total data storage allocated, in terabytes (TB).
- dbNode NumberStorage Size In Gbs 
- The local node storage allocated in GBs.
- dbServers List<String>
- The list of OCIDs of the Db servers.
- Map<String>
- 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.
- exadataStorage NumberIn Tbs Lowest Scaled Value 
- The lowest value to which exadataStorage (in TBs) can be scaled down.
- Map<String>
- 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.
- isMtls BooleanEnabled Vm Cluster 
- Enable mutual TLS(mTLS) authentication for database at time of provisioning a VMCluster. This is applicable to database TLS Certificates only. Default is TLS
- lastMaintenance StringRun Id 
- The OCID of the last maintenance run.
- lastUpdate StringHistory Entry Id 
- 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 services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Oracle Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null. It is already set at the Autonomous Exadata Infrastructure level. When provisioning an [Autonomous Database Serverless] (https://docs.oracle.com/en/cloud/paas/autonomous-database/index.html) database, if a value is not specified, the system defaults the value to BRING_YOUR_OWN_LICENSE. Bring your own license (BYOL) also allows you to select the DB edition using the optional parameter.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- maintenanceWindow List<Property Map>Details 
- maintenanceWindows List<Property Map>
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maxAcds NumberLowest Scaled Value 
- The lowest value to which maximum number of ACDs can be scaled down.
- memoryPer NumberOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per OCPU or ECPU.
- memorySize NumberIn Gbs 
- The memory allocated in GBs.
- nextMaintenance StringRun Id 
- The OCID of the next maintenance run.
- nodeCount Number
- The number of database servers in the cloud VM cluster.
- nonProvisionable NumberAutonomous Container Databases 
- The number of non-provisionable Autonomous Container Databases in an Autonomous 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.
- ocpusLowest NumberScaled Value 
- The lowest value to which ocpus can be scaled down.
- provisionableAutonomous NumberContainer Databases 
- The number of provisionable Autonomous Container Databases in an Autonomous VM Cluster.
- provisionedAutonomous NumberContainer Databases 
- The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- provisionedCpus Number
- The number of CPUs provisioned in an Autonomous VM Cluster.
- reclaimableCpus Number
- For Autonomous Databases on Dedicated Exadata Infrastructure:- These are the CPUs that continue to be included in the count of CPUs 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 CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
 
- reservedCpus Number
- The number of CPUs reserved in an Autonomous VM Cluster.
- scanListener NumberPort Non Tls 
- The SCAN Listener Non TLS port. Default is 1521.
- scanListener NumberPort Tls 
- The SCAN Listenenr TLS port. Default is 2484.
- securityAttributes Map<String>
- Security Attributes for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {"Oracle-ZPR": {"MaxEgressCount": {"value": "42", "mode": "audit"}}}
- 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.
- timeDatabase StringSsl Certificate Expires 
- The date and time of Database SSL certificate expiration.
- timeOrds StringCertificate Expires 
- The date and time of ORDS certificate expiration.
- timeUpdated String
- The last date and time that the cloud Autonomous VM cluster was updated.
- totalAutonomous NumberData Storage In Tbs 
- The total data disk group size for Autonomous Databases, in TBs.
- totalContainer NumberDatabases 
- The total number of Autonomous Container Databases that can be created with the allocated local storage.
- totalCpus Number
- The total number of CPUs in an Autonomous VM Cluster.
Supporting Types
GetCloudAutonomousVmClusterMaintenanceWindow      
- CustomAction intTimeout In Mins 
- 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).
- DaysOf List<GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Days Of Week> 
- Days during the week when maintenance should be performed.
- HoursOf List<int>Days 
- 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
 
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- IsMonthly boolPatching Enabled 
- If true, enables the monthly patching option.
- LeadTime intIn Weeks 
- 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<GetCloud Autonomous Vm Cluster Maintenance Window Month> 
- 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.
- SkipRus List<bool>
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- WeeksOf List<int>Months 
- 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.
- CustomAction intTimeout In Mins 
- 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).
- DaysOf []GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Days Of Week 
- Days during the week when maintenance should be performed.
- HoursOf []intDays 
- 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
 
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- IsMonthly boolPatching Enabled 
- If true, enables the monthly patching option.
- LeadTime intIn Weeks 
- 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
[]GetCloud Autonomous Vm Cluster Maintenance Window Month 
- 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.
- SkipRus []bool
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- WeeksOf []intMonths 
- 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.
- customAction IntegerTimeout In Mins 
- 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).
- daysOf List<GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Days Of Week> 
- Days during the week when maintenance should be performed.
- hoursOf List<Integer>Days 
- 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
 
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly BooleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime IntegerIn Weeks 
- 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<GetCloud Autonomous Vm Cluster Maintenance Window Month> 
- 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.
- skipRus List<Boolean>
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeksOf List<Integer>Months 
- 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.
- customAction numberTimeout In Mins 
- 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).
- daysOf GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Days Of Week[] 
- Days during the week when maintenance should be performed.
- hoursOf number[]Days 
- 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
 
- isCustom booleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly booleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime numberIn Weeks 
- 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
GetCloud Autonomous Vm Cluster Maintenance Window Month[] 
- 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.
- skipRus boolean[]
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeksOf number[]Months 
- 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_ inttimeout_ in_ mins 
- 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_ Sequence[Getweeks Cloud Autonomous Vm Cluster Maintenance Window Days Of Week] 
- Days during the week when maintenance should be performed.
- hours_of_ Sequence[int]days 
- 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_ boolaction_ timeout_ enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is_monthly_ boolpatching_ enabled 
- If true, enables the monthly patching option.
- lead_time_ intin_ weeks 
- 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
Sequence[GetCloud Autonomous Vm Cluster Maintenance Window Month] 
- 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.
- skip_rus Sequence[bool]
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeks_of_ Sequence[int]months 
- 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.
- customAction NumberTimeout In Mins 
- 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).
- daysOf List<Property Map>Weeks 
- Days during the week when maintenance should be performed.
- hoursOf List<Number>Days 
- 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
 
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly BooleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime NumberIn Weeks 
- 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.
- skipRus List<Boolean>
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeksOf List<Number>Months 
- 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       
- CustomAction intTimeout In Mins 
- 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).
- DaysOf List<GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Detail Days Of Week> 
- Days during the week when maintenance should be performed.
- HoursOf List<int>Days 
- 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
 
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- IsMonthly boolPatching Enabled 
- If true, enables the monthly patching option.
- LeadTime intIn Weeks 
- 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<GetCloud Autonomous Vm Cluster Maintenance Window Detail Month> 
- 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.
- SkipRus List<bool>
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- WeeksOf List<int>Months 
- 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.
- CustomAction intTimeout In Mins 
- 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).
- DaysOf []GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Detail Days Of Week 
- Days during the week when maintenance should be performed.
- HoursOf []intDays 
- 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
 
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- IsMonthly boolPatching Enabled 
- If true, enables the monthly patching option.
- LeadTime intIn Weeks 
- 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
[]GetCloud Autonomous Vm Cluster Maintenance Window Detail Month 
- 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.
- SkipRus []bool
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- WeeksOf []intMonths 
- 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.
- customAction IntegerTimeout In Mins 
- 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).
- daysOf List<GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Detail Days Of Week> 
- Days during the week when maintenance should be performed.
- hoursOf List<Integer>Days 
- 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
 
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly BooleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime IntegerIn Weeks 
- 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<GetCloud Autonomous Vm Cluster Maintenance Window Detail Month> 
- 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.
- skipRus List<Boolean>
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeksOf List<Integer>Months 
- 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.
- customAction numberTimeout In Mins 
- 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).
- daysOf GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Detail Days Of Week[] 
- Days during the week when maintenance should be performed.
- hoursOf number[]Days 
- 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
 
- isCustom booleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly booleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime numberIn Weeks 
- 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
GetCloud Autonomous Vm Cluster Maintenance Window Detail Month[] 
- 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.
- skipRus boolean[]
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeksOf number[]Months 
- 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_ inttimeout_ in_ mins 
- 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_ Sequence[Getweeks Cloud Autonomous Vm Cluster Maintenance Window Detail Days Of Week] 
- Days during the week when maintenance should be performed.
- hours_of_ Sequence[int]days 
- 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_ boolaction_ timeout_ enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is_monthly_ boolpatching_ enabled 
- If true, enables the monthly patching option.
- lead_time_ intin_ weeks 
- 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
Sequence[GetCloud Autonomous Vm Cluster Maintenance Window Detail Month] 
- 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.
- skip_rus Sequence[bool]
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeks_of_ Sequence[int]months 
- 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.
- customAction NumberTimeout In Mins 
- 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).
- daysOf List<Property Map>Weeks 
- Days during the week when maintenance should be performed.
- hoursOf List<Number>Days 
- 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
 
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly BooleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime NumberIn Weeks 
- 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.
- skipRus List<Boolean>
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeksOf List<Number>Months 
- 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 ociTerraform Provider.