Oracle Cloud Infrastructure v2.19.0 published on Thursday, Dec 12, 2024 by Pulumi
oci.Database.getAutonomousContainerDatabases
Explore with Pulumi AI
This data source provides the list of Autonomous Container Databases in Oracle Cloud Infrastructure Database service.
Gets a list of the Autonomous Container Databases in the specified compartment.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testAutonomousContainerDatabases = oci.Database.getAutonomousContainerDatabases({
compartmentId: compartmentId,
autonomousExadataInfrastructureId: testAutonomousExadataInfrastructure.id,
autonomousVmClusterId: testAutonomousVmCluster.id,
availabilityDomain: autonomousContainerDatabaseAvailabilityDomain,
cloudAutonomousVmClusterId: testCloudAutonomousVmCluster.id,
displayName: autonomousContainerDatabaseDisplayName,
infrastructureType: autonomousContainerDatabaseInfrastructureType,
serviceLevelAgreementType: autonomousContainerDatabaseServiceLevelAgreementType,
state: autonomousContainerDatabaseState,
});
import pulumi
import pulumi_oci as oci
test_autonomous_container_databases = oci.Database.get_autonomous_container_databases(compartment_id=compartment_id,
autonomous_exadata_infrastructure_id=test_autonomous_exadata_infrastructure["id"],
autonomous_vm_cluster_id=test_autonomous_vm_cluster["id"],
availability_domain=autonomous_container_database_availability_domain,
cloud_autonomous_vm_cluster_id=test_cloud_autonomous_vm_cluster["id"],
display_name=autonomous_container_database_display_name,
infrastructure_type=autonomous_container_database_infrastructure_type,
service_level_agreement_type=autonomous_container_database_service_level_agreement_type,
state=autonomous_container_database_state)
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.GetAutonomousContainerDatabases(ctx, &database.GetAutonomousContainerDatabasesArgs{
CompartmentId: compartmentId,
AutonomousExadataInfrastructureId: pulumi.StringRef(testAutonomousExadataInfrastructure.Id),
AutonomousVmClusterId: pulumi.StringRef(testAutonomousVmCluster.Id),
AvailabilityDomain: pulumi.StringRef(autonomousContainerDatabaseAvailabilityDomain),
CloudAutonomousVmClusterId: pulumi.StringRef(testCloudAutonomousVmCluster.Id),
DisplayName: pulumi.StringRef(autonomousContainerDatabaseDisplayName),
InfrastructureType: pulumi.StringRef(autonomousContainerDatabaseInfrastructureType),
ServiceLevelAgreementType: pulumi.StringRef(autonomousContainerDatabaseServiceLevelAgreementType),
State: pulumi.StringRef(autonomousContainerDatabaseState),
}, 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 testAutonomousContainerDatabases = Oci.Database.GetAutonomousContainerDatabases.Invoke(new()
{
CompartmentId = compartmentId,
AutonomousExadataInfrastructureId = testAutonomousExadataInfrastructure.Id,
AutonomousVmClusterId = testAutonomousVmCluster.Id,
AvailabilityDomain = autonomousContainerDatabaseAvailabilityDomain,
CloudAutonomousVmClusterId = testCloudAutonomousVmCluster.Id,
DisplayName = autonomousContainerDatabaseDisplayName,
InfrastructureType = autonomousContainerDatabaseInfrastructureType,
ServiceLevelAgreementType = autonomousContainerDatabaseServiceLevelAgreementType,
State = autonomousContainerDatabaseState,
});
});
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.GetAutonomousContainerDatabasesArgs;
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 testAutonomousContainerDatabases = DatabaseFunctions.getAutonomousContainerDatabases(GetAutonomousContainerDatabasesArgs.builder()
.compartmentId(compartmentId)
.autonomousExadataInfrastructureId(testAutonomousExadataInfrastructure.id())
.autonomousVmClusterId(testAutonomousVmCluster.id())
.availabilityDomain(autonomousContainerDatabaseAvailabilityDomain)
.cloudAutonomousVmClusterId(testCloudAutonomousVmCluster.id())
.displayName(autonomousContainerDatabaseDisplayName)
.infrastructureType(autonomousContainerDatabaseInfrastructureType)
.serviceLevelAgreementType(autonomousContainerDatabaseServiceLevelAgreementType)
.state(autonomousContainerDatabaseState)
.build());
}
}
variables:
testAutonomousContainerDatabases:
fn::invoke:
function: oci:Database:getAutonomousContainerDatabases
arguments:
compartmentId: ${compartmentId}
autonomousExadataInfrastructureId: ${testAutonomousExadataInfrastructure.id}
autonomousVmClusterId: ${testAutonomousVmCluster.id}
availabilityDomain: ${autonomousContainerDatabaseAvailabilityDomain}
cloudAutonomousVmClusterId: ${testCloudAutonomousVmCluster.id}
displayName: ${autonomousContainerDatabaseDisplayName}
infrastructureType: ${autonomousContainerDatabaseInfrastructureType}
serviceLevelAgreementType: ${autonomousContainerDatabaseServiceLevelAgreementType}
state: ${autonomousContainerDatabaseState}
Using getAutonomousContainerDatabases
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 getAutonomousContainerDatabases(args: GetAutonomousContainerDatabasesArgs, opts?: InvokeOptions): Promise<GetAutonomousContainerDatabasesResult>
function getAutonomousContainerDatabasesOutput(args: GetAutonomousContainerDatabasesOutputArgs, opts?: InvokeOptions): Output<GetAutonomousContainerDatabasesResult>
def get_autonomous_container_databases(autonomous_exadata_infrastructure_id: Optional[str] = None,
autonomous_vm_cluster_id: Optional[str] = None,
availability_domain: Optional[str] = None,
cloud_autonomous_vm_cluster_id: Optional[str] = None,
compartment_id: Optional[str] = None,
display_name: Optional[str] = None,
filters: Optional[Sequence[_database.GetAutonomousContainerDatabasesFilter]] = None,
infrastructure_type: Optional[str] = None,
service_level_agreement_type: Optional[str] = None,
state: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetAutonomousContainerDatabasesResult
def get_autonomous_container_databases_output(autonomous_exadata_infrastructure_id: Optional[pulumi.Input[str]] = None,
autonomous_vm_cluster_id: Optional[pulumi.Input[str]] = None,
availability_domain: Optional[pulumi.Input[str]] = None,
cloud_autonomous_vm_cluster_id: Optional[pulumi.Input[str]] = None,
compartment_id: Optional[pulumi.Input[str]] = None,
display_name: Optional[pulumi.Input[str]] = None,
filters: Optional[pulumi.Input[Sequence[pulumi.Input[_database.GetAutonomousContainerDatabasesFilterArgs]]]] = None,
infrastructure_type: Optional[pulumi.Input[str]] = None,
service_level_agreement_type: Optional[pulumi.Input[str]] = None,
state: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetAutonomousContainerDatabasesResult]
func GetAutonomousContainerDatabases(ctx *Context, args *GetAutonomousContainerDatabasesArgs, opts ...InvokeOption) (*GetAutonomousContainerDatabasesResult, error)
func GetAutonomousContainerDatabasesOutput(ctx *Context, args *GetAutonomousContainerDatabasesOutputArgs, opts ...InvokeOption) GetAutonomousContainerDatabasesResultOutput
> Note: This function is named GetAutonomousContainerDatabases
in the Go SDK.
public static class GetAutonomousContainerDatabases
{
public static Task<GetAutonomousContainerDatabasesResult> InvokeAsync(GetAutonomousContainerDatabasesArgs args, InvokeOptions? opts = null)
public static Output<GetAutonomousContainerDatabasesResult> Invoke(GetAutonomousContainerDatabasesInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetAutonomousContainerDatabasesResult> getAutonomousContainerDatabases(GetAutonomousContainerDatabasesArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: oci:Database/getAutonomousContainerDatabases:getAutonomousContainerDatabases
arguments:
# arguments dictionary
The following arguments are supported:
- Compartment
Id string - The compartment OCID.
- Autonomous
Exadata stringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- Autonomous
Vm stringCluster Id - The Autonomous VM Cluster OCID.
- Availability
Domain string - A filter to return only resources that match the given availability domain exactly.
- Cloud
Autonomous stringVm Cluster Id - The cloud Autonomous VM Cluster OCID.
- Display
Name string - A filter to return only resources that match the entire display name given. The match is not case sensitive.
- Filters
List<Get
Autonomous Container Databases Filter> - Infrastructure
Type string - A filter to return only resources that match the given Infrastructure Type.
- Service
Level stringAgreement Type - A filter to return only resources that match the given service level agreement type exactly.
- State string
- A filter to return only resources that match the given lifecycle state exactly.
- Compartment
Id string - The compartment OCID.
- Autonomous
Exadata stringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- Autonomous
Vm stringCluster Id - The Autonomous VM Cluster OCID.
- Availability
Domain string - A filter to return only resources that match the given availability domain exactly.
- Cloud
Autonomous stringVm Cluster Id - The cloud Autonomous VM Cluster OCID.
- Display
Name string - A filter to return only resources that match the entire display name given. The match is not case sensitive.
- Filters
[]Get
Autonomous Container Databases Filter - Infrastructure
Type string - A filter to return only resources that match the given Infrastructure Type.
- Service
Level stringAgreement Type - A filter to return only resources that match the given service level agreement type exactly.
- State string
- A filter to return only resources that match the given lifecycle state exactly.
- compartment
Id String - The compartment OCID.
- autonomous
Exadata StringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- autonomous
Vm StringCluster Id - The Autonomous VM Cluster OCID.
- availability
Domain String - A filter to return only resources that match the given availability domain exactly.
- cloud
Autonomous StringVm Cluster Id - The cloud Autonomous VM Cluster OCID.
- display
Name String - A filter to return only resources that match the entire display name given. The match is not case sensitive.
- filters
List<Get
Autonomous Containers Filter> - infrastructure
Type String - A filter to return only resources that match the given Infrastructure Type.
- service
Level StringAgreement Type - A filter to return only resources that match the given service level agreement type exactly.
- state String
- A filter to return only resources that match the given lifecycle state exactly.
- compartment
Id string - The compartment OCID.
- autonomous
Exadata stringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- autonomous
Vm stringCluster Id - The Autonomous VM Cluster OCID.
- availability
Domain string - A filter to return only resources that match the given availability domain exactly.
- cloud
Autonomous stringVm Cluster Id - The cloud Autonomous VM Cluster OCID.
- display
Name string - A filter to return only resources that match the entire display name given. The match is not case sensitive.
- filters
Get
Autonomous Container Databases Filter[] - infrastructure
Type string - A filter to return only resources that match the given Infrastructure Type.
- service
Level stringAgreement Type - A filter to return only resources that match the given service level agreement type exactly.
- state string
- A filter to return only resources that match the given lifecycle state exactly.
- compartment_
id str - The compartment OCID.
- autonomous_
exadata_ strinfrastructure_ id - The Autonomous Exadata Infrastructure OCID.
- autonomous_
vm_ strcluster_ id - The Autonomous VM Cluster OCID.
- availability_
domain str - A filter to return only resources that match the given availability domain exactly.
- cloud_
autonomous_ strvm_ cluster_ id - The cloud Autonomous VM Cluster OCID.
- display_
name str - A filter to return only resources that match the entire display name given. The match is not case sensitive.
- filters
Sequence[database.
Get Autonomous Container Databases Filter] - infrastructure_
type str - A filter to return only resources that match the given Infrastructure Type.
- service_
level_ stragreement_ type - A filter to return only resources that match the given service level agreement type exactly.
- state str
- A filter to return only resources that match the given lifecycle state exactly.
- compartment
Id String - The compartment OCID.
- autonomous
Exadata StringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- autonomous
Vm StringCluster Id - The Autonomous VM Cluster OCID.
- availability
Domain String - A filter to return only resources that match the given availability domain exactly.
- cloud
Autonomous StringVm Cluster Id - The cloud Autonomous VM Cluster OCID.
- display
Name String - A filter to return only resources that match the entire display name given. The match is not case sensitive.
- filters List<Property Map>
- infrastructure
Type String - A filter to return only resources that match the given Infrastructure Type.
- service
Level StringAgreement Type - A filter to return only resources that match the given service level agreement type exactly.
- state String
- A filter to return only resources that match the given lifecycle state exactly.
getAutonomousContainerDatabases Result
The following output properties are available:
- Autonomous
Container List<GetDatabases Autonomous Container Databases Autonomous Container Database> - The list of autonomous_container_databases.
- Compartment
Id string - The OCID of the compartment.
- Id string
- The provider-assigned unique ID for this managed resource.
- Autonomous
Exadata stringInfrastructure Id - No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified
cloudAutonomousVmCluster
. - Autonomous
Vm stringCluster Id - The OCID of the Autonomous VM Cluster.
- Availability
Domain string - The availability domain of the Autonomous Container Database.
- Cloud
Autonomous stringVm Cluster Id - The OCID of the cloud Autonomous Exadata VM Cluster.
- Display
Name string - The user-provided name for the Autonomous Container Database.
- Filters
List<Get
Autonomous Container Databases Filter> - Infrastructure
Type string - The infrastructure type this resource belongs to.
- Service
Level stringAgreement Type - The service level agreement type of the container database. The default is STANDARD.
- State string
- The current state of the Autonomous Container Database.
- Autonomous
Container []GetDatabases Autonomous Container Databases Autonomous Container Database - The list of autonomous_container_databases.
- Compartment
Id string - The OCID of the compartment.
- Id string
- The provider-assigned unique ID for this managed resource.
- Autonomous
Exadata stringInfrastructure Id - No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified
cloudAutonomousVmCluster
. - Autonomous
Vm stringCluster Id - The OCID of the Autonomous VM Cluster.
- Availability
Domain string - The availability domain of the Autonomous Container Database.
- Cloud
Autonomous stringVm Cluster Id - The OCID of the cloud Autonomous Exadata VM Cluster.
- Display
Name string - The user-provided name for the Autonomous Container Database.
- Filters
[]Get
Autonomous Container Databases Filter - Infrastructure
Type string - The infrastructure type this resource belongs to.
- Service
Level stringAgreement Type - The service level agreement type of the container database. The default is STANDARD.
- State string
- The current state of the Autonomous Container Database.
- autonomous
Container List<GetDatabases Autonomous Containers Autonomous Container> - The list of autonomous_container_databases.
- compartment
Id String - The OCID of the compartment.
- id String
- The provider-assigned unique ID for this managed resource.
- autonomous
Exadata StringInfrastructure Id - No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified
cloudAutonomousVmCluster
. - autonomous
Vm StringCluster Id - The OCID of the Autonomous VM Cluster.
- availability
Domain String - The availability domain of the Autonomous Container Database.
- cloud
Autonomous StringVm Cluster Id - The OCID of the cloud Autonomous Exadata VM Cluster.
- display
Name String - The user-provided name for the Autonomous Container Database.
- filters
List<Get
Autonomous Containers Filter> - infrastructure
Type String - The infrastructure type this resource belongs to.
- service
Level StringAgreement Type - The service level agreement type of the container database. The default is STANDARD.
- state String
- The current state of the Autonomous Container Database.
- autonomous
Container GetDatabases Autonomous Container Databases Autonomous Container Database[] - The list of autonomous_container_databases.
- compartment
Id string - The OCID of the compartment.
- id string
- The provider-assigned unique ID for this managed resource.
- autonomous
Exadata stringInfrastructure Id - No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified
cloudAutonomousVmCluster
. - autonomous
Vm stringCluster Id - The OCID of the Autonomous VM Cluster.
- availability
Domain string - The availability domain of the Autonomous Container Database.
- cloud
Autonomous stringVm Cluster Id - The OCID of the cloud Autonomous Exadata VM Cluster.
- display
Name string - The user-provided name for the Autonomous Container Database.
- filters
Get
Autonomous Container Databases Filter[] - infrastructure
Type string - The infrastructure type this resource belongs to.
- service
Level stringAgreement Type - The service level agreement type of the container database. The default is STANDARD.
- state string
- The current state of the Autonomous Container Database.
- autonomous_
container_ Sequence[database.databases Get Autonomous Container Databases Autonomous Container Database] - The list of autonomous_container_databases.
- compartment_
id str - The OCID of the compartment.
- id str
- The provider-assigned unique ID for this managed resource.
- autonomous_
exadata_ strinfrastructure_ id - No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified
cloudAutonomousVmCluster
. - autonomous_
vm_ strcluster_ id - The OCID of the Autonomous VM Cluster.
- availability_
domain str - The availability domain of the Autonomous Container Database.
- cloud_
autonomous_ strvm_ cluster_ id - The OCID of the cloud Autonomous Exadata VM Cluster.
- display_
name str - The user-provided name for the Autonomous Container Database.
- filters
Sequence[database.
Get Autonomous Container Databases Filter] - infrastructure_
type str - The infrastructure type this resource belongs to.
- service_
level_ stragreement_ type - The service level agreement type of the container database. The default is STANDARD.
- state str
- The current state of the Autonomous Container Database.
- autonomous
Container List<Property Map>Databases - The list of autonomous_container_databases.
- compartment
Id String - The OCID of the compartment.
- id String
- The provider-assigned unique ID for this managed resource.
- autonomous
Exadata StringInfrastructure Id - No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified
cloudAutonomousVmCluster
. - autonomous
Vm StringCluster Id - The OCID of the Autonomous VM Cluster.
- availability
Domain String - The availability domain of the Autonomous Container Database.
- cloud
Autonomous StringVm Cluster Id - The OCID of the cloud Autonomous Exadata VM Cluster.
- display
Name String - The user-provided name for the Autonomous Container Database.
- filters List<Property Map>
- infrastructure
Type String - The infrastructure type this resource belongs to.
- service
Level StringAgreement Type - The service level agreement type of the container database. The default is STANDARD.
- state String
- The current state of the Autonomous Container Database.
Supporting Types
GetAutonomousContainerDatabasesAutonomousContainerDatabase
- Autonomous
Exadata stringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- Autonomous
Vm stringCluster Id - The Autonomous VM Cluster OCID.
- Availability
Domain string - A filter to return only resources that match the given availability domain exactly.
- Available
Cpus double - Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Backup
Configs List<GetAutonomous Container Databases Autonomous Container Database Backup Config> - Backup options for the Autonomous Container Database.
- Cloud
Autonomous stringVm Cluster Id - The cloud Autonomous VM Cluster OCID.
- Compartment
Id string - The compartment OCID.
- Compute
Model string - The compute model of the Autonomous Container Database. For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (ECPUs or OCPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. 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.
- Database
Software stringImage Id - Db
Name string - The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- Db
Split intThreshold - The CPU value beyond which an Autonomous Database will be opened across multiple nodes. The default value of this attribute is 16 for OCPUs and 64 for ECPUs.
- Db
Unique stringName - Db
Version string - Oracle Database version of the Autonomous Container Database.
- 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 - A filter to return only resources that match the entire display name given. The match is not case sensitive.
- Distribution
Affinity string - Determines whether an Autonomous Database must be opened across the maximum number of nodes or the least number of nodes. By default, Minimum nodes is selected.
- Dst
File stringVersion - DST Time-zone File version of the Autonomous Container Database.
- Fast
Start intFail Over Lag Limit In Seconds - 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 id of the Autonomous Database Vault service key management history entry.
- Infrastructure
Type string - A filter to return only resources that match the given Infrastructure Type.
- Is
Automatic boolFailover Enabled - Is
Dst boolFile Update Enabled - Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- Key
History List<GetEntries Autonomous Container Databases Autonomous Container Database Key History Entry> - Key History Entry.
- Key
Store stringId - The OCID of the key store of Oracle Vault.
- Key
Store stringWallet Name - The wallet name for Oracle Key Vault.
- Key
Version stringId - Kms
Key stringId - The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- Largest
Provisionable doubleAutonomous Database In Cpus - The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- Last
Maintenance stringRun Id - The OCID of the last maintenance run.
- Lifecycle
Details string - Additional information about the current lifecycle state.
- List
One List<string>Off Patches - List of One-Off patches that has been successfully applied to Autonomous Container Database
- Maintenance
Window List<GetDetails Autonomous Container Databases Autonomous Container Database Maintenance Window Detail> - Maintenance
Windows List<GetAutonomous Container Databases Autonomous Container Database Maintenance Window> - The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Memory
Per intOracle Compute Unit In Gbs - The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- Net
Services stringArchitecture - Enabling SHARED server architecture enables a database server to allow many client processes to share very few server processes, thereby increasing the number of supported users.
- Next
Maintenance stringRun Id - The OCID of the next maintenance run.
- Patch
Id string - The OCID of the last patch applied on the system.
- Patch
Model string - Database patch model preference.
- Peer
Autonomous List<GetContainer Database Backup Configs Autonomous Container Databases Autonomous Container Database Peer Autonomous Container Database Backup Config> - Peer
Autonomous stringContainer Database Compartment Id - Peer
Autonomous stringContainer Database Display Name - Peer
Autonomous stringExadata Infrastructure Id - Peer
Autonomous stringVm Cluster Id - Peer
Cloud stringAutonomous Vm Cluster Id - Peer
Db stringUnique Name - Protection
Mode string - Provisionable
Cpuses List<double> - An array of CPU values that can be used to successfully provision a single Autonomous Database.
- Provisioned
Cpus double - The number of CPUs provisioned in an Autonomous Container Database.
- Reclaimable
Cpus double - 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.
- Reserved
Cpus double - The number of CPUs reserved in an Autonomous Container Database.
- Role string
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- Rotate
Key boolTrigger - Service
Level stringAgreement Type - A filter to return only resources that match the given service level agreement type exactly.
- Standby
Maintenance intBuffer In Days - The scheduling detail for the quarterly maintenance window of the standby Autonomous Container Database. This value represents the number of days before scheduled maintenance of the primary database.
- State string
- A filter to return only resources that match the given lifecycle state exactly.
- Time
Created string - The date and time the Autonomous Container Database was created.
- Time
Of stringLast Backup - The timestamp of last successful backup. Here NULL value represents either there are no successful backups or backups are not configured for this Autonomous Container Database.
- Time
Snapshot stringStandby Revert - The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- Total
Cpus int - The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
- Vault
Id string - The OCID of the Oracle Cloud Infrastructure vault.
- Version
Preference string - The next maintenance version preference.
- Vm
Failover intReservation - The percentage of CPUs reserved across nodes to support node failover. Allowed values are 0%, 25%, and 50%, with 50% being the default option.
- Autonomous
Exadata stringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- Autonomous
Vm stringCluster Id - The Autonomous VM Cluster OCID.
- Availability
Domain string - A filter to return only resources that match the given availability domain exactly.
- Available
Cpus float64 - Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Backup
Configs []GetAutonomous Container Databases Autonomous Container Database Backup Config - Backup options for the Autonomous Container Database.
- Cloud
Autonomous stringVm Cluster Id - The cloud Autonomous VM Cluster OCID.
- Compartment
Id string - The compartment OCID.
- Compute
Model string - The compute model of the Autonomous Container Database. For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (ECPUs or OCPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. 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.
- Database
Software stringImage Id - Db
Name string - The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- Db
Split intThreshold - The CPU value beyond which an Autonomous Database will be opened across multiple nodes. The default value of this attribute is 16 for OCPUs and 64 for ECPUs.
- Db
Unique stringName - Db
Version string - Oracle Database version of the Autonomous Container Database.
- 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 - A filter to return only resources that match the entire display name given. The match is not case sensitive.
- Distribution
Affinity string - Determines whether an Autonomous Database must be opened across the maximum number of nodes or the least number of nodes. By default, Minimum nodes is selected.
- Dst
File stringVersion - DST Time-zone File version of the Autonomous Container Database.
- Fast
Start intFail Over Lag Limit In Seconds - 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 id of the Autonomous Database Vault service key management history entry.
- Infrastructure
Type string - A filter to return only resources that match the given Infrastructure Type.
- Is
Automatic boolFailover Enabled - Is
Dst boolFile Update Enabled - Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- Key
History []GetEntries Autonomous Container Databases Autonomous Container Database Key History Entry - Key History Entry.
- Key
Store stringId - The OCID of the key store of Oracle Vault.
- Key
Store stringWallet Name - The wallet name for Oracle Key Vault.
- Key
Version stringId - Kms
Key stringId - The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- Largest
Provisionable float64Autonomous Database In Cpus - The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- Last
Maintenance stringRun Id - The OCID of the last maintenance run.
- Lifecycle
Details string - Additional information about the current lifecycle state.
- List
One []stringOff Patches - List of One-Off patches that has been successfully applied to Autonomous Container Database
- Maintenance
Window []GetDetails Autonomous Container Databases Autonomous Container Database Maintenance Window Detail - Maintenance
Windows []GetAutonomous Container Databases Autonomous Container Database Maintenance Window - The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Memory
Per intOracle Compute Unit In Gbs - The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- Net
Services stringArchitecture - Enabling SHARED server architecture enables a database server to allow many client processes to share very few server processes, thereby increasing the number of supported users.
- Next
Maintenance stringRun Id - The OCID of the next maintenance run.
- Patch
Id string - The OCID of the last patch applied on the system.
- Patch
Model string - Database patch model preference.
- Peer
Autonomous []GetContainer Database Backup Configs Autonomous Container Databases Autonomous Container Database Peer Autonomous Container Database Backup Config - Peer
Autonomous stringContainer Database Compartment Id - Peer
Autonomous stringContainer Database Display Name - Peer
Autonomous stringExadata Infrastructure Id - Peer
Autonomous stringVm Cluster Id - Peer
Cloud stringAutonomous Vm Cluster Id - Peer
Db stringUnique Name - Protection
Mode string - Provisionable
Cpuses []float64 - An array of CPU values that can be used to successfully provision a single Autonomous Database.
- Provisioned
Cpus float64 - The number of CPUs provisioned in an Autonomous Container Database.
- Reclaimable
Cpus float64 - 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.
- Reserved
Cpus float64 - The number of CPUs reserved in an Autonomous Container Database.
- Role string
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- Rotate
Key boolTrigger - Service
Level stringAgreement Type - A filter to return only resources that match the given service level agreement type exactly.
- Standby
Maintenance intBuffer In Days - The scheduling detail for the quarterly maintenance window of the standby Autonomous Container Database. This value represents the number of days before scheduled maintenance of the primary database.
- State string
- A filter to return only resources that match the given lifecycle state exactly.
- Time
Created string - The date and time the Autonomous Container Database was created.
- Time
Of stringLast Backup - The timestamp of last successful backup. Here NULL value represents either there are no successful backups or backups are not configured for this Autonomous Container Database.
- Time
Snapshot stringStandby Revert - The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- Total
Cpus int - The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
- Vault
Id string - The OCID of the Oracle Cloud Infrastructure vault.
- Version
Preference string - The next maintenance version preference.
- Vm
Failover intReservation - The percentage of CPUs reserved across nodes to support node failover. Allowed values are 0%, 25%, and 50%, with 50% being the default option.
- autonomous
Exadata StringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- autonomous
Vm StringCluster Id - The Autonomous VM Cluster OCID.
- availability
Domain String - A filter to return only resources that match the given availability domain exactly.
- available
Cpus Double - Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- backup
Configs List<GetAutonomous Containers Autonomous Container Backup Config> - Backup options for the Autonomous Container Database.
- cloud
Autonomous StringVm Cluster Id - The cloud Autonomous VM Cluster OCID.
- compartment
Id String - The compartment OCID.
- compute
Model String - The compute model of the Autonomous Container Database. For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (ECPUs or OCPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. 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.
- database
Software StringImage Id - db
Name String - The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- db
Split IntegerThreshold - The CPU value beyond which an Autonomous Database will be opened across multiple nodes. The default value of this attribute is 16 for OCPUs and 64 for ECPUs.
- db
Unique StringName - db
Version String - Oracle Database version of the Autonomous Container Database.
- 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 - A filter to return only resources that match the entire display name given. The match is not case sensitive.
- distribution
Affinity String - Determines whether an Autonomous Database must be opened across the maximum number of nodes or the least number of nodes. By default, Minimum nodes is selected.
- dst
File StringVersion - DST Time-zone File version of the Autonomous Container Database.
- fast
Start IntegerFail Over Lag Limit In Seconds - 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 id of the Autonomous Database Vault service key management history entry.
- infrastructure
Type String - A filter to return only resources that match the given Infrastructure Type.
- is
Automatic BooleanFailover Enabled - is
Dst BooleanFile Update Enabled - Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- key
History List<GetEntries Autonomous Containers Autonomous Container Key History Entry> - Key History Entry.
- key
Store StringId - The OCID of the key store of Oracle Vault.
- key
Store StringWallet Name - The wallet name for Oracle Key Vault.
- key
Version StringId - kms
Key StringId - The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- largest
Provisionable DoubleAutonomous Database In Cpus - The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- last
Maintenance StringRun Id - The OCID of the last maintenance run.
- lifecycle
Details String - Additional information about the current lifecycle state.
- list
One List<String>Off Patches - List of One-Off patches that has been successfully applied to Autonomous Container Database
- maintenance
Window List<GetDetails Autonomous Containers Autonomous Container Maintenance Window Detail> - maintenance
Windows List<GetAutonomous Containers Autonomous Container Maintenance Window> - The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per IntegerOracle Compute Unit In Gbs - The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- net
Services StringArchitecture - Enabling SHARED server architecture enables a database server to allow many client processes to share very few server processes, thereby increasing the number of supported users.
- next
Maintenance StringRun Id - The OCID of the next maintenance run.
- patch
Id String - The OCID of the last patch applied on the system.
- patch
Model String - Database patch model preference.
- peer
Autonomous List<GetContainer Database Backup Configs Autonomous Containers Autonomous Container Peer Autonomous Container Backup Config> - peer
Autonomous StringContainer Database Compartment Id - peer
Autonomous StringContainer Database Display Name - peer
Autonomous StringExadata Infrastructure Id - peer
Autonomous StringVm Cluster Id - peer
Cloud StringAutonomous Vm Cluster Id - peer
Db StringUnique Name - protection
Mode String - provisionable
Cpuses List<Double> - An array of CPU values that can be used to successfully provision a single Autonomous Database.
- provisioned
Cpus Double - The number of CPUs provisioned in an Autonomous Container Database.
- reclaimable
Cpus Double - 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.
- reserved
Cpus Double - The number of CPUs reserved in an Autonomous Container Database.
- role String
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- rotate
Key BooleanTrigger - service
Level StringAgreement Type - A filter to return only resources that match the given service level agreement type exactly.
- standby
Maintenance IntegerBuffer In Days - The scheduling detail for the quarterly maintenance window of the standby Autonomous Container Database. This value represents the number of days before scheduled maintenance of the primary database.
- state String
- A filter to return only resources that match the given lifecycle state exactly.
- time
Created String - The date and time the Autonomous Container Database was created.
- time
Of StringLast Backup - The timestamp of last successful backup. Here NULL value represents either there are no successful backups or backups are not configured for this Autonomous Container Database.
- time
Snapshot StringStandby Revert - The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- total
Cpus Integer - The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
- vault
Id String - The OCID of the Oracle Cloud Infrastructure vault.
- version
Preference String - The next maintenance version preference.
- vm
Failover IntegerReservation - The percentage of CPUs reserved across nodes to support node failover. Allowed values are 0%, 25%, and 50%, with 50% being the default option.
- autonomous
Exadata stringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- autonomous
Vm stringCluster Id - The Autonomous VM Cluster OCID.
- availability
Domain string - A filter to return only resources that match the given availability domain exactly.
- available
Cpus number - Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- backup
Configs GetAutonomous Container Databases Autonomous Container Database Backup Config[] - Backup options for the Autonomous Container Database.
- cloud
Autonomous stringVm Cluster Id - The cloud Autonomous VM Cluster OCID.
- compartment
Id string - The compartment OCID.
- compute
Model string - The compute model of the Autonomous Container Database. For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (ECPUs or OCPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. 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.
- database
Software stringImage Id - db
Name string - The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- db
Split numberThreshold - The CPU value beyond which an Autonomous Database will be opened across multiple nodes. The default value of this attribute is 16 for OCPUs and 64 for ECPUs.
- db
Unique stringName - db
Version string - Oracle Database version of the Autonomous Container Database.
- {[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 - A filter to return only resources that match the entire display name given. The match is not case sensitive.
- distribution
Affinity string - Determines whether an Autonomous Database must be opened across the maximum number of nodes or the least number of nodes. By default, Minimum nodes is selected.
- dst
File stringVersion - DST Time-zone File version of the Autonomous Container Database.
- fast
Start numberFail Over Lag Limit In Seconds - {[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 id of the Autonomous Database Vault service key management history entry.
- infrastructure
Type string - A filter to return only resources that match the given Infrastructure Type.
- is
Automatic booleanFailover Enabled - is
Dst booleanFile Update Enabled - Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- key
History GetEntries Autonomous Container Databases Autonomous Container Database Key History Entry[] - Key History Entry.
- key
Store stringId - The OCID of the key store of Oracle Vault.
- key
Store stringWallet Name - The wallet name for Oracle Key Vault.
- key
Version stringId - kms
Key stringId - The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- largest
Provisionable numberAutonomous Database In Cpus - The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- last
Maintenance stringRun Id - The OCID of the last maintenance run.
- lifecycle
Details string - Additional information about the current lifecycle state.
- list
One string[]Off Patches - List of One-Off patches that has been successfully applied to Autonomous Container Database
- maintenance
Window GetDetails Autonomous Container Databases Autonomous Container Database Maintenance Window Detail[] - maintenance
Windows GetAutonomous Container Databases Autonomous Container Database Maintenance Window[] - The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per numberOracle Compute Unit In Gbs - The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- net
Services stringArchitecture - Enabling SHARED server architecture enables a database server to allow many client processes to share very few server processes, thereby increasing the number of supported users.
- next
Maintenance stringRun Id - The OCID of the next maintenance run.
- patch
Id string - The OCID of the last patch applied on the system.
- patch
Model string - Database patch model preference.
- peer
Autonomous GetContainer Database Backup Configs Autonomous Container Databases Autonomous Container Database Peer Autonomous Container Database Backup Config[] - peer
Autonomous stringContainer Database Compartment Id - peer
Autonomous stringContainer Database Display Name - peer
Autonomous stringExadata Infrastructure Id - peer
Autonomous stringVm Cluster Id - peer
Cloud stringAutonomous Vm Cluster Id - peer
Db stringUnique Name - protection
Mode string - provisionable
Cpuses number[] - An array of CPU values that can be used to successfully provision a single Autonomous Database.
- provisioned
Cpus number - The number of CPUs provisioned in an Autonomous Container Database.
- reclaimable
Cpus number - 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.
- reserved
Cpus number - The number of CPUs reserved in an Autonomous Container Database.
- role string
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- rotate
Key booleanTrigger - service
Level stringAgreement Type - A filter to return only resources that match the given service level agreement type exactly.
- standby
Maintenance numberBuffer In Days - The scheduling detail for the quarterly maintenance window of the standby Autonomous Container Database. This value represents the number of days before scheduled maintenance of the primary database.
- state string
- A filter to return only resources that match the given lifecycle state exactly.
- time
Created string - The date and time the Autonomous Container Database was created.
- time
Of stringLast Backup - The timestamp of last successful backup. Here NULL value represents either there are no successful backups or backups are not configured for this Autonomous Container Database.
- time
Snapshot stringStandby Revert - The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- total
Cpus number - The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
- vault
Id string - The OCID of the Oracle Cloud Infrastructure vault.
- version
Preference string - The next maintenance version preference.
- vm
Failover numberReservation - The percentage of CPUs reserved across nodes to support node failover. Allowed values are 0%, 25%, and 50%, with 50% being the default option.
- autonomous_
exadata_ strinfrastructure_ id - The Autonomous Exadata Infrastructure OCID.
- autonomous_
vm_ strcluster_ id - The Autonomous VM Cluster OCID.
- availability_
domain str - A filter to return only resources that match the given availability domain exactly.
- available_
cpus float - Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- backup_
configs Sequence[database.Get Autonomous Container Databases Autonomous Container Database Backup Config] - Backup options for the Autonomous Container Database.
- cloud_
autonomous_ strvm_ cluster_ id - The cloud Autonomous VM Cluster OCID.
- compartment_
id str - The compartment OCID.
- compute_
model str - The compute model of the Autonomous Container Database. For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (ECPUs or OCPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. 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.
- database_
software_ strimage_ id - db_
name str - The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- db_
split_ intthreshold - The CPU value beyond which an Autonomous Database will be opened across multiple nodes. The default value of this attribute is 16 for OCPUs and 64 for ECPUs.
- db_
unique_ strname - db_
version str - Oracle Database version of the Autonomous Container Database.
- 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 - A filter to return only resources that match the entire display name given. The match is not case sensitive.
- distribution_
affinity str - Determines whether an Autonomous Database must be opened across the maximum number of nodes or the least number of nodes. By default, Minimum nodes is selected.
- dst_
file_ strversion - DST Time-zone File version of the Autonomous Container Database.
- fast_
start_ intfail_ over_ lag_ limit_ in_ seconds - 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 id of the Autonomous Database Vault service key management history entry.
- infrastructure_
type str - A filter to return only resources that match the given Infrastructure Type.
- is_
automatic_ boolfailover_ enabled - is_
dst_ boolfile_ update_ enabled - Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- key_
history_ Sequence[database.entries Get Autonomous Container Databases Autonomous Container Database Key History Entry] - Key History Entry.
- key_
store_ strid - The OCID of the key store of Oracle Vault.
- key_
store_ strwallet_ name - The wallet name for Oracle Key Vault.
- key_
version_ strid - kms_
key_ strid - The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- largest_
provisionable_ floatautonomous_ database_ in_ cpus - The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- last_
maintenance_ strrun_ id - The OCID of the last maintenance run.
- lifecycle_
details str - Additional information about the current lifecycle state.
- list_
one_ Sequence[str]off_ patches - List of One-Off patches that has been successfully applied to Autonomous Container Database
- maintenance_
window_ Sequence[database.details Get Autonomous Container Databases Autonomous Container Database Maintenance Window Detail] - maintenance_
windows Sequence[database.Get Autonomous Container Databases Autonomous Container Database Maintenance Window] - The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory_
per_ intoracle_ compute_ unit_ in_ gbs - The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- net_
services_ strarchitecture - Enabling SHARED server architecture enables a database server to allow many client processes to share very few server processes, thereby increasing the number of supported users.
- next_
maintenance_ strrun_ id - The OCID of the next maintenance run.
- patch_
id str - The OCID of the last patch applied on the system.
- patch_
model str - Database patch model preference.
- peer_
autonomous_ Sequence[database.container_ database_ backup_ configs Get Autonomous Container Databases Autonomous Container Database Peer Autonomous Container Database Backup Config] - peer_
autonomous_ strcontainer_ database_ compartment_ id - peer_
autonomous_ strcontainer_ database_ display_ name - peer_
autonomous_ strexadata_ infrastructure_ id - peer_
autonomous_ strvm_ cluster_ id - peer_
cloud_ strautonomous_ vm_ cluster_ id - peer_
db_ strunique_ name - protection_
mode str - provisionable_
cpuses Sequence[float] - An array of CPU values that can be used to successfully provision a single Autonomous Database.
- provisioned_
cpus float - The number of CPUs provisioned in an Autonomous Container Database.
- reclaimable_
cpus float - 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.
- reserved_
cpus float - The number of CPUs reserved in an Autonomous Container Database.
- role str
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- rotate_
key_ booltrigger - service_
level_ stragreement_ type - A filter to return only resources that match the given service level agreement type exactly.
- standby_
maintenance_ intbuffer_ in_ days - The scheduling detail for the quarterly maintenance window of the standby Autonomous Container Database. This value represents the number of days before scheduled maintenance of the primary database.
- state str
- A filter to return only resources that match the given lifecycle state exactly.
- time_
created str - The date and time the Autonomous Container Database was created.
- time_
of_ strlast_ backup - The timestamp of last successful backup. Here NULL value represents either there are no successful backups or backups are not configured for this Autonomous Container Database.
- time_
snapshot_ strstandby_ revert - The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- total_
cpus int - The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
- vault_
id str - The OCID of the Oracle Cloud Infrastructure vault.
- version_
preference str - The next maintenance version preference.
- vm_
failover_ intreservation - The percentage of CPUs reserved across nodes to support node failover. Allowed values are 0%, 25%, and 50%, with 50% being the default option.
- autonomous
Exadata StringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- autonomous
Vm StringCluster Id - The Autonomous VM Cluster OCID.
- availability
Domain String - A filter to return only resources that match the given availability domain exactly.
- available
Cpus Number - Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- backup
Configs List<Property Map> - Backup options for the Autonomous Container Database.
- cloud
Autonomous StringVm Cluster Id - The cloud Autonomous VM Cluster OCID.
- compartment
Id String - The compartment OCID.
- compute
Model String - The compute model of the Autonomous Container Database. For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (ECPUs or OCPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. 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.
- database
Software StringImage Id - db
Name String - The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- db
Split NumberThreshold - The CPU value beyond which an Autonomous Database will be opened across multiple nodes. The default value of this attribute is 16 for OCPUs and 64 for ECPUs.
- db
Unique StringName - db
Version String - Oracle Database version of the Autonomous Container Database.
- 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 - A filter to return only resources that match the entire display name given. The match is not case sensitive.
- distribution
Affinity String - Determines whether an Autonomous Database must be opened across the maximum number of nodes or the least number of nodes. By default, Minimum nodes is selected.
- dst
File StringVersion - DST Time-zone File version of the Autonomous Container Database.
- fast
Start NumberFail Over Lag Limit In Seconds - 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 id of the Autonomous Database Vault service key management history entry.
- infrastructure
Type String - A filter to return only resources that match the given Infrastructure Type.
- is
Automatic BooleanFailover Enabled - is
Dst BooleanFile Update Enabled - Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- key
History List<Property Map>Entries - Key History Entry.
- key
Store StringId - The OCID of the key store of Oracle Vault.
- key
Store StringWallet Name - The wallet name for Oracle Key Vault.
- key
Version StringId - kms
Key StringId - The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- largest
Provisionable NumberAutonomous Database In Cpus - The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- last
Maintenance StringRun Id - The OCID of the last maintenance run.
- lifecycle
Details String - Additional information about the current lifecycle state.
- list
One List<String>Off Patches - List of One-Off patches that has been successfully applied to Autonomous Container Database
- 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.
- memory
Per NumberOracle Compute Unit In Gbs - The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- net
Services StringArchitecture - Enabling SHARED server architecture enables a database server to allow many client processes to share very few server processes, thereby increasing the number of supported users.
- next
Maintenance StringRun Id - The OCID of the next maintenance run.
- patch
Id String - The OCID of the last patch applied on the system.
- patch
Model String - Database patch model preference.
- peer
Autonomous List<Property Map>Container Database Backup Configs - peer
Autonomous StringContainer Database Compartment Id - peer
Autonomous StringContainer Database Display Name - peer
Autonomous StringExadata Infrastructure Id - peer
Autonomous StringVm Cluster Id - peer
Cloud StringAutonomous Vm Cluster Id - peer
Db StringUnique Name - protection
Mode String - provisionable
Cpuses List<Number> - An array of CPU values that can be used to successfully provision a single Autonomous Database.
- provisioned
Cpus Number - The number of CPUs provisioned in an Autonomous Container Database.
- reclaimable
Cpus Number - 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.
- reserved
Cpus Number - The number of CPUs reserved in an Autonomous Container Database.
- role String
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- rotate
Key BooleanTrigger - service
Level StringAgreement Type - A filter to return only resources that match the given service level agreement type exactly.
- standby
Maintenance NumberBuffer In Days - The scheduling detail for the quarterly maintenance window of the standby Autonomous Container Database. This value represents the number of days before scheduled maintenance of the primary database.
- state String
- A filter to return only resources that match the given lifecycle state exactly.
- time
Created String - The date and time the Autonomous Container Database was created.
- time
Of StringLast Backup - The timestamp of last successful backup. Here NULL value represents either there are no successful backups or backups are not configured for this Autonomous Container Database.
- time
Snapshot StringStandby Revert - The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- total
Cpus Number - The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
- vault
Id String - The OCID of the Oracle Cloud Infrastructure vault.
- version
Preference String - The next maintenance version preference.
- vm
Failover NumberReservation - The percentage of CPUs reserved across nodes to support node failover. Allowed values are 0%, 25%, and 50%, with 50% being the default option.
GetAutonomousContainerDatabasesAutonomousContainerDatabaseBackupConfig
- Backup
Destination List<GetDetails Autonomous Container Databases Autonomous Container Database Backup Config Backup Destination Detail> - Backup destination details.
- Recovery
Window intIn Days - Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups. If the number of specified days is 0 then there will be no backups.
- Backup
Destination []GetDetails Autonomous Container Databases Autonomous Container Database Backup Config Backup Destination Detail - Backup destination details.
- Recovery
Window intIn Days - Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups. If the number of specified days is 0 then there will be no backups.
- backup
Destination List<GetDetails Autonomous Containers Autonomous Container Backup Config Backup Destination Detail> - Backup destination details.
- recovery
Window IntegerIn Days - Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups. If the number of specified days is 0 then there will be no backups.
- backup
Destination GetDetails Autonomous Container Databases Autonomous Container Database Backup Config Backup Destination Detail[] - Backup destination details.
- recovery
Window numberIn Days - Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups. If the number of specified days is 0 then there will be no backups.
- backup_
destination_ Sequence[database.details Get Autonomous Container Databases Autonomous Container Database Backup Config Backup Destination Detail] - Backup destination details.
- recovery_
window_ intin_ days - Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups. If the number of specified days is 0 then there will be no backups.
- backup
Destination List<Property Map>Details - Backup destination details.
- recovery
Window NumberIn Days - Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups. If the number of specified days is 0 then there will be no backups.
GetAutonomousContainerDatabasesAutonomousContainerDatabaseBackupConfigBackupDestinationDetail
- Id string
- The id of the Autonomous Database Vault service key management history entry.
- Internet
Proxy string - Proxy URL to connect to object store.
- Type string
- Type of the database backup destination.
- Vpc
Password string - For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- Vpc
User string - For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- Id string
- The id of the Autonomous Database Vault service key management history entry.
- Internet
Proxy string - Proxy URL to connect to object store.
- Type string
- Type of the database backup destination.
- Vpc
Password string - For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- Vpc
User string - For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id String
- The id of the Autonomous Database Vault service key management history entry.
- internet
Proxy String - Proxy URL to connect to object store.
- type String
- Type of the database backup destination.
- vpc
Password String - For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User String - For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id string
- The id of the Autonomous Database Vault service key management history entry.
- internet
Proxy string - Proxy URL to connect to object store.
- type string
- Type of the database backup destination.
- vpc
Password string - For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User string - For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id str
- The id of the Autonomous Database Vault service key management history entry.
- internet_
proxy str - Proxy URL to connect to object store.
- type str
- Type of the database backup destination.
- vpc_
password str - For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc_
user str - For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id String
- The id of the Autonomous Database Vault service key management history entry.
- internet
Proxy String - Proxy URL to connect to object store.
- type String
- Type of the database backup destination.
- vpc
Password String - For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User String - For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
GetAutonomousContainerDatabasesAutonomousContainerDatabaseKeyHistoryEntry
- Id string
- The id of the Autonomous Database Vault service key management history entry.
- Kms
Key stringVersion Id - The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation. Autonomous Database Serverless does not use key versions, hence is not applicable for Autonomous Database Serverless instances.
- Time
Activated string - The date and time the kms key activated.
- Vault
Id string - The OCID of the Oracle Cloud Infrastructure vault.
- Id string
- The id of the Autonomous Database Vault service key management history entry.
- Kms
Key stringVersion Id - The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation. Autonomous Database Serverless does not use key versions, hence is not applicable for Autonomous Database Serverless instances.
- Time
Activated string - The date and time the kms key activated.
- Vault
Id string - The OCID of the Oracle Cloud Infrastructure vault.
- id String
- The id of the Autonomous Database Vault service key management history entry.
- kms
Key StringVersion Id - The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation. Autonomous Database Serverless does not use key versions, hence is not applicable for Autonomous Database Serverless instances.
- time
Activated String - The date and time the kms key activated.
- vault
Id String - The OCID of the Oracle Cloud Infrastructure vault.
- id string
- The id of the Autonomous Database Vault service key management history entry.
- kms
Key stringVersion Id - The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation. Autonomous Database Serverless does not use key versions, hence is not applicable for Autonomous Database Serverless instances.
- time
Activated string - The date and time the kms key activated.
- vault
Id string - The OCID of the Oracle Cloud Infrastructure vault.
- id str
- The id of the Autonomous Database Vault service key management history entry.
- kms_
key_ strversion_ id - The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation. Autonomous Database Serverless does not use key versions, hence is not applicable for Autonomous Database Serverless instances.
- time_
activated str - The date and time the kms key activated.
- vault_
id str - The OCID of the Oracle Cloud Infrastructure vault.
- id String
- The id of the Autonomous Database Vault service key management history entry.
- kms
Key StringVersion Id - The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation. Autonomous Database Serverless does not use key versions, hence is not applicable for Autonomous Database Serverless instances.
- time
Activated String - The date and time the kms key activated.
- vault
Id String - The OCID of the Oracle Cloud Infrastructure vault.
GetAutonomousContainerDatabasesAutonomousContainerDatabaseMaintenanceWindow
- 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 Autonomous Container Databases Autonomous Container Database 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
Autonomous Container Databases Autonomous Container Database 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> - 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 - 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 Autonomous Container Databases Autonomous Container Database 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
Autonomous Container Databases Autonomous Container Database 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 - 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 - 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 Autonomous Containers Autonomous Container 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
Autonomous Containers Autonomous Container 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> - 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 - 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 Autonomous Container Databases Autonomous Container Database 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
Autonomous Container Databases Autonomous Container Database 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[] - 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 - 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 Autonomous Container Databases Autonomous Container Database 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 Autonomous Container Databases Autonomous Container Database Maintenance Window Month] - Months during the year when maintenance should be performed.
- patching_
mode str - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference str
- The maintenance window scheduling preference.
- skip_
rus Sequence[bool] - If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeks_
of_ Sequence[int]months - Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- 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> - 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.
GetAutonomousContainerDatabasesAutonomousContainerDatabaseMaintenanceWindowDaysOfWeek
- 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.
GetAutonomousContainerDatabasesAutonomousContainerDatabaseMaintenanceWindowDetail
- 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 Autonomous Container Databases Autonomous Container Database 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
Autonomous Container Databases Autonomous Container Database 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> - 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 - 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 Autonomous Container Databases Autonomous Container Database 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
Autonomous Container Databases Autonomous Container Database 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 - 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 - 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 Autonomous Containers Autonomous Container 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
Autonomous Containers Autonomous Container 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> - 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 - 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 Autonomous Container Databases Autonomous Container Database 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
Autonomous Container Databases Autonomous Container Database 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[] - 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 - 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 Autonomous Container Databases Autonomous Container Database 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 Autonomous Container Databases Autonomous Container Database Maintenance Window Detail Month] - Months during the year when maintenance should be performed.
- patching_
mode str - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference str
- The maintenance window scheduling preference.
- skip_
rus Sequence[bool] - If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeks_
of_ Sequence[int]months - Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- 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> - 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.
GetAutonomousContainerDatabasesAutonomousContainerDatabaseMaintenanceWindowDetailDaysOfWeek
- 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.
GetAutonomousContainerDatabasesAutonomousContainerDatabaseMaintenanceWindowDetailMonth
- 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.
GetAutonomousContainerDatabasesAutonomousContainerDatabaseMaintenanceWindowMonth
- 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.
GetAutonomousContainerDatabasesAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfig
- Backup
Destination List<GetDetails Autonomous Container Databases Autonomous Container Database Peer Autonomous Container Database Backup Config Backup Destination Detail> - Backup destination details.
- Recovery
Window intIn Days - Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups. If the number of specified days is 0 then there will be no backups.
- Backup
Destination []GetDetails Autonomous Container Databases Autonomous Container Database Peer Autonomous Container Database Backup Config Backup Destination Detail - Backup destination details.
- Recovery
Window intIn Days - Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups. If the number of specified days is 0 then there will be no backups.
- backup
Destination List<GetDetails Autonomous Containers Autonomous Container Peer Autonomous Container Backup Config Backup Destination Detail> - Backup destination details.
- recovery
Window IntegerIn Days - Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups. If the number of specified days is 0 then there will be no backups.
- backup
Destination GetDetails Autonomous Container Databases Autonomous Container Database Peer Autonomous Container Database Backup Config Backup Destination Detail[] - Backup destination details.
- recovery
Window numberIn Days - Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups. If the number of specified days is 0 then there will be no backups.
- backup_
destination_ Sequence[database.details Get Autonomous Container Databases Autonomous Container Database Peer Autonomous Container Database Backup Config Backup Destination Detail] - Backup destination details.
- recovery_
window_ intin_ days - Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups. If the number of specified days is 0 then there will be no backups.
- backup
Destination List<Property Map>Details - Backup destination details.
- recovery
Window NumberIn Days - Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups. If the number of specified days is 0 then there will be no backups.
GetAutonomousContainerDatabasesAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetail
- Id string
- The id of the Autonomous Database Vault service key management history entry.
- Internet
Proxy string - Proxy URL to connect to object store.
- Type string
- Type of the database backup destination.
- Vpc
Password string - For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- Vpc
User string - For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- Id string
- The id of the Autonomous Database Vault service key management history entry.
- Internet
Proxy string - Proxy URL to connect to object store.
- Type string
- Type of the database backup destination.
- Vpc
Password string - For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- Vpc
User string - For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id String
- The id of the Autonomous Database Vault service key management history entry.
- internet
Proxy String - Proxy URL to connect to object store.
- type String
- Type of the database backup destination.
- vpc
Password String - For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User String - For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id string
- The id of the Autonomous Database Vault service key management history entry.
- internet
Proxy string - Proxy URL to connect to object store.
- type string
- Type of the database backup destination.
- vpc
Password string - For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User string - For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id str
- The id of the Autonomous Database Vault service key management history entry.
- internet_
proxy str - Proxy URL to connect to object store.
- type str
- Type of the database backup destination.
- vpc_
password str - For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc_
user str - For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id String
- The id of the Autonomous Database Vault service key management history entry.
- internet
Proxy String - Proxy URL to connect to object store.
- type String
- Type of the database backup destination.
- vpc
Password String - For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User String - For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
GetAutonomousContainerDatabasesFilter
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
oci
Terraform Provider.