Docs Packages
  1. Pulumi Registry
  2. Oracle Cloud Infrastructure
  3. API Docs
  4. Database
  5. getAutonomousContainerDatabase
oci logo
Oracle Cloud Infrastructure v0.19.0, May 26 23

oci.Database.getAutonomousContainerDatabase

Explore with Pulumi AI

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

Gets information about the specified Autonomous Container Database.

Example Usage

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

return await Deployment.RunAsync(() => 
{
    var testAutonomousContainerDatabase = Oci.Database.GetAutonomousContainerDatabase.Invoke(new()
    {
        AutonomousContainerDatabaseId = oci_database_autonomous_container_database.Test_autonomous_container_database.Id,
    });

});

package main

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

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := Database.GetAutonomousContainerDatabase(ctx, &database.GetAutonomousContainerDatabaseArgs{
			AutonomousContainerDatabaseId: oci_database_autonomous_container_database.Test_autonomous_container_database.Id,
		}, nil)
		if err != nil {
			return err
		}
		return nil
	})
}

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Database.DatabaseFunctions;
import com.pulumi.oci.Database.inputs.GetAutonomousContainerDatabaseArgs;
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 testAutonomousContainerDatabase = DatabaseFunctions.getAutonomousContainerDatabase(GetAutonomousContainerDatabaseArgs.builder()
            .autonomousContainerDatabaseId(oci_database_autonomous_container_database.test_autonomous_container_database().id())
            .build());

    }
}

import pulumi
import pulumi_oci as oci

test_autonomous_container_database = oci.Database.get_autonomous_container_database(autonomous_container_database_id=%!v(PANIC=Format method: runtime error: invalid memory address or nil pointer dereference))

import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";

const testAutonomousContainerDatabase = oci.Database.getAutonomousContainerDatabase({
    autonomousContainerDatabaseId: oci_database_autonomous_container_database.test_autonomous_container_database.id,
});

variables:
  testAutonomousContainerDatabase:
    fn::invoke:
      Function: oci:Database:getAutonomousContainerDatabase
      Arguments:
        autonomousContainerDatabaseId: ${oci_database_autonomous_container_database.test_autonomous_container_database.id}

Using getAutonomousContainerDatabase

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 getAutonomousContainerDatabase(args: GetAutonomousContainerDatabaseArgs, opts?: InvokeOptions): Promise<GetAutonomousContainerDatabaseResult>
function getAutonomousContainerDatabaseOutput(args: GetAutonomousContainerDatabaseOutputArgs, opts?: InvokeOptions): Output<GetAutonomousContainerDatabaseResult>
def get_autonomous_container_database(autonomous_container_database_id: Optional[str] = None,
                                      opts: Optional[InvokeOptions] = None) -> GetAutonomousContainerDatabaseResult
def get_autonomous_container_database_output(autonomous_container_database_id: Optional[pulumi.Input[str]] = None,
                                      opts: Optional[InvokeOptions] = None) -> Output[GetAutonomousContainerDatabaseResult]
func GetAutonomousContainerDatabase(ctx *Context, args *GetAutonomousContainerDatabaseArgs, opts ...InvokeOption) (*GetAutonomousContainerDatabaseResult, error)
func GetAutonomousContainerDatabaseOutput(ctx *Context, args *GetAutonomousContainerDatabaseOutputArgs, opts ...InvokeOption) GetAutonomousContainerDatabaseResultOutput

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

