ADD_MATERIALIZE_OBJECT¶
Add new Object Definition for Materialization.
Table: REDADM.RED_MATERIALIZE_OBJECTS (Internal table used by view REDADM.RED_MATERIALIZE to materialize other views)
Parameter Name |
Properties |
Default Value |
Parameter Description |
|---|---|---|---|
p_mat_group |
(PK)(NN) |
Name of the materialization group as defined in table REDADM.RED_MATERIALIZE_GROUPS |
|
p_mat_order |
(PK)(NN) |
Order of materialization execution |
|
p_mat_base_schema |
(NN) |
Schema name of the object that should be materialized |
|
p_mat_base_name |
(NN) |
Name of the object that should be materialized |
|
p_mat_target_schema |
(NN) |
Schema name of the target object |
|
p_mat_target_name |
(NN) |
Object name of the target object |
|
p_del_where_clause |
Specifies the condition for the DELETE statement executed before data materialization. A value of ‘false’ ensures no data is removed. |
||
p_use_tmp_space |
(NN) |
FALSE |
Enables the use of a temporary table for materialization to reduce transaction conflicts. |
p_bdate_filter_column |
Identifies the column name used to filter the materialization process by the application’s BDATE. If set, only data matching the specified action date is processed; a NULL value indicates that no date restriction is applied. |
||
p_use_date_range |
(NN) |
FALSE |
Specifies whether a range is applied to the BDATE_FILTER_COLUMN (TRUE: “>=”, FALSE: “=”). |
Example
EXECUTE SCRIPT api_redadm.add_materialize_object
( 'XXXXXXXXXXXX' -- p_mat_group
, 999999999999 -- p_mat_order
, 'XXXXXXXXXXXX' -- p_mat_base_schema
, 'XXXXXXXXXXXX' -- p_mat_base_name
, 'XXXXXXXXXXXX' -- p_mat_target_schema
, 'XXXXXXXXXXXX' -- p_mat_target_name
, 'XXXXXXXXXXXX' -- p_del_where_clause
, FALSE -- p_use_tmp_space
, 'XXXXXXXXXXXX' -- p_bdate_filter_column
, FALSE -- p_use_date_range
);