oci.Database.getAutonomousExadataInfrastructure
Explore with Pulumi AI
This data source provides details about a specific Autonomous Exadata Infrastructure resource in Oracle Cloud Infrastructure Database service.
Deprecated. Use the GetCloudExadataInfrastructure operation to get details of an Exadata Infrastructure resource and the GetCloudAutonomousVmCluster operation to get details of an Autonomous Exadata VM cluster.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testAutonomousExadataInfrastructure = oci.Database.getAutonomousExadataInfrastructure({
    autonomousExadataInfrastructureId: testAutonomousExadataInfrastructureOciDatabaseAutonomousExadataInfrastructure.id,
});
import pulumi
import pulumi_oci as oci
test_autonomous_exadata_infrastructure = oci.Database.get_autonomous_exadata_infrastructure(autonomous_exadata_infrastructure_id=test_autonomous_exadata_infrastructure_oci_database_autonomous_exadata_infrastructure["id"])
package main
import (
	"github.com/pulumi/pulumi-oci/sdk/v2/go/oci/database"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := database.GetAutonomousExadataInfrastructure(ctx, &database.GetAutonomousExadataInfrastructureArgs{
			AutonomousExadataInfrastructureId: testAutonomousExadataInfrastructureOciDatabaseAutonomousExadataInfrastructure.Id,
		}, nil)
		if err != nil {
			return err
		}
		return nil
	})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Oci = Pulumi.Oci;
return await Deployment.RunAsync(() => 
{
    var testAutonomousExadataInfrastructure = Oci.Database.GetAutonomousExadataInfrastructure.Invoke(new()
    {
        AutonomousExadataInfrastructureId = testAutonomousExadataInfrastructureOciDatabaseAutonomousExadataInfrastructure.Id,
    });
});
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.GetAutonomousExadataInfrastructureArgs;
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 testAutonomousExadataInfrastructure = DatabaseFunctions.getAutonomousExadataInfrastructure(GetAutonomousExadataInfrastructureArgs.builder()
            .autonomousExadataInfrastructureId(testAutonomousExadataInfrastructureOciDatabaseAutonomousExadataInfrastructure.id())
            .build());
    }
}
variables:
  testAutonomousExadataInfrastructure:
    fn::invoke:
      function: oci:Database:getAutonomousExadataInfrastructure
      arguments:
        autonomousExadataInfrastructureId: ${testAutonomousExadataInfrastructureOciDatabaseAutonomousExadataInfrastructure.id}
Using getAutonomousExadataInfrastructure
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 getAutonomousExadataInfrastructure(args: GetAutonomousExadataInfrastructureArgs, opts?: InvokeOptions): Promise<GetAutonomousExadataInfrastructureResult>
function getAutonomousExadataInfrastructureOutput(args: GetAutonomousExadataInfrastructureOutputArgs, opts?: InvokeOptions): Output<GetAutonomousExadataInfrastructureResult>def get_autonomous_exadata_infrastructure(autonomous_exadata_infrastructure_id: Optional[str] = None,
                                          opts: Optional[InvokeOptions] = None) -> GetAutonomousExadataInfrastructureResult
def get_autonomous_exadata_infrastructure_output(autonomous_exadata_infrastructure_id: Optional[pulumi.Input[str]] = None,
                                          opts: Optional[InvokeOptions] = None) -> Output[GetAutonomousExadataInfrastructureResult]func LookupAutonomousExadataInfrastructure(ctx *Context, args *LookupAutonomousExadataInfrastructureArgs, opts ...InvokeOption) (*LookupAutonomousExadataInfrastructureResult, error)
func LookupAutonomousExadataInfrastructureOutput(ctx *Context, args *LookupAutonomousExadataInfrastructureOutputArgs, opts ...InvokeOption) LookupAutonomousExadataInfrastructureResultOutput> Note: This function is named LookupAutonomousExadataInfrastructure in the Go SDK.
public static class GetAutonomousExadataInfrastructure 
{
    public static Task<GetAutonomousExadataInfrastructureResult> InvokeAsync(GetAutonomousExadataInfrastructureArgs args, InvokeOptions? opts = null)
    public static Output<GetAutonomousExadataInfrastructureResult> Invoke(GetAutonomousExadataInfrastructureInvokeArgs args, InvokeOptions? opts = null)
}public static CompletableFuture<GetAutonomousExadataInfrastructureResult> getAutonomousExadataInfrastructure(GetAutonomousExadataInfrastructureArgs args, InvokeOptions options)
public static Output<GetAutonomousExadataInfrastructureResult> getAutonomousExadataInfrastructure(GetAutonomousExadataInfrastructureArgs args, InvokeOptions options)
fn::invoke:
  function: oci:Database/getAutonomousExadataInfrastructure:getAutonomousExadataInfrastructure
  arguments:
    # arguments dictionaryThe following arguments are supported:
