Once you load a database, Adaptive Server automatically identifies the endian type on the dump file and performs all necessary conversions while the load database and online database commands are executing.
After Adaptive Server converts the index rows, the order of index rows may be incorrect. Adaptive Server marks the following indexes on user tables as suspect indexes during execution of online database:
Nonclustered index on APL table
Clustered index on DOL table
Nonclustered index on DOL table
During cross-platform dump and load operations, suspect
partitions are handled as follows:
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.
