Oracle Cloud Infrastructure v2.15.0 published on Thursday, Oct 31, 2024 by Pulumi
oci.Database.getDatabasePdbConversionHistoryEntry
Explore with Pulumi AI
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:
- Database
Id string - The database OCID.
- Pdb
Conversion stringHistory Entry Id - The database conversion history OCID.
- Database
Id string - The database OCID.
- Pdb
Conversion stringHistory Entry Id - The database conversion history OCID.
- database
Id String - The database OCID.
- pdb
Conversion StringHistory Entry Id - The database conversion history OCID.
- database
Id string - The database OCID.
- pdb
Conversion stringHistory Entry Id - The database conversion history OCID.
- database_
id str - The database OCID.
- pdb_
conversion_ strhistory_ entry_ id - The database conversion history OCID.
- database
Id String - The database OCID.
- pdb
Conversion StringHistory Entry Id - 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.
- Use
- Additional
Cdb stringParams - Additional container database parameter.
- Cdb
Name 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.
- Database
Id string - Id string
- The provider-assigned unique ID for this managed resource.
- Lifecycle
Details string - Additional information about the current lifecycle state for the conversion operation.
- Pdb
Conversion stringHistory Entry Id - Source
Database stringId - 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.
- Use
- Target
Database stringId - The OCID of the database.
- Time
Ended string - The date and time when the database conversion operation ended.
- Time
Started 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.
- Use
- Additional
Cdb stringParams - Additional container database parameter.
- Cdb
Name 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.
- Database
Id string - Id string
- The provider-assigned unique ID for this managed resource.
- Lifecycle
Details string - Additional information about the current lifecycle state for the conversion operation.
- Pdb
Conversion stringHistory Entry Id - Source
Database stringId - 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.
- Use
- Target
Database stringId - The OCID of the database.
- Time
Ended string - The date and time when the database conversion operation ended.
- Time
Started 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.
- Use
- additional
Cdb StringParams - Additional container database parameter.
- cdb
Name 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.
- database
Id String - id String
- The provider-assigned unique ID for this managed resource.
- lifecycle
Details String - Additional information about the current lifecycle state for the conversion operation.
- pdb
Conversion StringHistory Entry Id - source
Database StringId - 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.
- Use
- target
Database StringId - The OCID of the database.
- time
Ended String - The date and time when the database conversion operation ended.
- time
Started 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.
- Use
- additional
Cdb stringParams - Additional container database parameter.
- cdb
Name 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.
- database
Id string - id string
- The provider-assigned unique ID for this managed resource.
- lifecycle
Details string - Additional information about the current lifecycle state for the conversion operation.
- pdb
Conversion stringHistory Entry Id - source
Database stringId - 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.
- Use
- target
Database stringId - The OCID of the database.
- time
Ended string - The date and time when the database conversion operation ended.
- time
Started 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.
- Use
- additional_
cdb_ strparams - 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_ strhistory_ entry_ id - source_
database_ strid - 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.
- Use
- target_
database_ strid - 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.
- Use
- additional
Cdb StringParams - Additional container database parameter.
- cdb
Name 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.
- database
Id String - id String
- The provider-assigned unique ID for this managed resource.
- lifecycle
Details String - Additional information about the current lifecycle state for the conversion operation.
- pdb
Conversion StringHistory Entry Id - source
Database StringId - 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.
- Use
- target
Database StringId - The OCID of the database.
- time
Ended String - The date and time when the database conversion operation ended.
- time
Started 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.