Installation and Configuration Guide

Sybase IQ
15.1
[ WINDOWS ]
DOCUMENT ID: DC30056-01-1510-01

LAST REVISED: July 2009

Copyright © 2009 by Sybase, Inc. All rights reserved.

This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions or technical notes.
Information in this document is subject to change without notice. The software described herein is furnished under a license agreement,
and it may be used or copied only in accordance with the terms of that agreement.

To order additional documents, U.S. and Canadian customers should call Customer Fulfillment at (800) 685-8225, fax (617) 229-9845.

Customers in other countries with a U.S. license agreement may contact Customer Fulfillment via the above fax number. All other
international customers should contact their Sybase subsidiary or local distributor. Upgrades are provided only at regularly scheduled
software release dates. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic,
mechanical, manual, optical, or otherwise, without the prior written permission of Sybase, Inc.

Sybase trademarks can be viewed at the Sybase trademarks page at http://www.sybase.com/detail?id=1011207. Sybase and the
marks listed are trademarks of Sybase, Inc. ® indicates registration in the United States of America.
Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Unicode and the Unicode Logo are registered trademarks of Unicode, Inc.

All other company and product names mentioned may be trademarks of the respective companies with which they are associated.

Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-7013
for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies.

Sybase, Inc., One Sybase Drive, Dublin, CA 94568.

Contents

About This Book ........................................................................................................................... ix

CHAPTER 1 Preparing for Installation................................................................ 1

Overview .......................................................................................... 2
Product editions......................................................................... 2
Platforms and operating systems .............................................. 2
Network Client supported platforms .......................................... 3
Updated software components.................................................. 3
Licensing requirements ............................................................. 3
Installation media ...................................................................... 3
Planning your installation ................................................................. 4
Installing Sybase IQ for the first time......................................... 4
Upgrading from a previous version ........................................... 5
Changing hardware platforms ................................................... 5
Disk space and memory requirements............................................. 6
Pre-installation tasks ........................................................................ 7
Check for operating system patches ......................................... 7
Check the available disk space and memory ............................ 8
Increase the swap space........................................................... 8
Enable 4GT ............................................................................... 8
Windows support issues............................................................ 9
Verify network functionality...................................................... 10
Installing your software .................................................................. 10

CHAPTER 2 Licensing your software............................................................... 13

Overview ........................................................................................ 14
Sybase Product Download Center ......................................... 14
Available licenses .................................................................... 14
Before you generate your license .................................................. 17
Read the SySAM documentation ............................................ 17
Decide on the license model you want to use ......................... 17
Get your host ID ...................................................................... 18
Determine the host name ........................................................ 18

Installation and Configuration Guide iii

Contents

Choose a port number............................................................. 18

Generate your SySAM license ....................................................... 19
Unserved licenses ................................................................... 19
Served licenses ....................................................................... 20
Installing a new license server ....................................................... 21

CHAPTER 3 Installing Sybase IQ Server .......................................................... 25

Overview ........................................................................................ 26
Before you install Sybase IQ server ........................................ 26
Server components ................................................................. 27
Plug–in compatibility................................................................ 27
What a server installation does ............................................... 28
Installing Server components ......................................................... 29
Post-installation tasks .................................................................... 31
Uninstalling Sybase IQ server........................................................ 32

CHAPTER 4 Testing installed products ............................................................ 33

Demo database.............................................................................. 34
Running interactive SQL queries ................................................... 35

CHAPTER 5 Installing Sybase IQ Client Components..................................... 39

Overview ........................................................................................ 40
Before you install Sybase IQ client tools ................................. 40
Client components................................................................... 40
What a client installation does................................................. 41
Installing client components on Windows ...................................... 41
Uninstalling Sybase IQ client ......................................................... 42

CHAPTER 6 Migrating Data................................................................................ 43

Overview ........................................................................................ 44
Upgrading from a previous version ......................................... 44
Converting to a new hardware platform .................................. 45
Migration utilities ............................................................................ 47
Sybase IQ 15.1 Unload utility (iqunload) ................................. 47
Sybase 12.7 Local Store Unload utility (iqlsunload) ................ 58
Avoiding potential migration problems ........................................... 62
Addressing unsupported objects ............................................. 62
Correcting invalid SQL syntax ................................................. 63
Migrating simplex databases.......................................................... 66
Task summary......................................................................... 66
Verify your databases.............................................................. 67
Shutdown your 12.x server...................................................... 67

iv Sybase IQ
 Contents

Migrate your simplex database ............................................... 68

Start the 15.1 migrated database ............................................ 69
Verify the migrated databases................................................. 69
Migrating multiplex databases........................................................ 70
Task summary......................................................................... 70
Synchronize and shutdown multiplex query nodes ................. 71
Migrate your local stores ......................................................... 73
Verify the 12.x databases before migration............................. 79
Start the multiplex write server in single node mode ............... 80
Shutdown your 12.x server...................................................... 80
Use iqunload to migrate your database................................... 80
Start the 15.1 migrated database ............................................ 83
Verify the migrated databases................................................. 83
Start and verify the coordinator ............................................... 84
Manually synchronize the secondary nodes ........................... 84
Start the secondary nodes ...................................................... 86
Set the failover node ............................................................... 86
Post-migration tasks....................................................................... 87
Recreating indexes for EUC_TAIWAN data ............................ 87
Updating configuration files ..................................................... 87
Preserving database options ................................................... 87
Backing up your databases after migration ............................. 87

CHAPTER 7 Configuring Sybase IQ ................................................................. 91

Using configuration files ................................................................. 92
Installing Sybase IQ as a Service .................................................. 93
Configuring backup devices ........................................................... 94
Configuring client connectivity........................................................ 95
Connecting using JDBC .......................................................... 95
Connecting using ODBC ......................................................... 96
Connecting using OLE DB .................................................... 100
Connecting using Open Client............................................... 101
Running client and server on the same system .................... 101
Network issues for IQ servers ............................................... 101

AP PE ND IX A Silent Installations ...................................................................... 105

Overview ...................................................................................... 106
Installing IQ silently ...................................................................... 106
Task summary....................................................................... 106
Editing the installation parameters ........................................ 107
Running a silent install .......................................................... 107
Completing the installation .................................................... 109
Uninstalling IQ silently.................................................................. 109

Installation and Configuration Guide v

Contents

Editing the uninstall parameters ............................................ 110

Uninstalling IQ components .................................................. 110
Sample configuration files ............................................................ 111
SilentInstall.txt ....................................................................... 111
SilentUninstall.txt................................................................... 116

AP PE ND IX B Troubleshooting SySAM ............................................................. 119

Where to look for SySAM-related errors ...................................... 120
SySAM grace mode ..................................................................... 120
SySAM grace period .................................................................... 120
Enabling and changing e-mail notifications.................................. 121
Calling Sybase technical support for SySAM-related issues ....... 121
License checkout and verification ................................................ 122
Diagnosing SySAM issues ........................................................... 123
Cannot find license type during the Sybase IQ installation ... 124
The installation program produces a warning about not finding a
suitable license ............................................................... 124
The license server executables and scripts are not installed 124
The license server does not start .......................................... 125
The license server does not recognize the license files ........ 125
Sybase IQ does not start, and generates a license check-out
failure error ..................................................................... 126
Sybase IQ cannot check out a license and starts with graced
license instead................................................................ 126
Sybase IQ shows graced licenses even after the issue has been
fixed ................................................................................ 128
Sybase IQ cannot find license for an optional feature, even though
the license exists ............................................................ 128
Sybase IQ does not start with the expected edition or license type
129
Sybase IQ does not pick the correct license ......................... 129

Index ........................................................................................................................................... 131

vi Sybase IQ
Installation and Configuration Guide vii
viii Sybase IQ
About This Book

Subject The Sybase® IQ 15.1 Installation and Configuration Guide for Windows
provides information you need to install Sybase IQ. This book includes:
• Installation procedures for Sybase IQ Server and Client components.
• Instructions on how to install Sybase IQ with SySAM 2.
• Migration procedures for legacy databases.
Audience This book is intended for Sybase System Administrators and other
qualified personnel who are familiar with their system’s environment,
networks, disk resources, and media devices.
Related documents The Sybase IQ 15.1 documentation set includes:
• Release Bulletin provides information about last-minute changes to
the product and documentation.
• Advanced Security in Sybase IQ covers the use of user encrypted
columns within the Sybase IQ data repository. You need a separate
license to install this product option.
• Sybase IQ Error Messages lists Sybase IQ error messages referenced
by Sybase error code, SQLCode, and SQLState, and SQL
preprocessor errors and warnings.
• IMSL Numerical Library User’s Guide: Volume 2 of 2 C Stat Library
contains a concise description of the IMSL C Stat Library time series
C functions. This book is only available to RAP – The Trading
Edition™ Enterprise users.
• Introduction to Sybase IQ includes hands-on exercises for those
unfamiliar with Sybase IQ or with the Sybase Central™ database
management tool.
• Large Objects Management explains storage and retrieval of Binary
Large Objects (BLOBs) and Character Large Objects (CLOBs)
within the Sybase IQ data repository. You need a separate license to
install this product option.
• New Features in Sybase IQ 15.0 documents new features and
behavior changes for version 15.0.

Installation and Configuration Guide ix

 • New Features in Sybase IQ 15.1 summarizes new features and behavior
changes for the current version.
• Performance and Tuning Guide describes query optimization, design, and
tuning issues for very large databases.
• Quick Start lists steps to build and query the demo database provided with
Sybase IQ for validating the Sybase IQ software installation. Includes
information on converting the demo database to multiplex.
• Reference Manual – Includes two reference guides to Sybase IQ:
• Reference: Building Blocks, Tables, and Procedures describes SQL,
stored procedures, data types, and system tables that Sybase IQ
supports.
• Reference: Statements and Options describes the SQL statements and
options that Sybase IQ supports.
• System Administration Guide – Includes two volumes:
• System Administration Guide: Volume 1 describes startup,
connections, database creation, population and indexing, versioning,
collations, system backup and recovery, troubleshooting, and
database repair.
• System Administration Guide: Volume 2 describes writing and
running procedures and batches, programming with OLAP, accessing
remote data, setting up IQ as an Open Server, scheduling and event
handling, programming with XML, and debugging.
• User-Defined Functions Guide provides information about the user-
defined functions, their parameters, and possible usage scenarios.
• Using Sybase IQ Multiplex tells how to use multiplex capability, designed
to manage large query loads across multiple nodes.
• Utility Guide provides Sybase IQ utility program reference material, such
as available syntax, parameters, and options.

Sybase IQ and SQL Anywhere

Because Sybase IQ is an extension of SQL Anywhere Server, a component of
the SQL Anywhere® package, Sybase IQ supports many of the same features
as SQL Anywhere Server. The IQ documentation set refers you to SQL
Anywhere documentation, where appropriate.

x Sybase IQ
 About This Book

Documentation for SQL Anywhere includes:

• SQL Anywhere Server – Database Administration describes how to run,
manage, and configure SQL Anywhere databases. It describes database
connections, the database server, database files, backup procedures,
security, high availability, and replication with Replication Server®, as
well as administration utilities and options.
• SQL Anywhere Server – Programming describes how to build and deploy
database applications using the C, C++, Java, PHP, Perl, Python, and .NET
programming languages such as Visual Basic and Visual C#. This book
also describes a variety of programming interfaces such as ADO.NET and
ODBC.
• SQL Anywhere Server – SQL Reference provides reference information
for system procedures, and the catalog (system tables and views). It also
provides an explanation of the SQL Anywhere implementation of the SQL
language (search conditions, syntax, data types, and functions).
• SQL Anywhere Server – SQL Usage describes how to design and create
databases; how to import, export, and modify data; how to retrieve data;
and how to build stored procedures and triggers.
You can also refer to the SQL Anywhere documentation in the SQL Anywhere
11.0.1 collection at Product Manuals at http://www.sybase.com/support/manuals/
and in DocCommentXchange at http://dcx.sybase.com/dcx_home.php.
Documentation for Sybase Software Asset Management (SySAM) includes:
• Sybase Software Asset Management (SySAM) 2 introduces asset
management concepts and provides instructions for establishing and
administering SySAM 2 licenses.
• SySAM 2 Quick Start Guide tells you how to get your SySAM-enabled
Sybase product up and running.
• FLEXnet Licensing End User Guide explains FLEXnet Licensing for
administrators and end users and describes how to use the tools that are
part of the standard FLEXnet Licensing distribution kit from Sybase.
Other sources of Use the Sybase Getting Started CD, the SyBooks™ CD, and the Sybase
information Product Manuals Web site to learn more about your product:

Installation and Configuration Guide xi

 • The Getting Started CD contains release bulletins and installation guides
in PDF format, and may also contain other documents or updated
information not included on the SyBooks CD. It is included with your
software. To read or print documents on the Getting Started CD, you need
Adobe Acrobat Reader, which you can download at no charge from the
Adobe Web site using a link provided on the CD.
• The SyBooks CD contains product manuals and is included with your
software. The Eclipse-based SyBooks browser allows you to access the
manuals in an easy-to-use, HTML-based format.
Some documentation may be provided in PDF format, which you can
access through the PDF directory on the SyBooks CD. To read or print the
PDF files, you need Adobe Acrobat Reader.
Refer to the SyBooks Installation Guide on the Getting Started CD, or the
README.txt file on the SyBooks CD for instructions on installing and
starting SyBooks.
• The Sybase Product Manuals Web site is an online version of the SyBooks
CD that you can access using a standard Web browser. In addition to
product manuals, you will find links to EBFs/Maintenance, Technical
Documents, Case Management, Solved Cases, newsgroups, and the
Sybase Developer Network.
To access the Sybase Product Manuals Web site, go to Product Manuals at
http://www.sybase.com/support/manuals/.
Sybase certifications Technical documentation at the Sybase Web site is updated frequently.
on the Web

❖ Finding the latest information on product certifications

1 Point your Web browser to Technical Documents at
http://certification.sybase.com/ucr/search.do.

2 Either select the product family and product under Search by Base
Product; or select the platform and product under Search by Platform.
3 Select Search to display the availability and certification report for the
selection.

❖ Finding the latest information on component certifications

1 Point your Web browser to Availability and Certification Reports at
http://certification.sybase.com/.

2 Either select the product family and product under Search by Base
Product; or select the platform and product under Search by Platform.

xii Sybase IQ
 About This Book

3 Select Search to display the availability and certification report for the
selection.

❖ Creating a personalized view of the Sybase Web site (including support

pages)
Set up a MySybase profile. MySybase is a free service that allows you to create
a personalized view of Sybase Web pages.
1 Point your Web browser to Technical Documents at
http://www.sybase.com/support/techdocs/.

2 Click MySybase and create a MySybase profile.

Sybase EBFs and
software
maintenance

❖ Finding the latest information on EBFs and software maintenance

1 Point your Web browser to the Sybase Support Page at
http://www.sybase.com/support.

2 Select EBFs/Maintenance. If prompted, enter your MySybase user name

and password.
3 Select a product.
4 Specify a time frame and click Go. A list of EBF/Maintenance releases is
displayed.
Padlock icons indicate that you do not have download authorization for
certain EBF/Maintenance releases because you are not registered as a
Technical Support Contact. If you have not registered, but have valid
information provided by your Sybase representative or through your
support contract, click Edit Roles to add the “Technical Support Contact”
role to your MySybase profile.
5 Click the Info icon to display the EBF/Maintenance report, or click the
product description to download the software.
Syntax conventions This documentation uses these conventions in syntax descriptions:
• Keywords SQL keywords are shown in UPPERCASE. However,
SQL keywords are case-insensitive, so you can enter keywords in any
case; SELECT, Select, and select are equivalent.
• Placeholders Items that must be replaced with appropriate identifiers
or expressions are shown in italics.

Installation and Configuration Guide xiii

 • Continuation Lines beginning with an ellipsis (...) are a continuation
of the statements from the previous line.
• Repeating items Lists of repeating items are shown with an element
of the list followed by an ellipsis (...). One or more list elements are
allowed. If multiple elements are specified, they must be separated by
commas.
• Optional portions Optional portions of a statement are enclosed by
square brackets. For example:
RELEASE SAVEPOINT [ savepoint-name ]
The square brackets indicate that the savepoint-name is optional. Do not
type the brackets.
• Options When none or only one of a list of items must be chosen, the
items are separated by vertical bars and the list enclosed in square
brackets. For example:
[ ASC | DESC ]
The square brackets indicate that you can choose ASC, DESC, or neither.
Do not type the brackets.
• Alternatives When precisely one of the options must be chosen, the
alternatives are enclosed in curly braces. For example:
QUOTES { ON | OFF }
The curly braces indicate that you must include either ON or OFF. Do not
type the brackets.
Typographic Table 1 lists the typographic conventions used in this documentation.
conventions

xiv Sybase IQ
 About This Book

Table 1: Typographic conventions

Item Description
Code SQL and program code appears in a monospaced (fixed-
width) font.
User entry Text entered by the user is shown in a monospaced (fixed-
width) font.
emphasis Emphasized words are shown in italic.
file names File names are shown in italic.
database objects Names of database objects, such as tables and procedures,
are shown in bold, sans serif type in print, and in italic
online.

The demo database Sybase IQ includes scripts to create a demo database (iqdemo.db). Many of the
queries and code samples in this document use the demo database as a data
source.
The demo database contains internal information about a small company
(employees, departments, and financial data), as well as product (products),
and sales information (sales orders, customers, and contacts).
See the Sybase IQ installation guide for your platform or talk to your system
administrator for more information about the demo database.
Accessibility This document is available in an HTML version that is specialized for
features accessibility. You can navigate the HTML with an adaptive technology such as
a screen reader, or view it with a screen enlarger.
Sybase IQ 15.1 and the HTML documentation have been tested for compliance
with U.S. government Section 508 Accessibility requirements. Documents that
comply with Section 508 generally also meet non-U.S. accessibility guidelines,
such as the World Wide Web Consortium (W3C) guidelines for Web sites.

Configuring your accessibility tool

You might need to configure your accessibility tool for optimal use. Some
screen readers pronounce text based on its case; for example, they pronounce
ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You
might find it helpful to configure your tool to announce syntax conventions.
Consult the documentation for your tool for information on using screen
readers.

For information about how Sybase supports accessibility, see Sybase

Accessibility at http://www.sybase.com/accessibility. The Sybase Accessibility
site includes links to information on Section 508 and W3C standards.

Installation and Configuration Guide xv

If you need help Each Sybase installation that has purchased a support contract has one or more
designated people who are authorized to contact Sybase Technical Support. If
you cannot resolve a problem using the manuals or online help, please have the
designated person contact Sybase Technical Support or the Sybase subsidiary
in your area.

xvi Sybase IQ
CH A PTE R 1 Preparing for Installation

About this chapter This chapter describes preinstallation requirements and considerations.
Contents
Topic Page
Overview 2
Planning your installation 4
Disk space and memory requirements 6
Pre-installation tasks 7
Installing your software 10

Installation and Configuration Guide 1

Overview

Overview
Sybase IQ is a high-performance decision support server designed specifically
for data warehousing.
Sybase IQ is part of the Adaptive Server® product family that includes
Adaptive Server Enterprise and SQL Anywhere. Component Integration
Services embedded within Sybase IQ provide direct access to relational and
non-relational databases on mainframe, UNIX, or Windows servers.

Product editions
Sybase IQ is available in the following editions:
• Enterprise Edition
• Small Business Edition
• Single Application Server Edition
• Evaluation Edition

Platforms and operating systems

Sybase IQ analytics server is compatible with the following platforms and
operating systems:
• Microsoft Windows 2003 (x86) for 32-bit systems – minimum patch level
Service Pack 2
• Microsoft Windows 2003 (x64) for 64-bit systems – minimum patch level
Service Pack 2
• Microsoft Windows XP Professional (x86) for 32-bit systems – minimum
patch level Service Pack 2
• Microsoft Windows Vista for 32-bit and 64-bit systems – minimum patch
level Service Pack 1
• Microsoft Windows 2008 for 32-bit and 64-bit systems – minimum patch
level Service Pack 1

2 Sybase IQ
 CHAPTER 1 Preparing for Installation

Network Client supported platforms

Sybase IQ 15.1 provides a Network Client for all supported server platforms
and includes the platform-specific network client with each server purchased.
Sybase IQ Network Client for Windows includes the 32-bit ODBC Windows
drivers. Windows 64-bit ODBC drivers allow you to connect to Sybase IQ
from third-party packaged 64-bit Windows applications and 64-bit Windows
applications written in C++.

Updated software components

Sybase IQ Server 15.1 installs the following software components, updated to
the latest versions available at release time:
• Sybase jConnect™ JDBC Driver version 6.0. This component is optional
but strongly recommended. If you install the jConnect driver, Java classes
installed into a database can make JDBC calls to access and modify data.
• Java Runtime Environment (JRE) version 6.0 to use the latest Sybase
Central plug-in for Sybase IQ.

Licensing requirements
Sybase IQ is available in Evaluation and Licensed Editions.
Installing an unlicensed Evaluation Edition of Sybase IQ provides full access
to all features and options available in the Enterprise Edition. To run an
unlicensed database beyond a 30 day evaluation period, however, you must
purchase and install an appropriate Sybase Software Asset Management
(SySAM) license.
To install and configure any product edition and any optional feature, you
should know which features you are licensed to use. See “Licensing your
software” on page 13 for information about obtaining and installing your
license.

Installation media
Sybase IQ includes installation media for server and client installations.

Installation and Configuration Guide 3

Planning your installation

Media Description
Sybase IQ Product DVD Installs Sybase IQ server components and other support
tools.
Sybase IQ Network Client CD Installs the components required for client connections
to a Sybase IQ network server.

Planning your installation

How you install Sybase IQ depends on whether you are installing Sybase IQ
for the first time, upgrading from a previous version, or migrating your
databases to a new hardware platform.

Installing Sybase IQ for the first time

If you are installing Sybase IQ for the first time, not upgrading from a previous
edition, follow these steps:
• Read the 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.
• Complete all preinstallation tasks. Apply any required operating system
patches, check to see that there is sufficient disk space and memory, and
update any necessary configuration changes. See “Pre-installation tasks”
on page 7 for specific information.
• Determine the license model you want to use. SySAM supports served and
unserved license models. See Chapter 2, “Choosing a License Model" in
the Sybase Software Asset Management Users Guide to determine which
model is best suited for your environment.
• Use the product and licensing information from the e-mail or web key you
received from Sybase to logon to the Sybase Product Download Center
and generate a license key for your software.
• Install Sybase IQ server components, activate your license, then start and
test your server. See “Installing Sybase IQ Server” on page 25 and
“Testing installed products” on page 33 for additional information.

4 Sybase IQ
 CHAPTER 1 Preparing for Installation

• Install and configure Sybase IQ client components. See “Installing Sybase

IQ Client Components” on page 39 and “Configuring Sybase IQ” on page
91 for more information.

Upgrading from a previous version

What you do depends on the version of Sybase IQ currently installed on your
system.
Sybase IQ 15.0 • Uninstall Sybase IQ 15.0 before you install Sybase IQ 15.1. Use the
Control Panel to remove Sybase IQ 15.0, and then proceed as if you were
installing Sybase IQ for the first time.
• Upgrade your client tools. Although you can use 15.0 client tools to
connect to a 15.1 server, some options, tools, and objects specific to
Sybase IQ 15.1 may not be available.
Sybase IQ 12.x • Upgrade Sybase IQ, if necessary. All database migration paths assume that
you are migrating from Sybase IQ 12.6 ESD 11 or Sybase 12.7 ESD 5. If
you are migrating from a version prior to 12.6, you must upgrade your
software before you migrate your database.
• Review the migration chapter and plan your migration. Sybase provides
utilities that you can use to migrate your 12.x data to Sybase IQ 15.1.
Understanding how these utilities work can help you plan your migration
more effectively. See “Migration utilities” on page 47 for more
information.
• Follow the work flows for the type of databases you want to migrate.
There are separate migration paths for simplex and multiplex databases.
See “Migrating simplex databases” on page 66 and “Migrating multiplex
databases” on page 70 for additional information.

Changing hardware platforms

If you are upgrading from a previous version and want to move your Sybase IQ
databases to a different supported hardware platform, perform the conversion
before you upgrade your data to Sybase IQ 15.1.
• For information about migrating a database from one platform to another
with the same endian structure, see “Converting to a new hardware
platform” on page 45 for specific steps.

Installation and Configuration Guide 5

Disk space and memory requirements

• After you change upgrade your hardware platform, follow the appropriate
workflow in “Migrating Data” on page 43 to migrate your databases.

