Change rules used with object attributes

For more information about using change rules or change flag keywords in a comparison, refer to the Using section.

Change rules and change flag keywords for Db2 objects

^{1 You can specify a change rule for a LOB table space by using the table space (TS) object.}

^{2 You can specify a change rule for a LOB base table or an auxiliary table by using the table (TB) object.} 

^{3 You can specify a change rule for an auxiliary index by using the index (IX) object.}

^{4 The product ignores this attribute for a change rule for an auxiliary table.} 

^{5 The product ignores this attribute for a change rule for a LOB table space} 

^{6 The product treats this attribute as a comment unless the AUTHSW keyword or installation option is set to B.} 

^{7 The CREATOR and OWNER keywords correspond to the CREATOR column in the Db2 catalog tables for the objects.} 

^{8 The product applies this change rule only to table spaces with a DSSIZE greater than 0.}

^{9 You cannot specify a change rule for a FIELDPROC attribute on a BIGINT, BINARY, or VARBINARY column in a table.}

^{10 ( Db2 Version 10 and later ) The product applies this change rule only to an inline LOB column; the column must be in a table that is in a partition-by-growth or range-partitioned table space.}

^{11 If you set the table space LOCKSIZE attribute to TABLESPACE or TABLE, you must set LOCKMAX to 0.}

^{12 The product applies this change rule only to existing partition-by-growth table spaces.}

^{13 You can include or exclude volumes from storage groups, VCAT-defined table spaces, or VCAT-defined indexes.}

^{14 This object is available if PTF BQU1880 is applied.} 

^{15 The product applies this change rule to Global Temporary Tables only.} 

^{16 The product applies this change rule only to partition-by-range table spaces that use relative page numbering.} 

The following table shows the types of change rules or change flag keywords that you can use to compare, import, or migrate attributes of the application objects. The All column indicates that a rule can be used for an attribute for all objects that are listed for the attribute.

Change rules and change flag keywords for application objects

^{1 The Import and Compare components ignore this change rule.}

^{2 To indicate the active version of a native SQL stored procedure, specify ALTER ACTIVATE VERSION in the DDL or CDL.}

^{3 The product does not apply change rules for COLLECTION to trigger packages.}

^{4 The product applies this change rule to native stored procedures and external stored procedures that are written in Java. Valid values for the current attribute are *, ALLOW, DISALLOW, or DISABLE. Valid values for the new attribute are ALLOW, DISALLOW, or DISABLE.}

^{5 The NOLOCKSIZE keyword suppresses the LOCKMAX and the LOCKSIZE attributes.}

^{6 The OWNER keyword corresponds to the OWNER column in the Db2 catalog tables for the objects.}

^{7 The QUALIFIER keyword corresponds to the QUALIFIER column in the Db2 catalog tables for the objects.}

^{8 The Import and Compare components will not change the CREATE PROCEDURE statement to an ALTER PROCEDURE statement.}

^{9 The Import and Compare components will not convert an external SQL stored procedure to a native SQL stored procedure.}

^{10 The product applies this change rule only to native SQL stored procedures.}

^{11 Valid values for the current attribute are *, n*, or nnn. Valid values for the new attribute are *nnn or nnn.}

^{12 Valid values for the new attribute are alphanumeric names or the <DEFLT> keyword. You can no longer specify <BLANK> or NO WLM for the new attribute value.}

^{13 Changes to SCHEMA and NAME will be applied to user-defined functions included in the text of MQTs, views, and triggers.}

^{14 All (or **) does not apply to user-defined function names in MQTs, triggers, and views.}

^{15 This object is available if  PTF BQU0665 is applied.}

^{16 This object is available if (SPE2005) is applied.}