[CR #400988] If a server crashes following an alter table unpartition operation on very large tables, the server recovery after restart may leave the table in an inconsistent or corrupted state. dbcc check table and other commands affecting a table’s pages may result in incorrect page errors. In some cases, the recovery process encounters timestamp mismatches on pages allocated to the table being unpartitioned. This form of corruption may occur when you issue a shutdown no wait command, and can affect very large tables with multiple OAM pages in the OAM chain for each partition.
Workaround: Run checkpoint <database> immediately following an unpartition operation. You can also issue a shutdown command without the no wait clause to avoid this form of corruption.
