oci.DataSafe.getSubsettingPolicy

Oracle Cloud Infrastructure v5.5.0, Oct 22 26

Viewing docs for Oracle Cloud Infrastructure v5.5.0
published on Thursday, Oct 22, 2026 by Pulumi

Schema (JSON)

pulumi/pulumi-oci

Viewing docs for Oracle Cloud Infrastructure v5.5.0
published on Thursday, Oct 22, 2026 by Pulumi

Schema (JSON)

pulumi/pulumi-oci

Example Usage

import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";

const testSubsettingPolicy = oci.datasafe.getSubsettingPolicy({
    subsettingPolicyId: testSubsettingPolicyOciDataSafeSubsettingPolicy.id,
});

import pulumi
import pulumi_oci as oci

test_subsetting_policy = oci.datasafe.get_subsetting_policy(subsetting_policy_id=test_subsetting_policy_oci_data_safe_subsetting_policy["id"])

package main

import (
	"github.com/pulumi/pulumi-oci/sdk/v5/go/oci/datasafe"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := datasafe.GetSubsettingPolicy(ctx, &datasafe.GetSubsettingPolicyArgs{
			SubsettingPolicyId: testSubsettingPolicyOciDataSafeSubsettingPolicy.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 testSubsettingPolicy = Oci.DataSafe.GetSubsettingPolicy.Invoke(new()
    {
        SubsettingPolicyId = testSubsettingPolicyOciDataSafeSubsettingPolicy.Id,
    });

});

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.DataSafe.DataSafeFunctions;
import com.pulumi.oci.DataSafe.inputs.GetSubsettingPolicyArgs;
import java.util.ArrayList;
import java.util.Arrays;
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 testSubsettingPolicy = DataSafeFunctions.getSubsettingPolicy(GetSubsettingPolicyArgs.builder()
            .subsettingPolicyId(testSubsettingPolicyOciDataSafeSubsettingPolicy.get("id"))
            .build());

    }
}

variables:
  testSubsettingPolicy:
    fn::invoke:
      function: oci:DataSafe:getSubsettingPolicy
      arguments:
        subsettingPolicyId: ${testSubsettingPolicyOciDataSafeSubsettingPolicy.id}

terraform {
  required_providers {
    oci = {
      source = "pulumi/oci"
    }
  }
}

data "oci_data_safe_subsetting_policy" "testSubsettingPolicy" {
  subsetting_policy_id = testSubsettingPolicyOciDataSafeSubsettingPolicy.id
}

Using getSubsettingPolicy

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 getSubsettingPolicy(args: GetSubsettingPolicyArgs, opts?: InvokeOptions): Promise<GetSubsettingPolicyResult>
function getSubsettingPolicyOutput(args: GetSubsettingPolicyOutputArgs, opts?: InvokeOutputOptions): Output<GetSubsettingPolicyResult>

def get_subsetting_policy(subsetting_policy_id: Optional[str] = None,
                          opts: Optional[InvokeOptions] = None) -> GetSubsettingPolicyResult
def get_subsetting_policy_output(subsetting_policy_id: pulumi.Input[Optional[str]] = None,
                          opts: Optional[InvokeOutputOptions] = None) -> Output[GetSubsettingPolicyResult]

func LookupSubsettingPolicy(ctx *Context, args *LookupSubsettingPolicyArgs, opts ...InvokeOption) (*LookupSubsettingPolicyResult, error)
func LookupSubsettingPolicyOutput(ctx *Context, args *LookupSubsettingPolicyOutputArgs, opts ...InvokeOption) LookupSubsettingPolicyResultOutput

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

public static class GetSubsettingPolicy 
{
    public static Task<GetSubsettingPolicyResult> InvokeAsync(GetSubsettingPolicyArgs args, InvokeOptions? opts = null)
    public static Output<GetSubsettingPolicyResult> Invoke(GetSubsettingPolicyInvokeArgs args, InvokeOptions? opts = null)
    public static Output<GetSubsettingPolicyResult> Invoke(GetSubsettingPolicyInvokeArgs args, InvokeOutputOptions opts)
}

