published on Tuesday, Oct 13, 2026 by Pulumi
published on Tuesday, Oct 13, 2026 by Pulumi
This resource provides the Subsetting Policy resource in Oracle Cloud Infrastructure Data Safe service. Api doc link for the resource: https://docs.oracle.com/iaas/api/#/en/data-safe/latest/SubsettingPolicy
Example terraform configs related to the resource : https://github.com/oracle/terraform-provider-oci/tree/master/examples/datasafe
Creates a new subsetting policy and associates it with a sensitive data model or a target database.
To use a sensitive data model as the source of subsetting schemas, set the schemaSource attribute to SENSITIVE_DATA_MODEL and provide the sensitiveDataModelId attribute. In this case, the target database associated with the sensitive data model is used for subsetting rules validations.
You can also create a subsetting policy without using a sensitive data model. In this case, you need to associate your subsetting policy with a target database by setting the schemaSource attribute to TARGET and providing the targetId attribute. The specified target database is used for subsetting rules validations.
After creating a subsetting policy, you can use the CreateSubsettingRule operation to manually add subsetting rules to the policy.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testSubsettingPolicy = new oci.datasafe.SubsettingPolicy("test_subsetting_policy", {
compartmentId: compartmentId,
schemaSource: {
schemaSource: subsettingPolicySchemaSourceSchemaSource,
schemasForSubsettings: subsettingPolicySchemaSourceSchemasForSubsetting,
sensitiveDataModelId: testSensitiveDataModel.id,
targetId: testTarget.id,
},
definedTags: {
"Operations.CostCenter": "42",
},
description: subsettingPolicyDescription,
displayName: subsettingPolicyDisplayName,
freeformTags: {
Department: "Finance",
},
isRedoLoggingEnabled: subsettingPolicyIsRedoLoggingEnabled,
isRefreshStatsEnabled: subsettingPolicyIsRefreshStatsEnabled,
maskingPolicyId: testMaskingPolicy.id,
parallelDegree: subsettingPolicyParallelDegree,
postSubsettingScript: subsettingPolicyPostSubsettingScript,
preSubsettingScript: subsettingPolicyPreSubsettingScript,
recompile: subsettingPolicyRecompile,
unrelatedTablesAction: subsettingPolicyUnrelatedTablesAction,
});
import pulumi
import pulumi_oci as oci
test_subsetting_policy = oci.datasafe.SubsettingPolicy("test_subsetting_policy",
compartment_id=compartment_id,
schema_source={
"schema_source": subsetting_policy_schema_source_schema_source,
"schemas_for_subsettings": subsetting_policy_schema_source_schemas_for_subsetting,
"sensitive_data_model_id": test_sensitive_data_model["id"],
"target_id": test_target["id"],
},
defined_tags={
"Operations.CostCenter": "42",
},
description=subsetting_policy_description,
display_name=subsetting_policy_display_name,
freeform_tags={
"Department": "Finance",
},
is_redo_logging_enabled=subsetting_policy_is_redo_logging_enabled,
is_refresh_stats_enabled=subsetting_policy_is_refresh_stats_enabled,
masking_policy_id=test_masking_policy["id"],
parallel_degree=subsetting_policy_parallel_degree,
post_subsetting_script=subsetting_policy_post_subsetting_script,
pre_subsetting_script=subsetting_policy_pre_subsetting_script,
recompile=subsetting_policy_recompile,
unrelated_tables_action=subsetting_policy_unrelated_tables_action)
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.NewSubsettingPolicy(ctx, "test_subsetting_policy", &datasafe.SubsettingPolicyArgs{
CompartmentId: pulumi.Any(compartmentId),
SchemaSource: &datasafe.SubsettingPolicySchemaSourceArgs{
SchemaSource: pulumi.Any(subsettingPolicySchemaSourceSchemaSource),
SchemasForSubsettings: pulumi.Any(subsettingPolicySchemaSourceSchemasForSubsetting),
SensitiveDataModelId: pulumi.Any(testSensitiveDataModel.Id),
TargetId: pulumi.Any(testTarget.Id),
},
DefinedTags: pulumi.StringMap{
"Operations.CostCenter": pulumi.String("42"),
},
Description: pulumi.Any(subsettingPolicyDescription),
DisplayName: pulumi.Any(subsettingPolicyDisplayName),
FreeformTags: pulumi.StringMap{
"Department": pulumi.String("Finance"),
},
IsRedoLoggingEnabled: pulumi.Any(subsettingPolicyIsRedoLoggingEnabled),
IsRefreshStatsEnabled: pulumi.Any(subsettingPolicyIsRefreshStatsEnabled),
MaskingPolicyId: pulumi.Any(testMaskingPolicy.Id),
ParallelDegree: pulumi.Any(subsettingPolicyParallelDegree),
PostSubsettingScript: pulumi.Any(subsettingPolicyPostSubsettingScript),
PreSubsettingScript: pulumi.Any(subsettingPolicyPreSubsettingScript),
Recompile: pulumi.Any(subsettingPolicyRecompile),
UnrelatedTablesAction: pulumi.Any(subsettingPolicyUnrelatedTablesAction),
})
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 = new Oci.DataSafe.SubsettingPolicy("test_subsetting_policy", new()
{
CompartmentId = compartmentId,
SchemaSource = new Oci.DataSafe.Inputs.SubsettingPolicySchemaSourceArgs
{
SchemaSource = subsettingPolicySchemaSourceSchemaSource,
SchemasForSubsettings = subsettingPolicySchemaSourceSchemasForSubsetting,
SensitiveDataModelId = testSensitiveDataModel.Id,
TargetId = testTarget.Id,
},
DefinedTags =
{
{ "Operations.CostCenter", "42" },
},
Description = subsettingPolicyDescription,
DisplayName = subsettingPolicyDisplayName,
FreeformTags =
{
{ "Department", "Finance" },
},
IsRedoLoggingEnabled = subsettingPolicyIsRedoLoggingEnabled,
IsRefreshStatsEnabled = subsettingPolicyIsRefreshStatsEnabled,
MaskingPolicyId = testMaskingPolicy.Id,
ParallelDegree = subsettingPolicyParallelDegree,
PostSubsettingScript = subsettingPolicyPostSubsettingScript,
PreSubsettingScript = subsettingPolicyPreSubsettingScript,
Recompile = subsettingPolicyRecompile,
UnrelatedTablesAction = subsettingPolicyUnrelatedTablesAction,
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.DataSafe.SubsettingPolicy;
import com.pulumi.oci.DataSafe.SubsettingPolicyArgs;
import com.pulumi.oci.DataSafe.inputs.SubsettingPolicySchemaSourceArgs;
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) {
var testSubsettingPolicy = new SubsettingPolicy("testSubsettingPolicy", SubsettingPolicyArgs.builder()
.compartmentId(compartmentId)
.schemaSource(SubsettingPolicySchemaSourceArgs.builder()
.schemaSource(subsettingPolicySchemaSourceSchemaSource)
.schemasForSubsettings(subsettingPolicySchemaSourceSchemasForSubsetting)
.sensitiveDataModelId(testSensitiveDataModel.get("id"))
.targetId(testTarget.get("id"))
.build())
.definedTags(Map.of("Operations.CostCenter", "42"))
.description(subsettingPolicyDescription)
.displayName(subsettingPolicyDisplayName)
.freeformTags(Map.of("Department", "Finance"))
.isRedoLoggingEnabled(subsettingPolicyIsRedoLoggingEnabled)
.isRefreshStatsEnabled(subsettingPolicyIsRefreshStatsEnabled)
.maskingPolicyId(testMaskingPolicy.get("id"))
.parallelDegree(subsettingPolicyParallelDegree)
.postSubsettingScript(subsettingPolicyPostSubsettingScript)
.preSubsettingScript(subsettingPolicyPreSubsettingScript)
.recompile(subsettingPolicyRecompile)
.unrelatedTablesAction(subsettingPolicyUnrelatedTablesAction)
.build());
}
}
resources:
testSubsettingPolicy:
type: oci:DataSafe:SubsettingPolicy
name: test_subsetting_policy
properties:
compartmentId: ${compartmentId}
schemaSource:
schemaSource: ${subsettingPolicySchemaSourceSchemaSource}
schemasForSubsettings: ${subsettingPolicySchemaSourceSchemasForSubsetting}
sensitiveDataModelId: ${testSensitiveDataModel.id}
targetId: ${testTarget.id}
definedTags:
Operations.CostCenter: '42'
description: ${subsettingPolicyDescription}
displayName: ${subsettingPolicyDisplayName}
freeformTags:
Department: Finance
isRedoLoggingEnabled: ${subsettingPolicyIsRedoLoggingEnabled}
isRefreshStatsEnabled: ${subsettingPolicyIsRefreshStatsEnabled}
maskingPolicyId: ${testMaskingPolicy.id}
parallelDegree: ${subsettingPolicyParallelDegree}
postSubsettingScript: ${subsettingPolicyPostSubsettingScript}
preSubsettingScript: ${subsettingPolicyPreSubsettingScript}
recompile: ${subsettingPolicyRecompile}
unrelatedTablesAction: ${subsettingPolicyUnrelatedTablesAction}
terraform {
required_providers {
oci = {
source = "pulumi/oci"
}
}
}
resource "oci_data_safe_subsetting_policy" "test_subsetting_policy" {
lifecycle {
create_before_destroy = true
}
compartment_id = compartmentId
schema_source = {
schema_source = subsettingPolicySchemaSourceSchemaSource
schemas_for_subsettings = subsettingPolicySchemaSourceSchemasForSubsetting
sensitive_data_model_id = testSensitiveDataModel.id
target_id = testTarget.id
}
#Required
#Optional
defined_tags = {
"Operations.CostCenter" = "42"
}
description = subsettingPolicyDescription
display_name = subsettingPolicyDisplayName
freeform_tags = {
"Department" = "Finance"
}
is_redo_logging_enabled = subsettingPolicyIsRedoLoggingEnabled
is_refresh_stats_enabled = subsettingPolicyIsRefreshStatsEnabled
masking_policy_id = testMaskingPolicy.id
parallel_degree = subsettingPolicyParallelDegree
post_subsetting_script = subsettingPolicyPostSubsettingScript
pre_subsetting_script = subsettingPolicyPreSubsettingScript
recompile = subsettingPolicyRecompile
unrelated_tables_action = subsettingPolicyUnrelatedTablesAction
}
Create SubsettingPolicy Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new SubsettingPolicy(name: string, args: SubsettingPolicyArgs, opts?: CustomResourceOptions);@overload
def SubsettingPolicy(resource_name: str,
args: SubsettingPolicyArgs,
opts: Optional[ResourceOptions] = None)
@overload
def SubsettingPolicy(resource_name: str,
opts: Optional[ResourceOptions] = None,
schema_source: Optional[SubsettingPolicySchemaSourceArgs] = None,
compartment_id: Optional[str] = None,
is_refresh_stats_enabled: Optional[bool] = None,
post_subsetting_script: Optional[str] = None,
display_name: Optional[str] = None,
freeform_tags: Optional[Mapping[str, str]] = None,
generate_health_report_trigger: Optional[int] = None,
is_redo_logging_enabled: Optional[bool] = None,
check_type: Optional[str] = None,
masking_policy_id: Optional[str] = None,
parallel_degree: Optional[str] = None,
description: Optional[str] = None,
pre_subsetting_script: Optional[str] = None,
recompile: Optional[str] = None,
defined_tags: Optional[Mapping[str, str]] = None,
tablespace: Optional[str] = None,
target_credentials: Optional[SubsettingPolicyTargetCredentialsArgs] = None,
target_id: Optional[str] = None,
unrelated_tables_action: Optional[str] = None)func NewSubsettingPolicy(ctx *Context, name string, args SubsettingPolicyArgs, opts ...ResourceOption) (*SubsettingPolicy, error)public SubsettingPolicy(string name, SubsettingPolicyArgs args, CustomResourceOptions? opts = null)
public SubsettingPolicy(String name, SubsettingPolicyArgs args)
public SubsettingPolicy(String name, SubsettingPolicyArgs args, CustomResourceOptions options)
type: oci:DataSafe:SubsettingPolicy
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
resource "oci_data_safe_subsetting_policy" "name" {
# resource properties
}Parameters
- name string
- The unique name of the resource.
- args SubsettingPolicyArgs
- 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 SubsettingPolicyArgs
- 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 SubsettingPolicyArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args SubsettingPolicyArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args SubsettingPolicyArgs
- 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 subsettingPolicyResource = new Oci.DataSafe.SubsettingPolicy("subsettingPolicyResource", new()
{
SchemaSource = new Oci.DataSafe.Inputs.SubsettingPolicySchemaSourceArgs
{
SchemaSource = "string",
DerivedSchemas = new[]
{
"string",
},
SchemasForSubsettings = new[]
{
"string",
},
SensitiveDataModelId = "string",
TargetId = "string",
},
CompartmentId = "string",
IsRefreshStatsEnabled = false,
PostSubsettingScript = "string",
DisplayName = "string",
FreeformTags =
{
{ "string", "string" },
},
GenerateHealthReportTrigger = 0,
IsRedoLoggingEnabled = false,
CheckType = "string",
MaskingPolicyId = "string",
ParallelDegree = "string",
Description = "string",
PreSubsettingScript = "string",
Recompile = "string",
DefinedTags =
{
{ "string", "string" },
},
Tablespace = "string",
TargetCredentials = new Oci.DataSafe.Inputs.SubsettingPolicyTargetCredentialsArgs
{
Password = "string",
UserName = "string",
},
TargetId = "string",
UnrelatedTablesAction = "string",
});
example, err := datasafe.NewSubsettingPolicy(ctx, "subsettingPolicyResource", &datasafe.SubsettingPolicyArgs{
SchemaSource: &datasafe.SubsettingPolicySchemaSourceArgs{
SchemaSource: pulumi.String("string"),
DerivedSchemas: pulumi.StringArray{
pulumi.String("string"),
},
SchemasForSubsettings: pulumi.StringArray{
pulumi.String("string"),
},
SensitiveDataModelId: pulumi.String("string"),
TargetId: pulumi.String("string"),
},
CompartmentId: pulumi.String("string"),
IsRefreshStatsEnabled: pulumi.Bool(false),
PostSubsettingScript: pulumi.String("string"),
DisplayName: pulumi.String("string"),
FreeformTags: pulumi.StringMap{
"string": pulumi.String("string"),
},
GenerateHealthReportTrigger: pulumi.Int(0),
IsRedoLoggingEnabled: pulumi.Bool(false),
CheckType: pulumi.String("string"),
MaskingPolicyId: pulumi.String("string"),
ParallelDegree: pulumi.String("string"),
Description: pulumi.String("string"),
PreSubsettingScript: pulumi.String("string"),
Recompile: pulumi.String("string"),
DefinedTags: pulumi.StringMap{
"string": pulumi.String("string"),
},
Tablespace: pulumi.String("string"),
TargetCredentials: &datasafe.SubsettingPolicyTargetCredentialsArgs{
Password: pulumi.String("string"),
UserName: pulumi.String("string"),
},
TargetId: pulumi.String("string"),
UnrelatedTablesAction: pulumi.String("string"),
})
resource "oci_data_safe_subsetting_policy" "subsettingPolicyResource" {
lifecycle {
create_before_destroy = true
}
schema_source = {
schema_source = "string"
derived_schemas = ["string"]
schemas_for_subsettings = ["string"]
sensitive_data_model_id = "string"
target_id = "string"
}
compartment_id = "string"
is_refresh_stats_enabled = false
post_subsetting_script = "string"
display_name = "string"
freeform_tags = {
"string" = "string"
}
generate_health_report_trigger = 0
is_redo_logging_enabled = false
check_type = "string"
masking_policy_id = "string"
parallel_degree = "string"
description = "string"
pre_subsetting_script = "string"
recompile = "string"
defined_tags = {
"string" = "string"
}
tablespace = "string"
target_credentials = {
password = "string"
user_name = "string"
}
target_id = "string"
unrelated_tables_action = "string"
}
var subsettingPolicyResource = new SubsettingPolicy("subsettingPolicyResource", SubsettingPolicyArgs.builder()
.schemaSource(SubsettingPolicySchemaSourceArgs.builder()
.schemaSource("string")
.derivedSchemas("string")
.schemasForSubsettings("string")
.sensitiveDataModelId("string")
.targetId("string")
.build())
.compartmentId("string")
.isRefreshStatsEnabled(false)
.postSubsettingScript("string")
.displayName("string")
.freeformTags(Map.of("string", "string"))
.generateHealthReportTrigger(0)
.isRedoLoggingEnabled(false)
.checkType("string")
.maskingPolicyId("string")
.parallelDegree("string")
.description("string")
.preSubsettingScript("string")
.recompile("string")
.definedTags(Map.of("string", "string"))
.tablespace("string")
.targetCredentials(SubsettingPolicyTargetCredentialsArgs.builder()
.password("string")
.userName("string")
.build())
.targetId("string")
.unrelatedTablesAction("string")
.build());
subsetting_policy_resource = oci.datasafe.SubsettingPolicy("subsettingPolicyResource",
schema_source={
"schema_source": "string",
"derived_schemas": ["string"],
"schemas_for_subsettings": ["string"],
"sensitive_data_model_id": "string",
"target_id": "string",
},
compartment_id="string",
is_refresh_stats_enabled=False,
post_subsetting_script="string",
display_name="string",
freeform_tags={
"string": "string",
},
generate_health_report_trigger=0,
is_redo_logging_enabled=False,
check_type="string",
masking_policy_id="string",
parallel_degree="string",
description="string",
pre_subsetting_script="string",
recompile="string",
defined_tags={
"string": "string",
},
tablespace="string",
target_credentials={
"password": "string",
"user_name": "string",
},
target_id="string",
unrelated_tables_action="string")
const subsettingPolicyResource = new oci.datasafe.SubsettingPolicy("subsettingPolicyResource", {
schemaSource: {
schemaSource: "string",
derivedSchemas: ["string"],
schemasForSubsettings: ["string"],
sensitiveDataModelId: "string",
targetId: "string",
},
compartmentId: "string",
isRefreshStatsEnabled: false,
postSubsettingScript: "string",
displayName: "string",
freeformTags: {
string: "string",
},
generateHealthReportTrigger: 0,
isRedoLoggingEnabled: false,
checkType: "string",
maskingPolicyId: "string",
parallelDegree: "string",
description: "string",
preSubsettingScript: "string",
recompile: "string",
definedTags: {
string: "string",
},
tablespace: "string",
targetCredentials: {
password: "string",
userName: "string",
},
targetId: "string",
unrelatedTablesAction: "string",
});
type: oci:DataSafe:SubsettingPolicy
properties:
checkType: string
compartmentId: string
definedTags:
string: string
description: string
displayName: string
freeformTags:
string: string
generateHealthReportTrigger: 0
isRedoLoggingEnabled: false
isRefreshStatsEnabled: false
maskingPolicyId: string
parallelDegree: string
postSubsettingScript: string
preSubsettingScript: string
recompile: string
schemaSource:
derivedSchemas:
- string
schemaSource: string
schemasForSubsettings:
- string
sensitiveDataModelId: string
targetId: string
tablespace: string
targetCredentials:
password: string
userName: string
targetId: string
unrelatedTablesAction: string
SubsettingPolicy 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 SubsettingPolicy resource accepts the following input properties:
- Compartment
Id string - (Updatable) The OCID of the compartment where the subsetting policy should be created
- Schema
Source SubsettingPolicy Schema Source - (Updatable) The source of subsetting schemas
- Check
Type string - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - Dictionary<string, string>
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- Display
Name string - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- Dictionary<string, string>
- (Updatable) 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 intReport Trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- Is
Redo boolLogging Enabled - (Updatable) 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 boolStats Enabled - (Updatable) 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 subsetted database tables after subsetting completes
- Masking
Policy stringId - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- Parallel
Degree string - (Updatable) 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 stringScript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- Pre
Subsetting stringScript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- Recompile string
- (Updatable) 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
- Tablespace string
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - Target
Credentials SubsettingPolicy Target Credentials - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - Target
Id string - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - string
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
- Compartment
Id string - (Updatable) The OCID of the compartment where the subsetting policy should be created
- Schema
Source SubsettingPolicy Schema Source Args - (Updatable) The source of subsetting schemas
- Check
Type string - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - map[string]string
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- Display
Name string - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- map[string]string
- (Updatable) 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 intReport Trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- Is
Redo boolLogging Enabled - (Updatable) 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 boolStats Enabled - (Updatable) 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 subsetted database tables after subsetting completes
- Masking
Policy stringId - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- Parallel
Degree string - (Updatable) 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 stringScript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- Pre
Subsetting stringScript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- Recompile string
- (Updatable) 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
- Tablespace string
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - Target
Credentials SubsettingPolicy Target Credentials Args - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - Target
Id string - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - string
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
- compartment_
id string - (Updatable) The OCID of the compartment where the subsetting policy should be created
- schema_
source object - (Updatable) The source of subsetting schemas
- check_
type string - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - map(string)
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- display_
name string - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- map(string)
- (Updatable) 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_ numberreport_ trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- is_
redo_ boollogging_ enabled - (Updatable) 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_ boolstats_ enabled - (Updatable) 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 subsetted database tables after subsetting completes
- masking_
policy_ stringid - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- parallel_
degree string - (Updatable) 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_ stringscript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- pre_
subsetting_ stringscript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- recompile string
- (Updatable) 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
- tablespace string
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - target_
credentials object - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - target_
id string - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - string
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
- compartment
Id String - (Updatable) The OCID of the compartment where the subsetting policy should be created
- schema
Source SubsettingPolicy Schema Source - (Updatable) The source of subsetting schemas
- check
Type String - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - Map<String,String>
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- display
Name String - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- Map<String,String>
- (Updatable) 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 IntegerReport Trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- is
Redo BooleanLogging Enabled - (Updatable) 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 BooleanStats Enabled - (Updatable) 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 subsetted database tables after subsetting completes
- masking
Policy StringId - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- parallel
Degree String - (Updatable) 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 StringScript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- pre
Subsetting StringScript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- recompile String
- (Updatable) 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
- tablespace String
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - target
Credentials SubsettingPolicy Target Credentials - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - target
Id String - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - String
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
- compartment
Id string - (Updatable) The OCID of the compartment where the subsetting policy should be created
- schema
Source SubsettingPolicy Schema Source - (Updatable) The source of subsetting schemas
- check
Type string - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - {[key: string]: string}
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- display
Name string - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- {[key: string]: string}
- (Updatable) 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 numberReport Trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- is
Redo booleanLogging Enabled - (Updatable) 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 booleanStats Enabled - (Updatable) 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 subsetted database tables after subsetting completes
- masking
Policy stringId - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- parallel
Degree string - (Updatable) 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 stringScript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- pre
Subsetting stringScript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- recompile string
- (Updatable) 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
- tablespace string
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - target
Credentials SubsettingPolicy Target Credentials - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - target
Id string - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - string
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
- compartment_
id str - (Updatable) The OCID of the compartment where the subsetting policy should be created
- schema_
source SubsettingPolicy Schema Source Args - (Updatable) The source of subsetting schemas
- check_
type str - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - Mapping[str, str]
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- display_
name str - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- Mapping[str, str]
- (Updatable) 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_ intreport_ trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- is_
redo_ boollogging_ enabled - (Updatable) 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_ boolstats_ enabled - (Updatable) 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 subsetted database tables after subsetting completes
- masking_
policy_ strid - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- parallel_
degree str - (Updatable) 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_ strscript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- pre_
subsetting_ strscript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- recompile str
- (Updatable) 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
- tablespace str
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - target_
credentials SubsettingPolicy Target Credentials Args - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - target_
id str - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - str
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
- compartment
Id String - (Updatable) The OCID of the compartment where the subsetting policy should be created
- schema
Source Property Map - (Updatable) The source of subsetting schemas
- check
Type String - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - Map<String>
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- display
Name String - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- Map<String>
- (Updatable) 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 NumberReport Trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- is
Redo BooleanLogging Enabled - (Updatable) 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 BooleanStats Enabled - (Updatable) 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 subsetted database tables after subsetting completes
- masking
Policy StringId - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- parallel
Degree String - (Updatable) 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 StringScript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- pre
Subsetting StringScript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- recompile String
- (Updatable) 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
- tablespace String
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - target
Credentials Property Map - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - target
Id String - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - String
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
Outputs
All input properties are implicitly available as output properties. Additionally, the SubsettingPolicy resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- State string
- The current state of the subsetting policy
- 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
- Id string
- The provider-assigned unique ID for this managed resource.
- State string
- The current state of the subsetting policy
- 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
- id string
- The provider-assigned unique ID for this managed resource.
- state string
- The current state of the subsetting policy
- 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
- id String
- The provider-assigned unique ID for this managed resource.
- state String
- The current state of the subsetting policy
- 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
- id string
- The provider-assigned unique ID for this managed resource.
- state string
- The current state of the subsetting policy
- 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
- id str
- The provider-assigned unique ID for this managed resource.
- state str
- The current state of the subsetting policy
- 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
- id String
- The provider-assigned unique ID for this managed resource.
- state String
- The current state of the subsetting policy
- 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
Look up Existing SubsettingPolicy Resource
Get an existing SubsettingPolicy 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?: SubsettingPolicyState, opts?: CustomResourceOptions): SubsettingPolicy@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
check_type: Optional[str] = None,
compartment_id: Optional[str] = None,
defined_tags: Optional[Mapping[str, str]] = None,
description: Optional[str] = None,
display_name: Optional[str] = None,
freeform_tags: Optional[Mapping[str, str]] = None,
generate_health_report_trigger: Optional[int] = None,
is_redo_logging_enabled: Optional[bool] = None,
is_refresh_stats_enabled: Optional[bool] = None,
masking_policy_id: Optional[str] = None,
parallel_degree: Optional[str] = None,
post_subsetting_script: Optional[str] = None,
pre_subsetting_script: Optional[str] = None,
recompile: Optional[str] = None,
schema_source: Optional[SubsettingPolicySchemaSourceArgs] = None,
state: Optional[str] = None,
tablespace: Optional[str] = None,
target_credentials: Optional[SubsettingPolicyTargetCredentialsArgs] = None,
target_id: Optional[str] = None,
time_created: Optional[str] = None,
time_updated: Optional[str] = None,
unrelated_tables_action: Optional[str] = None) -> SubsettingPolicyfunc GetSubsettingPolicy(ctx *Context, name string, id IDInput, state *SubsettingPolicyState, opts ...ResourceOption) (*SubsettingPolicy, error)public static SubsettingPolicy Get(string name, Input<string> id, SubsettingPolicyState? state, CustomResourceOptions? opts = null)public static SubsettingPolicy get(String name, Output<String> id, SubsettingPolicyState state, CustomResourceOptions options)resources: _: type: oci:DataSafe:SubsettingPolicy get: id: ${id}import {
to = oci_data_safe_subsetting_policy.example
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.
- Check
Type string - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - Compartment
Id string - (Updatable) The OCID of the compartment where the subsetting policy should be created
- Dictionary<string, string>
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- Display
Name string - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- Dictionary<string, string>
- (Updatable) 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 intReport Trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- Is
Redo boolLogging Enabled - (Updatable) 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 boolStats Enabled - (Updatable) 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 subsetted database tables after subsetting completes
- Masking
Policy stringId - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- Parallel
Degree string - (Updatable) 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 stringScript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- Pre
Subsetting stringScript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- Recompile string
- (Updatable) 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
Source SubsettingPolicy Schema Source - (Updatable) The source of subsetting schemas
- State string
- The current state of the subsetting policy
- Tablespace string
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - Target
Credentials SubsettingPolicy Target Credentials - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - Target
Id string - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - 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
- string
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
- Check
Type string - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - Compartment
Id string - (Updatable) The OCID of the compartment where the subsetting policy should be created
- map[string]string
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- Display
Name string - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- map[string]string
- (Updatable) 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 intReport Trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- Is
Redo boolLogging Enabled - (Updatable) 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 boolStats Enabled - (Updatable) 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 subsetted database tables after subsetting completes
- Masking
Policy stringId - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- Parallel
Degree string - (Updatable) 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 stringScript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- Pre
Subsetting stringScript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- Recompile string
- (Updatable) 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
Source SubsettingPolicy Schema Source Args - (Updatable) The source of subsetting schemas
- State string
- The current state of the subsetting policy
- Tablespace string
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - Target
Credentials SubsettingPolicy Target Credentials Args - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - Target
Id string - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - 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
- string
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
- check_
type string - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - compartment_
id string - (Updatable) The OCID of the compartment where the subsetting policy should be created
- map(string)
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- display_
name string - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- map(string)
- (Updatable) 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_ numberreport_ trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- is_
redo_ boollogging_ enabled - (Updatable) 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_ boolstats_ enabled - (Updatable) 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 subsetted database tables after subsetting completes
- masking_
policy_ stringid - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- parallel_
degree string - (Updatable) 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_ stringscript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- pre_
subsetting_ stringscript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- recompile string
- (Updatable) 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_
source object - (Updatable) The source of subsetting schemas
- state string
- The current state of the subsetting policy
- tablespace string
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - target_
credentials object - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - target_
id string - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - 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
- string
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
- check
Type String - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - compartment
Id String - (Updatable) The OCID of the compartment where the subsetting policy should be created
- Map<String,String>
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- display
Name String - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- Map<String,String>
- (Updatable) 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 IntegerReport Trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- is
Redo BooleanLogging Enabled - (Updatable) 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 BooleanStats Enabled - (Updatable) 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 subsetted database tables after subsetting completes
- masking
Policy StringId - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- parallel
Degree String - (Updatable) 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 StringScript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- pre
Subsetting StringScript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- recompile String
- (Updatable) 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
Source SubsettingPolicy Schema Source - (Updatable) The source of subsetting schemas
- state String
- The current state of the subsetting policy
- tablespace String
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - target
Credentials SubsettingPolicy Target Credentials - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - target
Id String - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - 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
- String
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
- check
Type string - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - compartment
Id string - (Updatable) The OCID of the compartment where the subsetting policy should be created
- {[key: string]: string}
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- display
Name string - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- {[key: string]: string}
- (Updatable) 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 numberReport Trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- is
Redo booleanLogging Enabled - (Updatable) 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 booleanStats Enabled - (Updatable) 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 subsetted database tables after subsetting completes
- masking
Policy stringId - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- parallel
Degree string - (Updatable) 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 stringScript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- pre
Subsetting stringScript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- recompile string
- (Updatable) 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
Source SubsettingPolicy Schema Source - (Updatable) The source of subsetting schemas
- state string
- The current state of the subsetting policy
- tablespace string
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - target
Credentials SubsettingPolicy Target Credentials - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - target
Id string - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - 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
- string
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
- check_
type str - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - compartment_
id str - (Updatable) The OCID of the compartment where the subsetting policy should be created
- Mapping[str, str]
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- display_
name str - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- Mapping[str, str]
- (Updatable) 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_ intreport_ trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- is_
redo_ boollogging_ enabled - (Updatable) 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_ boolstats_ enabled - (Updatable) 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 subsetted database tables after subsetting completes
- masking_
policy_ strid - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- parallel_
degree str - (Updatable) 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_ strscript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- pre_
subsetting_ strscript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- recompile str
- (Updatable) 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_
source SubsettingPolicy Schema Source Args - (Updatable) The source of subsetting schemas
- state str
- The current state of the subsetting policy
- tablespace str
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - target_
credentials SubsettingPolicy Target Credentials Args - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - target_
id str - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - 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
- str
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
- check
Type String - The health check type used when
generateHealthReportTriggeris incremented. Allowed values areALLandTABLESPACE_CHECK - compartment
Id String - (Updatable) The OCID of the compartment where the subsetting policy should be created
- Map<String>
- (Updatable) 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
- (Updatable) The description of the subsetting policy
- display
Name String - (Updatable) The display name of the subsetting policy. The name does not have to be unique, and it's changeable
- Map<String>
- (Updatable) 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 NumberReport Trigger An optional property that triggers Generate Health Report when incremented. The trigger runs after a policy update; use
oci.DataSafe.SubsettingPolicyHealthReportManagementwhen the report must be generated after creating separate subsetting rules.** 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
- is
Redo BooleanLogging Enabled - (Updatable) 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 BooleanStats Enabled - (Updatable) 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 subsetted database tables after subsetting completes
- masking
Policy StringId - (Updatable) The OCID of the masking policy to associate with this subsetting policy
- parallel
Degree String - (Updatable) 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 StringScript - (Updatable) A post-subsetting script, which can contain SQL and PL/SQL statements. It's executed after the subsetting process. It's usually used to perform additional transformation or cleanup work after subsetting data.
- pre
Subsetting StringScript - (Updatable) A pre-subsetting script, which can contain SQL and PL/SQL statements. It's executed before the subsetting process. It's usually used to perform any preparation or prerequisite work before subsetting data.
- recompile String
- (Updatable) 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
Source Property Map - (Updatable) The source of subsetting schemas
- state String
- The current state of the subsetting policy
- tablespace String
- The tablespace used by the health report when
generateHealthReportTriggeris incremented - target
Credentials Property Map - Credentials used by the health report when
generateHealthReportTriggeris incremented. Required when the trigger is changed. - target
Id String - The target database override used by the health report when
generateHealthReportTriggeris incremented. If omitted, the target associated with the policy is used. - 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
- String
- (Updatable) Strategy to be applied for tables which are not impacted by any of the subsetting rules
Supporting Types
SubsettingPolicySchemaSource, SubsettingPolicySchemaSourceArgs
- Schema
Source string - (Updatable) 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'
- Schemas
For List<string>Subsettings - (Updatable) The schemas to be subsetted
- Sensitive
Data stringModel Id - (Updatable) The OCID of the sensitive data model that's used as the source of subsetting schemas
- Target
Id string - (Updatable) The OCID of the target database that's used as the source of subsetting schemas
- Schema
Source string - (Updatable) The source of subsetting schemas
- Derived
Schemas []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'
- Schemas
For []stringSubsettings - (Updatable) The schemas to be subsetted
- Sensitive
Data stringModel Id - (Updatable) The OCID of the sensitive data model that's used as the source of subsetting schemas
- Target
Id string - (Updatable) The OCID of the target database that's used as the source of subsetting schemas
- schema_
source string - (Updatable) 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'
- schemas_
for_ list(string)subsettings - (Updatable) The schemas to be subsetted
- sensitive_
data_ stringmodel_ id - (Updatable) The OCID of the sensitive data model that's used as the source of subsetting schemas
- target_
id string - (Updatable) The OCID of the target database that's used as the source of subsetting schemas
- schema
Source String - (Updatable) 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'
- schemas
For List<String>Subsettings - (Updatable) The schemas to be subsetted
- sensitive
Data StringModel Id - (Updatable) The OCID of the sensitive data model that's used as the source of subsetting schemas
- target
Id String - (Updatable) The OCID of the target database that's used as the source of subsetting schemas
- schema
Source string - (Updatable) The source of subsetting schemas
- derived
Schemas 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'
- schemas
For string[]Subsettings - (Updatable) The schemas to be subsetted
- sensitive
Data stringModel Id - (Updatable) The OCID of the sensitive data model that's used as the source of subsetting schemas
- target
Id string - (Updatable) The OCID of the target database that's used as the source of subsetting schemas
- schema_
source str - (Updatable) 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'
- schemas_
for_ Sequence[str]subsettings - (Updatable) The schemas to be subsetted
- sensitive_
data_ strmodel_ id - (Updatable) The OCID of the sensitive data model that's used as the source of subsetting schemas
- target_
id str - (Updatable) The OCID of the target database that's used as the source of subsetting schemas
- schema
Source String - (Updatable) 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'
- schemas
For List<String>Subsettings - (Updatable) The schemas to be subsetted
- sensitive
Data StringModel Id - (Updatable) The OCID of the sensitive data model that's used as the source of subsetting schemas
- target
Id String - (Updatable) The OCID of the target database that's used as the source of subsetting schemas
SubsettingPolicyTargetCredentials, SubsettingPolicyTargetCredentialsArgs
Import
SubsettingPolicies can be imported using the id, e.g.
$ pulumi import oci:DataSafe/subsettingPolicy:SubsettingPolicy test_subsetting_policy "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.
published on Tuesday, Oct 13, 2026 by Pulumi