IBM Db2 Administration Tool for z/OS 13.1 and its extension, IBM Db2 Object Comparison Tool for z/OS 13.1, support the following features of Db2 13 function level (FL) 507:
Support for online PBR-to-PBG conversions
Db2 13 FL 507 introduced the much-anticipated ability to convert a table space from partition-by-range (PBR) to partition-by-growth (PBG) as an online change. Combine this conversion with an online PBG-to-PBR conversion (introduced in Db2 13 FL 500) and you can now make partitioning changes to your table space without requiring an application outage: Simply alter your PBR table space to PBG, then alter it back to PBR with the partitioning changes that you want, and materialize both of these changes with a single online REORG operation.
Now, add Db2 Admin Tool to this process. Besides supporting these online changes, Db2 Admin Tool performs some additional work for you. When you use Db2 Admin Tool to change the partitioning scheme or drop a partition, Db2 Admin Tool retains partition-level attributes from the original PBR table space and restores all partitioned and data-partitioned indexes and index attributes. Without Db2 Admin Tool, you need to manually alter the attributes and re-create the indexes.
Specifically, Db2 Admin Tool offers support for the following tasks:
- You can do a simple online PBR-to-PBG conversion. To do so, use the existing AL line command or ALT line command; Db2 Admin Tool implements the change as an online conversion rather than dropping and re-creating the table.
- You can also repartition or drop a partition from a table in a PBR table space as an online change. To do so, use the ALT line command on a table or table space. Db2 Admin Tool implements this change online by “stacking” a PBR-to-PBG conversion with a subsequent PBG-to-PBR conversion that includes your partitioning changes and running REORG. Db2 Admin Tool retains any partition-level attributes that were defined in the original PBR table space and restores all partitioned and data-partitioned indexes and index attributes.
- If you use the GEN function to generate SQL for an object and the Apply Pending Changes option is set to YES, any pending table space conversions are accounted for in the generated SQL statements:
- For PBR-to-PBG pending changes: The generated CREATE TABLESPACE and CREATE TABLE statements, when executed, result in a PBG table space as specified by the pending ALTER TABLE statement's ALTER PARTITIONING TO PARTITION BY GROWTH clause.
- For stacked pending changes (PBR-to-PBG followed by PBG-to-PBR): The generated CREATE TABLESPACE and CREATE TABLE statements, when executed, result in a PBR table space as specified by the second pending ALTER TABLE statement's ALTER PARTITIONING TO PARTITION BY RANGE clause. Partition-level attributes are retained.
- CREATE INDEX statements are generated that, when executed, result in nonpartitioned indexes, even if they were originally partitioned indexes. This action ensures that the ALTER PARTITIONING TO PARTITION BY GROWTH clause's expected behavior is included in the generated CREATE statements.
Additionally, Db2 Object Comparison Tool now generates ALTER operations when converting a table space to PBG and when dropping a partition from or repartitioning a table in a PBR table space. (Previously these operations were done by dropping and re-creating the objects.) When dropping a partition from or repartitioning a table, Db2 Object Compare also retains any partition-level attributes and partitioned indexes and index attributes.
For more information about this PBR-to-PBG enhancement in Db2, see the blog PBR-to-PBG conversions for tables and more online PBR UTS alterations in FL 507.
For instructions on how to make these changes in Db2 Admin Tool, see:
Support for primary and secondary space allocations greater than 64 GB
To reduce the need to frequently allocate extents, Db2 13 FL 507 introduced support for increased space allocations for table spaces. You can now specify primary space allocations (PRIQTY) up to 1TB and secondary space allocations (SECQTY) up to 200 GB.
Db2 Admin Tool supports these larger values; you can now enter or display PRIQTY up to 1073741824 and SECQTY up to 209715200.
Additionally, the GEN function and Db2 Object Comparison Tool can also handle the larger values; if the target function level is less than FL 507, the tool adjusts the PRIQTY and SECQTY values to match the previous limits.
Required program temporary fixes (PTFs)
To use Db2 Admin Tool and Db2 Object Comparison Tool with Db2 13 FL 507, apply the following fixes:
For FL 507 toleration:
UO02958 (APAR PH66002)
UO02957 (APAR PH66003)
For FL 507 support for the increased space allocation enhancement:
UO03232 (APAR PH66531)
For FL 507 support for the PBR-to-PBG enhancement:
UO04303 (APAR PH67403)
UO04304 (APAR PH67457)
If your system is missing any of these FL 507 PTFs, Db2 Admin Tool displays a confirmation panel when you open the tool. For example:
This panel warns you about the level of FL 507 support:
- If you do not have the FL 507 toleration PTFs applied, this panel warns that function level 507 is not tolerated, and results might be unpredictable.
- If you do not have all of the FL 507 support fixes applied, this panel warns that enhancements in FL 507 are not supported. If you have applied at least one fix, but not all fixes, this panel means that not all FL 507 enhancements are supported.
For more information about this confirmation panel and continuous delivery support in Db2 Admin Tool, see Support for Db2 continuous delivery.