public static CompletableFuture<GetSubsettingPolicyResult> getSubsettingPolicy(GetSubsettingPolicyArgs args, InvokeOptions options)
public static Output<GetSubsettingPolicyResult> getSubsettingPolicy(GetSubsettingPolicyArgs args, InvokeOptions options)
public static Output<GetSubsettingPolicyResult> getSubsettingPolicy(GetSubsettingPolicyArgs args, InvokeOutputOptions options)

fn::invoke:
  function: oci:DataSafe/getSubsettingPolicy:getSubsettingPolicy
  arguments:
    # arguments dictionary

data "oci_data_safe_get_subsetting_policy" "name" {
    # arguments
}

The following arguments are supported:

SubsettingPolicyId string: The OCID of the subsetting policy.

SubsettingPolicyId string: The OCID of the subsetting policy.

subsetting_policy_id string: The OCID of the subsetting policy.

subsettingPolicyId String: The OCID of the subsetting policy.

subsettingPolicyId string: The OCID of the subsetting policy.

subsetting_policy_id str: The OCID of the subsetting policy.

subsettingPolicyId String: The OCID of the subsetting policy.

getSubsettingPolicy Result

The following output properties are available:

CheckType string
CompartmentId string: The OCID of the compartment that contains the subsetting policy
DefinedTags Dictionary<string, string>: Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags Example: {"Operations.CostCenter": "42"}
Description string: The description of the subsetting policy
DisplayName string: The display name of the subsetting policy
FreeformTags Dictionary<string, string>: Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags Example: {"Department": "Finance"}
GenerateHealthReportTrigger int
Id string: The OCID of the subsetting policy
IsRedoLoggingEnabled bool: Indicates if redo logging is enabled during a subsetting operation. It's disabled by default. Set this attribute to true to enable redo logging. By default, subsetting disables redo logging and flashback logging to purge any original data from logs. However, in certain circumstances when you only want to test subsetting, rollback changes, and retry subsetting, you could enable logging and use a flashback database to retrieve the original data after it has been subsetted.
IsRefreshStatsEnabled bool: Indicates if statistics gathering is enabled. It's enabled by default. Set this attribute to false to disable statistics gathering. The subsetting process gathers statistics on database tables after subsetting completes
MaskingPolicyId string: The OCID of the masking policy associated with this subsetting policy
ParallelDegree string: Specifies options to enable parallel execution when running data subsetting. Allowed values are 'NONE' (no parallelism), 'DEFAULT' (the Oracle Database computes the optimum degree of parallelism) or an integer value to be used as the degree of parallelism. Parallel execution helps effectively use multiple CPUs and improve subsetting performance. Refer to the Oracle Database parallel execution framework when choosing an explicit degree of parallelism
PostSubsettingScript string: A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the core subsetting script generated using the subsetting policy. It's usually used to perform additional transformation or cleanup work after subsetting.
PreSubsettingScript string: A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the core subsetting script generated using the subsetting policy. It's usually used to perform any preparation or prerequisite work before subsetting data
Recompile string: Specifies how to recompile invalid objects post data subsetting. Allowed values are 'SERIAL' (recompile in serial), 'PARALLEL' (recompile in parallel), 'NONE' (do not recompile). If it's set to PARALLEL, the value of parallelDegree attribute is used. Use the built-in UTL_RECOMP package to recompile any remaining invalid objects after subsetting completes
SchemaSources List<GetSubsettingPolicySchemaSource>: The source of subsetting schemas
State string: The current state of the subsetting policy
SubsettingPolicyId string
Tablespace string
TargetCredentials List<GetSubsettingPolicyTargetCredential>
TargetId string: The OCID of the target database that's used as the source of subsetting schemas
TimeCreated string: The date and time the subsetting policy was created, in the format defined by RFC3339
TimeUpdated string: The date and time the subsetting policy was last updated, in the format defined by RFC3339
UnrelatedTablesAction string: Strategy to be applied for tables which are not impacted by any of the subsetting rules

