Determining Migration Switches

In some cases, you may need to set some switches to migrate your database.

The -au parameter starts these two servers:

To minimize startup times, first verify that your server starts cleanly in IQ 12.6 or 12.7.

Default iqunlspt Arguments

By default, iqunlspt starts on your Sybase IQ 12.6/12.7 database with these command line arguments:
iqunlspt -iqnotemp 100 -iqro 1 -c 48MB -gc 20 -gd
all -gk all -gl all -gm 1 -gu all -ti 4400 -x shmem 
iqunlspt also includes the -n parameter followed by a special randomly generated server name.

These cache settings suffice for most migration cases, although you may need to increase these values. At migration, data queries execute against the system catalogs, not IQ data, so the iqunlspt engine needs lower cache levels than complex queries or multiple concurrent users. The time required to start your existing Sybase IQ 12.6 or 12.7 database is the same amount of time required to start the iqunlspt process. This time is included in the startup time for iqunload.

Default iqsrv15 Arguments

iqsrv15 starts with these command line arguments:
iqsrv15 -gp 4096 -c 40p -gc 20 -gd all -gk all -gl all
-gm 1 -gu all -qi -qs -ti 4400 
iqsrv15 also includes the -n parameter followed by a special randomly generated server name. The -c 40p setting provides a larger cache for the catalog store, allowing the Sybase IQ15 engine to execute many schema DDL statements. Both server start commands use the default values for -iqmc and -iqtc. If your Sybase IQ 12.6/12.7 server requires larger values for startup performance, consider adding these to the START= parameter (see below).

iqunload Results

The iqunload utility generates script and output files in the $IQTMP15 directory and removes them on completion.

By default, Sybase IQ allocates the lesser of 256MB or 40% of physical memory for the Catalog Store cache size upper limit. Insufficient cache causes iqunload errors like Tried to allocate 4167598080 bytes, failed. You can control the upper and lower limits for the Catalog Store cache size by setting the –ch and -cl startup switches through the StartLine [START] connection parameter. See the Utility Guide.

Users with wide tables (large numbers of column/null values) should not decrease the Catalog Store page size for database migration.

If the database being migrated contains invalid views, Sybase IQ completes migration but issues user warnings. This may occur, for example, if tables involved in a view are dropped.

If you set the IQTMP15 environment variable, you must set it to a valid directory name.

If the database being migrated is encrypted, then you must specify the DBKEY connection parameter to provide the encryption key for the database. The migrated database uses the same encryption key.

The iqunload utility automatically starts the old version of the server (12.6 or 12.7) to upgrade the catalog .db file, and shuts down the old server after the unload completes. The utility uses default values for the various cache sizes (catalog cache, main cache, temp cache). If the database being migrated is normally run with much higher cache values, specify these values as part of the START connection parameter to ensure that the server has adequate catalog cache, main cache, temp cache for the database being unloaded.

The current defaults are 48MB for the catalog cache size, 32MB for the main cache size and 24MB for the temp cache size.

Related concepts
Logging and Correcting Errors
Working With Large Schemas
Working with Extremely Large Schemas