Notes
• If you created your Sybase IQ database on a Linux 32–bit version prior to
Sybase IQ 12.6 ESD #2, you must first install IQ 12.6 ESD #2 for Linux
32–bit and create a new data backup before converting to another
platform.
• Sybase IQ 12.6 ESD #2 and higher releases support migration between
Windows and Linux.

Disk space and memory requirements

Use the following tables to plan your disk space and memory requirements.
Server and client components are listed separately. Typical installations share
some common components and generally require less disk space than the totals
indicate.
Server Table 1-1: Sybase IQ Windows 64-bit Server Requirements
Component Feature Disk Space RAM
Server Sybase IQ 474 MB -- --
Sybase Central Java Edition 223 MB -- --
jConnect 89 MB -- --
SySAM License Server 153 MB -- --
Sybase Software Asset Management Utilities 142 MB -- --
Total 1081 MB 1 GB

Table 1-2: Sybase IQ Windows 32-bit Server Requirements

Component Feature Disk Space RAM
Server Sybase IQ 485 MB -- --
Sybase Central Java Edition 279 MB -- --
jConnect 108 MB -- --
SySAM License Server 150 MB -- --
Sybase Software Asset Management Utilities 142 MB -- --
Total 1164 MB 1 GB

6 Sybase IQ
 CHAPTER 1 Preparing for Installation

Client Table 1-3: Sybase IQ 64-bit Client Requirements

Component Feature Disk Space RAM
Client Sybase IQ 270 MB -- --
Sybase Central Java Edition 223 MB -- --
jConnect 89 MB -- --
Total 582 MB 1 GB

Table 1-4: Sybase IQ 32-bit Client Requirements

Component Feature Disk Space RAM
Client Sybase IQ 311 MB -- --
Sybase Central Java Edition 279 MB -- --
jConnect 108 MB -- --
Total 698 MB 1 GB

Note Servers require additional disk space for data storage. See Chapter 3,
“Working with Database Objects” in the System Administration Guide for
information about estimating the disk space you need for your IQ data.

Pre-installation tasks
Perform the following tasks before you install Sybase IQ. You may need to
refer to your operating system documentation for specific commands.

Check for operating system patches

Apply any operating system patches before you install Sybase IQ. Check with
your operating system vendor for information on the latest operating system
patches.

Note Do not use a patch that is earlier than the version suggested for your
operating system. Use the patch recommended by the operating system vendor,
even if it supersedes the patch listed under “Platforms and operating systems”
on page 2.

Installation and Configuration Guide 7

Pre-installation tasks

Check the available disk space and memory

Check the available disk space and RAM against the “Disk space and memory
requirements” on page 6 to ensure that you have sufficient resources to install
and run Sybase IQ.

Increase the swap space

The recommended minimum swap space to run Sybase IQ is at least 1GB.
Certain operations may cause the memory used by Sybase IQ to grow
dynamically. Changing the way Sybase IQ uses buffers can dramatically
change the way it uses memory. See the chapter “Managing System
Resources” in the Performance and Tuning Guide for more information about
buffers.
Depending upon the load on the system where the Sybase IQ executable is
running, swap requirements may exceed space allotted. Insufficient swap space
may result in the system supporting fewer users, and large processes that
cannot acquire sufficient swap space may be prematurely killed by the
operating system.
See your operating system documentation for information about extending
swap space.

Enable 4GT
Enabling 4-gigabyte tuning (4GT) increases the amount of physical memory
available to memory-intensive applications running on Windows Server 2003,
Enterprise Edition, or Windows Server 2003, Datacenter Edition.
To enable 4GT, add the /3GB parameter to the start-up lines in the boot.ini file
by. For example:
[boot loader] timeout=5 default=multi(0)disk(0)rdisk(0)
partition(1)\WINNT
[operating systems] multi(0)disk(0)rdisk(0)
partition(1)\WINNT="Microsoft Windows 2000
Professional"
/fastdetect /3GB

8 Sybase IQ
 CHAPTER 1 Preparing for Installation

Notes
• Setting Sybase IQ cache sizes with 4GT support allows the size of the main
and temporary caches to be increased up to a combined total of 2GB.
• With Windows platforms that support 4GT, a Sybase IQ process can
extend beyond the 2GB address space boundary, up to a total of 3GB.
However, the total size of the two IQ buffer caches cannot exceed 2GB.
This is due to the Windows restriction that prevents a single memory
allocation from crossing the 2GB boundary.

Windows support issues

Following are some issues relating to running Sybase IQ software on Windows
Vista and Windows 2008:
Windows security Windows Vista and Windows 2008 incorporate a new security model. User
Account Control (UAC) is enabled by default and may affect the behavior of
programs that expect to be able to write files, especially when the computer
supports more than one user. Depending on where and how files and directories
are created, a file created by one user may have permissions that do not allow
another user to read or write to that file. If you install Sybase IQ in the default
directories, files and directories that require read/write access for multiple
users are set up appropriately.
Sybase IQ elevated Certain actions require privilege elevation to execute when run under User
operations agent Account Control. The programs dbelevate11.exe and iqdsn.exe may require
elevation in Sybase IQ.
The following dll files require elevation when they are registered or
unregistered: dbodbc11.dll and dboledb11.dll.
Certain actions require privilege elevation to execute when run under User
Account Control. The following programs may require elevation in Sybase IQ:
SybaseIQservice15.exe, dbelevate11.exe, and iqdsn.exe.
The following dlls require elevation when they are registered or unregistered:
dbodbc11.dll and dboledb11.dll.
On a system with User Account Control activated, you may receive an
elevation prompt for the Sybase IQ elevated operations agent. The prompt is
issued by the User Account Control system to confirm that you want to
continue running the identified program (if logged on as an administrator) or
to provide administrator credentials (if logged on as a non-administrator).

Installation and Configuration Guide 9

Installing your software

Deployment changes The program dbelevate11.exe is used internally by Sybase IQ components to

perform operations that require elevated privileges. This executable must be
included in deployments of Sybase IQ. Administrator privileges are required to
run dbelevate.
Sybase IQ Sybase IQ executables are signed by Sybase, Inc.
executables signed
Using an AWE cache To use an AWE (Address Windowing Extensions) cache on Windows Vista or
Windows 2008, you must run the database server as administrator. Starting a
non-elevated database server with an AWE cache results in a warning that the
database server must be run as an administrator to use AWE. See “-cw server
option” in Chapter 1, “Running the Database Server,” in the Utility Guide.
Samples Samples now correctly handle Sybase IQ installation path names that contain
one or more spaces.
Windows services Vista and Windows 2008-compliant services are not allowed to interact with
the desktop. Sybase IQ services do not interact with the desktop (even if Allow
Interaction with Desktop is enabled in the service definition). Sybase IQ
database servers can be monitored using the dbconsole utility or from Sybase
Central. Sybase Central disables the option to allow service to interact with
desktop when running on Windows Vista or Windows 2008.

Verify network functionality

Sybase IQ uses networking software whenever the client and server
components are installed on different systems. Use the ping command to and
from another computer to verify that the server where you plan to install
Sybase IQ can use TCP/IP to communicate with other devices on your
network.

Installing your software

The Sybase IQ installation media includes all of the components you need to
install your software. There are interactive and silent install options available.
Interactive installs The interactive installer is a standard installation wizard that lets you set up
your software in a graphically-based environment. The interactive installer
supports all product editions and installation types.

10 Sybase IQ
 CHAPTER 1 Preparing for Installation

Silent installs Silent install scripts perform standard IQ installations without the need to
interact with the product. These scripts are configured to perform typical server
installations by default; custom installs require additional configuration. See
“Silent Installations” on page 105 for more information.
Installation types Typical and custom installation types are available.Typical installations install
features suitable for most production environments. Custom installs let you
choose the components you want to install. You can select group packages,
individual items, or a combination of the two.

Installation and Configuration Guide 11

Installing your software

12 Sybase IQ
CH A PTE R 2 Licensing your software

About this chapter This chapter provides information about generating a SySAM license for
Sybase IQ 15.1 server.
Contents
Topic Page
Overview 14
Before you generate your license 17
Generate your SySAM license 19
Installing a new license server 21

Installation and Configuration Guide 13

Overview

Overview
Generate your SySAM license before you install your server or client
components. SySAM is a licensing mechanism that provides system
administrators with a means to enable and monitor their site's use of Sybase
products.
Sybase IQ includes separate SySAM licenses for each product edition and
separate licenses for any optional features available for that edition. For
example, all Sybase IQ product editions require a CPU license, but an MPXO
license is available only for the Enterprise and Single Application editions
where multiplex is offered as a separate purchase option.

Sybase Product Download Center

When you purchase a Sybase product you receive an e-mail or web key that
tells you how to logon to the Sybase Product Download Center (SPDC). SPDC
is an online Web portal where you can download and license your software.
You must use SPDC to dynamically generate license keys for Sybase IQ.
The e-mail or web key you get also provides specific product and licensing
information. Use this information when you generate your licenses.

Available licenses
Available licenses are determined by the product edition and options you
purchase for that product edition.

Enterprise Edition (EE)

Orderable Actual License Required Optional

License Description
CPU IQ_CORE • License restricts the number of cores
(not CPUs) which an IQ server can use.
LOMO IQ_LOB • Allows you to create and use CLOB or
LOB columns. The number of LOB
licenses must match number of cores.
This license is required for 12.6 or 12.7
customers who already have a LOB
license (IQ_LOB).

14 Sybase IQ
 CHAPTER 2 Licensing your software

Orderable Actual License Required Optional

License Description
VLDB MO IQ_VLDBMGMT • Allows you to create multiple table
spaces and more than one user dbspace.
Also restricts the ability to create table
partitions. An IQ_VLDBMGMT is
required whenever an IQ server creates
or starts with three or more user
dbspaces.
Each VLDB license allows for 1 TB of
storage. You will need to purchase one
license for each additional TB of storage
in the main store.
ASO IQ_SECURITY • Allows you to use column encryption,
ECC Kerberos and FIPS. The number of
ASO licenses must match cores
This license is required for 12.6 or 12.7
customers who already have encryption
(IQ_ENC).
MPXO IQ_MPXNODE • Allows you to start secondary multiplex
nodes (readers/writers). The number of
nodes must always be less than cores, as
each multiplex server must have at least
one core.
This license is required for 12.6 or 12.7
customers who are already running
multiplex. This is a new license
requirement.
IDBA-PSO IQ_UDF • Allows you to define and run high-
performance scalar and aggregate user-
defined functions.

Installation and Configuration Guide 15

Overview

Small Businesss Edition (SE)

Orderable Actual License Required Optional

License Description
CPU IQ_CORE • Licenses the number of sockets (not
CPUs) which an IQ server can use.

Other limits set by the SE license

• Server checks out licenses equal to the number of sockets. However, the
combined total number of cores should never exceed 4 sockets (MAXCP)
• Total concurrent IP connections <= 25 (MC)
• Total main store <= 250GB (MS)

Single Application Edition (SA)

Orderable Actual License Required Optional

License Description
CPU IQ_CORE • Licenses the number of cores (not
CPUs) which an IQ server can use.

Other limits set by the SA license

• Total cores per/server <= 32 (MAXCP)
• Total number of user tables <= 25 (MT)
• Total number of columns <= 100 (MV)
• Total number of mpx nodes <= 1 (MSN)

Demo/Evaluation Edition
No license is required for the Evaluation Edition. The Evaluation Edition is an
unlicensed server that provides full access to all features and options available
in the Enterprise Edition. To run an unlicensed database beyond a 30 day
evaluation period, however, you must purchase and install an appropriate
license.

16 Sybase IQ
 CHAPTER 2 Licensing your software

Before you generate your license

Follow these steps before you generate your license.

Read the SySAM documentation

Review the SySAM documentation for specific information about SySAM
licensing, license models, and procedures:
• Sybase Software Asset Management (SySAM) 2 Users Guide introduces
asset management concepts and provides instructions for establishing and
administering SySAM 2 licenses.
• SySAM 2 Quick Start Guide tells you how to get your SySAM-enabled
Sybase product up and running quickly.
• FLEXnet Licensing End User Guide explains FLEXnet Licensing for
administrators and end users and describes how to use the tools which are
part of the standard FLEXnet Licensing distribution kit from Sybase.
These documents are available on the Getting Started CD and on the Web at
Product Manuals at http://sybooks.sybase.com

Decide on the license model you want to use

Decide on the license model you want to use before you generate your license
file. A license model refers to the way you set up your license files for your
licensed program(s). License files can reside on a central, networked license
server in a Served License model or on the machine running the licensed
program in an Unserved License model.
For information about served and unserved licenses, and which model is best
suited for your environment, see Chapter 2, "Choosing a License Model" in the
Sybase Software Asset Management Users Guide.

Installation and Configuration Guide 17

Before you generate your license

Get your host ID

If you plan to install a new license server, or use an existing license server, you
need the license server host ID. FLEXnet Licensing uses different machine
identifications for different machine architectures. If you have a copy of the
FLEXnet licensing utilities installed, you can use the lmhostid utility to print
the exact host ID that FLEXnet Licensing expects to use on any given machine.
lmutil is included in your product distribution, or you can download a copy from
FLEXnet Publisher download page at
http://www.globes.com/support/fnp_utilities_download.htm#unixdownload

You can also use a system level command to find the host ID. For platform-
specific commands and examples, see Hostids for FLEXnet Licensing-Supported
Platforms at http://www.ece.uci.edu/eceware/flexlm/chap9.htm. For additional
information, see the FAQs after you logon to the Sybase Product Download
Center (SPDC).

Note
Some platforms derive the host ID from the network adapter address. If your
machine has multiple network adapters, the command you use to get the host
ID may return one host ID for each network adapter. If this occurs, choose only
ONE from the list of host IDs. Sybase recommends that you use the value
associated with the primary wired Ethernet adapter. Do not use values
associated with internal loop back adapters.

Determine the host name

Although the host name is optional for unserved license models, you must
specify the host name of the license server for served licenses. Providing the
host name for all license types can simplify future license administration tasks.

Choose a port number

If you plan to install a license server or use an existing license server, you need
to know the TCP/IP port number that the license server will use to serve your
licenses. If you do not specify a port number, the license server uses the first
available port in the range of 27000 to 27009. If you are using three-server
redundancy, you must specify a port outside of this range.

18 Sybase IQ
 CHAPTER 2 Licensing your software

Generate your SySAM license

The procedure you use to generate your license depends on the license model
you plan to use. This section includes separate procedures for “Unserved
licenses” on page 19 and “Served licenses” on page 20.

Unserved licenses
Before you generate your license, you need the host ID and host name of the
server where you plan to install Sybase IQ. See “Get your host ID” on page 18
and “Determine the host name” on page 18 for more information.

❖ Generating an unserved license

1 Start your browser and log in to the Sybase Product Download Center
(SPDC) at https://sybase.subscribenet.com.

2 On the Product List page, choose Sybase IQ.

3 On the Product Information page, choose the product version appropriate
for your platform.
4 On the License Information page, choose the appropriate location, then
read and accept the license agreement, if necessary.
5 On the Product Download page, click the License Keys link.
6 On the License Information page, choose the appropriate license(s), scroll
to the bottom of the page, and click Select to Generate.
7 On the Generate Licenses page, do the following:
• Choose Unserved license, click Next.
• Specify the number of licenses you want to generate, click Next.
• Identify the host machine where you intend to install Sybase IQ. You
must identify the host ID and number of licenses. The host name is
optional. Click Generate.

Installation and Configuration Guide 19

Generate your SySAM license

8 Click Download License File and save your license to a temporary

location on the local file system. You must save the license file with a .lic
extension or SySAM will not recognize the license.

Note If you chose an unserved license model, you can now install Sybase IQ
server components. During installation, the installer will prompt you for
information about your license.

Served licenses
Before you generate your license, you need the host ID of the license server.
You may also want to specify the host name to simplify future license
administration. See “Get your host ID” on page 18 and “Determine the host
name” on page 18 for more information.

❖ Generating served licenses

1 Start your browser and log in to the Sybase Product Download Center
(SPDC) at https://sybase.subscribenet.com.

2 On the Product List page, choose Sybase IQ.

3 On the Product Information page, choose the product version appropriate
for your platform.
4 On the License Information page, choose the appropriate location, then
read and accept the license agreement, if necessary.
5 On the Product Download page, click the License Keys link.
6 On the License Information page, choose the appropriate license(s), scroll
to the bottom of the page, and click Select to Generate.
7 On the Generate Licenses page, do the following:
• Choose Served License, click Next.
• Specify the number of licenses you want to generate, click Next.
• Identify the host ID, host name, and port number of the license server.
Host name and port number are optional. Click Generate
8 Click Download License File and save your license to a temporary
location on the local file system. You must save the license file with a .lic
extension or SySAM will not recognize the license.

20 Sybase IQ
 CHAPTER 2 Licensing your software

Notes
Served licenses require a license server. If you do not plan to use an existing
license server, you must install one before you install Sybase IQ. See
“Installing a new license server” on page 21 for additional information.

Installing a new license server

If you chose a served license model and do not plan to use an existing license
server, you need to install a new one.
The Sybase IQ Server Installation DVD includes SySAM Network License
Server utilities you can use to install a new license server. You must run a
custom server installation to install a new license server. You do not need to run
the license server on the same machine where you install the Sybase IQ server
components.

❖ Installing a new license server

1 Use an account with Administrator privileges to log in to Windows. Stop
and shut down all programs before you run the installer.
2 Insert the Sybase IQ Product DVD into the drive.
If the Sybase IQ installer does not start automatically, start Windows
Explorer, change to your DVD drive, choose the appropriate setup file:
setup32.bat or setup64.bat.
3 On the Welcome screen, click Next.
4 Choose an installation directory, click Next.
5 Choose Evaluation as the product edition you want to configure, click
Next.
6 On the next screen, choose a location, then read and accept the license
agreement. Click Next.
You must accept an appropriate license agreement to install Sybase IQ.
You can review all available license agreements on the Sybase Web site at
http://www.sybase.com/softwarelicenses.

7 Choose Custom as the installation type you want to perform, click Next.

Installation and Configuration Guide 21

Installing a new license server

8 Deselect all installation features except Sybase Software Asset

Management.
9 Select both Sybase Software Asset Management features: Network
License Server and Network License Utilities, click Next.
10 Review the installation summary, then click Install.

❖ Starting your license server

1 From a command prompt, copy the license file you saved from SPDC to
the%SYBASE%\SYSAM-2_0\licenses directory on the network license
server.
2 Change to %SYBASE%\%SYSAM-2_0\%bin, then refresh or restart the
license server:
Use this command... To do this...
sysam start Start the license server.
Perform this step if the license server is not
running. After you perform this step repeat step
2 to verify that the server is running.
sysam reread Make the license server read the new license
file.
Perform this step if the license server is already
started.

3 Use the sysam status command to verify that the license server is running.
If the server is running, you can expect to see output like this:
Starting the SYSAM service
The SYSAM service is starting.
The SYSAM service was started successfully.
lmutil - Copyright (c) 1989-2006 Macrovision Europe
Ltd. and/or Macrovision Corporation. All Rights
Reserved. Flexible License Manager status on Wed
5/24/2006 15:04
License server status: 27000@mysysamserver
License file(s) on <server name>:
/opt/sybase/SYSAM_0/licenses/mysysamserver_60302031
5.lic

22 Sybase IQ
 CHAPTER 2 Licensing your software

Notes
• To verify your license, you can run the sp_iqlmconfig stored procedure in
Interactive SQL (iqisql) or check the Sybase IQ error log and
<dbname>.iqmsg file.
In the error log, a line beginning with “Checked out license...”
indicates that the license configuration is successful. If you see a “Sysam:
FLEXnet Licensing error:” message, check with your Sybase
representative to resolve the issue.
• The SySAM License Server Installer installs both IPv4 only and
IPv4/IPv6 dual stack License Server binaries during installation and
configures use of IPv4 only binaries. You can use the SySAM script to
configure the appropriate version of the license server: sysam configure
[IPv6|IPv4].

For example: sysam configure IPv6 will configure use of the IPv4/IPv6
dual stack binaries. For more information, see SySAM Users Guide.
• If you have problems activating your license, see “Troubleshooting
SySAM” on page 119.

Installation and Configuration Guide 23

Installing a new license server

24 Sybase IQ
CH A PTE R 3 Installing Sybase IQ Server

About this chapter This chapter provides instructions for installing Sybase IQ for operation
as a network server.
Contents
Topic Page
Overview 26
Installing Server components 29
Post-installation tasks 31
Uninstalling Sybase IQ server 32

Installation and Configuration Guide 25

Overview

Overview
Installing Sybase IQ server is part of a planned installation sequence. Follow
the installation path you chose in “Planning your installation” on page 4. Read
this section for information you should know before you begin your server
installation:

Before you install Sybase IQ server

• Read the Sybase IQ Release Bulletin for the latest information. See the
special installation instructions section for any installation instructions not
included in this document.
• Complete all pre-installation tasks. Apply any required operating system
patches, check to see that there is sufficient disk space and memory, and
make any necessary configuration changes. See “Pre-installation tasks”
on page 7 for specific information.
• Generate your license key and download your license to a temporary
location on the local file system. If you chose a served license model,
install and start the new license server, or know which license server you
plan to use. See “Licensing your software” on page 13 for details.
• Know the product edition you intend to install and license you intend to
use. If you plan to use a license server, you need to know the license
server’s Host ID, host name, and port number.
• Determine the target installation directory. The default installation
directory is C:\Sybase. You can choose an alternate location during
installation.

Note Instructions in this chapter are specific to the graphically-based

interactive installer, see “Silent Installations” on page 105 for silent
installation setup instructions.

26 Sybase IQ
 CHAPTER 3 Installing Sybase IQ Server

Server components
Server components are grouped by feature. In this table, items marked as
default are installed in a typical installation.
Feature Components Default Notes
Sybase IQ Sybase IQ Server • Installs server software, client
Sybase IQ Client • tools, and ODBC drivers.
Sybase IQ ODBC •
Sybase Central Sybase Central Viewer • Viewer and plug–in are required
Sybase Central Plug–in • for Sybase Central.
jConnect • Required for JDBC connections.

Sybase Software Asset Network License Server Network license server utilities,
Management License Utilities • and FLEXnet Licensing utilities

Plug–in compatibility
Sybase Central is a graphically-based administration console for Sybase
products. The Sybase IQ Server 15.1 plug-in for Sybase Central is NOT
compatible with 12.x servers. You can only use the 15.x plug-in with 15.x
servers; you cannot use it to connect to 12.x servers.
Sybase
Central
IQ Plug–in Sybase IQ Toolkit Agent JRE
15.x Compatible only with 15.x servers. You 6.0 or later Agent – 15.x JRE – 6.0
cannot use the 15.x plug-in to connect to 12.x required agent required
servers. required
12.7 12.5 and higher fully supported. Earlier IQ 4.3 or later 12.7 Agent 1.4.2
versions minimally supported. required required required
12.6 12.6 or 12.5 fully supported. Earlier IQ 4.3 or later 12.6 Agent 1.4.2
versions minimally supported. required required required
12.5 12.5 or earlier 3.2 required 12.5 Agent 1.2.2
required required
(1.3.1 on
Linux)

Installation and Configuration Guide 27

Overview

What a server installation does

A typical server installation installs Sybase IQ server and support components
into a parent directory on the host machine.
Parent installation The parent directory contains files, scripts, and other objects required to
directory support Sybase IQ server.
The default installation directory is C:\Sybase. You can, however, specify
another target directory during the install if you use the interactive GUI
installer, or by changing the silent installation script if you perform a silent
install. This document uses the variable %SYBASE% to refer to the parent
directory.
A list of the major subdirectories in the parent directory appears below.
Directory Contents
charsets Provides character sets available for use with Adaptive Server.
collate Provides the collation sequences available for use with
Adaptive Server.
ini Contains various configuration files.
IQ-15_1 Contains subdirectories, scripts, and property files required to
run Sybase IQ server.
jConnect-6_0 Provides the Java Database Connectivity (JDBC) driver for
Sybase IQ.
locales Provides language modules for system messages and date/time
formats.
shared Contains components and libraries that are shared by several
other components, including Sybase Central 60 and Java
Runtime Environment (JRE).
SYSAM-2_0 Location of the SySAM licenses and utilities. This directory
contains two subdirectories: bin and licenses.
uninstall Contains subdirectories for scripts that uninstall IQ and
SySAM.

28 Sybase IQ
 CHAPTER 3 Installing Sybase IQ Server