public static class GetAutonomousContainerDatabase 
{
    public static Task<GetAutonomousContainerDatabaseResult> InvokeAsync(GetAutonomousContainerDatabaseArgs args, InvokeOptions? opts = null)
    public static Output<GetAutonomousContainerDatabaseResult> Invoke(GetAutonomousContainerDatabaseInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetAutonomousContainerDatabaseResult> getAutonomousContainerDatabase(GetAutonomousContainerDatabaseArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet

fn::invoke:
  function: oci:Database/getAutonomousContainerDatabase:getAutonomousContainerDatabase
  arguments:
    # arguments dictionary

The following arguments are supported:

AutonomousContainerDatabaseId string

The Autonomous Container Database OCID.

AutonomousContainerDatabaseId string

The Autonomous Container Database OCID.

autonomousContainerDatabaseId String

The Autonomous Container Database OCID.

autonomousContainerDatabaseId string

The Autonomous Container Database OCID.

autonomous_container_database_id str

The Autonomous Container Database OCID.

autonomousContainerDatabaseId String

The Autonomous Container Database OCID.

getAutonomousContainerDatabase Result

The following output properties are available:

AutonomousContainerDatabaseId string
AutonomousExadataInfrastructureId string

No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.

AutonomousVmClusterId string

The OCID of the Autonomous VM Cluster.

AvailabilityDomain string

The availability domain of the Autonomous Container Database.

AvailableCpus 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.

BackupConfigs List<GetAutonomousContainerDatabaseBackupConfig>

Backup options for the Autonomous Container Database.

CloudAutonomousVmClusterId string

The OCID of the cloud Autonomous Exadata VM Cluster.

CompartmentId string

The OCID of the compartment.

ComputeModel string

The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.

DbName 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.

DbUniqueName string
DbVersion string

Oracle Database version of the Autonomous Container Database.

DefinedTags Dictionary<string, object>

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

DisplayName string

The user-provided name for the Autonomous Container Database.

FastStartFailOverLagLimitInSeconds int
FreeformTags Dictionary<string, object>

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

Id string

The id of the Autonomous Database Vault service key management history entry.

InfrastructureType string

The infrastructure type this resource belongs to.

IsAutomaticFailoverEnabled bool
KeyHistoryEntries List<GetAutonomousContainerDatabaseKeyHistoryEntry>

Key History Entry.

KeyStoreId string

The OCID of the key store.

KeyStoreWalletName string

The wallet name for Oracle Key Vault.

KmsKeyId string

The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.

LastMaintenanceRunId string

The OCID of the last maintenance run.

LifecycleDetails string

Additional information about the current lifecycle state.

MaintenanceWindowDetails List<GetAutonomousContainerDatabaseMaintenanceWindowDetail>
MaintenanceWindows List<GetAutonomousContainerDatabaseMaintenanceWindow>

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

MemoryPerOracleComputeUnitInGbs int

The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.

NextMaintenanceRunId string

The OCID of the next maintenance run.

PatchId string

The OCID of the last patch applied on the system.

PatchModel string

Database patch model preference.

PeerAutonomousContainerDatabaseBackupConfigs List<GetAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfig>
PeerAutonomousContainerDatabaseCompartmentId string
PeerAutonomousContainerDatabaseDisplayName string
PeerAutonomousExadataInfrastructureId string
PeerAutonomousVmClusterId string
PeerCloudAutonomousVmClusterId string
PeerDbUniqueName string
ProtectionMode string
ProvisionableCpuses List<double>

An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database 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.

ReclaimableCpus double

For Autonomous Databases on Dedicated Exadata Infrastructure:

  • These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
  • The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
Role string

The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.

RotateKeyTrigger bool
ServiceLevelAgreementType string

The service level agreement type of the container database. The default is STANDARD.

StandbyMaintenanceBufferInDays int

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

The current state of the Autonomous Container Database.

TimeCreated string

The date and time the Autonomous Container Database was created.

TimeSnapshotStandbyRevert string

The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.

TotalCpus 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. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.

VaultId string

The OCID of the Oracle Cloud Infrastructure vault.

VersionPreference string

The next maintenance version preference.

AutonomousContainerDatabaseId string
AutonomousExadataInfrastructureId string

No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.

AutonomousVmClusterId string

The OCID of the Autonomous VM Cluster.

AvailabilityDomain string

The availability domain of the Autonomous Container Database.

AvailableCpus 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.

BackupConfigs []GetAutonomousContainerDatabaseBackupConfig

Backup options for the Autonomous Container Database.

CloudAutonomousVmClusterId string

The OCID of the cloud Autonomous Exadata VM Cluster.

CompartmentId string

The OCID of the compartment.

ComputeModel string

The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.

DbName 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.

DbUniqueName string
DbVersion string

Oracle Database version of the Autonomous Container Database.

DefinedTags map[string]interface{}

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

DisplayName string

The user-provided name for the Autonomous Container Database.

FastStartFailOverLagLimitInSeconds int
FreeformTags map[string]interface{}

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

Id string

The id of the Autonomous Database Vault service key management history entry.

InfrastructureType string

The infrastructure type this resource belongs to.

IsAutomaticFailoverEnabled bool
KeyHistoryEntries []GetAutonomousContainerDatabaseKeyHistoryEntry

Key History Entry.

KeyStoreId string

The OCID of the key store.

KeyStoreWalletName string

The wallet name for Oracle Key Vault.

KmsKeyId string

The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.

LastMaintenanceRunId string

The OCID of the last maintenance run.

LifecycleDetails string

Additional information about the current lifecycle state.

MaintenanceWindowDetails []GetAutonomousContainerDatabaseMaintenanceWindowDetail
MaintenanceWindows []GetAutonomousContainerDatabaseMaintenanceWindow

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

MemoryPerOracleComputeUnitInGbs int

The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.

NextMaintenanceRunId string

The OCID of the next maintenance run.

PatchId string

The OCID of the last patch applied on the system.

PatchModel string

Database patch model preference.

PeerAutonomousContainerDatabaseBackupConfigs []GetAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfig
PeerAutonomousContainerDatabaseCompartmentId string
PeerAutonomousContainerDatabaseDisplayName string
PeerAutonomousExadataInfrastructureId string
PeerAutonomousVmClusterId string
PeerCloudAutonomousVmClusterId string
PeerDbUniqueName string
ProtectionMode string
ProvisionableCpuses []float64

An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database 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.

ReclaimableCpus float64

For Autonomous Databases on Dedicated Exadata Infrastructure:

  • These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
  • The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
Role string

The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.

RotateKeyTrigger bool
ServiceLevelAgreementType string

The service level agreement type of the container database. The default is STANDARD.

StandbyMaintenanceBufferInDays int

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

The current state of the Autonomous Container Database.

TimeCreated string

The date and time the Autonomous Container Database was created.

TimeSnapshotStandbyRevert string

The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.

TotalCpus 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. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.

VaultId string

The OCID of the Oracle Cloud Infrastructure vault.

VersionPreference string

The next maintenance version preference.

autonomousContainerDatabaseId String
autonomousExadataInfrastructureId String

No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.

autonomousVmClusterId String

The OCID of the Autonomous VM Cluster.

availabilityDomain String

The availability domain of the Autonomous Container Database.

availableCpus 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.

backupConfigs List<GetAutonomousContainerBackupConfig>

Backup options for the Autonomous Container Database.

cloudAutonomousVmClusterId String

The OCID of the cloud Autonomous Exadata VM Cluster.

compartmentId String

The OCID of the compartment.

computeModel String

The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.

dbName 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.

dbUniqueName String
dbVersion String

Oracle Database version of the Autonomous Container Database.

definedTags Map<String,Object>

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

displayName String

The user-provided name for the Autonomous Container Database.

fastStartFailOverLagLimitInSeconds Integer
freeformTags Map<String,Object>

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

id String

The id of the Autonomous Database Vault service key management history entry.

infrastructureType String

The infrastructure type this resource belongs to.

isAutomaticFailoverEnabled Boolean
keyHistoryEntries List<GetAutonomousContainerKeyHistoryEntry>

Key History Entry.

keyStoreId String

The OCID of the key store.

keyStoreWalletName String

The wallet name for Oracle Key Vault.

kmsKeyId String

The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.

lastMaintenanceRunId String

The OCID of the last maintenance run.

lifecycleDetails String

Additional information about the current lifecycle state.

maintenanceWindowDetails List<GetAutonomousContainerMaintenanceWindowDetail>
maintenanceWindows List<GetAutonomousContainerMaintenanceWindow>

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

memoryPerOracleComputeUnitInGbs Integer

The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.

nextMaintenanceRunId String

The OCID of the next maintenance run.

patchId String

The OCID of the last patch applied on the system.

patchModel String

Database patch model preference.

peerAutonomousContainerDatabaseBackupConfigs List<GetAutonomousContainerPeerAutonomousContainerBackupConfig>
peerAutonomousContainerDatabaseCompartmentId String
peerAutonomousContainerDatabaseDisplayName String
peerAutonomousExadataInfrastructureId String
peerAutonomousVmClusterId String
peerCloudAutonomousVmClusterId String
peerDbUniqueName String
protectionMode String
provisionableCpuses List<Double>

An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database 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.

reclaimableCpus Double

For Autonomous Databases on Dedicated Exadata Infrastructure:

  • These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
  • The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
role String

The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.

rotateKeyTrigger Boolean
serviceLevelAgreementType String

The service level agreement type of the container database. The default is STANDARD.

standbyMaintenanceBufferInDays Integer

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

The current state of the Autonomous Container Database.

timeCreated String

The date and time the Autonomous Container Database was created.

timeSnapshotStandbyRevert String

The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.

totalCpus 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. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.

vaultId String

The OCID of the Oracle Cloud Infrastructure vault.

versionPreference String

The next maintenance version preference.

autonomousContainerDatabaseId string
autonomousExadataInfrastructureId string

No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.

autonomousVmClusterId string

The OCID of the Autonomous VM Cluster.

availabilityDomain string

The availability domain of the Autonomous Container Database.

availableCpus 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.

backupConfigs GetAutonomousContainerDatabaseBackupConfig[]

Backup options for the Autonomous Container Database.

cloudAutonomousVmClusterId string

The OCID of the cloud Autonomous Exadata VM Cluster.

compartmentId string

The OCID of the compartment.

computeModel string

The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.

dbName 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.

dbUniqueName string
dbVersion string

Oracle Database version of the Autonomous Container Database.

definedTags {[key: string]: any}

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

displayName string

The user-provided name for the Autonomous Container Database.

fastStartFailOverLagLimitInSeconds number
freeformTags {[key: string]: any}

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

id string

The id of the Autonomous Database Vault service key management history entry.

infrastructureType string

The infrastructure type this resource belongs to.

isAutomaticFailoverEnabled boolean
keyHistoryEntries GetAutonomousContainerDatabaseKeyHistoryEntry[]

Key History Entry.

keyStoreId string

The OCID of the key store.

keyStoreWalletName string

The wallet name for Oracle Key Vault.

kmsKeyId string

The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.

lastMaintenanceRunId string

The OCID of the last maintenance run.

lifecycleDetails string

Additional information about the current lifecycle state.

maintenanceWindowDetails GetAutonomousContainerDatabaseMaintenanceWindowDetail[]
maintenanceWindows GetAutonomousContainerDatabaseMaintenanceWindow[]

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

memoryPerOracleComputeUnitInGbs number

The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.

nextMaintenanceRunId string

The OCID of the next maintenance run.

patchId string

The OCID of the last patch applied on the system.

patchModel string

Database patch model preference.

peerAutonomousContainerDatabaseBackupConfigs GetAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfig[]
peerAutonomousContainerDatabaseCompartmentId string
peerAutonomousContainerDatabaseDisplayName string
peerAutonomousExadataInfrastructureId string
peerAutonomousVmClusterId string
peerCloudAutonomousVmClusterId string
peerDbUniqueName string
protectionMode string
provisionableCpuses number[]

An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database 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.

reclaimableCpus number

For Autonomous Databases on Dedicated Exadata Infrastructure:

  • These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
  • The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
role string

The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.

rotateKeyTrigger boolean
serviceLevelAgreementType string

The service level agreement type of the container database. The default is STANDARD.

standbyMaintenanceBufferInDays number

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

The current state of the Autonomous Container Database.

timeCreated string

The date and time the Autonomous Container Database was created.

timeSnapshotStandbyRevert string

The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.

totalCpus 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. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.

vaultId string

The OCID of the Oracle Cloud Infrastructure vault.

versionPreference string

The next maintenance version preference.

autonomous_container_database_id str
autonomous_exadata_infrastructure_id str

No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.

autonomous_vm_cluster_id str

The OCID of the Autonomous VM Cluster.

availability_domain str

The availability domain of the Autonomous Container Database.

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 GetAutonomousContainerDatabaseBackupConfig]

Backup options for the Autonomous Container Database.

cloud_autonomous_vm_cluster_id str

The OCID of the cloud Autonomous Exadata VM Cluster.

compartment_id str

The OCID of the compartment.

compute_model str

The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.

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_unique_name str
db_version str

Oracle Database version of the Autonomous Container Database.

defined_tags Mapping[str, Any]

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

display_name str

The user-provided name for the Autonomous Container Database.

fast_start_fail_over_lag_limit_in_seconds int
freeform_tags Mapping[str, Any]

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

id str

The id of the Autonomous Database Vault service key management history entry.

infrastructure_type str

The infrastructure type this resource belongs to.

is_automatic_failover_enabled bool
key_history_entries GetAutonomousContainerDatabaseKeyHistoryEntry]

Key History Entry.

key_store_id str

The OCID of the key store.

key_store_wallet_name str

The wallet name for Oracle Key Vault.

kms_key_id str

The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.

last_maintenance_run_id str

The OCID of the last maintenance run.

lifecycle_details str

Additional information about the current lifecycle state.

maintenance_window_details GetAutonomousContainerDatabaseMaintenanceWindowDetail]
maintenance_windows GetAutonomousContainerDatabaseMaintenanceWindow]

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

