Table of Contents

Search

  1. Preface
  2. Introduction to the Stored Procedure Accelerator for Oracle
  3. Masking Stored Procedures and User-Defined Table Functions
  4. Stored Procedure Accelerator Setup
  5. Stored Procedure Accelerator Rules

Stored Procedure Accelerator Guide for Oracle

Stored Procedure Accelerator Guide for Oracle

Blocks Containing Multiple Stored Procedure Calls

Blocks Containing Multiple Stored Procedure Calls

If a block contains multiple stored procedure calls, Dynamic Data Masking recognizes the first call, but does not recognize the following calls.
For example, you want to mask the output of the following stored procedure:
dummy_proc_table2( in_int integer, o_int integer, o_table ddmtabletype) ; -- ddmtabletype is a TABLE Type defined at SCHEMA level
The following text is an example of a call that masks the incorrect stored procedure:
Declare v_table ddmtabletype; begin -- first procedure call dummy_proc_table_3( in_int => 12, v_table => v_table ); --second procedure call dummy_proc_table2( in_int => 12, o_int => :o_int, o_var => :o_var, v_table => v_table ); end;
Because the first stored procedure in the call is dummy_proc_table_3, the stored procedure accelerator masks the dummy_proc_table_3 procedure, and does not mask the dummy_proc_table2 procedure.
The following text is an example of a call that masks the correct procedure:
Declare v_table ddmtabletype; begin -- first procedure call dummy_proc_table2( in_int => 12, o_int => :o_int, o_var => :o_var, v_table => v_table ); --second procedure call dummy_proc_table_3( in_int => 12, v_table => v_table ); end;
Because dummy_proc_table2 is the first procedure in the block, it is masked. However, in the example above, the dummy_proc_table_3 procedure is not masked.

0 COMMENTS

We’d like to hear from you!