Reorg utility missing after an ALTER TABLE DROP COLUMN

Products

• RC Compare for DB2 for z/OS

Issue/Introduction

When altering a Table to drop a column, an ALTER TABLE DROP COLUMN is generated, which when executed, will leave the table in Advisory Reorg-Pending state (AREOR).

DSNT404I SQLCODE = 610, WARNING: A CREATE/ALTER ON OBJECT

creator.name HAS PLACED OBJECT IN ADVISORY REORG PENDING

No Reorg utility has been generated after the ALTER. The pending definition changes could result in subsequent DDL failures.

DSNT408I SQLCODE = -20385, ERROR:  THE STATEMENT CANNOT BE PROCESSED

         BECAUSE THERE ARE PENDING DEFINITION CHANGES FOR OBJECT    

         object-name OF TYPE object-type (REASON reason-code)           

Environment

Release:
Component: RCM

Cause

With ALTER TABLE DROP COLUMN support for RC/Migrator and RC/Update, an ALTER is now generated to drop the column, rather than a DROP/CREATE. This leaves the Tablespace in advisory Reorg-pending state. A REORG is required to materialize the change.

Resolution

The new OREORGT utility is delivered as part of the @DEFAULT model. To use this utility, activate it using the X (include/exclude) command on the General Model Utilities panel, in RC/Migrator Utility Model services. A Reorg will then be generated to materialize the change when requested through the analysis or profile options.

Additional Information

For further details refer to the Enhancement for ALTER TABLE DROP COLUMN Support alter-table-drop-column-support