IBM Cloud Pak® for Data Version 4.7 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.
Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.7 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.
Rules reporting tables (Watson Knowledge Catalog)
Check the Postgres, Db2 , and Oracle statements for the tables that are related to data protection rules.
| Subject area | Table name | Description |
|---|---|---|
| Rules | enforcement_rules | The data protection rules that are defined. |
enforcement_rules table
This table contains information about the enforcement rules (data protection rules) that are defined.
This table has the following columns:
rule_id- The identifier of the rule.rule_type- The type of the rule.name- The name of the rule.created_by- The identifier of the user that created the rule.created_on- The timestamp when the rule was created.modified_by- The identifier of the user that last modified the rule.modified_on- The timestamp when the rule was last modified.description- The description of the rule.action_name- The type of the action that this rule enforces.rule_json- The JSON representation of the defined rule.
Postgres
CREATE TABLE statement:
create table enforcement_rules(rule_id varchar(36) not null,
rule_type varchar(128) not null,
name varchar(256) not null,
description text,
action_name varchar(256) not null,
created_on timestamp(6) not null,
created_by varchar(128) not null,
modified_on timestamp(6),
modified_by varchar(128),
rule_json text not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(rule_id));
Db2
CREATE TABLE statement:
create table enforcement_rules(rule_id varchar(36) not null,
rule_type varchar(128) not null,
name varchar(256) not null,
description clob,
action_name varchar(256) not null,
created_on timestamp(12) not null,
created_by varchar(128) not null,
modified_on timestamp(12),
modified_by varchar(128),
rule_json clob not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(rule_id),
period SYSTEM_TIME (tech_start,
tech_end) )
Oracle
CREATE TABLE statement:
CREATE TABLE enforcement_rules(rule_id varchar(36) NOT NULL,
rule_type varchar(128) NOT NULL,
name varchar(256) NOT NULL,
description clob,
action_name varchar(256) NOT NULL,
created_on timestamp(6) NOT NULL,
created_by varchar(128) NOT NULL,
modified_on timestamp(6),
modified_by varchar(128),
rule_json clob NOT NULL,
tech_start TIMESTAMP(6) DEFAULT SYSTIMESTAMP NOT NULL,
tech_end TIMESTAMP(6) DEFAULT to_timestamp('9999-12-30', 'YYYY-MM-DD') NOT NULL,
ts_id TIMESTAMP(6) DEFAULT SYSTIMESTAMP NOT NULL,
PRIMARY KEY(rule_id))
Learn more
Parent topic: Reporting tables