Running and Stopping Jobs

This section describes how users can run and stop jobs.

Submitting a job

To submit or resubmit a job, Click the (…) button to the right of the corresponding job row under the Actions column and click Run . If the user doesn’t have permission to run the job, then it will be disabled.

Upon submitting the job, the masking engine will check if there are enough resources allocated to simultaneously running jobs to determine whether to run or queue the submitted job. There are two resources that the submitted job will be verified against.

1. Maximum memory for all running jobs.

   • This limit defaults to a dynamic calculation of 75% of the entire system's available memory minus 6GB, which is reserved for the masking web application. This calculation can be manually overridden by setting the general application setting MaximumMemoryForJobs. To revert a manually overridden limit back to the dynamically calculated limit, set the MaximumMemoryForJobs to 0.

2. Maximum number of simultaneously running jobs.

   • This limit defaults to 7 simultaneously running jobs. However, this default value can be overridden by setting the general application setting NumSimulJobsAllowed to a different value. Users will need to modify this setting via the Masking API or the User Interface (Application Settings).

If the submitted job causes all of the currently running jobs to exceed either of those limits, the job will be queued and run at a later time when enough of the other jobs stop running to free up resources. To view the the position of the job in the queue, navigate to the Monitor Screen.

Once the job starts Running, the status will be changed. Editing/Deleting a Job is not allowed while it is running. When the job is completed, the status will change automatically.

Submitting a Multi-tenant Jobs

When the Multi tenant option is selected while creating a job, the User can select connector at the time of running a job. This option allows existing rulesets to be reused to mask identical schemas via different connectors. The displayed values in Environment and Connector dropdowns are defaults that are set during job creation. User can modify them as needed.

1. In-Place Job → The User can select the Target connector at the job execution time

   

2. On-The-Fly Job → User can select Source and Target connectors at the job execution time

   

Stopping a Job

To stop a job, Click the (…) button to the right of the corresponding job row under the Actions column and click Cancel . If the user doesn’t have permission to run the job, then it will be disabled.

On clicking Cancel Action, it will prompt for confirmation. Click on Confirm to cancel the job.

On clicking Confirm, the job will be cancelled and the status will be changed to CANCELLED.

Stopping a RUNNING job will result in semi-masked data and terminate all subsequent transactions related to this job execution. Any dropped indexes, constraints, or triggers will not be recreated.. Stopping a QUEUED job will have no impact on the data source since the execution of the job has not yet begun. If email notifications are enabled, stopping a QUEUED job will send an email to the user who created the job indicating that it has been canceled by the user who stopped the job.

Enabling and disabling database constraints in Jobs

Depending on the type of target database you are using, the Delphix Engine can automatically enable and disable database constraints.

The ability to enable and disable constraints ensures that the Delphix Engine can update columns that have primary key or foreign key relationships. You can set Delphix to handle constraints automatically by enabling the Disable Constraints checkbox on a Masking job. If the built-in or extended connector is using a driver support plugin, Disable Constraints can be enabled via Enable Tasks. For a full list of supported built-in connectors and information on specific built-in driver support plugins, see Built-in Driver Supports.

Delphix does not support the enable/disable constraints feature for all databases. To see which databases are supported, see the Data Source Support page.

Creating SQL statements to run before and after jobs

When you create a masking job or a certification job, you can specify standard, static SQL statements to run before (prescript) you run a job and/or after (postscript) the job has been completed.

You can create prescripts and postscripts by writing SQL statement(s) in a text document. If the text file contains multiple SQL statements, each statement must be separated by a semicolon [;]. For example, to remove records with date_column before December 12th, 2017 before masking a table (owner.table), one would create a prescript file containing the following and associate the prescript file to the masking job that includes the table in its ruleset:

DELETE FROM owner.table WHERE date_column < ‘20171207’;

Database-specific, SQL programming extensions (such as PL/SQL and Transact-SQL) and dynamic SQL statements are not supported in prescripts and postscripts. However, you can create procedures and functions using your database tooling of choice and call them using standard SQL statements from a prescript or postscript.

Schema-altering SQL cannot be executed as a pre-script because the JDBC connection is already established, and the schema is loaded before the pre-script runs.