CheckType string
CompartmentId string: The OCID of the compartment that contains the subsetting policy
DefinedTags map[string]string: Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags Example: {"Operations.CostCenter": "42"}
Description string: The description of the subsetting policy
DisplayName string: The display name of the subsetting policy
FreeformTags map[string]string: Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags Example: {"Department": "Finance"}
GenerateHealthReportTrigger int
Id string: The OCID of the subsetting policy
IsRedoLoggingEnabled bool: Indicates if redo logging is enabled during a subsetting operation. It's disabled by default. Set this attribute to true to enable redo logging. By default, subsetting disables redo logging and flashback logging to purge any original data from logs. However, in certain circumstances when you only want to test subsetting, rollback changes, and retry subsetting, you could enable logging and use a flashback database to retrieve the original data after it has been subsetted.
IsRefreshStatsEnabled bool: Indicates if statistics gathering is enabled. It's enabled by default. Set this attribute to false to disable statistics gathering. The subsetting process gathers statistics on database tables after subsetting completes
MaskingPolicyId string: The OCID of the masking policy associated with this subsetting policy
ParallelDegree string: Specifies options to enable parallel execution when running data subsetting. Allowed values are 'NONE' (no parallelism), 'DEFAULT' (the Oracle Database computes the optimum degree of parallelism) or an integer value to be used as the degree of parallelism. Parallel execution helps effectively use multiple CPUs and improve subsetting performance. Refer to the Oracle Database parallel execution framework when choosing an explicit degree of parallelism
PostSubsettingScript string: A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the core subsetting script generated using the subsetting policy. It's usually used to perform additional transformation or cleanup work after subsetting.
PreSubsettingScript string: A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the core subsetting script generated using the subsetting policy. It's usually used to perform any preparation or prerequisite work before subsetting data
Recompile string: Specifies how to recompile invalid objects post data subsetting. Allowed values are 'SERIAL' (recompile in serial), 'PARALLEL' (recompile in parallel), 'NONE' (do not recompile). If it's set to PARALLEL, the value of parallelDegree attribute is used. Use the built-in UTL_RECOMP package to recompile any remaining invalid objects after subsetting completes
SchemaSources []GetSubsettingPolicySchemaSource: The source of subsetting schemas
State string: The current state of the subsetting policy
SubsettingPolicyId string
Tablespace string
TargetCredentials []GetSubsettingPolicyTargetCredential
TargetId string: The OCID of the target database that's used as the source of subsetting schemas
TimeCreated string: The date and time the subsetting policy was created, in the format defined by RFC3339
TimeUpdated string: The date and time the subsetting policy was last updated, in the format defined by RFC3339
UnrelatedTablesAction string: Strategy to be applied for tables which are not impacted by any of the subsetting rules

