Database Upgrades

Important information about database upgrades.

For detailed information about installing and upgrading SAP Sybase IQ, see the Installation and Configuration Guide.

CR#	Description
750748	Shut down all products that use $SYBASE before upgrade – The SYBASE variable identifies the location of the common parent directory shared by SAP Sybase applications like SAP Adaptive Server Enterprise and Sybase Open Client. Failure to shut down all products that use $SYBASE may generate `signal 11 (SIGSEGV)` errors when you upgrade SAP Sybase IQ. Workaround – Shut down all SAP Sybase applications, restart the SAP Sybase IQ server, and retry the upgrade.
702052	Drop all JOIN and all LD indexes. On multiplex, drop all logical servers named AUTO, COORDINATOR, ALL or DEFAULT – If you do not drop these objects and try to run an ALTER DATABASE UPGRADE in SAP Sybase IQ 16.0, the upgrade fails and the server returns a message that indicates that a database upgrade is not possible when these objects are in use. Recovery Information – To recover from a failed upgrade, shut down the 16.0 server, open the database with SAP Sybase IQ 15.x, and drop all LD and all JOIN indexes as well as any named logical servers before proceeding with the migration.
487858	Upgrade Invalidates Data Source Names – 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. In SAP Sybase IQ 16.0, 64-bit drivers are now in the bin64 directory, instead of x64. Therefore, when migrating from 12.x to 16.0, you may need to update registries and applications to locate libraries. For example, win32\dbodbc12.dll is now in bin32. If upgrading from 15.x to 16.0 the directory names remain the same, but the driver library has changed from dbodbc11.dll (from SAP Sybase IQ 15.0 – 15.3) or dbodbc12.dll (from SAP Sybase IQ 15.4) to dbodbc16.dll.

CR#

Description

750748

Shut down all products that use $SYBASE before upgrade – The SYBASE variable identifies the location of the common parent directory shared by SAP Sybase applications like SAP Adaptive Server Enterprise and Sybase Open Client.
Failure to shut down all products that use $SYBASE may generate signal 11 (SIGSEGV) errors when you upgrade SAP Sybase IQ.

Workaround – Shut down all SAP Sybase applications, restart the SAP Sybase IQ server, and retry the upgrade.

702052

Drop all JOIN and all LD indexes. On multiplex, drop all logical servers named AUTO, COORDINATOR, ALL or DEFAULT – If you do not drop these objects and try to run an ALTER DATABASE UPGRADE in SAP Sybase IQ 16.0, the upgrade fails and the server returns a message that indicates that a database upgrade is not possible when these objects are in use.

Recovery Information – To recover from a failed upgrade, shut down the 16.0 server, open the database with SAP Sybase IQ 15.x, and drop all LD and all JOIN indexes as well as any named logical servers before proceeding with the migration.

487858

Upgrade Invalidates Data Source Names – 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.
In SAP Sybase IQ 16.0, 64-bit drivers are now in the bin64 directory, instead of x64. Therefore, when migrating from 12.x to 16.0, you may need to update registries and applications to locate libraries. For example, win32\dbodbc12.dll is now in bin32.

If upgrading from 15.x to 16.0 the directory names remain the same, but the driver library has changed from dbodbc11.dll (from SAP Sybase IQ 15.0 – 15.3) or dbodbc12.dll (from SAP Sybase IQ 15.4) to dbodbc16.dll.