Deletion_By_Rule_Log
view
The
IS_Public.Deletion_By_Rule_Log
view provides information on the status of the
deletion jobs in the queue in relation to each
rule. The view also contains details on the
results of each deletion job that is run.
You can access the view to check the status of
a deletion-by-rule job. For more information, see
Verifying deletion by rule.
After the deletion job is run, the
IS_Public.Deletion_By_Rule_Log
view contains one or more entries per job that
describe the result for each item type. For more
information, see Sample use cases.
The information that is contained in the
IS_Public.Deletion_By_Rule_Log
view is described in the following table.
Column name | Description |
---|---|
status |
Status of the deletion by rule job:
|
rule_name |
Name of the deletion rule. |
view_name |
Name of the view that the rule is targeting. |
conditions |
Deletion conditions that are applied by the rule. |
job_id |
Identifier for the job, which is also used
to identify the job in the job_id
column of the
Ingestion_Deletion_Reports
view. |
job_creation_time |
Time stamp that indicates when the deletion by rule job was created. |
job_run_time |
Time stamp that indicates when the deletion by rule job was run and corresponds to the value in the |
item_type |
Item type of the records that were deleted. There can be more than one entry in this view for the same job. For example, deleting entity records can also cause link records to be deleted. |
delete_count |
The number of records that are deleted. |
reject_count |
The number of records that are rejected. |
Example of job results logged
See the following tables for an example of how
the
IS_Public.Deletion_By_Rule_Log
view might look with completed job details.
status | rule_name | view_name | conditions |
---|---|---|---|
Succeeded | OLD ACCOUNTS | E_Account_DV | p_date_opened < CURRENT_DATE - 50 YEARS |
Succeeded | OLD ACCOUNTS | E_Account_DV | p_date_opened < CURRENT_DATE - 50 YEARS |
job_id | job_creation_time | job_run_time | item_type | delete_count | reject_count |
---|---|---|---|---|---|
77 | 2017-12-12 14:29:11.351 | 2017-12-12 14:29:16.467 | LAC1 | 3 | 0 |
77 | 2017-12-12 14:29:11.351 | 2017-12-12 14:29:16.467 | LTR1 | 3 | 0 |
In this example, deleting three Account entity records caused the deletion in the same job of three Transaction link records that were attached to the Accounts.