Upgrading from Sybase IQ 12.6/12.7 database is very different than upgrading from a Sybase IQ 15 database. This upgrade involves an unload/reload of the catalog. Follow this task flow to migrate a 12.6/12.7 database to Sybase IQ 15.4.
Read the Sybase IQ release bulletin for the latest information. See the special installation instructions section in the release bulletin for any installation instructions not included in this document.
Upgrade to Sybase IQ 12.7 ESD #5. All migration paths assume that you are migrating from Sybase IQ 12.7 ESD #5 as a minimum.
The SORTKEY function uses the International Components for Unicode (ICU) library, instead of the Sybase Unicode Infrastructure Library (Unilib®). Sort-key values created using a version earlier than 15.0 do not contain the same values created using version 15.0 and later. Regenerate any sort-key values in your database that were generated using a version of Sybase IQ earlier than 15.
Sybase IQ 15 no longer supports creating custom collations. If you are rebuilding a database with a custom collation, the collation is preserved if you rebuild in a single step. If you unload the database, then load the schema and data into a database that you create, then you must use one of the supplied collations.
Back up your current installation and save copies of any changes you made to default login and post-login scripts. Create your backups on removable media, like tape, DVD, or CD. Make sure the backups are readable before you proceed.
To effectively plan your migration, review and understand the database migration utilities. Sybase IQ 15 includes an iqunload utility that you can use to re-create the schema for your database or simply migrate your database from 12.x to 15. An iqlsunload utility is available for 12.7 multiplex users who need to move local stores.
Resolve potential migration errors before you migrate. Sybase IQ 15 no longer supports some 12.x features and objects. Update these objects before you begin for the migration utilities to function correctly.
Follow the work flows for the migration you want to perform. There are separate migration paths for simplex and multiplex databases.