With table partitioning, does each partition gets its own table ID in the catalog? What happens to the table ID during a partition detach or attach?

There is only one row in syscat.tables for a table (with or without table partitions). There is another catalog table which keeps track of the partitions.

I see SYSCAT.DATAPARTITIONS. Two columns of interest

DATAPARTITIONID - Identifier for the data partition.
PARTITIONOBJECTID - Identifier for the data partition within the table space.


What is the difference between them? Which one becomes the table ID in SYSCAT.TABLES when a partition gets detached and becomes a stand-alone table?

When you detach a partition into a new table, I believe that DB2 just assigns the next available table id, just like whenever any table is created. Why don't you try it?

I don't recall that there is any relation in the catalog between a table created via detach partition, and the original table or information in SYSCAT.DATAPARTITIONS. The way the relationship is normally associated is by careful naming of the table created via detach partition.

Everything works fine except db2pd