ADMIN_MOVE_TABLE FORCE NOT PARTITIONED INDEX CREATION

Francesco Proietti

ADMIN_MOVE_TABLE FORCE NOT PARTITIONED INDEX CREATION

Hi,

I have a question regarding the use of the ADMIN_MOVE_TABLE procedure on DB2 11.1. In particular, I have the need to move a table from a TBSP to another and modify the table structure from standard to range partitioned on a date field. So, the source table has got two index defined and the PK, but I would like to have those indexes defined as NOT PARTITIONED on the target table. Instead, I realised that they are created as PARTITIONED on the target table.
The KNOWLEDGE CENTER says:

"When moving from a source partitioned table to a target non-partitioned table, or vice-versa, the partitioned attribute is decided by the default behavior of the database."


I wonder if there is a way to modify this "default" behavior or if there is no hope :)

Thank you in advance for your support.