Important information about database upgrades.
For detailed information about installing and upgrading SAP Sybase IQ, see the Installation and Configuration Guide.
Omitting these steps may cause server startup failure and an error like Sybase IQ Abort From: slib/s_iqstore.cxx:1594.
pc: 0x7f5455eee3ec s_iqstore::ReplayCheckpointLog(s_checkpoint_log*, dbServerType, s_bm*, s_bm*)+0x6c pc: 0x7f545628e274 st_database::OpenDatabase(unsigned long long, int, unsigned long long*, unsigned int*)+0x3134
The only way out of this situation is to use forced recovery using your SAP Sybase IQ 16.0 installation. The following is an example of how you can start the coordinator for forced recovery. Just replace my_db with the name of your database and 'C:\work\my_db.db' with the path and name of your database. If the symptoms you encounter are different, please call SAP Sybase Technical Support:
start_iq -n my_server -x 'tcpip{port=9999}' -gd dba -gm 1 -iqmpx_sn 1 -iqfrec my_db C:\work\my_db.db
sp_iqcheckdb 'dropleaks database'; checkpoint;
Completion returns Freelist Updated.
The asejdbc server class is deprecated. Servers of type asejdbc must be dropped prior to running iqunload. SAP Sybase IQ 12.7 databases with remote server definitions based on the asejdbc driver will not have these definitions migrated to by the iqunload tool and will not give an error at the beginning of an unload saying that you need to drop any asejdbc servers (if there are any present).
In SAP Sybase IQ 15.x, 32-bit drivers are located in the bin32 directory, instead of win32, and 64-bit drivers are now in the bin64 directory, instead of x64. Therefore, when migrating from 12.x to 15.x, you may need to update registries and applications to locate libraries. For example, win32\dbodbc11.dll is now in bin32.
If you upgrade a database from 15.x to 16.0, you cannot enable row-level versioning (using the ALTER TABLE statement), or perform LOAD, INSERT or UPDATE statements on any IQ base table containing a CHAR, VARCHAR or VARBINARY column of width greater than 255. If your upgraded database contains a table having a column with these criteria, run the sp_iqrebuildindex procedure. After you run this procedure, you can enable row-level versioning and perform DML statements on these large-column tables.