Docs
Packagesoci.Database.AutonomousContainerDatabase
Explore with Pulumi AI
This resource provides the Autonomous Container Database resource in Oracle Cloud Infrastructure Database service.
Creates an Autonomous Container Database in the specified Autonomous Exadata Infrastructure.
Example Usage
Coming soon!
Coming soon!
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Database.AutonomousContainerDatabase;
import com.pulumi.oci.Database.AutonomousContainerDatabaseArgs;
import com.pulumi.oci.Database.inputs.AutonomousContainerDatabaseBackupConfigArgs;
import com.pulumi.oci.Database.inputs.AutonomousContainerDatabaseBackupConfigBackupDestinationDetailsArgs;
import com.pulumi.oci.Database.inputs.AutonomousContainerDatabaseMaintenanceWindowDetailsArgs;
import com.pulumi.oci.Database.inputs.AutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigArgs;
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 testAutonomousContainerDatabase = new AutonomousContainerDatabase("testAutonomousContainerDatabase", AutonomousContainerDatabaseArgs.builder()
.displayName(var_.autonomous_container_database_display_name())
.patchModel(var_.autonomous_container_database_patch_model())
.cloudAutonomousVmClusterId(oci_database_cloud_autonomous_vm_cluster.test_cloud_autonomous_vm_cluster().id())
.autonomousVmClusterId(oci_database_autonomous_vm_cluster.test_autonomous_vm_cluster().id())
.backupConfig(AutonomousContainerDatabaseBackupConfigArgs.builder()
.backupDestinationDetails(AutonomousContainerDatabaseBackupConfigBackupDestinationDetailsArgs.builder()
.type(var_.autonomous_container_database_backup_config_backup_destination_details_type())
.dbrsPolicyId(oci_identity_policy.test_policy().id())
.id(var_.autonomous_container_database_backup_config_backup_destination_details_id())
.internetProxy(var_.autonomous_container_database_backup_config_backup_destination_details_internet_proxy())
.vpcPassword(var_.autonomous_container_database_backup_config_backup_destination_details_vpc_password())
.vpcUser(var_.autonomous_container_database_backup_config_backup_destination_details_vpc_user())
.build())
.recoveryWindowInDays(var_.autonomous_container_database_backup_config_recovery_window_in_days())
.build())
.compartmentId(var_.compartment_id())
.dbName(var_.autonomous_container_database_db_name())
.dbUniqueName(var_.autonomous_container_database_db_unique_name())
.dbVersion(var_.autonomous_container_database_db_version())
.definedTags(Map.of("Operations.CostCenter", "42"))
.fastStartFailOverLagLimitInSeconds(var_.autonomous_container_database_fast_start_fail_over_lag_limit_in_seconds())
.freeformTags(Map.of("Department", "Finance"))
.isAutomaticFailoverEnabled(var_.autonomous_container_database_is_automatic_failover_enabled())
.keyStoreId(oci_database_key_store.test_key_store().id())
.kmsKeyId(oci_kms_key.test_key().id())
.maintenanceWindowDetails(AutonomousContainerDatabaseMaintenanceWindowDetailsArgs.builder()
.customActionTimeoutInMins(var_.autonomous_container_database_maintenance_window_details_custom_action_timeout_in_mins())
.daysOfWeeks(AutonomousContainerDatabaseMaintenanceWindowDetailsDaysOfWeekArgs.builder()
.name(var_.autonomous_container_database_maintenance_window_details_days_of_week_name())
.build())
.hoursOfDays(var_.autonomous_container_database_maintenance_window_details_hours_of_day())
.isCustomActionTimeoutEnabled(var_.autonomous_container_database_maintenance_window_details_is_custom_action_timeout_enabled())
.isMonthlyPatchingEnabled(var_.autonomous_container_database_maintenance_window_details_is_monthly_patching_enabled())
.leadTimeInWeeks(var_.autonomous_container_database_maintenance_window_details_lead_time_in_weeks())
.months(AutonomousContainerDatabaseMaintenanceWindowDetailsMonthArgs.builder()
.name(var_.autonomous_container_database_maintenance_window_details_months_name())
.build())
.patchingMode(var_.autonomous_container_database_maintenance_window_details_patching_mode())
.preference(var_.autonomous_container_database_maintenance_window_details_preference())
.weeksOfMonths(var_.autonomous_container_database_maintenance_window_details_weeks_of_month())
.build())
.peerAutonomousContainerDatabaseDisplayName(var_.autonomous_container_database_peer_autonomous_container_database_display_name())
.peerCloudAutonomousVmClusterId(oci_database_cloud_autonomous_vm_cluster.test_cloud_autonomous_vm_cluster().id())
.protectionMode(var_.autonomous_container_database_protection_mode())
.peerAutonomousContainerDatabaseBackupConfig(AutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigArgs.builder()
.backupDestinationDetails(AutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetailArgs.builder()
.type(var_.autonomous_container_database_peer_autonomous_container_database_backup_config_backup_destination_details_type())
.dbrsPolicyId(oci_identity_policy.test_policy().id())
.id(var_.autonomous_container_database_peer_autonomous_container_database_backup_config_backup_destination_details_id())
.internetProxy(var_.autonomous_container_database_peer_autonomous_container_database_backup_config_backup_destination_details_internet_proxy())
.vpcPassword(var_.autonomous_container_database_peer_autonomous_container_database_backup_config_backup_destination_details_vpc_password())
.vpcUser(var_.autonomous_container_database_peer_autonomous_container_database_backup_config_backup_destination_details_vpc_user())
.build())
.recoveryWindowInDays(var_.autonomous_container_database_peer_autonomous_container_database_backup_config_recovery_window_in_days())
.build())
.peerAutonomousContainerDatabaseCompartmentId(oci_identity_compartment.test_compartment().id())
.peerAutonomousVmClusterId(oci_database_autonomous_vm_cluster.test_autonomous_vm_cluster().id())
.peerDbUniqueName(var_.autonomous_container_database_peer_db_unique_name())
.serviceLevelAgreementType(var_.autonomous_container_database_service_level_agreement_type())
.vaultId(oci_kms_vault.test_vault().id())
.versionPreference(var_.autonomous_container_database_version_preference())
.standbyMaintenanceBufferInDays(var_.autonomous_container_database_standby_maintenance_buffer_in_days())
.build());
}
}
Coming soon!
Coming soon!
resources:
testAutonomousContainerDatabase:
type: oci:Database:AutonomousContainerDatabase
properties:
#Required
displayName: ${var.autonomous_container_database_display_name}
patchModel: ${var.autonomous_container_database_patch_model}
#Optional
cloudAutonomousVmClusterId: ${oci_database_cloud_autonomous_vm_cluster.test_cloud_autonomous_vm_cluster.id}
autonomousVmClusterId: ${oci_database_autonomous_vm_cluster.test_autonomous_vm_cluster.id}
backupConfig:
backupDestinationDetails:
type: ${var.autonomous_container_database_backup_config_backup_destination_details_type}
dbrsPolicyId: ${oci_identity_policy.test_policy.id}
id: ${var.autonomous_container_database_backup_config_backup_destination_details_id}
internetProxy: ${var.autonomous_container_database_backup_config_backup_destination_details_internet_proxy}
vpcPassword: ${var.autonomous_container_database_backup_config_backup_destination_details_vpc_password}
vpcUser: ${var.autonomous_container_database_backup_config_backup_destination_details_vpc_user}
recoveryWindowInDays: ${var.autonomous_container_database_backup_config_recovery_window_in_days}
compartmentId: ${var.compartment_id}
dbName: ${var.autonomous_container_database_db_name}
dbUniqueName: ${var.autonomous_container_database_db_unique_name}
dbVersion: ${var.autonomous_container_database_db_version}
definedTags:
Operations.CostCenter: '42'
fastStartFailOverLagLimitInSeconds: ${var.autonomous_container_database_fast_start_fail_over_lag_limit_in_seconds}
freeformTags:
Department: Finance
isAutomaticFailoverEnabled: ${var.autonomous_container_database_is_automatic_failover_enabled}
keyStoreId: ${oci_database_key_store.test_key_store.id}
kmsKeyId: ${oci_kms_key.test_key.id}
maintenanceWindowDetails:
customActionTimeoutInMins: ${var.autonomous_container_database_maintenance_window_details_custom_action_timeout_in_mins}
daysOfWeeks:
- name: ${var.autonomous_container_database_maintenance_window_details_days_of_week_name}
hoursOfDays: ${var.autonomous_container_database_maintenance_window_details_hours_of_day}
isCustomActionTimeoutEnabled: ${var.autonomous_container_database_maintenance_window_details_is_custom_action_timeout_enabled}
isMonthlyPatchingEnabled: ${var.autonomous_container_database_maintenance_window_details_is_monthly_patching_enabled}
leadTimeInWeeks: ${var.autonomous_container_database_maintenance_window_details_lead_time_in_weeks}
months:
- name: ${var.autonomous_container_database_maintenance_window_details_months_name}
patchingMode: ${var.autonomous_container_database_maintenance_window_details_patching_mode}
preference: ${var.autonomous_container_database_maintenance_window_details_preference}
weeksOfMonths: ${var.autonomous_container_database_maintenance_window_details_weeks_of_month}
peerAutonomousContainerDatabaseDisplayName: ${var.autonomous_container_database_peer_autonomous_container_database_display_name}
peerCloudAutonomousVmClusterId: ${oci_database_cloud_autonomous_vm_cluster.test_cloud_autonomous_vm_cluster.id}
protectionMode: ${var.autonomous_container_database_protection_mode}
peerAutonomousContainerDatabaseBackupConfig:
backupDestinationDetails:
- type: ${var.autonomous_container_database_peer_autonomous_container_database_backup_config_backup_destination_details_type}
dbrsPolicyId: ${oci_identity_policy.test_policy.id}
id: ${var.autonomous_container_database_peer_autonomous_container_database_backup_config_backup_destination_details_id}
internetProxy: ${var.autonomous_container_database_peer_autonomous_container_database_backup_config_backup_destination_details_internet_proxy}
vpcPassword: ${var.autonomous_container_database_peer_autonomous_container_database_backup_config_backup_destination_details_vpc_password}
vpcUser: ${var.autonomous_container_database_peer_autonomous_container_database_backup_config_backup_destination_details_vpc_user}
recoveryWindowInDays: ${var.autonomous_container_database_peer_autonomous_container_database_backup_config_recovery_window_in_days}
peerAutonomousContainerDatabaseCompartmentId: ${oci_identity_compartment.test_compartment.id}
peerAutonomousVmClusterId: ${oci_database_autonomous_vm_cluster.test_autonomous_vm_cluster.id}
peerDbUniqueName: ${var.autonomous_container_database_peer_db_unique_name}
serviceLevelAgreementType: ${var.autonomous_container_database_service_level_agreement_type}
vaultId: ${oci_kms_vault.test_vault.id}
versionPreference: ${var.autonomous_container_database_version_preference}
standbyMaintenanceBufferInDays: ${var.autonomous_container_database_standby_maintenance_buffer_in_days}
Create AutonomousContainerDatabase Resource
new AutonomousContainerDatabase(name: string, args: AutonomousContainerDatabaseArgs, opts?: CustomResourceOptions);@overload
def AutonomousContainerDatabase(resource_name: str,
opts: Optional[ResourceOptions] = None,
autonomous_exadata_infrastructure_id: Optional[str] = None,
autonomous_vm_cluster_id: Optional[str] = None,
backup_config: Optional[_database.AutonomousContainerDatabaseBackupConfigArgs] = None,
cloud_autonomous_vm_cluster_id: Optional[str] = None,
compartment_id: Optional[str] = None,
db_name: Optional[str] = None,
db_unique_name: Optional[str] = None,
db_version: Optional[str] = None,
defined_tags: Optional[Mapping[str, Any]] = None,
display_name: Optional[str] = None,
fast_start_fail_over_lag_limit_in_seconds: Optional[int] = None,
freeform_tags: Optional[Mapping[str, Any]] = None,
is_automatic_failover_enabled: Optional[bool] = None,
key_store_id: Optional[str] = None,
kms_key_id: Optional[str] = None,
maintenance_window_details: Optional[_database.AutonomousContainerDatabaseMaintenanceWindowDetailsArgs] = None,
patch_model: Optional[str] = None,
peer_autonomous_container_database_backup_config: Optional[_database.AutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigArgs] = None,
peer_autonomous_container_database_compartment_id: Optional[str] = None,
peer_autonomous_container_database_display_name: Optional[str] = None,
peer_autonomous_exadata_infrastructure_id: 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,
rotate_key_trigger: Optional[bool] = None,
service_level_agreement_type: Optional[str] = None,
standby_maintenance_buffer_in_days: Optional[int] = None,
vault_id: Optional[str] = None,
version_preference: Optional[str] = None)
@overload
def AutonomousContainerDatabase(resource_name: str,
args: AutonomousContainerDatabaseArgs,
opts: Optional[ResourceOptions] = None)func NewAutonomousContainerDatabase(ctx *Context, name string, args AutonomousContainerDatabaseArgs, opts ...ResourceOption) (*AutonomousContainerDatabase, error)public AutonomousContainerDatabase(string name, AutonomousContainerDatabaseArgs args, CustomResourceOptions? opts = null)
public AutonomousContainerDatabase(String name, AutonomousContainerDatabaseArgs args)
public AutonomousContainerDatabase(String name, AutonomousContainerDatabaseArgs args, CustomResourceOptions options)
type: oci:Database:AutonomousContainerDatabase
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args AutonomousContainerDatabaseArgs
- 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 AutonomousContainerDatabaseArgs
- 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 AutonomousContainerDatabaseArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args AutonomousContainerDatabaseArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args AutonomousContainerDatabaseArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
AutonomousContainerDatabase Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The AutonomousContainerDatabase resource accepts the following input properties:
- Display
Name string (Updatable) The display name for the Autonomous Container Database.
- Patch
Model string (Updatable) Database Patch model preference.
- Autonomous
Exadata stringInfrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
cloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- Autonomous
Vm stringCluster Id The OCID of the Autonomous VM Cluster.
- Backup
Config AutonomousContainer Database Backup Config Args (Updatable) Backup options for the Autonomous Container Database.
- Cloud
Autonomous stringVm Cluster Id The OCID of the Cloud Autonomous VM Cluster.
- Compartment
Id string (Updatable) The OCID of the compartment containing the Autonomous Container Database.
- Db
Name string The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- Db
Unique stringName - Db
Version string The base version for the Autonomous Container Database.
- Dictionary<string, object>
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- Fast
Start intFail Over Lag Limit In Seconds The lag time for my preference based on data loss tolerance in seconds.
- Dictionary<string, object>
(Updatable) 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"}- Is
Automatic boolFailover Enabled Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association. Input DataType: boolean. Example : is_automatic_failover_enabled = true.
- Key
Store stringId The OCID of the key store.
- Kms
Key stringId The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- Maintenance
Window AutonomousDetails Container Database Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Peer
Autonomous AutonomousContainer Database Backup Config Container Database Peer Autonomous Container Database Backup Config Args - Peer
Autonomous stringContainer Database Compartment Id The OCID of the compartment where the standby Autonomous Container Database will be created.
- Peer
Autonomous stringContainer Database Display Name The display name for the peer Autonomous Container Database.
- Peer
Autonomous stringExadata Infrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
peerCloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- Peer
Autonomous stringVm Cluster Id The OCID of the peer Autonomous VM cluster for Autonomous Data Guard. Required to enable Data Guard.
- Peer
Cloud stringAutonomous Vm Cluster Id The OCID of the peer Autonomous Cloud VM Cluster for autonomous dataguard.
- Peer
Db stringUnique Name - Protection
Mode 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.
- Rotate
Key boolTrigger (Updatable) An optional property when flipped triggers rotation of KMS key. It is only applicable on dedicated container databases i.e. where
cloud_autonomous_vm_cluster_idis set.- Service
Level stringAgreement Type The service level agreement type of the Autonomous Container Database. The default is STANDARD. For an autonomous dataguard Autonomous Container Database, the specified Autonomous Exadata Infrastructure must be associated with a remote Autonomous Exadata Infrastructure.
- Standby
Maintenance intBuffer In Days (Updatable) The scheduling detail for the quarterly maintenance window of standby Autonomous Container Database. This value represents the number of days before the primary database maintenance schedule.
** 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
- Vault
Id string - Version
Preference string (Updatable) The next maintenance version preference.
- Display
Name string (Updatable) The display name for the Autonomous Container Database.
- Patch
Model string (Updatable) Database Patch model preference.
- Autonomous
Exadata stringInfrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
cloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- Autonomous
Vm stringCluster Id The OCID of the Autonomous VM Cluster.
- Backup
Config AutonomousContainer Database Backup Config Args (Updatable) Backup options for the Autonomous Container Database.
- Cloud
Autonomous stringVm Cluster Id The OCID of the Cloud Autonomous VM Cluster.
- Compartment
Id string (Updatable) The OCID of the compartment containing the Autonomous Container Database.
- Db
Name string The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- Db
Unique stringName - Db
Version string The base version for the Autonomous Container Database.
- map[string]interface{}
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- Fast
Start intFail Over Lag Limit In Seconds The lag time for my preference based on data loss tolerance in seconds.
- map[string]interface{}
(Updatable) 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"}- Is
Automatic boolFailover Enabled Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association. Input DataType: boolean. Example : is_automatic_failover_enabled = true.
- Key
Store stringId The OCID of the key store.
- Kms
Key stringId The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- Maintenance
Window AutonomousDetails Container Database Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Peer
Autonomous AutonomousContainer Database Backup Config Container Database Peer Autonomous Container Database Backup Config Args - Peer
Autonomous stringContainer Database Compartment Id The OCID of the compartment where the standby Autonomous Container Database will be created.
- Peer
Autonomous stringContainer Database Display Name The display name for the peer Autonomous Container Database.
- Peer
Autonomous stringExadata Infrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
peerCloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- Peer
Autonomous stringVm Cluster Id The OCID of the peer Autonomous VM cluster for Autonomous Data Guard. Required to enable Data Guard.
- Peer
Cloud stringAutonomous Vm Cluster Id The OCID of the peer Autonomous Cloud VM Cluster for autonomous dataguard.
- Peer
Db stringUnique Name - Protection
Mode 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.
- Rotate
Key boolTrigger (Updatable) An optional property when flipped triggers rotation of KMS key. It is only applicable on dedicated container databases i.e. where
cloud_autonomous_vm_cluster_idis set.- Service
Level stringAgreement Type The service level agreement type of the Autonomous Container Database. The default is STANDARD. For an autonomous dataguard Autonomous Container Database, the specified Autonomous Exadata Infrastructure must be associated with a remote Autonomous Exadata Infrastructure.
- Standby
Maintenance intBuffer In Days (Updatable) The scheduling detail for the quarterly maintenance window of standby Autonomous Container Database. This value represents the number of days before the primary database maintenance schedule.
** 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
- Vault
Id string - Version
Preference string (Updatable) The next maintenance version preference.
- display
Name String (Updatable) The display name for the Autonomous Container Database.
- patch
Model String (Updatable) Database Patch model preference.
- autonomous
Exadata StringInfrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
cloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- autonomous
Vm StringCluster Id The OCID of the Autonomous VM Cluster.
- backup
Config AutonomousContainer Backup Config Args (Updatable) Backup options for the Autonomous Container Database.
- cloud
Autonomous StringVm Cluster Id The OCID of the Cloud Autonomous VM Cluster.
- compartment
Id String (Updatable) The OCID of the compartment containing the Autonomous Container Database.
- db
Name String The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- db
Unique StringName - db
Version String The base version for the Autonomous Container Database.
- Map<String,Object>
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- fast
Start IntegerFail Over Lag Limit In Seconds The lag time for my preference based on data loss tolerance in seconds.
- Map<String,Object>
(Updatable) 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"}- is
Automatic BooleanFailover Enabled Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association. Input DataType: boolean. Example : is_automatic_failover_enabled = true.
- key
Store StringId The OCID of the key store.
- kms
Key StringId The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- maintenance
Window AutonomousDetails Container Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- peer
Autonomous AutonomousContainer Database Backup Config Container Peer Autonomous Container Backup Config Args - peer
Autonomous StringContainer Database Compartment Id The OCID of the compartment where the standby Autonomous Container Database will be created.
- peer
Autonomous StringContainer Database Display Name The display name for the peer Autonomous Container Database.
- peer
Autonomous StringExadata Infrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
peerCloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- peer
Autonomous StringVm Cluster Id The OCID of the peer Autonomous VM cluster for Autonomous Data Guard. Required to enable Data Guard.
- peer
Cloud StringAutonomous Vm Cluster Id The OCID of the peer Autonomous Cloud VM Cluster for autonomous dataguard.
- peer
Db StringUnique Name - protection
Mode 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.
- rotate
Key BooleanTrigger (Updatable) An optional property when flipped triggers rotation of KMS key. It is only applicable on dedicated container databases i.e. where
cloud_autonomous_vm_cluster_idis set.- service
Level StringAgreement Type The service level agreement type of the Autonomous Container Database. The default is STANDARD. For an autonomous dataguard Autonomous Container Database, the specified Autonomous Exadata Infrastructure must be associated with a remote Autonomous Exadata Infrastructure.
- standby
Maintenance IntegerBuffer In Days (Updatable) The scheduling detail for the quarterly maintenance window of standby Autonomous Container Database. This value represents the number of days before the primary database maintenance schedule.
** 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
- vault
Id String - version
Preference String (Updatable) The next maintenance version preference.
- display
Name string (Updatable) The display name for the Autonomous Container Database.
- patch
Model string (Updatable) Database Patch model preference.
- autonomous
Exadata stringInfrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
cloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- autonomous
Vm stringCluster Id The OCID of the Autonomous VM Cluster.
- backup
Config AutonomousContainer Database Backup Config Args (Updatable) Backup options for the Autonomous Container Database.
- cloud
Autonomous stringVm Cluster Id The OCID of the Cloud Autonomous VM Cluster.
- compartment
Id string (Updatable) The OCID of the compartment containing the Autonomous Container Database.
- db
Name string The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- db
Unique stringName - db
Version string The base version for the Autonomous Container Database.
- {[key: string]: any}
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- fast
Start numberFail Over Lag Limit In Seconds The lag time for my preference based on data loss tolerance in seconds.
- {[key: string]: any}
(Updatable) 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"}- is
Automatic booleanFailover Enabled Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association. Input DataType: boolean. Example : is_automatic_failover_enabled = true.
- key
Store stringId The OCID of the key store.
- kms
Key stringId The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- maintenance
Window AutonomousDetails Container Database Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- peer
Autonomous AutonomousContainer Database Backup Config Container Database Peer Autonomous Container Database Backup Config Args - peer
Autonomous stringContainer Database Compartment Id The OCID of the compartment where the standby Autonomous Container Database will be created.
- peer
Autonomous stringContainer Database Display Name The display name for the peer Autonomous Container Database.
- peer
Autonomous stringExadata Infrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
peerCloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- peer
Autonomous stringVm Cluster Id The OCID of the peer Autonomous VM cluster for Autonomous Data Guard. Required to enable Data Guard.
- peer
Cloud stringAutonomous Vm Cluster Id The OCID of the peer Autonomous Cloud VM Cluster for autonomous dataguard.
- peer
Db stringUnique Name - protection
Mode 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.
- rotate
Key booleanTrigger (Updatable) An optional property when flipped triggers rotation of KMS key. It is only applicable on dedicated container databases i.e. where
cloud_autonomous_vm_cluster_idis set.- service
Level stringAgreement Type The service level agreement type of the Autonomous Container Database. The default is STANDARD. For an autonomous dataguard Autonomous Container Database, the specified Autonomous Exadata Infrastructure must be associated with a remote Autonomous Exadata Infrastructure.
- standby
Maintenance numberBuffer In Days (Updatable) The scheduling detail for the quarterly maintenance window of standby Autonomous Container Database. This value represents the number of days before the primary database maintenance schedule.
** 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
- vault
Id string - version
Preference string (Updatable) The next maintenance version preference.
- display_
name str (Updatable) The display name for the Autonomous Container Database.
- patch_
model str (Updatable) Database Patch model preference.
- autonomous_
exadata_ strinfrastructure_ id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
cloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- autonomous_
vm_ strcluster_ id The OCID of the Autonomous VM Cluster.
- backup_
config AutonomousContainer Database Backup Config Args (Updatable) Backup options for the Autonomous Container Database.
- cloud_
autonomous_ strvm_ cluster_ id The OCID of the Cloud Autonomous VM Cluster.
- compartment_
id str (Updatable) The OCID of the compartment containing the Autonomous Container Database.
- db_
name str The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- db_
unique_ strname - db_
version str The base version for the Autonomous Container Database.
- Mapping[str, Any]
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- fast_
start_ intfail_ over_ lag_ limit_ in_ seconds The lag time for my preference based on data loss tolerance in seconds.
- Mapping[str, Any]
(Updatable) 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"}- is_
automatic_ boolfailover_ enabled Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association. Input DataType: boolean. Example : is_automatic_failover_enabled = true.
- key_
store_ strid The OCID of the key store.
- kms_
key_ strid The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- maintenance_
window_ Autonomousdetails Container Database Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- peer_
autonomous_ Autonomouscontainer_ database_ backup_ config Container Database Peer Autonomous Container Database Backup Config Args - 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_ strexadata_ infrastructure_ id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
peerCloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- peer_
autonomous_ strvm_ cluster_ id The OCID of the peer Autonomous VM cluster for Autonomous Data Guard. Required to enable Data Guard.
- peer_
cloud_ strautonomous_ vm_ cluster_ id The OCID of the peer Autonomous Cloud VM Cluster for autonomous dataguard.
- peer_
db_ strunique_ name - 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.
- rotate_
key_ booltrigger (Updatable) An optional property when flipped triggers rotation of KMS key. It is only applicable on dedicated container databases i.e. where
cloud_autonomous_vm_cluster_idis set.- service_
level_ stragreement_ type The service level agreement type of the Autonomous Container Database. The default is STANDARD. For an autonomous dataguard Autonomous Container Database, the specified Autonomous Exadata Infrastructure must be associated with a remote Autonomous Exadata Infrastructure.
- standby_
maintenance_ intbuffer_ in_ days (Updatable) The scheduling detail for the quarterly maintenance window of standby Autonomous Container Database. This value represents the number of days before the primary database maintenance schedule.
** 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
- vault_
id str - version_
preference str (Updatable) The next maintenance version preference.
- display
Name String (Updatable) The display name for the Autonomous Container Database.
- patch
Model String (Updatable) Database Patch model preference.
- autonomous
Exadata StringInfrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
cloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- autonomous
Vm StringCluster Id The OCID of the Autonomous VM Cluster.
- backup
Config Property Map (Updatable) Backup options for the Autonomous Container Database.
- cloud
Autonomous StringVm Cluster Id The OCID of the Cloud Autonomous VM Cluster.
- compartment
Id String (Updatable) The OCID of the compartment containing the Autonomous Container Database.
- db
Name String The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- db
Unique StringName - db
Version String The base version for the Autonomous Container Database.
- Map<Any>
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- fast
Start NumberFail Over Lag Limit In Seconds The lag time for my preference based on data loss tolerance in seconds.
- Map<Any>
(Updatable) 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"}- is
Automatic BooleanFailover Enabled Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association. Input DataType: boolean. Example : is_automatic_failover_enabled = true.
- key
Store StringId The OCID of the key store.
- kms
Key StringId The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- maintenance
Window Property MapDetails (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- peer
Autonomous Property MapContainer Database Backup Config - peer
Autonomous StringContainer Database Compartment Id The OCID of the compartment where the standby Autonomous Container Database will be created.
- peer
Autonomous StringContainer Database Display Name The display name for the peer Autonomous Container Database.
- peer
Autonomous StringExadata Infrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
peerCloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- peer
Autonomous StringVm Cluster Id The OCID of the peer Autonomous VM cluster for Autonomous Data Guard. Required to enable Data Guard.
- peer
Cloud StringAutonomous Vm Cluster Id The OCID of the peer Autonomous Cloud VM Cluster for autonomous dataguard.
- peer
Db StringUnique Name - protection
Mode 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.
- rotate
Key BooleanTrigger (Updatable) An optional property when flipped triggers rotation of KMS key. It is only applicable on dedicated container databases i.e. where
cloud_autonomous_vm_cluster_idis set.- service
Level StringAgreement Type The service level agreement type of the Autonomous Container Database. The default is STANDARD. For an autonomous dataguard Autonomous Container Database, the specified Autonomous Exadata Infrastructure must be associated with a remote Autonomous Exadata Infrastructure.
- standby
Maintenance NumberBuffer In Days (Updatable) The scheduling detail for the quarterly maintenance window of standby Autonomous Container Database. This value represents the number of days before the primary database maintenance schedule.
** 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
- vault
Id String - version
Preference String (Updatable) The next maintenance version preference.
Outputs
All input properties are implicitly available as output properties. Additionally, the AutonomousContainerDatabase resource produces the following output properties:
- Availability
Domain string The availability domain of the Autonomous Container Database
- Available
Cpus double Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Compute
Model string The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Id string
The provider-assigned unique ID for this managed resource.
- Infrastructure
Type string The infrastructure type this resource belongs to.
- Key
History List<AutonomousEntries Container Database Key History Entry> Key History Entry.
- Key
Store stringWallet Name The wallet name for Oracle Key Vault.
- Last
Maintenance stringRun Id The OCID of the last maintenance run.
- Lifecycle
Details string Additional information about the current lifecycle state.
- Maintenance
Windows List<AutonomousContainer Database Maintenance Window> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Memory
Per intOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.
- Next
Maintenance stringRun Id The OCID of the next maintenance run.
- Patch
Id string The OCID of the last patch applied on the system.
- Provisionable
Cpuses List<double> An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Reclaimable
Cpus double For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Role string
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- State string
The current state of the Autonomous Container Database.
- Time
Created string The date and time the Autonomous Container Database was created.
- Time
Snapshot stringStandby Revert The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- Total
Cpus int The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Availability
Domain string The availability domain of the Autonomous Container Database
- Available
Cpus float64 Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Compute
Model string The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Id string
The provider-assigned unique ID for this managed resource.
- Infrastructure
Type string The infrastructure type this resource belongs to.
- Key
History []AutonomousEntries Container Database Key History Entry Key History Entry.
- Key
Store stringWallet Name The wallet name for Oracle Key Vault.
- Last
Maintenance stringRun Id The OCID of the last maintenance run.
- Lifecycle
Details string Additional information about the current lifecycle state.
- Maintenance
Windows []AutonomousContainer Database Maintenance Window The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Memory
Per intOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.
- Next
Maintenance stringRun Id The OCID of the next maintenance run.
- Patch
Id string The OCID of the last patch applied on the system.
- Provisionable
Cpuses []float64 An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Reclaimable
Cpus float64 For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Role string
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- State string
The current state of the Autonomous Container Database.
- Time
Created string The date and time the Autonomous Container Database was created.
- Time
Snapshot stringStandby Revert The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- Total
Cpus int The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- availability
Domain String The availability domain of the Autonomous Container Database
- available
Cpus Double Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- compute
Model String The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- id String
The provider-assigned unique ID for this managed resource.
- infrastructure
Type String The infrastructure type this resource belongs to.
- key
History List<AutonomousEntries Container Key History Entry> Key History Entry.
- key
Store StringWallet Name The wallet name for Oracle Key Vault.
- last
Maintenance StringRun Id The OCID of the last maintenance run.
- lifecycle
Details String Additional information about the current lifecycle state.
- maintenance
Windows List<AutonomousContainer Maintenance Window> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per IntegerOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.
- next
Maintenance StringRun Id The OCID of the next maintenance run.
- patch
Id String The OCID of the last patch applied on the system.
- provisionable
Cpuses List<Double> An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- reclaimable
Cpus Double For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- role String
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- state String
The current state of the Autonomous Container Database.
- time
Created String The date and time the Autonomous Container Database was created.
- time
Snapshot StringStandby Revert The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- total
Cpus Integer The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- availability
Domain string The availability domain of the Autonomous Container Database
- available
Cpus number Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- compute
Model string The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- id string
The provider-assigned unique ID for this managed resource.
- infrastructure
Type string The infrastructure type this resource belongs to.
- key
History AutonomousEntries Container Database Key History Entry[] Key History Entry.
- key
Store stringWallet Name The wallet name for Oracle Key Vault.
- last
Maintenance stringRun Id The OCID of the last maintenance run.
- lifecycle
Details string Additional information about the current lifecycle state.
- maintenance
Windows AutonomousContainer Database Maintenance Window[] The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per numberOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.
- next
Maintenance stringRun Id The OCID of the next maintenance run.
- patch
Id string The OCID of the last patch applied on the system.
- provisionable
Cpuses number[] An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- reclaimable
Cpus number For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- role string
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- state string
The current state of the Autonomous Container Database.
- time
Created string The date and time the Autonomous Container Database was created.
- time
Snapshot stringStandby Revert The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- total
Cpus number The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- availability_
domain str The availability domain of the Autonomous Container Database
- available_
cpus float Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- compute_
model str The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- id str
The provider-assigned unique ID for this managed resource.
- infrastructure_
type str The infrastructure type this resource belongs to.
- key_
history_ Autonomousentries Container Database Key History Entry] Key History Entry.
- key_
store_ strwallet_ name The wallet name for Oracle Key Vault.
- last_
maintenance_ strrun_ id The OCID of the last maintenance run.
- lifecycle_
details str Additional information about the current lifecycle state.
- maintenance_
windows AutonomousContainer Database Maintenance Window] The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory_
per_ intoracle_ compute_ unit_ in_ gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.
- next_
maintenance_ strrun_ id The OCID of the next maintenance run.
- patch_
id str The OCID of the last patch applied on the system.
- provisionable_
cpuses Sequence[float] An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- reclaimable_
cpus float For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- role str
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- state str
The current state of the Autonomous Container Database.
- time_
created str The date and time the Autonomous Container Database was created.
- time_
snapshot_ strstandby_ revert The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- total_
cpus int The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- availability
Domain String The availability domain of the Autonomous Container Database
- available
Cpus Number Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- compute
Model String The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- id String
The provider-assigned unique ID for this managed resource.
- infrastructure
Type String The infrastructure type this resource belongs to.
- key
History List<Property Map>Entries Key History Entry.
- key
Store StringWallet Name The wallet name for Oracle Key Vault.
- last
Maintenance StringRun Id The OCID of the last maintenance run.
- lifecycle
Details String Additional information about the current lifecycle state.
- maintenance
Windows List<Property Map> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per NumberOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.
- next
Maintenance StringRun Id The OCID of the next maintenance run.
- patch
Id String The OCID of the last patch applied on the system.
- provisionable
Cpuses List<Number> An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- reclaimable
Cpus Number For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- role String
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- state String
The current state of the Autonomous Container Database.
- time
Created String The date and time the Autonomous Container Database was created.
- time
Snapshot StringStandby Revert The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- total
Cpus Number The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
Look up Existing AutonomousContainerDatabase Resource
Get an existing AutonomousContainerDatabase 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?: AutonomousContainerDatabaseState, opts?: CustomResourceOptions): AutonomousContainerDatabase@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = 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_config: Optional[_database.AutonomousContainerDatabaseBackupConfigArgs] = None,
cloud_autonomous_vm_cluster_id: Optional[str] = None,
compartment_id: Optional[str] = None,
compute_model: Optional[str] = None,
db_name: Optional[str] = None,
db_unique_name: Optional[str] = None,
db_version: Optional[str] = None,
defined_tags: Optional[Mapping[str, Any]] = None,
display_name: Optional[str] = None,
fast_start_fail_over_lag_limit_in_seconds: Optional[int] = None,
freeform_tags: Optional[Mapping[str, Any]] = None,
infrastructure_type: Optional[str] = None,
is_automatic_failover_enabled: Optional[bool] = None,
key_history_entries: Optional[Sequence[_database.AutonomousContainerDatabaseKeyHistoryEntryArgs]] = None,
key_store_id: Optional[str] = None,
key_store_wallet_name: Optional[str] = None,
kms_key_id: Optional[str] = None,
last_maintenance_run_id: Optional[str] = None,
lifecycle_details: Optional[str] = None,
maintenance_window_details: Optional[_database.AutonomousContainerDatabaseMaintenanceWindowDetailsArgs] = None,
maintenance_windows: Optional[Sequence[_database.AutonomousContainerDatabaseMaintenanceWindowArgs]] = None,
memory_per_oracle_compute_unit_in_gbs: Optional[int] = 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.AutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigArgs] = None,
peer_autonomous_container_database_compartment_id: Optional[str] = None,
peer_autonomous_container_database_display_name: Optional[str] = None,
peer_autonomous_exadata_infrastructure_id: 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,
reclaimable_cpus: Optional[float] = None,
role: Optional[str] = None,
rotate_key_trigger: Optional[bool] = 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_snapshot_standby_revert: Optional[str] = None,
total_cpus: Optional[int] = None,
vault_id: Optional[str] = None,
version_preference: Optional[str] = None) -> AutonomousContainerDatabasefunc GetAutonomousContainerDatabase(ctx *Context, name string, id IDInput, state *AutonomousContainerDatabaseState, opts ...ResourceOption) (*AutonomousContainerDatabase, error)public static AutonomousContainerDatabase Get(string name, Input<string> id, AutonomousContainerDatabaseState? state, CustomResourceOptions? opts = null)public static AutonomousContainerDatabase get(String name, Output<String> id, AutonomousContainerDatabaseState state, CustomResourceOptions options)Resource lookup is not supported in YAML- 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.
- Autonomous
Exadata stringInfrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
cloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- Autonomous
Vm stringCluster Id The OCID of the Autonomous VM Cluster.
- Availability
Domain string The availability domain of the Autonomous Container Database
- Available
Cpus double Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Backup
Config AutonomousContainer Database Backup Config Args (Updatable) Backup options for the Autonomous Container Database.
- Cloud
Autonomous stringVm Cluster Id The OCID of the Cloud Autonomous VM Cluster.
- Compartment
Id string (Updatable) The OCID of the compartment containing the Autonomous Container Database.
- Compute
Model string The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Db
Name string The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- Db
Unique stringName - Db
Version string The base version for the Autonomous Container Database.
- Dictionary<string, object>
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- Display
Name string (Updatable) The display name for 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.
- Dictionary<string, object>
(Updatable) 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 string The infrastructure type this resource belongs to.
- Is
Automatic boolFailover Enabled Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association. Input DataType: boolean. Example : is_automatic_failover_enabled = true.
- Key
History List<AutonomousEntries Container Database Key History Entry Args> Key History Entry.
- Key
Store stringId The OCID of the key store.
- Key
Store stringWallet Name The wallet name for Oracle Key Vault.
- Kms
Key stringId The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- Last
Maintenance stringRun Id The OCID of the last maintenance run.
- Lifecycle
Details string Additional information about the current lifecycle state.
- Maintenance
Window AutonomousDetails Container Database Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Maintenance
Windows List<AutonomousContainer Database 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 OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.
- Next
Maintenance stringRun Id The OCID of the next maintenance run.
- Patch
Id string The OCID of the last patch applied on the system.
- Patch
Model string (Updatable) Database Patch model preference.
- Peer
Autonomous AutonomousContainer Database Backup Config Container Database Peer Autonomous Container Database Backup Config Args - Peer
Autonomous stringContainer Database Compartment Id The OCID of the compartment where the standby Autonomous Container Database will be created.
- Peer
Autonomous stringContainer Database Display Name The display name for the peer Autonomous Container Database.
- Peer
Autonomous stringExadata Infrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
peerCloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- Peer
Autonomous stringVm Cluster Id The OCID of the peer Autonomous VM cluster for Autonomous Data Guard. Required to enable Data Guard.
- Peer
Cloud stringAutonomous Vm Cluster Id The OCID of the peer Autonomous Cloud VM Cluster for autonomous dataguard.
- Peer
Db stringUnique Name - Protection
Mode 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.
- Provisionable
Cpuses List<double> An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Reclaimable
Cpus double For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Role string
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- Rotate
Key boolTrigger (Updatable) An optional property when flipped triggers rotation of KMS key. It is only applicable on dedicated container databases i.e. where
cloud_autonomous_vm_cluster_idis set.- Service
Level stringAgreement Type The service level agreement type of the Autonomous Container Database. The default is STANDARD. For an autonomous dataguard Autonomous Container Database, the specified Autonomous Exadata Infrastructure must be associated with a remote Autonomous Exadata Infrastructure.
- Standby
Maintenance intBuffer In Days (Updatable) The scheduling detail for the quarterly maintenance window of standby Autonomous Container Database. This value represents the number of days before the primary database maintenance schedule.
** 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.
- Time
Created string The date and time the Autonomous Container Database was created.
- Time
Snapshot stringStandby Revert The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- Total
Cpus int The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Vault
Id string - Version
Preference string (Updatable) The next maintenance version preference.
- Autonomous
Exadata stringInfrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
cloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- Autonomous
Vm stringCluster Id The OCID of the Autonomous VM Cluster.
- Availability
Domain string The availability domain of the Autonomous Container Database
- Available
Cpus float64 Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Backup
Config AutonomousContainer Database Backup Config Args (Updatable) Backup options for the Autonomous Container Database.
- Cloud
Autonomous stringVm Cluster Id The OCID of the Cloud Autonomous VM Cluster.
- Compartment
Id string (Updatable) The OCID of the compartment containing the Autonomous Container Database.
- Compute
Model string The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Db
Name string The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- Db
Unique stringName - Db
Version string The base version for the Autonomous Container Database.
- map[string]interface{}
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- Display
Name string (Updatable) The display name for 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.
- map[string]interface{}
(Updatable) 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 string The infrastructure type this resource belongs to.
- Is
Automatic boolFailover Enabled Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association. Input DataType: boolean. Example : is_automatic_failover_enabled = true.
- Key
History []AutonomousEntries Container Database Key History Entry Args Key History Entry.
- Key
Store stringId The OCID of the key store.
- Key
Store stringWallet Name The wallet name for Oracle Key Vault.
- Kms
Key stringId The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- Last
Maintenance stringRun Id The OCID of the last maintenance run.
- Lifecycle
Details string Additional information about the current lifecycle state.
- Maintenance
Window AutonomousDetails Container Database Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Maintenance
Windows []AutonomousContainer Database 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 OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.
- Next
Maintenance stringRun Id The OCID of the next maintenance run.
- Patch
Id string The OCID of the last patch applied on the system.
- Patch
Model string (Updatable) Database Patch model preference.
- Peer
Autonomous AutonomousContainer Database Backup Config Container Database Peer Autonomous Container Database Backup Config Args - Peer
Autonomous stringContainer Database Compartment Id The OCID of the compartment where the standby Autonomous Container Database will be created.
- Peer
Autonomous stringContainer Database Display Name The display name for the peer Autonomous Container Database.
- Peer
Autonomous stringExadata Infrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
peerCloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- Peer
Autonomous stringVm Cluster Id The OCID of the peer Autonomous VM cluster for Autonomous Data Guard. Required to enable Data Guard.
- Peer
Cloud stringAutonomous Vm Cluster Id The OCID of the peer Autonomous Cloud VM Cluster for autonomous dataguard.
- Peer
Db stringUnique Name - Protection
Mode 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.
- Provisionable
Cpuses []float64 An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Reclaimable
Cpus float64 For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Role string
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- Rotate
Key boolTrigger (Updatable) An optional property when flipped triggers rotation of KMS key. It is only applicable on dedicated container databases i.e. where
cloud_autonomous_vm_cluster_idis set.- Service
Level stringAgreement Type The service level agreement type of the Autonomous Container Database. The default is STANDARD. For an autonomous dataguard Autonomous Container Database, the specified Autonomous Exadata Infrastructure must be associated with a remote Autonomous Exadata Infrastructure.
- Standby
Maintenance intBuffer In Days (Updatable) The scheduling detail for the quarterly maintenance window of standby Autonomous Container Database. This value represents the number of days before the primary database maintenance schedule.
** 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.
- Time
Created string The date and time the Autonomous Container Database was created.
- Time
Snapshot stringStandby Revert The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- Total
Cpus int The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Vault
Id string - Version
Preference string (Updatable) The next maintenance version preference.
- autonomous
Exadata StringInfrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
cloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- autonomous
Vm StringCluster Id The OCID of the Autonomous VM Cluster.
- availability
Domain String The availability domain of the Autonomous Container Database
- available
Cpus Double Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- backup
Config AutonomousContainer Backup Config Args (Updatable) Backup options for the Autonomous Container Database.
- cloud
Autonomous StringVm Cluster Id The OCID of the Cloud Autonomous VM Cluster.
- compartment
Id String (Updatable) The OCID of the compartment containing the Autonomous Container Database.
- compute
Model String The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- db
Name String The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- db
Unique StringName - db
Version String The base version for the Autonomous Container Database.
- Map<String,Object>
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- display
Name String (Updatable) The display name for the Autonomous Container Database.
- fast
Start IntegerFail Over Lag Limit In Seconds The lag time for my preference based on data loss tolerance in seconds.
- Map<String,Object>
(Updatable) 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 String The infrastructure type this resource belongs to.
- is
Automatic BooleanFailover Enabled Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association. Input DataType: boolean. Example : is_automatic_failover_enabled = true.
- key
History List<AutonomousEntries Container Key History Entry Args> Key History Entry.
- key
Store StringId The OCID of the key store.
- key
Store StringWallet Name The wallet name for Oracle Key Vault.
- kms
Key StringId The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- last
Maintenance StringRun Id The OCID of the last maintenance run.
- lifecycle
Details String Additional information about the current lifecycle state.
- maintenance
Window AutonomousDetails Container Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maintenance
Windows List<AutonomousContainer Maintenance Window Args> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per IntegerOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.
- next
Maintenance StringRun Id The OCID of the next maintenance run.
- patch
Id String The OCID of the last patch applied on the system.
- patch
Model String (Updatable) Database Patch model preference.
- peer
Autonomous AutonomousContainer Database Backup Config Container Peer Autonomous Container Backup Config Args - peer
Autonomous StringContainer Database Compartment Id The OCID of the compartment where the standby Autonomous Container Database will be created.
- peer
Autonomous StringContainer Database Display Name The display name for the peer Autonomous Container Database.
- peer
Autonomous StringExadata Infrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
peerCloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- peer
Autonomous StringVm Cluster Id The OCID of the peer Autonomous VM cluster for Autonomous Data Guard. Required to enable Data Guard.
- peer
Cloud StringAutonomous Vm Cluster Id The OCID of the peer Autonomous Cloud VM Cluster for autonomous dataguard.
- peer
Db StringUnique Name - protection
Mode 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.
- provisionable
Cpuses List<Double> An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- reclaimable
Cpus Double For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- role String
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- rotate
Key BooleanTrigger (Updatable) An optional property when flipped triggers rotation of KMS key. It is only applicable on dedicated container databases i.e. where
cloud_autonomous_vm_cluster_idis set.- service
Level StringAgreement Type The service level agreement type of the Autonomous Container Database. The default is STANDARD. For an autonomous dataguard Autonomous Container Database, the specified Autonomous Exadata Infrastructure must be associated with a remote Autonomous Exadata Infrastructure.
- standby
Maintenance IntegerBuffer In Days (Updatable) The scheduling detail for the quarterly maintenance window of standby Autonomous Container Database. This value represents the number of days before the primary database maintenance schedule.
** 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.
- time
Created String The date and time the Autonomous Container Database was created.
- time
Snapshot StringStandby Revert The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- total
Cpus Integer The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- vault
Id String - version
Preference String (Updatable) The next maintenance version preference.
- autonomous
Exadata stringInfrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
cloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- autonomous
Vm stringCluster Id The OCID of the Autonomous VM Cluster.
- availability
Domain string The availability domain of the Autonomous Container Database
- available
Cpus number Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- backup
Config AutonomousContainer Database Backup Config Args (Updatable) Backup options for the Autonomous Container Database.
- cloud
Autonomous stringVm Cluster Id The OCID of the Cloud Autonomous VM Cluster.
- compartment
Id string (Updatable) The OCID of the compartment containing the Autonomous Container Database.
- compute
Model string The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- db
Name string The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- db
Unique stringName - db
Version string The base version for the Autonomous Container Database.
- {[key: string]: any}
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- display
Name string (Updatable) The display name for the Autonomous Container Database.
- fast
Start numberFail Over Lag Limit In Seconds The lag time for my preference based on data loss tolerance in seconds.
- {[key: string]: any}
(Updatable) 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 string The infrastructure type this resource belongs to.
- is
Automatic booleanFailover Enabled Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association. Input DataType: boolean. Example : is_automatic_failover_enabled = true.
- key
History AutonomousEntries Container Database Key History Entry Args[] Key History Entry.
- key
Store stringId The OCID of the key store.
- key
Store stringWallet Name The wallet name for Oracle Key Vault.
- kms
Key stringId The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- last
Maintenance stringRun Id The OCID of the last maintenance run.
- lifecycle
Details string Additional information about the current lifecycle state.
- maintenance
Window AutonomousDetails Container Database Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maintenance
Windows AutonomousContainer Database Maintenance Window Args[] The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per numberOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.
- next
Maintenance stringRun Id The OCID of the next maintenance run.
- patch
Id string The OCID of the last patch applied on the system.
- patch
Model string (Updatable) Database Patch model preference.
- peer
Autonomous AutonomousContainer Database Backup Config Container Database Peer Autonomous Container Database Backup Config Args - peer
Autonomous stringContainer Database Compartment Id The OCID of the compartment where the standby Autonomous Container Database will be created.
- peer
Autonomous stringContainer Database Display Name The display name for the peer Autonomous Container Database.
- peer
Autonomous stringExadata Infrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
peerCloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- peer
Autonomous stringVm Cluster Id The OCID of the peer Autonomous VM cluster for Autonomous Data Guard. Required to enable Data Guard.
- peer
Cloud stringAutonomous Vm Cluster Id The OCID of the peer Autonomous Cloud VM Cluster for autonomous dataguard.
- peer
Db stringUnique Name - protection
Mode 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.
- provisionable
Cpuses number[] An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- reclaimable
Cpus number For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- role string
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- rotate
Key booleanTrigger (Updatable) An optional property when flipped triggers rotation of KMS key. It is only applicable on dedicated container databases i.e. where
cloud_autonomous_vm_cluster_idis set.- service
Level stringAgreement Type The service level agreement type of the Autonomous Container Database. The default is STANDARD. For an autonomous dataguard Autonomous Container Database, the specified Autonomous Exadata Infrastructure must be associated with a remote Autonomous Exadata Infrastructure.
- standby
Maintenance numberBuffer In Days (Updatable) The scheduling detail for the quarterly maintenance window of standby Autonomous Container Database. This value represents the number of days before the primary database maintenance schedule.
** 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.
- time
Created string The date and time the Autonomous Container Database was created.
- time
Snapshot stringStandby Revert The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- total
Cpus number The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- vault
Id string - version
Preference string (Updatable) The next maintenance version preference.
- autonomous_
exadata_ strinfrastructure_ id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
cloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- autonomous_
vm_ strcluster_ id The OCID of the Autonomous VM Cluster.
- availability_
domain str The availability domain of the Autonomous Container Database
- available_
cpus float Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- backup_
config AutonomousContainer Database Backup Config Args (Updatable) Backup options for the Autonomous Container Database.
- cloud_
autonomous_ strvm_ cluster_ id The OCID of the Cloud Autonomous VM Cluster.
- compartment_
id str (Updatable) The OCID of the compartment containing the Autonomous Container Database.
- compute_
model str The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- db_
name str The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- db_
unique_ strname - db_
version str The base version for the Autonomous Container Database.
- Mapping[str, Any]
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- display_
name str (Updatable) The display name for 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, Any]
(Updatable) 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. Input DataType: boolean. Example : is_automatic_failover_enabled = true.
- key_
history_ Autonomousentries Container Database Key History Entry Args] Key History Entry.
- key_
store_ strid The OCID of the key store.
- 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.
- last_
maintenance_ strrun_ id The OCID of the last maintenance run.
- lifecycle_
details str Additional information about the current lifecycle state.
- maintenance_
window_ Autonomousdetails Container Database Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maintenance_
windows AutonomousContainer Database 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 OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.
- 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 (Updatable) Database Patch model preference.
- peer_
autonomous_ Autonomouscontainer_ database_ backup_ config Container Database Peer Autonomous Container Database Backup Config Args - 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_ strexadata_ infrastructure_ id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
peerCloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- peer_
autonomous_ strvm_ cluster_ id The OCID of the peer Autonomous VM cluster for Autonomous Data Guard. Required to enable Data Guard.
- peer_
cloud_ strautonomous_ vm_ cluster_ id The OCID of the peer Autonomous Cloud VM Cluster for autonomous dataguard.
- peer_
db_ strunique_ name - 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.\ For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- reclaimable_
cpus float For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- role str
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- rotate_
key_ booltrigger (Updatable) An optional property when flipped triggers rotation of KMS key. It is only applicable on dedicated container databases i.e. where
cloud_autonomous_vm_cluster_idis set.- service_
level_ stragreement_ type The service level agreement type of the Autonomous Container Database. The default is STANDARD. For an autonomous dataguard Autonomous Container Database, the specified Autonomous Exadata Infrastructure must be associated with a remote Autonomous Exadata Infrastructure.
- standby_
maintenance_ intbuffer_ in_ days (Updatable) The scheduling detail for the quarterly maintenance window of standby Autonomous Container Database. This value represents the number of days before the primary database maintenance schedule.
** 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_
snapshot_ strstandby_ revert The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- total_
cpus int The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- vault_
id str - version_
preference str (Updatable) The next maintenance version preference.
- autonomous
Exadata StringInfrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
cloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- autonomous
Vm StringCluster Id The OCID of the Autonomous VM Cluster.
- availability
Domain String The availability domain of the Autonomous Container Database
- available
Cpus Number Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- backup
Config Property Map (Updatable) Backup options for the Autonomous Container Database.
- cloud
Autonomous StringVm Cluster Id The OCID of the Cloud Autonomous VM Cluster.
- compartment
Id String (Updatable) The OCID of the compartment containing the Autonomous Container Database.
- compute
Model String The compute model of the Autonomous VM Cluster. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- db
Name String The Database name for the Autonomous Container Database. The name must be unique within the Cloud Autonomous VM Cluster, starting with an alphabetic character, followed by 1 to 7 alphanumeric characters.
- db
Unique StringName - db
Version String The base version for the Autonomous Container Database.
- Map<Any>
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- display
Name String (Updatable) The display name for the Autonomous Container Database.
- fast
Start NumberFail Over Lag Limit In Seconds The lag time for my preference based on data loss tolerance in seconds.
- Map<Any>
(Updatable) 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 String The infrastructure type this resource belongs to.
- is
Automatic BooleanFailover Enabled Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association. Input DataType: boolean. Example : is_automatic_failover_enabled = true.
- key
History List<Property Map>Entries Key History Entry.
- key
Store StringId The OCID of the key store.
- key
Store StringWallet Name The wallet name for Oracle Key Vault.
- kms
Key StringId The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
- last
Maintenance StringRun Id The OCID of the last maintenance run.
- lifecycle
Details String Additional information about the current lifecycle state.
- maintenance
Window Property MapDetails (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maintenance
Windows List<Property Map> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per NumberOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.See Compute Models for more details.
- next
Maintenance StringRun Id The OCID of the next maintenance run.
- patch
Id String The OCID of the last patch applied on the system.
- patch
Model String (Updatable) Database Patch model preference.
- peer
Autonomous Property MapContainer Database Backup Config - peer
Autonomous StringContainer Database Compartment Id The OCID of the compartment where the standby Autonomous Container Database will be created.
- peer
Autonomous StringContainer Database Display Name The display name for the peer Autonomous Container Database.
- peer
Autonomous StringExadata Infrastructure Id No longer used. This parameter is no longer used for Autonomous Database on dedicated Exadata infrasture. Specify a
peerCloudAutonomousVmClusterIdinstead. Using this parameter will cause the operation to fail.- peer
Autonomous StringVm Cluster Id The OCID of the peer Autonomous VM cluster for Autonomous Data Guard. Required to enable Data Guard.
- peer
Cloud StringAutonomous Vm Cluster Id The OCID of the peer Autonomous Cloud VM Cluster for autonomous dataguard.
- peer
Db StringUnique Name - protection
Mode 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.
- provisionable
Cpuses List<Number> An array of CPU values that can be used to successfully provision a single Autonomous Database.\ For Autonomous Database on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- reclaimable
Cpus Number For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- role String
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- rotate
Key BooleanTrigger (Updatable) An optional property when flipped triggers rotation of KMS key. It is only applicable on dedicated container databases i.e. where
cloud_autonomous_vm_cluster_idis set.- service
Level StringAgreement Type The service level agreement type of the Autonomous Container Database. The default is STANDARD. For an autonomous dataguard Autonomous Container Database, the specified Autonomous Exadata Infrastructure must be associated with a remote Autonomous Exadata Infrastructure.
- standby
Maintenance NumberBuffer In Days (Updatable) The scheduling detail for the quarterly maintenance window of standby Autonomous Container Database. This value represents the number of days before the primary database maintenance schedule.
** 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.
- time
Created String The date and time the Autonomous Container Database was created.
- time
Snapshot StringStandby Revert The date and time the Autonomous Container Database will be reverted to Standby from Snapshot Standby.
- total
Cpus Number The number of CPUs allocated to the Autonomous VM cluster. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- vault
Id String - version
Preference String (Updatable) The next maintenance version preference.
Supporting Types
AutonomousContainerDatabaseBackupConfig
- Backup
Destination AutonomousDetails Container Database Backup Config Backup Destination Details 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.
- Backup
Destination AutonomousDetails Container Database Backup Config Backup Destination Details 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.
- backup
Destination AutonomousDetails Container Backup Config Backup Destination Details Backup destination details.
- recovery
Window IntegerIn Days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
- backup
Destination AutonomousDetails Container Database Backup Config Backup Destination Details Backup destination details.
- recovery
Window numberIn Days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
- backup_
destination_ Autonomousdetails Container Database Backup Config Backup Destination Details 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.
- backup
Destination Property MapDetails Backup destination details.
- recovery
Window NumberIn Days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
AutonomousContainerDatabaseBackupConfigBackupDestinationDetails
- Type string
Type of the database backup destination.
- Id string
The OCID of the backup destination.
- Internet
Proxy string Proxy URL to connect to object store.
- Vpc
Password string For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- Vpc
User string For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- Type string
Type of the database backup destination.
- Id string
The OCID of the backup destination.
- Internet
Proxy string Proxy URL to connect to object store.
- Vpc
Password string For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- Vpc
User string For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- type String
Type of the database backup destination.
- id String
The OCID of the backup destination.
- internet
Proxy String Proxy URL to connect to object store.
- vpc
Password String For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User String For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- type string
Type of the database backup destination.
- id string
The OCID of the backup destination.
- internet
Proxy string Proxy URL to connect to object store.
- vpc
Password string For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User string For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- type str
Type of the database backup destination.
- 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.
- id String
The OCID of the backup destination.
- internet
Proxy String Proxy URL to connect to object store.
- vpc
Password String For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User String For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
AutonomousContainerDatabaseKeyHistoryEntry
- Id string
The OCID of the backup destination.
- Kms
Key stringVersion Id The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation.
- Time
Activated string The date and time the kms key activated.
- Vault
Id string
- Id string
The OCID of the backup destination.
- Kms
Key stringVersion Id The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation.
- Time
Activated string The date and time the kms key activated.
- Vault
Id string
- id String
The OCID of the backup destination.
- kms
Key StringVersion Id The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation.
- time
Activated String The date and time the kms key activated.
- vault
Id String
- id string
The OCID of the backup destination.
- kms
Key stringVersion Id The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation.
- time
Activated string The date and time the kms key activated.
- vault
Id string
- id str
The OCID of the backup destination.
- 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.
- time_
activated str The date and time the kms key activated.
- vault_
id str
- id String
The OCID of the backup destination.
- kms
Key StringVersion Id The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation.
- time
Activated String The date and time the kms key activated.
- vault
Id String
AutonomousContainerDatabaseMaintenanceWindow
- Custom
Action intTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- Days
Of List<AutonomousWeeks Container Database Maintenance Window Days Of Week> (Updatable) Days during the week when maintenance should be performed.
- Hours
Of List<int>Days (Updatable) 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 (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- Is
Monthly boolPatching Enabled (Updatable) If true, enables the monthly patching option.
- Lead
Time intIn Weeks (Updatable) 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<Autonomous
Container Database Maintenance Window Month> (Updatable) Months during the year when maintenance should be performed.
- Patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- Preference string
(Updatable) The maintenance window scheduling preference.
- Weeks
Of List<int>Months (Updatable) 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 (Updatable) 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 []AutonomousWeeks Container Database Maintenance Window Days Of Week (Updatable) Days during the week when maintenance should be performed.
- Hours
Of []intDays (Updatable) 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 (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- Is
Monthly boolPatching Enabled (Updatable) If true, enables the monthly patching option.
- Lead
Time intIn Weeks (Updatable) 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
[]Autonomous
Container Database Maintenance Window Month (Updatable) Months during the year when maintenance should be performed.
- Patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- Preference string
(Updatable) The maintenance window scheduling preference.
- Weeks
Of []intMonths (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action IntegerTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of List<AutonomousWeeks Container Maintenance Window Days Of Week> (Updatable) Days during the week when maintenance should be performed.
- hours
Of List<Integer>Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom BooleanAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled (Updatable) If true, enables the monthly patching option.
- lead
Time IntegerIn Weeks (Updatable) 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<Autonomous
Container Maintenance Window Month> (Updatable) Months during the year when maintenance should be performed.
- patching
Mode String (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- preference String
(Updatable) The maintenance window scheduling preference.
- weeks
Of List<Integer>Months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action numberTimeout In Mins (Updatable) 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 AutonomousWeeks Container Database Maintenance Window Days Of Week[] (Updatable) Days during the week when maintenance should be performed.
- hours
Of number[]Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom booleanAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly booleanPatching Enabled (Updatable) If true, enables the monthly patching option.
- lead
Time numberIn Weeks (Updatable) 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
Autonomous
Container Database Maintenance Window Month[] (Updatable) Months during the year when maintenance should be performed.
- patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- preference string
(Updatable) The maintenance window scheduling preference.
- weeks
Of number[]Months (Updatable) 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 (Updatable) 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_ Autonomousweeks Container Database Maintenance Window Days Of Week] (Updatable) Days during the week when maintenance should be performed.
- hours_
of_ Sequence[int]days (Updatable) 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 (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is_
monthly_ boolpatching_ enabled (Updatable) If true, enables the monthly patching option.
- lead_
time_ intin_ weeks (Updatable) 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
Autonomous
Container Database Maintenance Window Month] (Updatable) Months during the year when maintenance should be performed.
- patching_
mode str (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- preference str
(Updatable) The maintenance window scheduling preference.
- weeks_
of_ Sequence[int]months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action NumberTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of List<Property Map>Weeks (Updatable) Days during the week when maintenance should be performed.
- hours
Of List<Number>Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom BooleanAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled (Updatable) If true, enables the monthly patching option.
- lead
Time NumberIn Weeks (Updatable) 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>
(Updatable) Months during the year when maintenance should be performed.
- patching
Mode String (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- preference String
(Updatable) The maintenance window scheduling preference.
- weeks
Of List<Number>Months (Updatable) 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.
AutonomousContainerDatabaseMaintenanceWindowDaysOfWeek
- Name string
(Updatable) Name of the month of the year.
- Name string
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
- name string
(Updatable) Name of the month of the year.
- name str
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
AutonomousContainerDatabaseMaintenanceWindowDetails
- Custom
Action intTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- Days
Of List<AutonomousWeeks Container Database Maintenance Window Details Days Of Week> (Updatable) Days during the week when maintenance should be performed.
- Hours
Of List<int>Days (Updatable) 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 (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- Is
Monthly boolPatching Enabled (Updatable) If true, enables the monthly patching option.
- Lead
Time intIn Weeks (Updatable) 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<Autonomous
Container Database Maintenance Window Details Month> (Updatable) Months during the year when maintenance should be performed.
- Patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- Preference string
(Updatable) The maintenance window scheduling preference.
- Weeks
Of List<int>Months (Updatable) 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 (Updatable) 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 []AutonomousWeeks Container Database Maintenance Window Details Days Of Week (Updatable) Days during the week when maintenance should be performed.
- Hours
Of []intDays (Updatable) 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 (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- Is
Monthly boolPatching Enabled (Updatable) If true, enables the monthly patching option.
- Lead
Time intIn Weeks (Updatable) 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
[]Autonomous
Container Database Maintenance Window Details Month (Updatable) Months during the year when maintenance should be performed.
- Patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- Preference string
(Updatable) The maintenance window scheduling preference.
- Weeks
Of []intMonths (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action IntegerTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of List<AutonomousWeeks Container Maintenance Window Details Days Of Week> (Updatable) Days during the week when maintenance should be performed.
- hours
Of List<Integer>Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom BooleanAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled (Updatable) If true, enables the monthly patching option.
- lead
Time IntegerIn Weeks (Updatable) 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<Autonomous
Container Maintenance Window Details Month> (Updatable) Months during the year when maintenance should be performed.
- patching
Mode String (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- preference String
(Updatable) The maintenance window scheduling preference.
- weeks
Of List<Integer>Months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action numberTimeout In Mins (Updatable) 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 AutonomousWeeks Container Database Maintenance Window Details Days Of Week[] (Updatable) Days during the week when maintenance should be performed.
- hours
Of number[]Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom booleanAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly booleanPatching Enabled (Updatable) If true, enables the monthly patching option.
- lead
Time numberIn Weeks (Updatable) 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
Autonomous
Container Database Maintenance Window Details Month[] (Updatable) Months during the year when maintenance should be performed.
- patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- preference string
(Updatable) The maintenance window scheduling preference.
- weeks
Of number[]Months (Updatable) 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 (Updatable) 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_ Autonomousweeks Container Database Maintenance Window Details Days Of Week] (Updatable) Days during the week when maintenance should be performed.
- hours_
of_ Sequence[int]days (Updatable) 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 (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is_
monthly_ boolpatching_ enabled (Updatable) If true, enables the monthly patching option.
- lead_
time_ intin_ weeks (Updatable) 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
Autonomous
Container Database Maintenance Window Details Month] (Updatable) Months during the year when maintenance should be performed.
- patching_
mode str (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- preference str
(Updatable) The maintenance window scheduling preference.
- weeks_
of_ Sequence[int]months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action NumberTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of List<Property Map>Weeks (Updatable) Days during the week when maintenance should be performed.
- hours
Of List<Number>Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom BooleanAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled (Updatable) If true, enables the monthly patching option.
- lead
Time NumberIn Weeks (Updatable) 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>
(Updatable) Months during the year when maintenance should be performed.
- patching
Mode String (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- preference String
(Updatable) The maintenance window scheduling preference.
- weeks
Of List<Number>Months (Updatable) 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.
AutonomousContainerDatabaseMaintenanceWindowDetailsDaysOfWeek
- Name string
(Updatable) Name of the month of the year.
- Name string
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
- name string
(Updatable) Name of the month of the year.
- name str
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
AutonomousContainerDatabaseMaintenanceWindowDetailsMonth
- Name string
(Updatable) Name of the month of the year.
- Name string
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
- name string
(Updatable) Name of the month of the year.
- name str
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
AutonomousContainerDatabaseMaintenanceWindowMonth
- Name string
(Updatable) Name of the month of the year.
- Name string
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
- name string
(Updatable) Name of the month of the year.
- name str
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
AutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfig
- Backup
Destination List<AutonomousDetails Container Database Peer Autonomous Container Database Backup Config Backup Destination Detail> Backup destination details.
- Recovery
Window intIn Days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
- Backup
Destination []AutonomousDetails Container Database Peer Autonomous Container Database Backup Config Backup Destination Detail Backup destination details.
- Recovery
Window intIn Days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
- backup
Destination List<AutonomousDetails Container Peer Autonomous Container Backup Config Backup Destination Detail> Backup destination details.
- recovery
Window IntegerIn Days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
- backup
Destination AutonomousDetails Container Database Peer Autonomous Container Database Backup Config Backup Destination Detail[] Backup destination details.
- recovery
Window numberIn Days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
- backup_
destination_ Autonomousdetails Container Database Peer Autonomous Container Database Backup Config Backup Destination Detail] Backup destination details.
- recovery_
window_ intin_ days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
- backup
Destination List<Property Map>Details Backup destination details.
- recovery
Window NumberIn Days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
AutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetail
- Type string
Type of the database backup destination.
- Id string
The OCID of the backup destination.
- Internet
Proxy string Proxy URL to connect to object store.
- Vpc
Password string For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- Vpc
User string For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- Type string
Type of the database backup destination.
- Id string
The OCID of the backup destination.
- Internet
Proxy string Proxy URL to connect to object store.
- Vpc
Password string For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- Vpc
User string For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- type String
Type of the database backup destination.
- id String
The OCID of the backup destination.
- internet
Proxy String Proxy URL to connect to object store.
- vpc
Password String For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User String For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- type string
Type of the database backup destination.
- id string
The OCID of the backup destination.
- internet
Proxy string Proxy URL to connect to object store.
- vpc
Password string For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User string For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- type str
Type of the database backup destination.
- 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.
- id String
The OCID of the backup destination.
- internet
Proxy String Proxy URL to connect to object store.
- vpc
Password String For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User String For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
Import
AutonomousContainerDatabases can be imported using the id, e.g.
$ pulumi import oci:Database/autonomousContainerDatabase:AutonomousContainerDatabase test_autonomous_container_database "id"
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
This Pulumi package is based on the
ociTerraform Provider.