check_type string
compartment_id string: The OCID of the compartment that contains the subsetting policy
defined_tags map(string): Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags Example: {"Operations.CostCenter": "42"}
description string: The description of the subsetting policy
display_name string: The display name of the subsetting policy
freeform_tags map(string): Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags Example: {"Department": "Finance"}
generate_health_report_trigger number
id string: The OCID of the subsetting policy
is_redo_logging_enabled bool: Indicates if redo logging is enabled during a subsetting operation. It's disabled by default. Set this attribute to true to enable redo logging. By default, subsetting disables redo logging and flashback logging to purge any original data from logs. However, in certain circumstances when you only want to test subsetting, rollback changes, and retry subsetting, you could enable logging and use a flashback database to retrieve the original data after it has been subsetted.
is_refresh_stats_enabled bool: Indicates if statistics gathering is enabled. It's enabled by default. Set this attribute to false to disable statistics gathering. The subsetting process gathers statistics on database tables after subsetting completes
masking_policy_id string: The OCID of the masking policy associated with this subsetting policy
parallel_degree string: Specifies options to enable parallel execution when running data subsetting. Allowed values are 'NONE' (no parallelism), 'DEFAULT' (the Oracle Database computes the optimum degree of parallelism) or an integer value to be used as the degree of parallelism. Parallel execution helps effectively use multiple CPUs and improve subsetting performance. Refer to the Oracle Database parallel execution framework when choosing an explicit degree of parallelism
post_subsetting_script string: A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the core subsetting script generated using the subsetting policy. It's usually used to perform additional transformation or cleanup work after subsetting.
pre_subsetting_script string: A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the core subsetting script generated using the subsetting policy. It's usually used to perform any preparation or prerequisite work before subsetting data
recompile string: Specifies how to recompile invalid objects post data subsetting. Allowed values are 'SERIAL' (recompile in serial), 'PARALLEL' (recompile in parallel), 'NONE' (do not recompile). If it's set to PARALLEL, the value of parallelDegree attribute is used. Use the built-in UTL_RECOMP package to recompile any remaining invalid objects after subsetting completes
schema_sources list(object): The source of subsetting schemas
state string: The current state of the subsetting policy
subsetting_policy_id string
tablespace string
target_credentials list(object)
target_id string: The OCID of the target database that's used as the source of subsetting schemas
time_created string: The date and time the subsetting policy was created, in the format defined by RFC3339
time_updated string: The date and time the subsetting policy was last updated, in the format defined by RFC3339
unrelated_tables_action string: Strategy to be applied for tables which are not impacted by any of the subsetting rules

checkType String
compartmentId String: The OCID of the compartment that contains the subsetting policy
definedTags Map<String,String>: Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags Example: {"Operations.CostCenter": "42"}
description String: The description of the subsetting policy
displayName String: The display name of the subsetting policy
freeformTags Map<String,String>: Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags Example: {"Department": "Finance"}
generateHealthReportTrigger Integer
id String: The OCID of the subsetting policy
isRedoLoggingEnabled Boolean: Indicates if redo logging is enabled during a subsetting operation. It's disabled by default. Set this attribute to true to enable redo logging. By default, subsetting disables redo logging and flashback logging to purge any original data from logs. However, in certain circumstances when you only want to test subsetting, rollback changes, and retry subsetting, you could enable logging and use a flashback database to retrieve the original data after it has been subsetted.
isRefreshStatsEnabled Boolean: Indicates if statistics gathering is enabled. It's enabled by default. Set this attribute to false to disable statistics gathering. The subsetting process gathers statistics on database tables after subsetting completes
maskingPolicyId String: The OCID of the masking policy associated with this subsetting policy
parallelDegree String: Specifies options to enable parallel execution when running data subsetting. Allowed values are 'NONE' (no parallelism), 'DEFAULT' (the Oracle Database computes the optimum degree of parallelism) or an integer value to be used as the degree of parallelism. Parallel execution helps effectively use multiple CPUs and improve subsetting performance. Refer to the Oracle Database parallel execution framework when choosing an explicit degree of parallelism
postSubsettingScript String: A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the core subsetting script generated using the subsetting policy. It's usually used to perform additional transformation or cleanup work after subsetting.
preSubsettingScript String: A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the core subsetting script generated using the subsetting policy. It's usually used to perform any preparation or prerequisite work before subsetting data
recompile String: Specifies how to recompile invalid objects post data subsetting. Allowed values are 'SERIAL' (recompile in serial), 'PARALLEL' (recompile in parallel), 'NONE' (do not recompile). If it's set to PARALLEL, the value of parallelDegree attribute is used. Use the built-in UTL_RECOMP package to recompile any remaining invalid objects after subsetting completes
schemaSources List<GetSubsettingPolicySchemaSource>: The source of subsetting schemas
state String: The current state of the subsetting policy
subsettingPolicyId String
tablespace String
targetCredentials List<GetSubsettingPolicyTargetCredential>
targetId String: The OCID of the target database that's used as the source of subsetting schemas
timeCreated String: The date and time the subsetting policy was created, in the format defined by RFC3339
timeUpdated String: The date and time the subsetting policy was last updated, in the format defined by RFC3339
unrelatedTablesAction String: Strategy to be applied for tables which are not impacted by any of the subsetting rules

