Installation and Upgrade

This section provides last-minute information about installation and upgrading that was omitted from or incorrect in your installation guide, or that needs special emphasis.

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

Before you run a new version of SAP Sybase IQ, see Restrictions for the most current requirements. This section includes installation and migration information that is new for this release or needs emphasis.

SAP Sybase IQ 16.0 Requires a License

SAP Sybase IQ 16.0 uses the SAP Sybase Software Asset Management (SySAM) licensing mechanism that lets system administrators enable and monitor their site’s use of SAP Sybase products.

SAP Sybase IQ includes separate SySAM licenses for each product edition and separate licenses for any optional features available for that edition. See Installation and Configuration Guide > Licensing Your Software.

Extract and Install Installation Packages on the Same Machine [CR #728377]

The SAP Sybase Product Download Center is an online software delivery service that provides easy access to the latest versions of your software. When you download your software, uncompress the downloaded image and run the installer on the same machine where you install SAP Sybase IQ. Do not copy an uncompressed installation archive to a secondary machine and run the install.

Avoid Using Relative Path to Launch Installer [CR #691212]

SAP Sybase IQ installation fails if you launch the installer using a relative path. During GUI installation, the installer fails to prompt for the license file information and does not install properly.

For example, when launched from the console using a command line:

Installer files directory :  /system1/users/jones/installdir
$SYBASE dir : /system1/users/jones/IQ160
cd $SYBASE
../installdir/setup.bin 

Sybase Partners with v3 UDFs Must Specify a License Key When Upgrading to v4 [CR #688135]

If you are an SAP Sybase design partner using v3 UDFs, your UDFs will not continue to work after you upgrade your libraries to v4 unless you specify the SAP Sybase-provided license key in the a_v4_extfn_license_info structure. You must implement the extfn_get_license_info method, and the method must return a valid key. See the User-Defined Functions guide for information on upgrading to the v4 API, and adding the extfn_get_license_info method.

SySAM Licensing Checkout [CR #628594]

If SAP Sybase IQ was licensed using a per-processor license type in previous releases, the license quantity was determined at startup. In this release, SAP Sybase IQ periodically checks the number of processors it can use and attempts to check-out additional licenses for any increase. SAP Sybase IQ shuts down after 30 days, if additional licenses are not made available within this period. See the SySAM Users Guide for details regarding license grace.

ALTER DATABASE UPGRADE PROCEDURE ON Required

To install new system tables, you must run ALTER DATABASE UPGRADE PROCEDURE ON on existing databases after installing SAP Sybase IQ 16.0.

For syntax, see Reference: Statements and Options.

Using Remote Server Classes for ASE [CR #615420]

Component Integration Services (CIS) connectivity from SAP Sybase IQ to Adaptive Server® Enterprise (ASE) is available using server class aseodbc. The aseodbc server class uses the Adaptive Server ODBC driver. The Adaptive Server ODBC driver requires a separate installation of SDK 15.5 ESD #8 or higher which can be downloaded from the SAP Sybase EBF download site.

Creating Dbspaces on Multiple Files

Due to the IBM implementation of reads for JFS database files, SAP Sybase IQ performance improves if you create dbspaces on each disk, instead of creating one large file. Smaller files allow SAP Sybase IQ to handle disk I/O operations much more efficiently, especially when combined with disk striping and possibly multiple controllers.

The current recommendation is that you create three files per underlying disk drive.

When setting up raw partitions, the system administrator specifies the sector size, which defines the minimum usable chunk of disk (and sets the minimum block size). When you use raw partitions, the integer you specify as a block size must be a multiple of the sector size.

Related reference
Restrictions