oci.Database.AutonomousContainerDatabaseAddStandby
Explore with Pulumi AI
This resource provides the Autonomous Container Database Add Standby resource in Oracle Cloud Infrastructure Database service.
Create Standby Autonomous Container Database. For more information about changing Autonomous Container Databases Add Standby, see Create Standby Autonomous Container Database and Convert Snapshot Standby to Physical Standby.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testAutonomousContainerDatabaseAddStandby = new oci.database.AutonomousContainerDatabaseAddStandby("test_autonomous_container_database_add_standby", {
    autonomousContainerDatabaseId: testAutonomousContainerDatabase.id,
    fastStartFailOverLagLimitInSeconds: autonomousContainerDatabaseAddStandbyFastStartFailOverLagLimitInSeconds,
    isAutomaticFailoverEnabled: autonomousContainerDatabaseAddStandbyIsAutomaticFailoverEnabled,
    peerAutonomousContainerDatabaseBackupConfig: {
        backupDestinationDetails: [{
            type: autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsType,
            dbrsPolicyId: testPolicy.id,
            id: autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsId,
            internetProxy: autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsInternetProxy,
            vpcPassword: autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsVpcPassword,
            vpcUser: autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsVpcUser,
        }],
        recoveryWindowInDays: autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigRecoveryWindowInDays,
    },
    peerAutonomousContainerDatabaseCompartmentId: testCompartment.id,
    peerAutonomousContainerDatabaseDisplayName: autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseDisplayName,
    peerAutonomousVmClusterId: testAutonomousVmCluster.id,
    peerCloudAutonomousVmClusterId: testCloudAutonomousVmCluster.id,
    peerDbUniqueName: autonomousContainerDatabaseAddStandbyPeerDbUniqueName,
    protectionMode: autonomousContainerDatabaseAddStandbyProtectionMode,
    standbyMaintenanceBufferInDays: autonomousContainerDatabaseAddStandbyStandbyMaintenanceBufferInDays,
});
import pulumi
import pulumi_oci as oci
test_autonomous_container_database_add_standby = oci.database.AutonomousContainerDatabaseAddStandby("test_autonomous_container_database_add_standby",
    autonomous_container_database_id=test_autonomous_container_database["id"],
    fast_start_fail_over_lag_limit_in_seconds=autonomous_container_database_add_standby_fast_start_fail_over_lag_limit_in_seconds,
    is_automatic_failover_enabled=autonomous_container_database_add_standby_is_automatic_failover_enabled,
    peer_autonomous_container_database_backup_config={
        "backup_destination_details": [{
            "type": autonomous_container_database_add_standby_peer_autonomous_container_database_backup_config_backup_destination_details_type,
            "dbrs_policy_id": test_policy["id"],
            "id": autonomous_container_database_add_standby_peer_autonomous_container_database_backup_config_backup_destination_details_id,
            "internet_proxy": autonomous_container_database_add_standby_peer_autonomous_container_database_backup_config_backup_destination_details_internet_proxy,
            "vpc_password": autonomous_container_database_add_standby_peer_autonomous_container_database_backup_config_backup_destination_details_vpc_password,
            "vpc_user": autonomous_container_database_add_standby_peer_autonomous_container_database_backup_config_backup_destination_details_vpc_user,
        }],
        "recovery_window_in_days": autonomous_container_database_add_standby_peer_autonomous_container_database_backup_config_recovery_window_in_days,
    },
    peer_autonomous_container_database_compartment_id=test_compartment["id"],
    peer_autonomous_container_database_display_name=autonomous_container_database_add_standby_peer_autonomous_container_database_display_name,
    peer_autonomous_vm_cluster_id=test_autonomous_vm_cluster["id"],
    peer_cloud_autonomous_vm_cluster_id=test_cloud_autonomous_vm_cluster["id"],
    peer_db_unique_name=autonomous_container_database_add_standby_peer_db_unique_name,
    protection_mode=autonomous_container_database_add_standby_protection_mode,
    standby_maintenance_buffer_in_days=autonomous_container_database_add_standby_standby_maintenance_buffer_in_days)
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.NewAutonomousContainerDatabaseAddStandby(ctx, "test_autonomous_container_database_add_standby", &database.AutonomousContainerDatabaseAddStandbyArgs{
			AutonomousContainerDatabaseId:      pulumi.Any(testAutonomousContainerDatabase.Id),
			FastStartFailOverLagLimitInSeconds: pulumi.Any(autonomousContainerDatabaseAddStandbyFastStartFailOverLagLimitInSeconds),
			IsAutomaticFailoverEnabled:         pulumi.Any(autonomousContainerDatabaseAddStandbyIsAutomaticFailoverEnabled),
			PeerAutonomousContainerDatabaseBackupConfig: &database.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigArgs{
				BackupDestinationDetails: database.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailArray{
					&database.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailArgs{
						Type:          pulumi.Any(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsType),
						DbrsPolicyId:  pulumi.Any(testPolicy.Id),
						Id:            pulumi.Any(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsId),
						InternetProxy: pulumi.Any(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsInternetProxy),
						VpcPassword:   pulumi.Any(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsVpcPassword),
						VpcUser:       pulumi.Any(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsVpcUser),
					},
				},
				RecoveryWindowInDays: pulumi.Any(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigRecoveryWindowInDays),
			},
			PeerAutonomousContainerDatabaseCompartmentId: pulumi.Any(testCompartment.Id),
			PeerAutonomousContainerDatabaseDisplayName:   pulumi.Any(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseDisplayName),
			PeerAutonomousVmClusterId:                    pulumi.Any(testAutonomousVmCluster.Id),
			PeerCloudAutonomousVmClusterId:               pulumi.Any(testCloudAutonomousVmCluster.Id),
			PeerDbUniqueName:                             pulumi.Any(autonomousContainerDatabaseAddStandbyPeerDbUniqueName),
			ProtectionMode:                               pulumi.Any(autonomousContainerDatabaseAddStandbyProtectionMode),
			StandbyMaintenanceBufferInDays:               pulumi.Any(autonomousContainerDatabaseAddStandbyStandbyMaintenanceBufferInDays),
		})
		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 testAutonomousContainerDatabaseAddStandby = new Oci.Database.AutonomousContainerDatabaseAddStandby("test_autonomous_container_database_add_standby", new()
    {
        AutonomousContainerDatabaseId = testAutonomousContainerDatabase.Id,
        FastStartFailOverLagLimitInSeconds = autonomousContainerDatabaseAddStandbyFastStartFailOverLagLimitInSeconds,
        IsAutomaticFailoverEnabled = autonomousContainerDatabaseAddStandbyIsAutomaticFailoverEnabled,
        PeerAutonomousContainerDatabaseBackupConfig = new Oci.Database.Inputs.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigArgs
        {
            BackupDestinationDetails = new[]
            {
                new Oci.Database.Inputs.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailArgs
                {
                    Type = autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsType,
                    DbrsPolicyId = testPolicy.Id,
                    Id = autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsId,
                    InternetProxy = autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsInternetProxy,
                    VpcPassword = autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsVpcPassword,
                    VpcUser = autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsVpcUser,
                },
            },
            RecoveryWindowInDays = autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigRecoveryWindowInDays,
        },
        PeerAutonomousContainerDatabaseCompartmentId = testCompartment.Id,
        PeerAutonomousContainerDatabaseDisplayName = autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseDisplayName,
        PeerAutonomousVmClusterId = testAutonomousVmCluster.Id,
        PeerCloudAutonomousVmClusterId = testCloudAutonomousVmCluster.Id,
        PeerDbUniqueName = autonomousContainerDatabaseAddStandbyPeerDbUniqueName,
        ProtectionMode = autonomousContainerDatabaseAddStandbyProtectionMode,
        StandbyMaintenanceBufferInDays = autonomousContainerDatabaseAddStandbyStandbyMaintenanceBufferInDays,
    });
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Database.AutonomousContainerDatabaseAddStandby;
import com.pulumi.oci.Database.AutonomousContainerDatabaseAddStandbyArgs;
import com.pulumi.oci.Database.inputs.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigArgs;
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) {
        var testAutonomousContainerDatabaseAddStandby = new AutonomousContainerDatabaseAddStandby("testAutonomousContainerDatabaseAddStandby", AutonomousContainerDatabaseAddStandbyArgs.builder()
            .autonomousContainerDatabaseId(testAutonomousContainerDatabase.id())
            .fastStartFailOverLagLimitInSeconds(autonomousContainerDatabaseAddStandbyFastStartFailOverLagLimitInSeconds)
            .isAutomaticFailoverEnabled(autonomousContainerDatabaseAddStandbyIsAutomaticFailoverEnabled)
            .peerAutonomousContainerDatabaseBackupConfig(AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigArgs.builder()
                .backupDestinationDetails(AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailArgs.builder()
                    .type(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsType)
                    .dbrsPolicyId(testPolicy.id())
                    .id(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsId)
                    .internetProxy(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsInternetProxy)
                    .vpcPassword(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsVpcPassword)
                    .vpcUser(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsVpcUser)
                    .build())
                .recoveryWindowInDays(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigRecoveryWindowInDays)
                .build())
            .peerAutonomousContainerDatabaseCompartmentId(testCompartment.id())
            .peerAutonomousContainerDatabaseDisplayName(autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseDisplayName)
            .peerAutonomousVmClusterId(testAutonomousVmCluster.id())
            .peerCloudAutonomousVmClusterId(testCloudAutonomousVmCluster.id())
            .peerDbUniqueName(autonomousContainerDatabaseAddStandbyPeerDbUniqueName)
            .protectionMode(autonomousContainerDatabaseAddStandbyProtectionMode)
            .standbyMaintenanceBufferInDays(autonomousContainerDatabaseAddStandbyStandbyMaintenanceBufferInDays)
            .build());
    }
}
resources:
  testAutonomousContainerDatabaseAddStandby:
    type: oci:Database:AutonomousContainerDatabaseAddStandby
    name: test_autonomous_container_database_add_standby
    properties:
      autonomousContainerDatabaseId: ${testAutonomousContainerDatabase.id}
      fastStartFailOverLagLimitInSeconds: ${autonomousContainerDatabaseAddStandbyFastStartFailOverLagLimitInSeconds}
      isAutomaticFailoverEnabled: ${autonomousContainerDatabaseAddStandbyIsAutomaticFailoverEnabled}
      peerAutonomousContainerDatabaseBackupConfig:
        backupDestinationDetails:
          - type: ${autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsType}
            dbrsPolicyId: ${testPolicy.id}
            id: ${autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsId}
            internetProxy: ${autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsInternetProxy}
            vpcPassword: ${autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsVpcPassword}
            vpcUser: ${autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailsVpcUser}
        recoveryWindowInDays: ${autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigRecoveryWindowInDays}
      peerAutonomousContainerDatabaseCompartmentId: ${testCompartment.id}
      peerAutonomousContainerDatabaseDisplayName: ${autonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseDisplayName}
      peerAutonomousVmClusterId: ${testAutonomousVmCluster.id}
      peerCloudAutonomousVmClusterId: ${testCloudAutonomousVmCluster.id}
      peerDbUniqueName: ${autonomousContainerDatabaseAddStandbyPeerDbUniqueName}
      protectionMode: ${autonomousContainerDatabaseAddStandbyProtectionMode}
      standbyMaintenanceBufferInDays: ${autonomousContainerDatabaseAddStandbyStandbyMaintenanceBufferInDays}