Sybase IQ installation The Sybase IQ installation directory is a child of %SYBASE% directory called
directory IQ-15_1.
This directory contains files, scripts, and other objects required to run Sybase
IQ server. This document uses the variable %IQDIR151% to refer to the
Sybase IQ installation directory. A list of the major subdirectories you are
likely to use in this directory during installation appears in the table below.
Directory Contents
Assembly ADO.NET and .NET assembly files.
bin<platform> Utilities you use to start and manage your server. <platform> value is
64 or 32 depending on your installation.
charsets Character encoding files.
demo Contains a readme that identifies the location of the demo database
scripts and sample data: C:\Documents and Settings\All
Users\SybaseIQ\demo directory.
install Installation history file.
java Different jar files.
logfiles Various logfiles. Sybase IQ writes log files to this directory.
lsunload Local Store Unload utility.
scripts Sample scripts and stored procedures.
SDK Subdirectories for various language utilities.
snmp Definitions for Simplet Network Management Protocol servers.
sun Local copy of the JRE to support Java in the database.
Sysam Local SySAM configuration information.
support Contains a Web page with links to online resources.
unload Various unload scripts, files and utilities.

Installing Server components

The Sybase IQ Server Installation media includes all of the components you
need to install an IQ Server.

❖ Running the Sybase IQ installer

1 Use an account with Administrator privileges to log in to Windows. Stop
and shut down all programs before you run the installer.
2 Insert the Sybase IQ Product DVD into the drive.

Installation and Configuration Guide 29

Installing Server components

If the Sybase IQ installer does not start automatically, start Windows

Explorer, change to your DVD drive, choose the appropriate setup file:
setup32.bat or setup64.bat.
3 On the Welcome screen, click Next.
4 Choose an installation directory, click Next.
5 Choose the Licensed Edition as the product edition you want to configure,
click Next.
6 On the next screen, choose a location, then read and accept the license
agreement.
You must accept an appropriate license agreement to install Sybase IQ.
You can review all available license agreements on the Sybase Web site at
http://www.sybase.com/softwarelicenses.

7 When the installer prompts you for the Sybase IQ license key(s), do one
of the following:
• Use an editor to open the license you downloaded from the SPDC site,
and paste the license in the license key text box.
• Click Browse, navigate to the license location, and, choose your
license.
• Click Use previously deployed license server, then specify the
server’s Host Name and Port Number. Use this option if you want to
use a previously deployed license server.
• Click Continue installation without a license key. Use this option to
install Sybase IQ in grace mode.
8 Click Next, then choose the appropriate Product Edition and License Type.
9 Click Next, then follow the instructions on the screen to complete your
installation.

30 Sybase IQ
 CHAPTER 3 Installing Sybase IQ Server

Notes
• If you decide to install Sybase IQ in grace mode, you can install the
product without a license, and activate a 30 grace period. You must obtain
an appropriate license from Sybase before the grace period ends.
• To verify your license, you can run the sp_iqlmconfig stored procedure in
Interactive SQL (iqisql) or check the Sybase IQ error log and
<dbname>.iqmsg file.
• In the server log, a line beginning with “Checked out license...”
indicates that the license configuration is successful. If you see a “Sysam:
FLEXnet Licensing error:” message, check with your Sybase
representative to resolve the issue.

Post-installation tasks
• Check the Sybase Support Page at http://www.sybase.com/support for
software updates. This site provides access to product updates and a
variety of downloads to help you get the most out of your Sybase products
and solutions.
• If you are upgrading from 15.0, use an account with DBA privileges to
connect to the server and database with dbisql. Run the ALTER DATABASE
UPGRADE command. For additional information about this command, see
ALTER DATABASE statement in Reference: Statements and Options.
• If you are upgrading from a 12.x version of Sybase IQ, see “Migrating
Data” on page 43 for information about migrating 12.x databases to
Sybase IQ 15.1.
• See “Testing installed products” on page 33 for information about starting
your server, running queries with Interactive SQL, and working with the
demo database.
• See “Installing Sybase IQ Client Components” on page 39 for
information about installing Sybase IQ Client tools.
• See Introduction to Sybase IQ for hands-on exercises if you are unfamiliar
with Sybase IQ and the Sybase Central management console.

Installation and Configuration Guide 31

Uninstalling Sybase IQ server

Uninstalling Sybase IQ server

Use these instructions to uninstall Sybase IQ server.

❖ Uninstalling Sybase IQ Server Windows components

1 Click Start, point to Settings, choose Control Panel | Add or Remove
Programs.
2 Choose Sybase IQ 15.1 from the program list.
3 Click Change/Remove.
4 Follow the instructions on the screen.

32 Sybase IQ
CH A PTE R 4 Testing installed products

About this chapter This chapter tells you how to start Sybase IQ and use the demo database
to test your installation.
Contents
Topic Page
Demo database 34
Running interactive SQL queries 35

Installation and Configuration Guide 33

Demo database

Demo database
Sybase IQ includes scripts to create a demo database. In the
%ALLUSERSPROFILE%\SybaseIQ\demo directory, you will see the script
mkiqdemo.bat. This script creates the demo database by modifying, then
running the script mkiqdemo.sql, which will load in data from the sub-directory
\adata.
The sample data supports an imaginary sporting goods company. The sample
database has been updated for the 15.1 release. If you are upgrading from a
previous edition, see “Table names” on page 34 for demo database table
names.
Table names This table includes the former names and new names of sample tables so that
you can update scripts or applications.
12.7 name 15.0 name 15.0 owner
contact Contacts GROUPO
customer Customers GROUPO
department Departments GROUPO
emp1 emp1 DBA
employee Employees GROUPO
fin_code FinancialCodes GROUPO
fin_data FinancialData GROUPO
iq_dummy iq_dummy DBA
product Products GROUPO
sale sale DBA
sales_order_items SalesOrderItems GROUPO
sales_order SalesOrders GROUPO
SYSOPTIONDEFAULTS DBA

Note The previous demo database, Megaphone Telco, is not included with
Sybase IQ 15.1

34 Sybase IQ
 CHAPTER 4 Testing installed products

❖ Starting the demo database

Use these instructions to start the demo database installed with the product.
• Click Start, point to Programs | Sybase | Sybase IQ 15.1 | Start Sybase IQ
Demo Database. This step also creates iqdemo if it does not exist.

Note For customers who are use to the older asiqdemo database, you can still
create that database by passing in the flag -old to the mkiqdemo.bat script.

Running interactive SQL queries

Interactive SQL is a utility shipped with Sybase IQ that lets you execute SQL
statements, build scripts, and display database data.
When you start Interactive SQL, a Connect window appears that lets you
define connection parameters to your server or database. The Connect window
also has a Connect Assistant to help you connect to a database. To display or
hide the Connect Assistant, click the arrow in the top right corner of the
window.

❖ Starting Interactive SQL and running queries

Assume that you want to execute a query against iqdemo that is running on a
local host machine named localhost-xp. If you need connection help when you
work with Interactive SQL, click the
1 Click Start, point to Programs | Sybase | Sybase IQ 15.1 | Interactive SQL
Java.
2 On the Identification tab, type DBA in the User box, and sql in the
Password box. DBA is not case-sensitive; sql is case-sensitive, and must
appear in all lowercase letters.
3 On the Database tab, choose a server from the Server name box. If there
are no servers listed, click Find to search for running servers.
Server names appear in this format <hostname>_dbname. If the host
name is localhost-xp and you are running the sample iqdemo database, the
server name would be localhost-xp_iqdemo
4 Choose iqdemo as the database from the Database name box. If there is
only one database running, this can be left blank.

Installation and Configuration Guide 35

Running interactive SQL queries

5 What you do next depends on the server location:

• If you are running dbisql against a server installed on the same
machine, you must also choose an appropriate Database file.
• If you are running dbisql against a networked server, click the
Network tab, click the TCP/IP box, then specify the Host name and
Port number.
6 Click OK to open Interactive SQL.
The Interactive SQL window is split into 3 subwindows. In the top
window (SQL Statements), type:
SELECT * FROM employees
7 Click the right-facing triangle button to execute the query.

Notes
• Sybase Central and Interactive SQL no longer support jConnect. Sybase
Central and Interactive SQL use the SQL Anywhere JDBC Driver.
jConnect is provided with Sybase IQ 15.1 for customer application
backward compatibility purposes.
• As a general rule, the jConnect driver cannot use ODBC data sources.
However, Sybase Central and Interactive SQL are special cases. When
you use the jConnect driver in either of them, you can specify an ODBC
data source to establish a connection.

Creating databases To create your own databases, start and connect to the utility database, as
described in the Sybase IQ System Administration Guide.
Starting your own To start your own databases, use the start_iq utility.
databases
To run start_iq, at the Command Prompt, change to a directory where the
configuration and database files are located, and use the following command
format:
start_iq @configuration_filename.cfg dbname.db
This command starts the database and sets parameters named in the (optional)
configuration (.cfg) file.

36 Sybase IQ
 CHAPTER 4 Testing installed products

You can use a configuration file to specify options that you want to set
whenever you start your server. A configuration file for the demo database is
installed in the %ALLUSERSPROFILE%\SybaseIQ\demo directory as an
example. For details about configuration files, see “Using configuration files”
on page 92.

Note The directory where the server is started becomes the default directory
for all server files created by Sybase IQ.

For example, to start the demo database, use these commands:

C:\> cd %ALLUSERSPROFILE%\SybaseIQ\demo
start_iq @iqdemo.cfg iqdemo.db
Using defaults in %IQDIR15%\scripts\default.cfg, the start_iq utility sets any
required environment variables that have not been set and sets parameters that
govern Sybase IQ to the recommended defaults. (You may use a configuration
file to override these defaults.) If you start your server using any command
other than start_iq, or if your configuration file is encrypted, the following
parameters are highly recommended:
Table 4-1: Parameters set by start_iq
Parameter Value Description
-c 48MB on all platforms Catalog store cache size
-gc 20 Checkpoint interval
-gd all Allows all users to start the database by
connecting
-gl all Allows all users to load or unload tables
-gm 10 Default number of connections
-gp 4096 Catalog store page size
-ti 4400 Client time-out set to 72 hours. Prevents
users with long queries from being
logged off over a long weekend.

Note Do not discard this document after installing Sybase IQ. You may need
these required parameters later.

For a complete list and description of start-up parameters, see “The database
server” in Chapter 1 of the Sybase IQ Utility Guide.
If you have Sybase Central, you can use the Start Database Server wizard, as
documented in the Introduction to Sybase IQ, instead of start_iq.

Installation and Configuration Guide 37

Running interactive SQL queries

The server process runs in the background. It sends output to a server log file,
%ALLUSERSPROFILE%\SybaseIQ\logfiles\servername.NNNN.srvlog,
where NNN is the number of times the server has been started. For example,
%ALLUSERSPROFILE%\SybaseIQ\logfiles\localhost_iqdemo.0006.srvlog.
Stopping servers To stop a server, click the Sybase IQ icon to open the server window, then click
Shutdown. You can also stop a server using the STOP ENGINE command from
DBISQL or any front-end client, or using the Stop utility, as documented in the
Sybase IQ Reference Manual, Chapter 4, “Database Administration Utilities.”

Note When you stop a server using the DBSTOP command, you need to
specify the same parameters used to start that server.

38 Sybase IQ
CH A PTE R 5 Installing Sybase IQ Client
Components

About this chapter This chapter tells you how to install Sybase IQ client components. These
components are required to connect to a network server. For information
about installing Sybase IQ Server Components, see Chapter 3, “Installing
Sybase IQ Server”.
Contents
Topic Page
Overview 40
Installing client components on Windows 41
Uninstalling Sybase IQ client 42

Installation and Configuration Guide 39

Overview

Overview
The Sybase IQ Client Tools Installation CD includes all of the client tools you
need to connect a client machine to an Sybase IQ Server on the network.

Before you install Sybase IQ client tools

• Read the Release Bulletin for the latest information. See the special
installation instructions section for any installation instructions not
included in this document.
• Complete all pre-installation tasks. Apply any required operating system
patches, check to see that there is sufficient disk space and memory, and
make any necessary configuration changes. See “Pre-installation tasks”
on page 7 for specific information.

Note Instructions in this chapter are specific to the graphically-based

interactive installer, see “Silent Installations” on page 105 for silent
installation setup instructions.

Client components
Client components are grouped by feature. Items marked as default are
installed in Typical installations.
Feature Components Default Notes
Sybase IQ Sybase IQ Client • Installs client tools, and ODBC
Sybase IQ ODBC • drivers.
Sybase Central Sybase Central Viewer • Viewer and plug–in are required
Sybase Central Plug–in • for Sybase Central.
jConnect • Required for JDBC connections.

40 Sybase IQ
 CHAPTER 5 Installing Sybase IQ Client Components

What a client installation does

A typical client installation installs the network client components into a parent
directory on a client machine.
Parent installation The parent directory contains the files, scripts, and other objects required to
directory support the Sybase IQ client. This document uses the variable %SYBASE% to
refer to the client parent directory.
The default installation directory is C:\Sybase.You can, however, specify
another target directory during the install if you use the interactive GUI
installer, or by changing the silent installation script if you perform a silent
install. This document uses the variable %SYBASE% to refer to the parent
directory.
Sybase IQ installation The Sybase IQ client installation directory, IQ-15_1, is a child of the
directory %SYBASE% parent directory.
This directory contains subdirectories, scripts, and property files required to
run Sybase IQ client. This document uses the variable %IQDIR151% to refer
to the Sybase IQ installation directory on the client.
Demo database and C:\Documents and Settings\All Users\SybaseIQ contains subdirectories for the
samples directory demo database and code sample installed with Sybase IQ. This document uses
the variables %ALLUSERSPROFILE%\SybaseIQ\demo and
%ALLUSERSPROFILE%\SybaseIQ\samples to refer to these directories.

Installing client components on Windows

The Sybase IQ Windows Client Installation CD includes all of the components
you need to install a Sybase IQ client on Windows. The client installer includes
a single setup wizard for all product editions.

❖ Installing Sybase IQ Client Tools on Windows

1 Use an account with Administrator privileges to log in to Windows. Stop
and shut down all programs before you run the installer.
2 Insert the Sybase IQ Client installation DVD into the drive.
If the Sybase IQ installer does not start automatically, start Windows
Explorer, change to your DVD drive, choose the appropriate setup file for
your platform (setup32.bat or setup64.bat).
3 Click Next on the Welcome screen.

Installation and Configuration Guide 41

Uninstalling Sybase IQ client

4 Choose the product edition you want to configure, then click Next.
5 Choose a location, then read and accept the license agreement. Click Next.
You must accept an appropriate licence agreement to install Sybase IQ.
You can review all available license agreements on the Sybase Web site at
http://www.sybase.com/softwarelicenses.

6 Follow the instructions on the screen.

Uninstalling Sybase IQ client

Use these instruction to uninstall Sybase IQ client components.

❖ Uninstalling Windows client components

1 Click Start, point to Settings, choose Control Panel | Add or Remove
Programs.
2 Choose Sybase IQ-15_1 from the program list.
3 Click Change/Remove.
4 Follow the instructions on the screen.

42 Sybase IQ
CH A PTE R 6 Migrating Data

About this chapter This chapter explains how to migrate data from previous Sybase IQ
versions to Sybase IQ 15.1.
Contents
Topic Page
Overview 44
Migration utilities 47
Avoiding potential migration problems 62
Migrating simplex databases 66
Migrating multiplex databases 70
Post-migration tasks 87

Installation and Configuration Guide 43

Overview

Overview
All Sybase IQ databases follow the same basic migration process. Platform
migration and multiplex migration includes some extra additional steps.
Sybase strongly recommends that you read this entire chapter before
performing any migration.
Install Sybase IQ 15.1 before you migrate your 12.x databases. Sybase IQ 15.1
includes tools that you can use to migrate your databases. See “Installing
Sybase IQ for the first time” on page 4 for a summary of all installation tasks.

Upgrading from a previous version

• 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 Sybase IQ. If you are migrating from a version prior to 12.6, you
must upgrade to Sybase IQ 12.6 or later. All migration paths assume that
you are migrating from Sybase IQ 12.6 ESD 11 or Sybase IQ 12.7 ESD 5.
• Sybase IQ 12.6 and higher versions do not support existing LONG BINARY
columns created using any release prior to Sybase IQ 12.5 ESD8. You
must explicitly drop LONG BINARY columns before migrate 15.1, and
recreate them after installing. For details, see “Upgrading existing LONG
BINARY columns” in Large Objects Management in Sybase IQ.
• The SORTKEY function now uses the International Components for
Unicode (ICU) library, instead of the Sybase Unicode Infrastructure
Library (Unilib®). Sort key values created using a version of Sybase IQ
prior to 15.0 do not contain the same values created using version 15.0 and
higher. You should regenerate any sort key values in your database that
were generated using a version of Sybase IQ prior to 15.0.
• Sybase IQ 15.1 no longer supports the creation of 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 choose to unload the
database and then load the schema and data into a database that you create,
then you must use one of the supplied collations.
• Backup 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.

44 Sybase IQ
 CHAPTER 6 Migrating Data

• Review and understand the database migration utilities. Sybase IQ 15.1

includes an iqunload utility that you can use to recreate the schema for your
database or simply migrate your database from 12.x to 15.1. An iqlsunload
utility is available for 12.7 multiplex users who need to move local stores.
Understanding these utilities before you begin can help you plan your
migration more effectively.
• Resolve potential migration errors before you migrate. Sybase IQ 15.1 no
longer supports some 12.x features and objects. You must 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. See
“Migrating simplex databases” on page 66 and “Migrating multiplex
databases” on page 70 additional information.

Converting to a new hardware platform

Sybase IQ supports migrating your database from one platform to another, as
long as both have the same endian structure. If you are upgrading from a
previous version and want to move your Sybase IQ databases to a different
supported hardware platform, perform the conversion before you upgrade your
data to Sybase IQ 15.1.

Notes
• If you created your Sybase IQ database on a Linux 32–bit version prior to
Sybase IQ 12.6 ESD #2, you must first install IQ 12.6 ESD #2 for Linux
32–bit and create a new data backup before converting to another
platform.
• Sybase IQ 12.6 ESD #2 and higher releases support migration between
Windows and Linux.

❖ Migrating a database from one platform to another (same endian

structure)
1 Back up the database.
2 Shut down the Sybase IQ server.
3 Install the Sybase IQ 12.x server on the new platform. Your migration can
take place on the same or a different machine.
4 Start the Sybase IQ server on the new hardware platform.

Installation and Configuration Guide 45

Overview

5 Connect to the utility database, utility_db.

6 Restore the database from the backup you created in Step 1.
7 Shut down the server and restart it against the restored database. If the
current version of Sybase IQ is higher than the version on which you were
previously running, you need to upgrade databases, and therefore restart
the server in a way that restricts user connections. Sybase recommends
using two server startup options:
• Use -gd DBA so that only users with DBA authority can start and stop
databases.
• Use -gm 1 to allow a single connection plus one DBA connection
above the limit so that a DBA can connect and drop others in an
emergency.
An alternate way to restrict connections is to specify
sa_server_option 'disable_connections', 'ON'
on the connection where you intend to perform the upgrade and
sa_server_option 'disable_connections', 'OFF'
on the same connection after upgrading. The disadvantage is that this
method precludes emergency access from another DBA connection.
8 Start Interactive SQL and issue the database upgrade statement. For
example:
ALTER DATABASE UPGRADE

If the database was created with the Java options off, append the keywords
JAVA OFF JCONNECT OFF to the preceding command.

Note Now that your database has been converted to the new platform, you can
proceed with migrating the 12.x database to Sybase IQ 15.1.

46 Sybase IQ
 CHAPTER 6 Migrating Data

Migration utilities
Sybase provides utilities that you can use to migrate your 12.x data to Sybase
IQ 15.1.

Sybase IQ 15.1 Unload utility (iqunload)

iqunload is a migration utility included with Sybase IQ 15.1 that performs two
main functions:
• Unloads the schema from a 12.x database.
• Migrates a 12.x database to Sybase IQ 15.1.
Command line arguments determine the operating mode. You can run iqunload
in schema unload mode or database migration mode.

Schema unload mode

Running iqunload in schema unload mode (iqunload -n) lets you connect to an
existing IQ 12.x server, and generate a reload.sql script that contains the entire
schema for your 12.x database. You can run this script against a new Sybase IQ
15.1 database to recreate the schema of the legacy database. Running iqunload
in schema unload mode provides two major benefits. You can:

• Verify the correctness of the schema by applying it to a new Sybase IQ

15.1 database.
• Estimate how long the actual migration process should take.

Note Schema unload mode is not supported for Sybase IQ 12.6. You must use
Sybase IQ 12.7 ESD 5 or later to use this option.

Database migration mode

Running iqunload in database migration mode (iqunload -au) performs the
actual database migration from IQ 12.x to Sybase IQ 15.1. This mode does not
use your existing IQ 12.x servers. Instead, database migration mode uses a
special bundled IQ 12.7 ESD 5+ server called iqunlspt.
Running iqunload -au performs the following tasks:
1 Starts your old database with the iqunlspt database engine

Installation and Configuration Guide 47

Migration utilities

2 Performs internal database checks

3 Determines if the database is a MPX write server
4 Generates the schema (similar to schema unload mode)
5 Starts the Sybase IQ 15.1 server
6 Creates a new database
7 Applies the generated schema
8 Backs up the operating system files. (This does not use the SQL BACKUP
statement.)
“Understanding iqunload” on page 51 for information about prerequisites,
syntax, and examples for using the iqunload utility in both modes.

Understanding data storage changes and schema reload

Migration to Sybase IQ 15.1 creates a new Catalog Store. Migration creates
and modifies system tables, system procedures, and options in the new Catalog
Store to enable 15.1 features and removes preexisting options eliminated for
version 15.1. For lists of these options and features, see the New Features
Guide.

Note Unlike previous versions, Sybase IQ 15.1 preserves previous settings of

database options and reapplies them after you create the new Sybase IQ 15.1
database. You no longer need to run SELECT * from SYS.SYSOPTIONS
before upgrading.

In Sybase IQ 15.1, all user data should reside in a user dbspace comprised of
one or more files. Migration converts main dbspaces into files under one user
dbspace, IQ_MAIN, for the IQ main store, and temporary dbspaces into files
under a single temporary dbspace, IQ_SYSTEM_TEMP, for a single IQ
Temporary Store. Existing Catalog Store dbspaces remain as dbspaces with a
single file. All of the old main dbspaces become files in the new iq_main user
main dbspace. Migration sets the option PUBLIC.default_dbspace to the value
“iq_main.”
The logical names for files created from converted dbspaces are the dbspace
name followed by an underscore and the file ID. For example, a main dbspace
with file ID 16384 becomes IQ_SYSTEM_MAIN_16384.

48 Sybase IQ
 CHAPTER 6 Migrating Data

For details on creating new dbspaces after migration and how to move objects
from one dbspace to another, see “SQL syntax for dbspace management and
partitioning”, in Chapter 1, “New Features in Sybase IQ 15.0,” in the New
Features Guide.
Migration creates a new system file for the IQ_SYSTEM_MAIN dbspace that
contains no tables. By default the name of this file is new_main_store.iq, but
you can use the ms_filename argument to specify another filename. The
iqunload utility computes the size of the new IQ_SYSTEM_MAIN based on
the size of your existing database.
If you accept the default settings for iqunload -au -c, then the new store marked
as ‘MAIN’ has DBSpaceName = ‘IQ_SYSTEM_MAIN’, DBFileName =
‘IQ_SYSTEM_MAIN’ and path = ‘new_main_store.iq.’ For MPX migration,
the location of the new main store must be visible to all nodes on the multiplex,
and the -ms_filename argument is required to specify the path instead of the
default value of new_main_store.iq.
When you migrate a database, you may specify which file to use for the new
IQ_SYSTEM_MAIN dbspace, its name, whether or not to use a raw device,
and the size of the main store and its reserve. See “Understanding iqunload”
on page 51 for iqunload parameters that determine these specifications and their
defaults. For main store size guidelines, see the New Features Guide.
Examples Example 1 Schema unloading allows you to verify schema correctness and
approximates how long migration may take.
For example:
• Make sure that you have copied the required scripts to your IQ 12.x server.
See “Correcting invalid SQL syntax” on page 63 for more information.
• Run iqunload -n to create the empty schema. This creates a SQL file with
the entire schema called reload.sql in the current directory. The reload.sql
file also contains a template CREATE DATABASE command that is
commented out.

