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 can no longer contain double quote characters.User names and database names can no longer contain double quote characters, single quote, and semicolon characters.User names and database names may no longer start with a space or end with a space. |
Change these names |
Join indexes |
The iqunload utility will 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 |
The iqunload utility searches BLANK PADDING OFF databases for any indexes that would become invalid after migration. The iqunload utility fails and lists indexes and constraints that must be dropped and in which order. |
Drop these indexes and constraints before schema reload and recreate the indexes and constraints after schema reload has been completed. |
Unenforced constraints |
The iqunload utility tool 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 below may have these indexes. Because these indexes were automatically created by Sybase IQ, you cannot drop and recreate them; you need to rebuild them. |
Allow iqunload to check for these and list them. Rebuild these indexes using sp_iqrebuildindex before migration. For details about rebuilding indexes, see “Configuring FP(3) indexes” in the New Features Guide. The rebuilt indexes will be upgraded. |