Create AutonomousContainerDatabaseAddStandby Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new AutonomousContainerDatabaseAddStandby(name: string, args: AutonomousContainerDatabaseAddStandbyArgs, opts?: CustomResourceOptions);@overload
def AutonomousContainerDatabaseAddStandby(resource_name: str,
                                          args: AutonomousContainerDatabaseAddStandbyArgs,
                                          opts: Optional[ResourceOptions] = None)
@overload
def AutonomousContainerDatabaseAddStandby(resource_name: str,
                                          opts: Optional[ResourceOptions] = None,
                                          autonomous_container_database_id: Optional[str] = None,
                                          fast_start_fail_over_lag_limit_in_seconds: Optional[int] = None,
                                          is_automatic_failover_enabled: Optional[bool] = None,
                                          peer_autonomous_container_database_backup_config: Optional[_database.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigArgs] = None,
                                          peer_autonomous_container_database_compartment_id: Optional[str] = None,
                                          peer_autonomous_container_database_display_name: Optional[str] = None,
                                          peer_autonomous_vm_cluster_id: Optional[str] = None,
                                          peer_cloud_autonomous_vm_cluster_id: Optional[str] = None,
                                          peer_db_unique_name: Optional[str] = None,
                                          protection_mode: Optional[str] = None,
                                          standby_maintenance_buffer_in_days: Optional[int] = None)func NewAutonomousContainerDatabaseAddStandby(ctx *Context, name string, args AutonomousContainerDatabaseAddStandbyArgs, opts ...ResourceOption) (*AutonomousContainerDatabaseAddStandby, error)public AutonomousContainerDatabaseAddStandby(string name, AutonomousContainerDatabaseAddStandbyArgs args, CustomResourceOptions? opts = null)
public AutonomousContainerDatabaseAddStandby(String name, AutonomousContainerDatabaseAddStandbyArgs args)
public AutonomousContainerDatabaseAddStandby(String name, AutonomousContainerDatabaseAddStandbyArgs args, CustomResourceOptions options)
type: oci:Database:AutonomousContainerDatabaseAddStandby
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args AutonomousContainerDatabaseAddStandbyArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args AutonomousContainerDatabaseAddStandbyArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args AutonomousContainerDatabaseAddStandbyArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args AutonomousContainerDatabaseAddStandbyArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args AutonomousContainerDatabaseAddStandbyArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var autonomousContainerDatabaseAddStandbyResource = new Oci.Database.AutonomousContainerDatabaseAddStandby("autonomousContainerDatabaseAddStandbyResource", new()
{
    AutonomousContainerDatabaseId = "string",
    FastStartFailOverLagLimitInSeconds = 0,
    IsAutomaticFailoverEnabled = false,
    PeerAutonomousContainerDatabaseBackupConfig = new Oci.Database.Inputs.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigArgs
    {
        BackupDestinationDetails = new[]
        {
            new Oci.Database.Inputs.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailArgs
            {
                Type = "string",
                DbrsPolicyId = "string",
                Id = "string",
                InternetProxy = "string",
                VpcPassword = "string",
                VpcUser = "string",
            },
        },
        RecoveryWindowInDays = 0,
    },
    PeerAutonomousContainerDatabaseCompartmentId = "string",
    PeerAutonomousContainerDatabaseDisplayName = "string",
    PeerAutonomousVmClusterId = "string",
    PeerCloudAutonomousVmClusterId = "string",
    PeerDbUniqueName = "string",
    ProtectionMode = "string",
    StandbyMaintenanceBufferInDays = 0,
});
example, err := Database.NewAutonomousContainerDatabaseAddStandby(ctx, "autonomousContainerDatabaseAddStandbyResource", &Database.AutonomousContainerDatabaseAddStandbyArgs{
	AutonomousContainerDatabaseId:      pulumi.String("string"),
	FastStartFailOverLagLimitInSeconds: pulumi.Int(0),
	IsAutomaticFailoverEnabled:         pulumi.Bool(false),
	PeerAutonomousContainerDatabaseBackupConfig: &database.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigArgs{
		BackupDestinationDetails: database.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailArray{
			&database.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailArgs{
				Type:          pulumi.String("string"),
				DbrsPolicyId:  pulumi.String("string"),
				Id:            pulumi.String("string"),
				InternetProxy: pulumi.String("string"),
				VpcPassword:   pulumi.String("string"),
				VpcUser:       pulumi.String("string"),
			},
		},
		RecoveryWindowInDays: pulumi.Int(0),
	},
	PeerAutonomousContainerDatabaseCompartmentId: pulumi.String("string"),
	PeerAutonomousContainerDatabaseDisplayName:   pulumi.String("string"),
	PeerAutonomousVmClusterId:                    pulumi.String("string"),
	PeerCloudAutonomousVmClusterId:               pulumi.String("string"),
	PeerDbUniqueName:                             pulumi.String("string"),
	ProtectionMode:                               pulumi.String("string"),
	StandbyMaintenanceBufferInDays:               pulumi.Int(0),
})
var autonomousContainerDatabaseAddStandbyResource = new AutonomousContainerDatabaseAddStandby("autonomousContainerDatabaseAddStandbyResource", AutonomousContainerDatabaseAddStandbyArgs.builder()
    .autonomousContainerDatabaseId("string")
    .fastStartFailOverLagLimitInSeconds(0)
    .isAutomaticFailoverEnabled(false)
    .peerAutonomousContainerDatabaseBackupConfig(AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigArgs.builder()
        .backupDestinationDetails(AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailArgs.builder()
            .type("string")
            .dbrsPolicyId("string")
            .id("string")
            .internetProxy("string")
            .vpcPassword("string")
            .vpcUser("string")
            .build())
        .recoveryWindowInDays(0)
        .build())
    .peerAutonomousContainerDatabaseCompartmentId("string")
    .peerAutonomousContainerDatabaseDisplayName("string")
    .peerAutonomousVmClusterId("string")
    .peerCloudAutonomousVmClusterId("string")
    .peerDbUniqueName("string")
    .protectionMode("string")
    .standbyMaintenanceBufferInDays(0)
    .build());
autonomous_container_database_add_standby_resource = oci.database.AutonomousContainerDatabaseAddStandby("autonomousContainerDatabaseAddStandbyResource",
    autonomous_container_database_id="string",
    fast_start_fail_over_lag_limit_in_seconds=0,
    is_automatic_failover_enabled=False,
    peer_autonomous_container_database_backup_config={
        "backup_destination_details": [{
            "type": "string",
            "dbrs_policy_id": "string",
            "id": "string",
            "internet_proxy": "string",
            "vpc_password": "string",
            "vpc_user": "string",
        }],
        "recovery_window_in_days": 0,
    },
    peer_autonomous_container_database_compartment_id="string",
    peer_autonomous_container_database_display_name="string",
    peer_autonomous_vm_cluster_id="string",
    peer_cloud_autonomous_vm_cluster_id="string",
    peer_db_unique_name="string",
    protection_mode="string",
    standby_maintenance_buffer_in_days=0)
const autonomousContainerDatabaseAddStandbyResource = new oci.database.AutonomousContainerDatabaseAddStandby("autonomousContainerDatabaseAddStandbyResource", {
    autonomousContainerDatabaseId: "string",
    fastStartFailOverLagLimitInSeconds: 0,
    isAutomaticFailoverEnabled: false,
    peerAutonomousContainerDatabaseBackupConfig: {
        backupDestinationDetails: [{
            type: "string",
            dbrsPolicyId: "string",
            id: "string",
            internetProxy: "string",
            vpcPassword: "string",
            vpcUser: "string",
        }],
        recoveryWindowInDays: 0,
    },
    peerAutonomousContainerDatabaseCompartmentId: "string",
    peerAutonomousContainerDatabaseDisplayName: "string",
    peerAutonomousVmClusterId: "string",
    peerCloudAutonomousVmClusterId: "string",
    peerDbUniqueName: "string",
    protectionMode: "string",
    standbyMaintenanceBufferInDays: 0,
});
type: oci:Database:AutonomousContainerDatabaseAddStandby
properties:
    autonomousContainerDatabaseId: string
    fastStartFailOverLagLimitInSeconds: 0
    isAutomaticFailoverEnabled: false
    peerAutonomousContainerDatabaseBackupConfig:
        backupDestinationDetails:
            - dbrsPolicyId: string
              id: string
              internetProxy: string
              type: string
              vpcPassword: string
              vpcUser: string
        recoveryWindowInDays: 0
    peerAutonomousContainerDatabaseCompartmentId: string
    peerAutonomousContainerDatabaseDisplayName: string
    peerAutonomousVmClusterId: string
    peerCloudAutonomousVmClusterId: string
    peerDbUniqueName: string
    protectionMode: string
    standbyMaintenanceBufferInDays: 0