Note The generated reload.sql will not contain any checkpoints. If you
have a very large schema, you may wish to edit the reload.sql and add a
few checkpoints now and then. If you do not, then IQ will end up with a
lot of object metadata objects requiring lots of (-iqmc) main cache memory.

• Using Interactive SQL or Sybase Central, create a new Sybase IQ 15.1

database with IQ SIZE and TEMPORARY SIZE clauses to create an
IQ_SYSTEM_MAIN of 10 GB and IQ_SYSTEM_TEMP of 5 GB.

Installation and Configuration Guide 49

Migration utilities

For example:
CREATE DATABASE 'test.db'
IQ PATH 'test.iq'
IQ SIZE 10240
TEMPORARY PATH 'test.iqtmp'
TEMPORARY SIZE 5120
• Start the new database, connect to it, and execute the reload.sql file
generated by iqunload -n against the new database. The execution time
roughly approximates the actual time to allow for database migration,
excluding validation checks.
Example 2 You can specify the IQ_SYSTEM_MAIN size in the database
migration command. The -ms_size parameter requires a value in MB, not GB.
Omit -ms_size and -ms_reserve if specifying a raw device. For a raw device,
you must specify an unused raw partition.
For example, this statement creates an IQ_SYSTEM_MAIN on a raw device:
iqunload -au -ms_filename \\\\.\\PhysicalDrive1 -c
"UID=DBA;PWD=SQL;DBF=latest.db"
Example 3 In CREATE DATABASE syntax, size units are in MB, not GB. The
following statement creates a database with 100 GB IQ_SYSTEM_MAIN
with 100 GB reserve:
CREATE DATABASE 'test.db'
IQ PATH 'test.iq'
IQ SIZE 102400
IQ RESERVE 102400
TEMPORARY PATH 'test.iqtmp'
TEMPORARY SIZE 5120

Files before and after migration

Assume that prior to migration, the directory W:\iq-i5\unload\127\db\*
contains these files:
• iq127db.db
• iq127db.iq
• iq127db.iqmsg
• iq127db.iqtmp
• iq127db.log

50 Sybase IQ
 CHAPTER 6 Migrating Data

After migration, the directory W:\iq-15\unload\127\db\* contains the

following:
• iq127db.db – the new IQ catalog store
• iq127db.db.before_schema_reload – the original 12.6 or 12.7 database. If
you need to go back to Sybase IQ 12.6 or 12.7, and you have not started
Sybase IQ 15.1 in writeable mode, you may copy this file to the original
catalog store name (iq127db.db in this example).
• iq127db.iq – the original IQ main store. The file and its data are unchanged
during migration. Starting Sybase IQ 15.1 in writeable mode flags this file
as upgraded, after which it cannot be used in previous versions.
• iq127db.iqmsg.before_schema_reload – the original 12.6 or 12.7 message
file. This is left intact in its pre-migration state in case you need messages
issued during migration while using the 12.7 unload utility embedded in
Sybase IQ 15.1.
• iq127db.iqtmp – the Sybase IQ 15.1 temporary store.
• iq127db.lmp – the Sybase IQ 15.1 license manager property file.
• iq127db.db.out – output log file.
• new_main_store.iq– the new Sybase IQ 15.1 IQ_SYSTEM_MAIN.
In addition to the files listed, any additional SA catalog stores would also be
renamed to have the .before_schema_reload extension and new versions
created.

Understanding iqunload
iqunload is a command line utility. Refer to this section for information about
syntax, parameters, usage, examples, and permissions.
Syntax iqunload [ options ]
data:[ environment variable | file ]
Parameters The iqunload utility takes one or more parameters.
Table 6-1: iqunload parameters
Option Description
-ap <size> (Optional) Set page size for the new catalog store.
-au (Required, except when specifying -n) Migrate the
database.
You can specify-au or-n as an argument, but not both.

Installation and Configuration Guide 51

Migration utilities

Option Description
-c “keyword=value;...” (Required) Supply database connection parameters. You
must specify a DBF parameter to specify the name of the
database file for migration. The file path is either absolute
or relative to the server startup directory.
-dc (Optional) Recalculate computed columns in the
database.
-ms_filename Specify filename for new empty IQ_SYSTEM_MAIN
store created during database migration. If not specified,
the default new main store will be a file system file called
new_main_store.iq.
-ms_filename is optional for a simplex migration, but is
required for a multiplex migration
-ms_reserve (Optional) Size of new IQ_SYSTEM_MAIN reserve in
MB. If unspecified, defaults to zero.
-ms_size (Optional) Size of new IQ_SYSTEM_MAIN store in
MB, computed by Sybase IQ based on the database size.
The minimum, assuming a default page size, is 200MB.
If the user specifies –ms_size value smaller than the
computed value, IQ uses the computed value; otherwise
the user–specified value is used.
-n (Optional, except for schema unload.) Unload schema
definition only. You can specify-au or-n as an argument,
but not both.

Note This argument is not supported for Sybase IQ 12.6.

You must use Sybase IQ 12.7 ESD 5 or later to use this
option.

-new_startline (Optional) Specify startup switches for the new Sybase

IQ 15.1 server that is the migration target. For a complete
list of server startup switches, see the Utility Guide.
-o <file> (Optional) Log output messages to file.
-q (Optional) Run quietly. Suppress messages and windows.
-r <file> (Optional) Specify name of generated the reload.sql
command file.
-t <list> (Optional) Output listed tables only. Can specify
OwnerName.TableName or TableName alone.
-v (Optional) Return verbose messages.
-y (Optional) Replace existing reload schema SQL script
with new output without confirmation.

52 Sybase IQ
 CHAPTER 6 Migrating Data

Examples Example 1 Migrate a simplex database to 15.x server:

iqunload –au –c
“UID=DBA;PWD=SQL;DBF=W:\\mydevice\\test_dir\\test2.db”
Example 2 Unload schema from database and rename the reload.sql file to
test2_reload.sql :

iqunload –n -c
“UID=DBA;PWD=SQL;DBF=D:\\test_dir\\test2\\test2.db;
ENG=myserver_test2” –r
“D:\test\unload_dir\test2_reload.sql”
Example 3 Migrate database test3.db. The START connection parameter
specifies switches for starting the database being reloaded. The –new_startline
parameter specifies switches for starting the utility_db to create the new
catalog store.
iqunload –au -c “
UID=DBA;PWD=SQL;DBF=D:\\test\\test3\\test3.db;START=–
ch 128M –iqmc 50" –new_startline "–ch 256M –iqtc 400"

Note Do not include -iqnotemp XYZ in the new start line or else migration will
fail. As part of the migration process, temp files will be added to
IQ_SYSTEM_TEMP. If the server is started with iqnotemp then the iqunload
will NOT be able to add these temp files.

Example 4 Migrate the database iq_demo.db using a raw device for a new
IQ_SYSTEM_MAIN store.
Syntax example if you have a second physical drive 2:
iqunload –au –c
"UID=DBA;PWD=SQL;DBF=asiqdemo.db" -ms_filename
\\\\.\\PhysicalDrive2
Syntax example if you have a logical partition K:
iqunload –au –c
"UID=DBA;PWD=SQL;DBF=asiqdemo.db" -ms_filename
\\\\.\\K:
You may optionally specify the size and reserve size for the
IQ_SYSTEM_MAIN store, for example:
–ms_size 10000 –ms_reserve 1000
Example 5 Migrate a database and specify startup parameters using a
configuration file.

Installation and Configuration Guide 53

Migration utilities

iqunload –au –c
"UID=DBA;PWD=SQL;DBF=asiqdemo.db;[email protected]"
Note that the user ID and password must be those for the old database. (The
default password for 12.6 and 12.7 was upper case “SQL.”)
Usage The specified user ID must have DBA authority.
For schema unloads, the iqunload utility requires the following minimum
server versions:
• Sybase IQ version 12.6 ESD #11.
• Sybase IQ version 12.7 ESD #5.
For schema unload, start your existing 12.6 or 12.7 server and specify the -n
parameter on the iqunload command. Schema unload creates schema load
scripts and output files in the current directory.
When migrating a database, specify -au parameter.
Determining switches for migration The iqunload utility starts and
communicates with a special IQ 12.7 server and the Sybase IQ 15.1 server.
This section documents the default switches sent to these servers to help you
understand the cache settings. You can use this information to determine if your
existing IQ 12.7 / 12.6 server requires switches to be set during migration.
For most cases, you can skip to “Results of iqunload” on page 55.
The -au parameter causes the utility to start two servers:
• iqunlspt – A special unload engine based on Sybase IQ 12.7 ESD 5.

• iqsrv15 – The new Sybase IQ 15.1 server.

Note Make sure that your server starts cleanly in IQ 12.6 or 12.7 to minimize
startup times.

iqunlspt starts on your Sybase IQ 12.6 or 12.7 database with the following
command line arguments:
iqunlspt.exe -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.

54 Sybase IQ
 CHAPTER 6 Migrating Data

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 IQ queries or multiple concurrent users. Note that the time required to
start your existing Sybase IQ 12.6 or 12.7 database will also be required to start
the iqunlspt.exe process. This time is included in the startup time for the
iqunload.exe.
iqsrv15 starts with the following 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 IQ 15.1 engine to execute many schema
DDL statements.
Both of the server start commands above 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 docs
below).
The iqunload utility generates script and output files in
Results of iqunload
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.
If desired, 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. For details about -ch and –cl, 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. For example, this might occur if tables
involved in a view were 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.

Installation and Configuration Guide 55

Migration utilities

The iqunload utility automatically starts the old version of the server (12.6 or
12.7) in order 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, 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 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 cache size.
Logging and Extra logging To start the Sybase IQ 15.1 server with extra logging, use the
correcting errors -new_startline parameter on the iqunload command to specify diagnostic
parameters -z and -zr all.
For example:
iqunload -au -c "UID=DBA;PWD=SQL;DBF=W:\\iq-
15\\unload\\127\\db\\iq127db.db" -new_startline "-z -zr
all" -o d:\\iq15db.out
This statement causes the new iqsrv15 database engine to produce more
verbose logging output to the file d:\iq15db.out.
For details about the -z diagnostic parameter, see the Utility Guide. For
information about request logging (-zr), which has been updated for 15.1, see
“Request logging” in SQL Anywhere Server – SQL Usage > Monitoring and
Improving Database Performance > Improving database performance > Other
diagnostic tools and techniques.
To start the bundled Sybase IQ 12.7 engine with extra logging, use the START=
connection property to specify the -z and -zr all parameters. For example:
iqunload -v -au -c "UID=DBA;PWD=SQL;DBF=W:\\iq-
15\\unload\\127\\db\\iq127db.db;START=-z -zr all -o
d:\\iq127db.out"
This statement causes the bundled Sybase IQ 12.7 engine to produce more
verbose logging output to the file d:\iq127db.out.
Examine the output file iq15db.out or iq127db.out for server error messages.
Cannot start database If the iqunload utility cannot start a database, it
returns an error and echoes the command line so that you can correct errors.
Server not found If you see a message like the following, iqunload started
the database but could not connect:
SQL error:Database server not found

56 Sybase IQ
 CHAPTER 6 Migrating Data

Check to see if an iqunlspt process is running, and stop the process before
retrying iqunload.
Open Task Manager and click the Processes tab. Locate the image name
iqunlspt. Right-click iqunlspt and choose End Process.
If you try to run iqunload without killing the orphaned iqunlspt process, you
may see the following error:
SQL error: Unable to start specified database:
autostarting database failed.
Obsolete stored procedures logged Migration replaces 12.7 login
procedures to support new Sybase IQ 15.1 login management functionality.
The procedure sp_login_environment replaces the 12.7 default login procedure
DBA.sp_iq_process_login and the post-login procedure
dbo.sa_post_login_procedure replaces 12.7 default post-login procedure
DBA.sp_iq_process_post_login. The iqunload utility generally replaces obsolete
options with their new defaults, but if the 12.7 option is set on a specific user
instead of PUBLIC (the default), the log file may report errors like the
following:
E. 10/31 16:53:40. Login procedure
'DBA.sp_iq_process_login' caused SQLSTATE '52W09'
E. 10/31 16:53:40. Procedure 'sp_iq_process_login' not
found

Note See Managing login policies overview at

http://dcx.sybase.com/index.php#https%3A%2F%2Ffanyv88.com%3A443%2Fhttp%2Fdcx.sybase.com%2F1100en
%2Fdbadmin_en11%2Fda-permissi-s-4686947.html. for an overview of login
management functionality.

Working with large schemas

With large schemas, the default cache settings may be too small and the Sybase
IQ 15.1 server could exhaust dynamic memory. To increase the 15.1 server's
cache memory, use the -c server switch. Use the -new_startline to pass this
switch to the 15.1 server.
A diagnostic example would include the following switches:
-ca 1
-c 1000m

Installation and Configuration Guide 57

Migration utilities

-o d:\iq15console.out

Note The value shown for -c is arbitrary. You should set switches
appropriately for your system. The value for -c is in bytes. To specify
megabytes, use the m suffix, as shown.

The switches in the example perform as follows:

• ca 1 – Enables dynamic catalog cache sizing. This will also cause memory
cache statistics to be logged to the console.
• c 1000m – Sets initial catalog cache at 1GB.
• -o d:\iq15console.out – Specifies the log file for console output.
Now you can load d:\iqconsole.out into your editor and examine the log
entries. You can watch how the catalog store adjusts the cache and determine
if the settings of 1000m and 2000m are appropriate.

Working with extremely large schemas

Generating a reload schema (iqunload -n) places the entire schema in a single
reload.sql file. In extreme cases, you may need to break a very large reload.sql
file into pieces that can be executed sequentially. This will also help the server
manage the cache.
If the migration fails (iqunload -au) with dynamic memory exhausted and you
have set cache settings as high as your hardware and operating system
limitations allow, please contact Sybase for assistance.

Sybase 12.7 Local Store Unload utility (iqlsunload)

Sybase IQ 15.1 does not support local stores. Multiple nodes can now write to
the main store. This new functionality replaces the local stores functionality.
iqlsunload is a utility that you can use to unload the contents of an IQ 12.7 local
store, and unload schema and data from user tables in an IQ 12.7 local store.
iqlsunload is included with all versions of Sybase IQ starting with 12.7 ESD5.
For Sybase IQ 15.1, you can find this utility in the %IQDIR151%\lsunload
directory.

58 Sybase IQ
 CHAPTER 6 Migrating Data

Running iqlsunload
iqlsunload is a command line utility. Refer to this section for information about
syntax, parameters, usage, examples, and permissions.
Syntax iqlsunload [ options ] directory [ @data ]

