ADMIN_MOVE_TABLES needs to support INDEXES on EXPRESSION

ADMIN_MOVE_TABLE (AMT) procedure fails in SWAP phase, if the table to be moved has an expression based index defined.

This issue has been lifted partially, as the RENAME of the table is now supported with INDEX on EXPRESSION (IoE).

But in our case, the index is based on a generated column, and AMT has to alter this generated column to (re-)start at the number which the source table currently had reached.
Thus an ALTER TABLE is required, which seems not to be permitted with IoE defined.

Here’s a short reproduction scenario:

CREATE TABLE "TAB1" ( "ID" BIGINT NOT NULL )

DB20000I The SQL command completed successfully.

CREATE INDEX "IDX1" ON "TAB1" (MOD(ID, 10) ASC)

DB20000I The SQL command completed successfully.

ALTER TABLE "TAB1" ALTER COLUMN "ID" SET GENERATED BY DEFAULT AS IDENTITY ( START WITH 1 INCREMENT BY 10 )

DB21034E The command was processed as an SQL statement because it was not a

valid Command Line Processor command. During SQL processing it returned:

SQL0478N The statement failed because one or more dependencies exist on the

target object. Target object type: "COLUMN". Name of an object that is

dependent on the target object: "IDX1". Type of object that is dependent on

the target object: "INDEX". SQLSTATE=42893

Business need:

AMT runs online having less impact to the application processing compared to a regular reorg.
But as soon as an IoE is defined, the index has to be dropped before and recreated after the AMT, which means the index is NOT available to the application for a maybe very long period.
We have to move (range partitioned) tables having more than a billion of rows, where AMT runs for more than 24 hours.
Thus we cannot afford to have that index dropped for such a long time.