AutonomousContainerDatabaseAddStandby Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The AutonomousContainerDatabaseAddStandby resource accepts the following input properties:
- AutonomousContainer stringDatabase Id 
- The Autonomous Container Database OCID.
- FastStart intFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- IsAutomatic boolFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- PeerAutonomous AutonomousContainer Database Backup Config Container Database Add Standby Peer Autonomous Container Database Backup Config 
- Backup options for the standby Autonomous Container Database.
- PeerAutonomous stringContainer Database Compartment Id 
- The OCID of the compartment where the standby Autonomous Container Database will be created.
- PeerAutonomous stringContainer Database Display Name 
- The display name for the peer Autonomous Container Database.
- PeerAutonomous stringVm Cluster Id 
- The OCID of the peer Autonomous Exadata VM Cluster.
- PeerCloud stringAutonomous Vm Cluster Id 
- The OCID of the peer cloud Autonomous Exadata VM Cluster.
- PeerDb stringUnique Name 
- Specifies the DB_UNIQUE_NAMEof the peer database to be created.
- ProtectionMode string
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- StandbyMaintenance 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. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- AutonomousContainer stringDatabase Id 
- The Autonomous Container Database OCID.
- FastStart intFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- IsAutomatic boolFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- PeerAutonomous AutonomousContainer Database Backup Config Container Database Add Standby Peer Autonomous Container Database Backup Config Args 
- Backup options for the standby Autonomous Container Database.
- PeerAutonomous stringContainer Database Compartment Id 
- The OCID of the compartment where the standby Autonomous Container Database will be created.
- PeerAutonomous stringContainer Database Display Name 
- The display name for the peer Autonomous Container Database.
- PeerAutonomous stringVm Cluster Id 
- The OCID of the peer Autonomous Exadata VM Cluster.
- PeerCloud stringAutonomous Vm Cluster Id 
- The OCID of the peer cloud Autonomous Exadata VM Cluster.
- PeerDb stringUnique Name 
- Specifies the DB_UNIQUE_NAMEof the peer database to be created.
- ProtectionMode string
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- StandbyMaintenance 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. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- autonomousContainer StringDatabase Id 
- The Autonomous Container Database OCID.
- fastStart IntegerFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- isAutomatic BooleanFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- peerAutonomous AutonomousContainer Database Backup Config Container Add Standby Peer Autonomous Container Backup Config 
- Backup options for the standby Autonomous Container Database.
- peerAutonomous StringContainer Database Compartment Id 
- The OCID of the compartment where the standby Autonomous Container Database will be created.
- peerAutonomous StringContainer Database Display Name 
- The display name for the peer Autonomous Container Database.
- peerAutonomous StringVm Cluster Id 
- The OCID of the peer Autonomous Exadata VM Cluster.
- peerCloud StringAutonomous Vm Cluster Id 
- The OCID of the peer cloud Autonomous Exadata VM Cluster.
- peerDb StringUnique Name 
- Specifies the DB_UNIQUE_NAMEof the peer database to be created.
- protectionMode String
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- standbyMaintenance 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. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- autonomousContainer stringDatabase Id 
- The Autonomous Container Database OCID.
- fastStart numberFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- isAutomatic booleanFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- peerAutonomous AutonomousContainer Database Backup Config Container Database Add Standby Peer Autonomous Container Database Backup Config 
- Backup options for the standby Autonomous Container Database.
- peerAutonomous stringContainer Database Compartment Id 
- The OCID of the compartment where the standby Autonomous Container Database will be created.
- peerAutonomous stringContainer Database Display Name 
- The display name for the peer Autonomous Container Database.
- peerAutonomous stringVm Cluster Id 
- The OCID of the peer Autonomous Exadata VM Cluster.
- peerCloud stringAutonomous Vm Cluster Id 
- The OCID of the peer cloud Autonomous Exadata VM Cluster.
- peerDb stringUnique Name 
- Specifies the DB_UNIQUE_NAMEof the peer database to be created.
- protectionMode string
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- standbyMaintenance 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. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- autonomous_container_ strdatabase_ id 
- The Autonomous Container Database OCID.
- fast_start_ intfail_ over_ lag_ limit_ in_ seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- is_automatic_ boolfailover_ enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- peer_autonomous_ database.container_ database_ backup_ config Autonomous Container Database Add Standby Peer Autonomous Container Database Backup Config Args 
- Backup options for the standby Autonomous Container Database.
- peer_autonomous_ strcontainer_ database_ compartment_ id 
- The OCID of the compartment where the standby Autonomous Container Database will be created.
- peer_autonomous_ strcontainer_ database_ display_ name 
- The display name for the peer Autonomous Container Database.
- peer_autonomous_ strvm_ cluster_ id 
- The OCID of the peer Autonomous Exadata VM Cluster.
- peer_cloud_ strautonomous_ vm_ cluster_ id 
- The OCID of the peer cloud Autonomous Exadata VM Cluster.
- peer_db_ strunique_ name 
- Specifies the DB_UNIQUE_NAMEof the peer database to be created.
- protection_mode str
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- 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. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- autonomousContainer StringDatabase Id 
- The Autonomous Container Database OCID.
- fastStart NumberFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- isAutomatic BooleanFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- peerAutonomous Property MapContainer Database Backup Config 
- Backup options for the standby Autonomous Container Database.
- peerAutonomous StringContainer Database Compartment Id 
- The OCID of the compartment where the standby Autonomous Container Database will be created.
- peerAutonomous StringContainer Database Display Name 
- The display name for the peer Autonomous Container Database.
- peerAutonomous StringVm Cluster Id 
- The OCID of the peer Autonomous Exadata VM Cluster.
- peerCloud StringAutonomous Vm Cluster Id 
- The OCID of the peer cloud Autonomous Exadata VM Cluster.
- peerDb StringUnique Name 
- Specifies the DB_UNIQUE_NAMEof the peer database to be created.
- protectionMode String
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- standbyMaintenance 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. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
Outputs
All input properties are implicitly available as output properties. Additionally, the AutonomousContainerDatabaseAddStandby resource produces the following output properties:
- AutonomousExadata stringInfrastructure Id 
- No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.
- AutonomousVm stringCluster Id 
- The OCID of the Autonomous VM Cluster.
- AvailabilityDomain string
- The 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.
- BackupConfigs List<AutonomousContainer Database Add Standby Backup Config> 
- Backup options for the Autonomous Container Database.
- CloudAutonomous stringVm Cluster Id 
- The OCID of the cloud Autonomous Exadata VM Cluster.
- CompartmentId string
- The OCID of the compartment.
- ComputeModel 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.
- DataguardGroup List<AutonomousMembers Container Database Add Standby Dataguard Group Member> 
- Array of Dg associations.
- Dataguards
List<AutonomousContainer Database Add Standby Dataguard> 
- The properties that define Autonomous Container Databases Dataguard.
- 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.
- DbSplit 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.
- DbUnique stringName 
- DbVersion 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.
- DisplayName string
- The user-provided name for the Autonomous Container Database.
- DistributionAffinity 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.
- DstFile stringVersion 
- DST Time-Zone File version of the Autonomous Container Database.
- 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 provider-assigned unique ID for this managed resource.
- InfrastructureType string
- The infrastructure type this resource belongs to.
- IsData boolGuard Enabled 
- Deprecated. Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
- IsDst 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.
- IsMultiple boolStandby 
- Whether it is multiple standby Autonomous Dataguard
- KeyHistory List<AutonomousEntries Container Database Add Standby Key History Entry> 
- Key History Entry.
- KeyStore stringId 
- The OCID of the key store of Oracle Vault.
- KeyStore stringWallet Name 
- The wallet name for Oracle Key Vault.
- KmsKey stringId 
- The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- KmsKey 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.
- LargestProvisionable doubleAutonomous Database In Cpus 
- The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- LastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- ListOne List<string>Off Patches 
- List of One-Off patches that has been successfully applied to Autonomous Container Database
- MaintenanceWindows List<AutonomousContainer Database Add Standby Maintenance Window> 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- MemoryPer intOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- NetServices 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.
- NextMaintenance stringRun Id 
- 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.
- ProvisionableCpuses List<double>
- An array of CPU values that can be used to successfully provision a single Autonomous Database.
- ProvisionedCpus double
- The number of CPUs provisioned in an Autonomous Container Database.
- ReclaimableCpus 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.
- ReservedCpus 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.
- ServiceLevel 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.
- TimeCreated string
- The date and time the Autonomous Container Database was created.
- TimeOf 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.
- TimeSnapshot stringStandby Revert 
- 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.
- VaultId string
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- VersionPreference string
- The next maintenance version preference.
- VmFailover 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.
- AutonomousExadata stringInfrastructure Id 
- No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.
- AutonomousVm stringCluster Id 
- The OCID of the Autonomous VM Cluster.
- AvailabilityDomain string
- The 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.
- BackupConfigs []AutonomousContainer Database Add Standby Backup Config 
- Backup options for the Autonomous Container Database.
- CloudAutonomous stringVm Cluster Id 
- The OCID of the cloud Autonomous Exadata VM Cluster.
- CompartmentId string
- The OCID of the compartment.
- ComputeModel 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.
- DataguardGroup []AutonomousMembers Container Database Add Standby Dataguard Group Member 
- Array of Dg associations.
- Dataguards
[]AutonomousContainer Database Add Standby Dataguard 
- The properties that define Autonomous Container Databases Dataguard.
- 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.
- DbSplit 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.
- DbUnique stringName 
- DbVersion 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.
- DisplayName string
- The user-provided name for the Autonomous Container Database.
- DistributionAffinity 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.
- DstFile stringVersion 
- DST Time-Zone File version of the Autonomous Container Database.
- 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 provider-assigned unique ID for this managed resource.
- InfrastructureType string
- The infrastructure type this resource belongs to.
- IsData boolGuard Enabled 
- Deprecated. Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
- IsDst 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.
- IsMultiple boolStandby 
- Whether it is multiple standby Autonomous Dataguard
- KeyHistory []AutonomousEntries Container Database Add Standby Key History Entry 
- Key History Entry.
- KeyStore stringId 
- The OCID of the key store of Oracle Vault.
- KeyStore stringWallet Name 
- The wallet name for Oracle Key Vault.
- KmsKey stringId 
- The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- KmsKey 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.
- LargestProvisionable float64Autonomous Database In Cpus 
- The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- LastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- ListOne []stringOff Patches 
- List of One-Off patches that has been successfully applied to Autonomous Container Database
- MaintenanceWindows []AutonomousContainer Database Add Standby Maintenance Window 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- MemoryPer intOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- NetServices 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.
- NextMaintenance stringRun Id 
- 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.
- ProvisionableCpuses []float64
- An array of CPU values that can be used to successfully provision a single Autonomous Database.
- ProvisionedCpus float64
- The number of CPUs provisioned in an Autonomous Container Database.
- ReclaimableCpus 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.
- ReservedCpus 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.
- ServiceLevel 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.
- TimeCreated string
- The date and time the Autonomous Container Database was created.
- TimeOf 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.
- TimeSnapshot stringStandby Revert 
- 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.
- VaultId string
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- VersionPreference string
- The next maintenance version preference.
- VmFailover 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.
- autonomousExadata StringInfrastructure Id 
- No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.
- autonomousVm StringCluster Id 
- The OCID of the Autonomous VM Cluster.
- availabilityDomain String
- The 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.
- backupConfigs List<AutonomousContainer Add Standby Backup Config> 
- Backup options for the Autonomous Container Database.
- cloudAutonomous StringVm Cluster Id 
- The OCID of the cloud Autonomous Exadata VM Cluster.
- compartmentId String
- The OCID of the compartment.
- computeModel 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.
- dataguardGroup List<AutonomousMembers Container Add Standby Dataguard Group Member> 
- Array of Dg associations.
- dataguards
List<AutonomousContainer Add Standby Dataguard> 
- The properties that define Autonomous Container Databases Dataguard.
- 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.
- dbSplit 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.
- dbUnique StringName 
- dbVersion 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.
- displayName String
- The user-provided name for the Autonomous Container Database.
- distributionAffinity 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.
- dstFile StringVersion 
- DST Time-Zone File version of the Autonomous Container Database.
- 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 provider-assigned unique ID for this managed resource.
- infrastructureType String
- The infrastructure type this resource belongs to.
- isData BooleanGuard Enabled 
- Deprecated. Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
- isDst 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.
- isMultiple BooleanStandby 
- Whether it is multiple standby Autonomous Dataguard
- keyHistory List<AutonomousEntries Container Add Standby Key History Entry> 
- Key History Entry.
- keyStore StringId 
- The OCID of the key store of Oracle Vault.
- keyStore StringWallet Name 
- The wallet name for Oracle Key Vault.
- kmsKey StringId 
- The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- kmsKey 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.
- largestProvisionable DoubleAutonomous Database In Cpus 
- The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- lastMaintenance StringRun Id 
- The OCID of the last maintenance run.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- listOne List<String>Off Patches 
- List of One-Off patches that has been successfully applied to Autonomous Container Database
- maintenanceWindows List<AutonomousContainer Add Standby Maintenance Window> 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memoryPer IntegerOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- netServices 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.
- nextMaintenance StringRun Id 
- 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.
- provisionableCpuses List<Double>
- An array of CPU values that can be used to successfully provision a single Autonomous Database.
- provisionedCpus Double
- The number of CPUs provisioned in an Autonomous Container Database.
- reclaimableCpus 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.
- reservedCpus 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.
- serviceLevel 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.
- timeCreated String
- The date and time the Autonomous Container Database was created.
- timeOf 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.
- timeSnapshot StringStandby Revert 
- 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.
- vaultId String
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- versionPreference String
- The next maintenance version preference.
- vmFailover 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.
- autonomousExadata stringInfrastructure Id 
- No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.
- autonomousVm stringCluster Id 
- The OCID of the Autonomous VM Cluster.
- availabilityDomain string
- The 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.
- backupConfigs AutonomousContainer Database Add Standby Backup Config[] 
- Backup options for the Autonomous Container Database.
- cloudAutonomous stringVm Cluster Id 
- The OCID of the cloud Autonomous Exadata VM Cluster.
- compartmentId string
- The OCID of the compartment.
- computeModel 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.
- dataguardGroup AutonomousMembers Container Database Add Standby Dataguard Group Member[] 
- Array of Dg associations.
- dataguards
AutonomousContainer Database Add Standby Dataguard[] 
- The properties that define Autonomous Container Databases Dataguard.
- 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.
- dbSplit 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.
- dbUnique stringName 
- dbVersion 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.
- displayName string
- The user-provided name for the Autonomous Container Database.
- distributionAffinity 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.
- dstFile stringVersion 
- DST Time-Zone File version of the Autonomous Container Database.
- {[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 provider-assigned unique ID for this managed resource.
- infrastructureType string
- The infrastructure type this resource belongs to.
- isData booleanGuard Enabled 
- Deprecated. Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
- isDst 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.
- isMultiple booleanStandby 
- Whether it is multiple standby Autonomous Dataguard
- keyHistory AutonomousEntries Container Database Add Standby Key History Entry[] 
- Key History Entry.
- keyStore stringId 
- The OCID of the key store of Oracle Vault.
- keyStore stringWallet Name 
- The wallet name for Oracle Key Vault.
- kmsKey stringId 
- The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- kmsKey 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.
- largestProvisionable numberAutonomous Database In Cpus 
- The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- lastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- lifecycleDetails string
- Additional information about the current lifecycle state.
- listOne string[]Off Patches 
- List of One-Off patches that has been successfully applied to Autonomous Container Database
- maintenanceWindows AutonomousContainer Database Add Standby Maintenance Window[] 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memoryPer numberOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- netServices 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.
- nextMaintenance stringRun Id 
- 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.
- provisionableCpuses number[]
- An array of CPU values that can be used to successfully provision a single Autonomous Database.
- provisionedCpus number
- The number of CPUs provisioned in an Autonomous Container Database.
- reclaimableCpus 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.
- reservedCpus 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.
- serviceLevel 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.
- timeCreated string
- The date and time the Autonomous Container Database was created.
- timeOf 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.
- timeSnapshot stringStandby Revert 
- 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.
- vaultId string
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- versionPreference string
- The next maintenance version preference.
- vmFailover 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 
- 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 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.
- backup_configs Sequence[database.Autonomous Container Database Add Standby Backup Config] 
- Backup options for the Autonomous Container Database.
- cloud_autonomous_ strvm_ cluster_ id 
- 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 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.
- dataguard_group_ Sequence[database.members Autonomous Container Database Add Standby Dataguard Group Member] 
- Array of Dg associations.
- dataguards
Sequence[database.Autonomous Container Database Add Standby Dataguard] 
- The properties that define Autonomous Container Databases Dataguard.
- 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
- The user-provided name for the Autonomous Container Database.
- 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.
- 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 provider-assigned unique ID for this managed resource.
- infrastructure_type str
- The infrastructure type this resource belongs to.
- is_data_ boolguard_ enabled 
- Deprecated. Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
- 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.
- is_multiple_ boolstandby 
- Whether it is multiple standby Autonomous Dataguard
- key_history_ Sequence[database.entries Autonomous Container Database Add Standby 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.
- kms_key_ strid 
- The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- 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.
- 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_windows Sequence[database.Autonomous Container Database Add Standby 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.
- 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.
- 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.
- 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.
- vault_id str
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- 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.
- autonomousExadata StringInfrastructure Id 
- No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.
- autonomousVm StringCluster Id 
- The OCID of the Autonomous VM Cluster.
- availabilityDomain String
- The 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.
- backupConfigs List<Property Map>
- Backup options for the Autonomous Container Database.
- cloudAutonomous StringVm Cluster Id 
- The OCID of the cloud Autonomous Exadata VM Cluster.
- compartmentId String
- The OCID of the compartment.
- computeModel 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.
- dataguardGroup List<Property Map>Members 
- Array of Dg associations.
- dataguards List<Property Map>
- The properties that define Autonomous Container Databases Dataguard.
- 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.
- dbSplit 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.
- dbUnique StringName 
- dbVersion 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.
- displayName String
- The user-provided name for the Autonomous Container Database.
- distributionAffinity 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.
- dstFile StringVersion 
- DST Time-Zone File version of the Autonomous Container Database.
- 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 provider-assigned unique ID for this managed resource.
- infrastructureType String
- The infrastructure type this resource belongs to.
- isData BooleanGuard Enabled 
- Deprecated. Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
- isDst 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.
- isMultiple BooleanStandby 
- Whether it is multiple standby Autonomous Dataguard
- keyHistory List<Property Map>Entries 
- Key History Entry.
- keyStore StringId 
- The OCID of the key store of Oracle Vault.
- keyStore StringWallet Name 
- The wallet name for Oracle Key Vault.
- kmsKey StringId 
- The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- kmsKey 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.
- largestProvisionable NumberAutonomous Database In Cpus 
- The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- lastMaintenance StringRun Id 
- The OCID of the last maintenance run.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- listOne List<String>Off Patches 
- List of One-Off patches that has been successfully applied to Autonomous Container Database
- maintenanceWindows List<Property Map>
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memoryPer NumberOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- netServices 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.
- nextMaintenance StringRun Id 
- 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.
- provisionableCpuses List<Number>
- An array of CPU values that can be used to successfully provision a single Autonomous Database.
- provisionedCpus Number
- The number of CPUs provisioned in an Autonomous Container Database.
- reclaimableCpus 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.
- reservedCpus 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.
- serviceLevel 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.
- timeCreated String
- The date and time the Autonomous Container Database was created.
- timeOf 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.
- timeSnapshot StringStandby Revert 
- 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.
- vaultId String
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- versionPreference String
- The next maintenance version preference.
- vmFailover 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.
Look up Existing AutonomousContainerDatabaseAddStandby Resource
Get an existing AutonomousContainerDatabaseAddStandby resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: AutonomousContainerDatabaseAddStandbyState, opts?: CustomResourceOptions): AutonomousContainerDatabaseAddStandby@staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        autonomous_container_database_id: Optional[str] = None,
        autonomous_exadata_infrastructure_id: Optional[str] = None,
        autonomous_vm_cluster_id: Optional[str] = None,
        availability_domain: Optional[str] = None,
        available_cpus: Optional[float] = None,
        backup_configs: Optional[Sequence[_database.AutonomousContainerDatabaseAddStandbyBackupConfigArgs]] = None,
        cloud_autonomous_vm_cluster_id: Optional[str] = None,
        compartment_id: Optional[str] = None,
        compute_model: Optional[str] = None,
        dataguard_group_members: Optional[Sequence[_database.AutonomousContainerDatabaseAddStandbyDataguardGroupMemberArgs]] = None,
        dataguards: Optional[Sequence[_database.AutonomousContainerDatabaseAddStandbyDataguardArgs]] = None,
        db_name: Optional[str] = None,
        db_split_threshold: Optional[int] = None,
        db_unique_name: Optional[str] = None,
        db_version: Optional[str] = None,
        defined_tags: Optional[Mapping[str, str]] = None,
        display_name: Optional[str] = None,
        distribution_affinity: Optional[str] = None,
        dst_file_version: Optional[str] = None,
        fast_start_fail_over_lag_limit_in_seconds: Optional[int] = None,
        freeform_tags: Optional[Mapping[str, str]] = None,
        infrastructure_type: Optional[str] = None,
        is_automatic_failover_enabled: Optional[bool] = None,
        is_data_guard_enabled: Optional[bool] = None,
        is_dst_file_update_enabled: Optional[bool] = None,
        is_multiple_standby: Optional[bool] = None,
        key_history_entries: Optional[Sequence[_database.AutonomousContainerDatabaseAddStandbyKeyHistoryEntryArgs]] = None,
        key_store_id: Optional[str] = None,
        key_store_wallet_name: Optional[str] = None,
        kms_key_id: Optional[str] = None,
        kms_key_version_id: Optional[str] = None,
        largest_provisionable_autonomous_database_in_cpus: Optional[float] = None,
        last_maintenance_run_id: Optional[str] = None,
        lifecycle_details: Optional[str] = None,
        list_one_off_patches: Optional[Sequence[str]] = None,
        maintenance_windows: Optional[Sequence[_database.AutonomousContainerDatabaseAddStandbyMaintenanceWindowArgs]] = None,
        memory_per_oracle_compute_unit_in_gbs: Optional[int] = None,
        net_services_architecture: Optional[str] = None,
        next_maintenance_run_id: Optional[str] = None,
        patch_id: Optional[str] = None,
        patch_model: Optional[str] = None,
        peer_autonomous_container_database_backup_config: Optional[_database.AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigArgs] = None,
        peer_autonomous_container_database_compartment_id: Optional[str] = None,
        peer_autonomous_container_database_display_name: Optional[str] = None,
        peer_autonomous_vm_cluster_id: Optional[str] = None,
        peer_cloud_autonomous_vm_cluster_id: Optional[str] = None,
        peer_db_unique_name: Optional[str] = None,
        protection_mode: Optional[str] = None,
        provisionable_cpuses: Optional[Sequence[float]] = None,
        provisioned_cpus: Optional[float] = None,
        reclaimable_cpus: Optional[float] = None,
        reserved_cpus: Optional[float] = None,
        role: Optional[str] = None,
        service_level_agreement_type: Optional[str] = None,
        standby_maintenance_buffer_in_days: Optional[int] = None,
        state: Optional[str] = None,
        time_created: Optional[str] = None,
        time_of_last_backup: Optional[str] = None,
        time_snapshot_standby_revert: Optional[str] = None,
        total_cpus: Optional[int] = None,
        vault_id: Optional[str] = None,
        version_preference: Optional[str] = None,
        vm_failover_reservation: Optional[int] = None) -> AutonomousContainerDatabaseAddStandbyfunc GetAutonomousContainerDatabaseAddStandby(ctx *Context, name string, id IDInput, state *AutonomousContainerDatabaseAddStandbyState, opts ...ResourceOption) (*AutonomousContainerDatabaseAddStandby, error)public static AutonomousContainerDatabaseAddStandby Get(string name, Input<string> id, AutonomousContainerDatabaseAddStandbyState? state, CustomResourceOptions? opts = null)public static AutonomousContainerDatabaseAddStandby get(String name, Output<String> id, AutonomousContainerDatabaseAddStandbyState state, CustomResourceOptions options)resources:  _:    type: oci:Database:AutonomousContainerDatabaseAddStandby    get:      id: ${id}- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- AutonomousContainer stringDatabase Id 
- The Autonomous Container Database OCID.
- AutonomousExadata stringInfrastructure Id 
- No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.
- AutonomousVm stringCluster Id 
- The OCID of the Autonomous VM Cluster.
- AvailabilityDomain string
- The 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.
- BackupConfigs List<AutonomousContainer Database Add Standby Backup Config> 
- Backup options for the Autonomous Container Database.
- CloudAutonomous stringVm Cluster Id 
- The OCID of the cloud Autonomous Exadata VM Cluster.
- CompartmentId string
- The OCID of the compartment.
- ComputeModel 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.
- DataguardGroup List<AutonomousMembers Container Database Add Standby Dataguard Group Member> 
- Array of Dg associations.
- Dataguards
List<AutonomousContainer Database Add Standby Dataguard> 
- The properties that define Autonomous Container Databases Dataguard.
- 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.
- DbSplit 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.
- DbUnique stringName 
- DbVersion 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.
- DisplayName string
- The user-provided name for the Autonomous Container Database.
- DistributionAffinity 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.
- DstFile stringVersion 
- DST Time-Zone File version of the Autonomous Container Database.
- FastStart intFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance 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"}
- InfrastructureType string
- The infrastructure type this resource belongs to.
- IsAutomatic boolFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- IsData boolGuard Enabled 
- Deprecated. Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
- IsDst 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.
- IsMultiple boolStandby 
- Whether it is multiple standby Autonomous Dataguard
- KeyHistory List<AutonomousEntries Container Database Add Standby Key History Entry> 
- Key History Entry.
- KeyStore stringId 
- The OCID of the key store of Oracle Vault.
- KeyStore stringWallet Name 
- The wallet name for Oracle Key Vault.
- KmsKey stringId 
- The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- KmsKey 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.
- LargestProvisionable doubleAutonomous Database In Cpus 
- The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- LastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- ListOne List<string>Off Patches 
- List of One-Off patches that has been successfully applied to Autonomous Container Database
- MaintenanceWindows List<AutonomousContainer Database Add Standby Maintenance Window> 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- MemoryPer intOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- NetServices 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.
- NextMaintenance stringRun Id 
- 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.
- PeerAutonomous AutonomousContainer Database Backup Config Container Database Add Standby Peer Autonomous Container Database Backup Config 
- Backup options for the standby Autonomous Container Database.
- PeerAutonomous stringContainer Database Compartment Id 
- The OCID of the compartment where the standby Autonomous Container Database will be created.
- PeerAutonomous stringContainer Database Display Name 
- The display name for the peer Autonomous Container Database.
- PeerAutonomous stringVm Cluster Id 
- The OCID of the peer Autonomous Exadata VM Cluster.
- PeerCloud stringAutonomous Vm Cluster Id 
- The OCID of the peer cloud Autonomous Exadata VM Cluster.
- PeerDb stringUnique Name 
- Specifies the DB_UNIQUE_NAMEof the peer database to be created.
- ProtectionMode string
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- ProvisionableCpuses List<double>
- An array of CPU values that can be used to successfully provision a single Autonomous Database.
- ProvisionedCpus double
- The number of CPUs provisioned in an Autonomous Container Database.
- ReclaimableCpus 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.
- ReservedCpus 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.
- ServiceLevel stringAgreement Type 
- The service level agreement type of the container database. The default is STANDARD.
- StandbyMaintenance 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. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- State string
- The current state of the Autonomous Container Database.
- TimeCreated string
- The date and time the Autonomous Container Database was created.
- TimeOf 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.
- TimeSnapshot stringStandby Revert 
- 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.
- VaultId string
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- VersionPreference string
- The next maintenance version preference.
- VmFailover 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.
- AutonomousContainer stringDatabase Id 
- The Autonomous Container Database OCID.
- AutonomousExadata stringInfrastructure Id 
- No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.
- AutonomousVm stringCluster Id 
- The OCID of the Autonomous VM Cluster.
- AvailabilityDomain string
- The 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.
- BackupConfigs []AutonomousContainer Database Add Standby Backup Config Args 
- Backup options for the Autonomous Container Database.
- CloudAutonomous stringVm Cluster Id 
- The OCID of the cloud Autonomous Exadata VM Cluster.
- CompartmentId string
- The OCID of the compartment.
- ComputeModel 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.
- DataguardGroup []AutonomousMembers Container Database Add Standby Dataguard Group Member Args 
- Array of Dg associations.
- Dataguards
[]AutonomousContainer Database Add Standby Dataguard Args 
- The properties that define Autonomous Container Databases Dataguard.
- 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.
- DbSplit 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.
- DbUnique stringName 
- DbVersion 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.
- DisplayName string
- The user-provided name for the Autonomous Container Database.
- DistributionAffinity 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.
- DstFile stringVersion 
- DST Time-Zone File version of the Autonomous Container Database.
- FastStart intFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance 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"}
- InfrastructureType string
- The infrastructure type this resource belongs to.
- IsAutomatic boolFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- IsData boolGuard Enabled 
- Deprecated. Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
- IsDst 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.
- IsMultiple boolStandby 
- Whether it is multiple standby Autonomous Dataguard
- KeyHistory []AutonomousEntries Container Database Add Standby Key History Entry Args 
- Key History Entry.
- KeyStore stringId 
- The OCID of the key store of Oracle Vault.
- KeyStore stringWallet Name 
- The wallet name for Oracle Key Vault.
- KmsKey stringId 
- The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- KmsKey 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.
- LargestProvisionable float64Autonomous Database In Cpus 
- The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- LastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- ListOne []stringOff Patches 
- List of One-Off patches that has been successfully applied to Autonomous Container Database
- MaintenanceWindows []AutonomousContainer Database Add Standby Maintenance Window Args 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- MemoryPer intOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- NetServices 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.
- NextMaintenance stringRun Id 
- 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.
- PeerAutonomous AutonomousContainer Database Backup Config Container Database Add Standby Peer Autonomous Container Database Backup Config Args 
- Backup options for the standby Autonomous Container Database.
- PeerAutonomous stringContainer Database Compartment Id 
- The OCID of the compartment where the standby Autonomous Container Database will be created.
- PeerAutonomous stringContainer Database Display Name 
- The display name for the peer Autonomous Container Database.
- PeerAutonomous stringVm Cluster Id 
- The OCID of the peer Autonomous Exadata VM Cluster.
- PeerCloud stringAutonomous Vm Cluster Id 
- The OCID of the peer cloud Autonomous Exadata VM Cluster.
- PeerDb stringUnique Name 
- Specifies the DB_UNIQUE_NAMEof the peer database to be created.
- ProtectionMode string
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- ProvisionableCpuses []float64
- An array of CPU values that can be used to successfully provision a single Autonomous Database.
- ProvisionedCpus float64
- The number of CPUs provisioned in an Autonomous Container Database.
- ReclaimableCpus 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.
- ReservedCpus 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.
- ServiceLevel stringAgreement Type 
- The service level agreement type of the container database. The default is STANDARD.
- StandbyMaintenance 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. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- State string
- The current state of the Autonomous Container Database.
- TimeCreated string
- The date and time the Autonomous Container Database was created.
- TimeOf 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.
- TimeSnapshot stringStandby Revert 
- 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.
- VaultId string
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- VersionPreference string
- The next maintenance version preference.
- VmFailover 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.
- autonomousContainer StringDatabase Id 
- The Autonomous Container Database OCID.
- autonomousExadata StringInfrastructure Id 
- No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.
- autonomousVm StringCluster Id 
- The OCID of the Autonomous VM Cluster.
- availabilityDomain String
- The 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.
- backupConfigs List<AutonomousContainer Add Standby Backup Config> 
- Backup options for the Autonomous Container Database.
- cloudAutonomous StringVm Cluster Id 
- The OCID of the cloud Autonomous Exadata VM Cluster.
- compartmentId String
- The OCID of the compartment.
- computeModel 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.
- dataguardGroup List<AutonomousMembers Container Add Standby Dataguard Group Member> 
- Array of Dg associations.
- dataguards
List<AutonomousContainer Add Standby Dataguard> 
- The properties that define Autonomous Container Databases Dataguard.
- 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.
- dbSplit 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.
- dbUnique StringName 
- dbVersion 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.
- displayName String
- The user-provided name for the Autonomous Container Database.
- distributionAffinity 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.
- dstFile StringVersion 
- DST Time-Zone File version of the Autonomous Container Database.
- fastStart IntegerFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance 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"}
- infrastructureType String
- The infrastructure type this resource belongs to.
- isAutomatic BooleanFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- isData BooleanGuard Enabled 
- Deprecated. Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
- isDst 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.
- isMultiple BooleanStandby 
- Whether it is multiple standby Autonomous Dataguard
- keyHistory List<AutonomousEntries Container Add Standby Key History Entry> 
- Key History Entry.
- keyStore StringId 
- The OCID of the key store of Oracle Vault.
- keyStore StringWallet Name 
- The wallet name for Oracle Key Vault.
- kmsKey StringId 
- The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- kmsKey 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.
- largestProvisionable DoubleAutonomous Database In Cpus 
- The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- lastMaintenance StringRun Id 
- The OCID of the last maintenance run.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- listOne List<String>Off Patches 
- List of One-Off patches that has been successfully applied to Autonomous Container Database
- maintenanceWindows List<AutonomousContainer Add Standby Maintenance Window> 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memoryPer IntegerOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- netServices 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.
- nextMaintenance StringRun Id 
- 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.
- peerAutonomous AutonomousContainer Database Backup Config Container Add Standby Peer Autonomous Container Backup Config 
- Backup options for the standby Autonomous Container Database.
- peerAutonomous StringContainer Database Compartment Id 
- The OCID of the compartment where the standby Autonomous Container Database will be created.
- peerAutonomous StringContainer Database Display Name 
- The display name for the peer Autonomous Container Database.
- peerAutonomous StringVm Cluster Id 
- The OCID of the peer Autonomous Exadata VM Cluster.
- peerCloud StringAutonomous Vm Cluster Id 
- The OCID of the peer cloud Autonomous Exadata VM Cluster.
- peerDb StringUnique Name 
- Specifies the DB_UNIQUE_NAMEof the peer database to be created.
- protectionMode String
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- provisionableCpuses List<Double>
- An array of CPU values that can be used to successfully provision a single Autonomous Database.
- provisionedCpus Double
- The number of CPUs provisioned in an Autonomous Container Database.
- reclaimableCpus 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.
- reservedCpus 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.
- serviceLevel StringAgreement Type 
- The service level agreement type of the container database. The default is STANDARD.
- standbyMaintenance 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. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- state String
- The current state of the Autonomous Container Database.
- timeCreated String
- The date and time the Autonomous Container Database was created.
- timeOf 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.
- timeSnapshot StringStandby Revert 
- 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.
- vaultId String
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- versionPreference String
- The next maintenance version preference.
- vmFailover 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.
- autonomousContainer stringDatabase Id 
- The Autonomous Container Database OCID.
- autonomousExadata stringInfrastructure Id 
- No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.
- autonomousVm stringCluster Id 
- The OCID of the Autonomous VM Cluster.
- availabilityDomain string
- The 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.
- backupConfigs AutonomousContainer Database Add Standby Backup Config[] 
- Backup options for the Autonomous Container Database.
- cloudAutonomous stringVm Cluster Id 
- The OCID of the cloud Autonomous Exadata VM Cluster.
- compartmentId string
- The OCID of the compartment.
- computeModel 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.
- dataguardGroup AutonomousMembers Container Database Add Standby Dataguard Group Member[] 
- Array of Dg associations.
- dataguards
AutonomousContainer Database Add Standby Dataguard[] 
- The properties that define Autonomous Container Databases Dataguard.
- 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.
- dbSplit 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.
- dbUnique stringName 
- dbVersion 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.
- displayName string
- The user-provided name for the Autonomous Container Database.
- distributionAffinity 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.
- dstFile stringVersion 
- DST Time-Zone File version of the Autonomous Container Database.
- fastStart numberFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance 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"}
- infrastructureType string
- The infrastructure type this resource belongs to.
- isAutomatic booleanFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- isData booleanGuard Enabled 
- Deprecated. Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
- isDst 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.
- isMultiple booleanStandby 
- Whether it is multiple standby Autonomous Dataguard
- keyHistory AutonomousEntries Container Database Add Standby Key History Entry[] 
- Key History Entry.
- keyStore stringId 
- The OCID of the key store of Oracle Vault.
- keyStore stringWallet Name 
- The wallet name for Oracle Key Vault.
- kmsKey stringId 
- The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- kmsKey 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.
- largestProvisionable numberAutonomous Database In Cpus 
- The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- lastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- lifecycleDetails string
- Additional information about the current lifecycle state.
- listOne string[]Off Patches 
- List of One-Off patches that has been successfully applied to Autonomous Container Database
- maintenanceWindows AutonomousContainer Database Add Standby Maintenance Window[] 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memoryPer numberOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- netServices 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.
- nextMaintenance stringRun Id 
- 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.
- peerAutonomous AutonomousContainer Database Backup Config Container Database Add Standby Peer Autonomous Container Database Backup Config 
- Backup options for the standby Autonomous Container Database.
- peerAutonomous stringContainer Database Compartment Id 
- The OCID of the compartment where the standby Autonomous Container Database will be created.
- peerAutonomous stringContainer Database Display Name 
- The display name for the peer Autonomous Container Database.
- peerAutonomous stringVm Cluster Id 
- The OCID of the peer Autonomous Exadata VM Cluster.
- peerCloud stringAutonomous Vm Cluster Id 
- The OCID of the peer cloud Autonomous Exadata VM Cluster.
- peerDb stringUnique Name 
- Specifies the DB_UNIQUE_NAMEof the peer database to be created.
- protectionMode string
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- provisionableCpuses number[]
- An array of CPU values that can be used to successfully provision a single Autonomous Database.
- provisionedCpus number
- The number of CPUs provisioned in an Autonomous Container Database.
- reclaimableCpus 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.
- reservedCpus 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.
- serviceLevel stringAgreement Type 
- The service level agreement type of the container database. The default is STANDARD.
- standbyMaintenance 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. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- state string
- The current state of the Autonomous Container Database.
- timeCreated string
- The date and time the Autonomous Container Database was created.
- timeOf 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.
- timeSnapshot stringStandby Revert 
- 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.
- vaultId string
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- versionPreference string
- The next maintenance version preference.
- vmFailover 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_container_ strdatabase_ id 
- The Autonomous Container Database OCID.
- 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 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.
- backup_configs Sequence[database.Autonomous Container Database Add Standby Backup Config Args] 
- Backup options for the Autonomous Container Database.
- cloud_autonomous_ strvm_ cluster_ id 
- 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 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.
- dataguard_group_ Sequence[database.members Autonomous Container Database Add Standby Dataguard Group Member Args] 
- Array of Dg associations.
- dataguards
Sequence[database.Autonomous Container Database Add Standby Dataguard Args] 
- The properties that define Autonomous Container Databases Dataguard.
- 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
- The user-provided name for the Autonomous Container Database.
- 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 
- The lag time for my preference based on data loss tolerance 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"}
- infrastructure_type str
- The infrastructure type this resource belongs to.
- is_automatic_ boolfailover_ enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- is_data_ boolguard_ enabled 
- Deprecated. Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
- 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.
- is_multiple_ boolstandby 
- Whether it is multiple standby Autonomous Dataguard
- key_history_ Sequence[database.entries Autonomous Container Database Add Standby Key History Entry Args] 
- 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.
- kms_key_ strid 
- The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- 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.
- 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_windows Sequence[database.Autonomous Container Database Add Standby Maintenance Window Args] 
- 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_ database.container_ database_ backup_ config Autonomous Container Database Add Standby Peer Autonomous Container Database Backup Config Args 
- Backup options for the standby Autonomous Container Database.
- peer_autonomous_ strcontainer_ database_ compartment_ id 
- The OCID of the compartment where the standby Autonomous Container Database will be created.
- peer_autonomous_ strcontainer_ database_ display_ name 
- The display name for the peer Autonomous Container Database.
- peer_autonomous_ strvm_ cluster_ id 
- The OCID of the peer Autonomous Exadata VM Cluster.
- peer_cloud_ strautonomous_ vm_ cluster_ id 
- The OCID of the peer cloud Autonomous Exadata VM Cluster.
- peer_db_ strunique_ name 
- Specifies the DB_UNIQUE_NAMEof the peer database to be created.
- protection_mode str
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- 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.
- service_level_ stragreement_ type 
- The service level agreement type of the container database. The default is STANDARD.
- 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. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- state str
- The current state of the Autonomous Container Database.
- 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.
- vault_id str
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- 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.
- autonomousContainer StringDatabase Id 
- The Autonomous Container Database OCID.
- autonomousExadata StringInfrastructure Id 
- No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified cloudAutonomousVmCluster.
- autonomousVm StringCluster Id 
- The OCID of the Autonomous VM Cluster.
- availabilityDomain String
- The 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.
- backupConfigs List<Property Map>
- Backup options for the Autonomous Container Database.
- cloudAutonomous StringVm Cluster Id 
- The OCID of the cloud Autonomous Exadata VM Cluster.
- compartmentId String
- The OCID of the compartment.
- computeModel 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.
- dataguardGroup List<Property Map>Members 
- Array of Dg associations.
- dataguards List<Property Map>
- The properties that define Autonomous Container Databases Dataguard.
- 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.
- dbSplit 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.
- dbUnique StringName 
- dbVersion 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.
- displayName String
- The user-provided name for the Autonomous Container Database.
- distributionAffinity 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.
- dstFile StringVersion 
- DST Time-Zone File version of the Autonomous Container Database.
- fastStart NumberFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance 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"}
- infrastructureType String
- The infrastructure type this resource belongs to.
- isAutomatic BooleanFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- isData BooleanGuard Enabled 
- Deprecated. Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
- isDst 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.
- isMultiple BooleanStandby 
- Whether it is multiple standby Autonomous Dataguard
- keyHistory List<Property Map>Entries 
- Key History Entry.
- keyStore StringId 
- The OCID of the key store of Oracle Vault.
- keyStore StringWallet Name 
- The wallet name for Oracle Key Vault.
- kmsKey StringId 
- The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- kmsKey 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.
- largestProvisionable NumberAutonomous Database In Cpus 
- The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- lastMaintenance StringRun Id 
- The OCID of the last maintenance run.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- listOne List<String>Off Patches 
- List of One-Off patches that has been successfully applied to Autonomous Container Database
- maintenanceWindows List<Property Map>
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memoryPer NumberOracle Compute Unit In Gbs 
- The amount of memory (in GBs) enabled per ECPU or OCPU in the Autonomous VM Cluster.
- netServices 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.
- nextMaintenance StringRun Id 
- 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.
- peerAutonomous Property MapContainer Database Backup Config 
- Backup options for the standby Autonomous Container Database.
- peerAutonomous StringContainer Database Compartment Id 
- The OCID of the compartment where the standby Autonomous Container Database will be created.
- peerAutonomous StringContainer Database Display Name 
- The display name for the peer Autonomous Container Database.
- peerAutonomous StringVm Cluster Id 
- The OCID of the peer Autonomous Exadata VM Cluster.
- peerCloud StringAutonomous Vm Cluster Id 
- The OCID of the peer cloud Autonomous Exadata VM Cluster.
- peerDb StringUnique Name 
- Specifies the DB_UNIQUE_NAMEof the peer database to be created.
- protectionMode String
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- provisionableCpuses List<Number>
- An array of CPU values that can be used to successfully provision a single Autonomous Database.
- provisionedCpus Number
- The number of CPUs provisioned in an Autonomous Container Database.
- reclaimableCpus 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.
- reservedCpus 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.
- serviceLevel StringAgreement Type 
- The service level agreement type of the container database. The default is STANDARD.
- standbyMaintenance 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. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- state String
- The current state of the Autonomous Container Database.
- timeCreated String
- The date and time the Autonomous Container Database was created.
- timeOf 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.
- timeSnapshot StringStandby Revert 
- 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.
- vaultId String
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- versionPreference String
- The next maintenance version preference.
- vmFailover 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.
Supporting Types
AutonomousContainerDatabaseAddStandbyBackupConfig, AutonomousContainerDatabaseAddStandbyBackupConfigArgs              
- BackupDestination List<AutonomousDetails Container Database Add Standby Backup Config Backup Destination Detail> 
- Backup destination details.
- RecoveryWindow 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.
- BackupDestination []AutonomousDetails Container Database Add Standby Backup Config Backup Destination Detail 
- Backup destination details.
- RecoveryWindow 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.
- backupDestination List<AutonomousDetails Container Add Standby Backup Config Backup Destination Detail> 
- Backup destination details.
- recoveryWindow 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.
- backupDestination AutonomousDetails Container Database Add Standby Backup Config Backup Destination Detail[] 
- Backup destination details.
- recoveryWindow 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 Autonomous Container Database Add Standby 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.
- backupDestination List<Property Map>Details 
- Backup destination details.
- recoveryWindow 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.
AutonomousContainerDatabaseAddStandbyBackupConfigBackupDestinationDetail, AutonomousContainerDatabaseAddStandbyBackupConfigBackupDestinationDetailArgs                    
- DbrsPolicy stringId 
- The OCID of the DBRS policy used for backup.
- 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.
- DbrsPolicy stringId 
- The OCID of the DBRS policy used for backup.
- 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.
- dbrsPolicy StringId 
- The OCID of the DBRS policy used for backup.
- 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.
- dbrsPolicy stringId 
- The OCID of the DBRS policy used for backup.
- 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.
- dbrs_policy_ strid 
- The OCID of the DBRS policy used for backup.
- 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.
- dbrsPolicy StringId 
- The OCID of the DBRS policy used for backup.
- 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.
AutonomousContainerDatabaseAddStandbyDataguard, AutonomousContainerDatabaseAddStandbyDataguardArgs            
- ApplyLag string
- The lag time between updates to the primary Autonomous Container Database and application of the redo data on the standby Autonomous Container Database, as computed by the reporting database. Example: 9 seconds
- ApplyRate string
- The rate at which redo logs are synchronized between the associated Autonomous Container Databases. Example: 180 Mb per second
- AutomaticFailover stringTarget 
- Automatically selected by backend when observer is enabled.
- AutonomousContainer stringDatabase Id 
- The Autonomous Container Database OCID.
- AvailabilityDomain string
- The domain of the Autonomous Container Database
- FastStart intFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- IsAutomatic boolFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- LifecycleDetails string
- Additional information about the current lifecycle state.
- ProtectionMode string
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- RedoTransport stringMode 
- Automatically selected by backend based on the protection mode.
- Role string
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- State string
- The current state of the Autonomous Container Database.
- TimeCreated string
- The date and time the Autonomous Container Database was created.
- TimeLag stringRefreshed On 
- Timestamp when the lags were last calculated for a standby.
- TimeLast stringRole Changed 
- The date and time when the last role change action happened.
- TimeLast stringSynced 
- The date and time of the last update to the apply lag, apply rate, and transport lag values.
- TransportLag string
- The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database. Example: 7 seconds
- ApplyLag string
- The lag time between updates to the primary Autonomous Container Database and application of the redo data on the standby Autonomous Container Database, as computed by the reporting database. Example: 9 seconds
- ApplyRate string
- The rate at which redo logs are synchronized between the associated Autonomous Container Databases. Example: 180 Mb per second
- AutomaticFailover stringTarget 
- Automatically selected by backend when observer is enabled.
- AutonomousContainer stringDatabase Id 
- The Autonomous Container Database OCID.
- AvailabilityDomain string
- The domain of the Autonomous Container Database
- FastStart intFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- IsAutomatic boolFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- LifecycleDetails string
- Additional information about the current lifecycle state.
- ProtectionMode string
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- RedoTransport stringMode 
- Automatically selected by backend based on the protection mode.
- Role string
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- State string
- The current state of the Autonomous Container Database.
- TimeCreated string
- The date and time the Autonomous Container Database was created.
- TimeLag stringRefreshed On 
- Timestamp when the lags were last calculated for a standby.
- TimeLast stringRole Changed 
- The date and time when the last role change action happened.
- TimeLast stringSynced 
- The date and time of the last update to the apply lag, apply rate, and transport lag values.
- TransportLag string
- The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database. Example: 7 seconds
- applyLag String
- The lag time between updates to the primary Autonomous Container Database and application of the redo data on the standby Autonomous Container Database, as computed by the reporting database. Example: 9 seconds
- applyRate String
- The rate at which redo logs are synchronized between the associated Autonomous Container Databases. Example: 180 Mb per second
- automaticFailover StringTarget 
- Automatically selected by backend when observer is enabled.
- autonomousContainer StringDatabase Id 
- The Autonomous Container Database OCID.
- availabilityDomain String
- The domain of the Autonomous Container Database
- fastStart IntegerFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- isAutomatic BooleanFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- lifecycleDetails String
- Additional information about the current lifecycle state.
- protectionMode String
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- redoTransport StringMode 
- Automatically selected by backend based on the protection mode.
- role String
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- state String
- The current state of the Autonomous Container Database.
- timeCreated String
- The date and time the Autonomous Container Database was created.
- timeLag StringRefreshed On 
- Timestamp when the lags were last calculated for a standby.
- timeLast StringRole Changed 
- The date and time when the last role change action happened.
- timeLast StringSynced 
- The date and time of the last update to the apply lag, apply rate, and transport lag values.
- transportLag String
- The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database. Example: 7 seconds
- applyLag string
- The lag time between updates to the primary Autonomous Container Database and application of the redo data on the standby Autonomous Container Database, as computed by the reporting database. Example: 9 seconds
- applyRate string
- The rate at which redo logs are synchronized between the associated Autonomous Container Databases. Example: 180 Mb per second
- automaticFailover stringTarget 
- Automatically selected by backend when observer is enabled.
- autonomousContainer stringDatabase Id 
- The Autonomous Container Database OCID.
- availabilityDomain string
- The domain of the Autonomous Container Database
- fastStart numberFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- isAutomatic booleanFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- lifecycleDetails string
- Additional information about the current lifecycle state.
- protectionMode string
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- redoTransport stringMode 
- Automatically selected by backend based on the protection mode.
- role string
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- state string
- The current state of the Autonomous Container Database.
- timeCreated string
- The date and time the Autonomous Container Database was created.
- timeLag stringRefreshed On 
- Timestamp when the lags were last calculated for a standby.
- timeLast stringRole Changed 
- The date and time when the last role change action happened.
- timeLast stringSynced 
- The date and time of the last update to the apply lag, apply rate, and transport lag values.
- transportLag string
- The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database. Example: 7 seconds
- apply_lag str
- The lag time between updates to the primary Autonomous Container Database and application of the redo data on the standby Autonomous Container Database, as computed by the reporting database. Example: 9 seconds
- apply_rate str
- The rate at which redo logs are synchronized between the associated Autonomous Container Databases. Example: 180 Mb per second
- automatic_failover_ strtarget 
- Automatically selected by backend when observer is enabled.
- autonomous_container_ strdatabase_ id 
- The Autonomous Container Database OCID.
- availability_domain str
- The domain of the Autonomous Container Database
- fast_start_ intfail_ over_ lag_ limit_ in_ seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- is_automatic_ boolfailover_ enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- lifecycle_details str
- Additional information about the current lifecycle state.
- protection_mode str
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- redo_transport_ strmode 
- Automatically selected by backend based on the protection mode.
- role str
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- state str
- The current state of the Autonomous Container Database.
- time_created str
- The date and time the Autonomous Container Database was created.
- time_lag_ strrefreshed_ on 
- Timestamp when the lags were last calculated for a standby.
- time_last_ strrole_ changed 
- The date and time when the last role change action happened.
- time_last_ strsynced 
- The date and time of the last update to the apply lag, apply rate, and transport lag values.
- transport_lag str
- The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database. Example: 7 seconds
- applyLag String
- The lag time between updates to the primary Autonomous Container Database and application of the redo data on the standby Autonomous Container Database, as computed by the reporting database. Example: 9 seconds
- applyRate String
- The rate at which redo logs are synchronized between the associated Autonomous Container Databases. Example: 180 Mb per second
- automaticFailover StringTarget 
- Automatically selected by backend when observer is enabled.
- autonomousContainer StringDatabase Id 
- The Autonomous Container Database OCID.
- availabilityDomain String
- The domain of the Autonomous Container Database
- fastStart NumberFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- isAutomatic BooleanFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- lifecycleDetails String
- Additional information about the current lifecycle state.
- protectionMode String
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- redoTransport StringMode 
- Automatically selected by backend based on the protection mode.
- role String
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- state String
- The current state of the Autonomous Container Database.
- timeCreated String
- The date and time the Autonomous Container Database was created.
- timeLag StringRefreshed On 
- Timestamp when the lags were last calculated for a standby.
- timeLast StringRole Changed 
- The date and time when the last role change action happened.
- timeLast StringSynced 
- The date and time of the last update to the apply lag, apply rate, and transport lag values.
- transportLag String
- The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database. Example: 7 seconds
AutonomousContainerDatabaseAddStandbyDataguardGroupMember, AutonomousContainerDatabaseAddStandbyDataguardGroupMemberArgs                
- ApplyLag string
- The lag time between updates to the primary Autonomous Container Database and application of the redo data on the standby Autonomous Container Database, as computed by the reporting database. Example: 9 seconds
- ApplyRate string
- The rate at which redo logs are synchronized between the associated Autonomous Container Databases. Example: 180 Mb per second
- AutomaticFailover stringTarget 
- Automatically selected by backend when observer is enabled.
- AutonomousContainer stringDatabase Id 
- The Autonomous Container Database OCID.
- AvailabilityDomain string
- The domain of the Autonomous Container Database
- FastStart intFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- IsAutomatic boolFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- LifecycleDetails string
- Additional information about the current lifecycle state.
- ProtectionMode string
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- RedoTransport stringMode 
- Automatically selected by backend based on the protection mode.
- Role string
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- State string
- The current state of the Autonomous Container Database.
- TimeCreated string
- The date and time the Autonomous Container Database was created.
- TimeLag stringRefreshed On 
- Timestamp when the lags were last calculated for a standby.
- TimeLast stringRole Changed 
- The date and time when the last role change action happened.
- TimeLast stringSynced 
- The date and time of the last update to the apply lag, apply rate, and transport lag values.
- TransportLag string
- The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database. Example: 7 seconds
- ApplyLag string
- The lag time between updates to the primary Autonomous Container Database and application of the redo data on the standby Autonomous Container Database, as computed by the reporting database. Example: 9 seconds
- ApplyRate string
- The rate at which redo logs are synchronized between the associated Autonomous Container Databases. Example: 180 Mb per second
- AutomaticFailover stringTarget 
- Automatically selected by backend when observer is enabled.
- AutonomousContainer stringDatabase Id 
- The Autonomous Container Database OCID.
- AvailabilityDomain string
- The domain of the Autonomous Container Database
- FastStart intFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- IsAutomatic boolFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- LifecycleDetails string
- Additional information about the current lifecycle state.
- ProtectionMode string
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- RedoTransport stringMode 
- Automatically selected by backend based on the protection mode.
- Role string
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- State string
- The current state of the Autonomous Container Database.
- TimeCreated string
- The date and time the Autonomous Container Database was created.
- TimeLag stringRefreshed On 
- Timestamp when the lags were last calculated for a standby.
- TimeLast stringRole Changed 
- The date and time when the last role change action happened.
- TimeLast stringSynced 
- The date and time of the last update to the apply lag, apply rate, and transport lag values.
- TransportLag string
- The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database. Example: 7 seconds
- applyLag String
- The lag time between updates to the primary Autonomous Container Database and application of the redo data on the standby Autonomous Container Database, as computed by the reporting database. Example: 9 seconds
- applyRate String
- The rate at which redo logs are synchronized between the associated Autonomous Container Databases. Example: 180 Mb per second
- automaticFailover StringTarget 
- Automatically selected by backend when observer is enabled.
- autonomousContainer StringDatabase Id 
- The Autonomous Container Database OCID.
- availabilityDomain String
- The domain of the Autonomous Container Database
- fastStart IntegerFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- isAutomatic BooleanFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- lifecycleDetails String
- Additional information about the current lifecycle state.
- protectionMode String
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- redoTransport StringMode 
- Automatically selected by backend based on the protection mode.
- role String
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- state String
- The current state of the Autonomous Container Database.
- timeCreated String
- The date and time the Autonomous Container Database was created.
- timeLag StringRefreshed On 
- Timestamp when the lags were last calculated for a standby.
- timeLast StringRole Changed 
- The date and time when the last role change action happened.
- timeLast StringSynced 
- The date and time of the last update to the apply lag, apply rate, and transport lag values.
- transportLag String
- The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database. Example: 7 seconds
- applyLag string
- The lag time between updates to the primary Autonomous Container Database and application of the redo data on the standby Autonomous Container Database, as computed by the reporting database. Example: 9 seconds
- applyRate string
- The rate at which redo logs are synchronized between the associated Autonomous Container Databases. Example: 180 Mb per second
- automaticFailover stringTarget 
- Automatically selected by backend when observer is enabled.
- autonomousContainer stringDatabase Id 
- The Autonomous Container Database OCID.
- availabilityDomain string
- The domain of the Autonomous Container Database
- fastStart numberFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- isAutomatic booleanFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- lifecycleDetails string
- Additional information about the current lifecycle state.
- protectionMode string
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- redoTransport stringMode 
- Automatically selected by backend based on the protection mode.
- role string
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- state string
- The current state of the Autonomous Container Database.
- timeCreated string
- The date and time the Autonomous Container Database was created.
- timeLag stringRefreshed On 
- Timestamp when the lags were last calculated for a standby.
- timeLast stringRole Changed 
- The date and time when the last role change action happened.
- timeLast stringSynced 
- The date and time of the last update to the apply lag, apply rate, and transport lag values.
- transportLag string
- The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database. Example: 7 seconds
- apply_lag str
- The lag time between updates to the primary Autonomous Container Database and application of the redo data on the standby Autonomous Container Database, as computed by the reporting database. Example: 9 seconds
- apply_rate str
- The rate at which redo logs are synchronized between the associated Autonomous Container Databases. Example: 180 Mb per second
- automatic_failover_ strtarget 
- Automatically selected by backend when observer is enabled.
- autonomous_container_ strdatabase_ id 
- The Autonomous Container Database OCID.
- availability_domain str
- The domain of the Autonomous Container Database
- fast_start_ intfail_ over_ lag_ limit_ in_ seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- is_automatic_ boolfailover_ enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- lifecycle_details str
- Additional information about the current lifecycle state.
- protection_mode str
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- redo_transport_ strmode 
- Automatically selected by backend based on the protection mode.
- role str
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- state str
- The current state of the Autonomous Container Database.
- time_created str
- The date and time the Autonomous Container Database was created.
- time_lag_ strrefreshed_ on 
- Timestamp when the lags were last calculated for a standby.
- time_last_ strrole_ changed 
- The date and time when the last role change action happened.
- time_last_ strsynced 
- The date and time of the last update to the apply lag, apply rate, and transport lag values.
- transport_lag str
- The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database. Example: 7 seconds
- applyLag String
- The lag time between updates to the primary Autonomous Container Database and application of the redo data on the standby Autonomous Container Database, as computed by the reporting database. Example: 9 seconds
- applyRate String
- The rate at which redo logs are synchronized between the associated Autonomous Container Databases. Example: 180 Mb per second
- automaticFailover StringTarget 
- Automatically selected by backend when observer is enabled.
- autonomousContainer StringDatabase Id 
- The Autonomous Container Database OCID.
- availabilityDomain String
- The domain of the Autonomous Container Database
- fastStart NumberFail Over Lag Limit In Seconds 
- The lag time for my preference based on data loss tolerance in seconds.
- isAutomatic BooleanFailover Enabled 
- Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
- lifecycleDetails String
- Additional information about the current lifecycle state.
- protectionMode String
- The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
- redoTransport StringMode 
- Automatically selected by backend based on the protection mode.
- role String
- The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- state String
- The current state of the Autonomous Container Database.
- timeCreated String
- The date and time the Autonomous Container Database was created.
- timeLag StringRefreshed On 
- Timestamp when the lags were last calculated for a standby.
- timeLast StringRole Changed 
- The date and time when the last role change action happened.
- timeLast StringSynced 
- The date and time of the last update to the apply lag, apply rate, and transport lag values.
- transportLag String
- The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database. Example: 7 seconds
AutonomousContainerDatabaseAddStandbyKeyHistoryEntry, AutonomousContainerDatabaseAddStandbyKeyHistoryEntryArgs                
- Id string
- The id of the Autonomous Database Vault service key management history entry.
- KmsKey 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.
- TimeActivated string
- The date and time the kms key activated.
- VaultId string
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- Id string
- The id of the Autonomous Database Vault service key management history entry.
- KmsKey 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.
- TimeActivated string
- The date and time the kms key activated.
- VaultId string
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- id String
- The id of the Autonomous Database Vault service key management history entry.
- kmsKey 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.
- timeActivated String
- The date and time the kms key activated.
- vaultId String
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- id string
- The id of the Autonomous Database Vault service key management history entry.
- kmsKey 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.
- timeActivated string
- The date and time the kms key activated.
- vaultId string
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
- 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. This parameter and secretIdare required for Customer Managed Keys.
- id String
- The id of the Autonomous Database Vault service key management history entry.
- kmsKey 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.
- timeActivated String
- The date and time the kms key activated.
- vaultId String
- The OCID of the Oracle Cloud Infrastructure vault. This parameter and secretIdare required for Customer Managed Keys.
AutonomousContainerDatabaseAddStandbyMaintenanceWindow, AutonomousContainerDatabaseAddStandbyMaintenanceWindowArgs              
- CustomAction intTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- DaysOf List<AutonomousWeeks Container Database Add Standby Maintenance Window Days Of Week> 
- Days during the week when maintenance should be performed.
- HoursOf List<int>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are - 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- IsMonthly boolPatching Enabled 
- If true, enables the monthly patching option.
- LeadTime intIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
List<AutonomousContainer Database Add Standby Maintenance Window Month> 
- Months during the year when maintenance should be performed.
- PatchingMode string
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
- The maintenance window scheduling preference.
- SkipRus List<bool>
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- WeeksOf List<int>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- CustomAction intTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- DaysOf []AutonomousWeeks Container Database Add Standby Maintenance Window Days Of Week 
- Days during the week when maintenance should be performed.
- HoursOf []intDays 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are - 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- IsMonthly boolPatching Enabled 
- If true, enables the monthly patching option.
- LeadTime intIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
[]AutonomousContainer Database Add Standby Maintenance Window Month 
- Months during the year when maintenance should be performed.
- PatchingMode string
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
- The maintenance window scheduling preference.
- SkipRus []bool
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- WeeksOf []intMonths 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction IntegerTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- daysOf List<AutonomousWeeks Container Add Standby Maintenance Window Days Of Week> 
- Days during the week when maintenance should be performed.
- hoursOf List<Integer>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are - 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly BooleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime IntegerIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
List<AutonomousContainer Add Standby Maintenance Window Month> 
- Months during the year when maintenance should be performed.
- patchingMode String
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
- The maintenance window scheduling preference.
- skipRus List<Boolean>
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeksOf List<Integer>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction numberTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- daysOf AutonomousWeeks Container Database Add Standby Maintenance Window Days Of Week[] 
- Days during the week when maintenance should be performed.
- hoursOf number[]Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are - 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- isCustom booleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly booleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime numberIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
AutonomousContainer Database Add Standby Maintenance Window Month[] 
- Months during the year when maintenance should be performed.
- patchingMode string
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference string
- The maintenance window scheduling preference.
- skipRus boolean[]
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeksOf number[]Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom_action_ inttimeout_ in_ mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days_of_ Sequence[database.weeks Autonomous Container Database Add Standby 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.Autonomous Container Database Add Standby Maintenance Window Month] 
- Months during the year when maintenance should be performed.
- patching_mode str
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference str
- The maintenance window scheduling preference.
- skip_rus Sequence[bool]
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeks_of_ Sequence[int]months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction NumberTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- daysOf List<Property Map>Weeks 
- Days during the week when maintenance should be performed.
- hoursOf List<Number>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are - 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly BooleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime NumberIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months List<Property Map>
- Months during the year when maintenance should be performed.
- patchingMode String
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
- The maintenance window scheduling preference.
- skipRus List<Boolean>
- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.
- weeksOf List<Number>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
AutonomousContainerDatabaseAddStandbyMaintenanceWindowDaysOfWeek, AutonomousContainerDatabaseAddStandbyMaintenanceWindowDaysOfWeekArgs                    
- 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.
AutonomousContainerDatabaseAddStandbyMaintenanceWindowMonth, AutonomousContainerDatabaseAddStandbyMaintenanceWindowMonthArgs                
- 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.
AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfig, AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigArgs                      
- BackupDestination List<AutonomousDetails Container Database Add Standby Peer Autonomous Container Database Backup Config Backup Destination Detail> 
- Backup destination details.
- RecoveryWindow 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.
- BackupDestination []AutonomousDetails Container Database Add Standby Peer Autonomous Container Database Backup Config Backup Destination Detail 
- Backup destination details.
- RecoveryWindow 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.
- backupDestination List<AutonomousDetails Container Add Standby Peer Autonomous Container Backup Config Backup Destination Detail> 
- Backup destination details.
- recoveryWindow 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.
- backupDestination AutonomousDetails Container Database Add Standby Peer Autonomous Container Database Backup Config Backup Destination Detail[] 
- Backup destination details.
- recoveryWindow 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 Autonomous Container Database Add Standby 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.
- backupDestination List<Property Map>Details 
- Backup destination details.
- recoveryWindow 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.
AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetail, AutonomousContainerDatabaseAddStandbyPeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailArgs                            
- Type string
- Type of the database backup destination.
- DbrsPolicy stringId 
- The OCID of the DBRS policy used for backup.
- Id string
- The OCID of the backup destination.
- InternetProxy string
- Proxy URL to connect to object store.
- 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.
- Type string
- Type of the database backup destination.
- DbrsPolicy stringId 
- The OCID of the DBRS policy used for backup.
- Id string
- The OCID of the backup destination.
- InternetProxy string
- Proxy URL to connect to object store.
- 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.
- type String
- Type of the database backup destination.
- dbrsPolicy StringId 
- The OCID of the DBRS policy used for backup.
- id String
- The OCID of the backup destination.
- internetProxy String
- Proxy URL to connect to object store.
- 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.
- type string
- Type of the database backup destination.
- dbrsPolicy stringId 
- The OCID of the DBRS policy used for backup.
- id string
- The OCID of the backup destination.
- internetProxy string
- Proxy URL to connect to object store.
- 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.
- type str
- Type of the database backup destination.
- dbrs_policy_ strid 
- The OCID of the DBRS policy used for backup.
- id str
- The OCID of the backup destination.
- internet_proxy str
- Proxy URL to connect to object store.
- 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.
- type String
- Type of the database backup destination.
- dbrsPolicy StringId 
- The OCID of the DBRS policy used for backup.
- id String
- The OCID of the backup destination.
- internetProxy String
- Proxy URL to connect to object store.
- 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.
Import
AutonomousContainerDatabaseAddStandby can be imported using the id, e.g.
$ pulumi import oci:Database/autonomousContainerDatabaseAddStandby:AutonomousContainerDatabaseAddStandby test_autonomous_container_database_add_standby "id"
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the ociTerraform Provider.