oci.Database.MaintenanceRun
Explore with Pulumi AI
This resource provides the Maintenance Run resource in Oracle Cloud Infrastructure Database service.
Creates a maintenance run with one of the following: The latest available release update patch (RUP) for the Autonomous Container Database. The latest available RUP and DST time zone (TZ) file updates for the Autonomous Container Database. Creates a maintenance run to update the DST TZ file for the Autonomous Container Database.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testMaintenanceRun = new oci.database.MaintenanceRun("test_maintenance_run", {
    patchType: maintenanceRunPatchType,
    targetResourceId: testResource.id,
    timeScheduled: maintenanceRunTimeScheduled,
    compartmentId: compartmentId,
    databaseSoftwareImageId: testDatabaseSoftwareImage.id,
    isDstFileUpdateEnabled: maintenanceRunIsDstFileUpdateEnabled,
    patchingMode: maintenanceRunPatchingMode,
});
import pulumi
import pulumi_oci as oci
test_maintenance_run = oci.database.MaintenanceRun("test_maintenance_run",
    patch_type=maintenance_run_patch_type,
    target_resource_id=test_resource["id"],
    time_scheduled=maintenance_run_time_scheduled,
    compartment_id=compartment_id,
    database_software_image_id=test_database_software_image["id"],
    is_dst_file_update_enabled=maintenance_run_is_dst_file_update_enabled,
    patching_mode=maintenance_run_patching_mode)
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.NewMaintenanceRun(ctx, "test_maintenance_run", &database.MaintenanceRunArgs{
			PatchType:               pulumi.Any(maintenanceRunPatchType),
			TargetResourceId:        pulumi.Any(testResource.Id),
			TimeScheduled:           pulumi.Any(maintenanceRunTimeScheduled),
			CompartmentId:           pulumi.Any(compartmentId),
			DatabaseSoftwareImageId: pulumi.Any(testDatabaseSoftwareImage.Id),
			IsDstFileUpdateEnabled:  pulumi.Any(maintenanceRunIsDstFileUpdateEnabled),
			PatchingMode:            pulumi.Any(maintenanceRunPatchingMode),
		})
		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 = new Oci.Database.MaintenanceRun("test_maintenance_run", new()
    {
        PatchType = maintenanceRunPatchType,
        TargetResourceId = testResource.Id,
        TimeScheduled = maintenanceRunTimeScheduled,
        CompartmentId = compartmentId,
        DatabaseSoftwareImageId = testDatabaseSoftwareImage.Id,
        IsDstFileUpdateEnabled = maintenanceRunIsDstFileUpdateEnabled,
        PatchingMode = maintenanceRunPatchingMode,
    });
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Database.MaintenanceRun;
import com.pulumi.oci.Database.MaintenanceRunArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }
    public static void stack(Context ctx) {
        var testMaintenanceRun = new MaintenanceRun("testMaintenanceRun", MaintenanceRunArgs.builder()
            .patchType(maintenanceRunPatchType)
            .targetResourceId(testResource.id())
            .timeScheduled(maintenanceRunTimeScheduled)
            .compartmentId(compartmentId)
            .databaseSoftwareImageId(testDatabaseSoftwareImage.id())
            .isDstFileUpdateEnabled(maintenanceRunIsDstFileUpdateEnabled)
            .patchingMode(maintenanceRunPatchingMode)
            .build());
    }
}
resources:
  testMaintenanceRun:
    type: oci:Database:MaintenanceRun
    name: test_maintenance_run
    properties:
      patchType: ${maintenanceRunPatchType}
      targetResourceId: ${testResource.id}
      timeScheduled: ${maintenanceRunTimeScheduled}
      compartmentId: ${compartmentId}
      databaseSoftwareImageId: ${testDatabaseSoftwareImage.id}
      isDstFileUpdateEnabled: ${maintenanceRunIsDstFileUpdateEnabled}
      patchingMode: ${maintenanceRunPatchingMode}
Create MaintenanceRun Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new MaintenanceRun(name: string, args: MaintenanceRunArgs, opts?: CustomResourceOptions);@overload
def MaintenanceRun(resource_name: str,
                   args: MaintenanceRunArgs,
                   opts: Optional[ResourceOptions] = None)