memory_per_oracle_compute_unit_in_gbs int

The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.

next_maintenance_run_id str

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_container_database_backup_configs GetAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfig]
peer_autonomous_container_database_compartment_id str
peer_autonomous_container_database_display_name str
peer_autonomous_exadata_infrastructure_id str
peer_autonomous_vm_cluster_id str
peer_cloud_autonomous_vm_cluster_id str
peer_db_unique_name str
protection_mode str
provisionable_cpuses Sequence[float]

An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database 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.

reclaimable_cpus float

For Autonomous Databases on Dedicated Exadata Infrastructure:

  • These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
  • The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
role str

The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.

rotate_key_trigger bool
service_level_agreement_type str

The service level agreement type of the container database. The default is STANDARD.

standby_maintenance_buffer_in_days int

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

The current state of the Autonomous Container Database.

time_created str

The date and time the Autonomous Container Database was created.

time_snapshot_standby_revert str

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. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.

vault_id str

The OCID of the Oracle Cloud Infrastructure vault.

version_preference str

The next maintenance version preference.

autonomousContainerDatabaseId String
autonomousExadataInfrastructureId String

No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.

autonomousVmClusterId String

The OCID of the Autonomous VM Cluster.

availabilityDomain String

The availability domain of the Autonomous Container Database.

