Customizations reporting tables (IBM Knowledge Catalog)

Check the Postgres, Db2 , and Oracle statements for the tables that contain custom roles, relationships, attributes, properties and others.

Subject area	Table name	Description
Customizations	category_custom_roles	The custom category roles.
Customizations	glossary_custom_relationship_def	The custom relationship definitions.
Customizations	glossary_ca_attr_artifact_type_assoc	The supported artifact types for custom attribute definition.
Customizations	glossary_custom_relationship_nodes	The source and target artifact type for custom relationship definitions.
Customizations	glossary_custom_attr_def	The custom attribute definitions.
Customizations	glossary_ca_enum_list	the custom attribute definitions of ENUM type.
Customizations	governance_artifact_custom_attr_values	The custom attribute values.
Customizations	asset_custom_properties	The custom properties group assigned to an asset type and the property under that group.
Customizations	asset_type_custom_properties	The type of custom property and its associated custom group.
Customizations	asset_prop_enum_list	The custom property of type `enumeration`.
Customizations	asset_custom_prop_values	The the values assigned to the custom properties which are defined against the asset.

category_custom_roles table

This table contains information about the custom category roles.

This table has the following columns:

role_id - The identifier of the category custom role.
role_name - The name of the category custom role.

Postgres

CREATE TABLE statement:

create table category_custom_roles(role_id varchar(32) not null,
role_name varchar(128) not null,
primary key(role_id))

Db2

CREATE TABLE statement:

create table category_custom_roles(role_id varchar(32) not null,
role_name varchar(128) not null,
primary key(role_id)) ORGANIZE by row

Oracle

CREATE TABLE statement:

CREATE TABLE category_custom_roles(role_id varchar(32) NOT NULL,
	role_name varchar(128) NOT NULL,
	PRIMARY KEY(role_id))

glossary_custom_relationship_def table

This table contains information about the custom relationship definitions.

This table has the following columns:

cr_definition_id - The identifier of the custom relationship definition.
artifact_id - The identifier of the custom relationship definition.
name - The name of the custom relationship definition.
created_on - The creation date of the custom relationship definition.
created_by - The person who created the custom relationship definition.
modified_on - The modification date of the custom relationship definition.
modified_by - The person who modified the custom relationship definition.
system_id - The system identifier where custom relationship definition is created.
type - The type of custom relationship definition.
reverse_name - The reverse relationship name of custom relationship definition.
description - The description of the custom relationship definition.
read_only - Specifies whether custom relationship definition is read only or not.
default_value - The default value of custom relationship definition.
multiple_values - Specifies whether custom relationship definition can have multiple values or not.

Postgres

CREATE TABLE statement:

create table glossary_custom_relationship_def(cr_definition_id varchar(128) not null,
artifact_id varchar(128) not null,
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),
system_id varchar(128),
type varchar(128) not null,
reverse_name varchar(256) not null,
description varchar(256),
read_only boolean not null,
default_value text,
multiple_values boolean 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(cr_definition_id))

Db2

CREATE TABLE statement:

create table glossary_custom_relationship_def(cr_definition_id varchar(128) not null,
artifact_id varchar(128) not null,
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),
system_id varchar(128),
type varchar(128) not null,
reverse_name varchar(256) not null,
description varchar(256),
read_only boolean not null,
default_value clob(128),
multiple_values boolean 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(cr_definition_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

Oracle

CREATE TABLE statement:

CREATE TABLE glossary_custom_relationship_def(cr_definition_id varchar(128) NOT NULL,
	artifact_id varchar(128) NOT NULL,
	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),
	system_id varchar(128),
	TYPE varchar(128) NOT NULL,
	reverse_name varchar(256) NOT NULL,
	description varchar(256),
	read_only decimal(1) NOT NULL,
	default_value clob,
	multiple_values decimal(1) 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(cr_definition_id))

glossary_ca_attr_artifact_type_assoc table

This table contains information about the supported artifact types for custom attribute definition.

This table has the following columns:

ca_definition_id - The identifier of the custom attribute definition.
artifact_type - The artifact type for which custom relationship definition is applicable.

Postgres

CREATE TABLE statement:

create table glossary_ca_attr_artifact_type_assoc(ca_definition_id varchar(128) not null,
artifact_type varchar(256) 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(ca_definition_id,
artifact_type))

