Check the schema for objects that Sybase IQ 15.4 does not support.
Run iqunload in schema unload mode (iqunload -n) against the legacy server to generate a script (reload.sql) that contains the entire database schema. Compare the contents of this script against this table to find identify objects not supported by Sybase IQ 15.4.
Object |
Details |
Action |
|---|---|---|
Invalid database, table, or user names |
Table names cannot contain double quote characters.User names and database names cannot contain double quote characters, single quote, and semicolon characters. User names and database names cannot start or end with a space. |
Change these names. |
Join indexes |
iqunload does not run if the database to be migrated contains join indexes. |
Use Sybase Central to view the join index definitions. Copy them to a file. Drop join indexes before migrating data. After migrating data, recreate the join indexes. |
Database with BLANK PADDING OFF |
iqunload searches BLANK PADDING OFF databases for any indexes that would become invalid after migration. iqunload fails and lists indexes and constraints that must be dropped and in which order. |
Drop these indexes and constraints before the schema reloads and recreate the indexes and constraints after schema reload has been completed. |
Unenforced constraints |
iqunload fails and lists unenforced constraints that must be dropped. |
Drop unenforced constraints before proceeding with migration. |
Old 1–byte FP or old 2–byte FP indexes |
Databases created with IQ 12.4.2 or earlier may have these indexes. Because these indexes were automatically created by Sybase IQ, you cannot drop and recreate them; you must rebuild them. |
Allow iqunload to check for these and list them. Rebuild these indexes using sp_iqrebuildindex before migration.The rebuilt indexes are upgraded. |