Oracle Cloud Infrastructure v1.41.0 published on Wednesday, Jun 19, 2024 by Pulumi
oci.Database.getMaintenanceRun
Explore with Pulumi AI
Oracle Cloud Infrastructure v1.41.0 published on Wednesday, Jun 19, 2024 by Pulumi
This data source provides details about a specific Maintenance Run resource in Oracle Cloud Infrastructure Database service.
Gets information about the specified maintenance run.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testMaintenanceRun = oci.Database.getMaintenanceRun({
maintenanceRunId: testMaintenanceRunOciDatabaseMaintenanceRun.id,
});
import pulumi
import pulumi_oci as oci
test_maintenance_run = oci.Database.get_maintenance_run(maintenance_run_id=test_maintenance_run_oci_database_maintenance_run["id"])
package main
import (
"github.com/pulumi/pulumi-oci/sdk/go/oci/Database"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := Database.GetMaintenanceRun(ctx, &database.GetMaintenanceRunArgs{
MaintenanceRunId: testMaintenanceRunOciDatabaseMaintenanceRun.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 testMaintenanceRun = Oci.Database.GetMaintenanceRun.Invoke(new()
{
MaintenanceRunId = testMaintenanceRunOciDatabaseMaintenanceRun.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.GetMaintenanceRunArgs;
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 testMaintenanceRun = DatabaseFunctions.getMaintenanceRun(GetMaintenanceRunArgs.builder()
.maintenanceRunId(testMaintenanceRunOciDatabaseMaintenanceRun.id())
.build());
}
}
variables:
testMaintenanceRun:
fn::invoke:
Function: oci:Database:getMaintenanceRun
Arguments:
maintenanceRunId: ${testMaintenanceRunOciDatabaseMaintenanceRun.id}
Using getMaintenanceRun
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 getMaintenanceRun(args: GetMaintenanceRunArgs, opts?: InvokeOptions): Promise<GetMaintenanceRunResult>
function getMaintenanceRunOutput(args: GetMaintenanceRunOutputArgs, opts?: InvokeOptions): Output<GetMaintenanceRunResult>
def get_maintenance_run(maintenance_run_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetMaintenanceRunResult
def get_maintenance_run_output(maintenance_run_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetMaintenanceRunResult]
func GetMaintenanceRun(ctx *Context, args *GetMaintenanceRunArgs, opts ...InvokeOption) (*GetMaintenanceRunResult, error)
func GetMaintenanceRunOutput(ctx *Context, args *GetMaintenanceRunOutputArgs, opts ...InvokeOption) GetMaintenanceRunResultOutput
> Note: This function is named GetMaintenanceRun
in the Go SDK.
public static class GetMaintenanceRun
{
public static Task<GetMaintenanceRunResult> InvokeAsync(GetMaintenanceRunArgs args, InvokeOptions? opts = null)
public static Output<GetMaintenanceRunResult> Invoke(GetMaintenanceRunInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetMaintenanceRunResult> getMaintenanceRun(GetMaintenanceRunArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: oci:Database/getMaintenanceRun:getMaintenanceRun
arguments:
# arguments dictionary
The following arguments are supported:
- Maintenance
Run stringId - The maintenance run OCID.
- Maintenance
Run stringId - The maintenance run OCID.
- maintenance
Run StringId - The maintenance run OCID.
- maintenance
Run stringId - The maintenance run OCID.
- maintenance_
run_ strid - The maintenance run OCID.
- maintenance
Run StringId - The maintenance run OCID.
getMaintenanceRun Result
The following output properties are available:
- Compartment
Id string - The OCID of the compartment.
- Current
Custom intAction Timeout In Mins - Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- Current
Patching stringComponent - The name of the current infrastruture component that is getting patched.
- Custom
Action intTimeout In Mins - Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120.
- Description string
- Description of the maintenance run.
- Display
Name string - The user-friendly name for the maintenance run.
- Estimated
Component stringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- Estimated
Patching List<GetTimes Maintenance Run Estimated Patching Time> - The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- Id string
- The OCID of the maintenance run.
- Is
Custom boolAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- Is
Dst boolFile Update Enabled - Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- Lifecycle
Details string - Additional information about the current lifecycle state.
- Maintenance
Run stringId - Maintenance
Subtype string - Maintenance sub-type.
- Maintenance
Type string - Maintenance type.
- Patch
Failure intCount - Contain the patch failure count.
- Patch
Id string - The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier
ru_patch_19.9.0.0_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - Patch
Type string - Patching
End stringTime - The time when the patching operation ended.
- Patching
Mode string - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Patching
Start stringTime - The time when the patching operation started.
- Patching
Status string - The status of the patching operation.
- Peer
Maintenance stringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- State string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- Target
Db stringServer Version - The target software version for the database server patching operation.
- Target
Resource stringId - The ID of the target resource on which the maintenance run occurs.
- Target
Resource stringType - The type of the target resource on which the maintenance run occurs.
- Target
Storage stringServer Version - The target Cell version that is to be patched to.
- Time
Ended string - The date and time the maintenance run was completed.
- Time
Scheduled string - The date and time the maintenance run is scheduled to occur.
- Time
Started string - The date and time the maintenance run starts.
- Compartment
Id string - The OCID of the compartment.
- Current
Custom intAction Timeout In Mins - Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- Current
Patching stringComponent - The name of the current infrastruture component that is getting patched.
- Custom
Action intTimeout In Mins - Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120.
- Description string
- Description of the maintenance run.
- Display
Name string - The user-friendly name for the maintenance run.
- Estimated
Component stringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- Estimated
Patching []GetTimes Maintenance Run Estimated Patching Time - The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- Id string
- The OCID of the maintenance run.
- Is
Custom boolAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- Is
Dst boolFile Update Enabled - Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- Lifecycle
Details string - Additional information about the current lifecycle state.
- Maintenance
Run stringId - Maintenance
Subtype string - Maintenance sub-type.
- Maintenance
Type string - Maintenance type.
- Patch
Failure intCount - Contain the patch failure count.
- Patch
Id string - The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier
ru_patch_19.9.0.0_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - Patch
Type string - Patching
End stringTime - The time when the patching operation ended.
- Patching
Mode string - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Patching
Start stringTime - The time when the patching operation started.
- Patching
Status string - The status of the patching operation.
- Peer
Maintenance stringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- State string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- Target
Db stringServer Version - The target software version for the database server patching operation.
- Target
Resource stringId - The ID of the target resource on which the maintenance run occurs.
- Target
Resource stringType - The type of the target resource on which the maintenance run occurs.
- Target
Storage stringServer Version - The target Cell version that is to be patched to.
- Time
Ended string - The date and time the maintenance run was completed.
- Time
Scheduled string - The date and time the maintenance run is scheduled to occur.
- Time
Started string - The date and time the maintenance run starts.
- compartment
Id String - The OCID of the compartment.
- current
Custom IntegerAction Timeout In Mins - Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- current
Patching StringComponent - The name of the current infrastruture component that is getting patched.
- custom
Action IntegerTimeout In Mins - Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120.
- description String
- Description of the maintenance run.
- display
Name String - The user-friendly name for the maintenance run.
- estimated
Component StringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- estimated
Patching List<GetTimes Maintenance Run Estimated Patching Time> - The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- id String
- The OCID of the maintenance run.
- is
Custom BooleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- is
Dst BooleanFile Update Enabled - Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- lifecycle
Details String - Additional information about the current lifecycle state.
- maintenance
Run StringId - maintenance
Subtype String - Maintenance sub-type.
- maintenance
Type String - Maintenance type.
- patch
Failure IntegerCount - Contain the patch failure count.
- patch
Id String - The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier
ru_patch_19.9.0.0_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - patch
Type String - patching
End StringTime - The time when the patching operation ended.
- patching
Mode String - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- patching
Start StringTime - The time when the patching operation started.
- patching
Status String - The status of the patching operation.
- peer
Maintenance StringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- state String
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- target
Db StringServer Version - The target software version for the database server patching operation.
- target
Resource StringId - The ID of the target resource on which the maintenance run occurs.
- target
Resource StringType - The type of the target resource on which the maintenance run occurs.
- target
Storage StringServer Version - The target Cell version that is to be patched to.
- time
Ended String - The date and time the maintenance run was completed.
- time
Scheduled String - The date and time the maintenance run is scheduled to occur.
- time
Started String - The date and time the maintenance run starts.
- compartment
Id string - The OCID of the compartment.
- current
Custom numberAction Timeout In Mins - Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- current
Patching stringComponent - The name of the current infrastruture component that is getting patched.
- custom
Action numberTimeout In Mins - Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120.
- description string
- Description of the maintenance run.
- display
Name string - The user-friendly name for the maintenance run.
- estimated
Component stringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- estimated
Patching GetTimes Maintenance Run Estimated Patching Time[] - The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- id string
- The OCID of the maintenance run.
- is
Custom booleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- is
Dst booleanFile Update Enabled - Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- lifecycle
Details string - Additional information about the current lifecycle state.
- maintenance
Run stringId - maintenance
Subtype string - Maintenance sub-type.
- maintenance
Type string - Maintenance type.
- patch
Failure numberCount - Contain the patch failure count.
- patch
Id string - The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier
ru_patch_19.9.0.0_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - patch
Type string - patching
End stringTime - The time when the patching operation ended.
- patching
Mode string - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- patching
Start stringTime - The time when the patching operation started.
- patching
Status string - The status of the patching operation.
- peer
Maintenance stringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- state string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- target
Db stringServer Version - The target software version for the database server patching operation.
- target
Resource stringId - The ID of the target resource on which the maintenance run occurs.
- target
Resource stringType - The type of the target resource on which the maintenance run occurs.
- target
Storage stringServer Version - The target Cell version that is to be patched to.
- time
Ended string - The date and time the maintenance run was completed.
- time
Scheduled string - The date and time the maintenance run is scheduled to occur.
- time
Started string - The date and time the maintenance run starts.
- compartment_
id str - The OCID of the compartment.
- current_
custom_ intaction_ timeout_ in_ mins - Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- current_
patching_ strcomponent - The name of the current infrastruture component that is getting patched.
- custom_
action_ inttimeout_ in_ mins - Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120.
- description str
- Description of the maintenance run.
- display_
name str - The user-friendly name for the maintenance run.
- estimated_
component_ strpatching_ start_ time - The estimated start time of the next infrastruture component patching operation.
- estimated_
patching_ Sequence[database.times Get Maintenance Run Estimated Patching Time] - The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- id str
- The OCID of the maintenance run.
- is_
custom_ boolaction_ timeout_ enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- is_
dst_ boolfile_ update_ enabled - Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- lifecycle_
details str - Additional information about the current lifecycle state.
- maintenance_
run_ strid - maintenance_
subtype str - Maintenance sub-type.
- maintenance_
type str - Maintenance type.
- patch_
failure_ intcount - Contain the patch failure count.
- patch_
id str - The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier
ru_patch_19.9.0.0_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - patch_
type str - patching_
end_ strtime - The time when the patching operation ended.
- patching_
mode str - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- patching_
start_ strtime - The time when the patching operation started.
- patching_
status str - The status of the patching operation.
- peer_
maintenance_ strrun_ id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- state str
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- target_
db_ strserver_ version - The target software version for the database server patching operation.
- target_
resource_ strid - The ID of the target resource on which the maintenance run occurs.
- target_
resource_ strtype - The type of the target resource on which the maintenance run occurs.
- target_
storage_ strserver_ version - The target Cell version that is to be patched to.
- time_
ended str - The date and time the maintenance run was completed.
- time_
scheduled str - The date and time the maintenance run is scheduled to occur.
- time_
started str - The date and time the maintenance run starts.
- compartment
Id String - The OCID of the compartment.
- current
Custom NumberAction Timeout In Mins - Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- current
Patching StringComponent - The name of the current infrastruture component that is getting patched.
- custom
Action NumberTimeout In Mins - Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120.
- description String
- Description of the maintenance run.
- display
Name String - The user-friendly name for the maintenance run.
- estimated
Component StringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- estimated
Patching List<Property Map>Times - The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- id String
- The OCID of the maintenance run.
- is
Custom BooleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- is
Dst BooleanFile Update Enabled - Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- lifecycle
Details String - Additional information about the current lifecycle state.
- maintenance
Run StringId - maintenance
Subtype String - Maintenance sub-type.
- maintenance
Type String - Maintenance type.
- patch
Failure NumberCount - Contain the patch failure count.
- patch
Id String - The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier
ru_patch_19.9.0.0_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - patch
Type String - patching
End StringTime - The time when the patching operation ended.
- patching
Mode String - Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- patching
Start StringTime - The time when the patching operation started.
- patching
Status String - The status of the patching operation.
- peer
Maintenance StringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- state String
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- target
Db StringServer Version - The target software version for the database server patching operation.
- target
Resource StringId - The ID of the target resource on which the maintenance run occurs.
- target
Resource StringType - The type of the target resource on which the maintenance run occurs.
- target
Storage StringServer Version - The target Cell version that is to be patched to.
- time
Ended String - The date and time the maintenance run was completed.
- time
Scheduled String - The date and time the maintenance run is scheduled to occur.
- time
Started String - The date and time the maintenance run starts.
Supporting Types
GetMaintenanceRunEstimatedPatchingTime
- Estimated
Db intServer Patching Time - The estimated time required in minutes for database server patching.
- Estimated
Network intSwitches Patching Time - The estimated time required in minutes for network switch patching.
- Estimated
Storage intServer Patching Time - The estimated time required in minutes for storage server patching.
- Total
Estimated intPatching Time - The estimated total time required in minutes for all patching operations.
- Estimated
Db intServer Patching Time - The estimated time required in minutes for database server patching.
- Estimated
Network intSwitches Patching Time - The estimated time required in minutes for network switch patching.
- Estimated
Storage intServer Patching Time - The estimated time required in minutes for storage server patching.
- Total
Estimated intPatching Time - The estimated total time required in minutes for all patching operations.
- estimated
Db IntegerServer Patching Time - The estimated time required in minutes for database server patching.
- estimated
Network IntegerSwitches Patching Time - The estimated time required in minutes for network switch patching.
- estimated
Storage IntegerServer Patching Time - The estimated time required in minutes for storage server patching.
- total
Estimated IntegerPatching Time - The estimated total time required in minutes for all patching operations.
- estimated
Db numberServer Patching Time - The estimated time required in minutes for database server patching.
- estimated
Network numberSwitches Patching Time - The estimated time required in minutes for network switch patching.
- estimated
Storage numberServer Patching Time - The estimated time required in minutes for storage server patching.
- total
Estimated numberPatching Time - The estimated total time required in minutes for all patching operations.
- estimated_
db_ intserver_ patching_ time - The estimated time required in minutes for database server patching.
- estimated_
network_ intswitches_ patching_ time - The estimated time required in minutes for network switch patching.
- estimated_
storage_ intserver_ patching_ time - The estimated time required in minutes for storage server patching.
- total_
estimated_ intpatching_ time - The estimated total time required in minutes for all patching operations.
- estimated
Db NumberServer Patching Time - The estimated time required in minutes for database server patching.
- estimated
Network NumberSwitches Patching Time - The estimated time required in minutes for network switch patching.
- estimated
Storage NumberServer Patching Time - The estimated time required in minutes for storage server patching.
- total
Estimated NumberPatching Time - The estimated total time required in minutes for all patching operations.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
oci
Terraform Provider.
Oracle Cloud Infrastructure v1.41.0 published on Wednesday, Jun 19, 2024 by Pulumi