1. Packages
  2. Oracle Cloud Infrastructure
  3. API Docs
  4. Database
  5. getDatabasePdbConversionHistoryEntry
Oracle Cloud Infrastructure v2.17.0 published on Friday, Nov 15, 2024 by Pulumi

oci.Database.getDatabasePdbConversionHistoryEntry

Explore with Pulumi AI

oci logo
Oracle Cloud Infrastructure v2.17.0 published on Friday, Nov 15, 2024 by Pulumi

    This data source provides details about a specific Database Pdb Conversion History Entry resource in Oracle Cloud Infrastructure Database service.

    Gets the details of operations performed to convert the specified database from non-container (non-CDB) to pluggable (PDB).

    Example Usage

    import * as pulumi from "@pulumi/pulumi";
    import * as oci from "@pulumi/oci";
    
    const testDatabasePdbConversionHistoryEntry = oci.Database.getDatabasePdbConversionHistoryEntry({
        databaseId: testDatabase.id,
        pdbConversionHistoryEntryId: testPdbConversionHistoryEntry.id,
    });
    
    import pulumi
    import pulumi_oci as oci
    
    test_database_pdb_conversion_history_entry = oci.Database.get_database_pdb_conversion_history_entry(database_id=test_database["id"],
        pdb_conversion_history_entry_id=test_pdb_conversion_history_entry["id"])
    
    package main
    
    import (
    	"github.com/pulumi/pulumi-oci/sdk/v2/go/oci/Database"
    	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
    )
    
    func main() {
    	pulumi.Run(func(ctx *pulumi.Context) error {
    		_, err := Database.GetDatabasePdbConversionHistoryEntry(ctx, &database.GetDatabasePdbConversionHistoryEntryArgs{
    			DatabaseId:                  testDatabase.Id,
    			PdbConversionHistoryEntryId: testPdbConversionHistoryEntry.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 testDatabasePdbConversionHistoryEntry = Oci.Database.GetDatabasePdbConversionHistoryEntry.Invoke(new()
        {
            DatabaseId = testDatabase.Id,
            PdbConversionHistoryEntryId = testPdbConversionHistoryEntry.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.GetDatabasePdbConversionHistoryEntryArgs;
    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 testDatabasePdbConversionHistoryEntry = DatabaseFunctions.getDatabasePdbConversionHistoryEntry(GetDatabasePdbConversionHistoryEntryArgs.builder()
                .databaseId(testDatabase.id())
                .pdbConversionHistoryEntryId(testPdbConversionHistoryEntry.id())
                .build());
    
        }
    }
    
    variables:
      testDatabasePdbConversionHistoryEntry:
        fn::invoke:
          Function: oci:Database:getDatabasePdbConversionHistoryEntry
          Arguments:
            databaseId: ${testDatabase.id}
            pdbConversionHistoryEntryId: ${testPdbConversionHistoryEntry.id}
    

    Using getDatabasePdbConversionHistoryEntry

    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 getDatabasePdbConversionHistoryEntry(args: GetDatabasePdbConversionHistoryEntryArgs, opts?: InvokeOptions): Promise<GetDatabasePdbConversionHistoryEntryResult>
    function getDatabasePdbConversionHistoryEntryOutput(args: GetDatabasePdbConversionHistoryEntryOutputArgs, opts?: InvokeOptions): Output<GetDatabasePdbConversionHistoryEntryResult>
    def get_database_pdb_conversion_history_entry(database_id: Optional[str] = None,
                                                  pdb_conversion_history_entry_id: Optional[str] = None,
                                                  opts: Optional[InvokeOptions] = None) -> GetDatabasePdbConversionHistoryEntryResult
    def get_database_pdb_conversion_history_entry_output(database_id: Optional[pulumi.Input[str]] = None,
                                                  pdb_conversion_history_entry_id: Optional[pulumi.Input[str]] = None,
                                                  opts: Optional[InvokeOptions] = None) -> Output[GetDatabasePdbConversionHistoryEntryResult]
    func GetDatabasePdbConversionHistoryEntry(ctx *Context, args *GetDatabasePdbConversionHistoryEntryArgs, opts ...InvokeOption) (*GetDatabasePdbConversionHistoryEntryResult, error)
    func GetDatabasePdbConversionHistoryEntryOutput(ctx *Context, args *GetDatabasePdbConversionHistoryEntryOutputArgs, opts ...InvokeOption) GetDatabasePdbConversionHistoryEntryResultOutput

    > Note: This function is named GetDatabasePdbConversionHistoryEntry in the Go SDK.

    public static class GetDatabasePdbConversionHistoryEntry 
    {
        public static Task<GetDatabasePdbConversionHistoryEntryResult> InvokeAsync(GetDatabasePdbConversionHistoryEntryArgs args, InvokeOptions? opts = null)
        public static Output<GetDatabasePdbConversionHistoryEntryResult> Invoke(GetDatabasePdbConversionHistoryEntryInvokeArgs args, InvokeOptions? opts = null)
    }
    public static CompletableFuture<GetDatabasePdbConversionHistoryEntryResult> getDatabasePdbConversionHistoryEntry(GetDatabasePdbConversionHistoryEntryArgs args, InvokeOptions options)
    // Output-based functions aren't available in Java yet
    
    fn::invoke:
      function: oci:Database/getDatabasePdbConversionHistoryEntry:getDatabasePdbConversionHistoryEntry
      arguments:
        # arguments dictionary

    The following arguments are supported:

    DatabaseId string
    The database OCID.
    PdbConversionHistoryEntryId string
    The database conversion history OCID.
    DatabaseId string
    The database OCID.
    PdbConversionHistoryEntryId string
    The database conversion history OCID.
    databaseId String
    The database OCID.
    pdbConversionHistoryEntryId String
    The database conversion history OCID.
    databaseId string
    The database OCID.
    pdbConversionHistoryEntryId string
    The database conversion history OCID.
    database_id str
    The database OCID.
    pdb_conversion_history_entry_id str
    The database conversion history OCID.
    databaseId String
    The database OCID.
    pdbConversionHistoryEntryId String
    The database conversion history OCID.

    getDatabasePdbConversionHistoryEntry Result

    The following output properties are available:

    Action string
    The operations used to convert a non-container database to a pluggable database.

    • Use PRECHECK to run a pre-check operation on non-container database prior to converting it into a pluggable database.
    • Use CONVERT to convert a non-container database into a pluggable database.
    • Use SYNC if the non-container database was manually converted into a pluggable database using the dbcli command-line utility. Databases may need to be converted manually if the CONVERT action fails when converting a non-container database using the API.
    • Use SYNC_ROLLBACK if the conversion of a non-container database into a pluggable database was manually rolled back using the dbcli command line utility. Conversions may need to be manually rolled back if the CONVERT action fails when converting a non-container database using the API.
    AdditionalCdbParams string
    Additional container database parameter.
    CdbName string
    The database name. The name must begin with an alphabetic character and can contain a maximum of 8 alphanumeric characters. Special characters are not permitted. The database name must be unique in the tenancy.
    DatabaseId string
    Id string
    The provider-assigned unique ID for this managed resource.
    LifecycleDetails string
    Additional information about the current lifecycle state for the conversion operation.
    PdbConversionHistoryEntryId string
    SourceDatabaseId string
    The OCID of the database.
    State string
    Status of an operation performed during the conversion of a non-container database to a pluggable database.
    Target string
    The target container database of the pluggable database created by the database conversion operation. Currently, the database conversion operation only supports creating the pluggable database in a new container database.

    • Use NEW_DATABASE to specify that the pluggable database be created within a new container database in the same database home.
    TargetDatabaseId string
    The OCID of the database.
    TimeEnded string
    The date and time when the database conversion operation ended.
    TimeStarted string
    The date and time when the database conversion operation started.
    Action string
    The operations used to convert a non-container database to a pluggable database.

    • Use PRECHECK to run a pre-check operation on non-container database prior to converting it into a pluggable database.
    • Use CONVERT to convert a non-container database into a pluggable database.
    • Use SYNC if the non-container database was manually converted into a pluggable database using the dbcli command-line utility. Databases may need to be converted manually if the CONVERT action fails when converting a non-container database using the API.
    • Use SYNC_ROLLBACK if the conversion of a non-container database into a pluggable database was manually rolled back using the dbcli command line utility. Conversions may need to be manually rolled back if the CONVERT action fails when converting a non-container database using the API.
    AdditionalCdbParams string
    Additional container database parameter.
    CdbName string
    The database name. The name must begin with an alphabetic character and can contain a maximum of 8 alphanumeric characters. Special characters are not permitted. The database name must be unique in the tenancy.
    DatabaseId string
    Id string
    The provider-assigned unique ID for this managed resource.
    LifecycleDetails string
    Additional information about the current lifecycle state for the conversion operation.
    PdbConversionHistoryEntryId string
    SourceDatabaseId string
    The OCID of the database.
    State string
    Status of an operation performed during the conversion of a non-container database to a pluggable database.
    Target string
    The target container database of the pluggable database created by the database conversion operation. Currently, the database conversion operation only supports creating the pluggable database in a new container database.

    • Use NEW_DATABASE to specify that the pluggable database be created within a new container database in the same database home.
    TargetDatabaseId string
    The OCID of the database.
    TimeEnded string
    The date and time when the database conversion operation ended.
    TimeStarted string
    The date and time when the database conversion operation started.
    action String
    The operations used to convert a non-container database to a pluggable database.

    • Use PRECHECK to run a pre-check operation on non-container database prior to converting it into a pluggable database.
    • Use CONVERT to convert a non-container database into a pluggable database.
    • Use SYNC if the non-container database was manually converted into a pluggable database using the dbcli command-line utility. Databases may need to be converted manually if the CONVERT action fails when converting a non-container database using the API.
    • Use SYNC_ROLLBACK if the conversion of a non-container database into a pluggable database was manually rolled back using the dbcli command line utility. Conversions may need to be manually rolled back if the CONVERT action fails when converting a non-container database using the API.
    additionalCdbParams String
    Additional container database parameter.
    cdbName String
    The database name. The name must begin with an alphabetic character and can contain a maximum of 8 alphanumeric characters. Special characters are not permitted. The database name must be unique in the tenancy.
    databaseId String
    id String
    The provider-assigned unique ID for this managed resource.
    lifecycleDetails String
    Additional information about the current lifecycle state for the conversion operation.
    pdbConversionHistoryEntryId String
    sourceDatabaseId String
    The OCID of the database.
    state String
    Status of an operation performed during the conversion of a non-container database to a pluggable database.
    target String
    The target container database of the pluggable database created by the database conversion operation. Currently, the database conversion operation only supports creating the pluggable database in a new container database.

    • Use NEW_DATABASE to specify that the pluggable database be created within a new container database in the same database home.
    targetDatabaseId String
    The OCID of the database.
    timeEnded String
    The date and time when the database conversion operation ended.
    timeStarted String
    The date and time when the database conversion operation started.
    action string
    The operations used to convert a non-container database to a pluggable database.

    • Use PRECHECK to run a pre-check operation on non-container database prior to converting it into a pluggable database.
    • Use CONVERT to convert a non-container database into a pluggable database.
    • Use SYNC if the non-container database was manually converted into a pluggable database using the dbcli command-line utility. Databases may need to be converted manually if the CONVERT action fails when converting a non-container database using the API.
    • Use SYNC_ROLLBACK if the conversion of a non-container database into a pluggable database was manually rolled back using the dbcli command line utility. Conversions may need to be manually rolled back if the CONVERT action fails when converting a non-container database using the API.
    additionalCdbParams string
    Additional container database parameter.
    cdbName string
    The database name. The name must begin with an alphabetic character and can contain a maximum of 8 alphanumeric characters. Special characters are not permitted. The database name must be unique in the tenancy.
    databaseId string
    id string
    The provider-assigned unique ID for this managed resource.
    lifecycleDetails string
    Additional information about the current lifecycle state for the conversion operation.
    pdbConversionHistoryEntryId string
    sourceDatabaseId string
    The OCID of the database.
    state string
    Status of an operation performed during the conversion of a non-container database to a pluggable database.
    target string
    The target container database of the pluggable database created by the database conversion operation. Currently, the database conversion operation only supports creating the pluggable database in a new container database.

    • Use NEW_DATABASE to specify that the pluggable database be created within a new container database in the same database home.
    targetDatabaseId string
    The OCID of the database.
    timeEnded string
    The date and time when the database conversion operation ended.
    timeStarted string
    The date and time when the database conversion operation started.
    action str
    The operations used to convert a non-container database to a pluggable database.

    • Use PRECHECK to run a pre-check operation on non-container database prior to converting it into a pluggable database.
    • Use CONVERT to convert a non-container database into a pluggable database.
    • Use SYNC if the non-container database was manually converted into a pluggable database using the dbcli command-line utility. Databases may need to be converted manually if the CONVERT action fails when converting a non-container database using the API.
    • Use SYNC_ROLLBACK if the conversion of a non-container database into a pluggable database was manually rolled back using the dbcli command line utility. Conversions may need to be manually rolled back if the CONVERT action fails when converting a non-container database using the API.
    additional_cdb_params str
    Additional container database parameter.
    cdb_name str
    The database name. The name must begin with an alphabetic character and can contain a maximum of 8 alphanumeric characters. Special characters are not permitted. The database name must be unique in the tenancy.
    database_id str
    id str
    The provider-assigned unique ID for this managed resource.
    lifecycle_details str
    Additional information about the current lifecycle state for the conversion operation.
    pdb_conversion_history_entry_id str
    source_database_id str
    The OCID of the database.
    state str
    Status of an operation performed during the conversion of a non-container database to a pluggable database.
    target str
    The target container database of the pluggable database created by the database conversion operation. Currently, the database conversion operation only supports creating the pluggable database in a new container database.

    • Use NEW_DATABASE to specify that the pluggable database be created within a new container database in the same database home.
    target_database_id str
    The OCID of the database.
    time_ended str
    The date and time when the database conversion operation ended.
    time_started str
    The date and time when the database conversion operation started.
    action String
    The operations used to convert a non-container database to a pluggable database.

    • Use PRECHECK to run a pre-check operation on non-container database prior to converting it into a pluggable database.
    • Use CONVERT to convert a non-container database into a pluggable database.
    • Use SYNC if the non-container database was manually converted into a pluggable database using the dbcli command-line utility. Databases may need to be converted manually if the CONVERT action fails when converting a non-container database using the API.
    • Use SYNC_ROLLBACK if the conversion of a non-container database into a pluggable database was manually rolled back using the dbcli command line utility. Conversions may need to be manually rolled back if the CONVERT action fails when converting a non-container database using the API.
    additionalCdbParams String
    Additional container database parameter.
    cdbName String
    The database name. The name must begin with an alphabetic character and can contain a maximum of 8 alphanumeric characters. Special characters are not permitted. The database name must be unique in the tenancy.
    databaseId String
    id String
    The provider-assigned unique ID for this managed resource.
    lifecycleDetails String
    Additional information about the current lifecycle state for the conversion operation.
    pdbConversionHistoryEntryId String
    sourceDatabaseId String
    The OCID of the database.
    state String
    Status of an operation performed during the conversion of a non-container database to a pluggable database.
    target String
    The target container database of the pluggable database created by the database conversion operation. Currently, the database conversion operation only supports creating the pluggable database in a new container database.

    • Use NEW_DATABASE to specify that the pluggable database be created within a new container database in the same database home.
    targetDatabaseId String
    The OCID of the database.
    timeEnded String
    The date and time when the database conversion operation ended.
    timeStarted String
    The date and time when the database conversion operation started.

    Package Details

    Repository
    oci pulumi/pulumi-oci
    License
    Apache-2.0
    Notes
    This Pulumi package is based on the oci Terraform Provider.
    oci logo
    Oracle Cloud Infrastructure v2.17.0 published on Friday, Nov 15, 2024 by Pulumi