- AutonomousExadata stringInfrastructure Id 
- The Autonomous Exadata Infrastructure OCID.
- AutonomousExadata stringInfrastructure Id 
- The Autonomous Exadata Infrastructure OCID.
- autonomousExadata StringInfrastructure Id 
- The Autonomous Exadata Infrastructure OCID.
- autonomousExadata stringInfrastructure Id 
- The Autonomous Exadata Infrastructure OCID.
- autonomous_exadata_ strinfrastructure_ id 
- The Autonomous Exadata Infrastructure OCID.
- autonomousExadata StringInfrastructure Id 
- The Autonomous Exadata Infrastructure OCID.
getAutonomousExadataInfrastructure Result
The following output properties are available:
- AutonomousExadata stringInfrastructure Id 
- AvailabilityDomain string
- The name of the availability domain that the Autonomous Exadata Infrastructure is located in.
- CompartmentId string
- The OCID of the compartment.
- CreateAsync bool
- Dictionary<string, string>
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- DisplayName string
- The user-friendly name for the Autonomous Exadata Infrastructure.
- Domain string
- The domain name for the Autonomous Exadata Infrastructure.
- Dictionary<string, string>
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}
- Hostname string
- The host name for the Autonomous Exadata Infrastructure node.
- Id string
- The OCID of the Autonomous Exadata Infrastructure.
- LastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- LicenseModel string
- The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
- LifecycleDetails string
- Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
- MaintenanceWindow List<GetDetails Autonomous Exadata Infrastructure Maintenance Window Detail> 
- MaintenanceWindows List<GetAutonomous Exadata Infrastructure Maintenance Window> 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- NextMaintenance stringRun Id 
- The OCID of the next maintenance run.
- NsgIds List<string>
- The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
 
- ScanDns stringName 
- The FQDN of the DNS record for the SCAN IP addresses that are associated with the Autonomous Exadata Infrastructure.
- Shape string
- The shape of the Autonomous Exadata Infrastructure. The shape determines resources to allocate to the Autonomous Exadata Infrastructure (CPU cores, memory and storage).
- State string
- The current lifecycle state of the Autonomous Exadata Infrastructure.
- SubnetId string
- The OCID of the subnet the Autonomous Exadata Infrastructure is associated with.
- TimeCreated string
- The date and time the Autonomous Exadata Infrastructure was created.
- ZoneId string
- The OCID of the zone the Autonomous Exadata Infrastructure is associated with.
- AutonomousExadata stringInfrastructure Id 
- AvailabilityDomain string
- The name of the availability domain that the Autonomous Exadata Infrastructure is located in.
- CompartmentId string
- The OCID of the compartment.
- CreateAsync bool
- map[string]string
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- DisplayName string
- The user-friendly name for the Autonomous Exadata Infrastructure.
- Domain string
- The domain name for the Autonomous Exadata Infrastructure.
- map[string]string
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}
- Hostname string
- The host name for the Autonomous Exadata Infrastructure node.
- Id string
- The OCID of the Autonomous Exadata Infrastructure.
- LastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- LicenseModel string
- The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
- LifecycleDetails string
- Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
- MaintenanceWindow []GetDetails Autonomous Exadata Infrastructure Maintenance Window Detail 
- MaintenanceWindows []GetAutonomous Exadata Infrastructure Maintenance Window 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- NextMaintenance stringRun Id 
- The OCID of the next maintenance run.
- NsgIds []string
- The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
 
