Partitions are marked suspect because of a sort order or character set change on a range-partitioned table, or because of a cross-platform dump and load with a hash-partitioned table.
If the table is marked with suspect partitions:
All updates and cursor activities are suspended on this table.
No alter table commands, except partition by, are allowed. create index and drop index are not allowed on a table with suspect partitions.
The select command is allowed on tables containing suspect partitions. However, the optimizer treats such tables as round-robin partitioned tables, to avoid using the possibly corrupt partition condition.
If the partition condition needs fixing after a sort-order change, you can use alter table with the partition by option to repartition a table that has suspect partitions.
If the partition condition does not need fixing, you can use the reorg rebuild table command to rebuild the table, redistributing only the data rows among the partitions.
If the indexes as well as the partitions on a table are marked suspect, use partition by or reorg rebuild to fix both the suspect index and suspect partitions.
During the first online database command, after you execute load database across two platforms with different endian types, the hash partition is marked suspect.
Any global clustered index on a round-robin partition, which has an internally generated partition condition with a unichar or varchar partition key, is marked suspect.
After the database is online, use sp_post_xpload to fix the suspect partitions and indexes.