Oracle Cloud Infrastructure v2.11.0 published on Thursday, Sep 19, 2024 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 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:
- Cloud
Autonomous stringVm Cluster Id - The Cloud VM cluster OCID.
- Cloud
Autonomous stringVm Cluster Id - The Cloud VM cluster OCID.
- cloud
Autonomous StringVm Cluster Id - The Cloud VM cluster OCID.
- cloud
Autonomous stringVm Cluster Id - The Cloud VM cluster OCID.
- cloud_
autonomous_ strvm_ cluster_ id - The Cloud VM cluster OCID.
- cloud
Autonomous StringVm Cluster Id - The Cloud VM cluster OCID.
getCloudAutonomousVmCluster Result
The following output properties are available:
- Autonomous
Data doubleStorage Percentage - The percentage of the data storage used for the Autonomous Databases in an Autonomous VM Cluster.
- Autonomous
Data doubleStorage Size In Tbs - The data disk group size allocated for Autonomous Databases, in TBs.
- Availability
Domain string - The name of the availability domain that the cloud Autonomous VM cluster is located in.
- Available
Autonomous doubleData 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 double - CPU cores available for allocation to Autonomous Databases.
- Cloud
Autonomous stringVm Cluster Id - Cloud
Exadata stringInfrastructure Id - The OCID of the cloud Exadata infrastructure.
- Cluster
Time stringZone - The time zone of the Cloud Autonomous VM Cluster.
- Compartment
Id string - The OCID of the compartment.
- Compute
Model 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.
- 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 double - The percentage of total number of CPUs used in an Autonomous VM Cluster.
- Data
Storage doubleSize In Gb - The total data storage allocated, in gigabytes (GB).
- Data
Storage doubleSize 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 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.
- Display
Name 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.
- Exadata
Storage 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.
- 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 stringRun Id - The OCID of the last maintenance run.
- Last
Update stringHistory Entry Id - The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- License
Model 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. - Lifecycle
Details string - Additional information about the current lifecycle state.
- Maintenance
Window List<GetDetails Cloud Autonomous Vm Cluster Maintenance Window Detail> - Maintenance
Windows 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.
- 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 stringRun 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 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.
- Ocpu
Count double - 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 double - The number of CPUs provisioned in an Autonomous VM Cluster.
- Reclaimable
Cpus 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.
- Reserved
Cpus double - 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.
- 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.
- Subnet
Id string - The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- Time
Created string - The date and time that the cloud Autonomous VM cluster was created.
- Time
Updated string - The last date and time that the cloud Autonomous VM cluster was updated.
- Total
Autonomous doubleData 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 double - The total number of CPUs in an Autonomous VM Cluster.
- Autonomous
Data float64Storage Percentage - The percentage of the data storage used for the Autonomous Databases in an Autonomous VM Cluster.
- Autonomous
Data float64Storage Size In Tbs - The data disk group size allocated for Autonomous Databases, in TBs.
- Availability
Domain string - The name of the availability domain that the cloud Autonomous VM cluster is located in.
- Available
Autonomous float64Data 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 float64 - CPU cores available for allocation to Autonomous Databases.
- Cloud
Autonomous stringVm Cluster Id - Cloud
Exadata stringInfrastructure Id - The OCID of the cloud Exadata infrastructure.
- Cluster
Time stringZone - The time zone of the Cloud Autonomous VM Cluster.
- Compartment
Id string - The OCID of the compartment.
- Compute
Model 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.
- 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 float64 - The percentage of total number of CPUs used in an Autonomous VM Cluster.
- Data
Storage float64Size In Gb - The total data storage allocated, in gigabytes (GB).
- Data
Storage float64Size 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 []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.
- Display
Name 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.
- Exadata
Storage 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.
- 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 stringRun Id - The OCID of the last maintenance run.
- Last
Update stringHistory Entry Id - The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- License
Model 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. - Lifecycle
Details string - Additional information about the current lifecycle state.
- Maintenance
Window []GetDetails Cloud Autonomous Vm Cluster Maintenance Window Detail - Maintenance
Windows []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 stringRun 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 []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.
- Ocpu
Count float64 - 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 float64 - The number of CPUs provisioned in an Autonomous VM Cluster.
- Reclaimable
Cpus 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.
- Reserved
Cpus float64 - 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.
- 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.
- Subnet
Id string - The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- Time
Created string - The date and time that the cloud Autonomous VM cluster was created.
- Time
Updated string - The last date and time that the cloud Autonomous VM cluster was updated.
- Total
Autonomous float64Data 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 float64 - The total number of CPUs in an Autonomous VM Cluster.
- autonomous
Data DoubleStorage Percentage - The percentage of the data storage used for the Autonomous Databases in an Autonomous VM Cluster.
- autonomous
Data DoubleStorage Size In Tbs - The data disk group size allocated for Autonomous Databases, in TBs.
- availability
Domain String - The name of the availability domain that the cloud Autonomous VM cluster is located in.
- available
Autonomous DoubleData Storage Size In Tbs - The data disk group size available for Autonomous Databases, in TBs.
- available
Container IntegerDatabases - The number of Autonomous Container Databases that can be created with the currently available local storage.
- available
Cpus Double - CPU cores available for allocation to Autonomous Databases.
- cloud
Autonomous StringVm Cluster Id - cloud
Exadata StringInfrastructure Id - The OCID of the cloud Exadata infrastructure.
- cluster
Time StringZone - The time zone of the Cloud Autonomous VM Cluster.
- compartment
Id String - The OCID of the compartment.
- compute
Model 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.
- cpu
Core IntegerCount - The number of CPU cores on the cloud Autonomous VM cluster.
- cpu
Core IntegerCount Per Node - The number of CPU cores enabled per VM cluster node.
- cpu
Percentage Double - The percentage of total number of CPUs used in an Autonomous VM Cluster.
- data
Storage DoubleSize In Gb - The total data storage allocated, in gigabytes (GB).
- data
Storage DoubleSize In Tbs - The total data storage allocated, in terabytes (TB).
- db
Node IntegerStorage Size In Gbs - The local node storage allocated in GBs.
- db
Servers 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.
- display
Name 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.
- exadata
Storage 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.
- is
Mtls 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
- last
Maintenance StringRun Id - The OCID of the last maintenance run.
- last
Update StringHistory Entry Id - The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- license
Model 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. - lifecycle
Details String - Additional information about the current lifecycle state.
- maintenance
Window List<GetDetails Cloud Autonomous Vm Cluster Maintenance Window Detail> - maintenance
Windows 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.
- max
Acds IntegerLowest Scaled Value - The lowest value to which maximum number of ACDs can be scaled down.
- memory
Per IntegerOracle Compute Unit In Gbs - The amount of memory (in GBs) enabled per OCPU or ECPU.
- memory
Size IntegerIn Gbs - The memory allocated in GBs.
- next
Maintenance StringRun Id - The OCID of the next maintenance run.
- node
Count Integer - The number of database servers in the cloud VM cluster.
- non
Provisionable IntegerAutonomous Container Databases - The number of non-provisionable Autonomous Container Databases in an Autonomous VM Cluster.
- nsg
Ids 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.
- ocpu
Count Double - The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- ocpus
Lowest IntegerScaled Value - The lowest value to which ocpus can be scaled down.
- provisionable
Autonomous IntegerContainer Databases - The number of provisionable Autonomous Container Databases in an Autonomous VM Cluster.
- provisioned
Autonomous IntegerContainer Databases - The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- provisioned
Cpus Double - The number of CPUs provisioned in an Autonomous VM Cluster.
- reclaimable
Cpus 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.
- reserved
Cpus Double - The number of CPUs reserved in an Autonomous VM Cluster.
- scan
Listener IntegerPort Non Tls - The SCAN Listener Non TLS port. Default is 1521.
- scan
Listener IntegerPort Tls - The SCAN Listenenr TLS port. Default is 2484.
- 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.
- subnet
Id String - The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- time
Created String - The date and time that the cloud Autonomous VM cluster was created.
- time
Updated String - The last date and time that the cloud Autonomous VM cluster was updated.
- total
Autonomous DoubleData Storage In Tbs - The total data disk group size for Autonomous Databases, in TBs.
- total
Container IntegerDatabases - The total number of Autonomous Container Databases that can be created with the allocated local storage.
- total
Cpus Double - The total number of CPUs in an Autonomous VM Cluster.
- autonomous
Data numberStorage Percentage - The percentage of the data storage used for the Autonomous Databases in an Autonomous VM Cluster.
- autonomous
Data numberStorage Size In Tbs - The data disk group size allocated for Autonomous Databases, in TBs.
- availability
Domain string - The name of the availability domain that the cloud Autonomous VM cluster is located in.
- available
Autonomous numberData Storage Size In Tbs - The data disk group size available for Autonomous Databases, in TBs.
- available
Container numberDatabases - The number of Autonomous Container Databases that can be created with the currently available local storage.
- available
Cpus number - CPU cores available for allocation to Autonomous Databases.
- cloud
Autonomous stringVm Cluster Id - cloud
Exadata stringInfrastructure Id - The OCID of the cloud Exadata infrastructure.
- cluster
Time stringZone - The time zone of the Cloud Autonomous VM Cluster.
- compartment
Id string - The OCID of the compartment.
- compute
Model 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.
- cpu
Core numberCount - The number of CPU cores on the cloud Autonomous VM cluster.
- cpu
Core numberCount Per Node - The number of CPU cores enabled per VM cluster node.
- cpu
Percentage number - The percentage of total number of CPUs used in an Autonomous VM Cluster.
- data
Storage numberSize In Gb - The total data storage allocated, in gigabytes (GB).
- data
Storage numberSize In Tbs - The total data storage allocated, in terabytes (TB).
- db
Node numberStorage Size In Gbs - The local node storage allocated in GBs.
- db
Servers 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.
- display
Name 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.
- exadata
Storage 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.
- is
Mtls 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
- last
Maintenance stringRun Id - The OCID of the last maintenance run.
- last
Update stringHistory Entry Id - The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- license
Model 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. - lifecycle
Details string - Additional information about the current lifecycle state.
- maintenance
Window GetDetails Cloud Autonomous Vm Cluster Maintenance Window Detail[] - maintenance
Windows 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 numberLowest Scaled Value - The lowest value to which maximum number of ACDs can be scaled down.
- memory
Per numberOracle Compute Unit In Gbs - The amount of memory (in GBs) enabled per OCPU or ECPU.
- memory
Size numberIn Gbs - The memory allocated in GBs.
- next
Maintenance stringRun Id - The OCID of the next maintenance run.
- node
Count number - The number of database servers in the cloud VM cluster.
- non
Provisionable numberAutonomous Container Databases - The number of non-provisionable Autonomous Container Databases in an Autonomous VM Cluster.
- nsg
Ids 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.
- ocpu
Count number - The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- ocpus
Lowest numberScaled Value - The lowest value to which ocpus can be scaled down.
- provisionable
Autonomous numberContainer Databases - The number of provisionable Autonomous Container Databases in an Autonomous VM Cluster.
- provisioned
Autonomous numberContainer Databases - The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- provisioned
Cpus number - The number of CPUs provisioned in an Autonomous VM Cluster.
- reclaimable
Cpus 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.
- reserved
Cpus number - The number of CPUs reserved in an Autonomous VM Cluster.
- scan
Listener numberPort Non Tls - The SCAN Listener Non TLS port. Default is 1521.
- scan
Listener numberPort Tls - The SCAN Listenenr TLS port. Default is 2484.
- 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.
- subnet
Id string - The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- time
Created string - The date and time that the cloud Autonomous VM cluster was created.
- time
Updated string - The last date and time that the cloud Autonomous VM cluster was updated.
- total
Autonomous numberData Storage In Tbs - The total data disk group size for Autonomous Databases, in TBs.
- total
Container numberDatabases - The total number of Autonomous Container Databases that can be created with the allocated local storage.
- total
Cpus 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[database.details Get Cloud Autonomous Vm Cluster Maintenance Window Detail] - maintenance_
windows Sequence[database.Get Cloud 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.
- 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_
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.
- autonomous
Data NumberStorage Percentage - The percentage of the data storage used for the Autonomous Databases in an Autonomous VM Cluster.
- autonomous
Data NumberStorage Size In Tbs - The data disk group size allocated for Autonomous Databases, in TBs.
- availability
Domain String - The name of the availability domain that the cloud Autonomous VM cluster is located in.
- available
Autonomous NumberData Storage Size In Tbs - The data disk group size available for Autonomous Databases, in TBs.
- available
Container NumberDatabases - The number of Autonomous Container Databases that can be created with the currently available local storage.
- available
Cpus Number - CPU cores available for allocation to Autonomous Databases.
- cloud
Autonomous StringVm Cluster Id - cloud
Exadata StringInfrastructure Id - The OCID of the cloud Exadata infrastructure.
- cluster
Time StringZone - The time zone of the Cloud Autonomous VM Cluster.
- compartment
Id String - The OCID of the compartment.
- compute
Model 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.
- cpu
Core NumberCount - The number of CPU cores on the cloud Autonomous VM cluster.
- cpu
Core NumberCount Per Node - The number of CPU cores enabled per VM cluster node.
- cpu
Percentage Number - The percentage of total number of CPUs used in an Autonomous VM Cluster.
- data
Storage NumberSize In Gb - The total data storage allocated, in gigabytes (GB).
- data
Storage NumberSize In Tbs - The total data storage allocated, in terabytes (TB).
- db
Node NumberStorage Size In Gbs - The local node storage allocated in GBs.
- db
Servers 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.
- display
Name 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.
- exadata
Storage 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.
- is
Mtls 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
- last
Maintenance StringRun Id - The OCID of the last maintenance run.
- last
Update StringHistory Entry Id - The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- license
Model 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. - lifecycle
Details String - Additional information about the current lifecycle state.
- maintenance
Window List<Property Map>Details - maintenance
Windows List<Property Map> - The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- max
Acds NumberLowest Scaled Value - The lowest value to which maximum number of ACDs can be scaled down.
- memory
Per NumberOracle Compute Unit In Gbs - The amount of memory (in GBs) enabled per OCPU or ECPU.
- memory
Size NumberIn Gbs - The memory allocated in GBs.
- next
Maintenance StringRun Id - The OCID of the next maintenance run.
- node
Count Number - The number of database servers in the cloud VM cluster.
- non
Provisionable NumberAutonomous Container Databases - The number of non-provisionable Autonomous Container Databases in an Autonomous VM Cluster.
- nsg
Ids 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.
- ocpu
Count Number - The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- ocpus
Lowest NumberScaled Value - The lowest value to which ocpus can be scaled down.
- provisionable
Autonomous NumberContainer Databases - The number of provisionable Autonomous Container Databases in an Autonomous VM Cluster.
- provisioned
Autonomous NumberContainer Databases - The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- provisioned
Cpus Number - The number of CPUs provisioned in an Autonomous VM Cluster.
- reclaimable
Cpus 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.
- reserved
Cpus Number - The number of CPUs reserved in an Autonomous VM Cluster.
- scan
Listener NumberPort Non Tls - The SCAN Listener Non TLS port. Default is 1521.
- scan
Listener NumberPort Tls - The SCAN Listenenr TLS port. Default is 2484.
- 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.
- subnet
Id String - The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- time
Created String - The date and time that the cloud Autonomous VM cluster was created.
- time
Updated String - The last date and time that the cloud Autonomous VM cluster was updated.
- total
Autonomous NumberData Storage In Tbs - The total data disk group size for Autonomous Databases, in TBs.
- total
Container NumberDatabases - The total number of Autonomous Container Databases that can be created with the allocated local storage.
- total
Cpus Number - The total number of CPUs in an Autonomous VM Cluster.
Supporting Types
GetCloudAutonomousVmClusterMaintenanceWindow
- 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 List<GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Days Of Week> - Days during the week when maintenance should be performed.
- Hours
Of 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
- 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
List<Get
Cloud Autonomous Vm Cluster Maintenance Window Month> - Months during the year when maintenance should be performed.
- Patching
Mode string - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
- The maintenance window scheduling preference.
- Skip
Rus List<bool> - Weeks
Of 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.
- 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 []GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Days Of Week - Days during the week when maintenance should be performed.
- Hours
Of []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
- 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
[]Get
Cloud Autonomous Vm Cluster Maintenance Window Month - Months during the year when maintenance should be performed.
- Patching
Mode string - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
- The maintenance window scheduling preference.
- Skip
Rus []bool - Weeks
Of []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.
- custom
Action 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).
- days
Of List<GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Days Of Week> - Days during the week when maintenance should be performed.
- hours
Of 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
- is
Custom BooleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled - If true, enables the monthly patching option.
- lead
Time 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<Get
Cloud Autonomous Vm Cluster Maintenance Window Month> - Months during the year when maintenance should be performed.
- patching
Mode String - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
- The maintenance window scheduling preference.
- skip
Rus List<Boolean> - weeks
Of 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.
- custom
Action 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).
- days
Of GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Days Of Week[] - Days during the week when maintenance should be performed.
- hours
Of 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
- is
Custom booleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly booleanPatching Enabled - If true, enables the monthly patching option.
- lead
Time 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
Get
Cloud Autonomous Vm Cluster Maintenance Window Month[] - Months during the year when maintenance should be performed.
- patching
Mode string - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference string
- The maintenance window scheduling preference.
- skip
Rus boolean[] - weeks
Of 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[database.weeks Get 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[database.
Get Cloud 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] - 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.
- custom
Action 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).
- days
Of List<Property Map>Weeks - Days during the week when maintenance should be performed.
- hours
Of 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
- is
Custom BooleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled - If true, enables the monthly patching option.
- lead
Time 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.
- patching
Mode String - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
- The maintenance window scheduling preference.
- skip
Rus List<Boolean> - weeks
Of 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
- 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 List<GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Detail Days Of Week> - Days during the week when maintenance should be performed.
- Hours
Of 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
- 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
List<Get
Cloud Autonomous Vm Cluster Maintenance Window Detail Month> - Months during the year when maintenance should be performed.
- Patching
Mode string - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
- The maintenance window scheduling preference.
- Skip
Rus List<bool> - Weeks
Of 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.
- 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 []GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Detail Days Of Week - Days during the week when maintenance should be performed.
- Hours
Of []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
- 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
[]Get
Cloud Autonomous Vm Cluster Maintenance Window Detail Month - Months during the year when maintenance should be performed.
- Patching
Mode string - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
- The maintenance window scheduling preference.
- Skip
Rus []bool - Weeks
Of []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.
- custom
Action 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).
- days
Of List<GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Detail Days Of Week> - Days during the week when maintenance should be performed.
- hours
Of 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
- is
Custom BooleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled - If true, enables the monthly patching option.
- lead
Time 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<Get
Cloud Autonomous Vm Cluster Maintenance Window Detail Month> - Months during the year when maintenance should be performed.
- patching
Mode String - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
- The maintenance window scheduling preference.
- skip
Rus List<Boolean> - weeks
Of 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.
- custom
Action 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).
- days
Of GetWeeks Cloud Autonomous Vm Cluster Maintenance Window Detail Days Of Week[] - Days during the week when maintenance should be performed.
- hours
Of 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
- is
Custom booleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly booleanPatching Enabled - If true, enables the monthly patching option.
- lead
Time 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
Get
Cloud Autonomous Vm Cluster Maintenance Window Detail Month[] - Months during the year when maintenance should be performed.
- patching
Mode string - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference string
- The maintenance window scheduling preference.
- skip
Rus boolean[] - weeks
Of 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[database.weeks Get 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[database.
Get Cloud 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] - 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.
- custom
Action 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).
- days
Of List<Property Map>Weeks - Days during the week when maintenance should be performed.
- hours
Of 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
- is
Custom BooleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled - If true, enables the monthly patching option.
- lead
Time 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.
- patching
Mode String - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
- The maintenance window scheduling preference.
- skip
Rus List<Boolean> - weeks
Of 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
oci
Terraform Provider.