The DataBee Create/Edit Command Rule Form

This form is used to create and edit DataBee Command rules which are designed to run user written PL/SQL statements. The title text and button labels on the form will change as is appropriate to the create or edit mode. In the example screen shot above, the form is editing an existing Command rule.

Both extraction and loader sets can have any number of Command rules created within them. Within extraction sets, Command rules can execute in either stage 1 or stage 3 of the extraction process. Loader sets do not have the concept of stages. In both extraction and loader sets, rule blocks must be used to explicitly specify the execution order of the command rules.

Any valid PL/SQL statement which performs data manipulation actions (INSERT, UPDATE, DELETE) or DDL commands (CREATE INDEX, DROP TABLE etc) is valid within a DataBee Command rule. It is possible to implement an unlimited number of SQL statements in a Command rule. See the discussion in the Command rule help file for more information.

The Ignore ORA- errors panel permits the execution of the rule (and hence the masking set) to continue if the specified error occurs. Note that if multiple SQL statements are placed in the same Command rule, the Oracle error exception handler applies to them all. See the discussion in the Command rule help file for a detailed information.

There are two modes of operation: Script mode which runs the commands as a script or PL/SQL mode which runs the commands as a PL/SQL block. The primary difference between the two modes is the wrapper placed around the SQL Statements prior to execution. When the rule is placed in PL/SQL mode the contents are inserted into an anonymous PL/SQL block. For most cases Script mode will be used. PL/SQL mode is usually only required when specialized and complex anonymous PL/SQL blocks are required. See the discussion in the Command rule help file for more information and examples.

Each Command rule will execute a commit statement after all SQL statements in the rule complete. If multiple SQL statements are used, commits can be placed in the sequence as is required.

Existing Command rules can be edited by double clicking on them with the mouse. Command rules are created by launching the New Command rule form using the New Rule button located on the lower right hand corner of the main form in the Set Designer application. Creating or editing the contents of a Command rule is a straightforward process. Once the Command rule form is open, simply enter the PL/SQL statements you wish to execute in the SQL Command window and press the Create/Update Command Rule button. It can be useful to enter a summary of the rules purpose in the Description area.

How to Create a New Command Rule