@overload
def MaintenanceRun(resource_name: str,
                   opts: Optional[ResourceOptions] = None,
                   patch_type: Optional[str] = None,
                   target_resource_id: Optional[str] = None,
                   time_scheduled: Optional[str] = None,
                   compartment_id: Optional[str] = None,
                   database_software_image_id: Optional[str] = None,
                   is_dst_file_update_enabled: Optional[bool] = None,
                   patching_mode: Optional[str] = None)func NewMaintenanceRun(ctx *Context, name string, args MaintenanceRunArgs, opts ...ResourceOption) (*MaintenanceRun, error)public MaintenanceRun(string name, MaintenanceRunArgs args, CustomResourceOptions? opts = null)
public MaintenanceRun(String name, MaintenanceRunArgs args)
public MaintenanceRun(String name, MaintenanceRunArgs args, CustomResourceOptions options)
type: oci:Database:MaintenanceRun
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args MaintenanceRunArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args MaintenanceRunArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args MaintenanceRunArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args MaintenanceRunArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args MaintenanceRunArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var maintenanceRunResource = new Oci.Database.MaintenanceRun("maintenanceRunResource", new()
{
    PatchType = "string",
    TargetResourceId = "string",
    TimeScheduled = "string",
    CompartmentId = "string",
    DatabaseSoftwareImageId = "string",
    IsDstFileUpdateEnabled = false,
    PatchingMode = "string",
});
example, err := database.NewMaintenanceRun(ctx, "maintenanceRunResource", &database.MaintenanceRunArgs{
	PatchType:               pulumi.String("string"),
	TargetResourceId:        pulumi.String("string"),
	TimeScheduled:           pulumi.String("string"),
	CompartmentId:           pulumi.String("string"),
	DatabaseSoftwareImageId: pulumi.String("string"),
	IsDstFileUpdateEnabled:  pulumi.Bool(false),
	PatchingMode:            pulumi.String("string"),
})
var maintenanceRunResource = new MaintenanceRun("maintenanceRunResource", MaintenanceRunArgs.builder()
    .patchType("string")
    .targetResourceId("string")
    .timeScheduled("string")
    .compartmentId("string")
    .databaseSoftwareImageId("string")
    .isDstFileUpdateEnabled(false)
    .patchingMode("string")
    .build());
maintenance_run_resource = oci.database.MaintenanceRun("maintenanceRunResource",
    patch_type="string",
    target_resource_id="string",
    time_scheduled="string",
    compartment_id="string",
    database_software_image_id="string",
    is_dst_file_update_enabled=False,
    patching_mode="string")
const maintenanceRunResource = new oci.database.MaintenanceRun("maintenanceRunResource", {
    patchType: "string",
    targetResourceId: "string",
    timeScheduled: "string",
    compartmentId: "string",
    databaseSoftwareImageId: "string",
    isDstFileUpdateEnabled: false,
    patchingMode: "string",
});
type: oci:Database:MaintenanceRun
properties:
    compartmentId: string
    databaseSoftwareImageId: string
    isDstFileUpdateEnabled: false
    patchType: string
    patchingMode: string
    targetResourceId: string
    timeScheduled: string
