Running iqunload in schema unload mode (iqunload -n) against an existing 12.x server generates a reload.sql script that contains the entire schema for a 12.x database. You can compare the contents of this script against the following table to identify unsupported objects and metadata.
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 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 |
qunload 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. See “Configuring FP(3) indexes” in the New Features Guide. The rebuilt indexes are upgraded. |
