GA enhancements in Db2 Object Comparison Tool 13.1

The following enhancements are available as of the General Availability (GA) date of Object Comparison Tool 13.1.

Online conversion of partition-by-growth (PBG) table spaces to partition-by-range (PBR) table spaces

Db2® 13 introduces the capability to convert a table with growth-based partitions (in a PBG table space) to use range-based partitions (in a PBR table space) with an online change that has minimal impact to your applications. This online conversion is accomplished by using an ALTER TABLE statement with the new ALTER PARTITIONING TO PARTITION BY RANGE clause.

You can use Db2 Object Comparison Tool 13.1 to perform this online conversion. When APPLCOMPAT is set to V13R1M500 or higher and a target PBG table space needs to be changed to a PBR table space, Object Comparison Tool generates an ALTER statement when valid (according to any Db2 restrictions) and any necessary REORG statements to perform this conversion and thus minimize outages.

Support for package owner type

To increase flexibility for package ownership, Db2 13 allows you to specify whether the owner of a package is a role or authorization ID with the following new syntax:

  • For the Db2 commands BIND and REBIND, Db2 13 introduces the new keyword OWNERTYPE for the OWNER bind option.
  • For the SQL CREATE and ALTER statements for compiled SQL scalar functions and native SQL procedures, Db2 13 introduces the new keywords AS ROLE and AS OWNER in the PACKAGE OWNER clause.

Object Comparison Tool 13.1 can compare the owner and owner type for these procedures and functions and generate changes as needed. For example, if the owner and owner type differ between the source object and the target object, the compare report includes a message similar to the following message:


Options
  (A)Field PACKAGE OWNER changed from 'RL174061 AS ROLE' to 'TS5465 AS USER'
Native SQL Procedure options will be altered

Support for long column names

Db2 13 introduced support for long column names (up to 128 bytes) when the TABLE_COL_NAME_EXPANSION subsystem parameter setting is ON. Previously, the limit was 30 bytes. Object Comparison Tool 13.1 can manage these longer column names. For example, you can compare objects with long column names and generate changes as needed.