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 GetAutonomousExadataInfrastructure(ctx *Context, args *GetAutonomousExadataInfrastructureArgs, opts ...InvokeOption) (*GetAutonomousExadataInfrastructureResult, error)
func GetAutonomousExadataInfrastructureOutput(ctx *Context, args *GetAutonomousExadataInfrastructureOutputArgs, opts ...InvokeOption) GetAutonomousExadataInfrastructureResultOutput
> Note: This function is named GetAutonomousExadataInfrastructure
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)
// Output-based functions aren't available in Java yet
fn::invoke:
function: oci:Database/getAutonomousExadataInfrastructure:getAutonomousExadataInfrastructure
arguments:
# arguments dictionary
The following arguments are supported:
- Autonomous
Exadata stringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- Autonomous
Exadata stringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- autonomous
Exadata StringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- autonomous
Exadata stringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
- autonomous_
exadata_ strinfrastructure_ id - The Autonomous Exadata Infrastructure OCID.
- autonomous
Exadata StringInfrastructure Id - The Autonomous Exadata Infrastructure OCID.
getAutonomousExadataInfrastructure Result
The following output properties are available:
- Autonomous
Exadata stringInfrastructure Id - Availability
Domain string - The name of the availability domain that the Autonomous Exadata Infrastructure is located in.
- Compartment
Id string - The OCID of the compartment.
- Create
Async bool - Dictionary<string, string>
- 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-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.
- Last
Maintenance stringRun Id - The OCID of the last maintenance run.
- License
Model string - The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
- Lifecycle
Details string - Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
- Maintenance
Window List<GetDetails Autonomous Exadata Infrastructure Maintenance Window Detail> - Maintenance
Windows List<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 stringRun Id - The OCID of the next maintenance run.
- Nsg
Ids 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.
- Scan
Dns 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.
- Subnet
Id string - The OCID of the subnet the Autonomous Exadata Infrastructure is associated with.
- Time
Created string - The date and time the Autonomous Exadata Infrastructure was created.
- Zone
Id string - The OCID of the zone the Autonomous Exadata Infrastructure is associated with.
- Autonomous
Exadata stringInfrastructure Id - Availability
Domain string - The name of the availability domain that the Autonomous Exadata Infrastructure is located in.
- Compartment
Id string - The OCID of the compartment.
- Create
Async bool - map[string]string
- 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-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.
- Last
Maintenance stringRun Id - The OCID of the last maintenance run.
- License
Model string - The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
- Lifecycle
Details string - Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
- Maintenance
Window []GetDetails Autonomous Exadata Infrastructure Maintenance Window Detail - Maintenance
Windows []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 stringRun Id - The OCID of the next maintenance run.
- Nsg
Ids []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.
- Scan
Dns 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.
- Subnet
Id string - The OCID of the subnet the Autonomous Exadata Infrastructure is associated with.
- Time
Created string - The date and time the Autonomous Exadata Infrastructure was created.
- Zone
Id string - The OCID of the zone the Autonomous Exadata Infrastructure is associated with.
- autonomous
Exadata StringInfrastructure Id - availability
Domain String - The name of the availability domain that the Autonomous Exadata Infrastructure is located in.
- compartment
Id String - The OCID of the compartment.
- create
Async Boolean - Map<String,String>
- 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-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.
- last
Maintenance StringRun Id - The OCID of the last maintenance run.
- license
Model String - The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
- lifecycle
Details String - Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
- maintenance
Window List<GetDetails Autonomous Exadata Infrastructure Maintenance Window Detail> - maintenance
Windows List<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 StringRun Id - The OCID of the next maintenance run.
- nsg
Ids 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.
- scan
Dns 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.
- subnet
Id String - The OCID of the subnet the Autonomous Exadata Infrastructure is associated with.
- time
Created String - The date and time the Autonomous Exadata Infrastructure was created.
- zone
Id String - The OCID of the zone the Autonomous Exadata Infrastructure is associated with.
- autonomous
Exadata stringInfrastructure Id - availability
Domain string - The name of the availability domain that the Autonomous Exadata Infrastructure is located in.
- compartment
Id string - The OCID of the compartment.
- create
Async boolean - {[key: string]: string}
- 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-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.
- last
Maintenance stringRun Id - The OCID of the last maintenance run.
- license
Model string - The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
- lifecycle
Details string - Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
- maintenance
Window GetDetails Autonomous Exadata Infrastructure Maintenance Window Detail[] - maintenance
Windows 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 stringRun Id - The OCID of the next maintenance run.
- nsg
Ids 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.
- scan
Dns 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.
- subnet
Id string - The OCID of the subnet the Autonomous Exadata Infrastructure is associated with.
- time
Created string - The date and time the Autonomous Exadata Infrastructure was created.
- zone
Id 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[database.details Get Autonomous Exadata Infrastructure Maintenance Window Detail] - maintenance_
windows Sequence[database.Get Autonomous 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.
- autonomous
Exadata StringInfrastructure Id - availability
Domain String - The name of the availability domain that the Autonomous Exadata Infrastructure is located in.
- compartment
Id String - The OCID of the compartment.
- create
Async Boolean - Map<String>
- 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-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.
- last
Maintenance StringRun Id - The OCID of the last maintenance run.
- license
Model String - The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
- lifecycle
Details String - Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
- 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.
- next
Maintenance StringRun Id - The OCID of the next maintenance run.
- nsg
Ids 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.
- scan
Dns 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.
- subnet
Id String - The OCID of the subnet the Autonomous Exadata Infrastructure is associated with.
- time
Created String - The date and time the Autonomous Exadata Infrastructure was created.
- zone
Id String - The OCID of the zone the Autonomous Exadata Infrastructure is associated with.
Supporting Types
GetAutonomousExadataInfrastructureMaintenanceWindow
- 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 Exadata Infrastructure 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 Exadata Infrastructure 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.
- Skip
Rus List<bool> - 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 Exadata Infrastructure 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 Exadata Infrastructure 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.
- Skip
Rus []bool - 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 Exadata Infrastructure 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 Exadata Infrastructure 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.
- skip
Rus List<Boolean> - 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 Exadata Infrastructure 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 Exadata Infrastructure 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.
- skip
Rus boolean[] - 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_ Sequence[database.weeks Get 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[database.
Get Autonomous 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.
- 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.
- skip
Rus List<Boolean> - 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.
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
- 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 Exadata Infrastructure 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 Exadata Infrastructure 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.
- Skip
Rus List<bool> - 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 Exadata Infrastructure 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 Exadata Infrastructure 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.
- Skip
Rus []bool - 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 Exadata Infrastructure 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 Exadata Infrastructure 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.
- skip
Rus List<Boolean> - 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 Exadata Infrastructure 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 Exadata Infrastructure 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.
- skip
Rus boolean[] - 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_ Sequence[database.weeks Get 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[database.
Get Autonomous 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.
- 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.
- skip
Rus List<Boolean> - 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.
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
oci
Terraform Provider.