availableCpus 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.

backupConfigs List<Property Map>

Backup options for the Autonomous Container Database.

cloudAutonomousVmClusterId String

The OCID of the cloud Autonomous Exadata VM Cluster.

compartmentId String

The OCID of the compartment.

computeModel String

The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.

dbName 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.

dbUniqueName String
dbVersion String

Oracle Database version of the Autonomous Container Database.

definedTags Map<Any>

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

displayName String

The user-provided name for the Autonomous Container Database.

fastStartFailOverLagLimitInSeconds Number
freeformTags Map<Any>

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

id String

The id of the Autonomous Database Vault service key management history entry.

infrastructureType String

The infrastructure type this resource belongs to.

isAutomaticFailoverEnabled Boolean
keyHistoryEntries List<Property Map>

Key History Entry.

keyStoreId String

The OCID of the key store.

keyStoreWalletName String

The wallet name for Oracle Key Vault.

kmsKeyId String

The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.

lastMaintenanceRunId String

The OCID of the last maintenance run.

lifecycleDetails String

Additional information about the current lifecycle state.

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

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

memoryPerOracleComputeUnitInGbs Number

The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.

nextMaintenanceRunId String

The OCID of the next maintenance run.

patchId String

The OCID of the last patch applied on the system.

patchModel String

