oci.Database.getAutonomousContainerDatabase
Explore with Pulumi AI
This data source provides details about a specific Autonomous Container Database resource in Oracle Cloud Infrastructure Database service.
Gets information about the specified Autonomous Container Database.
Example Usage
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Oci = Pulumi.Oci;
return await Deployment.RunAsync(() =>
{
var testAutonomousContainerDatabase = Oci.Database.GetAutonomousContainerDatabase.Invoke(new()
{
AutonomousContainerDatabaseId = oci_database_autonomous_container_database.Test_autonomous_container_database.Id,
});
});
package main
import (
"github.com/pulumi/pulumi-oci/sdk/go/oci/Database"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := Database.GetAutonomousContainerDatabase(ctx, &database.GetAutonomousContainerDatabaseArgs{
AutonomousContainerDatabaseId: oci_database_autonomous_container_database.Test_autonomous_container_database.Id,
}, nil)
if err != nil {
return err
}
return nil
})
}
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Database.DatabaseFunctions;
import com.pulumi.oci.Database.inputs.GetAutonomousContainerDatabaseArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var testAutonomousContainerDatabase = DatabaseFunctions.getAutonomousContainerDatabase(GetAutonomousContainerDatabaseArgs.builder()
.autonomousContainerDatabaseId(oci_database_autonomous_container_database.test_autonomous_container_database().id())
.build());
}
}
import pulumi
import pulumi_oci as oci
test_autonomous_container_database = oci.Database.get_autonomous_container_database(autonomous_container_database_id=oci_database_autonomous_container_database["test_autonomous_container_database"]["id"])
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testAutonomousContainerDatabase = oci.Database.getAutonomousContainerDatabase({
autonomousContainerDatabaseId: oci_database_autonomous_container_database.test_autonomous_container_database.id,
});
variables:
testAutonomousContainerDatabase:
fn::invoke:
Function: oci:Database:getAutonomousContainerDatabase
Arguments:
autonomousContainerDatabaseId: ${oci_database_autonomous_container_database.test_autonomous_container_database.id}
Using getAutonomousContainerDatabase
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getAutonomousContainerDatabase(args: GetAutonomousContainerDatabaseArgs, opts?: InvokeOptions): Promise<GetAutonomousContainerDatabaseResult>
function getAutonomousContainerDatabaseOutput(args: GetAutonomousContainerDatabaseOutputArgs, opts?: InvokeOptions): Output<GetAutonomousContainerDatabaseResult>
def get_autonomous_container_database(autonomous_container_database_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetAutonomousContainerDatabaseResult
def get_autonomous_container_database_output(autonomous_container_database_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetAutonomousContainerDatabaseResult]
func GetAutonomousContainerDatabase(ctx *Context, args *GetAutonomousContainerDatabaseArgs, opts ...InvokeOption) (*GetAutonomousContainerDatabaseResult, error)
func GetAutonomousContainerDatabaseOutput(ctx *Context, args *GetAutonomousContainerDatabaseOutputArgs, opts ...InvokeOption) GetAutonomousContainerDatabaseResultOutput
> Note: This function is named GetAutonomousContainerDatabase
in the Go SDK.
public static class GetAutonomousContainerDatabase
{
public static Task<GetAutonomousContainerDatabaseResult> InvokeAsync(GetAutonomousContainerDatabaseArgs args, InvokeOptions? opts = null)
public static Output<GetAutonomousContainerDatabaseResult> Invoke(GetAutonomousContainerDatabaseInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetAutonomousContainerDatabaseResult> getAutonomousContainerDatabase(GetAutonomousContainerDatabaseArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: oci:Database/getAutonomousContainerDatabase:getAutonomousContainerDatabase
arguments:
# arguments dictionary
The following arguments are supported:
- Autonomous
Container stringDatabase Id The Autonomous Container Database OCID.
- Autonomous
Container stringDatabase Id The Autonomous Container Database OCID.
- autonomous
Container StringDatabase Id The Autonomous Container Database OCID.
- autonomous
Container stringDatabase Id The Autonomous Container Database OCID.
- autonomous_
container_ strdatabase_ id The Autonomous Container Database OCID.
- autonomous
Container StringDatabase Id The Autonomous Container Database OCID.
getAutonomousContainerDatabase Result
The following output properties are available:
- Autonomous
Container stringDatabase Id - Autonomous
Exadata stringInfrastructure Id No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified
cloudAutonomousVmCluster
.- Autonomous
Vm stringCluster Id The OCID of the Autonomous VM Cluster.
- Availability
Domain string The availability domain of the Autonomous Container Database.
- Available
Cpus double Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Backup
Configs List<GetAutonomous Container Database Backup Config> Backup options for the Autonomous Container Database.
- Cloud
Autonomous stringVm Cluster Id The OCID of the cloud Autonomous Exadata VM Cluster.
- Compartment
Id string The OCID of the compartment.
- Compute
Model string The compute model of the Autonomous VM Cluster.
- 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 Oracle Database version of the Autonomous Container Database.
- Dictionary<string, object>
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- Display
Name string The user-provided name for the Autonomous Container Database.
- Dst
File stringVersion DST Time Zone File version of the Autonomous Container Database.
- Fast
Start intFail Over Lag Limit In Seconds - Dictionary<string, object>
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:
{"Department": "Finance"}
- Id string
The id of the Autonomous Database Vault service key management history entry.
- Infrastructure
Type string The infrastructure type this resource belongs to.
- Is
Automatic boolFailover Enabled - Is
Dst boolFile Update Enabled Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- Key
History List<GetEntries Autonomous Container Database Key History Entry> 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.
- Largest
Provisionable doubleAutonomous Database In Cpus The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- Last
Maintenance stringRun Id The OCID of the last maintenance run.
- Lifecycle
Details string Additional information about the current lifecycle state.
- Maintenance
Window List<GetDetails Autonomous Container Database Maintenance Window Detail> - Maintenance
Windows List<GetAutonomous Container Database Maintenance Window> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Memory
Per intOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.
- Next
Maintenance stringRun Id The OCID of the next maintenance run.
- Patch
Id string The OCID of the last patch applied on the system.
- Patch
Model string Database patch model preference.
- Peer
Autonomous List<GetContainer Database Backup Configs Autonomous Container Database Peer Autonomous Container Database Backup Config> - Peer
Autonomous stringContainer Database Compartment Id - Peer
Autonomous stringContainer Database Display Name - Peer
Autonomous stringExadata Infrastructure Id - Peer
Autonomous stringVm Cluster Id - Peer
Cloud stringAutonomous Vm Cluster Id - Peer
Db stringUnique Name - Protection
Mode string - Provisionable
Cpuses List<double> An array of CPU values that can be used to successfully provision a single Autonomous Database.\ 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.
- Provisioned
Cpus double The number of CPUs provisioned in an Autonomous Container Database.
- 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.
- Reserved
Cpus double The number of CPUs reserved in an Autonomous Container Database.
- Role string
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- Rotate
Key boolTrigger - Service
Level stringAgreement Type The service level agreement type of the container database. The default is STANDARD.
- Standby
Maintenance intBuffer In Days The scheduling detail for the quarterly maintenance window of the standby Autonomous Container Database. This value represents the number of days before scheduled maintenance of the primary database.
- 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.
- Vault
Id string - Version
Preference string The next maintenance version preference.
- Autonomous
Container stringDatabase Id - Autonomous
Exadata stringInfrastructure Id No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified
cloudAutonomousVmCluster
.- Autonomous
Vm stringCluster Id The OCID of the Autonomous VM Cluster.
- Availability
Domain string The availability domain of the Autonomous Container Database.
- Available
Cpus float64 Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- Backup
Configs []GetAutonomous Container Database Backup Config Backup options for the Autonomous Container Database.
- Cloud
Autonomous stringVm Cluster Id The OCID of the cloud Autonomous Exadata VM Cluster.
- Compartment
Id string The OCID of the compartment.
- Compute
Model string The compute model of the Autonomous VM Cluster.
- 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 Oracle Database version of the Autonomous Container Database.
- map[string]interface{}
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- Display
Name string The user-provided name for the Autonomous Container Database.
- Dst
File stringVersion DST Time Zone File version of the Autonomous Container Database.
- Fast
Start intFail Over Lag Limit In Seconds - map[string]interface{}
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:
{"Department": "Finance"}
- Id string
The id of the Autonomous Database Vault service key management history entry.
- Infrastructure
Type string The infrastructure type this resource belongs to.
- Is
Automatic boolFailover Enabled - Is
Dst boolFile Update Enabled Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- Key
History []GetEntries Autonomous Container Database Key History Entry 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.
- Largest
Provisionable float64Autonomous Database In Cpus The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- Last
Maintenance stringRun Id The OCID of the last maintenance run.
- Lifecycle
Details string Additional information about the current lifecycle state.
- Maintenance
Window []GetDetails Autonomous Container Database Maintenance Window Detail - Maintenance
Windows []GetAutonomous Container Database Maintenance Window The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Memory
Per intOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.
- Next
Maintenance stringRun Id The OCID of the next maintenance run.
- Patch
Id string The OCID of the last patch applied on the system.
- Patch
Model string Database patch model preference.
- Peer
Autonomous []GetContainer Database Backup Configs Autonomous Container Database Peer Autonomous Container Database Backup Config - Peer
Autonomous stringContainer Database Compartment Id - Peer
Autonomous stringContainer Database Display Name - Peer
Autonomous stringExadata Infrastructure Id - Peer
Autonomous stringVm Cluster Id - Peer
Cloud stringAutonomous Vm Cluster Id - Peer
Db stringUnique Name - Protection
Mode string - Provisionable
Cpuses []float64 An array of CPU values that can be used to successfully provision a single Autonomous Database.\ 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.
- Provisioned
Cpus float64 The number of CPUs provisioned in an Autonomous Container Database.
- 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.
- Reserved
Cpus float64 The number of CPUs reserved in an Autonomous Container Database.
- Role string
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- Rotate
Key boolTrigger - Service
Level stringAgreement Type The service level agreement type of the container database. The default is STANDARD.
- Standby
Maintenance intBuffer In Days The scheduling detail for the quarterly maintenance window of the standby Autonomous Container Database. This value represents the number of days before scheduled maintenance of the primary database.
- 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.
- Vault
Id string - Version
Preference string The next maintenance version preference.
- autonomous
Container StringDatabase Id - autonomous
Exadata StringInfrastructure Id No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified
cloudAutonomousVmCluster
.- autonomous
Vm StringCluster Id The OCID of the Autonomous VM Cluster.
- availability
Domain String The availability domain of the Autonomous Container Database.
- available
Cpus Double Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- backup
Configs List<GetAutonomous Container Backup Config> Backup options for the Autonomous Container Database.
- cloud
Autonomous StringVm Cluster Id The OCID of the cloud Autonomous Exadata VM Cluster.
- compartment
Id String The OCID of the compartment.
- compute
Model String The compute model of the Autonomous VM Cluster.
- 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 Oracle Database version of the Autonomous Container Database.
- Map<String,Object>
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- display
Name String The user-provided name for the Autonomous Container Database.
- dst
File StringVersion DST Time Zone File version of the Autonomous Container Database.
- fast
Start IntegerFail Over Lag Limit In Seconds - Map<String,Object>
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:
{"Department": "Finance"}
- id String
The id of the Autonomous Database Vault service key management history entry.
- infrastructure
Type String The infrastructure type this resource belongs to.
- is
Automatic BooleanFailover Enabled - is
Dst BooleanFile Update Enabled Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- key
History List<GetEntries Autonomous Container Key History Entry> 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.
- largest
Provisionable DoubleAutonomous Database In Cpus The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- last
Maintenance StringRun Id The OCID of the last maintenance run.
- lifecycle
Details String Additional information about the current lifecycle state.
- maintenance
Window List<GetDetails Autonomous Container Maintenance Window Detail> - maintenance
Windows List<GetAutonomous Container Maintenance Window> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per IntegerOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.
- next
Maintenance StringRun Id The OCID of the next maintenance run.
- patch
Id String The OCID of the last patch applied on the system.
- patch
Model String Database patch model preference.
- peer
Autonomous List<GetContainer Database Backup Configs Autonomous Container Peer Autonomous Container Backup Config> - peer
Autonomous StringContainer Database Compartment Id - peer
Autonomous StringContainer Database Display Name - peer
Autonomous StringExadata Infrastructure Id - peer
Autonomous StringVm Cluster Id - peer
Cloud StringAutonomous Vm Cluster Id - peer
Db StringUnique Name - protection
Mode String - provisionable
Cpuses List<Double> An array of CPU values that can be used to successfully provision a single Autonomous Database.\ 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.
- provisioned
Cpus Double The number of CPUs provisioned in an Autonomous Container Database.
- 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.
- reserved
Cpus Double The number of CPUs reserved in an Autonomous Container Database.
- role String
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- rotate
Key BooleanTrigger - service
Level StringAgreement Type The service level agreement type of the container database. The default is STANDARD.
- standby
Maintenance IntegerBuffer In Days The scheduling detail for the quarterly maintenance window of the standby Autonomous Container Database. This value represents the number of days before scheduled maintenance of the primary database.
- state String
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.
- vault
Id String - version
Preference String The next maintenance version preference.
- autonomous
Container stringDatabase Id - autonomous
Exadata stringInfrastructure Id No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified
cloudAutonomousVmCluster
.- autonomous
Vm stringCluster Id The OCID of the Autonomous VM Cluster.
- availability
Domain string The availability domain of the Autonomous Container Database.
- available
Cpus number Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- backup
Configs GetAutonomous Container Database Backup Config[] Backup options for the Autonomous Container Database.
- cloud
Autonomous stringVm Cluster Id The OCID of the cloud Autonomous Exadata VM Cluster.
- compartment
Id string The OCID of the compartment.
- compute
Model string The compute model of the Autonomous VM Cluster.
- 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 Oracle Database version of the Autonomous Container Database.
- {[key: string]: any}
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- display
Name string The user-provided name for the Autonomous Container Database.
- dst
File stringVersion DST Time Zone File version of the Autonomous Container Database.
- fast
Start numberFail Over Lag Limit In Seconds - {[key: string]: any}
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:
{"Department": "Finance"}
- id string
The id of the Autonomous Database Vault service key management history entry.
- infrastructure
Type string The infrastructure type this resource belongs to.
- is
Automatic booleanFailover Enabled - is
Dst booleanFile Update Enabled Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- key
History GetEntries Autonomous Container Database Key History Entry[] 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.
- largest
Provisionable numberAutonomous Database In Cpus The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- last
Maintenance stringRun Id The OCID of the last maintenance run.
- lifecycle
Details string Additional information about the current lifecycle state.
- maintenance
Window GetDetails Autonomous Container Database Maintenance Window Detail[] - maintenance
Windows GetAutonomous Container Database Maintenance Window[] The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per numberOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.
- next
Maintenance stringRun Id The OCID of the next maintenance run.
- patch
Id string The OCID of the last patch applied on the system.
- patch
Model string Database patch model preference.
- peer
Autonomous GetContainer Database Backup Configs Autonomous Container Database Peer Autonomous Container Database Backup Config[] - peer
Autonomous stringContainer Database Compartment Id - peer
Autonomous stringContainer Database Display Name - peer
Autonomous stringExadata Infrastructure Id - peer
Autonomous stringVm Cluster Id - peer
Cloud stringAutonomous Vm Cluster Id - peer
Db stringUnique Name - protection
Mode string - provisionable
Cpuses number[] An array of CPU values that can be used to successfully provision a single Autonomous Database.\ 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.
- provisioned
Cpus number The number of CPUs provisioned in an Autonomous Container Database.
- reclaimable
Cpus number For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
- reserved
Cpus number The number of CPUs reserved in an Autonomous Container Database.
- role string
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- rotate
Key booleanTrigger - service
Level stringAgreement Type The service level agreement type of the container database. The default is STANDARD.
- standby
Maintenance numberBuffer In Days The scheduling detail for the quarterly maintenance window of the standby Autonomous Container Database. This value represents the number of days before scheduled maintenance of the primary database.
- state string
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.
- vault
Id string - version
Preference string The next maintenance version preference.
- autonomous_
container_ strdatabase_ id - autonomous_
exadata_ strinfrastructure_ id No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified
cloudAutonomousVmCluster
.- autonomous_
vm_ strcluster_ id The OCID of the Autonomous VM Cluster.
- availability_
domain str The availability domain of the Autonomous Container Database.
- available_
cpus float Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- backup_
configs GetAutonomous Container Database Backup Config] Backup options for the Autonomous Container Database.
- cloud_
autonomous_ strvm_ cluster_ id The OCID of the cloud Autonomous Exadata VM Cluster.
- compartment_
id str The OCID of the compartment.
- compute_
model str The compute model of the Autonomous VM Cluster.
- 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 Oracle Database version of the Autonomous Container Database.
- Mapping[str, Any]
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- display_
name str The user-provided name for the Autonomous Container Database.
- dst_
file_ strversion DST Time Zone File version of the Autonomous Container Database.
- fast_
start_ intfail_ over_ lag_ limit_ in_ seconds - Mapping[str, Any]
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:
{"Department": "Finance"}
- id str
The id of the Autonomous Database Vault service key management history entry.
- infrastructure_
type str The infrastructure type this resource belongs to.
- is_
automatic_ boolfailover_ enabled - is_
dst_ boolfile_ update_ enabled Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- key_
history_ Getentries Autonomous Container Database Key History Entry] 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.
- largest_
provisionable_ floatautonomous_ database_ in_ cpus The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- last_
maintenance_ strrun_ id The OCID of the last maintenance run.
- lifecycle_
details str Additional information about the current lifecycle state.
- maintenance_
window_ Getdetails Autonomous Container Database Maintenance Window Detail] - maintenance_
windows GetAutonomous Container Database Maintenance Window] The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory_
per_ intoracle_ compute_ unit_ in_ gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.
- next_
maintenance_ strrun_ id The OCID of the next maintenance run.
- patch_
id str The OCID of the last patch applied on the system.
- patch_
model str Database patch model preference.
- peer_
autonomous_ Getcontainer_ database_ backup_ configs Autonomous Container Database Peer Autonomous Container Database Backup Config] - peer_
autonomous_ strcontainer_ database_ compartment_ id - peer_
autonomous_ strcontainer_ database_ display_ name - peer_
autonomous_ strexadata_ infrastructure_ id - peer_
autonomous_ strvm_ cluster_ id - peer_
cloud_ strautonomous_ vm_ cluster_ id - peer_
db_ strunique_ name - protection_
mode str - provisionable_
cpuses Sequence[float] An array of CPU values that can be used to successfully provision a single Autonomous Database.\ 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.
- provisioned_
cpus float The number of CPUs provisioned in an Autonomous Container Database.
- 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.
- reserved_
cpus float The number of CPUs reserved in an Autonomous Container Database.
- role str
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- rotate_
key_ booltrigger - service_
level_ stragreement_ type The service level agreement type of the container database. The default is STANDARD.
- standby_
maintenance_ intbuffer_ in_ days The scheduling detail for the quarterly maintenance window of the standby Autonomous Container Database. This value represents the number of days before scheduled maintenance of the primary database.
- 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.
- vault_
id str - version_
preference str The next maintenance version preference.
- autonomous
Container StringDatabase Id - autonomous
Exadata StringInfrastructure Id No longer used. For Autonomous Database on dedicated Exadata infrastructure, the container database is created within a specified
cloudAutonomousVmCluster
.- autonomous
Vm StringCluster Id The OCID of the Autonomous VM Cluster.
- availability
Domain String The availability domain of the Autonomous Container Database.
- available
Cpus Number Sum of CPUs available on the Autonomous VM Cluster + Sum of reclaimable CPUs available in the Autonomous Container Database. For Autonomous Databases on Dedicated Exadata Infrastructure, the CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model. See Compute Models in Autonomous Database on Dedicated Exadata Infrastructure for more details.
- backup
Configs List<Property Map> Backup options for the Autonomous Container Database.
- cloud
Autonomous StringVm Cluster Id The OCID of the cloud Autonomous Exadata VM Cluster.
- compartment
Id String The OCID of the compartment.
- compute
Model String The compute model of the Autonomous VM Cluster.
- 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 Oracle Database version of the Autonomous Container Database.
- Map<Any>
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- display
Name String The user-provided name for the Autonomous Container Database.
- dst
File StringVersion DST Time Zone File version of the Autonomous Container Database.
- fast
Start NumberFail Over Lag Limit In Seconds - Map<Any>
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:
{"Department": "Finance"}
- id String
The id of the Autonomous Database Vault service key management history entry.
- infrastructure
Type String The infrastructure type this resource belongs to.
- is
Automatic BooleanFailover Enabled - is
Dst BooleanFile Update Enabled Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- key
History List<Property Map>Entries Key History Entry.
- key
Store StringId The OCID of the key store.
- 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.
- largest
Provisionable NumberAutonomous Database In Cpus The largest Autonomous Database (CPU) that can be created in a new Autonomous Container Database.
- last
Maintenance StringRun Id The OCID of the last maintenance run.
- lifecycle
Details String Additional information about the current lifecycle state.
- maintenance
Window List<Property Map>Details - maintenance
Windows List<Property Map> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per NumberOracle Compute Unit In Gbs The amount of memory (in GBs) enabled per OCPU or ECPU in the Autonomous VM Cluster.
- next
Maintenance StringRun Id The OCID of the next maintenance run.
- patch
Id String The OCID of the last patch applied on the system.
- patch
Model String Database patch model preference.
- peer
Autonomous List<Property Map>Container Database Backup Configs - peer
Autonomous StringContainer Database Compartment Id - peer
Autonomous StringContainer Database Display Name - peer
Autonomous StringExadata Infrastructure Id - peer
Autonomous StringVm Cluster Id - peer
Cloud StringAutonomous Vm Cluster Id - peer
Db StringUnique Name - protection
Mode String - provisionable
Cpuses List<Number> An array of CPU values that can be used to successfully provision a single Autonomous Database.\ 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.
- provisioned
Cpus Number The number of CPUs provisioned in an Autonomous Container Database.
- reclaimable
Cpus Number For Autonomous Databases on Dedicated Exadata Infrastructure:
- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
- reserved
Cpus Number The number of CPUs reserved in an Autonomous Container Database.
- role String
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
- rotate
Key BooleanTrigger - service
Level StringAgreement Type The service level agreement type of the container database. The default is STANDARD.
- standby
Maintenance NumberBuffer In Days The scheduling detail for the quarterly maintenance window of the standby Autonomous Container Database. This value represents the number of days before scheduled maintenance of the primary database.
- state String
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.
- vault
Id String - version
Preference String The next maintenance version preference.
Supporting Types
GetAutonomousContainerDatabaseBackupConfig
- Backup
Destination List<GetDetails 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 []GetDetails 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<GetDetails 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 GetDetails 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_ Getdetails 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.
GetAutonomousContainerDatabaseBackupConfigBackupDestinationDetail
- Id string
The id of the Autonomous Database Vault service key management history entry.
- Internet
Proxy string Proxy URL to connect to object store.
- Type string
Type of the database backup destination.
- Vpc
Password string For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- Vpc
User string For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- Id string
The id of the Autonomous Database Vault service key management history entry.
- Internet
Proxy string Proxy URL to connect to object store.
- Type string
Type of the database backup destination.
- Vpc
Password string For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- Vpc
User string For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id String
The id of the Autonomous Database Vault service key management history entry.
- internet
Proxy String Proxy URL to connect to object store.
- type String
Type of the database backup destination.
- vpc
Password String For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User String For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id string
The id of the Autonomous Database Vault service key management history entry.
- internet
Proxy string Proxy URL to connect to object store.
- type string
Type of the database backup destination.
- vpc
Password string For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User string For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id str
The id of the Autonomous Database Vault service key management history entry.
- internet_
proxy str Proxy URL to connect to object store.
- type str
Type of the database backup destination.
- vpc_
password str For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc_
user str For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id String
The id of the Autonomous Database Vault service key management history entry.
- internet
Proxy String Proxy URL to connect to object store.
- type String
Type of the database backup destination.
- vpc
Password String For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User String For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
GetAutonomousContainerDatabaseKeyHistoryEntry
- Id string
The id of the Autonomous Database Vault service key management history entry.
- Kms
Key stringVersion Id The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation.
- Time
Activated string The date and time the kms key activated.
- Vault
Id string
- Id string
The id of the Autonomous Database Vault service key management history entry.
- Kms
Key stringVersion Id The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation.
- Time
Activated string The date and time the kms key activated.
- Vault
Id string
- id String
The id of the Autonomous Database Vault service key management history entry.
- kms
Key StringVersion Id The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation.
- time
Activated String The date and time the kms key activated.
- vault
Id String
- id string
The id of the Autonomous Database Vault service key management history entry.
- kms
Key stringVersion Id The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation.
- time
Activated string The date and time the kms key activated.
- vault
Id string
- id str
The id of the Autonomous Database Vault service key management history entry.
- kms_
key_ strversion_ id The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation.
- time_
activated str The date and time the kms key activated.
- vault_
id str
- id String
The id of the Autonomous Database Vault service key management history entry.
- kms
Key StringVersion Id The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation.
- time
Activated String The date and time the kms key activated.
- vault
Id String
GetAutonomousContainerDatabaseMaintenanceWindow
- Custom
Action intTimeout In Mins Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- Days
Of List<GetWeeks Autonomous Container Database Maintenance Window Days Of Week> Days during the week when maintenance should be performed.
- Hours
Of List<int>Days The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- Is
Custom boolAction Timeout Enabled If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- Is
Monthly boolPatching Enabled If true, enables the monthly patching option.
- Lead
Time intIn Weeks Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
List<Get
Autonomous Container Database Maintenance Window Month> Months during the year when maintenance should be performed.
- Patching
Mode string Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
The maintenance window scheduling preference.
- Weeks
Of List<int>Months Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- Custom
Action intTimeout In Mins Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- Days
Of []GetWeeks Autonomous Container Database Maintenance Window Days Of Week Days during the week when maintenance should be performed.
- Hours
Of []intDays The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- Is
Custom boolAction Timeout Enabled If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- Is
Monthly boolPatching Enabled If true, enables the monthly patching option.
- Lead
Time intIn Weeks Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
[]Get
Autonomous Container Database Maintenance Window Month Months during the year when maintenance should be performed.
- Patching
Mode string Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
The maintenance window scheduling preference.
- Weeks
Of []intMonths Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action IntegerTimeout In Mins Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of List<GetWeeks Autonomous Container Maintenance Window Days Of Week> Days during the week when maintenance should be performed.
- hours
Of List<Integer>Days The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom BooleanAction Timeout Enabled If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled If true, enables the monthly patching option.
- lead
Time IntegerIn Weeks Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
List<Get
Autonomous Container Maintenance Window Month> Months during the year when maintenance should be performed.
- patching
Mode String Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
The maintenance window scheduling preference.
- weeks
Of List<Integer>Months Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action numberTimeout In Mins Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of GetWeeks Autonomous Container Database Maintenance Window Days Of Week[] Days during the week when maintenance should be performed.
- hours
Of number[]Days The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom booleanAction Timeout Enabled If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly booleanPatching Enabled If true, enables the monthly patching option.
- lead
Time numberIn Weeks Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
Get
Autonomous Container Database Maintenance Window Month[] Months during the year when maintenance should be performed.
- patching
Mode string Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference string
The maintenance window scheduling preference.
- weeks
Of number[]Months Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom_
action_ inttimeout_ in_ mins Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days_
of_ Getweeks Autonomous Container Database Maintenance Window Days Of Week] Days during the week when maintenance should be performed.
- hours_
of_ Sequence[int]days The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is_
custom_ boolaction_ timeout_ enabled If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is_
monthly_ boolpatching_ enabled If true, enables the monthly patching option.
- lead_
time_ intin_ weeks Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
Get
Autonomous Container Database Maintenance Window Month] Months during the year when maintenance should be performed.
- patching_
mode str Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference str
The maintenance window scheduling preference.
- weeks_
of_ Sequence[int]months Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action NumberTimeout In Mins Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of List<Property Map>Weeks Days during the week when maintenance should be performed.
- hours
Of List<Number>Days The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom BooleanAction Timeout Enabled If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled If true, enables the monthly patching option.
- lead
Time NumberIn Weeks Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months List<Property Map>
Months during the year when maintenance should be performed.
- patching
Mode String Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
The maintenance window scheduling preference.
- weeks
Of List<Number>Months Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
GetAutonomousContainerDatabaseMaintenanceWindowDaysOfWeek
- Name string
Name of the month of the year.
- Name string
Name of the month of the year.
- name String
Name of the month of the year.
- name string
Name of the month of the year.
- name str
Name of the month of the year.
- name String
Name of the month of the year.
GetAutonomousContainerDatabaseMaintenanceWindowDetail
- Custom
Action intTimeout In Mins Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- Days
Of List<GetWeeks Autonomous Container Database Maintenance Window Detail Days Of Week> Days during the week when maintenance should be performed.
- Hours
Of List<int>Days The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- Is
Custom boolAction Timeout Enabled If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- Is
Monthly boolPatching Enabled If true, enables the monthly patching option.
- Lead
Time intIn Weeks Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
List<Get
Autonomous Container Database Maintenance Window Detail Month> Months during the year when maintenance should be performed.
- Patching
Mode string Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
The maintenance window scheduling preference.
- Weeks
Of List<int>Months Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- Custom
Action intTimeout In Mins Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- Days
Of []GetWeeks Autonomous Container Database Maintenance Window Detail Days Of Week Days during the week when maintenance should be performed.
- Hours
Of []intDays The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- Is
Custom boolAction Timeout Enabled If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- Is
Monthly boolPatching Enabled If true, enables the monthly patching option.
- Lead
Time intIn Weeks Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
[]Get
Autonomous Container Database Maintenance Window Detail Month Months during the year when maintenance should be performed.
- Patching
Mode string Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
The maintenance window scheduling preference.
- Weeks
Of []intMonths Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action IntegerTimeout In Mins Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of List<GetWeeks Autonomous Container Maintenance Window Detail Days Of Week> Days during the week when maintenance should be performed.
- hours
Of List<Integer>Days The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom BooleanAction Timeout Enabled If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled If true, enables the monthly patching option.
- lead
Time IntegerIn Weeks Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
List<Get
Autonomous Container Maintenance Window Detail Month> Months during the year when maintenance should be performed.
- patching
Mode String Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
The maintenance window scheduling preference.
- weeks
Of List<Integer>Months Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action numberTimeout In Mins Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of GetWeeks Autonomous Container Database Maintenance Window Detail Days Of Week[] Days during the week when maintenance should be performed.
- hours
Of number[]Days The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom booleanAction Timeout Enabled If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly booleanPatching Enabled If true, enables the monthly patching option.
- lead
Time numberIn Weeks Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
Get
Autonomous Container Database Maintenance Window Detail Month[] Months during the year when maintenance should be performed.
- patching
Mode string Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference string
The maintenance window scheduling preference.
- weeks
Of number[]Months Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom_
action_ inttimeout_ in_ mins Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days_
of_ Getweeks Autonomous Container Database Maintenance Window Detail Days Of Week] Days during the week when maintenance should be performed.
- hours_
of_ Sequence[int]days The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is_
custom_ boolaction_ timeout_ enabled If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is_
monthly_ boolpatching_ enabled If true, enables the monthly patching option.
- lead_
time_ intin_ weeks Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
Get
Autonomous Container Database Maintenance Window Detail Month] Months during the year when maintenance should be performed.
- patching_
mode str Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference str
The maintenance window scheduling preference.
- weeks_
of_ Sequence[int]months Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action NumberTimeout In Mins Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of List<Property Map>Weeks Days during the week when maintenance should be performed.
- hours
Of List<Number>Days The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom BooleanAction Timeout Enabled If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled If true, enables the monthly patching option.
- lead
Time NumberIn Weeks Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months List<Property Map>
Months during the year when maintenance should be performed.
- patching
Mode String Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
The maintenance window scheduling preference.
- weeks
Of List<Number>Months Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
GetAutonomousContainerDatabaseMaintenanceWindowDetailDaysOfWeek
- Name string
Name of the month of the year.
- Name string
Name of the month of the year.
- name String
Name of the month of the year.
- name string
Name of the month of the year.
- name str
Name of the month of the year.
- name String
Name of the month of the year.
GetAutonomousContainerDatabaseMaintenanceWindowDetailMonth
- Name string
Name of the month of the year.
- Name string
Name of the month of the year.
- name String
Name of the month of the year.
- name string
Name of the month of the year.
- name str
Name of the month of the year.
- name String
Name of the month of the year.
GetAutonomousContainerDatabaseMaintenanceWindowMonth
- Name string
Name of the month of the year.
- Name string
Name of the month of the year.
- name String
Name of the month of the year.
- name string
Name of the month of the year.
- name str
Name of the month of the year.
- name String
Name of the month of the year.
GetAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfig
- Backup
Destination List<GetDetails Autonomous Container Database Peer Autonomous Container Database Backup Config Backup Destination Detail> Backup destination details.
- Recovery
Window intIn Days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
- Backup
Destination []GetDetails Autonomous Container Database Peer Autonomous Container Database Backup Config Backup Destination Detail Backup destination details.
- Recovery
Window intIn Days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
- backup
Destination List<GetDetails Autonomous Container Peer Autonomous Container Backup Config Backup Destination Detail> Backup destination details.
- recovery
Window IntegerIn Days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
- backup
Destination GetDetails Autonomous Container Database Peer Autonomous Container Database Backup Config Backup Destination Detail[] Backup destination details.
- recovery
Window numberIn Days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
- backup_
destination_ Getdetails Autonomous Container Database Peer Autonomous Container Database Backup Config Backup Destination Detail] Backup destination details.
- recovery_
window_ intin_ days Number of days between the current and the earliest point of recoverability covered by automatic backups. This value applies to automatic backups. After a new automatic backup has been created, Oracle removes old automatic backups that are created before the window. When the value is updated, it is applied to all existing automatic backups.
- 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.
GetAutonomousContainerDatabasePeerAutonomousContainerDatabaseBackupConfigBackupDestinationDetail
- Id string
The id of the Autonomous Database Vault service key management history entry.
- Internet
Proxy string Proxy URL to connect to object store.
- Type string
Type of the database backup destination.
- Vpc
Password string For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- Vpc
User string For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- Id string
The id of the Autonomous Database Vault service key management history entry.
- Internet
Proxy string Proxy URL to connect to object store.
- Type string
Type of the database backup destination.
- Vpc
Password string For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- Vpc
User string For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id String
The id of the Autonomous Database Vault service key management history entry.
- internet
Proxy String Proxy URL to connect to object store.
- type String
Type of the database backup destination.
- vpc
Password String For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User String For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id string
The id of the Autonomous Database Vault service key management history entry.
- internet
Proxy string Proxy URL to connect to object store.
- type string
Type of the database backup destination.
- vpc
Password string For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User string For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id str
The id of the Autonomous Database Vault service key management history entry.
- internet_
proxy str Proxy URL to connect to object store.
- type str
Type of the database backup destination.
- vpc_
password str For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc_
user str For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
- id String
The id of the Autonomous Database Vault service key management history entry.
- internet
Proxy String Proxy URL to connect to object store.
- type String
Type of the database backup destination.
- vpc
Password String For a RECOVERY_APPLIANCE backup destination, the password for the VPC user that is used to access the Recovery Appliance.
- vpc
User String For a RECOVERY_APPLIANCE backup destination, the Virtual Private Catalog (VPC) user that is used to access the Recovery Appliance.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
This Pulumi package is based on the
oci
Terraform Provider.