MaintenanceRun Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The MaintenanceRun resource accepts the following input properties:
- PatchType string
- Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- TargetResource stringId 
- The ID of the target resource for which the maintenance run should be created.
- TimeScheduled string
- (Updatable) The date and time that update should be scheduled. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- CompartmentId string
- The OCID of the compartment containing the Maintenance Run.
- DatabaseSoftware stringImage Id 
- The Autonomous Database Software Image OCID
- IsDst 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.
- PatchingMode string
- (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING. - IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information. 
- PatchType string
- Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- TargetResource stringId 
- The ID of the target resource for which the maintenance run should be created.
- TimeScheduled string
- (Updatable) The date and time that update should be scheduled. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- CompartmentId string
- The OCID of the compartment containing the Maintenance Run.
- DatabaseSoftware stringImage Id 
- The Autonomous Database Software Image OCID
- IsDst 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.
- PatchingMode string
- (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING. - IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information. 
- patchType String
- Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- targetResource StringId 
- The ID of the target resource for which the maintenance run should be created.
- timeScheduled String
- (Updatable) The date and time that update should be scheduled. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- compartmentId String
- The OCID of the compartment containing the Maintenance Run.
- databaseSoftware StringImage Id 
- The Autonomous Database Software Image OCID
- isDst 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.
- patchingMode String
- (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING. - IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information. 
- patchType string
- Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- targetResource stringId 
- The ID of the target resource for which the maintenance run should be created.
- timeScheduled string
- (Updatable) The date and time that update should be scheduled. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- compartmentId string
- The OCID of the compartment containing the Maintenance Run.
- databaseSoftware stringImage Id 
- The Autonomous Database Software Image OCID
- isDst 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.
- patchingMode string
- (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING. - IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information. 
- patch_type str
- Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- target_resource_ strid 
- The ID of the target resource for which the maintenance run should be created.
- time_scheduled str
- (Updatable) The date and time that update should be scheduled. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- compartment_id str
- The OCID of the compartment containing the Maintenance Run.
- database_software_ strimage_ id 
- The Autonomous Database Software Image OCID
- 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.
- patching_mode str
- (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING. - IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information. 
- patchType String
- Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- targetResource StringId 
- The ID of the target resource for which the maintenance run should be created.
- timeScheduled String
- (Updatable) The date and time that update should be scheduled. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- compartmentId String
- The OCID of the compartment containing the Maintenance Run.
- databaseSoftware StringImage Id 
- The Autonomous Database Software Image OCID
- isDst 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.
- patchingMode String
- (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING. - IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information. 
Outputs
All input properties are implicitly available as output properties. Additionally, the MaintenanceRun resource produces the following output properties:
- CurrentCustom intAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- CurrentPatching stringComponent 
- The name of the current infrastruture component that is getting patched.
- CustomAction 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.
- DisplayName string
- The user-friendly name for the maintenance run.
- EstimatedComponent stringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- EstimatedPatching List<MaintenanceTimes 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 provider-assigned unique ID for this managed resource.
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- IsMaintenance boolRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- MaintenanceSubtype string
- Maintenance sub-type.
- MaintenanceType string
- Maintenance type.
- PatchFailure intCount 
- Contain the patch failure count.
- PatchId 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_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- PatchingEnd stringTime 
- The time when the patching operation ended.
- PatchingStart stringTime 
- The time when the patching operation started.
- PatchingStatus string
- The status of the patching operation.
- PeerMaintenance stringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- PeerMaintenance List<string>Run Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- State string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- TargetDb stringServer Version 
- The target software version for the database server patching operation.
- TargetResource stringType 
- The type of the target resource on which the maintenance run occurs.
- TargetStorage stringServer Version 
- The target Cell version that is to be patched to.
- TimeEnded string
- The date and time the maintenance run was completed.
- TimeStarted string
- The date and time the maintenance run starts.
- TotalTime intTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
- CurrentCustom intAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- CurrentPatching stringComponent 
- The name of the current infrastruture component that is getting patched.
- CustomAction 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.
- DisplayName string
- The user-friendly name for the maintenance run.
- EstimatedComponent stringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- EstimatedPatching []MaintenanceTimes 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 provider-assigned unique ID for this managed resource.
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- IsMaintenance boolRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- MaintenanceSubtype string
- Maintenance sub-type.
- MaintenanceType string
- Maintenance type.
- PatchFailure intCount 
- Contain the patch failure count.
- PatchId 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_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- PatchingEnd stringTime 
- The time when the patching operation ended.
- PatchingStart stringTime 
- The time when the patching operation started.
- PatchingStatus string
- The status of the patching operation.
- PeerMaintenance stringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- PeerMaintenance []stringRun Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- State string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- TargetDb stringServer Version 
- The target software version for the database server patching operation.
- TargetResource stringType 
- The type of the target resource on which the maintenance run occurs.
- TargetStorage stringServer Version 
- The target Cell version that is to be patched to.
- TimeEnded string
- The date and time the maintenance run was completed.
- TimeStarted string
- The date and time the maintenance run starts.
- TotalTime intTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
- currentCustom IntegerAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- currentPatching StringComponent 
- The name of the current infrastruture component that is getting patched.
- customAction 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.
- displayName String
- The user-friendly name for the maintenance run.
- estimatedComponent StringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- estimatedPatching List<MaintenanceTimes 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 provider-assigned unique ID for this managed resource.
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- isMaintenance BooleanRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- maintenanceSubtype String
- Maintenance sub-type.
- maintenanceType String
- Maintenance type.
- patchFailure IntegerCount 
- Contain the patch failure count.
- patchId 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_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- patchingEnd StringTime 
- The time when the patching operation ended.
- patchingStart StringTime 
- The time when the patching operation started.
- patchingStatus String
- The status of the patching operation.
- peerMaintenance StringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- peerMaintenance List<String>Run Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- state String
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- targetDb StringServer Version 
- The target software version for the database server patching operation.
- targetResource StringType 
- The type of the target resource on which the maintenance run occurs.
- targetStorage StringServer Version 
- The target Cell version that is to be patched to.
- timeEnded String
- The date and time the maintenance run was completed.
- timeStarted String
- The date and time the maintenance run starts.
- totalTime IntegerTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
- currentCustom numberAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- currentPatching stringComponent 
- The name of the current infrastruture component that is getting patched.
- customAction 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.
- displayName string
- The user-friendly name for the maintenance run.
- estimatedComponent stringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- estimatedPatching MaintenanceTimes 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 provider-assigned unique ID for this managed resource.
- isCustom booleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- isMaintenance booleanRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- lifecycleDetails string
- Additional information about the current lifecycle state.
- maintenanceSubtype string
- Maintenance sub-type.
- maintenanceType string
- Maintenance type.
- patchFailure numberCount 
- Contain the patch failure count.
- patchId 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_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- patchingEnd stringTime 
- The time when the patching operation ended.
- patchingStart stringTime 
- The time when the patching operation started.
- patchingStatus string
- The status of the patching operation.
- peerMaintenance stringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- peerMaintenance string[]Run Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- state string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- targetDb stringServer Version 
- The target software version for the database server patching operation.
- targetResource stringType 
- The type of the target resource on which the maintenance run occurs.
- targetStorage stringServer Version 
- The target Cell version that is to be patched to.
- timeEnded string
- The date and time the maintenance run was completed.
- timeStarted string
- The date and time the maintenance run starts.
- totalTime numberTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
- 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[Maintenancetimes 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 provider-assigned unique ID for this managed resource.
- is_custom_ boolaction_ timeout_ enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- is_maintenance_ boolrun_ granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- lifecycle_details str
- Additional information about the current lifecycle state.
- 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_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- patching_end_ strtime 
- The time when the patching operation ended.
- 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.
- peer_maintenance_ Sequence[str]run_ ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- 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_ 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_started str
- The date and time the maintenance run starts.
- total_time_ inttaken_ in_ mins 
- The total time taken by corresponding resource activity in minutes.
- currentCustom NumberAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- currentPatching StringComponent 
- The name of the current infrastruture component that is getting patched.
- customAction 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.
- displayName String
- The user-friendly name for the maintenance run.
- estimatedComponent StringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- estimatedPatching 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 provider-assigned unique ID for this managed resource.
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- isMaintenance BooleanRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- maintenanceSubtype String
- Maintenance sub-type.
- maintenanceType String
- Maintenance type.
- patchFailure NumberCount 
- Contain the patch failure count.
- patchId 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_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- patchingEnd StringTime 
- The time when the patching operation ended.
- patchingStart StringTime 
- The time when the patching operation started.
- patchingStatus String
- The status of the patching operation.
- peerMaintenance StringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- peerMaintenance List<String>Run Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- state String
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- targetDb StringServer Version 
- The target software version for the database server patching operation.
- targetResource StringType 
- The type of the target resource on which the maintenance run occurs.
- targetStorage StringServer Version 
- The target Cell version that is to be patched to.
- timeEnded String
- The date and time the maintenance run was completed.
- timeStarted String
- The date and time the maintenance run starts.
- totalTime NumberTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
Look up Existing MaintenanceRun Resource
Get an existing MaintenanceRun resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: MaintenanceRunState, opts?: CustomResourceOptions): MaintenanceRun@staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        compartment_id: Optional[str] = None,
        current_custom_action_timeout_in_mins: Optional[int] = None,
        current_patching_component: Optional[str] = None,
        custom_action_timeout_in_mins: Optional[int] = None,
        database_software_image_id: Optional[str] = None,
        description: Optional[str] = None,
        display_name: Optional[str] = None,
        estimated_component_patching_start_time: Optional[str] = None,
        estimated_patching_times: Optional[Sequence[MaintenanceRunEstimatedPatchingTimeArgs]] = None,
        is_custom_action_timeout_enabled: Optional[bool] = None,
        is_dst_file_update_enabled: Optional[bool] = None,
        is_maintenance_run_granular: Optional[bool] = None,
        lifecycle_details: Optional[str] = None,
        maintenance_subtype: Optional[str] = None,
        maintenance_type: Optional[str] = None,
        patch_failure_count: Optional[int] = None,
        patch_id: Optional[str] = None,
        patch_type: Optional[str] = None,
        patching_end_time: Optional[str] = None,
        patching_mode: Optional[str] = None,
        patching_start_time: Optional[str] = None,
        patching_status: Optional[str] = None,
        peer_maintenance_run_id: Optional[str] = None,
        peer_maintenance_run_ids: Optional[Sequence[str]] = None,
        state: Optional[str] = None,
        target_db_server_version: Optional[str] = None,
        target_resource_id: Optional[str] = None,
        target_resource_type: Optional[str] = None,
        target_storage_server_version: Optional[str] = None,
        time_ended: Optional[str] = None,
        time_scheduled: Optional[str] = None,
        time_started: Optional[str] = None,
        total_time_taken_in_mins: Optional[int] = None) -> MaintenanceRunfunc GetMaintenanceRun(ctx *Context, name string, id IDInput, state *MaintenanceRunState, opts ...ResourceOption) (*MaintenanceRun, error)public static MaintenanceRun Get(string name, Input<string> id, MaintenanceRunState? state, CustomResourceOptions? opts = null)public static MaintenanceRun get(String name, Output<String> id, MaintenanceRunState state, CustomResourceOptions options)resources:  _:    type: oci:Database:MaintenanceRun    get:      id: ${id}- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- CompartmentId string
- The OCID of the compartment containing the Maintenance Run.
- CurrentCustom intAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- CurrentPatching stringComponent 
- The name of the current infrastruture component that is getting patched.
- CustomAction 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.
- DatabaseSoftware stringImage Id 
- The Autonomous Database Software Image OCID
- Description string
- Description of the maintenance run.
- DisplayName string
- The user-friendly name for the maintenance run.
- EstimatedComponent stringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- EstimatedPatching List<MaintenanceTimes Run Estimated Patching Time> 
- The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- IsDst 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.
- IsMaintenance boolRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- MaintenanceSubtype string
- Maintenance sub-type.
- MaintenanceType string
- Maintenance type.
- PatchFailure intCount 
- Contain the patch failure count.
- PatchId 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_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- PatchType string
- Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- PatchingEnd stringTime 
- The time when the patching operation ended.
- PatchingMode string
- (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING. - IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information. 
- PatchingStart stringTime 
- The time when the patching operation started.
- PatchingStatus string
- The status of the patching operation.
- PeerMaintenance stringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- PeerMaintenance List<string>Run Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- State string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- TargetDb stringServer Version 
- The target software version for the database server patching operation.
- TargetResource stringId 
- The ID of the target resource for which the maintenance run should be created.
- TargetResource stringType 
- The type of the target resource on which the maintenance run occurs.
- TargetStorage stringServer Version 
- The target Cell version that is to be patched to.
- TimeEnded string
- The date and time the maintenance run was completed.
- TimeScheduled string
- (Updatable) The date and time that update should be scheduled. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- TimeStarted string
- The date and time the maintenance run starts.
- TotalTime intTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
- CompartmentId string
- The OCID of the compartment containing the Maintenance Run.
- CurrentCustom intAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- CurrentPatching stringComponent 
- The name of the current infrastruture component that is getting patched.
- CustomAction 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.
- DatabaseSoftware stringImage Id 
- The Autonomous Database Software Image OCID
- Description string
- Description of the maintenance run.
- DisplayName string
- The user-friendly name for the maintenance run.
- EstimatedComponent stringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- EstimatedPatching []MaintenanceTimes Run Estimated Patching Time Args 
- The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- IsDst 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.
- IsMaintenance boolRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- MaintenanceSubtype string
- Maintenance sub-type.
- MaintenanceType string
- Maintenance type.
- PatchFailure intCount 
- Contain the patch failure count.
- PatchId 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_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- PatchType string
- Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- PatchingEnd stringTime 
- The time when the patching operation ended.
- PatchingMode string
- (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING. - IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information. 
- PatchingStart stringTime 
- The time when the patching operation started.
- PatchingStatus string
- The status of the patching operation.
- PeerMaintenance stringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- PeerMaintenance []stringRun Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- State string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- TargetDb stringServer Version 
- The target software version for the database server patching operation.
- TargetResource stringId 
- The ID of the target resource for which the maintenance run should be created.
- TargetResource stringType 
- The type of the target resource on which the maintenance run occurs.
- TargetStorage stringServer Version 
- The target Cell version that is to be patched to.
- TimeEnded string
- The date and time the maintenance run was completed.
- TimeScheduled string
- (Updatable) The date and time that update should be scheduled. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- TimeStarted string
- The date and time the maintenance run starts.
- TotalTime intTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
- compartmentId String
- The OCID of the compartment containing the Maintenance Run.
- currentCustom IntegerAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- currentPatching StringComponent 
- The name of the current infrastruture component that is getting patched.
- customAction 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.
- databaseSoftware StringImage Id 
- The Autonomous Database Software Image OCID
- description String
- Description of the maintenance run.
- displayName String
- The user-friendly name for the maintenance run.
- estimatedComponent StringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- estimatedPatching List<MaintenanceTimes Run Estimated Patching Time> 
- The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- isDst 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.
- isMaintenance BooleanRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- maintenanceSubtype String
- Maintenance sub-type.
- maintenanceType String
- Maintenance type.
- patchFailure IntegerCount 
- Contain the patch failure count.
- patchId 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_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- patchType String
- Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- patchingEnd StringTime 
- The time when the patching operation ended.
- patchingMode String
- (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING. - IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information. 
- patchingStart StringTime 
- The time when the patching operation started.
- patchingStatus String
- The status of the patching operation.
- peerMaintenance StringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- peerMaintenance List<String>Run Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- state String
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- targetDb StringServer Version 
- The target software version for the database server patching operation.
- targetResource StringId 
- The ID of the target resource for which the maintenance run should be created.
- targetResource StringType 
- The type of the target resource on which the maintenance run occurs.
- targetStorage StringServer Version 
- The target Cell version that is to be patched to.
- timeEnded String
- The date and time the maintenance run was completed.
- timeScheduled String
- (Updatable) The date and time that update should be scheduled. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- timeStarted String
- The date and time the maintenance run starts.
- totalTime IntegerTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
- compartmentId string
- The OCID of the compartment containing the Maintenance Run.
- currentCustom numberAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- currentPatching stringComponent 
- The name of the current infrastruture component that is getting patched.
- customAction 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.
- databaseSoftware stringImage Id 
- The Autonomous Database Software Image OCID
- description string
- Description of the maintenance run.
- displayName string
- The user-friendly name for the maintenance run.
- estimatedComponent stringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- estimatedPatching MaintenanceTimes Run Estimated Patching Time[] 
- The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- isCustom booleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- isDst 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.
- isMaintenance booleanRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- lifecycleDetails string
- Additional information about the current lifecycle state.
- maintenanceSubtype string
- Maintenance sub-type.
- maintenanceType string
- Maintenance type.
- patchFailure numberCount 
- Contain the patch failure count.
- patchId 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_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- patchType string
- Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- patchingEnd stringTime 
- The time when the patching operation ended.
- patchingMode string
- (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING. - IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information. 
- patchingStart stringTime 
- The time when the patching operation started.
- patchingStatus string
- The status of the patching operation.
- peerMaintenance stringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- peerMaintenance string[]Run Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- state string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- targetDb stringServer Version 
- The target software version for the database server patching operation.
- targetResource stringId 
- The ID of the target resource for which the maintenance run should be created.
- targetResource stringType 
- The type of the target resource on which the maintenance run occurs.
- targetStorage stringServer Version 
- The target Cell version that is to be patched to.
- timeEnded string
- The date and time the maintenance run was completed.
- timeScheduled string
- (Updatable) The date and time that update should be scheduled. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- timeStarted string
- The date and time the maintenance run starts.
- totalTime numberTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
- compartment_id str
- The OCID of the compartment containing the Maintenance Run.
- 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.
- database_software_ strimage_ id 
- The Autonomous Database Software Image OCID
- 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[Maintenancetimes Run Estimated Patching Time Args] 
- The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- 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.
- is_maintenance_ boolrun_ granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- lifecycle_details str
- Additional information about the current lifecycle state.
- 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_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- patch_type str
- Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- patching_end_ strtime 
- The time when the patching operation ended.
- patching_mode str
- (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING. - IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information. 
- 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.
- peer_maintenance_ Sequence[str]run_ ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- 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 for which the maintenance run should be created.
- 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
- (Updatable) The date and time that update should be scheduled. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- time_started str
- The date and time the maintenance run starts.
- total_time_ inttaken_ in_ mins 
- The total time taken by corresponding resource activity in minutes.
- compartmentId String
- The OCID of the compartment containing the Maintenance Run.
- currentCustom NumberAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- currentPatching StringComponent 
- The name of the current infrastruture component that is getting patched.
- customAction 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.
- databaseSoftware StringImage Id 
- The Autonomous Database Software Image OCID
- description String
- Description of the maintenance run.
- displayName String
- The user-friendly name for the maintenance run.
- estimatedComponent StringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- estimatedPatching List<Property Map>Times 
- The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- isDst 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.
- isMaintenance BooleanRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- maintenanceSubtype String
- Maintenance sub-type.
- maintenanceType String
- Maintenance type.
- patchFailure NumberCount 
- Contain the patch failure count.
- patchId 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_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- patchType String
- Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- patchingEnd StringTime 
- The time when the patching operation ended.
- patchingMode String
- (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING. - IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information. 
- patchingStart StringTime 
- The time when the patching operation started.
- patchingStatus String
- The status of the patching operation.
- peerMaintenance StringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- peerMaintenance List<String>Run Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- state String
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- targetDb StringServer Version 
- The target software version for the database server patching operation.
- targetResource StringId 
- The ID of the target resource for which the maintenance run should be created.
- targetResource StringType 
- The type of the target resource on which the maintenance run occurs.
- targetStorage StringServer Version 
- The target Cell version that is to be patched to.
- timeEnded String
- The date and time the maintenance run was completed.
- timeScheduled String
- (Updatable) The date and time that update should be scheduled. - ** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values 
- timeStarted String
- The date and time the maintenance run starts.
- totalTime NumberTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
Supporting Types
MaintenanceRunEstimatedPatchingTime, MaintenanceRunEstimatedPatchingTimeArgs          
- EstimatedDb intServer Patching Time 
- The estimated time required in minutes for database server patching.
- EstimatedNetwork intSwitches Patching Time 
- The estimated time required in minutes for network switch patching.
- EstimatedStorage intServer Patching Time 
- The estimated time required in minutes for storage server patching.
- TotalEstimated intPatching Time 
- The estimated total time required in minutes for all patching operations.
- EstimatedDb intServer Patching Time 
- The estimated time required in minutes for database server patching.
- EstimatedNetwork intSwitches Patching Time 
- The estimated time required in minutes for network switch patching.
- EstimatedStorage intServer Patching Time 
- The estimated time required in minutes for storage server patching.
- TotalEstimated intPatching Time 
- The estimated total time required in minutes for all patching operations.
- estimatedDb IntegerServer Patching Time 
- The estimated time required in minutes for database server patching.
- estimatedNetwork IntegerSwitches Patching Time 
- The estimated time required in minutes for network switch patching.
- estimatedStorage IntegerServer Patching Time 
- The estimated time required in minutes for storage server patching.
- totalEstimated IntegerPatching Time 
- The estimated total time required in minutes for all patching operations.
- estimatedDb numberServer Patching Time 
- The estimated time required in minutes for database server patching.
- estimatedNetwork numberSwitches Patching Time 
- The estimated time required in minutes for network switch patching.
- estimatedStorage numberServer Patching Time 
- The estimated time required in minutes for storage server patching.
- totalEstimated 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.
- estimatedDb NumberServer Patching Time 
- The estimated time required in minutes for database server patching.
- estimatedNetwork NumberSwitches Patching Time 
- The estimated time required in minutes for network switch patching.
- estimatedStorage NumberServer Patching Time 
- The estimated time required in minutes for storage server patching.
- totalEstimated NumberPatching Time 
- The estimated total time required in minutes for all patching operations.
Import
MaintenanceRuns can be imported using the id, e.g.
$ pulumi import oci:Database/maintenanceRun:MaintenanceRun test_maintenance_run "id"
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the ociTerraform Provider.