checkType string
compartmentId string: The OCID of the compartment that contains the subsetting policy
definedTags {[key: string]: string}: Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags Example: {"Operations.CostCenter": "42"}
description string: The description of the subsetting policy
displayName string: The display name of the subsetting policy
freeformTags {[key: string]: string}: Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags Example: {"Department": "Finance"}
generateHealthReportTrigger number
id string: The OCID of the subsetting policy
isRedoLoggingEnabled boolean: Indicates if redo logging is enabled during a subsetting operation. It's disabled by default. Set this attribute to true to enable redo logging. By default, subsetting disables redo logging and flashback logging to purge any original data from logs. However, in certain circumstances when you only want to test subsetting, rollback changes, and retry subsetting, you could enable logging and use a flashback database to retrieve the original data after it has been subsetted.
isRefreshStatsEnabled boolean: Indicates if statistics gathering is enabled. It's enabled by default. Set this attribute to false to disable statistics gathering. The subsetting process gathers statistics on database tables after subsetting completes
maskingPolicyId string: The OCID of the masking policy associated with this subsetting policy
parallelDegree string: Specifies options to enable parallel execution when running data subsetting. Allowed values are 'NONE' (no parallelism), 'DEFAULT' (the Oracle Database computes the optimum degree of parallelism) or an integer value to be used as the degree of parallelism. Parallel execution helps effectively use multiple CPUs and improve subsetting performance. Refer to the Oracle Database parallel execution framework when choosing an explicit degree of parallelism
postSubsettingScript string: A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the core subsetting script generated using the subsetting policy. It's usually used to perform additional transformation or cleanup work after subsetting.
preSubsettingScript string: A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the core subsetting script generated using the subsetting policy. It's usually used to perform any preparation or prerequisite work before subsetting data
recompile string: Specifies how to recompile invalid objects post data subsetting. Allowed values are 'SERIAL' (recompile in serial), 'PARALLEL' (recompile in parallel), 'NONE' (do not recompile). If it's set to PARALLEL, the value of parallelDegree attribute is used. Use the built-in UTL_RECOMP package to recompile any remaining invalid objects after subsetting completes
schemaSources GetSubsettingPolicySchemaSource[]: The source of subsetting schemas
state string: The current state of the subsetting policy
subsettingPolicyId string
tablespace string
targetCredentials GetSubsettingPolicyTargetCredential[]
targetId string: The OCID of the target database that's used as the source of subsetting schemas
timeCreated string: The date and time the subsetting policy was created, in the format defined by RFC3339
timeUpdated string: The date and time the subsetting policy was last updated, in the format defined by RFC3339
unrelatedTablesAction string: Strategy to be applied for tables which are not impacted by any of the subsetting rules