data:[ environment variable | file

Parameters directory is a required parameter that contains a path relative to the database
on the database server, not relative to the path where iqlsunload is executed.
This specification is required to generate extract_data.sql. The directory must
exist. The unload on the server side will not create it. The iqlsunload utility
unloads the actual data files to this target directory when you use Interactive
SQL to run extract_data.sql. For example, extract_data.stql references the
directory as follows:
CREATE VARIABLE @extract_directory varchar(2048);
SET @extract_directory = '
'C:\\testIQ15\\database\\IQ127_beta2_mpx_test\\demo_r1
\';
SET TEMPORARY OPTION temp_extract_directory =
'C:\\testIQ15\database\\IQ127_beta2_mpx_test\\demo_r1\
';
The iqlsunload application takes one or more optional parameters. Use the
appropriate parameters for desired behavior; you cannot perform both
functions in the same command.
Table 6-2: iqlsunload command line switches
Parameter Description
-al Unload IQ local store schema and data. (Cannot be
specified with -t)
-c “keyword=value;...” Supply database connection parameters
-h Print out the syntax (help) for the utility.
-o <file> Log output messages, including errors, to file.
-q Run quietly. Suppress messages and windows.
-r <directory> Specify the directory where SQL scripts are generated.
The default reload command file is reload.sqlin the
current directory. The directory is relative to the current
directory of the client application, not the server.
-t <list> Output listed tables only. Can specify
OwnerName.TableName or TableName alone. (Cannot
be specified with -al).
-v Output verbose messages.

Installation and Configuration Guide 59

Migration utilities

Parameter Description
-y Replace existing reload schema SQL script without
confirmation.

Usage The iqlsunload utility requires a minimum server version of Sybase IQ 12.7
ESD #5.
The database must be running before you run iqlsunload.
The specified directory is a path relative to the database on the database server,
not relative to the path where iqlsunload is executed.
The iqlsunload tool connects to the database using connection parameters -c in
a way which is consistent with other tools like dbping and dbisql as described
in the Sybase IQ Utility Guide.
On Windows, you must specify double instead of single slashes in all path and
file names.
You must run the iqlsunload tool from within the %IQDIR15%\lsunload
directory so that it picks up updated libraries before resolving any IQ 12.7
libraries.
Objects unloaded Unloading the local store does not unload database
objects that are not part of the local store.
The -al parameter unloads the following persistent objects:
• Base tables
• Global temporary tables
• Indexes
• Domains (user-defined data types)
• Constraints (column check constraint, table constraint, primary key,
foreign key, unique, default, IQ unique, not null)
• Views
• Stored procedures and functions
• Messages
• Remote servers and external logins
• Events
Sybase IQ 15.1 no longer allows users with empty user names. Users of this
type could formerly be created using statements like:

60 Sybase IQ
 CHAPTER 6 Migrating Data

GRANT CONNECT TO ““ IDENTIFIED BY 'sql'

Users with empty user names cannot be dropped with the 12.6 or 12.7 server
and cannot be migrated. The schema reload operation warns that an empty user
name was encountered and the user will not be recreated. The reload operation
ignores such users and any associated objects.
When unloading tables, note that:
• Join indexes, which do not exist in a local store, are only unloaded when
the user specifies unloading schema and data for a list of tables (-t). All
tables involved in the index must be specified with the -t parameter.
• When extracting table schema and data only, be sure that the collation of
the database you run the reload script against matches the collation of the
database specified on the initial iqlsunload command.
• If you do not qualify table names with owner names, iqlsunload extracts
table data from all tables with that table name.
The iqlsunload utility ignores any system tables or nonexistent tables specified.
Examples Example Unload local stores from a database called mpxtest2, extracting
any table data to the directory W:\\mydevice\\test_dir\\unload_dir:
iqlsunload -o iqunload_624.out -al -c
“UID=DBA;PWD=SQL;ENG=myserver_mpxtest02”
W:\\mydevice\\test_dir\\unload_dir
The preceding command creates three scripts in the current directory:
• reload_schema.sql – Recreates schema for unloaded objects (either
objects from local store or tables selected by the user.) This script is
executed against a node that will write to the multiplex. This node could
either be the existing writer node or a writer or coordinator for the
multiplex after migration, depending on where you plan to recreate the
schema.
• extract_data.sql – Extracts table data for the unloaded tables from the
local store. Execute this script in Interactive SQL while connected to the
query node from which it was generated. When this script executes, it
generates the data files into the directory data. This script’s contents follow
the guidelines set out in Chapter 7, “Moving Data In and Out of
Databases,” in the System Administration Guide.
• reload_data.sql – Loads extracted table data. This script is executed on the
node where you ran reload_schema.sql and will reload the data extracted
from the extract_data.sql file.

Installation and Configuration Guide 61

Avoiding potential migration problems

Permissions You must have DBA authority to run this utility.

Avoiding potential migration problems

Sybase IQ 15.1 no longer supports some 12.x features and objects. You must
correct these items before you migrate your databases. “Addressing
unsupported objects” on page 62 tells you how to identify and update
unsupported objects and metadata. “Correcting invalid SQL syntax” on page
63 identifies syntax changes you must make before migration.

Addressing unsupported objects

Running iqunload in schema unload mode (iqunload -n) against an existing 12.x
server generates a reload.sql script that contains the entire schema for a 12.x
database. You can compare the contents of this script against the following
table to identify unsupported objects and metadata.
Table 6-3: Troubleshooting unsupported metadata
Object Details Action
Invalid database, Table names can no longer contain double Change these names
table, or user names quote characters.
User names and database names can no longer
contain double quote characters, single quote,
and semicolon characters.User names and
database names may no longer start with a
space or end with a space.
Join indexes The iqunload utility will not run if the Use Sybase Central to view the join
database to be migrated contains join indexes. index definitions. Copy them to a
file. Drop join indexes before
migrating data. After migrating
data, recreate the join indexes.
Database with The iqunload utility searches BLANK Drop these indexes and constraints
BLANK PADDING PADDING OFF databases for any indexes that before schema reload and recreate
OFF would become invalid after migration. The the indexes and constraints after
iqunload utility fails and lists indexes and schema reload has been completed.
constraints that must be dropped and in which
order.
Unenforced The iqunload utility tool fails and lists Drop unenforced constraints before
constraints unenforced constraints that must be dropped. proceeding with migration.

62 Sybase IQ
 CHAPTER 6 Migrating Data

Object Details Action

Old 1–byte FP or old Databases created with IQ 12.4.2 or below Allow iqunload to check for these
2–byte FP indexes may have these indexes. Because these and list them. Rebuild these indexes
indexes were automatically created by Sybase using sp_iqrebuildindex before
IQ, you cannot drop and recreate them; you migration. For details about
need to rebuild them. rebuilding indexes, see
“Configuring FP(3) indexes” in the
New Features Guide. The rebuilt
indexes will be upgraded.

Correcting invalid SQL syntax

See the following table for steps to address elements that cause iqunload
failures.
Table 6-4: Troubleshooting schema issues
Problem Solution
A DECLARE LOCAL TEMPORARY TABLE statement in Remove the owner name.
a procedure or trigger causes a syntax error if the table
name is prefixed with an owner name.
If a CREATE TRIGGER statement does not include an Prefix the table name with the owner name.
owner name for the table on which the trigger is
defined, and the table must be qualified with an owner
when referenced by the user executing the reload.sql
file, the statement fails with a “Table ‘table–name’ not
found” error.
If an object name (such as a table, column, variable or Change all references to the reserved word to use
parameter name) corresponds to a reserved word a different name. For variable names, prefixing
introduced in a later version of Sybase IQ or SQL the name with @ is a common convention that
Anywhere (such as NCHAR), then the reload fails. prevents naming conflicts.
(For reserved words, see the Reference Manual and
SQL Anywhere Server SQL Reference.) For example:
CREATE PROCEDURE p( )
BEGIN
DECLARE NCHAR INT;
SET NCHAR = 1;
END

Installation and Configuration Guide 63

Avoiding potential migration problems

Problem Solution
Views that use Transact–SQL™ outer joins (by Add the following line to the reload script:
specifying *= or =*) may not be created properly SET TEMPORARY OPTION
when they are reloaded. tsql_outer_joins='on'
and also set this option for your database.
You should later rewrite any views or Stored
Procedures that use Transact–SQL outer joins.
Stored procedures that use Transact–SQL outer joins Rewrite views and stored procedures.
may not work correctly.
Functions that have OUT or INOUT parameters cannot OUT and INOUT parameters are no longer
be reloaded. supported. The functions must be dropped before
doing a reload.

Note If the examples in the above two tables do not apply to you, skip the next
section, and proceed directly to either “Migrating simplex databases” on page
66 or “Migrating multiplex databases” on page 70.

64 Sybase IQ
 CHAPTER 6 Migrating Data

❖ Correcting invalid SQL

Sybase recommends this procedure to avoid the SQL syntax problems that
cause failures.
1 Copy the following scripts from %IQDIR15%\unload to
%ASDIR%\scripts
• unloadold.sql
• unload.sql
• optdeflt.sql
• opttemp.sql
2 Use your 12.x server to start the database you want to migrate.
3 Use the iqunload utility to run a schema unload. For example:
iqunload –n –c
"UID=DBA;PWD=SQL;ENG=my_eng;DBN=my_dbname".
The schema unload produces a reload.sql script that contains the schema
for the database being migrated in the directory from which you ran the
unload.
As an aid to users, the generated reload.sql file contains a sample CREATE
DATABASE statement, for example:

-- CREATE DATABASE command: CREATE DATABASE 'W:\\iq-

15\\unload\\127\\db\\iq127db.db' LOG ON 'W:\\iq-
15\\unload\\127\\db\\iq127db.log' CASE IGNORE
ACCENT IGNORE PAGE SIZE 4096 COLLATION 'ISO_BINENG'
BLANK PADDING ON JCONNECT OFF CHECKSUM OFF IQ PATH
'iq127db.iq' IQ SIZE 50 TEMPORARY PATH
'iq127db.iqtmp' TEMPORARY SIZE 25 MESSAGE PATH
'iq127db.iqmsg' IQ PAGE SIZE 131072 BLOCK SIZE 8192
Running the reload.sql script does not execute the sample statement, but
you can use this generated statement as a template when you create your
database with Sybase IQ 15.1. If you want to create a completely new
Sybase IQ database, see Chapter 1, “New Features in Sybase IQ 15.x,” in
the New Features Guide for sizing guidelines.
4 Start the utility database using the Sybase IQ 15.1 Server, and create a new,
empty, Sybase IQ 15.1 database.

Installation and Configuration Guide 65

Migrating simplex databases

5 Use Interactive SQL to run the reload.sql script that contains the unloaded
schema against the new Sybase IQ 15.1 database. This loads the schema
of the old database into an Sybase IQ 15.1 database. If there are any SQL
syntax errors, you will receive warnings when running the SQL script.
Ignore the errors found in order to get a complete list of the problems.
Modify the database to be migrated to eliminate the errors found. See
“Correcting invalid SQL syntax” on page 63 to determine how to fix the
problems.
6 Perform this process iteratively if necessary until you can cleanly reload
the schema unloaded from the database to be migrated, against the empty
15.1 database.

Migrating simplex databases

Follow this workflow to migrate simplex databases. Review the task summary
and perform all steps in sequence.

Task summary
• Review “Upgrading from a previous version” on page 44 for steps
common to all database migrations.
• Run sp_iqcheckdb to check the validity of your current databases. Repair
any index and allocation problems. See “Verify your databases” on page
67 for more information.
• Shutdown your 12.x servers. See “Shutdown your 12.x server” on page 67
for more information.
• Run iqunload with the appropriate parameters to migrate your databases.
See “Migrate your simplex database” on page 68 for more information.
• Start the migrated database in readonly mode. Update the appropriate
configuration settings and database options. See “Start the 15.1 migrated
database” on page 69 for more information.
• Use sp_iqcheckdb to verify the migrated database. See“Verify the
migrated databases” on page 69 for more information.
• Complete any necessary post-migration tasks. See “Post-migration tasks”
on page 87 for more information.

66 Sybase IQ
 CHAPTER 6 Migrating Data

Verify your databases

Run the 12.x version of sp_iqcheckdb to check the validity of your current
databases. Make sure that the database is in a valid state and can start without
requiring recovery.
The 12.x versions of sp_iqcheckdb use input parameters, rather than database
options, to specify the type of database consistency checking.

❖ Running sp_iqcheckdb
1 Start version 12.6 or 12.7 and connect to your database.
2 Issue a CHECKPOINT command.
3 Run sp_iqcheckdb in verify mode.
sp_iqcheckdb 'verify database'
If you run the procedure from Interactive SQL, redirect output to a file by
typing the following:
sp_iqcheckdb 'verify database' >& filename
4 Issue a COMMIT statement.
Examine the sp_iqcheckdb report for errors. Repair any index and
allocation problems.

Note For information on interpreting the sp_iqcheckdb results and corrective

action, refer to Chapter 13, “System Recovery and Database Repair,” in System
Administration Guide: Volume 1. If you need to contact Sybase Technical
Support, you must provide the output from sp_iqcheckdb.

Shutdown your 12.x server

At the command prompt, issue a stop_asiq command to shutdown your 12.x
server. You can also stop a server by using the STOP ENGINE command from
Interactive SQL or any front–end client.

Installation and Configuration Guide 67

Migrating simplex databases

Migrate your simplex database

Make sure that the database file is not in use, and run the iqunload utility with
the -au (migrate database) and -c (connection parameters) to migrate the
database. See “Sybase IQ 15.1 Unload utility (iqunload)” on page 47 for
additional options.
For example, this command migrates the simplex database mytest and saves
ouput in unload.out in the current directory:
iqunload -au -c "uid=DBA;pwd=SQL;dbf=d:\\mytest" -o
unload.out
The database and the iqunload utility must be on the same machine to migrate
the database, or iqunload returns an error. The -o is an optional switch. that
sends a copy of the console output to the specified log file, here named
unload.out.
Because the example specified DBF=mytest.db, the iqunload utility attempts
to connect to this database in the current directory. You could also specify the
full path to the database, as shown in the following example:
iqunload -au -c "dbf=W:\\iq-
15\\unload\\iq127db.db;uid=DBA;pwd=SQL"

Output:
Sybase IQ Unload Utility Version 15.0.0.5120
Connecting and initializing
Unloading user and group definitions
Unloading table definitions
Unloading index definitions
Unloading functions
Unloading view definitions
Unloading procedures
Unloading triggers
Unloading SQL Remote definitions
Creating new database
Creating indexes for (1/14)
"DBA"."sales_order"
Creating indexes for(2/14)
"DBA"."sales_order_items"
Creating indexes for (3/14) "DBA"."contact"
Creating indexes for (4/14) "DBA"."customer"
Creating indexes for (5/14) "DBA"."fin_code"
Creating indexes for (6/14) "DBA"."fin_data"
Creating indexes for (7/14) "DBA"."product"
Creating indexes for (8/14) "DBA"."department"
Creating indexes for (9/14) "DBA"."employee"

68 Sybase IQ
 CHAPTER 6 Migrating Data

Creating indexes for (10/14)"DBA"."alt_sales_order"

Creating indexes for (11/14)
"DBA"."alt_sales_order_items"
Creating indexes for (12/14) "DBA"."iq_dummy"
Creating indexes for (13/14) "DBA"."emp1"
Creating indexes for (14/14) "DBA"."sale"
Successfully backed up file
"W:\iq-15\unload\iq127db.db"
by renaming it to
"W:\iq-15\unload\iq127db.db.before_schema_reload".
Successfully backed up file "W:\iq-
15\unload\iq127db.iqmsg" by renaming it to
"W:\iq-15\unload\iq127db.iqmsg.before_schema_reload"
Successfully reloaded schema of database
"W:\iq-15\unload\iq127db.db".

Start the 15.1 migrated database

Use this command to start the migrated database in readonly mode with Sybase
IQ 15.1:
start_iq -iqro 1
Update the appropriate configuration settings and database options. the
database. See the New Features Guide and Release Bulletin for changes to
legacy features and options.

Verify the migrated databases

Run sp_iqcheckdb to verify the consistency of the databases.

Note In this step, you run the IQ 15.1 version of sp_iqcheckdb, which uses
input parameters, rather than database options, to specify the type of database
consistency checking.

❖ Running sp_iqcheckdb
1 Start the database using the read-only switch, -iqro 1.
When starting the coordinator in 15.1, use the same port used by the 12.6
or 12.7 writer server.
2 Issue a CHECKPOINT command.

Installation and Configuration Guide 69

Migrating multiplex databases

3 Run sp_iqcheckdb in verify mode.

sp_iqcheckdb ('verify database')
If you run the procedure from Interactive SQL, redirect output to a file by
typing the following:
dbisql -c "..." "sp_iqcheckdb ('verify database')"
>& filename
where “...” represents startup parameters for your database.
4 Issue a COMMIT statement.

Note For information on interpreting the sp_iqcheckdb results and corrective

action, refer to Chapter 13, “System Recovery and Database Repair,” in System
Administration Guide: Volume 1. If you need to contact Sybase Technical
Support, you must provide the output from sp_iqcheckdb.

Migrating multiplex databases

Follow this workflow to migrate multiplex databases. Review the task
summary and perform all steps in sequence.

Task summary
• Review “Upgrading from a previous version” on page 44 for steps
common to all database migrations.
• Synchronize and shutdown multiplex all query nodes. See “Synchronize
and shutdown multiplex query nodes” on page 71 for more information.
• Migrate local stores, if necessary. This step is only required if you created
local stores for your 12.x multiplex query nodes. See “Migrate your local
stores” on page 73 for more information.
• Run sp_iqcheckdb to check the validity of your 12.x databases. Repair any
index and allocation problems. See “Verify the 12.x databases before
migration” on page 79 for more information.

70 Sybase IQ
 CHAPTER 6 Migrating Data

• Start the multiplex write server in single node mode. See “Start the
multiplex write server in single node mode” on page 80 for more
information.
• Shutdown your 12.x server and backup your database. See “Shutdown
your 12.x server” on page 80 for more information.
• Run iqunload with the appropriate parameters to migrate your databases.
See “Use iqunload to migrate your database” on page 80 for more
information.
• Use the -iqro 1 -iqmpx_sn 1 switches to start the writer in READONLY
mode. See “Start the 15.1 migrated database” on page 83.
• Run sp_iqcheckdb to verify your migrated databases, then backup the
databases. See “Verify the migrated databases” on page 83 for more
information.
• Synchronize the secondary nodes from the coordinator node. See
“Manually synchronize the secondary nodes” on page 84 for more
information.
• Start the secondary nodes, then import the schema and data for the local
stores into the coordinator. See “Start the secondary nodes” on page 86 for
more information.
• Set the failover mode for the failover node. See “Set the failover node” on
page 86 for more information.
• Complete any necessary post-migration tasks. See “Post-migration tasks”
on page 87 for more information.

Synchronize and shutdown multiplex query nodes

When you migrate a multiplex, Sybase recommends that you check the SQL
Remote and multiplex server log files for synchronization problems.

❖ Correcting synchronization problems

1 Start the multiplex server.
2 Start SQL Remote on all nodes in the multiplex, if not already started.
These are normally started by Sybase Central when starting servers.

Installation and Configuration Guide 71

Migrating multiplex databases

3 Give the multiplex time to propagate any changes throughout the

multiplex. To do this, look at the write server console log file and check
that the events starting with 'ev_iqmpx' have successfully executed. Note:
the server console log file, by default, is created in %ASDIR%/logfiles.
For example:
Now accepting requests
OS Available: 933096K, Working Set: 83988K, Cache
Target: 11483K
OS Available: 860680K, Working Set: 83996K, Cache
Target: 11483K
Next time for 'ev_iqmpxq2w' is 2008/11/23
22:03:00.000
Next time for 'ev_iqmpxstatus' is 2008/11/23
22:03:00.000
OS Available: 859232K, Working Set: 84112K, Cache
Target: 11489K
OS Available: 861052K, Working Set: 84424K, Cache
Target: 11489K
OS Available: 860972K, Working Set: 84428K, Cache
Target: 11489K
OS Available: 850248K, Working Set: 85540K, Cache
Target: 11579K
OS Available: 850104K, Working Set: 85568K, Cache
Target: 11579K
Next time for 'ev_iqmpxq2w' is 2008/11/23
22:04:00.000
Next time for 'ev_iqmpxstatus' is 2008/11/23
22:04:00.000
OS Available: 850120K, Working Set: 85600K, Cache
Target: 11579K
Next time for 'ev_iqmpxq2w' is 2008/11/23
22:05:00.000
Next time for 'ev_iqmpxstatus' is 2008/11/23
22:05:00.000
OS Available: 852668K, Working Set: 85604K, Cache
Target: 11579K
4 Wait for SQL Remote to scan its log files a few times and view the logs.
To view these log files from Sybase Central, right-click the multiplex
server and select SQL Remote | View SQL Remote Log.
The console indicates that SQL Remote is hovering at the end of the active
log. Wait for the sleeping to stop to give SQL Remote a chance to process
any messages. SQL Remote will go back to sleep once it finishes
processing. For example:

72 Sybase IQ
 CHAPTER 6 Migrating Data

I. 11/23 22:06:10. Scanning logs starting at offset

0001787252
I. 11/23 22:06:10. Hovering at end of active log
5 Please shut down SQL Remote and multiplex servers. If you simply shut
down the multiplex servers, the SQL Remote servers will hover, then
detect that the multiplex servers are no longer running and shut themselves
down. By default, the SQL Remote servers should shut themselves down
within 60 seconds.
6 Shut down query servers in the multiplex. They are no longer required.
7 If the logs report no errors, verify the database. For details, see “Verify the
12.x databases before migration” on page 79.

Migrate your local stores

If you created local stores for your 12.x multiplex query nodes, you need to
move these stores before migrating data to Sybase IQ 15.1. The iqlsunload tool
connects to a Sybase IQ 12.7 database with an IQ Local Store and creates
scripts that unload its schema and data.
Local Store migration means consolidating node-specific information into
either the existing 12.7 Writer or the new Sybase IQ 15.1 Main Store. You can
customize the steps in the process to meet your data requirements.
If existing query nodes have node or department-specific information, you can
use tablespaces and partitioning to achieve the same results. For more
information, see Data storage in Chapter 3, “Multplex Overview,” in the New
Features Guide.
If information is duplicated across your query nodes, you may only need to
migrate a single query server's local store. The duplicated information on the
other query servers becomes redundant and can be ignored for multiplex
migration.
Query server data If the same table exists on multiple query nodes, and each node has its own
partitioning subset of the data, then you must manually edit the local store migration scripts.

❖ Partitioning query server data

For a department-specific employee table on each query server, you would
follow these basic steps:
1 Unload the schema and data from the query nodes.

Installation and Configuration Guide 73

Migrating multiplex databases

The reload_schema.sql script produced for each query node will contain
the same schema definition for employee.
2 Execute the reload_schema.sql from one of the query nodes against either
the existing 12.7 writer or the new Sybase IQ 15.1 main store.
3 Execute the reload_data.sql script from each of the query nodes against
the same server used in the previous step.
This procedure creates the employee table once but loads each of the query
node data sets.
Query server data If the same table exists on each query node with overlapping data sets, you
overlap must resolve the issue. You may edit the extract data files to ensure that the data
sets are unique, or you may decide to just rename the tables and then reload all
the unique tables.

❖ Addressing overlapping query server data

1 Run iqlsunload against all your query servers with local stores that have the
data you wish to consolidate.
2 Modify the reload_schema.sql and reload_data.sql files to have the new
table names. Leave the extract_data.sql file alone as if references the table
found in the query server's local store.
3 Run the extract_data.sql from each of the nodes.
The following example shows modifications to the iqlsunload output to carry
out Step 2.
Suppose that the reload_schema.sql script contains the following:
CREATE TABLE "DBA"."sales_order"

"id" unsigned int NOT NULL IQ UNIQUE (648),

"cust_id" unsigned int NOT NULL IQ UNIQUE
(111),
"order_date" "datetime" NOT NULL IQ UNIQUE
(376),
"fin_code_id" char(2) NULL IQ UNIQUE (1),
"region" char(7) NULL IQ UNIQUE (5),
"sales_rep" unsigned int NOT NULL IQ UNIQUE
(75),
PRIMARY KEY ("id"),
Edit the reload_schema.sql and change it as follows:
CREATE TABLE "DBA"."q1_sales_order"

74 Sybase IQ
 CHAPTER 6 Migrating Data

"id" unsigned int NOT NULL IQ UNIQUE (648),

"cust_id" unsigned int NOT NULL IQ UNIQUE
(111),
"order_date" "datetime" NOT NULL IQ UNIQUE
(376),
"fin_code_id" char(2) NULL IQ UNIQUE (1),
"region" char(7) NULL IQ UNIQUE (5),
"sales_rep" unsigned int NOT NULL IQ UNIQUE
(75),
PRIMARY KEY ("id"),
The extract_data.sql file contains the following:
--
-- Extract Table Data for table sales_order
-- NOTE: Approximately 57672 bytes of storage space.
-- will be required to extract the data for this table.
--
-- The following will unload the data for table
sales_order, row group 1, column group 1
SET TEMPORARY OPTION temp_extract_name1 =
'DBA_sales_order_1_1_DATA_1.inp';
SET TEMPORARY OPTION temp_extract_name2 =
'DBA_sales_order_1_1_DATA_2.inp';
SET TEMPORARY OPTION temp_extract_name3 =
'DBA_sales_order_1_1_DATA_3.inp';
SET TEMPORARY OPTION temp_extract_name4 =
'DBA_sales_order_1_1_DATA_4.inp';
SET TEMPORARY OPTION temp_extract_name5 =
'DBA_sales_order_1_1_DATA_5.inp';
SET TEMPORARY OPTION temp_extract_name6 =
'DBA_sales_order_1_1_DATA_6.inp';
SET TEMPORARY OPTION temp_extract_name7 =
'DBA_sales_order_1_1_DATA_7.inp';
SET TEMPORARY OPTION temp_extract_name8 =
'DBA_sales_order_1_1_DATA_8.inp';
;
SELECT id, cust_id, order_date,
IFNULL(fin_code_id, @null_string, fin_code_id),
IFNULL(region, @null_string, region), sales_rep
FROM "DBA"."sales_order"
WHERE rowid( "sales_order" ) >= 1
AND rowid( "sales_order" ) <= 648;
;
SET TEMPORARY OPTION temp_extract_name1 = '';
SET TEMPORARY OPTION temp_extract_name2 = '';

Installation and Configuration Guide 75

Migrating multiplex databases

SET TEMPORARY OPTION temp_extract_name3 = '';

SET TEMPORARY OPTION temp_extract_name4 = '';
SET TEMPORARY OPTION temp_extract_name5 = '';
SET TEMPORARY
Leave the previous extract_data.sql code unchanged in order to extract the
sales_order table from the query server.

Suppose that reload_data.sql contains the following:

-- Reload Table Data for table "sales_order"
-------------------------------------------------
ALTER TABLE "DBA"."sales_order" MODIFY cust_id NULL;
ALTER TABLE "DBA"."sales_order" MODIFY order_date NULL;
ALTER TABLE "DBA"."sales_order" MODIFY sales_rep NULL;

SET @max_row_id =
( SELECT MAX( rowid( "sales_order" ) )+1
FROM "DBA"."sales_order" );
SET @load_statement =
'LOAD TABLE "DBA"."sales_order"
(id, cust_id, order_date, fin_code_id NULL(
'''||@null_string||''' ) , region NULL(
'''||@null_string||''' ) , sales_rep)
FROM
'''||@extract_directory||'DBA_sales_order_1_1_DATA_1.
inp'',
'''||@extract_directory||'DBA_sales_order_1_1_DATA_2.
inp'',
'''||@extract_directory||'DBA_sales_order_1_1_DATA_3.
inp'',
'''||@extract_directory||'DBA_sales_order_1_1_DATA_4.
inp'',
'''||@extract_directory||'DBA_sales_order_1_1_DATA_5.
inp'',
'''||@extract_directory||'DBA_sales_order_1_1_DATA_6.
inp'',
'''||@extract_directory||'DBA_sales_order_1_1_DATA_7.
inp'',
'''||@extract_directory||'DBA_sales_order_1_1_DATA_8.
inp'' ROW DELIMITED BY ''\n'' QUOTES ON
ESCAPES OFF DEFAULTS OFF FORMAT ASCII
IGNORE CONSTRAINT ALL 0 START ROW ID
'||@max_row_id;
CALL IqExecuteCommand( @load_statement );
ALTER TABLE "DBA"."sales_order" MODIFY cust_id NOT
NULL;

76 Sybase IQ
 CHAPTER 6 Migrating Data

ALTER TABLE "DBA"."sales_order" MODIFY order_date NOT

NULL;
ALTER TABLE "DBA"."sales_order" MODIFY sales_rep NOT
NULL;
Change reload_data.sql to the following:
-- Reload Table Data for table
"q1_sales_order"
-------------------------------------------------
ALTER TABLE "DBA"."q1_sales_order" MODIFY cust_id NULL;
ALTER TABLE "DBA"."q1_sales_order" MODIFY order_date
NULL;
ALTER TABLE "DBA"."q1_sales_order" MODIFY sales_rep
NULL;

SET @max_row_id = ( SELECT MAX( rowid( "q1_sales_order"

) )+1 FROM "DBA"."q1_sales_order" );
SET @load_statement =
'LOAD TABLE "DBA"."q1_sales_order"
(id, cust_id, order_date, fin_code_id NULL(
'''||@null_string||''' ) , region NULL(
'''||@null_string||''' ) , sales_rep) FROM
'''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_
1.inp'',
'''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_
2.inp'',
'''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_
3.inp'',
'''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_
4.inp'',
'''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_
5.inp'',
'''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_
6.inp'',
'''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_
7.inp'',
'''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_
8.inp'' ROW DELIMITED BY ''\n'' QUOTES ON ESCAPES OFF
DEFAULTS OFF FORMAT ASCII IGNORE CONSTRAINT ALL 0
START ROW ID '||@max_row_id;
CALL IqExecuteCommand( @load_statement );ALTER TABLE
"DBA"."q1_sales_order" MODIFY cust_id NOT
NULL;
ALTER TABLE "DBA"."q1_sales_order" MODIFY order_date
NOT NULL;
ALTER TABLE "DBA"."q1_sales_order" MODIFY sales_rep NOT

Installation and Configuration Guide 77

Migrating multiplex databases

NULL;
The preceding example shows query server schema and data that require
intervention during migration. Your situation may vary, but you have complete
control of the content of the final reload_schema.sql and reload_data sql files.

❖ Moving local stores with iqlsunload

Follow these steps to unload the schema and data for local objects in the 12.7
IQ Local Store and move them to another node for migration.
1 If using an older version, you must upgrade to the minimum version
Sybase IQ 12.7 ESD #5 before local store migration.
2 The iqlsunload utility is installed with Sybase IQ 15.1 in the
%IQDIR15%\lsunload directory.
3 Run the 12.7 iqlsunload utility against each query server with a local store.
For syntax and examples, see “Sybase 12.7 Local Store Unload utility
(iqlsunload)” on page 58.
4 Edit the reload_schema.sql script as follows:
• Delete unwanted objects.
• Uncomment any objects that you want to reload that are commented
out in the reload_schema.sql script.
• Add commands to define any objects that you defined in
sp_mpxcfg_<servername> procedures.

5 Edit the extract_data.sql script to remove objects that you do not wish to
migrate. These objects are generally the same ones that you removed from
reload_schema.sql.
6 Use Interactive SQL to run extract_data.sql from your 12.7 local store.
You now have unloaded the schema and data for local objects in the 12.7
local store.
7 Run the reload_schema.sql and load_data.sql scripts against the 12.7
write server.

Note If you prefer, you may wait until the write server has been migrated
to 15.1 and run the reload_schema.sql and load_data.sql scripts against
the new 15.1 coordinator.

78 Sybase IQ
 CHAPTER 6 Migrating Data

Verify the 12.x databases before migration

Sybase recommends that you run sp_iqcheckdb to verify the consistency of
your 12.x databases before you migrate.

Note In this step, run the IQ 12.6 or 12.7 version of sp_iqcheckdb, depending
on the version from which you are migrating. These versions of sp_iqcheckdb
use input parameters, rather than database options, to specify the type of
database consistency checking.

❖ Running sp_iqcheckdb
1 Start version 12.6 or 12.7 and connect to your database.
2 Issue a CHECKPOINT command.
3 Run sp_iqcheckdb in verify mode.
sp_iqcheckdb 'verify database'
If you run the procedure from Interactive SQL, redirect output to a file by
typing the following:
sp_iqcheckdb 'verify database' >& filename
4 Issue a COMMIT statement.

Note For information on interpreting the sp_iqcheckdb results and corrective

action, refer to Chapter 13, “System Recovery and Database Repair,” in System
Administration Guide: Volume 1. If you need to contact Sybase Technical
Support, you must provide the output from sp_iqcheckdb.

Installation and Configuration Guide 79

Migrating multiplex databases

Start the multiplex write server in single node mode

To ensure a smooth multiplex migration, start the write server in single node
mode to clean internal state information. To do this, start the writer node in
single node mode, then shutdown, start up again normally, and shut down.
Start the writer node with the server arguments -gm 1 and -iqmpx_sn 1:
-gm 1 -iqmpx_sn 1
If you use administrative startup scripts, create a copy of the start_server.bat
script to start the write server you want to migrate.
Add the two single node startup arguments to change the preceding command
as follows in start_server_single_node.bat:
start_asiq -STARTDIR d:\work\iq-127\mpx\main
@d:\work\iq-127\mpx\main\params.cfg -n mpx_main -gm 1 -
iqmpx_sn 1 %readonly% %nomain% -x tcpip{port=62631}
d:\work\iq-127\mpx\main\main.db %dbkey%
There are now two .bat files, start_server.bat and start_server_single_node.bat
that you will use to put the server into a good state for migration:
1 Start the writer node with start_server_single_node.bat.
2 Shutdown the writer node.
3 Start the writer node with start_server.bat.
4 Shut down the writer node.

Shutdown your 12.x server

At the command prompt, issue a stop_asiq command to shutdown your 12.x
server. You can also stop a server by using the STOP ENGINE command from
Interactive SQL or any front–end client.

Use iqunload to migrate your database

Run iqunload with the appropriate parameters to migrate your databases.
Multiplex migration differs from Simplex migration and requires additional
parameters.

80 Sybase IQ
 CHAPTER 6 Migrating Data

Minimum required parameters for a multiplex writer are -au (migrate

database), -c (connection parameters), ENG= connection parameter and -
ms_filename. The ENG= value must match your existing server name used in
IQ 12.7 and the -ms_filename specifies the new main store for the migrated
writer. This path must be the same for all nodes in the muliplex. For
complete syntax, see “Sybase IQ 15.1 Unload utility (iqunload)” on page 47.
For multiplex, there are two differences in the way you will execute the
iqunload utility:

• You need to specify the engine name in the -c connection parameters. This
is the same name that your
<mpx_dir>\<writer_node>\start_server.bat<mpx_dir>/<writer_node>/
start_server script file uses to start the writer node. The iqunload utility
attempts to start the database server as simplex first. This start requires that
the name of the server match the naming conventions for the multiplex
nodes. Once the iqunload detects that the server is a multiplex node, it shuts
the node down and restarts it with the iqmpx_sn 1 option.
• The name of the new main store needs to be visible and accessible by all
nodes of the multiplex. This is important because main store filename
defaults to new_system_main.iq. This path is relative to the catalog
database file (.db). Later, when the15.1 multiplex is synchronized, the
catalog is replicated to the secondary nodes, formerly known as the query
nodes. If you leave the default value for the main store name unchanged,
the path remains new_system_main.iq and secondary nodes are unable to
find the shared main store.
For multiplex writers, required arguments are ENG=, DBF=, and -ms_filename:
• The ENG= argument specifies the multiplex main engine name. This is
because the iqunload utility attempts to start the database to determine if
the database is a simplex or multiplex database. If multiplex, then the
server name is enforced. If you are unsure of the servername, check the
administrative script start_server in the database directory.
• The DBF= argument must specify the actual path that you used to create
the multiplex. If you are unsure of this, look at the SYSIQFILE table in
your 12.7 server to verify the database path.
• The -ms_filename argument specifies the location of the new main store.
This path must be visible and accessible by all servers in the multiplex.
Make sure that you begin all paths supplied as values for the arguments DBF=
and -ms_filename with double backslashes.
For example:

Installation and Configuration Guide 81

Migrating multiplex databases

iqunload -au -c
"UID=DBA;PWD=SQL;DBF=d:\\marshall\\work\\iq-
127\\mpx\\main\\main.db;ENG=mpx_main" -ms_filename
d:\\marshall\\work\\iq-
127\\mpx\\main\\new_main_store.iq
Sybase IQ Unload Utility Version 15.0.0.5120
Connecting and initializing
2008-11-23 22:32:07 Unloading user and group
definitions
2008-11-23 22:32:08 Unloading table definitions
2008-11-23 22:32:09 Unloading index definitions
2008-11-23 22:32:09 Unloading functions
2008-11-23 22:32:09 Unloading view definitions
2008-11-23 22:32:09 Unloading procedures
2008-11-23 22:32:09 Unloading triggers
2008-11-23 22:32:09 Unloading SQL Remote
definitions
2008-11-23 22:32:09 Unloading MobiLink definitions
2008-11-23 22:32:10 Creating new database
2008-11-23 22:32:48 Reloading user and group
definitions
2008-11-23 22:32:48 Reloading table definitions
2008-11-23 22:32:53 Reloading index definitions
2008-11-23 22:32:53 Reloading functions
2008-11-23 22:32:53 Reloading view definitions
2008-11-23 22:32:53 Reloading procedures
2008-11-23 22:32:53 Reloading triggers
2008-11-23 22:32:53 Reloading SQL Remote
definitions
2008-11-23 22:32:53 Reloading MobiLink definitions
Successfully backed up file "D:\marshall\work\iq-
127\mpx\main\sa_dbspace.db" by renaming it to
"D:\marshall\work\iq-
127\mpx\main\sa_dbspace.db.before_schema_reload".
Successfully backed up file "d:\marshall\work\iq-
127\mpx\main\main.db" by renaming it to
"d:\marshall\work\iq-
127\mpx\main\main.db.before_schema_reload".
Successfully backed up file "d:\marshall\work\iq-
127\mpx\main\main.iqmsg" by renaming it to
"d:\marshall\work\iq-
127\mpx\main\main.iqmsg.before_schema_reload".
Successfully reloaded schema of database
"d:\marshall\work\iq-127\mpx\main\main.db".

82 Sybase IQ
 CHAPTER 6 Migrating Data

Start the 15.1 migrated database

Use this command to start the migrated database in readonly mode with Sybase
IQ 15.1:
start_iq -iqro 1 -iqmpx_sn 1
Update the appropriate configuration settings and database options. See the
New Features Guide and Release Bulletin for changes to legacy features and
options.

Verify the migrated databases

Run sp_iqcheckdb to verify the consistency of the migrated databases.

Note In this step, you run the IQ 15.1 version of sp_iqcheckdb, which uses
input parameters, rather than database options, to specify the type of database
consistency checking.

❖ Running sp_iqcheckdb
1 Start the database using the read-only switch, -iqro 1. Start the coordinator
(the 12.6 or 12.7 write server) using both -iqro 1 and single node mode, -
iqmpx_sn 1.

When starting the coordinator in 15.1, use the same port used by the 12.6
or 12.7 writer server.
2 Issue a CHECKPOINT command.
3 Run sp_iqcheckdb in verify mode.
sp_iqcheckdb 'verify database'
If you run the procedure from Interactive SQL, redirect output to a file by
typing the following:
dbisql -c "..." "sp_iqcheckdb ('verify database')"
>& filename
where “...” represents startup parameters for your database.
4 Issue a COMMIT statement.

Installation and Configuration Guide 83

Migrating multiplex databases

Because we started the server in readonly mode, the server cannot complete
some post migration bookkeeping tasks, and the verification will report some
problems with Block Count Mismatch, Blocks Leaked and Unallocated Blocks
in Use. All other segments of the verify database should not report any errors.
For example:
'** Block Count Mismatch','79','*****'
'** Blocks Leaked','25','*****'
'** Unallocated Blocks in Use','104','*****'
Examine the sp_iqcheckdb report for errors. For information on interpreting the
sp_iqcheckdb results and corrective action, refer to Chapter 2, “System
Recovery and Database Repair,” in Sybase IQ Troubleshooting and Recovery
Guide. If you need to contact Sybase Technical Support, you must provide the
output from sp_iqcheckdb.

Start and verify the coordinator

In the previous section, the multiplex coordinator was started in single node
mode (-iqmpx_sn) and readonly (-iqro) to perform some initial database checks.
For coordinators, the server needs to reset an identity cookie before the
multiplex can be used.
Once you successfully restart the coordinator with iqro 1 and iqmpx_sn 1, shut
it down and then restart it normally without any special switches.

Manually synchronize the secondary nodes

To start the secondary nodes, you first need to install Sybase IQ 15.1 and then
synchronize from the coordinator node. When you migrate a query node, it will
become a reader node.

❖ Synchronizing secondary nodes manually

1 Back up the query node files. It is recommended that you at least back up
existing catalog .db, catalog .log and iqmsg files.
For example:
rename d:\work\iq-127\mpx\q1\q1.db d:\work\iq-
127\mpx\q1\q1.db.before_schema_reload
rename d:\work\iq-127\mpx\q1\q1.log d:\work\iq-
127\mpx\q1\q1.log.before_schema_reloadrename

84 Sybase IQ
 CHAPTER 6 Migrating Data

d:\work\iq-127\mpx\q1\q1.iqmsg d:\work\iq-
127\mpx\q1\q1.iqmsg.before_schema_reload
2 Issue a dbbackup command to synchronize servers. You might have a
different name for the query node's catalog file, depending on your
configuration. In the following example, q1.db is the catalog file name on
the query node:
dbbackup -y -x -c
"uid=dba;pwd=sql;eng=mpx_main;dbf=d:\\work\\iq-
127\\mpx\\main\\main.db" d:\work\iq-127\mpx\q1
SQL Anywhere Backup Utility Version 11.0.0.5020
Debug
(702 of 699 pages, 100% complete)
Transaction log truncated
Database backup completed
3 If your query nodes do not use a different catalog database name, skip to
Step 4.
Step 2 synchronized the catalog database file from the coordinator. If you
prefer to use the same catalog database file name as the coordinator, adjust
any server start/stop administration scripts on the secondary nodes to use
the new name.
To retain the same catalog database file names:
a Rename the synchronized coordinator catalog database file name.
Assuming the coordinator file was called main.db and the secondary
server was called q1.db
rename main.db q1.db
b Rename the log file for the query node. This is necessary as the file
renamed above still contains an internal pointer to main.log:
dblog -t q1.log q1.db
4 Start the secondary server in normal mode:
start_iq.exe @params.cfg -n mpx_q1 -x
tcpip{port=62632} -o d:\work\iq-127\mpx\q1\o.out -Z
-zr all -zo d:\work\iq-127\mpx\q1\zo.out D:\work\iq-
127\mpx\q1\main.db
The above command line is derived from your existing query server
start_server administration script.

Installation and Configuration Guide 85

Migrating multiplex databases

5 Repeat the preceding steps on the remaining secondary nodes that you
want to migrate.

Start the secondary nodes

You must complete the steps in “Manually synchronize the secondary nodes”
on page 84 and all nodes of the multiplex must be up and running in order to
execute the following steps.
After you synchronize the secondary nodes, you can start them. For details
about how the administration scripts have changed, see New Features Guide.
In general, secondary servers can be started with the command line startup
utility. For example:
start_iq @params.cfg -n <server_name> database_file.db
In this syntax, <server_name> specifies the secondary server. You can obtain
the name from the existing start server administration script. The specified
database_file.db is the name resulting after you performed the secondary node
synchronization steps.

Set the failover node

After migrating a multiplex database, you need to set the failover node. This is
done while connected to the coordinator and server name is one of the
secondary nodes. Syntax for this is:
ALTER MULTIPLEX SERVER servername ASSIGN AS FAILOVER
SERVER

86 Sybase IQ
 CHAPTER 6 Migrating Data

Post-migration tasks
After you migrate you databases, you may want to perform these post-
migration tasks.

Recreating indexes for EUC_TAIWAN data

In Sybase IQ 15.1, the character encoding specification for the EUC–TAIWAN
collation has been corrected and now uses the EUC_TW character set. Due to
the correction, you must recreate indexes on data in version 12.7 or earlier
databases that use the EUC_TAIWAN collation to make them work with
Sybase IQ 15.1.

Updating configuration files

Be sure to compare your existing params.cfg files with the new default.cfg file
created by the installation. The installation does not update or overwrite
existing params.cfg files. In each params.cfg file, update parameter defaults
that differ from those in the default.cfg file, while maintaining any customized
parameter settings appropriate for your system. Be sure that you add any new
start–up parameters in default.cfg to your params.cfg file. The -gl parameter,
for example, is required for server start–up in version 12.5 and above.

Preserving database options

Sybase IQ preserves the settings of all 12.7 database options that are still valid
in Sybase IQ 15.1 in migrated databases. For more information, see Deprecated
features in Chapter 2, “Behavior Changes in Sybase IQ 15.0,”and Database
option changes in Chapter 2, “Behavior Changes in Sybase IQ 15.0,” in the
New Features Guide.

Backing up your databases after migration

Sybase recommends that you back up your databases again with the BACKUP
statement. For complete syntax, see the System Administration Guide.

Installation and Configuration Guide 87

Post-migration tasks

This backup after the migration is recommended but not required. If you use
the IQ BACKUP statement instead of a system–level backup, you can run
backups and queries concurrently.

88 Sybase IQ
 CHAPTER 6 Migrating Data

For a multiplex migration, back up the coordinator only in this manner. For
secondary servers, run the dbbackup utility from the secondary server
directory.
If you do not use multiplex capability, your migration is complete. The
following sections apply only to multiplex migration.

Installation and Configuration Guide 89

Post-migration tasks

90 Sybase IQ
CH A PTE R 7 Configuring Sybase IQ

About this chapter This chapter describes configuration files, start up options, client access,
backups, and other configuration issues.
Contents
Topic Page
Using configuration files 92
Installing Sybase IQ as a Service 93
Configuring backup devices 94

Installation and Configuration Guide 91

Using configuration files

Using configuration files

If you use an extensive set of options to start your server, you may want to store
them in a configuration file.
The @data option allows you to specify environment variables and
configuration files on the command line. To specify a configuration file,
replace data with the path and name of the configuration file:
start_iq @configuration_filename.cfg dbname.db
If both an environment variable and configuration file exist with the same
name, the environment variable is used.
Configuration files can contain line breaks, and may include any set of options,
including the @data option. Use a number sign (#) to designate lines as
comments. Ampersand (&) characters that appear by itself at the end of a line
indicates that the previous token is continued on the next line.
See Chapter 1 of the Utility Guide for a complete list of switches.
Default configuration %IQDIR151%\scripts directory called default.cfg. This file is also the source
file of parameters for the Service Manager, the params.cfg file used by Sybase
Central and in multiplex configurations. You can maintain consistency by
editing parameters in default.cfg.
If you need to increase the amount of virtual memory, for example, you can
change the parameters in default.cfg to reduce the virtual memory that other
programs use, add swap space to machines, or reduce IQ memory demands
(cache sizes, thread count, stack size, etc.).
Security and You can use the dbfhide (File Hiding) utility to encrypt your configuration files.
configuration files For details see the Adaptive Server Anywhere Database Administration Guide.
If you specify log file parameters (-o logfile) in encrypted files, the log is not
available to the IQ Agent or start_iq, which is unable to display server log
information back to the database administrator. You may want to add
parameters that do not require encryption on the command line or in a separate
configuration file. For example:
start_iq @encrypt_params @other_params
– Or –
start_iq @encrypt_params -n myserv -c 400 -o
%IQDIR151%/logfile/myserv.log

92 Sybase IQ
 CHAPTER 7 Configuring Sybase IQ

Installing Sybase IQ as a Service

Running Sybase IQ as a Windows service lets you start a server automatically
whenever the machine is booted and run in the background as long as Windows
is running.

❖ Creating a new service

1 Click Start, point to Programs | Sybase | Sybase IQ 15.1 | Sybase IQ
Service Manager.
2 Choose Create a New Service.
3 Assign a name to the new service.
4 Add the appropriate start-up parameters.
Include the full path to the database file. The server cannot start without a
valid database path name. For an example of start-up parameters, see
%ALLUSERSPROFILE%SybaseIQ\demo\iqdemo.cfg.
5 Click Apply.

Notes
• Copy any input files that you use to load your databases into the directory
where the service starts, not where the database files are located. On most
systems, the services start-up defaults to the %SYSTEMROOT%\system32
directory.
• To use Sybase IQ as a Windows service when raw device access is
required, you must grant the service Administrator privileges.
• Use Modify an Existing Service or Delete an Existing Service in the Add
Service utility to change or delete Sybase IQ services.

Suppressing Windows If you run the database server as a Windows service, you can set the
event log messages Software\Sybase\Adaptive Server Anywhere\11.0.1 registry entry to suppress
event log entries.
To control event log entries, set the EventLogMask key, which is of type
REG_DWORD. The value is a bit mask containing the internal bit values for
the different types of event messages:
errors EVENTLOG_ERROR_TYPE 0x0001
warnings EVENTLOG_WARNING_TYPE 0x0002
information EVENTLOG_INFORMATION_TYPE 0x0004

Installation and Configuration Guide 93

Configuring backup devices

If the EventLogMask, for example, is set to zero, no messages appear at all.

Setting EventLogMask to 1 surpresses informational and warning messages,
but logs all errors messages. The default setting (no entry present) logs all
message types to appear.
Granting Administrator You must assign Administrator privileges to a Sybase IQ service when raw
privilege to the device access is required.
Sybase IQ service

❖ Granting Administrator privilege to the Sybase IQ service

1 Click Start, point to Settings, choose Control Panel | Administrative Tools
| Services.
2 Right-click the Sybase IQ service, choose Properties.
3 On the Properties sheet, choose Automatic as the Startup Type.
4 Click the Log On tab, then click This account.
5 Assign the account to a user with Administrative privileges. In the account
box, type the administrator’s user ID, then type and confirm the user’s
password in the appropriate text boxes.
6 Click OK to close the Property sheet.
7 Click Close to close the Services console.

Configuring backup devices

Windows does not specify rewind or no rewind devices and supports only
fixed-length I/O operations to tape devices. Sybase IQ requires variable-length
devices and must perform additional processing to accommodate fixed-length
tape I/O.
Because Sybase IQ does not support Windows tape partitioning, do not use
another application to format tapes for Sybase IQ backup or restore. Windows
has a simpler naming strategy for its tape devices.
See also • For more information about fixed-length I/O on Windows, see the
Performance and Tuning Guide.
• For information on naming and specifying tape devices on Windows, see
the chapter “Backup and Data Recovery” in the System Administration
Guide.

94 Sybase IQ
 CHAPTER 7 Configuring Sybase IQ

Configuring client connectivity

Sybase IQ supports ODBC and JDBC connectivity. Sybase IQ 15.1 uses SQL
Anywhere as a server to store catalog information.
Sybase IQ versions prior to 12.0 used Adaptive Server Enterprise as catalog
server. ODBC applications used as client front-end tools with older versions of
Sybase IQ will continue to run in Sybase IQ 15.1, but third-party and customer-
written Open Client™ DB-Library and Client-Library applications are
unlikely to perform as expected.
The only Open Client applications that run with Sybase IQ 12.x are user-
written or iqisql applications that use only catalog tables or system stored
procedures supported by both Adaptive Server Enterprise and SQL
Anywhere (ASA).
Sybase IQ is compatible with clients (like Open Client-Library and DB-
Library) that use TDS. Open Client version 11.1.1 supports TDS 5.x and
applications would therefore work with Sybase IQ, but only if these
applications use the system tables, views, and procedures that are found in
Sybase IQ. System procedures, catalog tables, and views available in Sybase
IQ are listed in the Reference Manual. There are no restrictions to accessing
data in the IQ Store through any supported interface.

Connecting using JDBC

JDBC (Java Database Connectivity) is an Java application programming
interface (API) that provides programmatic access to Sybase IQ. IQ also
includes jConnect, a utility that provides high performance native access to all
Sybase products as a standard installation option.
Sybase Central and Interactive SQL (iqisql) can use either JDBC or ODBC
connectivity. For an overview of using JDBC in Sybase IQ, see “Data Access
Using JDBC” in the System Administration Guide.

Notes
• The iAnywhere JDBC driver is the default driver for Sybase Central and
dbisql.

• IQ Agent can only use jConnect with JDBC to connect to a multiplex

server. The jConnect JDBC drivers have been certified with multiplex and
non–multiplex servers.

Installation and Configuration Guide 95

Configuring client connectivity

Connecting using ODBC

Open Database Connectivity (ODBC) is a standard application programming
interface (API) developed by Microsoft. It allows a single application to access
a variety of data sources for which ODBC-compliant drivers exist. The
application uses SQL as the standard data access language.
ODBC conformance ODBC drivers manufactured by different vendors may vary widely in the
functions they provide. Sybase IQ supports ODBC 3.5.2. ODBC 3.x, drivers
are classified based on the features they provide:
Conformance Level Sybase IQ Support
Core conformance All Core level features.
Level 1 conformance All Level 1 features, except for asynchronous
execution of ODBC functions.
Sybase IQ does support multiple threads sharing a
single connection. The requests from the different
threads are serialized by Sybase IQ.
Level 2 conformance All Level 2 features, except for the following:
• Three-part names of tables and views. This is not
applicable for Sybase IQ.
• Asynchronous execution of ODBC functions for
specified individual statements.
• Ability to time out login request and SQL queries.

Notes
• Although you can use new ODBC 3.5.x features such as descriptors in
your ODBC applications, ODBC 2.x applications will continue to work
with Sybase IQ.
• For more information about ODBC, see the ODBC Programmer's
Reference, available from Microsoft Corporation as part of the ODBC
software development kit or from the Microsoft Web site at
http://www.microsoft.com.

Adding ODBC Data Source Names on 64-bit Windows systems

On 64-bit Windows systems, Sybase IQ installs a 32-bit ODBC driver. To add
new Data Source Names, invoke the ODBC Administrator one of two ways:
• Click Start, point to Programs | Sybase | Sybase IQ | ODBC Data Source
Administrator 64 bit

96 Sybase IQ
 CHAPTER 7 Configuring Sybase IQ

• Run C:\WINDOWS\SysWOW64\odbcad32.exe
Other methods of launching ODBC Administrator from the Control Panel or
Run box do not return desired results. If you type “odbcad32” instead of the
full path in the Run text box, ODBC lists only one driver (SQL Server driver)
and prevents adding Data Source Names. The Version or Company column in
the driver list may include the value “(Not Marked).”
Attempts to add a DSN starting the ODBC Administrator incorrectly may
return one of the following errors:
• The setup routines for the Adaptive Server IQ ODBC
driver could not be loaded due to system error code 126.

• Driver’s ConfigDSN, ConfigDriver, or ConfigTranslator

failed: Could not load the setup or translator library.

• The setup routines for the Adaptive Server IQ ODBC

driver could not be found. Please reinstall the driver.

Installing ODBC drivers

You need to install the Sybase IQ Client Components on each client computer
in your network.The Sybase IQ 32-bit ODBC Driver is shipped with Sybase IQ
as part of the Network Client CD and installed automatically.
To connect UNIX or Linux clients to your server, you must download and
install a platform-specific Sybase IQ ODBC Driver. Check the EBF/Update
information on the Web for the appropriate driver.

Using UNIX-based query tools through ODBC

UNIX or Linux platforms do not provide a standard ODBC driver manager, but
you can use the driver manager emulation capabilities provided by the Sybase
IQ ODBC driver to connect to the driver.
Tools (like Brio) that do not require extensive driver manager services can use
the symbolic links provided with Sybase IQ to connect directly to the driver.
Tools (like Whitelight) that require the presence of a driver manager may ship
with a driver manager.
For information and recommendations about compatible driver managers
available, see the documentation for the application.

Installation and Configuration Guide 97

Configuring client connectivity

Third-party ODBC applications

For information on third-party vendor applications certified with Sybase IQ,
refer to the section “Sybase certifications on the Web” in the Release Bulletin.

Creating ODBC data sources

You need an ODBC data source on the client computer for each database you
want to access using ODBC. A data source describes how to connect to data on
a network. For example, a data source may include the name of a database, the
server where it resides, and the network used to access the server.

Note The AUTOSTOP parameter is required in file data sources and odbc.ini
files. Always be set to NO.

On Windows XP and 2000, the ODBC Administrator adds new data sources
for you. Each data source allows you to access a database over a network by
means of ODBC.

❖ Creating an ODBC data source

On Windows, the ODBC Administrator adds new data sources for you. Each
data source allows you to access a database over a network by means of ODBC.
1 Click Start, point to Programs | Sybase | Sybase IQ 15.1 .
2 Choose the option appropriate for your operating system:
• ODBC Data Source Administrator 32 bit
• ODBC Data Source Administrator 64 bit
3 On the Create New Data Source dialog, choose the Server IQ driver, then
click Finish.
4 When you return to the ODBC Configuration dialog, type a Data Source
Name in the Data Source Name box.
5 Click the Login tab, type a database User ID and Password in the
appropriate text boxes.
6 Click the Database tab. Do one of the following:
• If the data source is on a remote machine, type the server name and
database file name. (The database file is used only if the database is
not started automatically on server start-up.)

98 Sybase IQ
 CHAPTER 7 Configuring Sybase IQ

• If the data source is on your local machine, type a start line and
database name (without the .db extension).
• If the data source is on a remote system, click the Network tab, and
select the appropriate protocol and options.
For example, to use TCP/IP to connect to server on a host named
localhost2k and port 1870, click the TCP/IP box and type
host=localhost2k:port=1870 in the text box.

You can also use the host network address:

host=157.133.66.75:1870
7 Click OK to return to the ODBC Data Source Administrator.

Note You cannot connect to a Sybase IQ 15.1 server using an ODBC Data
Source Name created for a 12.5 server, even if you specify the same server
name, port number, and database name. Use the ODBC Data Source
Administrator to remove DSNs created in 12.5 and add new DSNs.

You can use files as data sources instead of databases. File data sources are
stored as files with the extension .dsn. For information about creating a file data
source, see the System Administration Guide.

❖ Testing an ODBC data source

1 Start the database.
2 In the ODBC Data Source Administrator, select your new data source from
the list of User Data Sources.
3 Click Configure.
4 On the ODBC Configuration dialog box, click Test Connection.
If you cannot access the data source, check that you have filled out the
various tabs with correct file and path names.

Command-line connection to 32-bit applications

To connect to 32-bit applications without using a data source, enter an
Interactive SQL command like the following at the command prompt:
dbisql -c "UID=DBA;PWD=sql;AUTOSTOP=no;
ENG=<engine name>;DBF=%ALLUSERSPROFILE%\Sybase\
IQ 15.1\iqdemo.db"

Installation and Configuration Guide 99

Configuring client connectivity

This dbisql command can have the following parameters:

UID — user ID
PWD — password
ENG — engine name
COMMLINKS — tcpip (port=engine_port_number)
AUTOSTOP — no
DBF — database file name with path
The DBF parameter is used only with embedded databases.

Note The AUTOSTOP parameter is required. It should always be set to NO.

Connecting using OLE DB

OLE DB is a data access model from Microsoft. It uses the Component Object
Model (COM) interfaces. Unlike ODBC, OLE DB does not assume that the
data source uses a SQL query processor.
This release of Sybase IQ includes an OLE DB provider. If you use the Sybase
IQ OLE DB provider, ODBC is not required in your deployment.
OLE DB requires a Windows client. However, you can access both Windows
and UNIX servers using OLE DB. For more information, see the Adaptive
Server Anywhere Programming Interfaces Guide.
Sybase IQ support for certain features used with OLE DB differs from
Adaptive Server Anywhere support. Be aware of these differences when using
the Adaptive Server Anywhere documentation:
• Sybase IQ does not support Windows CE.
• Sybase IQ does not support remote updates through a cursor.
• Sybase IQ supports Dynamic (dynamic scroll), Static (insensitive), and
and Forward only (no-scroll) cursors, but does not support Keyset (scroll)
cursors.
• In Sybase IQ the isolation level is always 3, no matter what you specify.
For information on connecting to a database using OLE DB, see the System
Administration Guide.

100 Sybase IQ
 CHAPTER 7 Configuring Sybase IQ

Connecting using Open Client

If you need to insert from an Adaptive Server Enterprise database to a Sybase
IQ database, or you want to connect using iqisql, each server must have an entry
in the interfaces file on the client computer. Interfaces file entries, also called
server objects, also simplify database start-up.
Use iqdsedit (IQ Directory Services Editor) to create entries in the interfaces
file. You must be the owner of the Sybase home directory (%SYBASE%) to run
iqdsedit.

Adding server objects also simplifies connections to servers from Sybase

Central.

Running client and server on the same system

Shared memory is the default communications mechanism when the client and
server are on the same system. It is configured automatically, and starts up
automatically, on both UNIX and Windows platforms. When the client and
server are on the same machine and the -hs option is not used to start the server,
Sybase IQ uses a shared memory segment and several semaphores for
communication.

Network issues for IQ servers

• Properly configured Sybase IQ database servers on Windows run on
networks using the TCP/IP protocols.
• The client library for each platform supports the same protocols as the
corresponding server.
• For Sybase IQ to run properly, the protocol stack on the client and server
computers must be compatible at each layer.

Using Sybase IQ with TCP/IP

Because different TCP/IP implementations rely on particular data link drivers
to work correctly, Sybase IQ supports only certain TCP/IP implementations on
each platform. For details, see the subsections below for each platform. As all
TCP/IP implementations do implement the same protocol suite, they are all
compatible.

Installation and Configuration Guide 101

Configuring client connectivity

User Datagram There are several entries into the TCP/IP protocol stack. IQ employs the User
Protocol Datagram Protocol (UDP). Although it is called a transport protocol here and
elsewhere, UDP provides little more than a user interface to the network layer
IP. In particular, UDP is not a guaranteed transmission protocol.
Verified TCP/IP Many vendors supply TCP/IP protocol stacks and associated software. IQ
protocol stacks communications have been explicitly verified with the following TCP/IP
implementations.
• Windows Microsoft Winsock version 2.0.
Using TCP/IP with Windows NT 3.5 and later ship with TCP/IP software that uses NDIS network
Windows drivers. Install TCP/IP Protocol from Control Panel, Network Settings.
This software allows an IQ server for Windows or an IQ client application to
use Windows TCP/IP.
Tuning Sybase IQ Although the default packet size for TCP/IP is 512 bytes, a larger packet size
performance under may improve query response time, especially for queries transferring a large
TCP/IP
amount of data between a client and a server process. You can set the packet
size using the -p parameter on both the IQ client and the database server
command lines.

Connecting across a firewall

There are restrictions on connections when the client application is on one side
of a firewall, and the server is on the other. Firewall software filters network
packets according to network port. Also, it is common to disallow UDP packets
from crossing the firewall.
When connecting across a firewall, you must use a set of communication
parameters in the CommLinks connection parameter of your application's
connection string.
• Set the UseUDP parameter to OFF to prevent UDP packets from being
used to locate the server. You can use the short form UDP.
• Set the ClientPort parameter to a range of allowed values for the client
application to use. You can then configure your firewall to allow these
packets across. You can use the short form CPort.
• Set the HOST parameter to the host name on which the database server is
running. You can use the short form IP.
• If your database server is not using the default port of 2638, you must
specify the port it is using, in the ServerPort parameter. You can use the
short form Port.

102 Sybase IQ
 CHAPTER 7 Configuring Sybase IQ

For more information on these parameters see the System Administration

Guide.
Example The following connection string fragment restricts the client application to
ports 5050 through 5060, disables UDP packets, and connect to a server named
myiq running on the machine at address myhost using the server port 2020.
CommLinks=tcpip(UseUDP=OFF;ClientPort=5050-
5060;Host=myhost;Port=2020;Eng=myiq)
Additional networking For more detailed information on networking and protocol stacks, refer to
details networking-specific documentation.

Installation and Configuration Guide 103

Configuring client connectivity

104 Sybase IQ
A P PE N DI X A Silent Installations

About this chapter This chapter tells you how to install Sybase IQ without having to interact
with the standard installation wizard.
Contents
Topic Page
Overview 106
Installing IQ silently 106
Uninstalling IQ silently 110
Sample configuration files 110

Installation and Configuration Guide 105

Overview

Overview
Your installation media includes scripts that perform standard IQ installs and
uninstalls without the need to interact with the product. These scripts are
configured to perform typical installations by default; custom installation tasks
require additional configuration.
The installation media includes installation scripts, an appropriate JRE,
CLASSPATH settings, java command string, and pointers to the text file that
contains the feature selections and configuration options.

Note Client and Server silent installation scripts share the same filenames. Be
sure that you are running the correct script when you are installing or
uninstalling IQ components.

Installing IQ silently
IQ silent installation scripts support typical and custom installations. See
“Editing the installation parameters” on page 107 for information about
changing the installation defaults; see “Running a silent install” on page 107
for information about running a silent install.

Task summary
The following list summarizes the tasks required to run a silent install.
• Update the installation parameters, if necessary. Installation parameters
are stored in SilentInstall.txt and match the defaults in a typical
installation. If you want to change any installation options, you need to
edit this file and save your changes on the file system. See “Editing the
installation parameters” on page 107 for more information.
• Run the silent install scripts. Be sure to complete all preinstallation tasks
before you run the installer. See “Running a silent install” on page 107 and
“Completing the installation” on page 109 for more information.

106 Sybase IQ
 APPENDIX A Silent Installations

Editing the installation parameters

Installation parameters are stored in SilentInstall.txt. SilentInstall.txt is
configured to perform typical installations by default; custom installs require
additional configuration.
SilentInstall.txt contains the same default selection and configuration options
as the interactive installer. If you change the target installation directory, for
example, use an editor to change the default parameters. See “SilentInstall.txt”
on page 111 to review the parameters in this file.
• Comments in the file are prefixed with a # sign
• Modifiable parameters appear between “quotes”
• Feature selections start with a –P
• Variable options are prefixed with a –V
If you modify the file, read the comments before the section you want to
change, update the parameters, then save SilentInstall.txt to the local file
system.

Running a silent install

SilentInstall.bat is a batch file that you launch from the command line to start
the install. You must include a license acceptance switch as an argument when
you run this script. If you do not have the %SYBASE% environment variable
set, you must also specify the -dst parameter. Other arguments depend on
whether you plan to run a Typical install or Custom install.
Command line You can display options for this script by running the SilentInstall.bat with the
arguments –h or –? option on the command line. All arguments appear in the table below.
Argument Description
h or ? Display help and exit.
jvm "JVM_ARGS" Include user specified JVM_ARGS.
java Specify the location of the java folder.
txt Specify the location of Silent Install text file.
bs <32|64> Specify the bit size of the installed files.
cl Specify the location of the silent install console log.
src Specify the path to root directory of installer files.
I_accept_sybase_license Agree to the Sybase IQ licensing terms.
dst Specify the install location for Sybase IQ .

Installation and Configuration Guide 107

Installing IQ silently

Argument Description
licensed_user Installs the licensed version of Sybase IQ.
eval_user Installs the evaluation version of Sybase IQ.

Typical install You can run a typical silent install directly from the installation CD. The
command you use to launch the install must include a version switch (–
licensed_user or – eval_user) and a – license acceptance switch:
<DVD drive>\SilentInstall.bat -licensed_user
-I_accept_sybase_license
If you do not have the %SYBASE% environment variable set, you must also
specify the -dst parameter and the destination directory as parameters.
Custom install Custom install commands must include the –txt switch that points to the
location of the modified SilentInstall.txt as well as a version switch and –
license acceptance switch:
<path>\SilentInstall.bat –txt <path>\SilentInstall.txt
-licensed_user -I_accept_sybase_license
If you do not have the %SYBASE% environment variable set, you must also
specify the -dst parameter and the destination directory as parameters.
Running silent install You must have sufficient user permissions to run applications in Microsoft
scripts on Microsoft Vista. If you do not have administrator privileges and want to run a silent install
Vista
or uninstall, open a command prompt as an Administrator, then execute the
silent install or uninstall from the command line.
For example:
1 Click Start, right-click Command Prompt, choose Run as
administrator.
2 Change to the directory on the local file system where you saved your
updated installation script(s).
3 Run the command to execute the script.
For example:
SilentInstall.bat -licensed_user
–I_accept_sybase_license –dst <path to destination
directory>\Sybase_server

108 Sybase IQ
 APPENDIX A Silent Installations

Notes
• If you change the license acceptance parameter in the SilentInstall.txt file,
you do not need to specify that option on the command line.
• You can monitor silent installs by running a tail command on the log file.
The default name and location of this file is
\%ALLUSERSPROFILE%\SybaseIQ\logfiles\IQ15Console.log. This
location and log file name can be changed by adding –cl and the log
location as a command line parameter when launching the silent install.

Completing the installation

After you run the install, remove the DVD from the drive.
If you installed Sybase Central, see the System Administration Guide for
instructions on configuring and running the IQ Agent. You must configure and
run the IQ Agent in order to manage multiplexes with Sybase Central.

Note After you install the software, Sybase strongly recommends that you
check the online support Web site for software updates. If a software update
(EBF) has been released, it contains bug fixes made after this product shipped.

Uninstalling IQ silently
IQ silent uninstallation scripts support typical and custom uninstallations. See
“Editing the uninstall parameters” on page 110 for information about changing
the uninstall parameters; see “Running a silent install” on page 107 for
information about running the uninstaller.

Note You must run a silent uninstall from the installation directory, not the
installation media.

Installation and Configuration Guide 109

Uninstalling IQ silently

Editing the uninstall parameters

SilentUninstall.txt contains parameters that tell the uninstaller what
components you want to remove. SilentUninstall.txt is configured to remove
all components by default; removing specific components requires additional
configuration.
SilentUninstall.txt contains the same default selection and configuration
options as the interactive uninstaller. If you only want to uninstall some
components, edit the file, and change the default parameters:
• Features with parameters set to true will be uninstalled
• Features with parameters set to false will not be uninstalled
If you modify the file, read the comments for the section(s) you want to change,
update the parameters, then save SilentUninstall.txt to the local file system. See
“SilentUninstall.txt” on page 116 to review the parameters in this file.

Uninstalling IQ components
SilentUninstall.bat is the name of the script that you use to uninstall IQ
components. How you run the uninstall depends on whether you are
“Uninstalling all components” on page 110 or “Uninstalling some
components” on page 110.
Uninstalling all If you installed IQ with all defaults, you can run a typical silent uninstall
components directly from the installation directory. To run the uninstall, open a command
window, and use the following command:
%SYBASE%\uninstall\IQ\SilentUninstall.bat
Uninstalling some To perform a custom uninstall, the command you use to run SilentUninstall.bat
components must include the –txt switch that points to the location of a modified
SilentUninstall.txt:
%SYBASE%\uninstall\IQ\SilentUninstall.bat -txt
<directory name>\SilentUninstall.txt
Running silent You must have sufficient user permissions to run applications in Microsoft
uninstall scripts on Vista. If you do not have administrator privileges and want to run a silent
Microsoft Vista
uninstall, open a command prompt as an Administrator, then execute the silent
uninstall from the command line.

110 Sybase IQ
 APPENDIX A Silent Installations

Sample configuration files

Use this section to review the settings in the configuration files,
SilentInstall.txt and SilentUninstall.txt.

SilentInstall.txt
Use this example to review the server settings in a typical SilentInstall.txt file.
Client versions follow the same conventions.
################################################################
########################### SILENT INSTALLER ################################
#############################################################################

#############################################################################
# IMPORTANT NOTE BEFORE STARTING (If you have previously installed IQ):
# 1. Ensure IQ Server is not running.
#############################################################################

#############################################################################
# By setting the following argument to "true", you are agreeing to the
# Sybase License Agreement.
#############################################################################
-V AgreeToSybaseLicense="false"

#############################################################################
# By setting the following argument to "true", you wish to ignore the warning
# about installing Sybase IQ even though a previous version of Sybase IQ has
# been found.
#############################################################################
-V IgnorePreviousVersion="false"

#############################################################################
# By setting the following argument to "false" you wish to use the Evaluation
# version. By setting the following argument to "true" you wish to use the
# Licensed Version. You can specify a license file below if you select a
# licensed version.
#############################################################################
-V Variable_IQDemoSelect_LicensedYesRB="false"

#############################################################################
# NOTE: The following two variables apply to WINDOWS Platform Only
#
# The install will try to detect if Sybase Open Client is in the environment.
# To prevent conflicts, IQ will append the IQ executable directory to the end

Installation and Configuration Guide 111

Sample configuration files

# of the search PATH when it finds Sybase Open Client in the environment.
#
# In rare cases, appending to the end of the PATH can fail due to the length
# of the PATH exceeding the maximum system length, or if an invalid or corrupt
# entry preceeds IQ. If IQ is missing from the path after the install
# completes, please shorten or clean the current PATH and then reboot before
# attempting a reinstall.
#
# If you wish to modify the install behavior you can uncomment and modify
# the two variables below:
# Variable_OverridePrependOrAppendToPath"true" to override install
# behavior
# "false" to use install
# behavior
# Variable_IQAppendPath_Prepend_IQBinDir"true" to prepend
# "false" to append
#############################################################################
### -V Variable_OverridePrependOrAppendToPath="false"
### -V Variable_IQAppendPath_Prepend_IQBinDir="true"

#############################################################################
#
# Sybase Software Asset Management License
#
# Sybase Data Integration Suite requires Sybase Software Asset Management
# (SySAM) license key(s). If you have not yet obtained the license key(s), go
# to
# SPDC at http://sybase.subscribenet.com to obtain the license keys.
#
# You can specify the license file or license server where the license key(s)
# were previously deployed.
#
# -W sysamLicense.proceedWithoutLicense - Select this if you want to
# continue installation without
# a
# license key.
# -W sysamLicense.useExistingLicenseServer - Valid values are "true" or
# "false". Set to "true" if you
# want to use previously
# deployed
# license server or "false" if
# want to specify the license
# file.
# -W sysamLicense.licenseFile - Specify the Sybase Software
# Asset Management license file.
# -W sysamLicense.licenseServerHostName - Enter the hostname where the

112 Sybase IQ
 APPENDIX A Silent Installations

# license server was deployed.

# -W sysamLicense.licenseServerPortNumber - Enter the license server port
# number. Leave the entry blank
# if you want to use the default
# port numbers.
#

-W sysamLicense.proceedWithoutLicense=true
### -W sysamLicense.useExistingLicenseServer=false
### -W sysamLicense.licenseFile=
### -W sysamLicense.licenseServerHostName=localhost
### -W sysamLicense.licenseServerPortNumber=

#############################################################################
#
#
# Please select the product edition you would like to configure. For Enterprise
# and Small Business Editions, you also need to select the license type for this
# installation. For the productEdition and licenseType fields below, enter the
# 2-letter codes listed below that correspond to your license.
#
# sysamProductType.productEdition - Valid values are
# "EE" - Enterprise Edition,
# "SE" - Small Business Edition
# "SA" - Single Application Edition
#
# sysamProductType.licenseType - Valid values are dependant on the
# product edition.
# For Enterprise Edition the license type
# can be
# "CP" - CPU License
# "DT" - CPU Development and Testing License
# "SF" - CPU Standby License
# "AC" - OEM CPU License
# "BC" - OEM Standby CPU License
# "EV" - Evaluation License
# "" - Unknown
#
# For Small Business Edition the license type
# can be
# "CH" - Chip License
# "DH" - Chip Development and Testing License
# "SH" - Chip Standby License
# "AH" - OEM Chip License
# "BH" - OEM Standby Chip License
# "EV" - Evaluation License

Installation and Configuration Guide 113

Sample configuration files

# "" - Unknown
#
# For Single Application Edition the license type
# can be
# "CP" - CPU License
# "EV" - Evaluation License
# "" - Unknown
#############################################################################

-W sysamProductType.productEdition="EE"
-W sysamProductType.licenseType="DT"

#############################################################################
# Sybase Software Asset Management email alerts
#
# If you would like to configure email alerts, set
# -V Variable_IQSySAMEmail_AlertsYesRB=true
# -V Variable_IQSySAMEmail_AlertsNoRB=false
# and uncomment and set the other variables appropriately.
#
# Valid values for -V Variable_IQSySAMEmail_SeverityTF= are:
# WARNING, INFORMATIONAL, and ERROR
#############################################################################

-V Variable_IQSySAMEmail_AlertsYesRB=false
-V Variable_IQSySAMEmail_AlertsNoRB=true
# -V Variable_IQSySAMEmail_HostTF=smtp
# -V Variable_IQSySAMEmail_PortTF=25
# -V Variable_IQSySAMEmail_SenderTF=" "
# -V Variable_IQSySAMEmail_RecipientTF=" "
# -V Variable_IQSySAMEmail_SeverityTF=" "

#############################################################################
# Enable/Disable features to be installed by setting the value to
# "true" or "false".
#
# Legal values are:
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# In order to install a sub feature, all parent features must also be
# selected.
#
# Note: You will need to remember these same features if running the
# Silent Uninstall.
#

114 Sybase IQ
 APPENDIX A Silent Installations

# For example, to select "Server:" for installation, use

#
# -P Server.active=true
#
#############################################################################

# "SybaseIQ" Feature
-P SybaseIQ.active="true"
# "IQServer" Feature
-P IQServer.active="true"
# "IQOpenClient" Feature
-P IQOpenClient.active="true"
# "IQClient" Feature
-P IQClient.active="true"
# "IQODBC" Feature
-P IQODBC.active="true"
# "SybaseCentral" Feature
-P SybaseCentral.active="true"
# "SCJViewer" Feature
-P SCJViewer.active="true"
# "SCJPlugin" Feature - requires SCJViewer to be installed
-P SCJPlugin.active="true"
# "jConnect" Feature
-P jConnect.active="true"
# "SybaseSySAM" Feature
-P SybaseSySAM.active="true"
# "NetworkLicenseServer" Feature
-P NetworkLicenseServer.active="false"
# "LicenseUtilities" Feature
-P LicenseUtilities.active="true"

#############################################################################
# Please do not modify the values below.
#############################################################################
-V Variable_Silent="true"
-W InstallType.active="false"
-P copyJRE.active="true"
-P SilentUninstall.active="true"
-P copyJRE1.active="true"
-P SilentUninstall1.active="true"
-silent

Installation and Configuration Guide 115

Sample configuration files

SilentUninstall.txt
Use this example to review the server settings in a typical SilentUninstall.txt
file. Client versions follow the same conventions.
#############################################################################
########################### SILENT UNINSTALLER ##############################
#############################################################################

#############################################################################
# Enable/Disable features to be uninstalled by setting the value to
# "true" or "false".
#
# Legal values are:
# true - Indicates that the feature is selected for removal
# false - Indicates that the feature is not selected for removal
#
# For example, to select "Server:" for removal, use
#
# -P Server.activeForUninstall=true
#
#############################################################################

# "SybaseIQ" Feature
-P SybaseIQ.activeForUninstall="true"
# "IQServer" Feature
-P IQServer.activeForUninstall="true"
# "IQOpenClient" Feature
-P IQOpenClient.activeForUninstall="true"
# "IQClient" Feature
-P IQClient.activeForUninstall="true"
# "IQODBC" Feature
-P IQODBC.activeForUninstall="true"
# "SybaseCentral" Feature
-P SybaseCentral.activeForUninstall="true"
# "SCJViewer" Feature - removal of SCJViewer requires that SCJPlugin
# be removed as well
-P SCJViewer.activeForUninstall="true"
# "SCJPlugin" Feature
-P SCJPlugin.activeForUninstall="true"
# "jConnect" Feature
-P jConnect.activeForUninstall="true"
# "SybaseSySAM" Feature
-P SybaseSySAM.activeForUninstall="true"
# "NetworkLicenseServer" Feature
-P NetworkLicenseServer.activeForUninstall="true"
# "LicenseUtilities" Feature

116 Sybase IQ
 APPENDIX A Silent Installations

-P LicenseUtilities.activeForUninstall="true"

#############################################################################
# Please do not modify the values below.
#############################################################################
-G removeExistingResponse=yesToAll
-G removeModifiedResponse=yesToAll
-silent

Installation and Configuration Guide 117

Sample configuration files

118 Sybase IQ
A P PE N DI X B Troubleshooting SySAM

About this Chapter If SySAM 2 related errors are not addressed in a timely fashion, Sybase
IQ may cease to function. This section includes information about
troubleshooting the most common SySAM related errors.
For the most up to date information about troubleshooting SySAM, see the
SySAM FAQ at http://www.sybase.com/products/allproductsa-z/sysam.

Contents
Topic Page
Where to look for SySAM-related errors 120
SySAM grace mode 120
SySAM grace period 120
Enabling and changing e-mail notifications 121
Calling Sybase technical support for SySAM-related issues 121
License checkout and verification 123
Diagnosing SySAM issues 123

Installation and Configuration Guide 119

Where to look for SySAM-related errors

Where to look for SySAM-related errors

All SySAM related errors are printed in the Sybase IQ error log and
<dbname>.iqmsg file. If e-mail alerts are configured, recipients receive an e-
mail whenever a SySAM event occurs.
You can always check the current state of SySAM licenses in Sybase IQ using
the sp_iqlmconfig command. The output shows the current SySAM
configuration and the status of each license.
If you are using a served license model, the license server’s debug log located
in the log directory provides information about any license check-out issues.

SySAM grace mode

If Sybase IQ cannot find a required license, it continues to operate in grace
mode, if a grace period is available.
The Sybase IQ error log and <dbname>.iqmsg file include information about
licenses awarded under grace. If e-mail notifications are set up for warning
severity, e-mail messages are sent for this event. See “Enabling and changing
e-mail notifications” for more information.
The warnings in the Sybase IQ error log, <dbname>.iqmsg file, and e-mail
message are repeated while the license is under grace.

SySAM grace period

Typically, you get a 30-day grace period to resolve any SySAM-related issues.
When a license is awarded under grace, entries in Sybase IQ error log,
<dbname>.iqmsg file, and optional e-mail message include the date and time
when the grace period expires.
Sybase IQ disables the functionality corresponding to the license if the issue is
not fixed within the grace period. Sybase IQ itself shuts down if the graced
license is IQ_CORE.

120 Sybase IQ
 APPENDIX B Troubleshooting SySAM

Enabling and changing e-mail notifications

You can configure the e-mail notification setup using sp_iqlmconfig. Run
sp_iqlmconfig command without any parameters to view the current status and
configuration.
To enable e-mail notifications, set the smtp host, smtp port, email sender, email
recipients, and email severity properties.

To change the severity that triggers e-mails, set the e-mail severity property.
Values are: ERROR, WARNING, INFORMATIONAL and NONE.
To change the list of e-mail recipients, set the e-mail recipients property to the
comma separated list of e-mail addresses. E-mail addresses can include
distribution lists, e-mail address for a pager device, and anything that is capable
of receiving SMTP messages.

Calling Sybase technical support for SySAM-related

issues
If you call Sybase technical support for SySAM-related issues have the
following information available:
• The Sybase IQ error log located in
%ALLUSERSPROFILE%SybaseIQ\logfiles\<servername>.stderr
directory.
• The <dbname>.iqmsg file located in the same directory as your IQ
database
• If you started Sybase IQ in grace mode – output from the sp_iqlmconfig
command.
• If Sybase IQ does not start – output from the server’s log file(s) in the
%ALLUSERSPROFILE%SybaseIQ\logfiles\<servername>.nnn.srvlog.
• The license files in the %SYBASE%\SYSAM-2_0\licenses directory on the
machine running Sybase IQ.
• The value of SYBASE_LICENSE_FILE and LM_LICENSE_FILE
environment variables, if they have been defined.
• Output from lmutil lmpath -status command. The lmutil binary is located in
the %SYBASE%\SYSAM-2_0\bin directory.

Installation and Configuration Guide 121

License checkout and verification

• If you are using a served license model, the licenses in the

%SYBASE%\SYSAM-2_0\licenses directory, and the license server log file
in the %SYBASE%\SYSAM-2_0\log directory.

License checkout and verification

SySAM checks feature licensing at various times. Some features are only
checked on startup; others after the feature has been added to the database (e.g.,
passed the threshold for IQ store size, created multiplex writer, etc.); others are
triggered by a particular event.
IQ_SECURITY licenses are ALWAYS checked out during startup. This is
necessary because IQ_SECURITY features (column encryption, Kerberos
authentication, etc.) need to be turned on at startup. If you do not have an
IQ_SECURITY license, IQ_SECURITY checkout failures may simply mean
that security features will not be initialized during startup.
License checkout Table B-1 describes the events that determine when SySAM checks out
different licenses.
Table B-1: License checkout table
Initial Node Separate
checkout checking license per
License occurs on Coordinator Writer Reader out node
IQ_SECURITY Database startup Yes Yes Yes All nodes Yes
IQ_MPXNODE Database startup Never Yes Yes Secondary Yes
nodes only
IQ_VLDBMGMT User creates 3rd Yes Never Never Coordinator No
dbspace only
IQ_LOB User Yes Yes Yes All nodes Yes
creates/accesses
LOB/CLOB
table
IQ_CORE Database startup Yes Yes Yes All nodes Yes
IQ_UDF User accesses Yes Yes Yes All nodes Yes
UDF

Note IQ_SYSTEM_MAIN and one more user dbspace is provided with the
server; a third dbspace requires a IQ_VLDGMGMT license.

122 Sybase IQ
 APPENDIX B Troubleshooting SySAM

License verification Table B-2 identifies when SySAM verifies different licenses.
Table B-2: License verification table
Consistent Checks on
checks on startup after Checks on
License startup feature enabled feature access
IQ_SECURITY • •
IQ_MPXNODE • •
IQ_VLDBMGMT • •
IQ_LOB •
IQ_CORE •
IQ_UDF •

Note Changes to licensed features may not appear until the server is restarted.
Checked out licences remain in use until you restart the server.

Diagnosing SySAM issues

Refer to the following table to locate specific SySAM problems.
Problem Descriptions
“Cannot find license type during the Sybase IQ “Sybase IQ cannot check out a license and
installation” on page 124 starts with graced license instead” on page 126
“The installation program produces a warning “Sybase IQ shows graced licenses even after
about not finding a suitable license” on page the issue has been fixed” on page 128
124
“The license server executables and scripts are “Sybase IQ cannot find license for an optional
not installed” on page 124 feature, even though the license exists” on page
128
“The license server does not start” on page 125 “Sybase IQ does not start with the expected
edition or license type” on page 129
“The license server does not recognize the “Sybase IQ does not pick the correct license”
license files” on page 125 on page 129
“Sybase IQ does not start, and generates a
license check-out failure error” on page 126

Installation and Configuration Guide 123

Diagnosing SySAM issues

Cannot find license type during the Sybase IQ installation

Sybase IQ installation program displays only the most commonly used license
types. If you are using an optional license type, your license may not be listed
by the installation program.

The installation program produces a warning about not finding a

suitable license
If you select a served license model, the install program checks for a license
with the selected edition and license type. A warning message is displayed if
no suitable license is available.
If you are performing a new Sybase IQ installation, Sybase provides a 30 day
grace period to resolve licensing issues. When you complete the installation,
debug the license check-out failure. For more information, see “Sybase IQ
cannot check out a license and starts with graced license instead” on page 126.
You can determine the date based version of the license by looking at the
license checkout message in the Sybase IQ error log and <dbname>.iqmsg file;
or by examining the license itself. For more information see Appendix A
Anatomy of a License in the Sybase Software Asset Management Users Guide.
You can determine the Sybase IQ release date by the date displayed in the
version string, cover letter, or SPDC download link. This data is also shown in
the error message posted.
You can download an updated license from SPDC, if your support was paid for
the date the update was released. If you support was not paid, you are not
authorized to install an update.
See also • See Appendix B of the Sybase Software Asset Management Users Guide
for an explanation of how SySAM uses date-based versioning.
• See Updating your Sybase licenses in Chapter 3 Getting and Using your
Licenses, in the Sybase Software Asset Management Users Guide for how
to update your license.

The license server executables and scripts are not installed

The SySAM wrapper script and the executables for the license server (lmgrd
and SYBASE) are not installed or found in the %SYBASE%\SYSAM-2_0\bin
directory.

124 Sybase IQ
 APPENDIX B Troubleshooting SySAM

The license server component is not selected for installation by default. To

install the license server, run the installer, choose the Custom install option, and
select license server component.
Alternatively, you can download a standalone SySAM license server install
program from SPDC.

The license server does not start

The most common cause for the license server failing to start is that there are
no served licenses in the server. To start the license server, there needs to be at
least one served license in the licenses directory. When you install a new
license server, there are no served licenses in the licenses directory and the
license server does not start until you activate a license from SPDC and copy
it into the licenses directory.
Other causes for license server not to start include:
• The license activated from SPDC was an unserved license. Examine the
license files. Served licenses always start with a SERVER header. If you do
not see a line starting with SERVER at the top of the license, you are using
an unserved license which does not work with the license server.
• If you are using a specific port number for the license, that port number
may already be in use. Use netstat -a to verify that the port number is free.
If not, free the port or use a different port number for the license server.
• The host name recorded in the SERVER header does not match the actual
host name. The host name is recorded next to the SERVER keyword. If it
does not match, correct the host name in the license file or set it to
this_host, which is a keyword that works with any host name.
• The licenses copied may be activated for a different machine. Examine the
Host ID next to the host name in the SERVER header. This value must
match the Host ID for the machine where the license server is running.

The license server does not recognize the license files

If the license server refuses to serve the licenses, this may be because:

Installation and Configuration Guide 125

Diagnosing SySAM issues

• The license was activated for a different machine or activated using

incorrect Host ID. Examine the Host ID recorded in the license with the
Host ID for the machine. If they are mismatched, check-in and regenerate
the license with the correct Host ID.
• The license has been altered. Nothing in the license except some
designated information can be altered. The license is rejected if you
change other information. If the license is being created by typing from a
paper copy, verify if there are any errors entering the license. You can also
download a new copy of the activated license from SPDC.
• If the Host ID for your platform is based on the Network adapter
identification, verify that you have used an ID associated with a valid NIC.
IDs associated with loopback adapters are not valid. If the ID associated
with a removable network adapter was used, ensure that the adapter is
attached to the computer.

Sybase IQ does not start, and generates a license check-out failure

error
If Sybase IQ cannot check out the required license, it determines whether the
license can be issued in grace mode. If a grace period cannot be given, the
license is not granted. If the base license for Sybase IQ (IQ_CORE) was in
grace and the issue is not fixed by the end of the grace period, Sybase IQ fails
to start.
For more information, see Sybase IQ cannot check out a license and starts with
graced license instead in this table. The troubleshooting tips for resolving
licenses issued under grace apply to solve this issue as well.

Sybase IQ cannot check out a license and starts with graced

license instead
Execute the SySAM diag feature_name command from the %SYBASE\SYSAM-
2_0 bin directory, where feature_name is the SySAM feature name for Sybase
IQ or the optional feature that is in grace mode. The feature name is printed in
the Sybase IQ error log , <dbname>.iqmsg file, and in the optional e-mail
notifications.
If the diag command shows no licenses available for check-out, this may be due
to one of the following reasons:

126 Sybase IQ
 APPENDIX B Troubleshooting SySAM

Served models • Verify that the license server is running and reachable from the machine
you are using. Use sysam status to verify that you can access the license
server. If you cannot access the license server, see if the license server is
running.
• If the license server is running, use sysam status -f feature_name to
determine whether the license server is serving a license for the given
feature. If not, obtain the correct licenses from SPDC.
• All licenses on the license server may be in use. If sysam status -f
feature_name indicates that no licenses are available, obtain additional
licenses or shutdown Sybase IQ.
Unserved models • The license for the given feature may not be copied in the local licenses
directory. Obtain the correct licenses from SPDC and copy them to the
local licenses directory.
• The license may have been activated for a different machine or activated
with incorrect Host ID. Check-in and reactivate the license with the correct
Host ID.
Wrong license • The available licenses are for a different operating system or architecture.
Obtain license for the correct platform from SPDC.
• If you are running in a terminal server environment, unserved licenses
cannot be used. Set up served licenses for a terminal server environment.
• The available license may not authorize use of this version of Sybase IQ.
• For information about date based versioning, see Appendix B, Installing
Product Updates, EBFs, and Support Renewal in the Sybase Software
Asset Management Users Guide.
• For information about how to update your license, see the Updating your
Sybase licenses section in Chapter 3, Getting and Using your License, in
the Sybase Software Asset Management Users Guide.
product edition or If the diag command shows the license for the given feature is available for
license type check-out, the reason that Sybase IQ cannot check-out the license could be that
the product edition or license type does not match the requirement.
• If the edition and license type configuration parameters are set, Sybase IQ
uses only the license that matches these settings.
• Run sp_iqlmconfig to see the configured values.
• Check the VENDOR_STRING attribute of the licenses to make sure a
matching license exists. If a matching license does not exist, obtain a
suitable license from SPDC or adjust the Sybase IQ configuration.

Installation and Configuration Guide 127

Diagnosing SySAM issues

If Sybase IQ cannot start because the grace period expired, examine the
iq.default.lmp file located in the %IQDIR15%/Sysam directory under your
parent installation directory for values. These values are stored in two lines that
start with PE= and LT=. These lines are present only if the configuration is set.
See “Sybase IQ cannot find license for an optional feature, even though the
license exists” on page 128 for more information.

Sybase IQ shows graced licenses even after the issue has been
fixed
Sybase IQ performs license checks periodically, and the license status is not
immediately updated. It is updated only after the next heartbeat cycle is
completed. This may take a few hours.

Sybase IQ cannot find license for an optional feature, even though

the license exists
Execute sysam diag feature_name to ensure that the license for the optional
feature exists and can be checked out from the machine where Sybase IQ is
running. If the feature exists, but cannot be checked out from Sybase IQ, this
could be because:
• The optional feature is for a different edition.
• The Active or Standby flags do not match for base Sybase IQ and the
optional feature.
Execute sp_iqlmconfig to determine the edition and active and standby
configuration value. The edition and active and standby values are displayed in
the Property Name / Property Value table. The edition value is displayed in the
PE row and active and standby value is displayed in the AS row.
Compare the values of PE and LT for Sybase IQ with the same values recorded
in the VENDOR_STRING and ISSUER fields of the optional feature license. If
these values do not match, call technical support.

128 Sybase IQ
 APPENDIX B Troubleshooting SySAM

Sybase IQ does not start with the expected edition or license type
If the edition and license type configuration parameters are not set, Sybase IQ
uses the first available IQ_CORE license. If you have multiple IQ_CORE
licenses with different editions and license types, which license is the first
available depends on many factors such as license file directory sort order,
available licenses on the license server, and so on.
Because the edition and license type cannot be guaranteed, Sybase
recommends that you set the edition and license type configuration parameters.
When these parameters are set, you are assured that Sybase IQ starts with that
configuration. If a matching license were to be unavailable, Sybase IQ starts
under grace (if available) to allow you to resolve the licensing issue.

Sybase IQ does not pick the correct license

When Sybase IQ looks for a license, it does so in the following locations:
• Any saved values in the registry on Windows platforms, or the .flexlmrc
file on UNIX platforms. Use lmpath -status to view the saved values.
• The values set for SYBASE_LICENSE_FILE and LM_LICENSE_FILE
environment variables.
• All license files (any file with a .lic extension) in the licenses directory
under the SYSAM-2_0 directory.
• All of the above locations are searched in the order specified until a
suitable license is found. When a directory is specified, license files in that
directory are loaded in the directory sort order.
• The first license that matches the feature name, version, edition, and
license type filter is used. This license may not be what you were
expecting to use. Adjust the above locations to control this.

Installation and Configuration Guide 129

Diagnosing SySAM issues

130 Sybase IQ
Index

A Sybase IQ client 40
client installation
accessibility
client components 40
documentation xv
demo database 41
Adaptive Server Enterprise
overview 40
inserting data from 101
parent installation directory 41
Add Service utility 93
prerequisites 40
adding IQ as a Windows Service 93
running the installer 41
adding startup switches 52
samples directory 41
Administrator privilege
Sybase IQ installation directory 41
granting to IQ as a Windows service 94
typical installation 41
after upgrading
COMMLINKS parameter 100
updating configuration files 87
compliance
autostarting database 57
section 508 xv
AUTOSTOP parameter 100
components
certifications xii
configuration files 92
B security 92
configuration parameters
backing up databases set by start_asiq 37
after upgrade 87 connecting
procedure 87 using OLE DB 100
BLANK PADDING connection parameters 100
migration 62 connections
blank users 61 restricting 46
constraints
migration 62
unenforced 62
C conventions
cache sizes 56 documentation xiii, xiv
catalog cache 56 syntax xiii
certifications typographic xiv
documentation
updated xii
changing hardware platforms 45
client components 40 D
installing 39 data migration
jConnect 40 extract directory 59
ODBC 40 data sources
Sybase Central 40 setting up 98

Installation and Configuration Guide 131

Index

data storage changes accessibility features xv

migration 48 certifications xii
database conventions xiii, xiv
autostarting 57 on CD xi
encrypted 55 online xi
database migration SQL Anywhere x
iqunload 47 Sybase IQ ix
database options drivers 95
migrating 48 DSEDIT 101
database schema
unloading 58
databases
backing up 87 E
connection parameters 100 EBFs xiii
invalid names 62 empty user names 61
migrating 48 encrypted databases 55
sample xv ENG parameter 100
upgrading 58 environment variables
verifying 69, 79, 83 extract directory 59
DBF parameter 100 Evaluation edtion
dbspace size evaluation period 3
specifying during migration 53 evaluation period 3
dbspace,default 49 Event log
dbspaces suppressing entries 93
disk space for 7 extract directory 59
files 48
logical names 48
migrating 48
temporary 48 F
DECLARE LOCAL TEMPORARY TABLE statement Fast Projection indexes 63
migration 63 Federal Rehabilitation Act
default installation directory 26 section 508 xv
DEFAULT_DBSPACE option 49 file changes
demo database migration 50
directory location 41 file data sources 99
name changes 34 file ID 48
owner 34 files
Demo/Evaluation Edition after upgrade 48
license 16 fin_code
diagnosing SySAM problems 123 name change 34
Directory Services Editor 101 fin_data
diskspace name change 34
required 6 firewalls 102
diskspace and memory first time installations
see preinstallation tasks 8 planning installations 4
documentation FLEXNET

132 Sybase IQ
 Index

download page 18 server 26

utilities 18 installer
FLEXnet Licensing FLEXnet Licensing End User license server installation 21
Guide 17 running 21, 29
function running client install 41
migration 64 interfaces file
adding entries 101
IQ Agent 109
IQ Local Stores
G migrating 73
generating 19, 20 IQ Main Store
generating licenses 19 filename 53
Getting Started CD xi iq_main dbspace 49
grace mode 31 IQ_SYSTEM_MAIN
grace mode, SySAM 120, 121 on raw device 53
IQ_SYSTEM_MAIN dbspace 48
IQ_SYSTEM_MAIN store
size 53
H IQ_SYSTEM_TEMP dbspace 48
hardware platform iqdemo database
changing 5, 45 table names 34
host host name (licensing) 18 iqlsunload
host ID (licensing) 18 about 58
host IDs and network adapters 18 migration utilities 58
parameters 59
permissions 62
running 59
I syntax 59
iAnywhere JDBC driver 95 usage 60
indexes utilities
migration 62 unload 58
one-byte FP 63 iqlsunload utility
initialization file about 58
creating 101 iqunload 47
INOUT parameters 64 database migration mode 47
Installation logging errors 56
first time installations 4 migration 47
planning 4 parameters 51
upprading from a previous version 5 schema unload mode 47
installation syntax 51
installating a license serverr 21 troubleshooting connection 56
media 3 understanding 51
running the installer 21, 29 usage 54
installation directory very large schemas 58
IQ installation directory variable 29 working with large schemas 57
parent installation directory variable 28 utilities

Installation and Configuration Guide 133

Index

unload 47 License Utilities 27

iqunload logging 56 Network License Server 27
iqunload utility overview 14
about 47 port number 18
ISQL steps before you generate a license 17
connections 101 Sybase Product Download Center 14
Sybase Software Asset Management 27
SySAM documentation 17
SySAM server components 27
J licensing requirements
jConnect evaluation edition 3
client component 40 general requirements 3
server component 27 licensed edition 3
jConnect driver 95 SySAM 3
JDBC local stores
configuring connections 101 moving 73
join indexes locating SySAM errors 120
migration 62 logging
joins extra 56
migration 64

M
L main cache 56
large schemas main store
iqunload 57 filename 53
license key reserve size 53
server installation 26 size 53
license models 17 maintenance
unserved 17 software xiii
license server maintenance, product xiii
installing 21 memory
reread command 22 required 6
starting 22 migrating data
status command 22 from 32-bit to 64-bit 43, 45
License Utilities 27 from one platform to another 43, 45
Licensed edition 3 from prior Sybase IQ version 43, 45
licensing 19, 20 migrating databases
available licenses 14 multiplex 70
FLEXNET commands 18 option changes 48
FLEXNET utilities 18 procedure 48
host ID (obtaining) 18 simplex 66
host IDs and network adapters 18 migrating simplex databases 66
host name 18 task summary 66
license key 26 migration
license models 17 BLANK PADDING 62

134 Sybase IQ
 Index

changing hardware platforms 45 Network License Server 27

constraints 62 -new_startline parameter 52, 56
data storage changes 48
errors, avioding 62
extract directory 59
file changes 50 O
FP indexes 63 object names
functions 64 invalid 63
indexes 62 ODBC
invalid SQL syntax 63 driver managers 97
join indexes 62 ODBC data sources
local stores 73 creating 98
logging 56 odbc.ini file 100
migration utilities 47 OLE DB provider 100
overview 44 Open Client
schema reload 48 connecting from 101
setting page size 51 operating system patches
simplex databases 66 see preinstallation tasks 7
triggers 63 OUT parameters 64
unenforced constraints 62 outer joins
unsupported objects 62 Transact-SQL 64
upprading from a previous version 44 overview
using raw device for IQ_SYSTEM_MAIN 53 client installation 40
views 64 server installation 26
migration utilities
iqlsunload 58
iqunload 47
-ms_filename parameter 53 P
-ms_reserve parameter 53 page size
-ms_size parameter 53 migrated database 51
multiplex parameters
local stores 73 iqlsunload 59
multplex database migration iqunload 51
workflow 70 iqunload utility 51
MySybase passwords
creating personalized view xii protecting 92
EBFs xiii permissions
iqlsunload 62
planning installations 4
platforms, supported 2
N platforrms
named pipes changing 5, 45
Sybase IQ use of 101 port number (licensing) 18
names post-installation tasks
invalid 63 server 31
network adapters and host IDs 18 preinstallation 7

Installation and Configuration Guide 135

Index

preinstallation tasks 7 served 17

available diskspace and memory 8 served licenses 17, 20
increasing the swap space 8 server
operating system patches 7 not found 56
privilege server components
Administrator 94 jConnect 27
product edtion 26 License Utilities 27
product manuals xi Network License Server 27
protocols ODBC 27
supported 101 Sybase Central 27
PWD parameter 100 Sybase IQ client 27
Sybase IQ server 27
SySAM 27
server configuration files 92
R server installation
raw device default installation directory 26
specifying during migration 53 grace mode 31
readme.txt file 109 installation directory 26
reloading 58 installing server components 29
requirements IQ directory variable 29
disk space 6 overview 26
memory 6 parent directory variable 28
reserve size parent installation directory 28
specifying during migration 53 plug-in compatibility 27
reserved words 63 post-installation tasks 31
prerequisites 26
server components 27
Sybase IQ installation directory 29
S server installation options 6, 7
sales_order server objects
name change 34 adding 101
sample database xv servers
name changes 34 stopping 38
owner 34 setting server configurations 92
samples shared memory 101
directory 41 simplex database migration 66
schema 58 task summary 66
schema reload workflow 66
migration 48 simplex migration
schema unload database verification (sp_iqcheckdb) 67
iqunload 47 Single Application Edition (SA)
schema-only unload 54 license 16
schemas limits set by license 16
iqunload 58 Small Business Edition (SE)
section 508 license 16
compliance xv limits set by license 16

136 Sybase IQ
 Index

sp_iq_process_login procedure 57 Network License Server 27

sp_iq_process_post_login procedure 57 Network License Utilities 27
sp_iqcheckdb 67 overview 14
verifying databases 79 served licenses 20
verifying upgraded databases 69, 83 steps before you generate a license 17
sp_iqlmconfig Sybase SySAM server components 27
verifying your license 31 SySAM documentation 17
standards troubleshooting 119
section 508 compliance xv unserved licenses 19
startup parameters SySAM documentation
required 37 FLEXnet Licensing End User Guide 17
startup switches Quick Start Guide 17
migration 52 Users Guide 17
stored procedures 64 SySAM licenses
support, technical xvi Demo/Evaluation Edition 16
swap space 8 Enterprise Edition 14
increasing 8 FLEXNET commands 18
preinstallation tasks 8 FLEXNET utilities 18
Sybase Central host ID (obtaining) 18
requirements 109 host IDs and network adapters 18
setup 109 host name 18
Sybase IQ license models 17
and TCP/IP 101 port number 18
product edition 26 Single Application Edition (SA) 16
product editions 2 Small Business Edition (SE) 16
starting 36 SySAM server components 27
stopping 38
supported platforms 2
supported protocols 101
Sybase IQ Service T
granting Administrator privilege 94 tables
Sybase Product Download Center (SPDC) 14 invalid names 62
SyBooks CD xi not found 63
syntax sample database 34
documentation conventions xiii TCP/IP
invalid SQL syntax 63 and Sybase IQ 101
iqlsunload 59 tuning Sybase IQ performance under 102
iqunload 51 technical support xvi
SySAM SySAM problems 121
available licenses 14 To 31
calling technical support 121 Transact-SQL outer joins 64
diagnosing problems 123 triggers
generating licenses 19 migration errors 63
grace mode 120, 121 troubleshooting
license key 26 SySAM 119
locating errors 120 typographic

Installation and Configuration Guide 137

Index

conventions xiv W
typography
wide tables
documentation xiii
migrating 55
Windows Service
adding IQ as 93
U adding Sybase IQ servers 93
workflows
UID parameter 100
first time installations 4
unenforced constraints 62
installation and migration 4
unload utility
multiplex database migration 70
about 47
simplex database migration 66
unloading schema only 54
upgrading installations 5
unserved licenses 17, 19, 20
updating
configuration files 87
upgrading databases 48
upgrading from a previous version
migration 44
planning 5
usage
iqlsunload 60
iqunload 54
user names
empty 61
users
blank 61
invalid names 62
utilities
migration 47
start_asiq 36
utility database 46

V
variable
IQ installation directory 29
parent installation directory 28
verifying databases
after upgrade 69, 83
before upgrade 79
procedure 69, 79, 83
verifying your license 31
views
invalid 55, 64
MySybase, creating personalized xii

138 Sybase IQ
Installation and Configuration Guide 139
140 Sybase IQ
Installation and Configuration Guide 141
142 Sybase IQ