- ScanDns stringName 
- The FQDN of the DNS record for the SCAN IP addresses that are associated with the Autonomous Exadata Infrastructure.
- Shape string
- The shape of the Autonomous Exadata Infrastructure. The shape determines resources to allocate to the Autonomous Exadata Infrastructure (CPU cores, memory and storage).
- State string
- The current lifecycle state of the Autonomous Exadata Infrastructure.
- SubnetId string
- The OCID of the subnet the Autonomous Exadata Infrastructure is associated with.
- TimeCreated string
- The date and time the Autonomous Exadata Infrastructure was created.
- ZoneId string
- The OCID of the zone the Autonomous Exadata Infrastructure is associated with.
- autonomousExadata StringInfrastructure Id 
- availabilityDomain String
- The name of the availability domain that the Autonomous Exadata Infrastructure is located in.
- compartmentId String
- The OCID of the compartment.
- createAsync Boolean
- Map<String,String>
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- displayName String
- The user-friendly name for the Autonomous Exadata Infrastructure.
- domain String
- The domain name for the Autonomous Exadata Infrastructure.
- Map<String,String>
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}
- hostname String
- The host name for the Autonomous Exadata Infrastructure node.
- id String
- The OCID of the Autonomous Exadata Infrastructure.
- lastMaintenance StringRun Id 
- The OCID of the last maintenance run.
- licenseModel String
- The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
- lifecycleDetails String
- Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
- maintenanceWindow List<GetDetails Autonomous Exadata Infrastructure Maintenance Window Detail> 
- maintenanceWindows List<GetAutonomous Exadata Infrastructure Maintenance Window> 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- nextMaintenance StringRun Id 
- The OCID of the next maintenance run.
- nsgIds List<String>
- The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
 
- scanDns StringName 
- The FQDN of the DNS record for the SCAN IP addresses that are associated with the Autonomous Exadata Infrastructure.
- shape String
- The shape of the Autonomous Exadata Infrastructure. The shape determines resources to allocate to the Autonomous Exadata Infrastructure (CPU cores, memory and storage).
- state String
- The current lifecycle state of the Autonomous Exadata Infrastructure.
- subnetId String
- The OCID of the subnet the Autonomous Exadata Infrastructure is associated with.
- timeCreated String
- The date and time the Autonomous Exadata Infrastructure was created.
- zoneId String
- The OCID of the zone the Autonomous Exadata Infrastructure is associated with.
- autonomousExadata stringInfrastructure Id 
- availabilityDomain string
- The name of the availability domain that the Autonomous Exadata Infrastructure is located in.
- compartmentId string
- The OCID of the compartment.
- createAsync boolean
- {[key: string]: string}
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- displayName string
- The user-friendly name for the Autonomous Exadata Infrastructure.
- domain string
- The domain name for the Autonomous Exadata Infrastructure.
- {[key: string]: string}
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}
- hostname string
- The host name for the Autonomous Exadata Infrastructure node.
- id string
- The OCID of the Autonomous Exadata Infrastructure.
- lastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- licenseModel string
- The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
- lifecycleDetails string
- Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
- maintenanceWindow GetDetails Autonomous Exadata Infrastructure Maintenance Window Detail[] 
- maintenanceWindows GetAutonomous Exadata Infrastructure Maintenance Window[] 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- nextMaintenance stringRun Id 
- The OCID of the next maintenance run.
- nsgIds string[]
- The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
 
- scanDns stringName 
- The FQDN of the DNS record for the SCAN IP addresses that are associated with the Autonomous Exadata Infrastructure.
- shape string
- The shape of the Autonomous Exadata Infrastructure. The shape determines resources to allocate to the Autonomous Exadata Infrastructure (CPU cores, memory and storage).
- state string
- The current lifecycle state of the Autonomous Exadata Infrastructure.
- subnetId string
- The OCID of the subnet the Autonomous Exadata Infrastructure is associated with.
- timeCreated string
- The date and time the Autonomous Exadata Infrastructure was created.
- zoneId string
- The OCID of the zone the Autonomous Exadata Infrastructure is associated with.
- autonomous_exadata_ strinfrastructure_ id 
- availability_domain str
- The name of the availability domain that the Autonomous Exadata Infrastructure is located in.
- compartment_id str
- The OCID of the compartment.
- create_async bool
- Mapping[str, str]
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- display_name str
- The user-friendly name for the Autonomous Exadata Infrastructure.
- domain str
- The domain name for the Autonomous Exadata Infrastructure.
- Mapping[str, str]
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}
- hostname str
- The host name for the Autonomous Exadata Infrastructure node.
- id str
- The OCID of the Autonomous Exadata Infrastructure.
- last_maintenance_ strrun_ id 
- The OCID of the last maintenance run.
- license_model str
- The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
- lifecycle_details str
- Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
- maintenance_window_ Sequence[Getdetails Autonomous Exadata Infrastructure Maintenance Window Detail] 
- maintenance_windows Sequence[GetAutonomous Exadata Infrastructure Maintenance Window] 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- next_maintenance_ strrun_ id 
- The OCID of the next maintenance run.
- nsg_ids Sequence[str]
- The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
 