check_type str
compartment_id str: The OCID of the compartment that contains the subsetting policy
defined_tags Mapping[str, str]: Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags Example: {"Operations.CostCenter": "42"}
description str: The description of the subsetting policy
display_name str: The display name of the subsetting policy
freeform_tags Mapping[str, str]: Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags Example: {"Department": "Finance"}
generate_health_report_trigger int
id str: The OCID of the subsetting policy
is_redo_logging_enabled bool: Indicates if redo logging is enabled during a subsetting operation. It's disabled by default. Set this attribute to true to enable redo logging. By default, subsetting disables redo logging and flashback logging to purge any original data from logs. However, in certain circumstances when you only want to test subsetting, rollback changes, and retry subsetting, you could enable logging and use a flashback database to retrieve the original data after it has been subsetted.
is_refresh_stats_enabled bool: Indicates if statistics gathering is enabled. It's enabled by default. Set this attribute to false to disable statistics gathering. The subsetting process gathers statistics on database tables after subsetting completes
masking_policy_id str: The OCID of the masking policy associated with this subsetting policy
parallel_degree str: Specifies options to enable parallel execution when running data subsetting. Allowed values are 'NONE' (no parallelism), 'DEFAULT' (the Oracle Database computes the optimum degree of parallelism) or an integer value to be used as the degree of parallelism. Parallel execution helps effectively use multiple CPUs and improve subsetting performance. Refer to the Oracle Database parallel execution framework when choosing an explicit degree of parallelism
post_subsetting_script str: A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the core subsetting script generated using the subsetting policy. It's usually used to perform additional transformation or cleanup work after subsetting.
pre_subsetting_script str: A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the core subsetting script generated using the subsetting policy. It's usually used to perform any preparation or prerequisite work before subsetting data
recompile str: Specifies how to recompile invalid objects post data subsetting. Allowed values are 'SERIAL' (recompile in serial), 'PARALLEL' (recompile in parallel), 'NONE' (do not recompile). If it's set to PARALLEL, the value of parallelDegree attribute is used. Use the built-in UTL_RECOMP package to recompile any remaining invalid objects after subsetting completes
schema_sources Sequence[GetSubsettingPolicySchemaSource]: The source of subsetting schemas
state str: The current state of the subsetting policy
subsetting_policy_id str
tablespace str
target_credentials Sequence[GetSubsettingPolicyTargetCredential]
target_id str: The OCID of the target database that's used as the source of subsetting schemas
time_created str: The date and time the subsetting policy was created, in the format defined by RFC3339
time_updated str: The date and time the subsetting policy was last updated, in the format defined by RFC3339
unrelated_tables_action str: Strategy to be applied for tables which are not impacted by any of the subsetting rules

checkType String
compartmentId String: The OCID of the compartment that contains the subsetting policy
definedTags Map<String>: Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags Example: {"Operations.CostCenter": "42"}
description String: The description of the subsetting policy
displayName String: The display name of the subsetting policy
freeformTags Map<String>: Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags Example: {"Department": "Finance"}
generateHealthReportTrigger Number
id String: The OCID of the subsetting policy
isRedoLoggingEnabled Boolean: Indicates if redo logging is enabled during a subsetting operation. It's disabled by default. Set this attribute to true to enable redo logging. By default, subsetting disables redo logging and flashback logging to purge any original data from logs. However, in certain circumstances when you only want to test subsetting, rollback changes, and retry subsetting, you could enable logging and use a flashback database to retrieve the original data after it has been subsetted.
isRefreshStatsEnabled Boolean: Indicates if statistics gathering is enabled. It's enabled by default. Set this attribute to false to disable statistics gathering. The subsetting process gathers statistics on database tables after subsetting completes
maskingPolicyId String: The OCID of the masking policy associated with this subsetting policy
parallelDegree String: Specifies options to enable parallel execution when running data subsetting. Allowed values are 'NONE' (no parallelism), 'DEFAULT' (the Oracle Database computes the optimum degree of parallelism) or an integer value to be used as the degree of parallelism. Parallel execution helps effectively use multiple CPUs and improve subsetting performance. Refer to the Oracle Database parallel execution framework when choosing an explicit degree of parallelism
postSubsettingScript String: A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the core subsetting script generated using the subsetting policy. It's usually used to perform additional transformation or cleanup work after subsetting.
preSubsettingScript String: A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the core subsetting script generated using the subsetting policy. It's usually used to perform any preparation or prerequisite work before subsetting data
recompile String: Specifies how to recompile invalid objects post data subsetting. Allowed values are 'SERIAL' (recompile in serial), 'PARALLEL' (recompile in parallel), 'NONE' (do not recompile). If it's set to PARALLEL, the value of parallelDegree attribute is used. Use the built-in UTL_RECOMP package to recompile any remaining invalid objects after subsetting completes
schemaSources List<Property Map>: The source of subsetting schemas
state String: The current state of the subsetting policy
subsettingPolicyId String
tablespace String
targetCredentials List<Property Map>
targetId String: The OCID of the target database that's used as the source of subsetting schemas
timeCreated String: The date and time the subsetting policy was created, in the format defined by RFC3339
timeUpdated String: The date and time the subsetting policy was last updated, in the format defined by RFC3339
unrelatedTablesAction String: Strategy to be applied for tables which are not impacted by any of the subsetting rules