Database patch model preference.

peerAutonomousContainerDatabaseBackupConfigs List<Property Map>
peerAutonomousContainerDatabaseCompartmentId String
peerAutonomousContainerDatabaseDisplayName String
peerAutonomousExadataInfrastructureId String
peerAutonomousVmClusterId String
peerCloudAutonomousVmClusterId String
peerDbUniqueName String
protectionMode String
provisionableCpuses List<Number>

An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database 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.

reclaimableCpus Number

For Autonomous Databases on Dedicated Exadata Infrastructure:

  • These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
  • The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
role String

The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.

rotateKeyTrigger Boolean
serviceLevelAgreementType String

The service level agreement type of the container database. The default is STANDARD.

standbyMaintenanceBufferInDays Number

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

The current state of the Autonomous Container Database.

timeCreated String

The date and time the Autonomous Container Database was created.

timeSnapshotStandbyRevert String

The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.

totalCpus 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. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.

vaultId String

The OCID of the Oracle Cloud Infrastructure vault.

versionPreference String

The next maintenance version preference.

Supporting Types

GetAutonomousContainerDatabaseBackupConfig

BackupDestinationDetails List<GetAutonomousContainerDatabaseBackupConfigBackupDestinationDetail>

Backup destination details.

RecoveryWindowInDays int

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.