- scan_dns_ strname 
- The FQDN of the DNS record for the SCAN IP addresses that are associated with the Autonomous Exadata Infrastructure.
- shape str
- The shape of the Autonomous Exadata Infrastructure. The shape determines resources to allocate to the Autonomous Exadata Infrastructure (CPU cores, memory and storage).
- state str
- The current lifecycle state of the Autonomous Exadata Infrastructure.
- subnet_id str
- The OCID of the subnet the Autonomous Exadata Infrastructure is associated with.
- time_created str
- The date and time the Autonomous Exadata Infrastructure was created.
- zone_id str
- The OCID of the zone the Autonomous Exadata Infrastructure is associated with.
- autonomousExadata StringInfrastructure Id 
- availabilityDomain String
- The name of the availability domain that the Autonomous Exadata Infrastructure is located in.
- compartmentId String
- The OCID of the compartment.
- createAsync Boolean
- Map<String>
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- displayName String
- The user-friendly name for the Autonomous Exadata Infrastructure.
- domain String
- The domain name for the Autonomous Exadata Infrastructure.
- Map<String>
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}
- hostname String
- The host name for the Autonomous Exadata Infrastructure node.
- id String
- The OCID of the Autonomous Exadata Infrastructure.
- lastMaintenance StringRun Id 
- The OCID of the last maintenance run.
- licenseModel String
- The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
- lifecycleDetails String
- Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
- maintenanceWindow List<Property Map>Details 
- maintenanceWindows List<Property Map>
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- nextMaintenance StringRun Id 
- The OCID of the next maintenance run.
- nsgIds List<String>
- The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
 
