Saving a Subset Script

To prepare and submit a job to save a subset script:

  1. Select the definition within the table, open the Actions menu, then select Save Subset Script. The Subset Mode pop-up appears.

  2. Select a target database that is either the same target database you used to create the subset model, or similar to this database regarding the table schema and objects.

  3. Decide if you want to create a subset by writing subset data to export files, or by deleting data from a target database.

    Choosing to delete data creates an in-place subset by removing/deleting unwanted data from a cloned copy of the production database, rather than a production database. Only data satisfying the rules are retained. You should never use this option on a production database.

    Select either Named Credentials or New Credentials if you have not already set preferred credentials.

    If you have defined any parameters from the Rule Parameters tab, they appear in the table at the bottom. You can change a parameter value by clicking on the associated field in the Value column.

  4. Click Continue to access the Parameters pop-up. The contents of the pop-up depend on whether you chose the export or delete option in the previous step.

    For Writing Subset Data to Export Files, provide the requisite information, then click Continue to schedule the job.

    • Specify a subset directory where to save the export dump. The drop-down list consists of directory objects for which you have access. Alternatively, you can select a custom directory path. Click the check box if you want to speed the process by using an external directory. Recommended default: DATA_PUMP_DIR.

    • Specify appropriate values if you want to override the defaults: enter a name for the export file; specify a maximum file size in megabytes; specify the maximum number of threads of active execution operating on behalf of the export job. This enables you to consider trade-offs between resource consumption and elapsed time.

    • Select whether to enable dump file compression and encryption. Enter and confirm an encryption password, if appropriate. Log file generation is selected by default.

    For Deleting Data From a Target Database, provide the requisite information, then click Continue to schedule the job.

    • Specify a subset directory where to save the subset scripts. The drop-down list consists of directory objects for which you have access. Alternatively, you can select a custom directory path. Recommended default: DATA_FILE_DIR.

    • You must enable the check box indicating that the selected target is not a production database in order to proceed.

  5. Click Continue. A progress indicator tracks script generation. When complete, the Files table lists the results of script generation.

  6. Click Download. In the File Download pop-up that appears, click Save.

  7. In the Save As pop-up that appears, navigate to a file location and click Save.

    The file containing the scripts (SubsetBundle.zip) now appears at the specified location on your desktop.

To run the saved script at a later time:

  1. Port the ZIP file to the target database and extract it to a directory on which you have the requisite privileges.

  2. Change directory to where you extracted the files.

  3. Execute the following script from the SQL command line:

    subset_exec.sql

    Note that if you want to change generated parameter settings, you can do so by editing the following file in a text editor prior to executing the script:

    subset_exec_params.lst