BackupDestinationDetails []GetAutonomousContainerDatabaseBackupConfigBackupDestinationDetail

Backup destination details.

RecoveryWindowInDays int

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.

backupDestinationDetails List<GetAutonomousContainerBackupConfigBackupDestinationDetail>

Backup destination details.

recoveryWindowInDays Integer

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.

backupDestinationDetails GetAutonomousContainerDatabaseBackupConfigBackupDestinationDetail[]

Backup destination details.

recoveryWindowInDays number

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.

backup_destination_details GetAutonomousContainerDatabaseBackupConfigBackupDestinationDetail]

Backup destination details.

recovery_window_in_days int

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.

backupDestinationDetails List<Property Map>

Backup destination details.

recoveryWindowInDays Number

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.

GetAutonomousContainerDatabaseBackupConfigBackupDestinationDetail

Id string

The id of the Autonomous Database Vault service key management history entry.

InternetProxy string

Proxy URL to connect to object store.

Type string

Type of the database backup destination.

VpcPassword string

For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.

VpcUser 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.

InternetProxy string

Proxy URL to connect to object store.

Type string

Type of the database backup destination.

VpcPassword string

For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.

VpcUser 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.

internetProxy String

Proxy URL to connect to object store.

type String

Type of the database backup destination.

vpcPassword String

For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.

vpcUser 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.

internetProxy string

Proxy URL to connect to object store.

type string

Type of the database backup destination.

vpcPassword string

For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.

vpcUser 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.

internetProxy String

Proxy URL to connect to object store.

type String

Type of the database backup destination.

vpcPassword String

For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.

vpcUser String

For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.

GetAutonomousContainerDatabaseKeyHistoryEntry

Id string

The id of the Autonomous Database Vault service key management history entry.

KmsKeyVersionId string

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.

TimeActivated string

The date and time the kms key activated.

VaultId string

The OCID of the Oracle Cloud Infrastructure vault.

Id string

The id of the Autonomous Database Vault service key management history entry.

KmsKeyVersionId string

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.

TimeActivated string

The date and time the kms key activated.

VaultId string

The OCID of the Oracle Cloud Infrastructure vault.

id String

The id of the Autonomous Database Vault service key management history entry.

kmsKeyVersionId String

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.

timeActivated String

The date and time the kms key activated.

vaultId String

The OCID of the Oracle Cloud Infrastructure vault.

id string

The id of the Autonomous Database Vault service key management history entry.

kmsKeyVersionId string

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.

timeActivated string

The date and time the kms key activated.

vaultId 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_version_id str

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.

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.

kmsKeyVersionId String

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.

timeActivated String

The date and time the kms key activated.

vaultId String

The OCID of the Oracle Cloud Infrastructure vault.

GetAutonomousContainerDatabaseMaintenanceWindow

CustomActionTimeoutInMins int

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

DaysOfWeeks List<GetAutonomousContainerDatabaseMaintenanceWindowDaysOfWeek>

Days during the week when maintenance should be performed.

HoursOfDays List<int>

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

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

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

IsMonthlyPatchingEnabled bool

If true, enables the monthly patching option.

LeadTimeInWeeks int

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

Months List<GetAutonomousContainerDatabaseMaintenanceWindowMonth>

Months during the year when maintenance should be performed.