- scanDns StringName 
- The FQDN of the DNS record for the SCAN IP addresses that are associated with the Autonomous Exadata Infrastructure.
- shape String
- The shape of the Autonomous Exadata Infrastructure. The shape determines resources to allocate to the Autonomous Exadata Infrastructure (CPU cores, memory and storage).
- state String
- The current lifecycle state of the Autonomous Exadata Infrastructure.
- subnetId String
- The OCID of the subnet the Autonomous Exadata Infrastructure is associated with.
- timeCreated String
- The date and time the Autonomous Exadata Infrastructure was created.
- zoneId String
- The OCID of the zone the Autonomous Exadata Infrastructure is associated with.
Supporting Types
GetAutonomousExadataInfrastructureMaintenanceWindow     
- CustomAction intTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- DaysOf List<GetWeeks Autonomous Exadata Infrastructure Maintenance Window Days Of Week> 
- Days during the week when maintenance should be performed.
- HoursOf List<int>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- IsMonthly boolPatching Enabled 
- If true, enables the monthly patching option.
- LeadTime intIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
List<GetAutonomous Exadata Infrastructure Maintenance Window Month> 
- Months during the year when maintenance should be performed.
- PatchingMode string
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
- The maintenance window scheduling preference.
- SkipRus List<bool>
- WeeksOf List<int>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- CustomAction intTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- DaysOf []GetWeeks Autonomous Exadata Infrastructure Maintenance Window Days Of Week 
- Days during the week when maintenance should be performed.
- HoursOf []intDays 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- IsMonthly boolPatching Enabled 
- If true, enables the monthly patching option.
- LeadTime intIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
[]GetAutonomous Exadata Infrastructure Maintenance Window Month 
- Months during the year when maintenance should be performed.
- PatchingMode string
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
- The maintenance window scheduling preference.
- SkipRus []bool
- WeeksOf []intMonths 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction IntegerTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- daysOf List<GetWeeks Autonomous Exadata Infrastructure Maintenance Window Days Of Week> 
- Days during the week when maintenance should be performed.
- hoursOf List<Integer>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly BooleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime IntegerIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
List<GetAutonomous Exadata Infrastructure Maintenance Window Month> 
- Months during the year when maintenance should be performed.
- patchingMode String
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
- The maintenance window scheduling preference.
- skipRus List<Boolean>
- weeksOf List<Integer>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction numberTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- daysOf GetWeeks Autonomous Exadata Infrastructure Maintenance Window Days Of Week[] 
- Days during the week when maintenance should be performed.
- hoursOf number[]Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- isCustom booleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly booleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime numberIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
GetAutonomous Exadata Infrastructure Maintenance Window Month[] 
- Months during the year when maintenance should be performed.
- patchingMode string
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference string
- The maintenance window scheduling preference.
- skipRus boolean[]
- weeksOf number[]Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom_action_ inttimeout_ in_ mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days_of_ Sequence[Getweeks Autonomous Exadata Infrastructure Maintenance Window Days Of Week] 
- Days during the week when maintenance should be performed.
- hours_of_ Sequence[int]days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- is_custom_ boolaction_ timeout_ enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is_monthly_ boolpatching_ enabled 
- If true, enables the monthly patching option.
- lead_time_ intin_ weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
Sequence[GetAutonomous Exadata Infrastructure Maintenance Window Month] 
- Months during the year when maintenance should be performed.
- patching_mode str
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference str
- The maintenance window scheduling preference.
- skip_rus Sequence[bool]
- weeks_of_ Sequence[int]months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction NumberTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- daysOf List<Property Map>Weeks 
- Days during the week when maintenance should be performed.
- hoursOf List<Number>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly BooleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime NumberIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months List<Property Map>
- Months during the year when maintenance should be performed.
- patchingMode String
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
- The maintenance window scheduling preference.
- skipRus List<Boolean>
- weeksOf List<Number>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
GetAutonomousExadataInfrastructureMaintenanceWindowDaysOfWeek        
- 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.
GetAutonomousExadataInfrastructureMaintenanceWindowDetail      
- CustomAction intTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- DaysOf List<GetWeeks Autonomous Exadata Infrastructure Maintenance Window Detail Days Of Week> 
- Days during the week when maintenance should be performed.
- HoursOf List<int>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- IsMonthly boolPatching Enabled 
- If true, enables the monthly patching option.
- LeadTime intIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
List<GetAutonomous Exadata Infrastructure Maintenance Window Detail Month> 
- Months during the year when maintenance should be performed.
- PatchingMode string
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
- The maintenance window scheduling preference.
- SkipRus List<bool>
- WeeksOf List<int>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- CustomAction intTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- DaysOf []GetWeeks Autonomous Exadata Infrastructure Maintenance Window Detail Days Of Week 
- Days during the week when maintenance should be performed.
- HoursOf []intDays 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- IsMonthly boolPatching Enabled 
- If true, enables the monthly patching option.
- LeadTime intIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
[]GetAutonomous Exadata Infrastructure Maintenance Window Detail Month 
- Months during the year when maintenance should be performed.
- PatchingMode string
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
- The maintenance window scheduling preference.
- SkipRus []bool
- WeeksOf []intMonths 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction IntegerTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- daysOf List<GetWeeks Autonomous Exadata Infrastructure Maintenance Window Detail Days Of Week> 
- Days during the week when maintenance should be performed.
- hoursOf List<Integer>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly BooleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime IntegerIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
List<GetAutonomous Exadata Infrastructure Maintenance Window Detail Month> 
- Months during the year when maintenance should be performed.
- patchingMode String
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
- The maintenance window scheduling preference.
- skipRus List<Boolean>
- weeksOf List<Integer>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction numberTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- daysOf GetWeeks Autonomous Exadata Infrastructure Maintenance Window Detail Days Of Week[] 
- Days during the week when maintenance should be performed.
- hoursOf number[]Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- isCustom booleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly booleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime numberIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
GetAutonomous Exadata Infrastructure Maintenance Window Detail Month[] 
- Months during the year when maintenance should be performed.
- patchingMode string
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference string
- The maintenance window scheduling preference.
- skipRus boolean[]
- weeksOf number[]Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom_action_ inttimeout_ in_ mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days_of_ Sequence[Getweeks Autonomous Exadata Infrastructure Maintenance Window Detail Days Of Week] 
- Days during the week when maintenance should be performed.
- hours_of_ Sequence[int]days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- is_custom_ boolaction_ timeout_ enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is_monthly_ boolpatching_ enabled 
- If true, enables the monthly patching option.
- lead_time_ intin_ weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
Sequence[GetAutonomous Exadata Infrastructure Maintenance Window Detail Month] 
- Months during the year when maintenance should be performed.
- patching_mode str
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference str
- The maintenance window scheduling preference.
- skip_rus Sequence[bool]
- weeks_of_ Sequence[int]months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction NumberTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- daysOf List<Property Map>Weeks 
- Days during the week when maintenance should be performed.
- hoursOf List<Number>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- isMonthly BooleanPatching Enabled 
- If true, enables the monthly patching option.
- leadTime NumberIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months List<Property Map>
- Months during the year when maintenance should be performed.
- patchingMode String
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
- The maintenance window scheduling preference.
- skipRus List<Boolean>
- weeksOf List<Number>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
GetAutonomousExadataInfrastructureMaintenanceWindowDetailDaysOfWeek         
- 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.
GetAutonomousExadataInfrastructureMaintenanceWindowDetailMonth       
- 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.
GetAutonomousExadataInfrastructureMaintenanceWindowMonth      
- 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.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the ociTerraform Provider.