oci.Database.getAutonomousVmCluster
Explore with Pulumi AI
This data source provides details about a specific Autonomous Vm Cluster resource in Oracle Cloud Infrastructure Database service.
Gets information about the specified Autonomous VM cluster for an Exadata Cloud@Customer system. To get information about an Autonomous VM Cluster in the Oracle cloud, see GetCloudAutonomousVmCluster.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testAutonomousVmCluster = oci.Database.getAutonomousVmCluster({
autonomousVmClusterId: testAutonomousVmClusterOciDatabaseAutonomousVmCluster.id,
});
import pulumi
import pulumi_oci as oci
test_autonomous_vm_cluster = oci.Database.get_autonomous_vm_cluster(autonomous_vm_cluster_id=test_autonomous_vm_cluster_oci_database_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.GetAutonomousVmCluster(ctx, &database.GetAutonomousVmClusterArgs{
AutonomousVmClusterId: testAutonomousVmClusterOciDatabaseAutonomousVmCluster.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 testAutonomousVmCluster = Oci.Database.GetAutonomousVmCluster.Invoke(new()
{
AutonomousVmClusterId = testAutonomousVmClusterOciDatabaseAutonomousVmCluster.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.GetAutonomousVmClusterArgs;
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 testAutonomousVmCluster = DatabaseFunctions.getAutonomousVmCluster(GetAutonomousVmClusterArgs.builder()
.autonomousVmClusterId(testAutonomousVmClusterOciDatabaseAutonomousVmCluster.id())
.build());
}
}
variables:
testAutonomousVmCluster:
fn::invoke:
Function: oci:Database:getAutonomousVmCluster
Arguments:
autonomousVmClusterId: ${testAutonomousVmClusterOciDatabaseAutonomousVmCluster.id}
Using getAutonomousVmCluster
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 getAutonomousVmCluster(args: GetAutonomousVmClusterArgs, opts?: InvokeOptions): Promise<GetAutonomousVmClusterResult>
function getAutonomousVmClusterOutput(args: GetAutonomousVmClusterOutputArgs, opts?: InvokeOptions): Output<GetAutonomousVmClusterResult>
def get_autonomous_vm_cluster(autonomous_vm_cluster_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetAutonomousVmClusterResult
def get_autonomous_vm_cluster_output(autonomous_vm_cluster_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetAutonomousVmClusterResult]
func GetAutonomousVmCluster(ctx *Context, args *GetAutonomousVmClusterArgs, opts ...InvokeOption) (*GetAutonomousVmClusterResult, error)
func GetAutonomousVmClusterOutput(ctx *Context, args *GetAutonomousVmClusterOutputArgs, opts ...InvokeOption) GetAutonomousVmClusterResultOutput
> Note: This function is named GetAutonomousVmCluster
in the Go SDK.
public static class GetAutonomousVmCluster
{
public static Task<GetAutonomousVmClusterResult> InvokeAsync(GetAutonomousVmClusterArgs args, InvokeOptions? opts = null)
public static Output<GetAutonomousVmClusterResult> Invoke(GetAutonomousVmClusterInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetAutonomousVmClusterResult> getAutonomousVmCluster(GetAutonomousVmClusterArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: oci:Database/getAutonomousVmCluster:getAutonomousVmCluster
arguments:
# arguments dictionary
The following arguments are supported:
- Autonomous
Vm stringCluster Id - The autonomous VM cluster OCID.
- Autonomous
Vm stringCluster Id - The autonomous VM cluster OCID.
- autonomous
Vm StringCluster Id - The autonomous VM cluster OCID.
- autonomous
Vm stringCluster Id - The autonomous VM cluster OCID.
- autonomous_
vm_ strcluster_ id - The autonomous VM cluster OCID.
- autonomous
Vm StringCluster Id - The autonomous VM cluster OCID.
getAutonomousVmCluster Result
The following output properties are available:
- Autonomous
Data doubleStorage Percentage - Autonomous
Data doubleStorage Size In Tbs - The data disk group size allocated for Autonomous Databases, in TBs.
- Autonomous
Vm stringCluster Id - 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 int - The numnber of CPU cores available.
- Available
Data doubleStorage Size In Tbs - Deprecated. Use
availableAutonomousDataStorageSizeInTBs
for Autonomous Databases' data storage availability in TBs. - Compartment
Id string - The OCID of the compartment.
- Compute
Model string - The compute model of the 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 Per Node - The number of CPU cores enabled per VM cluster node.
- Cpu
Percentage double - Cpus
Enabled int - The number of enabled CPU cores.
- Cpus
Lowest intScaled Value - The lowest value to which cpus can be scaled down.
- Data
Storage doubleSize In Gb - The total data storage allocated in GBs.
- Data
Storage doubleSize In Tbs - The total data storage allocated in TBs
- 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.
- Display
Name string - The user-friendly name for the Autonomous VM cluster. The name does not need to be unique.
- Exadata
Infrastructure stringId - The OCID of the Exadata infrastructure.
- 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"}
- Id string
- The OCID of the Autonomous VM cluster.
- Is
Local boolBackup Enabled - If true, database backup on local Exadata storage is configured for the Autonomous VM cluster. If false, database backup on local Exadata storage is not available in the Autonomous VM cluster.
- Is
Mtls boolEnabled - Enable mutual TLS(mTLS) authentication for database while provisioning a VMCluster. Default is TLS.
- Last
Maintenance stringRun Id - The OCID of the last maintenance run.
- License
Model string - The Oracle license model that applies to the Autonomous VM cluster. The default is LICENSE_INCLUDED.
- Lifecycle
Details string - Additional information about the current lifecycle state.
- Maintenance
Window List<GetDetails Autonomous Vm Cluster Maintenance Window Detail> - Maintenance
Windows List<GetAutonomous 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) to be 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 nodes in the Autonomous VM Cluster.
- Non
Provisionable intAutonomous Container Databases - Ocpus
Enabled double - The number of enabled OCPU cores.
- Provisionable
Autonomous intContainer Databases - Deprecated. Use field totalContainerDatabases.
- 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 int - 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 number. Default value is 1521.
- Scan
Listener intPort Tls - The SCAN Listener TLS port number. Default value is 2484.
- State string
- The current state of the Autonomous VM cluster.
- Time
Created string - The date and time that the Autonomous VM cluster was created.
- Time
Database stringSsl Certificate Expires - The date and time of Database SSL certificate expiration.
- Time
Ords stringCertificate Expires - The date and time of ORDS certificate expiration.
- Time
Zone string - The time zone to use for the Autonomous VM cluster. For details, see DB System Time Zones.
- Total
Autonomous doubleData Storage In Tbs - Total
Container intDatabases - The total number of Autonomous Container Databases that can be created.
- Vm
Cluster stringNetwork Id - The OCID of the VM cluster network.
- Autonomous
Data float64Storage Percentage - Autonomous
Data float64Storage Size In Tbs - The data disk group size allocated for Autonomous Databases, in TBs.
- Autonomous
Vm stringCluster Id - 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 int - The numnber of CPU cores available.
- Available
Data float64Storage Size In Tbs - Deprecated. Use
availableAutonomousDataStorageSizeInTBs
for Autonomous Databases' data storage availability in TBs. - Compartment
Id string - The OCID of the compartment.
- Compute
Model string - The compute model of the 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 Per Node - The number of CPU cores enabled per VM cluster node.
- Cpu
Percentage float64 - Cpus
Enabled int - The number of enabled CPU cores.
- Cpus
Lowest intScaled Value - The lowest value to which cpus can be scaled down.
- Data
Storage float64Size In Gb - The total data storage allocated in GBs.
- Data
Storage float64Size In Tbs - The total data storage allocated in TBs
- 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.
- Display
Name string - The user-friendly name for the Autonomous VM cluster. The name does not need to be unique.
- Exadata
Infrastructure stringId - The OCID of the Exadata infrastructure.
- 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"}
- Id string
- The OCID of the Autonomous VM cluster.
- Is
Local boolBackup Enabled - If true, database backup on local Exadata storage is configured for the Autonomous VM cluster. If false, database backup on local Exadata storage is not available in the Autonomous VM cluster.
- Is
Mtls boolEnabled - Enable mutual TLS(mTLS) authentication for database while provisioning a VMCluster. Default is TLS.
- Last
Maintenance stringRun Id - The OCID of the last maintenance run.
- License
Model string - The Oracle license model that applies to the Autonomous VM cluster. The default is LICENSE_INCLUDED.
- Lifecycle
Details string - Additional information about the current lifecycle state.
- Maintenance
Window []GetDetails Autonomous Vm Cluster Maintenance Window Detail - Maintenance
Windows []GetAutonomous 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) to be 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 nodes in the Autonomous VM Cluster.
- Non
Provisionable intAutonomous Container Databases - Ocpus
Enabled float64 - The number of enabled OCPU cores.
- Provisionable
Autonomous intContainer Databases - Deprecated. Use field totalContainerDatabases.
- 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 int - 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 number. Default value is 1521.
- Scan
Listener intPort Tls - The SCAN Listener TLS port number. Default value is 2484.
- State string
- The current state of the Autonomous VM cluster.
- Time
Created string - The date and time that the Autonomous VM cluster was created.
- Time
Database stringSsl Certificate Expires - The date and time of Database SSL certificate expiration.
- Time
Ords stringCertificate Expires - The date and time of ORDS certificate expiration.
- Time
Zone string - The time zone to use for the Autonomous VM cluster. For details, see DB System Time Zones.
- Total
Autonomous float64Data Storage In Tbs - Total
Container intDatabases - The total number of Autonomous Container Databases that can be created.
- Vm
Cluster stringNetwork Id - The OCID of the VM cluster network.
- autonomous
Data DoubleStorage Percentage - autonomous
Data DoubleStorage Size In Tbs - The data disk group size allocated for Autonomous Databases, in TBs.
- autonomous
Vm StringCluster Id - 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 Integer - The numnber of CPU cores available.
- available
Data DoubleStorage Size In Tbs - Deprecated. Use
availableAutonomousDataStorageSizeInTBs
for Autonomous Databases' data storage availability in TBs. - compartment
Id String - The OCID of the compartment.
- compute
Model String - The compute model of the 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 Per Node - The number of CPU cores enabled per VM cluster node.
- cpu
Percentage Double - cpus
Enabled Integer - The number of enabled CPU cores.
- cpus
Lowest IntegerScaled Value - The lowest value to which cpus can be scaled down.
- data
Storage DoubleSize In Gb - The total data storage allocated in GBs.
- data
Storage DoubleSize In Tbs - The total data storage allocated in TBs
- 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.
- display
Name String - The user-friendly name for the Autonomous VM cluster. The name does not need to be unique.
- exadata
Infrastructure StringId - The OCID of the Exadata infrastructure.
- 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"}
- id String
- The OCID of the Autonomous VM cluster.
- is
Local BooleanBackup Enabled - If true, database backup on local Exadata storage is configured for the Autonomous VM cluster. If false, database backup on local Exadata storage is not available in the Autonomous VM cluster.
- is
Mtls BooleanEnabled - Enable mutual TLS(mTLS) authentication for database while provisioning a VMCluster. Default is TLS.
- last
Maintenance StringRun Id - The OCID of the last maintenance run.
- license
Model String - The Oracle license model that applies to the Autonomous VM cluster. The default is LICENSE_INCLUDED.
- lifecycle
Details String - Additional information about the current lifecycle state.
- maintenance
Window List<GetDetails Autonomous Vm Cluster Maintenance Window Detail> - maintenance
Windows List<GetAutonomous 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) to be 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 nodes in the Autonomous VM Cluster.
- non
Provisionable IntegerAutonomous Container Databases - ocpus
Enabled Double - The number of enabled OCPU cores.
- provisionable
Autonomous IntegerContainer Databases - Deprecated. Use field totalContainerDatabases.
- 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 Integer - 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 number. Default value is 1521.
- scan
Listener IntegerPort Tls - The SCAN Listener TLS port number. Default value is 2484.
- state String
- The current state of the Autonomous VM cluster.
- time
Created String - The date and time that the Autonomous VM cluster was created.
- time
Database StringSsl Certificate Expires - The date and time of Database SSL certificate expiration.
- time
Ords StringCertificate Expires - The date and time of ORDS certificate expiration.
- time
Zone String - The time zone to use for the Autonomous VM cluster. For details, see DB System Time Zones.
- total
Autonomous DoubleData Storage In Tbs - total
Container IntegerDatabases - The total number of Autonomous Container Databases that can be created.
- vm
Cluster StringNetwork Id - The OCID of the VM cluster network.
- autonomous
Data numberStorage Percentage - autonomous
Data numberStorage Size In Tbs - The data disk group size allocated for Autonomous Databases, in TBs.
- autonomous
Vm stringCluster Id - 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 - The numnber of CPU cores available.
- available
Data numberStorage Size In Tbs - Deprecated. Use
availableAutonomousDataStorageSizeInTBs
for Autonomous Databases' data storage availability in TBs. - compartment
Id string - The OCID of the compartment.
- compute
Model string - The compute model of the 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 Per Node - The number of CPU cores enabled per VM cluster node.
- cpu
Percentage number - cpus
Enabled number - The number of enabled CPU cores.
- cpus
Lowest numberScaled Value - The lowest value to which cpus can be scaled down.
- data
Storage numberSize In Gb - The total data storage allocated in GBs.
- data
Storage numberSize In Tbs - The total data storage allocated in TBs
- 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.
- display
Name string - The user-friendly name for the Autonomous VM cluster. The name does not need to be unique.
- exadata
Infrastructure stringId - The OCID of the Exadata infrastructure.
- 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"}
- id string
- The OCID of the Autonomous VM cluster.
- is
Local booleanBackup Enabled - If true, database backup on local Exadata storage is configured for the Autonomous VM cluster. If false, database backup on local Exadata storage is not available in the Autonomous VM cluster.
- is
Mtls booleanEnabled - Enable mutual TLS(mTLS) authentication for database while provisioning a VMCluster. Default is TLS.
- last
Maintenance stringRun Id - The OCID of the last maintenance run.
- license
Model string - The Oracle license model that applies to the Autonomous VM cluster. The default is LICENSE_INCLUDED.
- lifecycle
Details string - Additional information about the current lifecycle state.
- maintenance
Window GetDetails Autonomous Vm Cluster Maintenance Window Detail[] - maintenance
Windows GetAutonomous 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) to be 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 nodes in the Autonomous VM Cluster.
- non
Provisionable numberAutonomous Container Databases - ocpus
Enabled number - The number of enabled OCPU cores.
- provisionable
Autonomous numberContainer Databases - Deprecated. Use field totalContainerDatabases.
- 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 number. Default value is 1521.
- scan
Listener numberPort Tls - The SCAN Listener TLS port number. Default value is 2484.
- state string
- The current state of the Autonomous VM cluster.
- time
Created string - The date and time that the Autonomous VM cluster was created.
- time
Database stringSsl Certificate Expires - The date and time of Database SSL certificate expiration.
- time
Ords stringCertificate Expires - The date and time of ORDS certificate expiration.
- time
Zone string - The time zone to use for the Autonomous VM cluster. For details, see DB System Time Zones.
- total
Autonomous numberData Storage In Tbs - total
Container numberDatabases - The total number of Autonomous Container Databases that can be created.
- vm
Cluster stringNetwork Id - The OCID of the VM cluster network.
- autonomous_
data_ floatstorage_ percentage - autonomous_
data_ floatstorage_ size_ in_ tbs - The data disk group size allocated for Autonomous Databases, in TBs.
- autonomous_
vm_ strcluster_ id - 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 int - The numnber of CPU cores available.
- available_
data_ floatstorage_ size_ in_ tbs - Deprecated. Use
availableAutonomousDataStorageSizeInTBs
for Autonomous Databases' data storage availability in TBs. - compartment_
id str - The OCID of the compartment.
- compute_
model str - The compute model of the 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_ per_ node - The number of CPU cores enabled per VM cluster node.
- cpu_
percentage float - cpus_
enabled int - The number of enabled CPU cores.
- cpus_
lowest_ intscaled_ value - The lowest value to which cpus can be scaled down.
- data_
storage_ floatsize_ in_ gb - The total data storage allocated in GBs.
- data_
storage_ floatsize_ in_ tbs - The total data storage allocated in TBs
- 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.
- display_
name str - The user-friendly name for the Autonomous VM cluster. The name does not need to be unique.
- exadata_
infrastructure_ strid - The OCID of the Exadata infrastructure.
- 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"}
- id str
- The OCID of the Autonomous VM cluster.
- is_
local_ boolbackup_ enabled - If true, database backup on local Exadata storage is configured for the Autonomous VM cluster. If false, database backup on local Exadata storage is not available in the Autonomous VM cluster.
- is_
mtls_ boolenabled - Enable mutual TLS(mTLS) authentication for database while provisioning a VMCluster. Default is TLS.
- last_
maintenance_ strrun_ id - The OCID of the last maintenance run.
- license_
model str - The Oracle license model that applies to the Autonomous VM cluster. The default is LICENSE_INCLUDED.
- lifecycle_
details str - Additional information about the current lifecycle state.
- maintenance_
window_ Sequence[database.details Get Autonomous Vm Cluster Maintenance Window Detail] - maintenance_
windows Sequence[database.Get 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) to be 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 nodes in the Autonomous VM Cluster.
- non_
provisionable_ intautonomous_ container_ databases - ocpus_
enabled float - The number of enabled OCPU cores.
- provisionable_
autonomous_ intcontainer_ databases - Deprecated. Use field totalContainerDatabases.
- 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 int - 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 number. Default value is 1521.
- scan_
listener_ intport_ tls - The SCAN Listener TLS port number. Default value is 2484.
- state str
- The current state of the Autonomous VM cluster.
- time_
created str - The date and time that the 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_
zone str - The time zone to use for the Autonomous VM cluster. For details, see DB System Time Zones.
- total_
autonomous_ floatdata_ storage_ in_ tbs - total_
container_ intdatabases - The total number of Autonomous Container Databases that can be created.
- vm_
cluster_ strnetwork_ id - The OCID of the VM cluster network.
- autonomous
Data NumberStorage Percentage - autonomous
Data NumberStorage Size In Tbs - The data disk group size allocated for Autonomous Databases, in TBs.
- autonomous
Vm StringCluster Id - 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 - The numnber of CPU cores available.
- available
Data NumberStorage Size In Tbs - Deprecated. Use
availableAutonomousDataStorageSizeInTBs
for Autonomous Databases' data storage availability in TBs. - compartment
Id String - The OCID of the compartment.
- compute
Model String - The compute model of the 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 Per Node - The number of CPU cores enabled per VM cluster node.
- cpu
Percentage Number - cpus
Enabled Number - The number of enabled CPU cores.
- cpus
Lowest NumberScaled Value - The lowest value to which cpus can be scaled down.
- data
Storage NumberSize In Gb - The total data storage allocated in GBs.
- data
Storage NumberSize In Tbs - The total data storage allocated in TBs
- 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.
- display
Name String - The user-friendly name for the Autonomous VM cluster. The name does not need to be unique.
- exadata
Infrastructure StringId - The OCID of the Exadata infrastructure.
- 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"}
- id String
- The OCID of the Autonomous VM cluster.
- is
Local BooleanBackup Enabled - If true, database backup on local Exadata storage is configured for the Autonomous VM cluster. If false, database backup on local Exadata storage is not available in the Autonomous VM cluster.
- is
Mtls BooleanEnabled - Enable mutual TLS(mTLS) authentication for database while provisioning a VMCluster. Default is TLS.
- last
Maintenance StringRun Id - The OCID of the last maintenance run.
- license
Model String - The Oracle license model that applies to the Autonomous VM cluster. The default is LICENSE_INCLUDED.
- 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) to be 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 nodes in the Autonomous VM Cluster.
- non
Provisionable NumberAutonomous Container Databases - ocpus
Enabled Number - The number of enabled OCPU cores.
- provisionable
Autonomous NumberContainer Databases - Deprecated. Use field totalContainerDatabases.
- 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 number. Default value is 1521.
- scan
Listener NumberPort Tls - The SCAN Listener TLS port number. Default value is 2484.
- state String
- The current state of the Autonomous VM cluster.
- time
Created String - The date and time that the Autonomous VM cluster was created.
- time
Database StringSsl Certificate Expires - The date and time of Database SSL certificate expiration.
- time
Ords StringCertificate Expires - The date and time of ORDS certificate expiration.
- time
Zone String - The time zone to use for the Autonomous VM cluster. For details, see DB System Time Zones.
- total
Autonomous NumberData Storage In Tbs - total
Container NumberDatabases - The total number of Autonomous Container Databases that can be created.
- vm
Cluster StringNetwork Id - The OCID of the VM cluster network.
Supporting Types
GetAutonomousVmClusterMaintenanceWindow
- Custom
Action intTimeout In Mins - Days
Of List<GetWeeks 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 - Is
Monthly boolPatching Enabled - 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
Autonomous Vm Cluster Maintenance Window Month> - Months during the year when maintenance should be performed.
- Patching
Mode string - Preference string
- The maintenance window scheduling preference.
- Skip
Rus 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.
- 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 - Days
Of []GetWeeks 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 - Is
Monthly boolPatching Enabled - 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
Autonomous Vm Cluster Maintenance Window Month - Months during the year when maintenance should be performed.
- Patching
Mode string - Preference string
- The maintenance window scheduling preference.
- Skip
Rus []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 []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 - days
Of List<GetWeeks 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 - is
Monthly BooleanPatching Enabled - 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
Autonomous Vm Cluster Maintenance Window Month> - Months during the year when maintenance should be performed.
- patching
Mode String - preference String
- The maintenance window scheduling preference.
- skip
Rus 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.
- 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 - days
Of GetWeeks 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 - is
Monthly booleanPatching Enabled - 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
Autonomous Vm Cluster Maintenance Window Month[] - Months during the year when maintenance should be performed.
- patching
Mode string - preference string
- The maintenance window scheduling preference.
- skip
Rus 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.
- 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 - days_
of_ Sequence[database.weeks Get 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 - is_
monthly_ boolpatching_ enabled - 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 Autonomous Vm Cluster Maintenance Window Month] - Months during the year when maintenance should be performed.
- patching_
mode str - 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.
- custom
Action NumberTimeout In Mins - 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 - is
Monthly BooleanPatching Enabled - 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 - preference String
- The maintenance window scheduling preference.
- skip
Rus 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.
- 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.
GetAutonomousVmClusterMaintenanceWindowDaysOfWeek
- 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.
GetAutonomousVmClusterMaintenanceWindowDetail
- Custom
Action intTimeout In Mins - Days
Of List<GetWeeks 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 - Is
Monthly boolPatching Enabled - 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
Autonomous Vm Cluster Maintenance Window Detail Month> - Months during the year when maintenance should be performed.
- Patching
Mode string - Preference string
- The maintenance window scheduling preference.
- Skip
Rus 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.
- 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 - Days
Of []GetWeeks 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 - Is
Monthly boolPatching Enabled - 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
Autonomous Vm Cluster Maintenance Window Detail Month - Months during the year when maintenance should be performed.
- Patching
Mode string - Preference string
- The maintenance window scheduling preference.
- Skip
Rus []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 []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 - days
Of List<GetWeeks 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 - is
Monthly BooleanPatching Enabled - 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
Autonomous Vm Cluster Maintenance Window Detail Month> - Months during the year when maintenance should be performed.
- patching
Mode String - preference String
- The maintenance window scheduling preference.
- skip
Rus 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.
- 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 - days
Of GetWeeks 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 - is
Monthly booleanPatching Enabled - 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
Autonomous Vm Cluster Maintenance Window Detail Month[] - Months during the year when maintenance should be performed.
- patching
Mode string - preference string
- The maintenance window scheduling preference.
- skip
Rus 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.
- 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 - days_
of_ Sequence[database.weeks Get 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 - is_
monthly_ boolpatching_ enabled - 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 Autonomous Vm Cluster Maintenance Window Detail Month] - Months during the year when maintenance should be performed.
- patching_
mode str - 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.
- custom
Action NumberTimeout In Mins - 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 - is
Monthly BooleanPatching Enabled - 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 - preference String
- The maintenance window scheduling preference.
- skip
Rus 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.
- 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.
GetAutonomousVmClusterMaintenanceWindowDetailDaysOfWeek
- 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.
GetAutonomousVmClusterMaintenanceWindowDetailMonth
- 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.
GetAutonomousVmClusterMaintenanceWindowMonth
- 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.