ALTER TABLE statement:

alter table glossary_ca_attr_artifact_type_assoc add constraint fk_glossary_ca_attr_artifact_type_assoc_glossary_custom_attr_def_1 foreign key (ca_definition_id) references glossary_custom_attr_def(ca_definition_id) on
delete
	cascade on
	update
	no action

Db2

CREATE TABLE statement:

create table glossary_ca_attr_artifact_type_assoc(ca_definition_id varchar(128) not null,
artifact_type varchar(256) 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(ca_definition_id,
artifact_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

ALTER TABLE "BITNT2DBSAVIKASH1".glossary_ca_attr_artifact_type_assoc ADD CONSTRAINT fk_glossary_ca_attr_artifact_type_assoc_glossary_custom_attr_def_1 FOREIGN KEY (ca_definition_id) REFERENCES "BITNT2DBSAVIKASH1".glossary_custom_attr_def(ca_definition_id) ON DELETE CASCADE  ON UPDATE NO ACTION

Oracle

CREATE TABLE statement:

CREATE TABLE glossary_ca_attr_artifact_type_assoc(ca_definition_id varchar(128) NOT NULL,
	artifact_type varchar(256) 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(ca_definition_id,
	artifact_type))

ALTER TABLE statement:

ALTER TABLE glossary_ca_attr_artifact_type_assoc ADD CONSTRAINT fk_glossary_ca_attr_artifact_type_assoc_glossary_custom_attr_def_1 FOREIGN KEY (ca_definition_id) REFERENCES glossary_custom_attr_def(ca_definition_id) ON
	DELETE
	CASCADE

glossary_custom_relationship_nodes table

This table contains information about the source and target artifact type for custom relationship definitions.

This table has the following columns:

cr_definition_id - The identifier of the custom relationship definition.
end1_artifact_type - The source artifact type of the custom relationships.
end2_artifact_type - The target artifact type of the custom relationships.

Postgres

CREATE TABLE statement:

create table glossary_custom_relationship_nodes(cr_definition_id varchar(128) not null,
end1_artifact_type varchar(128) not null,
end2_artifact_type varchar(128) 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(cr_definition_id,
end1_artifact_type,
end2_artifact_type))

ALTER TABLE statement

alter table glossary_custom_relationship_nodes add constraint fk_glossary_custom_relationship_nodes_glossary_custom_relationship_def_3 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
	cascade on
	update
	no action

Db2

CREATE TABLE statement:

create table glossary_custom_relationship_nodes(cr_definition_id varchar(128) not null,
end1_artifact_type varchar(128) not null,
end2_artifact_type varchar(128) 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(cr_definition_id,
end1_artifact_type,
end2_artifact_type),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement

alter table glossary_custom_relationship_nodes add constraint fk_glossary_custom_relationship_nodes_glossary_custom_relationship_def_3 foreign key (cr_definition_id) references glossary_custom_relationship_def(cr_definition_id) on
delete
	cascade on
	update
	no action

Oracle

CREATE TABLE statement:

CREATE TABLE glossary_custom_relationship_nodes(cr_definition_id varchar(128) NOT NULL,
	end1_artifact_type varchar(128) NOT NULL,
	end2_artifact_type varchar(128) 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(cr_definition_id,
	end1_artifact_type,
	end2_artifact_type))

ALTER TABLE statement

ALTER TABLE glossary_custom_relationship_nodes ADD CONSTRAINT fk_glossary_custom_relationship_nodes_glossary_custom_relationship_def_3 FOREIGN KEY (cr_definition_id) REFERENCES glossary_custom_relationship_def(cr_definition_id) ON
	DELETE
	CASCADE

glossary_custom_attr_def table

This table contains information about the custom attribute definitions.

This table has the following columns:

ca_definition_id - The identifier of the custom attribute definition.
global_id - The global identifier of the custom attribute definition.
name - The name of the custom attribute definition.
created_on - The creation date of the custom attribute definition.
created_by - The person who created the custom attribute definition.
modified_on - The modification date of the custom attribute definition.
modified_by - The person who modified the custom attribute definition.
system_id - The system identified where custom attribute definition is created.
type - The type of custom attribute definition.
read_only - Specifies whether custom attribute definition is read only or not.
default_value - The default value of custom attribute definition.
multiple_values - Specifies whether custom attribute definition can have multiple values or not.

Postgres

CREATE TABLE statement:

create table glossary_custom_attr_def(ca_definition_id varchar(128) not null,
global_id varchar(256) not null,
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),
system_id varchar(128),
type varchar(128) not null,
read_only boolean not null,
default_value text,
multiple_values boolean 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(ca_definition_id))

Db2

CREATE TABLE statement:

create table glossary_custom_attr_def(ca_definition_id varchar(128) not null,
global_id varchar(256) not null,
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),
system_id varchar(128),
type varchar(128) not null,
read_only boolean not null,
default_value clob,
multiple_values boolean 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(ca_definition_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

Oracle

CREATE TABLE statement:

CREATE TABLE glossary_custom_attr_def(ca_definition_id varchar(128) NOT NULL,
	global_id varchar(256) NOT NULL,
	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),
	system_id varchar(128),
	TYPE varchar(128) NOT NULL,
	read_only decimal(1) NOT NULL,
	default_value clob,
	multiple_values decimal(1) 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(ca_definition_id))

glossary_ca_enum_list table

This table contains information about the custom attribute definitions of ENUM type.

This table has the following columns:

ca_definition_id - The identifier of the custom attribute definition of enum type.
value - The value of the custom attribute definition of enum type.
description - The description of the custom attribute definition.

Postgres

CREATE TABLE statement:

create table glossary_ca_enum_list(ca_definition_id varchar(128) not null,
value varchar(128) not null,
description varchar(256),
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(ca_definition_id,
value))

ALTER TABLE statement:

alter table "BITNT2DBSAVIKASH1".glossary_ca_enum_list add constraint fk_glossary_ca_enum_list_glossary_custom_attr_def_2 foreign key (ca_definition_id) references "BITNT2DBSAVIKASH1".glossary_custom_attr_def(ca_definition_id) on
delete
	cascade on
	update
	no action

Db2

CREATE TABLE statement:

create table glossary_ca_enum_list(ca_definition_id varchar(128) not null,
value varchar(128) not null,
description varchar(256),
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(ca_definition_id,
value),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row

ALTER TABLE statement:

alter table glossary_ca_enum_list add constraint fk_glossary_ca_enum_list_glossary_custom_attr_def_2 foreign key (ca_definition_id) references glossary_custom_attr_def(ca_definition_id) on
delete
	cascade on
	update
	no action

Oracle

CREATE TABLE statement:

CREATE TABLE glossary_ca_enum_list(ca_definition_id varchar(128) NOT NULL,
	value varchar(128) NOT NULL,
	description varchar(256),
	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(ca_definition_id,
	value))

ALTER TABLE statement:

ALTER TABLE glossary_ca_enum_list ADD CONSTRAINT fk_glossary_ca_enum_list_glossary_custom_attr_def_2 FOREIGN KEY (ca_definition_id) REFERENCES glossary_custom_attr_def(ca_definition_id) ON
	DELETE
	CASCADE

governance_artifact_custom_attr_values table

This table contains information about the custom attribute values.

This table has the following columns:

artifact_id - The identifier of the custom relationship definition.
ca_definition_id - The identifier of the custom attribute definition.
value_id - The identifier of the custom attribute value.
text_value - The text value of custom attribute.
num_value - The numerical value of custom attribute.
date_value - The date value of custom attribute.
value_type - The type of custom properties value.

Postgres

CREATE TABLE statement:

CREATE TABLE governance_artifact_custom_attr_values(
  artifact_id varchar(128) NOT NULL,ca_definition_id varchar(128) NOT NULL,
  value_id varchar(128) NOT NULL,text_value text,num_value double precision,
  date_value timestamp(6),value_type varchar(16),
  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(artifact_id,ca_definition_id,value_id))

ALTER TABLE statement:

alter table governance_artifact_custom_attr_values add constraint fk_governance_artifact_custom_attr_values_glossary_custom_attr_def_12 foreign key (ca_definition_id) references glossary_custom_attr_def(ca_definition_id) on
delete
	cascade on
	update
	no action

Db2

CREATE TABLE statement:

CREATE TABLE governance_artifact_custom_attr_values(
  artifact_id varchar(128) NOT NULL,ca_definition_id 
  varchar(128) NOT NULL,value_id varchar(128) NOT NULL,
  text_value text,num_value double precision,
  date_value timestamp(6),value_type varchar(16),
  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(artifact_id,ca_definition_id,value_id))

ALTER TABLE statement:

alter table governance_artifact_custom_attr_values add constraint fk_governance_artifact_custom_attr_values_glossary_custom_attr_def_12 foreign key (ca_definition_id) references glossary_custom_attr_def(ca_definition_id) on
delete
	cascade on
	update
	no action

Oracle

CREATE TABLE statement:

CREATE TABLE "globalschema".governance_artifact_custom_attr_values(
  artifact_id varchar(128) NOT NULL,ca_definition_id varchar(128) NOT NULL,
  value_id varchar(128) NOT NULL,text_value text,num_value double precision,
  date_value timestamp(6),value_type varchar(16),
  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(artifact_id,ca_definition_id,value_id))

ALTER TABLE statement:

ALTER TABLE governance_artifact_custom_attr_values ADD CONSTRAINT fk_governance_artifact_custom_attr_values_glossary_custom_attr_def_12 FOREIGN KEY (ca_definition_id) REFERENCES glossary_custom_attr_def(ca_definition_id) ON
	DELETE
	CASCADE

asset_custom_properties table

This table has the following columns:

property_id - The identifier for the custom property.
group_id -The identifier for the group type that has properties defined under it.
property_type - Defines the type for custom property.
property_is_array - Defines if a property has multiple values.
property_name - `The asset custom property name.
description - The description of an asset custom property.
property_group_name - The group name of an asset custom property.
is_column_property - Identify the column property is set.

Postgres

CREATE TABLE statement:

CREATE TABLE asset_custom_properties (
	property_id varchar(256) NOT NULL,
	property_group_id varchar(256) NOT NULL,
	property_type varchar(128) NOT NULL,
	property_name varchar(256) NOT NULL,
	property_group_name varchar(256) NOT NULL,
	property_is_array numeric(1) NOT NULL,
	description varchar(256) NULL,
	is_column_property numeric(1) NULL,
	tech_start timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
	tech_end timestamp(6) NOT NULL DEFAULT to_timestamp('9999-12-30'::text, 'YYYY-MM-DD'::text),
	ts_id timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
	CONSTRAINT asset_custom_properties_is_column_property_check CHECK ((is_column_property = ANY (ARRAY[(0)::numeric, (1)::numeric]))),
	CONSTRAINT asset_custom_properties_pkey PRIMARY KEY (property_id, property_group_id),
	CONSTRAINT asset_custom_properties_property_is_array_check CHECK ((property_is_array = ANY (ARRAY[(0)::numeric, (1)::numeric])))
);

ALTER TABLE statement:

ALTER TABLE IF EXISTS  asset_custom_properties
    OWNER to postgres;

Db2

CREATE TABLE statement:

CREATE TABLE asset_custom_properties(property_id varchar(256) NOT NULL,
property_group_id varchar(256) NOT NULL,
property_type varchar(128) NOT NULL,
property_name varchar(256) NOT NULL,
property_group_name varchar(256) NOT NULL,
property_is_array decimal(1) CHECK (property_is_array IN (0, 1)) NOT NULL,
description varchar(256),
is_column_property decimal(1) CHECK (is_column_property IN (0, 1)), 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(property_id,
property_group_id),
PERIOD SYSTEM_TIME (tech_start,
tech_end) )

ALTER TABLE statement:

ALTER TABLE IF EXISTS  asset_custom_properties
    OWNER to postgres;

Oracle

CREATE TABLE statement:

CREATE TABLE "ASSET_CUSTOM_PROPERTIES" 
   (	"PROPERTY_ID" VARCHAR2(256) NOT NULL ENABLE, 
	"PROPERTY_GROUP_ID" VARCHAR2(256) NOT NULL ENABLE, 
	"PROPERTY_TYPE" VARCHAR2(128) NOT NULL ENABLE, 
	"PROPERTY_NAME" VARCHAR2(256) NOT NULL ENABLE, 
	"PROPERTY_GROUP_NAME" VARCHAR2(256) NOT NULL ENABLE, 
	"PROPERTY_IS_ARRAY" NUMBER(1,0) NOT NULL ENABLE, 
	"DESCRIPTION" VARCHAR2(256), 
	"IS_COLUMN_PROPERTY" NUMBER(1,0), 
	"TECH_START" TIMESTAMP (6) DEFAULT SYSTIMESTAMP NOT NULL ENABLE, 
	"TECH_END" TIMESTAMP (6) DEFAULT to_timestamp('9999-12-30','YYYY-MM-DD') NOT NULL ENABLE, 
	"TS_ID" TIMESTAMP (6) DEFAULT SYSTIMESTAMP NOT NULL ENABLE, 
	 CHECK (property_is_array in (0,1)) ENABLE, 
	 CHECK (is_column_property in (0,1)) ENABLE, 
	 PRIMARY KEY ("PROPERTY_ID", "PROPERTY_GROUP_ID")
  USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS 
  TABLESPACE "USERS"  ENABLE
   ) SEGMENT CREATION DEFERRED 
  PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 
 NOCOMPRESS LOGGING
  TABLESPACE "USERS" ;

asset_type_custom_properties table

This table has the following columns:

property_id - The identifier for the custom property.
group_id - The identifier for the group type that has property defined underneath.
asset_type - The type of asset for which the custom property is defined.

Postgres

CREATE TABLE statement:

CREATE TABLE IF NOT EXISTS asset_type_custom_properties (
  property_id character varying(256) COLLATE pg_catalog.default NOT NULL,
  property_group_id character varying(256) COLLATE pg_catalog.default NOT NULL,
  asset_type character varying(128) COLLATE pg_catalog.default NOT NULL,
  tech_start timestamp(6) without time zone NOT NULL DEFAULT CURRENT_TIMESTAMP,
  tech_end timestamp(6) without time zone NOT NULL DEFAULT to_timestamp('9999-12-30' :: text, 'YYYY-MM-DD' :: text),
  ts_id timestamp(6) without time zone NOT NULL DEFAULT CURRENT_TIMESTAMP,
  CONSTRAINT asset_type_custom_properties_pkey PRIMARY KEY (property_id, property_group_id, asset_type),
  CONSTRAINT fk_asset_type_custom_properties_asset_custom_properties_1 FOREIGN KEY (property_id, property_group_id) REFERENCES asset_custom_properties (property_id, property_group_id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE CASCADE
)

ALTER TABLE statement:

ALTER TABLE IF EXISTS  asset_type_custom_properties
    OWNER to postgres;

Db2

CREATE TABLE statement:

CREATE TABLE ASSET_TYPE_CUSTOM_PROPERTIES (
  PROPERTY_ID VARCHAR(256 OCTETS) NOT NULL,
  PROPERTY_GROUP_ID VARCHAR(256 OCTETS) NOT NULL,
  ASSET_TYPE VARCHAR(128 OCTETS) 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,
  PERIOD SYSTEM_TIME (TECH_START, TECH_END)
) IN USERSPACE1 ORGANIZE BY ROW;

ALTER TABLE statements:

ALTER TABLE
  ASSET_TYPE_CUSTOM_PROPERTIES
ADD
  PRIMARY KEY (
    PROPERTY_ID,
    PROPERTY_GROUP_ID,
    ASSET_TYPE
  ) ENFORCED;

ALTER TABLE
  ASSET_TYPE_CUSTOM_PROPERTIES
ADD
  CONSTRAINT FK_ASSET_TYPE_CUSTOM_PROPERTIES_ASSET_CUSTOM_PROPERTIES_1 FOREIGN KEY (PROPERTY_ID, PROPERTY_GROUP_ID) REFERENCES ASSET_CUSTOM_PROPERTIES (PROPERTY_ID, PROPERTY_GROUP_ID) ON DELETE CASCADE ON UPDATE NO ACTION ENFORCED ENABLE QUERY OPTIMIZATION;

Oracle

CREATE TABLE statement:

CREATE TABLE asset_type_custom_properties(property_id varchar(256) NOT NULL,
property_group_id varchar(256) NOT NULL,
asset_type varchar(128) 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(property_id,
property_group_id,
asset_type))

ALTER TABLE statement:

ALTER TABLE asset_type_custom_properties ADD CONSTRAINT fk_asset_type_custom_properties_asset_custom_properties_1 FOREIGN KEY (property_id,
property_group_id) REFERENCES asset_custom_properties(property_id,
property_group_id) ON
DELETE
	CASCADE

asset_prop_enum_list table

The custom property of type enumeration.

This table has the following columns:

property_id - The identifier for the custom property.
group_id - The identifier for the group type that has property defined underneath.
value - The value assigned to the custom property.
description - The description of the enum property.

Postgres

CREATE TABLE statement:

CREATE TABLE IF NOT EXISTS asset_prop_enum_list (
  property_id character varying(128) COLLATE pg_catalog.default NOT NULL,
  property_group_id character varying(256) COLLATE pg_catalog.default NOT NULL,
  value character varying(128) COLLATE pg_catalog.default NOT NULL,
  description character varying(256) COLLATE pg_catalog.default,
  tech_start timestamp(6) without time zone NOT NULL DEFAULT CURRENT_TIMESTAMP,
  tech_end timestamp(6) without time zone NOT NULL DEFAULT to_timestamp('9999-12-30' :: text, 'YYYY-MM-DD' :: text),
  ts_id timestamp(6) without time zone NOT NULL DEFAULT CURRENT_TIMESTAMP,
  CONSTRAINT asset_prop_enum_list_pkey PRIMARY KEY (property_id, property_group_id, value),
  CONSTRAINT fk_asset_prop_enum_list_asset_custom_properties_2 FOREIGN KEY (property_id, property_group_id) REFERENCES asset_custom_properties (property_id, property_group_id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE CASCADE
)

ALTER TABLE statement:

ALTER TABLE IF EXISTS   asset_prop_enum_list
    OWNER to postgres;

Db2

CREATE TABLE statement:

CREATE TABLE ASSET_PROP_ENUM_LIST (
  PROPERTY_ID VARCHAR(128 OCTETS) NOT NULL,
  PROPERTY_GROUP_ID VARCHAR(256 OCTETS) NOT NULL,
  VALUE VARCHAR(128 OCTETS) NOT NULL,
  DESCRIPTION VARCHAR(256 OCTETS),
  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,
  PERIOD SYSTEM_TIME (TECH_START, TECH_END)
) IN USERSPACE1 ORGANIZE BY ROW;

ALTER TABLE statement:

ALTER TABLE
  ASSET_PROP_ENUM_LIST
ADD
  PRIMARY KEY (PROPERTY_ID, PROPERTY_GROUP_ID, VALUE) ENFORCED;

ALTER TABLE
  ASSET_PROP_ENUM_LIST
ADD
  CONSTRAINT FK_ASSET_PROP_ENUM_LIST_ASSET_CUSTOM_PROPERTIES_2 FOREIGN KEY (PROPERTY_ID, PROPERTY_GROUP_ID) REFERENCES ASSET_CUSTOM_PROPERTIES (PROPERTY_ID, PROPERTY_GROUP_ID) ON DELETE CASCADE ON UPDATE NO ACTION ENFORCED ENABLE QUERY OPTIMIZATION;

Oracle

CREATE TABLE statement:

CREATE TABLE asset_prop_enum_list(property_id varchar(128) NOT NULL,
property_group_id varchar(256) NOT NULL,
value varchar(128) NOT NULL,
description varchar(256),
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(property_id,
property_group_id,
value))

ALTER TABLE statement:

ALTER TABLE asset_prop_enum_list ADD CONSTRAINT fk_asset_prop_enum_list_asset_custom_properties_2 FOREIGN KEY (property_id,
property_group_id) REFERENCES asset_custom_properties(property_id,
property_group_id) ON
DELETE
	CASCADE

asset_custom_prop_values table

This table has the following columns:

container_id - Specifies the identifier of the catalog or project.
asset_id - The identifier for an asset to which the custom property is associated with.
property_id - The identifier for a custom property.
property_group_id - The identifier for the group that has a property defined below it.
asset_type - The type of asset for which the custom property is applicable to.
value_id - The value identifier for a given custom property.
property_text_value - The value of the text custom property.
property_num_value - The value of the number custom property.
property_date_value - The value of the date custom property.
property_value_type - The type of the value i.e. string, number, date, user, group.

Postgres

CREATE TABLE statement:

CREATE TABLE asset_custom_prop_values(
  container_id varchar(36) NOT NULL, 
  asset_id varchar(128) NOT NULL, 
  property_id varchar(256) NOT NULL, 
  property_group_id varchar(256) NOT NULL, 
  value_id varchar(256) NOT NULL, 
  asset_type varchar(256) NOT NULL, 
  property_text_value text, 
  property_num_value double precision, 
  property_date_value timestamp(6), 
  property_value_type varchar(16), 
  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(
    container_id, asset_id, property_id, 
    property_group_id, value_id, asset_type
  )
)

ALTER TABLE statement:

ALTER TABLE IF EXISTS asset_custom_prop_values
OWNER to postgres;

Db2

CREATE TABLE statement:

CREATE TABLE asset_custom_prop_values(
  container_id varchar(36) NOT NULL, 
  asset_id varchar(128) NOT NULL, 
  property_id varchar(256) NOT NULL, 
  property_group_id varchar(256) NOT NULL, 
  value_id varchar(256) NOT NULL, 
  asset_type varchar(256) NOT NULL, 
  property_text_value text, 
  property_num_value double precision, 
  property_date_value timestamp(6), 
  property_value_type varchar(16), 
  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(
    container_id, asset_id, property_id, 
    property_group_id, value_id, asset_type
  )
)

ALTER TABLE statements:

ALTER TABLE
  ASSET_CUSTOM_PROP_VALUES
ADD
  PRIMARY KEY (
    CONTAINER_ID,
    ASSET_ID,
    PROPERTY_ID,
    PROPERTY_GROUP_ID,
    VALUE_ID,
    ASSET_TYPE
  ) ENFORCED;

ALTER TABLE
  ASSET_CUSTOM_PROP_VALUES
ADD
  CONSTRAINT FK_ASSET_CUSTOM_PROP_VALUES_ASSET_TYPE_CUSTOM_PROPERTIES_2 FOREIGN KEY (
    PROPERTY_ID,
    PROPERTY_GROUP_ID,
    ASSET_TYPE
  ) REFERENCES ASSET_TYPE_CUSTOM_PROPERTIES (
    PROPERTY_ID,
    PROPERTY_GROUP_ID,
    ASSET_TYPE
  ) ON DELETE CASCADE ON UPDATE NO ACTION ENFORCED ENABLE QUERY OPTIMIZATION;

ALTER TABLE
  ASSET_CUSTOM_PROP_VALUES
ADD
  CONSTRAINT FK_ASSET_CUSTOM_PROP_VALUES_CONTAINER_ASSETS_1 FOREIGN KEY (CONTAINER_ID, ASSET_ID) REFERENCES CONTAINER_ASSETS (CONTAINER_ID, ASSET_ID) ON DELETE CASCADE ON UPDATE NO ACTION ENFORCED ENABLE QUERY OPTIMIZATION;

Oracle

CREATE TABLE statement:

CREATE TABLE asset_custom_prop_values(
  container_id varchar(36) NOT NULL, 
  asset_id varchar(128) NOT NULL, 
  property_id varchar(256) NOT NULL, 
  property_group_id varchar(256) NOT NULL, 
  value_id varchar(256) NOT NULL, 
  asset_type varchar(256) NOT NULL, 
  property_text_value text, 
  property_num_value double precision, 
  property_date_value timestamp(6), 
  property_value_type varchar(16), 
  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(
    container_id, asset_id, property_id, 
    property_group_id, value_id, asset_type
  )
)

ALTER TABLE statements:

ALTER TABLE asset_custom_prop_values ADD CONSTRAINT fk_asset_custom_prop_values_container_assets_1 FOREIGN KEY (container_id,
asset_id) REFERENCES container_assets(container_id,
asset_id) ON
DELETE
	CASCADE

ALTER TABLE asset_custom_prop_values ADD CONSTRAINT fk_asset_custom_prop_values_asset_type_custom_properties_2 FOREIGN KEY (property_id,
	property_group_id,
	asset_type) REFERENCES asset_type_custom_properties(property_id,
	property_group_id,
	asset_type) ON
	DELETE
	CASCADE

Learn more

Parent topic: Reporting tables