PatchingMode string

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

Preference string

The maintenance window scheduling preference.

WeeksOfMonths List<int>

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

CustomActionTimeoutInMins int

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

DaysOfWeeks []GetAutonomousContainerDatabaseMaintenanceWindowDaysOfWeek

Days during the week when maintenance should be performed.

HoursOfDays []int

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

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

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

IsMonthlyPatchingEnabled bool

If true, enables the monthly patching option.

LeadTimeInWeeks int

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

Months []GetAutonomousContainerDatabaseMaintenanceWindowMonth

Months during the year when maintenance should be performed.

PatchingMode string

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

Preference string

The maintenance window scheduling preference.

WeeksOfMonths []int

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

customActionTimeoutInMins Integer

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

daysOfWeeks List<GetAutonomousContainerMaintenanceWindowDaysOfWeek>

Days during the week when maintenance should be performed.

hoursOfDays List<Integer>

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

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

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

isMonthlyPatchingEnabled Boolean

If true, enables the monthly patching option.

leadTimeInWeeks Integer

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

months List<GetAutonomousContainerMaintenanceWindowMonth>

Months during the year when maintenance should be performed.

patchingMode String

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

preference String

The maintenance window scheduling preference.

weeksOfMonths List<Integer>

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

customActionTimeoutInMins number

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

daysOfWeeks GetAutonomousContainerDatabaseMaintenanceWindowDaysOfWeek[]

Days during the week when maintenance should be performed.

hoursOfDays number[]

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

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

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

isMonthlyPatchingEnabled boolean

If true, enables the monthly patching option.

leadTimeInWeeks number

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

months GetAutonomousContainerDatabaseMaintenanceWindowMonth[]

Months during the year when maintenance should be performed.

patchingMode string

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

preference string

The maintenance window scheduling preference.

weeksOfMonths number[]

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

custom_action_timeout_in_mins int

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

days_of_weeks GetAutonomousContainerDatabaseMaintenanceWindowDaysOfWeek]

Days during the week when maintenance should be performed.

hours_of_days Sequence[int]

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

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

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

is_monthly_patching_enabled bool

If true, enables the monthly patching option.

lead_time_in_weeks int

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

months GetAutonomousContainerDatabaseMaintenanceWindowMonth]

Months during the year when maintenance should be performed.

patching_mode str

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

preference str

The maintenance window scheduling preference.

weeks_of_months Sequence[int]

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

customActionTimeoutInMins Number

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

daysOfWeeks List<Property Map>

Days during the week when maintenance should be performed.

hoursOfDays List<Number>

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

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

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

isMonthlyPatchingEnabled Boolean

If true, enables the monthly patching option.

leadTimeInWeeks Number

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

months List<Property Map>

Months during the year when maintenance should be performed.

patchingMode String

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

preference String

The maintenance window scheduling preference.

weeksOfMonths List<Number>

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

GetAutonomousContainerDatabaseMaintenanceWindowDaysOfWeek

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.

GetAutonomousContainerDatabaseMaintenanceWindowDetail

CustomActionTimeoutInMins int

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

DaysOfWeeks List<GetAutonomousContainerDatabaseMaintenanceWindowDetailDaysOfWeek>

Days during the week when maintenance should be performed.

HoursOfDays List<int>

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

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

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

IsMonthlyPatchingEnabled bool

If true, enables the monthly patching option.

LeadTimeInWeeks int

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

Months List<GetAutonomousContainerDatabaseMaintenanceWindowDetailMonth>

Months during the year when maintenance should be performed.

PatchingMode string

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

Preference string

The maintenance window scheduling preference.

WeeksOfMonths List<int>

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

CustomActionTimeoutInMins int

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

DaysOfWeeks []GetAutonomousContainerDatabaseMaintenanceWindowDetailDaysOfWeek

Days during the week when maintenance should be performed.

HoursOfDays []int

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

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

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

IsMonthlyPatchingEnabled bool

If true, enables the monthly patching option.

LeadTimeInWeeks int

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

Months []GetAutonomousContainerDatabaseMaintenanceWindowDetailMonth

Months during the year when maintenance should be performed.

PatchingMode string

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

