When the Compare and Create Db2 Objects tasks are executed to perform the UTS conversion of the PTDB, it does not drop the obsolete objects. In the DDL script executed by the Create task (ssid0001), REORGs are performed on the obsolete Tablespaces even though they do not contain any tables and therefore no data.
PTFs LU09808 to LU09819
The REORG is still required for the now obsolete objects. This is a Db2 requirement.
The procedure to move a table from a segmented Tablespace to UTS using the new MOVE TABLE option is to issue an ALTER TABLESPACE source-non-UTS MOVE TABLE to target-UTS followed by REORG of the source Tablespace in order to materialize the MOVE TABLE operation. When the ALTER TABLESPACE statement is issued, the table is still not physically moved to UTS and that is why the source Tablespace is placed in pending REORG state.
For example, as part of the conversion of the source segmented Tablespace PTITSANA to target UTS PTUTSANA the following occurs:
ALTER TABLESPACE PTDB.PTITSANA
MOVE TABLE PTI.PTAN_STMT_1200
TO TABLESPACE PTDB.PTUTSANA
;
DSNT404I SQLCODE = 610, WARNING: A CREATE/ALTER ON OBJECT
PTDB.PTITSANA HAS PLACED OBJECT IN ADVISORY REORG PENDING
REORG TABLESPACE PTDB.PTITSANA
LOG NO
COPYDDN PTICOPY
UNLDDN PTIUNLD
DISCARDDN PTIDISC
SHRLEVEL CHANGE
Once the UTS conversion process has been completed successfully, you can then utilitize the new feature to cleanup obsolete PTDB objects, introduced with PTF LU10079 in level set 20.0.8.
This provided 3 new post-install tasks
as documented in the product Release Notes for New Features in Level Set PTF 20.0.08
For further details on the requirement for the REORG, please refer to the IBM documentation, Moving tables from multi-table table spaces to partition-by-growth table spaces.