Supporting Types

GetSubsettingPolicySchemaSource

DerivedSchemas List<string>: The schemas which are related to the input list of schemas in 'schemasForSubsetting'. These schemas can also be impacted from the subsetting process due to their relations with the schemas in 'schemasForSubsetting'
SchemaSource string: The source of subsetting schemas
SchemasForSubsettings List<string>: The schemas to be subsetted
SensitiveDataModelId string: The OCID of the sensitive data model that's used as the source of subsetting schemas
TargetId string: The OCID of the target database that's used as the source of subsetting schemas

DerivedSchemas []string: The schemas which are related to the input list of schemas in 'schemasForSubsetting'. These schemas can also be impacted from the subsetting process due to their relations with the schemas in 'schemasForSubsetting'
SchemaSource string: The source of subsetting schemas
SchemasForSubsettings []string: The schemas to be subsetted
SensitiveDataModelId string: The OCID of the sensitive data model that's used as the source of subsetting schemas
TargetId string: The OCID of the target database that's used as the source of subsetting schemas

derived_schemas list(string): The schemas which are related to the input list of schemas in 'schemasForSubsetting'. These schemas can also be impacted from the subsetting process due to their relations with the schemas in 'schemasForSubsetting'
schema_source string: The source of subsetting schemas
schemas_for_subsettings list(string): The schemas to be subsetted
sensitive_data_model_id string: The OCID of the sensitive data model that's used as the source of subsetting schemas
target_id string: The OCID of the target database that's used as the source of subsetting schemas

derivedSchemas List<String>: The schemas which are related to the input list of schemas in 'schemasForSubsetting'. These schemas can also be impacted from the subsetting process due to their relations with the schemas in 'schemasForSubsetting'
schemaSource String: The source of subsetting schemas
schemasForSubsettings List<String>: The schemas to be subsetted
sensitiveDataModelId String: The OCID of the sensitive data model that's used as the source of subsetting schemas
targetId String: The OCID of the target database that's used as the source of subsetting schemas

derivedSchemas string[]: The schemas which are related to the input list of schemas in 'schemasForSubsetting'. These schemas can also be impacted from the subsetting process due to their relations with the schemas in 'schemasForSubsetting'
schemaSource string: The source of subsetting schemas
schemasForSubsettings string[]: The schemas to be subsetted
sensitiveDataModelId string: The OCID of the sensitive data model that's used as the source of subsetting schemas
targetId string: The OCID of the target database that's used as the source of subsetting schemas

derived_schemas Sequence[str]: The schemas which are related to the input list of schemas in 'schemasForSubsetting'. These schemas can also be impacted from the subsetting process due to their relations with the schemas in 'schemasForSubsetting'
schema_source str: The source of subsetting schemas
schemas_for_subsettings Sequence[str]: The schemas to be subsetted
sensitive_data_model_id str: The OCID of the sensitive data model that's used as the source of subsetting schemas
target_id str: The OCID of the target database that's used as the source of subsetting schemas

derivedSchemas List<String>: The schemas which are related to the input list of schemas in 'schemasForSubsetting'. These schemas can also be impacted from the subsetting process due to their relations with the schemas in 'schemasForSubsetting'
schemaSource String: The source of subsetting schemas
schemasForSubsettings List<String>: The schemas to be subsetted
sensitiveDataModelId String: The OCID of the sensitive data model that's used as the source of subsetting schemas
targetId String: The OCID of the target database that's used as the source of subsetting schemas