If you use CLONE TABLEs (Db2 11 and Db2 12), please make sure to have a look at these (currently open) APARs:
PH05350 - ABEND04E RC00C90101 IN DSNGEPUF ERQUAL500A DBD CORRUPTION
PH06189 - RESIDUAL SYSOBDS RECORDS CAUSING DBD CORRUPTION
PH06476 - DB2 CRASHED FOLLOWING DISPLAY DATABASE COMMAND DUE TO CORRUPTED DBD
PH07272 - MODIFY RECOVERY UTILITY - DELETE RESIDUAL SYSIBM.SYSOBDS ROWS
The first one is directly linked to CLONE TABLEs and can result in corrupted DBD.
Then a REPAIR DBD REBUILD was done and this one picks up an incorrect SYSOBDS entry and again corrupted DBD (for the CLONE OBD, but it could happen for other objects).
If you access such a corrupted DBD, Db2 abends.
MODIFY utility does not remove such incorrect SYSOBDS entry.
The final three APARs are not limited to CLONE TABLE, but that problem was/is the main trigger.------------------------------
Karen Wilkins
Client Technical Professional
IBM UK Ltd
Bristol
------------------------------