Preference string

The maintenance window scheduling preference.

WeeksOfMonths []int

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

customActionTimeoutInMins Integer

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

daysOfWeeks List<GetAutonomousContainerMaintenanceWindowDetailDaysOfWeek>

Days during the week when maintenance should be performed.

hoursOfDays List<Integer>

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

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

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

isMonthlyPatchingEnabled Boolean

If true, enables the monthly patching option.

leadTimeInWeeks Integer

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

months List<GetAutonomousContainerMaintenanceWindowDetailMonth>

Months during the year when maintenance should be performed.

patchingMode String

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

preference String

The maintenance window scheduling preference.

weeksOfMonths List<Integer>

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

customActionTimeoutInMins number

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

daysOfWeeks GetAutonomousContainerDatabaseMaintenanceWindowDetailDaysOfWeek[]

Days during the week when maintenance should be performed.

hoursOfDays number[]

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

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

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

isMonthlyPatchingEnabled boolean

If true, enables the monthly patching option.

leadTimeInWeeks number

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

months GetAutonomousContainerDatabaseMaintenanceWindowDetailMonth[]

Months during the year when maintenance should be performed.

patchingMode string

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

preference string

The maintenance window scheduling preference.

weeksOfMonths number[]

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

custom_action_timeout_in_mins int

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

days_of_weeks GetAutonomousContainerDatabaseMaintenanceWindowDetailDaysOfWeek]

Days during the week when maintenance should be performed.

hours_of_days Sequence[int]

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

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

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

is_monthly_patching_enabled bool

If true, enables the monthly patching option.

lead_time_in_weeks int

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

months GetAutonomousContainerDatabaseMaintenanceWindowDetailMonth]

Months during the year when maintenance should be performed.

patching_mode str

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

preference str

The maintenance window scheduling preference.

weeks_of_months Sequence[int]

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

customActionTimeoutInMins Number

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

daysOfWeeks List<Property Map>

Days during the week when maintenance should be performed.

hoursOfDays List<Number>

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

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

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

isMonthlyPatchingEnabled Boolean

If true, enables the monthly patching option.

leadTimeInWeeks Number

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

months List<Property Map>

Months during the year when maintenance should be performed.

patchingMode String

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

preference String

The maintenance window scheduling preference.

weeksOfMonths List<Number>

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

GetAutonomousContainerDatabaseMaintenanceWindowDetailDaysOfWeek

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.

GetAutonomousContainerDatabaseMaintenanceWindowDetailMonth

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.

GetAutonomousContainerDatabaseMaintenanceWindowMonth

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.

GetAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfig

BackupDestinationDetails List<GetAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetail>

Backup destination details.

RecoveryWindowInDays int

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.

BackupDestinationDetails []GetAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetail

Backup destination details.

RecoveryWindowInDays int

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.

backupDestinationDetails List<GetAutonomousContainerPeerAutonomousContainerBackupConfigBackupDestinationDetail>

Backup destination details.

recoveryWindowInDays Integer

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.

backupDestinationDetails GetAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetail[]

Backup destination details.

recoveryWindowInDays number

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.

backup_destination_details GetAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetail]

Backup destination details.

recovery_window_in_days int

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.

backupDestinationDetails List<Property Map>

Backup destination details.

recoveryWindowInDays Number

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.

GetAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetail

Id string

The id of the Autonomous Database Vault service key management history entry.

InternetProxy string

Proxy URL to connect to object store.

Type string

Type of the database backup destination.

VpcPassword string

For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.

VpcUser 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.

InternetProxy string

Proxy URL to connect to object store.

Type string

Type of the database backup destination.

VpcPassword string

For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.

VpcUser 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.

internetProxy String

Proxy URL to connect to object store.

type String

Type of the database backup destination.

vpcPassword String

For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.

vpcUser 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.

internetProxy string

Proxy URL to connect to object store.

type string

Type of the database backup destination.

vpcPassword string

For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.

vpcUser 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.

internetProxy String

Proxy URL to connect to object store.

type String

Type of the database backup destination.

vpcPassword String

For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.

vpcUser String

For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.

Package Details

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

This Pulumi package is based on the oci Terraform Provider.