Download Sybase IQ

Installation and Configuration Guide
Sybase IQ
15.2
[ WINDOWS ]
DOCUMENT ID: DC30056-01-1520-01
LAST REVISED: May 2010
Copyright © 2010 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 .......................................................................................................................... vii
CHAPTER 1
Preparing for Installation................................................................ 1
About Sybase IQ .............................................................................. 1
Product editions......................................................................... 1
Platforms and operating systems .............................................. 2
Supported platforms for the network client ................................ 2
Updated software components.................................................. 2
Licensing requirements ............................................................. 3
Installation media ...................................................................... 3
Planning your installation ................................................................. 3
InstallingSybase IQ for the first time.......................................... 3
Upgrading from an earlier version ............................................. 4
Changing hardware platforms ................................................... 5
Preinstallation tasks ......................................................................... 6
Check for operating system patches ......................................... 6
Increase the swap space........................................................... 6
Sybase IQ 15.2 requires a new license server .......................... 7
Enable 4GT ............................................................................... 8
Windows support issues............................................................ 8
Verify network functionality...................................................... 10
Installing your software .................................................................. 10
CHAPTER 2
Licensing your software...............................................................
Sybase Product Download Center ................................................
Available licenses...........................................................................
Enterprise Edition (EE) ............................................................
Small Business Edition (SE)....................................................
Single Application Edition (SA)................................................
Evaluation Edition....................................................................
Before you generate your license ..................................................
Read the SySAM documentation ............................................
Decide on the license model you want to use .........................
Installation and Configuration Guide
11
11
12
12
13
14
14
14
15
15
iii
Contents
Get your host ID ......................................................................
Determine the host name ........................................................
Choose a port number.............................................................
Generate your SySAM license .......................................................
Unserved licenses ...................................................................
Served licenses .......................................................................
Installing a new license server .......................................................
15
16
16
17
17
18
18
CHAPTER 3
Installing Sybase IQ Server .......................................................... 23
Before you install Sybase IQ server ............................................... 23
Server components ........................................................................ 24
Plug-in compatibility ....................................................................... 24
What a server installation does ...................................................... 26
Installing Server components ......................................................... 27
Postinstallation tasks...................................................................... 29
Uninstalling Sybase IQ server........................................................ 30
CHAPTER 4
Testing installed products ............................................................ 31
Sybase IQ demo database............................................................. 31
Creating and starting the demo database ............................... 31
Running Sybase IQ Server ............................................................ 32
Stopping servers ..................................................................... 35
Running Interactive SQL queries ................................................... 35
CHAPTER 5
Installing Sybase IQ Client Components..................................... 37
Before you install Sybase IQ client tools........................................ 37
Client components ......................................................................... 38
What a client installation does........................................................ 38
Installing Windows client components ........................................... 39
Uninstalling Sybase IQ client ......................................................... 39
CHAPTER 6
Migrating Data................................................................................ 41
Upgrading from a previous version ................................................ 41
Converting to a new hardware platform ......................................... 42
Migration utilities ............................................................................ 45
Sybase IQ 15.2 Unload utility (iqunload) ................................. 45
Sybase 12.7 Local store unload utility (iqlsunload) ................. 56
Avoiding potential migration problems ........................................... 59
Addressing unsupported objects ............................................. 60
Correcting invalid SQL syntax ................................................. 60
Migrating simplex databases.......................................................... 63
Task summary......................................................................... 63
iv
Sybase IQ
Contents
CHAPTER 7
AP PE ND IX A
Verify your databases..............................................................
Shut down your 12.x server.....................................................
Migrate your simplex database ...............................................
Start the 15.2 migrated database ............................................
Verify the migrated databases.................................................
Migrating multiplex databases........................................................
Task summary.........................................................................
Synchronize and shutdown multiplex query nodes .................
Migrate your local stores .........................................................
Verify the 12.x databases before migration.............................
Start the multiplex write server in single node mode ...............
Shutdown your 12.x server......................................................
Use iqunload to migrate your database...................................
Start the 15.2 migrated database ............................................
Verify the migrated databases.................................................
Start and verify the coordinator ...............................................
Manually synchronize the secondary nodes ...........................
Start the secondary nodes ......................................................
Set the failover node ...............................................................
Postmigration tasks........................................................................
Re-create indexes for EUC_TAIWAN data .............................
Update configuration files ........................................................
Preserve database options......................................................
Back up your databases after migration..................................
64
64
65
66
66
67
67
68
70
75
77
77
77
80
80
81
81
83
83
84
84
84
84
84
Configuring Sybase IQ .................................................................
Using configuration files .................................................................
Installing Sybase IQ as a service ...................................................
Configuring backup devices ...........................................................
Configuring client connectivity........................................................
Connecting using JDBC ..........................................................
Connecting using ODBC .........................................................
Connecting using OLE DB ......................................................
Connecting using Open Client.................................................
Running client and server on the same system ......................
Network issues for IQ servers .................................................
87
88
90
90
91
91
96
96
97
97
87
Silent Installations ........................................................................ 99
Installing IQ silently ........................................................................ 99
Task summary ................................................................ 100
Editing the installation parameters ........................................ 100
Running a silent install .......................................................... 101
Installation and Configuration Guide
v
Contents
Completing the installation ....................................................
Uninstalling IQ silently..................................................................
Editing the uninstall parameters ............................................
Uninstalling IQ components ..................................................
Sample configuration files ............................................................
SilentInstall.txt .......................................................................
SilentUninstall.txt...................................................................
AP PE ND IX B
102
103
103
103
105
105
110
Troubleshooting SySAM ............................................................. 113
Where to look for SySAM-related errors ...................................... 113
SySAM grace mode ..................................................................... 114
SySAM grace period .................................................................... 114
Enabling and changing e-mail notifications.................................. 114
Calling Sybase technical support for SySAM-related issues ....... 115
License checkout and verification ................................................ 115
Diagnosing SySAM issues ........................................................... 117
Cannot find license type during the Sybase IQ installation ... 117
The installation program produces a warning about not finding a
suitable license ............................................................... 118
The license server executables and scripts are not installed 118
The license server does not start .......................................... 119
The license server does not recognize the license files ........ 119
Sybase IQ does not start, and generates a license check-out
failure error ..................................................................... 120
Sybase IQ cannot check out a license and starts with graced
license instead................................................................ 120
Sybase IQ shows graced licenses even after the issue has been
fixed ................................................................................ 122
Sybase IQ cannot find license for an optional feature, even though
the license exists ............................................................ 122
Sybase IQ does not start with the expected edition or license type
122
Sybase IQ does not pick the correct license ......................... 123
Index ........................................................................................................................................... 125
vi
Sybase IQ
About This Book
Audience
The Sybase® IQ 15.2 Installation and Configuration Guide for Windows
tells you how to install Sybase IQ 15.2.
Related Sybase IQ
documents
The Sybase IQ 15.2 documentation set includes:
•
Release Bulletin provides information about last-minute changes to
the product and documentation.
•
Installation and Configuration Guide provides platform-specific
instructions on installing, migrating to a new version, and configuring
Sybase IQ for a particular platform.
•
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.
•
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.
•
New Features Summary Sybase IQ 15.2 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:
Installation and Configuration Guide
vii
•
Related SQL
Anywhere
documentation
•
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.
•
Time Series Guide describes SQL functions used for time series
forecasting and analysis. You need RAP – The Trading Edition Enterprise
to use this product option.
•
Unstructured Data Analytics in Sybase IQ explains storage and retrieval
of unstructured data within the Sybase IQ data repository. You need a
separate license to install this product option.
•
User-Defined Functions Guide provides information about the userdefined 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.
Because Sybase IQ shares many components with 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.
Documentation for SQL Anywhere includes:
•
viii
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.
Sybase IQ
About This Book
•
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://sybooks.sybase.com and in
DocCommentXchange at http://dcx.sybase.com/dcx_home.php.
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.
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.
Installation and Configuration Guide
ix
x
Sybase IQ
CH A PTE R
1
Preparing for Installation
Topic
About Sybase IQ
Page
1
Planning your installation
Preinstallation tasks
3
6
Installing your software
10
About Sybase IQ
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 is embedded within Sybase IQ to provide direct access to
relational and nonrelational databases on mainframe, UNIX, or Windows
servers.
Product editions
Sybase IQ is available in several editions:
•
Enterprise Edition
•
Small Business Edition
•
Single Application Server Edition
•
Evaluation Edition
Installation and Configuration Guide
1
About Sybase IQ
Platforms and operating systems
Sybase IQ analytics server is compatible with these 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
•
Microsoft Windows 7 for 32-bit and 64-bit systems
Supported platforms for the network client
Sybase IQ 15.2 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, which allow you to connect to Sybase IQ from third-party 64-bit
Windows applications, and 64-bit Windows applications written in C++.
Updated software components
Sybase IQ Server 15.2 installs the following software components, updated to
the latest versions available at release time:
2
•
Sybase jConnect™ for JDBC™ 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.
Sybase IQ
CHAPTER 1
Preparing for Installation
Licensing requirements
Sybase IQ is available in an evaluation edition, as well as several licensed
editions.
Installing an unlicensed Evaluation Edition of Sybase IQ provides 30-day
access to all features and options available in the Enterprise Edition. To run an
unlicensed database for longer than 30 days, however, you must purchase and
install an appropriate Sybase Software Asset Management (SySAM) license.
Before installing and configuring any product edition and optional features,
know which features you are licensed to use. See “Licensing your software”
on page 11.
Installation media
Sybase IQ includes installation media for server and client installations.
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
Sybase IQ installation process 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.
InstallingSybase IQ for the first time
If you are installing Sybase IQ for the first time, follow these steps:
•
Read the release bulletin for the latest information. See the special
installation instructions section for any installation instructions not
included in this document.
Installation and Configuration Guide
3
Planning your installation
•
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 “Preinstallation tasks”
on page 6.
•
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 you received from Sybase to
log in 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 23 and
“Testing installed products” on page 31.
•
Install and configure Sybase IQ client components. See “Installing Sybase
IQ Client Components” on page 37 and “Configuring Sybase IQ” on page
87.
Upgrading from an earlier version
The upgrade process depends on the version of Sybase IQ currently installed
on your system.
Sybase IQ 15.x
Sybase IQ 12.x
4
•
Uninstall Sybase IQ 15.0 before you install Sybase IQ 15.2. 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 the current version of the
client tools to connect to an earlier 15.x server, some options, tools, and
objects may not be available.
•
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 earlier than 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.2.
Understanding how these utilities work can help you plan your migration
more effectively. See “Migration utilities” on page 45.
Sybase IQ
CHAPTER 1
•
Preparing for Installation
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 63 and “Migrating multiplex
databases” on page 67.
Changing hardware platforms
If you are upgrading from an earlier 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.2.
•
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 42.
•
After you change upgrade your hardware platform, follow the appropriate
work flow in “Migrating Data” on page 41 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, 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 later versions support migration between
Windows and Linux.
Installation and Configuration Guide
5
Preinstallation tasks
Preinstallation 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.
Patches required to
run the Windows
installer
You must install these patches before you run a GUI server install:
System
x86
Patch
Microsoft Visual C++ 2005 Redistributed Package.
x64
Microsoft Visual C++ 2005 Redistributed Package for x86
systems and Microsoft Visual C++ 2005 Redistributed Package
x64 systems.
If you do not install these packages, the installer may not function correctly. If
you experience problems with an install, apply these patches, and re-run the
install. You can find these packages in the ms-redist-* folders on the Sybase IQ
installation media.
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.
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.
6
Sybase IQ
CHAPTER 1
Preparing for Installation
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.
Sybase IQ 15.2 requires a new license server
Sybase IQ 15.2 requires SySAM license server version v11.6.1 or later, which
is distributed on the installation media. Using an older SySAM server can
cause the Sybase IQ server to become unresponsive. Install the license server
before you install Sybase IQ.
You can check the version of your current SySAM license server by running:
cd %SYBASE%\SYSAM-2_0\bin\lmutil lmver lmgrd
If you currently use a license server to host SySAM licenses for other Sybase
products:
❖
Installing a new
license server
•
Uninstall your current license server
•
Install the license server distributed on the Sybase IQ 15.2 installation
media
•
Rehost your licenses
Uninstalling a SySAM license server
1
On the Control Panel, click Add or Remove Programs.
2
Choose Sybase Software Asset Management License Server and Utilities
2.
3
Click Change/Remove.
4
Follow the directions on the screen.
Sybase Software Asset Management License Server and Utilities are
distributed as part of the Sybase IQ 15.2 installation media. To install a new
license server, see “Installing a new license server” on page 18.
Installation and Configuration Guide
7
Preinstallation tasks
Important!
If you plan to install a license server on Windows 7, you must start and stop the
license server as Administrator.
Rehosting SySAM
licenses
Rehost your SySAM licenses after you install the new license server. See
“Regenerating, renewing, and rehosting licenses” in Chapter 2, Generating
Licenses at SPDC”, in the Sybase Software Asset Management 2 Users Guide.
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
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:
8
Sybase IQ
CHAPTER 1
Preparing for Installation
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
operations agent
Certain actions require privilege elevation to execute when run under User
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).
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
executables signed
Sybase IQ executables are signed by Sybase, Inc.
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.
Installation and Configuration Guide
9
Installing your software
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 installations options
available.
Interactive
installations
Interactive installations let you set up your software in a graphic user interface
(GUI) environment. The interactive installer is wizard-driven and supports all
product editions and installation types.
Silent installations
Silent installations let you install Sybase IQ from the command line. Silent
installations are script-driven and configured to perform typical installations
by default; custom installs require additional configuration. See “Silent
Installations” on page 99.
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 to install. You can select group packages, individual
items, or a combination of the two.
10
Sybase IQ
CH A PTE R
2
Licensing your software
Generate your SySAM license before you install your server or client
components.
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.
Topic
Sybase Product Download Center
Page
11
Available licenses
Before you generate your license
12
14
Generate your SySAM license
Installing a new license server
17
18
Sybase Product Download Center
When you purchase a Sybase product, you receive an e-mail message or a
Web key that tells you how to log in to the Sybase Product Download
Center (SPDC). SPDC is an online Web portal from which you download
and license your software. You must use SPDC to dynamically generate
license keys for Sybase IQ.
The e-mail message or Web key also provides specific product and
licensing information. Use this information when you generate your
licenses.
Installation and Configuration Guide
11
Available licenses
Available licenses
Available licenses are determined by the product edition and options you
purchase.
Enterprise Edition (EE)
Orderable
License
Actual License
Required
Optional
Description
CPU
IQ_CORE
LOMO
IQ_LOB
•
License restricts the number of cores
(not CPUs) which an IQ server can use.
•
Allows you to create and use CLOB or
LOB columns. The number of LOB
licenses must match number of cores.
IQ_LOB license is included for
customers who purchase an IQ_UDA
license. An IQ_LOB license is also
available as a separate purchase option.
VLDB MO
IQ_VLDBMGMT
•
This license is required for 12.6 or 12.7
customers who already have a LOB
license (IQ_LOB).
Allows you to create multiple table
spaces and additional IQ dbspaces
beyond the defaults allowed. You are
allowed one IQ_SYSTEM_TEMP
dbspace, one IQ_SYSTEM_MAIN
dbspace, and one additional user
defined main store dbspace. To create
any additional IQ dbspace requires the
IQ_VLDBMGMT license. This license
restricts the ability to create table
partitions. An IQ_VLDBMGMT is
required whenever an IQ server creates
or starts with two or more IQ 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.
12
Sybase IQ
CHAPTER 2
Orderable
License
ASO
MPXO
IDBA-PSO
UDA
Actual License
Required
IQ_SECURITY
IQ_MPXNODE
IQ_UDF
Optional
•
Description
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).
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.
•
IQ_UDA
Licensing your software
•
This license is required for 12.6 or 12.7
customers who are already running
multiplex. This is a new license
requirement.
Allows you to define and run highperformance scalar and aggregate userdefined functions.
This license is only available with
approved third-party libraries.
Allows you to use the IQ Text Search
functionality, which lets Sybase IQ
search unstructured and semi-structured
data. An IQ_UDA also includes an
IQ_LOB license.
This license applies to IQ TEXT indexes.
Small Business Edition (SE)
Orderable
License
CPU
Actual License
Required
Optional
Description
IQ_CORE
Installation and Configuration Guide
•
Licenses the number of sockets (not
CPUs) which an IQ server can use.
13
Before you generate your license
Other limits set by the SE license
•
Server checks out licenses equal to the number of sockets. One license
allows one socket, and you can have up to four licenses. The total number
of cores should never exceed 4 (MAXCP).
•
Total concurrent IP connections <= 25 (MC)
•
Total main store <= 250GB (MS)
Single Application Edition (SA)
Orderable
License
Actual License
CPU
IQ_CORE
Other limits set by the
SA license
Required
Optional
Description
•
Licenses the number of cores (not
CPUs) which an IQ server can use.
•
Total cores per server <= 64 (MAXCP)
•
Total number of user tables <= 25 (MT)
•
Total number of columns <= 100 (MV)
•
Total number of mpx nodes <= 1 (MSN)
Evaluation Edition
No license is required for the Evaluation Edition, which 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.
Before you generate your license
Follow these steps before you generate your license.
14
Sybase IQ
CHAPTER 2
Licensing your software
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 from 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 programs. 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.
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
Installation and Configuration Guide
15
Before you generate your license
You can also use a system-level command to find the host ID. For platformspecific commands and examples, see Hostids for FLEXnet Licensing-Supported
Platforms at http://www.flexerasoftware.com/products/flexnetpublisher/requirements.htm. For additional information, see the FAQs at 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 loopback 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 may 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, specify a port number outside of this range.
16
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.
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.
❖
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:
8
•
Choose Unserved license, then click Next.
•
Specify the number of licenses to generate, then 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.
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.
Note You can now install Sybase IQ server components. During installation,
the installer prompts you for license information.
Installation and Configuration Guide
17
Installing a new license server
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.
❖
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:
8
•
Choose Served License, then click Next.
•
Specify the number of licenses to generate, then click Next.
•
Identify the host ID, host name, and port number of the license server.
Host name and port number are optional. Click Generate.
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.
Note 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 18.
Installing a new license server
If you chose a served license model, you must install a new license server.
18
Sybase IQ
CHAPTER 2
Licensing your software
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 need not run the
license server on the same machine as 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, then click Next.
5
Choose Evaluation as the product edition you want to configure, then 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, then click
Next.
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
Use these instructions to start and stop a license server on all Windows
platforms, except Windows 7. To start a license server on Windows 7, see
“Starting your license server on Windows 7” on page 20.
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.
Installation and Configuration Guide
19
Installing a new license server
2
Change to %SYBASE%\%SYSAM-2_0\%bin, then refresh or restart the
license server:
Use this command
To...
sysam start
Start the license server.
sysam reread
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.
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
❖
Starting your license server on Windows 7
You must start and stop a license server on Windows 7 as Administrator.
1
Click Start, choose Programs | Accessories.
2
Right-click Command Prompt, choose Run As Administrator.
3
Copy the license file you saved from SPDC to the %SYBASE%\SYSAM2_0\licenses directory on the network license server.
4
Change to %SYBASE%\%SYSAM-2_0\%bin, then refresh or restart the
license server:
Use this command
To...
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.
20
Sybase IQ
CHAPTER 2
Licensing your software
Use this command
To...
sysam reread
Make the license server read the new license
file.
Perform this step if the license server is already
started.
5
Use the sysam status command to verify that the license server is running.
Notes
•
To verify your license, 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. Use the sysam configure [IPv6|IPv4]
to configure the appropriate version of the license server.
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 113
Installation and Configuration Guide
21
Installing a new license server
22
Sybase IQ
CH A PTE R
3
Installing Sybase IQ Server
Installing Sybase IQ server is part of a planned installation sequence.
Follow the installation path you chose in “Planning your installation” on
page 3. Read this section for information you should know before you
begin your server installation.
Topic
Before you install Sybase IQ server
Page
23
Server components
Plug-in compatibility
24
24
What a server installation does
Installing Server components
26
27
Postinstallation tasks
Uninstalling Sybase IQ server
29
30
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, Verify that there is sufficient disk space and memory,
and make any necessary configuration changes. See “Preinstallation
tasks” on page 6 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 11.
•
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.
Installation and Configuration Guide
23
Server components
•
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 GUI installer, see “Silent
Installations” on page 99.
Server components
Server components are grouped by feature. In this table, items marked as
default are installed in a typical installation.
Feature
Components
Sybase IQ
Sybase IQ server
Sybase IQ client
•
•
Sybase IQ ODBC
Sybase Central Viewer
•
•
Sybase Central plug–in
•
•
Sybase Central
jConnect
Sybase Software Asset
Management
Default
Network license server
License utilities
•
Notes
Installs server software, client
tools, and ODBC drivers.
Viewer and plug-in are required
for Sybase Central.
Required for JDBC connections.
Network license server utilities,
and FLEXnet Licensing utilities
Plug-in compatibility
Sybase Central is an administration console for Sybase products. The Sybase
IQ server 15.2 plug-in for Sybase Central is not compatible with 12.x servers.
You can use the 15.x plug-in with 15.x servers; you cannot use it to connect to
12.x servers.
24
Sybase IQ
CHAPTER 3
Sybase
Central
toolkit
Installing Sybase IQ Server
IQ plug-in
Sybase IQ
Agent
JRE
15.x
Compatible only with 15.x servers. You
cannot use the 15.x plug-in to connect to 12.x
servers.
6.0 or later
required
15.x agent
required
JRE – 6.0
required
12.7
12.5 and later fully supported. Earlier IQ
versions minimally supported.
4.3 or later
required
12.7 agent
required
1.4.2
required
12.6
12.6 or 12.5 fully supported. Earlier IQ
versions minimally supported.
12.5 or earlier
4.3 or later
required
3.2 required
12.6 agent
required
12.5 agent
required
1.4.2
required
1.2.2
required
(1.3.1 on
Linux)
12.5
Installation and Configuration Guide
25
Plug-in compatibility
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
directory
The parent directory contains files, scripts, and other objects required to
support Sybase IQ server.
The default installation directory is C:\Sybase. You can, however, specify
another target directory during the installation process. 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
charsets
Contents
Character sets available for use with Adaptive Server.
collate
ini
Collation sequences available for use with Adaptive Server.
Various configuration files.
IQ-15_2
Subdirectories, scripts, and property files required to run
Sybase IQ server.
Java Database Connectivity (JDBC) driver for Sybase IQ.
jConnect-6_0
locales
shared
Language modules for system messages and date/time formats.
Components and libraries shared by several other components,
including Sybase Central and Java Runtime Environment
(JRE).
SYSAM-2_0
SySAM licenses and utilities. This directory contains two
subdirectories: bin and licenses.
Subdirectories for scripts that uninstall IQ and SySAM.
uninstall
26
Sybase IQ
CHAPTER 3
Sybase IQ installation
directory
Installing Sybase IQ Server
The Sybase IQ installation directory is IQ-15_2, and is a subdirectory within
%SYBASE%.
This directory contains files, scripts, and other objects required to run Sybase
IQ server. This document uses the variable %IQDIR15% 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
bin<platform>
ADO.NET and .NET assembly files.
Utilities you use to start and manage your server. <platform> value is
64 or 32 depending on your installation.
charsets
demo
install
Character encoding files.
A readme that identifies the location of the demo database scripts and
sample data: C:\Documents and Settings\All Users\SybaseIQ\demo
directory.
Installation history file.
java
logfiles
Different JAR files.
Various logfiles. Sybase IQ writes log files to this directory.
lsunload
scripts
Local Store Unload utility.
Sample scripts and stored procedures.
SDK
snmp
Subdirectories for various language utilities.
Definitions for Simple Network Management Protocol servers.
sun
Sysam
Local copy of the JRE to support Java in the database.
Local SySAM configuration information.
support
unload
A Web page with links to online resources.
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 installation.
2
Insert the Sybase IQ product DVD into the drive.
Installation and Configuration Guide
27
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, then 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
28
When the installer prompts you for the Sybase IQ license key, do one of
the following:
•
Open the license you downloaded from the SPDC site, and paste the
license in the license key text box. Do this only if you are installing
an unserved license.
•
Click Browse, navigate to where you stored your license location, and
select it. Do this only if you are installing an unserved license.
•
Click “Use previously deployed license server,” then specify the
server’s host name and port number. Use this option to use a
previously deployed license server.
•
Click “Continue installation without a license key” to install Sybase
IQ in grace mode.
8
Click Next, then choose the appropriate product edition and license type.
9
Follow the instructions on the screen to complete your installation.
Remove the installation media from the drive.
Sybase IQ
CHAPTER 3
Installing Sybase IQ Server
Notes
•
If you install Sybase IQ in grace mode, you can install the product without
a license, and activate a 30-day 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.
Postinstallation 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 Sybase IQ version 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, see “Migrating Data” on page
41.
•
See “Testing installed products” on page 31 for information about starting
your server, running queries, and working with the demo database.
•
See “Installing Sybase IQ Client Components” on page 37 for
information about installing Sybase IQ Client tools.
•
If you are unfamiliar with Sybase IQ and the Sybase Central management
console, see Introduction to Sybase IQ for exercises and examples.
Installation and Configuration Guide
29
Uninstalling Sybase IQ server
Uninstalling Sybase IQ server
❖
❖
30
Uninstalling from the Control Panel
1
On the Control Panel choose Add or Remove Programs.
2
Choose Sybase IQ 15.2 from the program list.
3
Click Change/Remove.
4
Follow the instructions on the screen.
Uninstalling from Windows Explorer
1
In Windows Explorer, change to %SYBASE%\uninstall\IQ.
2
Double-click IQuninstall.
3
Follow the instructions on the screen.
Sybase IQ
CH A PTE R
4
Testing installed products
This chapter tells you how to start Sybase IQ and use the demo database
to test your installation.
Topic
Sybase IQ demo database
Page
31
Running Sybase IQ Server
Running Interactive SQL queries
32
35
Sybase IQ demo database
Many of the examples throughout the documentation use the Sybase IQ
sample database, iqdemo.db, as a data source. The demo database
represents a small company that makes a limited range of sports clothing.
Sample data includes internal information about the company (employees,
departments, financial data), product (products), and sales information
(sales orders, customers, and contacts).
Creating and starting the demo database
To use the demo database to test your installation, create iqdemo.db and
load the sample data. Scripts that create and load the demo database are
located in the %ALLUSERSPROFILE%\SybaseIQ\demo directory.
To create or start the demo database, use the Start IQ Demo Database
option from Sybase IQ 15.2 program group:
•
Click Start, point to Programs | Sybase | Sybase IQ 15.2 | Start Sybase
IQ Demo Database.
The first time you use this option, Sybase IQ may prompt you for some
additional information.
Installation and Configuration Guide
31
Running Sybase IQ Server
Table names
15.x demo database table names are different than those in the 12.x versions of
the software. Table 4-1 includes current and former iqdemo table names. If you
are upgrading from an earlier version of Sybase IQ, use this table to update the
table names or permissions in your scripts or applications.
Table 4-1: Demo database table names
12.7 name
contact
15.x name
Contacts
15.x owner
GROUPO
customer
department
Customers
Departments
GROUPO
GROUPO
employee
fin_code
Employees
FinancialCodes
GROUPO
GROUPO
fin_data
product
FinancialData
Products
GROUPO
GROUPO
sales_order_items
sales_order
SalesOrderItems
SalesOrders
GROUPO
GROUPO
emp1
iq_dummy
emp1
iq_dummy
DBA
DBA
sale
SYSOPTIONDEFAULTS
sale
DBA
DBA
Note To create the older asiqdemo version of the demo database, open a
command window, change to %ALLUSERSPROFILE%\SybaseIQ\demo, and
run this command: mkiqdemo.bat -old
Running Sybase IQ Server
Sybase recommends that you use the startup utility, start_iq, to start your server.
start_iq is a command line utility that runs on all platforms, and ensures that all
required parameters are set correctly.
Starting a server or
database
To use start_iq to start a server or database from the command line, change to
a directory where the configuration and database files are located, and use the
following command format:
start_iq [ server-options ] [ database-file
[ database-options ], ...]
32
Sybase IQ
CHAPTER 4
Default startup
parameters
Testing installed products
•
server-options include the database server name and other options that
control the behavior of the server, for all databases that are running on that
server.
•
database-file is the file name of the catalog store. You can omit this option,
or enter one or more database file names on the command line. Each of
these databases is loaded and available for applications. If the starting
directory contains the database file, you do not need to specify the path;
otherwise, you must specify the path. You need not specify the .db file
extension.
•
database-options are options that you can specify for each database file
you start, that control certain aspects of its behavior.
start_iq uses a default configuration file (%IQDIR15%/scripts/default.cfg) to
set the start-up parameters to the defaults in Table 4-2.
Table 4-2: Parameters set by start_iq
Parameter
–c
–gc
–gd
–gl
–gm
–gp
–ti
Value
48MB
Description
Catalog store cache size.
20
all
Checkpoint interval.
Allows all users to start the database by connecting.
all
10
Allows all users to load or unload tables.
Default number of connections.
4096
4400
Catalog store page size.
Client timeout set to 72 hours. Prevents users with long
queries from being logged off over a long weekend.
For a complete list of startup parameters, see “The database server” in Chapter
2 of Sybase IQ Reference Manual.
Note If SQL Anywhere is installed on the same subnet as Sybase IQ, the server
must have a unique name. Both SQL Anywhere and Sybase IQ servers default
to the port 2638.
Use a new port number for each server. Set each new port number in the
%IQDIR15%/scripts/default.cfg file. Change the following line in each IQ
database configuration file (for example,
%ALLUSERSPROFILE%\SybaseIQ/demo/iqdemo.cfg)to update the port
number:
–x tcpip{port=2638}
Installation and Configuration Guide
33
Running Sybase IQ Server
Configuration files
To override the default start-up parameters, store your options in a
configuration file, and use this command to start your server:
start_iq @configuration_filename.cfg dbname.db
This command starts the database and sets parameters named in the (optional)
configuration (.cfg) file.
On the start_iq command line, the last option you specify takes precedence, so
to override your configuration file, list any options you want to change after
the configuration file name. For example:
start_iq @iqdemo.cfg –x 'tcpip{port=1870}' iqdemo.db
The –x parameter here overrides connection information in the iqdemo.cfg file.
A configuration file for the demo database (iqdemo.cfg) is installed in the
%ALLUSERSPROFILE%\SybaseIQ/demo directory as an example. .
Default server
directories
The directory where the server is started becomes the default directory for all
server files created by Sybase IQ.
Startup and server
logs
Sybase IQ writes start-up and server logs in the
%ALLUSERSPROFILE%\SybaseIQ\logfiles directory:
•
Startup information is saved in the iq_startup_nt.log file.
•
Server status is logged in the servername.nnnn.srvlog file.
The nnnn variable in the file name indicates the number of times the server has
been started. For example, localhost_iqdemo.0006.srvlog
Starting Sybase IQ
with Sybase Central
If you have Sybase Central, you can use the Start Database Server wizard to
start the database instead of start_iq. See Introduction to Sybase IQ for more
information.
Note Always use the default colors of the Common Desktop Environment
when you run Sybase Central and dbisql. Running these products under Open
Windows or changing the default colors may cause display problems.
34
Sybase IQ
CHAPTER 4
Testing installed products
Stopping servers
To stop a server, right-click the Sybase IQ icon, and choose Shutdown. You can
also stop a server using the STOP ENGINE command from Interactive SQL or
any front-end client, or using the Stop utility. See Chapter 4, “Database
Administration Utilities” in the Sybase IQ Reference Manual for more
information.
Note When you stop a server using the DBSTOP command, you need to
specify the same parameters used to start that server.
Running Interactive SQL queries
Interactive SQL is a utility that ships with Sybase IQ that lets you execute SQL
statements, build scripts, and display database data.
Starting Interactive SQL opens a dialog that lets you define the connection
parameters to your server or database. If you need connection help, click the
arrow in the top-right corner to display a Connect Assistant.
❖
Starting Interactive SQL and running queries
Assume that iqdemo is running on a local host named localhost-xp.
1
Select Start | Programs | Sybase | Sybase IQ 15.2 | Interactive SQL.
Interactive SQL starts and displays a connection dialog
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 demo iqdemo database, the
server name is localhost-xp_iqdemo.
4
Choose iqdemo as the database. If there is only one database running, you
can leave this field blank.
5
What you do next depends on the server location:
Installation and Configuration Guide
35
Running Interactive SQL queries
•
If you are running Interactive SQL against a server installed on the
same machine, you must also choose an appropriate database file.
•
If you are running Interactive SQL 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.
7
In the SQL Statements window, type:
SELECT * FROM employees
8
To execute the query, click the right-facing triangle on the toolbar.
Notes
36
•
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.2 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.
Sybase IQ
CH A PTE R
5
Installing Sybase IQ Client
Components
This chapter tells you how to use the installation media to install the
Sybase IQ client components, which are required to connect a client to a
network server.
Topic
Before you install Sybase IQ client tools
Client components
Page
37
38
What a client installation does
Installing Windows client components
38
39
Uninstalling Sybase IQ client
39
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, verify that there is sufficient disk space and memory,
and make any necessary configuration changes. See “Preinstallation
tasks” on page 6 for specific information.
Note Instructions in this chapter are specific to the GUI installer. See
“Silent Installations” on page 99 for silent installation setup instructions.
Installation and Configuration Guide
37
Client components
Client components
Client components are grouped by feature. Items designated in the default
column are included in “Typical” installations.
Feature
Components
Default
Notes
Sybase IQ
Sybase IQ client
Sybase IQ ODBC
•
•
Installs client tools, and ODBC
drivers.
Sybase Central
Sybase Central viewer
Sybase Central plug–in
•
•
Viewer and plug–in are required
for Sybase Central.
•
Required for JDBC connections.
jConnect
What a client installation does
A typical client installation installs the network client components into a parent
directory on a client machine.
Parent installation
directory
The parent directory contains the files, scripts, and other objects required to
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 installation. This document uses the variable
%SYBASE% to refer to the parent directory.
Sybase IQ installation
directory
The Sybase IQ client installation directory, IQ-15_2, is a subdirectory within
%SYBASE%.
This directory contains subdirectories, scripts, and property files required to
run Sybase IQ client. This document uses the variable %IQDIR15% to refer to
the Sybase IQ installation directory on the client.
Demo database and
samples directory
38
C:\Documents and Settings\All Users\SybaseIQ contains subdirectories for the
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.
Sybase IQ
CHAPTER 5
Installing Sybase IQ Client Components
Installing Windows client components
The Sybase IQ Windows client installer includes a single setup wizard for all
product editions.
❖
Installing Sybase IQ Client Tools on Windows
1
Log in to Windows using an account with Administrator privileges. Stop
and shut down all programs.
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, and choose the batch file to start the
installer (setup32.bat or setup64.bat).
3
On the Welcome screen, click Next.
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.
6
Follow the instructions on the screen.
Note Because Sybase distributes the 32-bit and 64-bit Windows client on the
same installation CD, you can install the 32-bit client on a 64-bit machine.
However, installing a client with a particular word size installs only those
drivers that match the word size of that particular client. This means that 32-bit
client installations only install 32-bit drivers; 64-bit client installations only
install 64-bit drivers.
Although you can install the 32-bit client on a 64-bit machine, you must use a
driver with the appropriate word size for a particular device or application. To
use a 32-bit client application to connect to IQ, for example, you must use a 32bit driver. 64-bit client applications require 64-bit drivers.
Uninstalling Sybase IQ client
❖
Uninstalling Windows client components
1
On the Control Panel, choose Add or Remove Programs | Sybase IQ 15.2.
2
Click Change/Remove.
Installation and Configuration Guide
39
Uninstalling Sybase IQ client
3
40
Follow the instructions on the screen.
Sybase IQ
CH A PTE R
6
Migrating Data
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.2 before you migrate your 12.x databases. Sybase IQ
15.2 includes tools that you can use to migrate your databases.
Topic
Upgrading from a previous version
Page
41
Converting to a new hardware platform
Migration utilities
42
45
Avoiding potential migration problems
Migrating simplex databases
59
63
Migrating multiplex databases
Postmigration tasks
67
84
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 earlier than
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.
Installation and Configuration Guide
41
Converting to a new hardware platform
•
The SORTKEY function 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 earlier
than 15.0 do not contain the same values created using version 15.0 and
later. Regenerate any sort-key values in your database that were generated
using a version of Sybase IQ earlier than 15.0.
•
Sybase IQ 15.2 no longer supports creating 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 unload the database, then load the
schema and data into a database that you create, then you must use one of
the supplied collations.
•
Back up 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.
•
To effectively plan you migration, review and understand the database
migration utilities. Sybase IQ 15.2 includes an iqunload utility that you can
use to re-create the schema for your database or simply migrate your
database from 12.x to 15.2. An iqlsunload utility is available for 12.7
multiplex users who need to move local stores.
•
Resolve potential migration errors before you migrate. Sybase IQ 15.2 no
longer supports some 12.x features and objects. 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 63 and “Migrating multiplex
databases” on page 67.
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 an
earlier 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.2.
42
Sybase IQ
CHAPTER 6
Migrating Data
Notes
❖
•
If you created your Sybase IQ database on a Linux 32–bit version prior to
Sybase IQ 12.6 ESD #2, 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 later versions 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.
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 later than the version on which you were
previously running, upgrade databases, and therefore restart the server in
a way that restricts user connections. Sybase recommends using these
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 this command on the
connection where you intend to perform the upgrade:
sa_server_option 'disable_connections', 'ON'
After you upgrade, execute this command on the same connecion:
sa_server_option 'disable_connections', 'OFF'
This method precludes emergency access from another DBA connection.
Installation and Configuration Guide
43
Converting to a new hardware platform
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 You can now proceed with migrating the 12.x database to Sybase IQ
15.2.
44
Sybase IQ
CHAPTER 6
Migrating Data
Migration utilities
Sybase provides utilities you can use to migrate your 12.x data to Sybase IQ
15.2.
Sybase IQ 15.2 Unload utility (iqunload)
iqunload performs two main functions:
•
Unloads the schema from a 12.x database.
•
Migrates a 12.x database to Sybase IQ 15.2.
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.2 database to recreate the schema of the legacy database. Running iqunload
in schema unload mode lets you:
•
Verify the correctness of the schema by applying it to a new Sybase IQ
15.2 database.
•
Estimate how long the actual migration process should take.
Note Schema unload mode is not supported for Sybase IQ 12.6. 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.2. This mode does not
use your existing IQ 12.x servers. Instead, database migration mode uses a
special bundled server called iqunlspt bundled with IQ 12.7 ESD #5 or later.
Running iqunload -au:
1
Starts your old database with the iqunlspt database engine.
Installation and Configuration Guide
45
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.2 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.).
See “Understanding iqunload” on page 49 for information about prerequisites,
syntax, and examples for using the iqunload utility in both modes.
Understanding data storage changes and schema reload
Migrating to Sybase IQ 15.2 creates a new catalog store. Migration creates and
modifies system tables, system procedures, and options in the new Catalog
Store to enable 15.2 features and removes options eliminated for version 15.2.
Note Sybase IQ 15.2 preserves previous settings of database options and
reapplies them after you create the new 15.2 database. You no longer need to
run SELECT * from SYS.SYSOPTIONS before upgrading.
In Sybase IQ 15.2, 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.
For details on creating new dbspaces after migration and how to move objects
from one dbspace to another, see "Dbspace management example," in Chapter
5, "Working with Database Objects," in the System Administration Guide:
Volume 1
46
Sybase IQ
CHAPTER 6
Migrating Data
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 a different file name. 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, the new store marked as
MAIN has DBSpaceName = IQ_SYSTEM_MAIN, DBFileName =
IQ_SYSTEM_MAIN and path = new_main_store.iq. For multiplex migration,
the location of the new main store must be visible to all nodes on the multiplex,
and you must use the -ms_filename argument 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 49 for iqunload parameters that determine these specifications and their
defaults. See "Sizing guidelines for main and temporary stores," in Chapter 5,
"Working with Database Objects,” in the System Administration Guide:
Volume 1.
Examples
Schema unloading allows you to verify schema correctness and
estimates how long migration may take. For example:
Example 1
•
Make sure that you have copied the required scripts to your IQ 12.x server.
See “Correcting invalid SQL syntax” on page 60.
•
Run iqunload -n to create the empty schema. This creates a SQL file with
called reload.sql in the current directory that contains the entire schema.
The reload.sql file also contains a template CREATE DATABASE command
that is commented out.
Note The generated reload.sql does not contain any checkpoints. If you
have a very large schema, you may want to edit reload.sql and add a few
checkpoints. If you do not, IQ generates additional metadata objects that
requiring extra (-iqmc) main cache memory.
•
Use Interactive SQL or Sybase Central to create a new Sybase IQ 15.2
database with IQ SIZE and TEMPORARY SIZE clauses to create an
IQ_SYSTEM_MAIN of 10GB and IQ_SYSTEM_TEMP of 5GB.
For example:
CREATE DATABASE 'test.db'
IQ PATH 'test.iq'
IQ SIZE 10240
Installation and Configuration Guide
47
Migration utilities
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.
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 you are specifying a raw device. For a raw
device, you must specify an unused raw partition.
Example 2
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"
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:
Example 3
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:
•
iq127db.db
•
iq127db.iq
•
iq127db.iqmsg
•
iq127db.iqtmp
•
iq127db.log
After migration, the directory W:\iq-15\unload\127\db\* contains the
following:
•
48
iq127db.db – the new IQ catalog store
Sybase IQ
CHAPTER 6
Migrating Data
•
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.2 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.2 in writeable mode flags this file
as upgraded, after which it cannot be used in earlier versions.
•
iq127db.iqmsg.before_schema_reload – the original 12.6 or 12.7 message
file. This file is left intact in its premigration state in case you need
messages issued during migration while using the 12.7 unload utility
embedded in Sybase IQ 15.2.
•
iq127db.iqtmp – the Sybase IQ 15.2 temporary store.
•
iq127db.lmp – the Sybase IQ 15.2 license manager property file.
•
iq127db.db.out – output log file.
•
new_main_store.iq– the new Sybase IQ 15.2 IQ_SYSTEM_MAIN.
In addition to these files, any additional SA catalog stores are created and the
original versions are renamed with a .before_schema_reload extension.
Understanding iqunload
Syntax
iqunload [ options ]
data:[ environment variable | file ]
Parameters
The iqunload utility takes one or more parameters.
Table 6-1: iqunload parameters
Option
-ap <size>
-au
Description
(Optional) Set the page size for the new catalog store.
(Required, except when specifying -n) Migrate the
database.
You can specify-au or-n as an argument, but not both.
-c “keyword=value;...”
-dc
Installation and Configuration Guide
(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.
(Optional) Recalculate computed columns in the
database.
49
Migration utilities
Option
Description
-ms_filename
-ms_filename is optional for a simplex migration, but
required for a multiplex migration.
-ms_reserve
Specify filename for new empty IQ_SYSTEM_MAIN
store created during database migration. If not specified,
the default new main store is a file system file called
new_main_store.iq
(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, based on the database size. The minimum, assuming
a default page size, is 200MB. If the user specifies an –
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 You must use Sybase IQ 12.7 ESD 5 or later to use
this option.
-new_startline
-o <file>
-q
-r <file>
(Optional) Suppress messages and windows.
(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.
(Optional) Replace existing reload schema SQL script
with new output without confirmation.
-y
50
(Optional) Specify startup switches for the new Sybase
IQ 15.2 server that is the migration target. For a complete
list of server startup switches, see the Utility Guide.
(Optional) Log output messages to file.
Sybase IQ
CHAPTER 6
Examples
Example 1
Migrating Data
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.
Migrate the database iq_demo.db using a raw device for a new
IQ_SYSTEM_MAIN store.
Example 4
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
Usage
The specified user ID must have DBA authority.
Installation and Configuration Guide
51
Migration utilities
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 the -au parameter.
Determining switches for migration The iqunload utility starts and
communicates with a special IQ 12.7 server and the Sybase IQ 15.2 server. Use
the information in this section 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 53.
The -au parameter starts these two servers:
•
iqunlspt – aspecial unload engine based on Sybase IQ 12.7 ESD 5.
•
iqsrv15 – the new Sybase IQ 15.2 server.
Note To minimize startup times, first verify that that your server starts cleanly
in IQ 12.6 or 12.7.
By default, iqunlspt starts on your Sybase IQ 12.6 or 12.7 database with these
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.
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. The time required to start
your existing Sybase IQ 12.6 or 12.7 database is the same amount of time
required to start the iqunlspt.exe process. This time is included in the startup
time for the iqunload.exe.
iqsrv15 starts with these command line arguments:
iqsrv15 -gp 4096 -c 40p -gc 20 -gd all -gk all -gl all
52
Sybase IQ
CHAPTER 6
Migrating Data
-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.2 engine to execute many schema
DDL statements.
Both server start commands use the default values for -iqmc and -iqtc. If your
Sybase IQ 12.6/12.7 server requires larger values for startup performance,
consider adding these to the START= parameter (see below).
The iqunload utility generates script and output files in
the %IQTMP15% directory and removes them on completion.
Results of iqunload
By default, Sybase IQ allocates the lesser of 256MB or 40% of physical
memory for the Catalog Store cache size upper limit. Insufficient cache causes
iqunload errors like Tried to allocate 4167598080 bytes, failed.
You can control the upper and lower limits for the Catalog Store cache size by
setting the –ch and -cl startup switches through the StartLine [START]
connection parameter. See the Utility Guide.
Users with wide tables (large numbers of column/null values) should not
decrease the Catalog Store page size for database migration.
If the database being migrated contains invalid views, Sybase IQ completes
migration but issues user warnings. This may occur, for example, if tables
involved in a view are dropped.
If you set the IQTMP15 environment variable, you must set it to a valid
directory name.
If the database being migrated is encrypted, then you must specify the DBKEY
connection parameter to provide the encryption key for the database. The
migrated database uses the same encryption key.
The iqunload utility automatically starts the old version of the server (12.6 or
12.7) to upgrade the catalog .db file, and shuts down the old server after the
unload completes. The utility uses default values for the various cache sizes
(catalog cache, main cache, 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.
Installation and Configuration Guide
53
Migration utilities
Logging and
correcting errors
Extra logging To start the Sybase IQ 15.2 server with extra logging, use the
-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:\\iq15\\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.2, 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:\\iq15\\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.
If the iqunload utility cannot start a database, it
returns an error and echoes the command line so that you can correct errors.
Cannot start database
Server not found IA message similar to this indicates that iqunload started
the database but could not connect:
SQL error:Database server not found
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 this:
SQL error: Unable to start specified database:
autostarting database failed.
54
Sybase IQ
CHAPTER 6
Migrating Data
Obsolete stored procedures logged Migration replaces 12.7 login
procedures to support new Sybase IQ 15.2 login management functionality.
The procedure sp_login_environment replaces the 12.7 default login procedure
DBA.sp_iq_process_login and dbo.sa_post_login_procedure replaces the 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 similar to:
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 SQL Anywhere 11.0.1 > SQL Anywhere Server - Database
Administration > Configuring Your Database > Managing user IDs,
authorities, and permissions for an overview of login management
functionality.
Working with large schemas
With large schemas, the default cache settings may be too small and could
exhaust dynamic memory in the Sybase IQ 15.2 server. To increase the 15.2
server's cache memory, use the -c server switch. Use the -new_startline to pass
this switch to the 15.2 server.
A diagnostic example would includes these switches:
-ca 1
-c 1000m
-o d:\iq15console.out
Note The value shown for -c is in bytes and arbitrary. Set switches
appropriately for your system. To specify megabytes, use the m suffix, as
shown.
The switches in the example perform as follows:
•
ca 1 – enables dynamic catalog cache sizing, and logs memory cache
statistics to the console.
•
c 1000m – sets initial catalog cache at 1GB.
•
-o d:\iq15console.out – specifies the log file for console output.
Installation and Configuration Guide
55
Migration utilities
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 also helps 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, contact Sybase for assistance.
Sybase 12.7 Local store unload utility (iqlsunload)
Sybase IQ 15.2 does not support local stores. Multiple nodes can now write to
the main store. This functionality replaces the local stores functionality. Use
iqlsunload 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.2, you can find this utility in the %IQDIR15%\lsunload
directory.
Running iqlsunload
Syntax
iqlsunload [ options ] directory [ @data ]
data:[ environment variable | file
Parameters
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 procedure on the server side does 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:
directory
CREATE VARIABLE @extract_directory varchar(2048);
SET @extract_directory = '
'C:\\testIQ15\\database\\IQ127_beta2_mpx_test\\demo_r1
56
Sybase IQ
CHAPTER 6
Migrating Data
\';
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
-c “keyword=value;...”
Unload IQ local store schema and data.
Supply database connection parameters.
-h
Print out the syntax (help) for the utility.
-o <file>
Log output messages, including errors, to file.
Suppress messages and windows.
-q
-r <directory>
-t <list>
-v
-y
Usage
Specify the directory where SQL scripts are generated.
The default reload command file is reload.sql in the
current directory. The directory is relative to the current
directory of the client application, not the server.
Output listed tables only. Can specify
OwnerName.TableName or TableName alone. (Cannot
be specified with -al).
Output verbose messages.
Replace existing reload schema SQL script without
confirmation.
The iqlsunload utility requires a minimum server version of Sybase IQ 12.7
ESD #5.
The database must be running before you can 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.
iqlsunload 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
Utility Guide.
On Windows, you must specify double instead of single slashes in all path and
file names.
Run iqlsunload from within the %IQDIR15%\lsunload directory so that it picks
up updated libraries before resolving any IQ 12.7 libraries.
Installation and Configuration Guide
57
Migration utilities
Objects unloaded Unloading the local store does not unload database
objects that are not part of the local store.
The -al parameter unloads these 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.2 no longer allows users with empty user names.
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 has been encountered and that the user will not be re-created. The reload
operation ignores such users and any associated objects.
When unloading tables:
•
Join indexes, which do not exist in a local store, are unloaded only 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”
58
Sybase IQ
CHAPTER 6
Migrating Data
W:\\mydevice\\test_dir\\unload_dir
This command creates these scripts in the current directory:
Permissions
•
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 writes to the multiplex. This node could can be either
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 Sybase IQ System Administration Guide.
•
reload_data.sql – loads extracted table data. This script is executed on the
node where you ran reload_schema.sql and reloads the data extracted from
the extract_data.sql file.
You must have DBA authority to run this utility.
Avoiding potential migration problems
Sybase IQ 15.2 no longer supports some 12.x features and objects. You must
correct these items before you migrate your databases. “Addressing
unsupported objects” on page 60 tells you how to identify and update
unsupported objects and metadata. “Correcting invalid SQL syntax” on page
60 identifies syntax changes you must make before migration.
Note During migration, the 15.x server creates a message file (*.iqmsg.R) as
it reloads the generated schema. This file is normally deleted as part of a
cleanup operation for successful migrations. If the migration fails during the
reload stage, cleanup does not occur, and *.iqmsg.R remains in the unload
directory. *.iqmsg.R may contain information that can help solve your
migration problems.
Installation and Configuration Guide
59
Avoiding potential migration problems
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, or user names
Table names cannot contain double quote
characters.
Change these names.
Join indexes
User names and database names cannot
contain double quote characters, single quote,
and semicolon characters.User names and
database names cannot start or end with a
space with a space.
iqunload does not run if the database to be
migrated contains join indexes.
Database with
BLANK PADDING
OFF
iqunload searches BLANK PADDING OFF
databases for any indexes that would become
invalid after migration. iqunload fails and lists
indexes and constraints that must be dropped
and in which order.
Unenforced
constraints
qunload fails and lists unenforced constraints
Old 1–byte FP or old
2–byte FP indexes
Databases created with IQ 12.4.2 or earlier
may have these indexes. Because these
indexes were automatically created by Sybase
IQ, you cannot drop and recreate them; you
must rebuild them.
that must be dropped.
Use Sybase Central to view the join
index definitions. Copy them to a
file. Drop join indexes before
migrating data. After migrating
data, recreate the join indexes.
Drop these indexes and constraints
before the schema reloads and
recreate the indexes and constraints
after schema reload has been
completed.
Drop unenforced constraints before
proceeding with migration.
Allow iqunload to check for these
and list them. Rebuild these indexes
using sp_iqrebuildindex before
migration. See “Configuring FP(3)
indexes” in the New Features
Guide. The rebuilt indexes are
upgraded.
Correcting invalid SQL syntax
Table 6-4 contains information about elements that cause iqunload failures.
60
Sybase IQ
CHAPTER 6
Migrating Data
Table 6-4: Troubleshooting schema issues
Problem
A DECLARE LOCAL TEMPORARY TABLE statement
in 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
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
parameter name) corresponds to a reserved word
introduced in a later version of Sybase IQ or SQL
Anywhere (such as NCHAR), the reload fails. (For
reserved words, see the Sybase IQ Reference Manual
and SQL Anywhere Server SQL Reference.) For
example:
Solution
Remove the owner name.
Prefix the table name with the owner name.
Change all references to the reserved word to use
a different name. For variable names, prefixing
the name with @ is a common convention that
prevents naming conflicts.
CREATE PROCEDURE p( )
BEGIN
DECLARE NCHAR INT;
SET NCHAR = 1;
END
Views that use Transact–SQL® outer joins (by
specifying *= or =*) may not be created properly
when they are reloaded.
Add the following line to the reload script:
SET TEMPORARY OPTION
tsql_outer_joins='on'
Also set this option for your database.
Rewrite any views or stored procedures that use
Transact–SQL outer joins.
Stored procedures that use Transact–SQL outer joins
may not work correctly.
Rewrite views and stored procedures.
Functions that have OUT or INOUT parameters cannot
be reloaded.
OUT and INOUT parameters are no longer
supported. Drop these functions before
reloading.
Note If the examples in the above two tables do not apply to you, proceed to
either “Migrating simplex databases” on page 63 or “Migrating multiplex
databases” on page 67.
Installation and Configuration Guide
61
Avoiding potential migration problems
❖
Running iqunload -n
Sybase recommends that you run 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.
The generated reload.sql file contains a sample CREATE DATABASE
statement, for example:
-- CREATE DATABASE command: CREATE DATABASE 'W:\\iq15\\unload\\127\\db\\iq127db.db' LOG ON 'W:\\iq15\\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.2. 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
62
Start the utility database using the Sybase IQ 15.2 Server, and create a new,
empty, Sybase IQ 15.2 database.
Sybase IQ
CHAPTER 6
Migrating Data
5
Use Interactive SQL to run the reload.sql script that contains the unloaded
schema against the new Sybase IQ 15.2 database. This loads the schema
of the old database into an Sybase IQ 15.2 database. If there are any SQL
syntax errors, you receive warnings when running the SQL script. Ignore
the errors to get a complete list of problems. Modify the database to be
migrated to eliminate the errors found. See “Correcting invalid SQL
syntax” on page 60.
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.2 database.
Migrating simplex databases
Follow this work flow to migrate simplex databases. Review the task summary
and perform all steps in sequence.
Task summary
•
Review “Upgrading from a previous version” on page 41 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
64.
•
Shutdown your 12.x servers. See “Shut down your 12.x server” on page
64.
•
Run iqunload with the appropriate parameters to migrate your databases.
See “Migrate your simplex database” on page 65.
•
Start the migrated database in read-only mode. Update the appropriate
configuration settings and database options. See “Start the 15.2 migrated
database” on page 66.
•
Use sp_iqcheckdb to verify the migrated database. See“Verify the
migrated databases” on page 66.
•
Complete any necessary post-migration tasks. See “Postmigration tasks”
on page 84.
Installation and Configuration Guide
63
Migrating simplex databases
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
entering:
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, see 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.
Shut down 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.
64
Sybase IQ
CHAPTER 6
Migrating Data
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.2 Unload utility (iqunload)” on page 45 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. -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:\\iq15\\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"
Creating indexes for (10/14)"DBA"."alt_sales_order"
Installation and Configuration Guide
65
Migrating simplex databases
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:\iq15\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.2 migrated database
Start the migrated database in read-only mode with Sybase IQ 15.2:
start_iq -iqro 1
Update the appropriate configuration settings and database options.
Verify the migrated databases
Run sp_iqcheckdb to verify the consistency of the databases.
Note In this step, you run the IQ 15.2 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.2, 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')
66
Sybase IQ
CHAPTER 6
Migrating Data
If you run the procedure from Interactive SQL, redirect output to a file by
entering:
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, see 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 41 for steps
common to all database migrations.
•
Synchronize and shutdown multiplex all query nodes. See “Synchronize
and shutdown multiplex query nodes” on page 68.
•
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 70.
•
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 75.
•
Start the multiplex write server in single node mode. See “Start the
multiplex write server in single node mode” on page 77.
•
Shut down your 12.x server and back up your database. See “Shutdown
your 12.x server” on page 77.
Installation and Configuration Guide
67
Migrating multiplex databases
•
Run iqunload with the appropriate parameters to migrate your databases.
See “Use iqunload to migrate your database” on page 77.
•
Use the -iqro 1 -iqmpx_sn 1 switches to start the writer in READONLY
mode. See “Start the 15.2 migrated database” on page 80.
•
Run sp_iqcheckdb to verify your migrated databases, then backup the
databases. See “Verify the migrated databases” on page 80.
•
Synchronize the secondary nodes from the coordinator node. See
“Manually synchronize the secondary nodes” on page 81.
•
Start the secondary nodes, then import the schema and data for the local
stores into the coordinator. See “Start the secondary nodes” on page 83.
•
Set the failover mode for the failover node. See “Set the failover node” on
page 83.
•
Complete any necessary postmigration tasks. See “Postmigration tasks”
on page 84.
Synchronize and shutdown multiplex query nodes
When you migrate a multiplex database, check the SQL Remote and multiplex
server log files for synchronization problems.
❖
Correcting synchronization problems
1
Start the multiplex server.
2
If it is not already, start SQL Remote on all nodes in the multiplex. These
are normally started by Sybase Central when starting servers.
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. By
default, the server console log file 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
68
Sybase IQ
CHAPTER 6
Next time for 'ev_iqmpxstatus'
22:03:00.000
OS Available: 859232K, Working
Target: 11489K
OS Available: 861052K, Working
Target: 11489K
OS Available: 860972K, Working
Target: 11489K
OS Available: 850248K, Working
Target: 11579K
OS Available: 850104K, Working
Target: 11579K
Next time for 'ev_iqmpxq2w' is
22:04:00.000
Next time for 'ev_iqmpxstatus'
22:04:00.000
OS Available: 850120K, Working
Target: 11579K
Next time for 'ev_iqmpxq2w' is
22:05:00.000
Next time for 'ev_iqmpxstatus'
22:05:00.000
OS Available: 852668K, Working
Target: 11579K
4
Migrating Data
is 2008/11/23
Set: 84112K, Cache
Set: 84424K, Cache
Set: 84428K, Cache
Set: 85540K, Cache
Set: 85568K, Cache
2008/11/23
is 2008/11/23
Set: 85600K, Cache
2008/11/23
is 2008/11/23
Set: 85604K, Cache
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 SQL Remote to process any messages. For example:
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
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. See “Verify the 12.x
databases before migration” on page 75.
Installation and Configuration Guide
69
Migrating multiplex databases
Migrate your local stores
If you created local stores for your 12.x multiplex query nodes, move these
stores before migrating data to Sybase IQ 15.2. 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 requires you to consolidate node-specific information
into either the existing 12.7 writer or the new Sybase IQ 15.2 main store. You
can customize 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.
If information is duplicated across your query nodes, you may need to migrate
only 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
partitioning
If the same table exists on multiple query nodes, and each node has its own
subset of the data, you must manually edit the local store migration scripts.
❖
Partitioning query server data
For a department-specific employee table on each query server, follow these
basic steps:
1
Unload the schema and data from the query nodes.
The reload_schema.sql script produced for each query node contains 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.2 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 query node
data set.
Query server data
overlap
If the same table exists on each query node with overlapping data sets, you
must resolve the issue. You can edit the extract data files to ensure that the data
sets are unique, or you can rename the tables and then reload all the unique
tables.
❖
Addressing overlapping query server data
1
70
Run iqlsunload against all your query servers with local stores that have the
data you want to consolidate.
Sybase IQ
CHAPTER 6
Migrating Data
2
Modify the reload_schema.sql and reload_data.sql files to use the new
table names. Do not modify extract_data.sql; it references the table found
in the query server's local store.
3
Run 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:
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"),
Modify reload_schema.sql to:
CREATE TABLE "DBA"."q1_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"),
extract_data.sql contains:
--- 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';
Installation and Configuration Guide
71
Migrating multiplex databases
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
SET
SET
SET
SET
SET
TEMPORARY
TEMPORARY
TEMPORARY
TEMPORARY
TEMPORARY
TEMPORARY
OPTION
OPTION
OPTION
OPTION
OPTION
temp_extract_name1
temp_extract_name2
temp_extract_name3
temp_extract_name4
temp_extract_name5
=
=
=
=
=
'';
'';
'';
'';
'';
Leave extract_data.sql code unchanged to extract the sales_order table from
the query server.
Suppose that reload_data.sql contains:
-- 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(
72
Sybase IQ
CHAPTER 6
Migrating Data
'''||@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;
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:
-- 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
Installation and Configuration Guide
73
Migrating multiplex databases
'''||@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
NULL;
This 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 necessary, you must upgrade to the at least Sybase IQ 12.7 ESD #5
before local store migration.
2
The iqlsunload utility is installed with Sybase IQ 15.2 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 56.
4
Edit the reload_schema.sql :
•
74
Delete unwanted objects.
Sybase IQ
CHAPTER 6
•
•
Migrating Data
Change any commented objects in the reload_schema.sql that you
want to reload.
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 want 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, wait until the write server has been migrated to 15.2
and run the reload_schema.sql and load_data.sql scripts against the new
15.2 coordinator.
Verify the 12.x databases before migration
Sybase recommends that you run sp_iqcheckdb before you migrate to verify the
consistency of your 12.x databases.
Note 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:
sp_iqcheckdb 'verify database' >& filename
Installation and Configuration Guide
75
Migrating multiplex databases
4
Issue a COMMIT statement.
Note For information on interpreting the sp_iqcheckdb results and corrective
action, see 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.
76
Sybase IQ
CHAPTER 6
Migrating Data
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, shutdown, start 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.
Installation and Configuration Guide
77
Migrating multiplex databases
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.2 Unload utility (iqunload)” on page 45.
For multiplex, there are two differences in the way you will execute the
iqunload utility:
•
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 the
name of the server match the naming conventions for the multiplex nodes.
Once 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 must be visible and accessible by all
nodes of the multiplex. This is important because the main store file name
defaults to new_system_main.iq. This path is relative to the catalog
database file (.db). Later, when the15.2 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 cannot 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, the server
name is enforced. If you are unsure of the server name, check the
administrative script start_server in the database directory.
•
The DBF= argument must specify the actual path 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:
78
Sybase IQ
CHAPTER 6
Migrating Data
iqunload -au -c
"UID=DBA;PWD=SQL;DBF=d:\\marshall\\work\\iq127\\mpx\\main\\main.db;ENG=mpx_main" -ms_filename
d:\\marshall\\work\\iq127\\mpx\\main\\new_main_store.iq
Sybase IQ Unload Utility Version 15.2.0.5533
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\iq127\mpx\main\sa_dbspace.db" by renaming it to
"D:\marshall\work\iq127\mpx\main\sa_dbspace.db.before_schema_reload".
Successfully backed up file "d:\marshall\work\iq127\mpx\main\main.db" by renaming it to
"d:\marshall\work\iq127\mpx\main\main.db.before_schema_reload".
Successfully backed up file "d:\marshall\work\iq127\mpx\main\main.iqmsg" by renaming it to
"d:\marshall\work\iq127\mpx\main\main.iqmsg.before_schema_reload".
Successfully reloaded schema of database
"d:\marshall\work\iq-127\mpx\main\main.db".
Installation and Configuration Guide
79
Migrating multiplex databases
Start the 15.2 migrated database
Start the migrated database in read-only mode:
start_iq -iqro 1 -iqmpx_sn 1
Update the appropriate configuration settings and database 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.2 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.2, 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 the output to a file:
dbisql -c "..." "sp_iqcheckdb ('verify database')"
>& filename
where “...” represents startup parameters for your database.
4
Issue a COMMIT statement.
The server is currently in read-only mode, and cannot complete some
postmigration tasks. Additionally, the verification reports 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','*****'
80
Sybase IQ
CHAPTER 6
Migrating Data
'** Blocks Leaked','25','*****'
'** Unallocated Blocks in Use','104','*****'
Examine the sp_iqcheckdb report for errors. See Chapter 2, “System Recovery
and Database Repair,” in Sybase IQ Troubleshooting and Recovery Guide for
information on interpreting the sp_iqcheckdb results and corrective action. 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 read-only (-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 restart it without any special switches.
Manually synchronize the secondary nodes
To start the secondary nodes, install Sybase IQ 15.2 and then synchronize from
the coordinator node. When you migrate a query node, it becomes a reader
node.
❖
Synchronizing secondary nodes manually
1
Back up the query node files. Sybase recommends 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\iq127\mpx\q1\q1.db.before_schema_reload
rename d:\work\iq-127\mpx\q1\q1.log d:\work\iq127\mpx\q1\q1.log.before_schema_reloadrename
d:\work\iq-127\mpx\q1\q1.iqmsg d:\work\iq127\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:
Installation and Configuration Guide
81
Migrating multiplex databases
dbbackup -y -x -c
"uid=dba;pwd=sql;eng=mpx_main;dbf=d:\\work\\iq127\\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 and 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. For
example, assuming the coordinator file was called main.db and the
secondary server was called q1.db enter
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\iq127\mpx\q1\main.db
The above command line is derived from your existing query server
start_server administration script.
5
82
Repeat these steps on the remaining secondary nodes that you want to
migrate.
Sybase IQ
CHAPTER 6
Migrating Data
Start the secondary nodes
You must complete the steps in “Manually synchronize the secondary nodes”
on page 81 and all nodes of the multiplex must be up and running to start the
secondary nodes.
After you synchronize the secondary nodes, you can start them. Start the
secondary servers 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, set the failover node. You must be
connected to the coordinator and the server name is one of the secondary
nodes:
ALTER MULTIPLEX SERVER servername ASSIGN AS FAILOVER
SERVER
Installation and Configuration Guide
83
Postmigration tasks
Postmigration tasks
After you migrate you databases, you may want to perform these postmigration tasks.
Re-create indexes for EUC_TAIWAN data
In Sybase IQ 15.2, the character encoding specification for the EUC–TAIWAN
collation now uses the EUC_TW character set. You must re-create indexes on
data in version 12.7 or earlier databases that use the EUC_TAIWAN collation
to make them work with Sybase IQ 15.2.
Update configuration files
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. 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 later.
Preserve database options
Sybase IQ preserves the settings of all 12.7 database options that are still valid
in Sybase IQ 15.2 in migrated databases. 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.
Back up your databases after migration
Sybase recommends that you back up your databases again with the BACKUP
statement. For complete syntax, see the Sybase IQ System Administration
Guide.
If you use the IQ BACKUP statement instead of a system–level backup, you can
run backups and queries concurrently.
84
Sybase IQ
CHAPTER 6
Migrating Data
For a multiplex migration, back up only the coordinator only in this manner.
For secondary servers, run the dbbackup utility from the secondary server
directory.
Installation and Configuration Guide
85
Postmigration tasks
86
Sybase IQ
CH A PTE R
7
Configuring Sybase IQ
This chapter describes configuration files, start up options, client access,
backups, and other configuration issues.
Topic
Using configuration files
Page
87
Installing Sybase IQ as a service
Configuring backup devices
88
90
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 file
%IQDIR15%\scripts directory called default.cfg. This file is also the
source of parameters for the Service Manager, the params.cfg file used by
Sybase Central, and multiplex configurations. You can maintain
consistency by editing parameters in default.cfg.
Installation and Configuration Guide
87
Installing Sybase IQ as a service
To increase the amount of virtual memory, 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, and so on).
Security and
configuration files
You can use the dbfhide (File Hiding) utility to encrypt your configuration files.
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 cannot 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
%IQDIR15%/logfile/myserv.log
Installing Sybase IQ as a service
Running Sybase IQ as a Windows service automatically starts the server
whenever the machine is restarted and run in the background as long as
Windows is running.
❖
Creating a new service
1
Click Start | Programs | Sybase | Sybase IQ 15.2 | Sybase IQ Service
Manager.
2
Choose Create a New Service.
3
Name 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.
88
5
Click Apply.
6
Restart Windows.
Sybase IQ
CHAPTER 7
Configuring Sybase IQ
Because Window service manager reads environmental variables only at
system startup, you must restart Windows after you configure Sybase IQ
as a Windows service.
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 event log messages
If you run the database server as a Windows service, you can set the
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 bitmask 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
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 privilege to the Sybase IQservice
You must assign Administrator privileges to a Sybase IQ service when raw
device access is required.
1
Click Start | Settings | 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.
Installation and Configuration Guide
89
Configuring backup devices
5
Assign the account to a user with Administrative privileges. In the account
box, type the administrator’s user ID, then enter and confirm the user’s
password.
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
uses 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
“Backup and Data Recovery” in the Sybase IQ System Administration
Guide.
Configuring client connectivity
Sybase IQ supports ODBC and JDBC connectivity. Sybase IQ 15.2 uses SQL
Anywhere to store catalog information.
Sybase IQ versions earlier than 12.0 used Adaptive Server as the catalog
server. ODBC applications used as client front–end tools with older versions of
Sybase IQ will continue to run in IQ version 12.x, but third–party and
customer–written Open Client™ DB–Library and Client–Library applications
are unlikely to perform as expected.
90
Sybase IQ
CHAPTER 7
Configuring Sybase IQ
When you develop Open Client applications to run with Sybase IQ 12.x, do not
use catalog tables or system stored procedures supported by Adaptive Server
but not Sybase IQ. See Appendix A, “Compatibility with Other Sybase
Databases,” in the Sybase IQ Reference Manual.
Sybase IQ is compatible with clients (like Open Client–Library and DB–
Library) that use Tabular Data Streams (TDS). Open Client version 11.1.1
supports TDS 5.x and applications developed using these tools work with
Sybase IQ, if these applications use the system tables, views, and procedures
in Sybase IQ. System procedures, catalog tables, and views available in Sybase
IQ are listed in the Sybase IQ Reference Manual. There are no restrictions for
accessing data in the IQ Store through any supported interface.
Connecting using JDBC
JDBC (Java Database Connectivity) is a 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 Sybase IQ System Administration Guide.
Notes
•
The JDBC driver is the default driver for Sybase Central and dbisql.
•
IQ Agent can use only jConnect with JDBC to connect to a multiplex
server. The jConnect JDBC drivers have been certified with simplex and
multiplex servers.
Connecting using ODBC
Open Database Connectivity (ODBC) is a standard API developed by
Microsoft that allows a single application to access a variety of data sources for
which ODBC–compliant drivers exist. ODBC uses SQL as the standard data
access language.
Installation and Configuration Guide
91
Configuring client connectivity
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
Level 1 conformance
All core features.
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:
• 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 requests and 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:
1
Click Start | Programs | Sybase | Sybase IQ | ODBC Administrator 64 bit.
2
Run C:\WINDOWS\SysWOW64\odbcad32.exe.
Do not launch the ODBC Administrator from the Control Panel or Run box.
Attempts to add a DSN starting the ODBC Administrator incorrectly may
returns these errors:
•
92
The setup routines for the Adaptive Server IQ ODBC
driver could not be loaded due to system error code 126.
Sybase IQ
CHAPTER 7
Configuring Sybase IQ
•
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
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, download and install a
platform-specific Sybase IQ ODBC Driver. Check the EBF/Update
information on the Sybase Web site 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.
Third-party ODBC applications
For information on third-party vendor applications certified with Sybase IQ,
See “Sybase certifications on the Web” in the release bulletin.
Installation and Configuration Guide
93
Configuring client connectivity
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, and may include, for example, database name, server where it
resides, and network used to access the server.
Note The AUTOSTOP parameter is required in file data sources and odbc.ini
files, must 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 | Programs | Sybase | Sybase IQ 15.2 .
2
Choose the appropriate option:
•
ODBC Administrator 32-bit
•
ODBC Administrator 64-bit
3
On the User DSN tab, click Add, choose Server IQ, then click Finish.
4
On the ODBC Configuration dialog, type a Data Source Name in the Data
Source Name box.
5
Click the Login tab, and enter the database User ID and Password.
6
Click the Database tab. If the data source:
•
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.)
•
On your local machine, type a start line and database name (without
the .db extension).
•
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, select the TCP/IP box and enter:
host=localhost2k:port=1870.
94
Sybase IQ
CHAPTER 7
Configuring Sybase IQ
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.2 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 Sybase IQ System Administration Guide.
❖
Testing an ODBC data source
1
Click Start | Programs | Sybase | Sybase IQ 15.2 | ODBC Administrator.
2
Choose the data source you want to test, and click Configure.
3
Click Test Connection.
Command line connection to 32-bit applications
To connect to 32-bit applications without using a data source, enter an
Interactive SQL command similar to this at the command prompt:
dbisql -c "UID=DBA;PWD=sql;AUTOSTOP=no;
ENG=<engine name>;DBF=%ALLUSERSPROFILE%\SybaseIQ\
demo\iqdemo.db"
This command can use these 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.
Installation and Configuration Guide
95
Configuring client connectivity
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.
Sybase IQ includes an OLE DB provider. If you use the Sybase IQ OLE DB
provider, ODBC is not required.
OLE DB requires a Windows client. However, you can access both Windows
and UNIX servers using OLE DB.
For more information, see the Server Programming Guide and “Connecting to
a database using OLE DB” in Chapter 3, “Sybase IQ Connections,” in the
Sybase IQ System Administration Guide.
Note Sybase IQ support for certain features used with OLE DB differs from
SQL Anywhere support. Be aware of these differences when using the SQL
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
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.
Connecting using Open Client
To insert data from an Adaptive Server database to a Sybase IQ database, or 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, simplify
database start-up and client connections from Sybase Central.
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.
96
Sybase IQ
CHAPTER 7
Configuring Sybase IQ
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. Shared memory is configured automatically,
and starts 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. All
implementations described in this document do implement the same protocol
suite, they are all compatible.
User Datagram
Protocol
There are several entries into the TCP/IP protocol stack. IQ employs the User
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
protocol stacks
Many vendors supply TCP/IP protocol stacks and associated software. IQ
communications have been explicitly verified with Microsoft Winsock version
2.0.
Using TCP/IP with
Windows
Windows NT 3.5 and later ship with TCP/IP software that uses NDIS network
drivers. This software allows an IQ server for Windows or an IQ client
application to use Windows TCP/IP. Install TCP/IP Protocol from the Network
Settings options on the Control Panel.
Installation and Configuration Guide
97
Configuring client connectivity
Tuning Sybase IQ
performance under
TCP/IP
Although the default packet size for TCP/IP is 512 bytes, a larger packet size
may improve query response time, especially for queries transferring a large
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.
For more information on these parameters, see the Sybase IQ System
Administration Guide.
Example
The following connection string fragment restricts the client application to
ports 5050 through 5060, disables UDP packets, and connects to a server
named myiq running on the machine at address myhost using the server port
2020:
CommLinks=tcpip(UseUDP=OFF;ClientPort=50505060;Host=myhost;Port=2020;Eng=myiq)
Additional networking
details
98
For more detailed information on networking and protocol stacks, refer to
networking-specific documentation.
Sybase IQ
A P PE N DI X
A
Silent Installations
Your installation media includes scripts that perform standard IQ installs
and uninstalls without interacting with the product. By default these
scripts are configured to perform typical installations; custom installation
tasks require additional configuration.
The installation media includes installation scripts, an appropriate JRE,
CLASSPATH settings, a Java command string, and pointers to the text file
that contains 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.
Topic
Installing IQ silently
Uninstalling IQ silently
Page
99
103
Sample configuration files
103
Installing IQ silently
IQ silent installation scripts support typical and custom installations. See
“Editing the installation parameters” on page 100 and “Running a silent
install” on page 101.
Note Before you install the software, stop and shut down all programs.
Installation and Configuration Guide
99
Installing IQ silently
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 100 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 101 and
“Completing the installation” on page 102 for more information.
Editing the installation parameters
Installation parameters are stored in SilentInstall.txt, which, by default, is
configured to perform typical installations; 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 105 to review the parameters in this file.
•
Comments in the file are prefixed with a # sign.
•
Modifiable parameters appear between “ ”.
•
Feature selections start with –P.
•
Variable options are prefixed with –V.
•
License options are prefixed with –W.
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.
100
Sybase IQ
APPENDIX A
Silent Installations
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
arguments
Typical install
You can display options for this script by running the SilentInstall.bat with the
–h or –? option on the command line. All arguments appear in the table below.
Argument
h or ?
Description
Display help and exit.
jvm "JVM_ARGS"
java
Include user specified JVM_ARGS.
Specify the location of the java folder.
txt
bs <32|64>
Specify the location of Silent Install text file.
Specify the bit size of the installed files.
cl
src
Specify the location of the silent install console log.
Specify the path to root directory of installer files.
I_accept_sybase_license
dst
Agree to the Sybase IQ licensing terms.
Specify the install location for Sybase IQ .
licensed_user
eval_user
Installs the licensed version of Sybase IQ.
Installs the evaluation version of Sybase IQ.
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.
Installation and Configuration Guide
101
Installing IQ silently
Running silent install
scripts on Microsoft
Vista
You must have sufficient user permissions to run applications in Microsoft
Vista. If you do not have administrator privileges and want to run a silent install
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
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 Sybase IQ 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.
102
Sybase IQ
APPENDIX A
Silent Installations
Uninstalling IQ silently
IQ silent uninstallation scripts support typical and custom uninstallations. See
“Editing the uninstall parameters” on page 103 and “Running a silent install”
on page 101
Note Run a silent uninstall from the installation directory, not the installation
media. Before you uninstall the software, stop and shut down all programs.
Editing the uninstall parameters
SilentUninstall.txt contains parameters that tell the uninstaller which
components to remove. By default, SilentUninstall.txt is configured to remove
all components; removing specific components requires additional
configuration.
SilentUninstall.txt contains the same default selection and configuration
options as the interactive uninstaller. To uninstall only some components, edit
the file, and change the default parameters:
•
Features with parameters set to true are uninstalled
•
Features with parameters set to false are not uninstalled
If you modify the file, read the comments for the sections you want to change,
update the parameters, then save SilentUninstall.txt to the local file system. See
“SilentUninstall.txt” on page 110 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 103 or “Uninstalling some
components” on page 104.
Uninstalling all
components
If you installed IQ with all defaults, you can run a typical silent uninstall
directly from the installation directory. To run the uninstall, open a command
window, and use the following command:
%SYBASE%\uninstall\IQ\SilentUninstall.bat
Installation and Configuration Guide
103
Uninstalling IQ silently
Uninstalling some
components
To perform a custom uninstall, edit SilentUninstall.txt, then use this command
format to run SilentUninstall.bat:
%SYBASE%\uninstall\IQ\SilentUninstall.bat <directory
name>\SilentUninstall.txt
Running silent
uninstall scripts on
Microsoft Vista
104
You must have sufficient user permissions to run applications in Microsoft
Vista. If you do not have administrator privileges and want to run a silent
uninstall, open a command prompt as an Administrator, then execute the silent
uninstall from the command line.
Sybase IQ
APPENDIX A
Silent Installations
Sample configuration files
Use this section to review the settings in the configuration files, and
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
105
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
106
Sybase IQ
APPENDIX A
#
#
#
#
#
#
-W sysamLicense.licenseServerPortNumber
Silent Installations
license server was deployed.
- 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
107
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.
#
108
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
109
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
110
Sybase IQ
APPENDIX A
Silent Installations
-P LicenseUtilities.activeForUninstall="true"
#############################################################################
# The following are shared components. They may be needed
# by other Sybase products.
#
# Set to false to keep these components.
#
# Variable_RemoveOpenClient: Doesn't uninstall IQ Open Client if false
#
- overrides the above setting IQOpenClient.activeForUninstall="true"
# Variable_RemoveLogs: Keeps local database and log files
# Variable_RemoveJRE: Keeps the shared JRE used by IQ Client and SCJ Viewer
#############################################################################
-V Variable_RemoveOpenClient="true"
-V Variable_RemoveLogs="true"
-V Variable_RemoveJRE="true"
#############################################################################
# Please do not modify the values below.
#############################################################################
-P SilentUninstall.activeForUninstall="false"
-P SilentUninstall1.activeForUninstall="false"
-G removeExistingResponse=yesToAll
-G removeModifiedResponse=yesToAll
-silent
Installation and Configuration Guide
111
Sample configuration files
112
Sybase IQ
A P PE N DI X
B
Troubleshooting SySAM
If you do not address SySAM 2 related errors in a timely fashion, Sybase
IQ may cease to function. For the most current information about
troubleshooting SySAM, see the SySAM FAQ at
http://www.sybase.com/products/allproductsa-z/sysam.
Topic
Where to look for SySAM-related errors
SySAM grace mode
Page
113
114
SySAM grace period
Enabling and changing e-mail notifications
114
114
Calling Sybase technical support for SySAM-related issues
License checkout and verification
115
117
Diagnosing SySAM issues
117
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 procedure. 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 (%SYBASE%/SYSAM-2_0/log provides
information about any license check-out issues).
Installation and Configuration Guide
113
SySAM grace mode
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 for the IQ_CORE license is more than 30 days.
Enabling and changing e-mail notifications
You can configure the e-mail notification setup using sp_iqlmconfig. Run the
sp_iqlmconfig procedures 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.
114
Sybase IQ
APPENDIX B
Troubleshooting SySAM
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.
•
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.
License checkout
Table B-1 describes the events that determine when SySAM checks out
different licenses.
Installation and Configuration Guide
115
License checkout and verification
Table B-1: License checkout table
Coordinator
Writer
Reader
Node
checking
out
IQ_SECURITY
On feature
access
Yes
Yes
Yes
All nodes
Yes
IQ_MPXNODE
On database
startup
Never
Yes
Yes
Secondary
nodes only
Yes
IQ_VLDBMGMT
When user
creates 3rd
dbspace
Yes
Never
Never
Coordinator
only
No
IQ_LOB
When user
creates/accesses
LOB/CLOB
table
On database
startup
Yes
Yes
Yes
All nodes
Yes
Yes
Yes
Yes
All nodes
Yes
IQ_UDF
When user
accesses UDF
Yes
Yes
Yes
All nodes
Yes
IQ_UDA
Only the first
time after an IQ
server is started;
when a TEXT
index is
created/altered;
or when you
execute a query
with CONTAINS
predicate.
License
IQ_CORE
Initial
checkout
occurs...
Separate
license per
node
Note IQ_SYSTEM_MAIN and one more user dbspace is provided with the
server; a third dbspace requires a IQ_VLDGMGMT license.
License verification
Table B-2 identifies when SySAM verifies different licenses.
Table B-2: License verification table
Checks on
startup after
feature enabled
Checks on
feature access
IQ_SECURITY
IQ_MPXNODE
•
•
•
IQ_VLDBMGMT
•
•
License
116
Consistent
checks on
startup
Sybase IQ
APPENDIX B
License
Consistent
checks on
startup
IQ_LOB
IQ_CORE
Troubleshooting SySAM
Checks on
startup after
feature enabled
Checks on
feature access
•
•
IQ_UDA
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 117
starts with graced license instead” on page 120
“The installation program produces a warning
about not finding a suitable license” on page
118
“The license server executables and scripts are
not installed” on page 118
“The license server does not start” on page 119
“The license server does not recognize the
license files” on page 119
“Sybase IQ shows graced licenses even after
the issue has been fixed” on page 122
“Sybase IQ cannot find license for an optional
feature, even though the license exists” on page
122
“Sybase IQ does not start with the expected
edition or license type” on page 122
“Sybase IQ does not pick the correct license”
on page 123
“Sybase IQ does not start, and generates a
license check-out failure error” on page 120
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.
Installation and Configuration Guide
117
Diagnosing SySAM issues
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 120.
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.
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.
118
Sybase IQ
APPENDIX B
Troubleshooting SySAM
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:
•
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.
Installation and Configuration Guide
119
Diagnosing SySAM issues
•
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\SYSAM2_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:
Served models
120
•
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.
Sybase IQ
APPENDIX B
•
Troubleshooting SySAM
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
Wrong license
product edition or
license type
•
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.
•
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.
If the diag command shows the license for the given feature is available for
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.
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 122 for more information.
Installation and Configuration Guide
121
Diagnosing SySAM issues
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.
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.
122
Sybase IQ
APPENDIX B
Troubleshooting SySAM
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
123
Diagnosing SySAM issues
124
Sybase IQ
Index
Numerics
4GT (enabling)
8
A
Adaptive Server Enterprise
inserting data from 96
Add Service utility 88
adding IQ as a Windows Service 88
adding startup switches 50
Administrator privilege
granting to IQ as a Windows service
after upgrading
updating configuration files 84
autostarting database 54
AUTOSTOP parameter 95
AWE cache, using (Windows) 9
B
backing up databases
after upgrade 84
procedure 84
backups
devices supported 90
BLANK PADDING
migration 60
blank users 58
block mode
displaying 90
89
client components 38
installing 37
jConnect 38
ODBC 38
Sybase Central 38
Sybase IQ client 38
client installation
client components 38
demo database 38
parent installation directory 38
prerequisites 37
running the installer 39
samples directory 38
Sybase IQ installation directory 38
typical installation 38
code samples (Windows) 9
COMMLINKS parameter 95
configuration files 87
security 88
configuration parameters
overriding 34
set by start_asiq 33
connecting
using OLE DB 96
with JDBC 91
connection parameters 95
connections
restricting 43
constraints
migration 60
unenforced 60
D
C
cache sizes 53
catalog cache 53
changing hardware platforms
42
Installation and Configuration Guide
data migration
extract directory 56
data sources
setting up 94
data storage changes
125
Index
migration 46
database
autostarting 54
encrypted 53
database migration
iqunload 45
database options
migrating 46
database schema
unloading 56
databases
backing up 84
connection parameters 95
creating 32
demo ix
invalid names 60
migrating 46
upgrading 56
verifying 66, 75, 80
DBF parameter 95
dbspace size
specifying during migration 51
dbspace,default 47
dbspaces
files 46
logical names 46
migrating 46
temporary 46
DECLARE LOCAL TEMPORARY TABLE statement
migration 61
default installation directory 24
DEFAULT_DBSPACE option 47
demo database ix
directory location 38
name changes 32
owner 32
Demo/Evaluation Edition
license 14
deployement changes, Windows 9
diagnosing SySAM problems 117
Directory Services Editor 96
documentation
SQL Anywhere viii
Sybase IQ vii
drivers 91
DSEDIT 96
126
E
elevated operations agent (Sybase IQ)
empty user names 58
Enable 4GT 8
encrypted databases 53
ENG parameter 95
environment variables
extract directory 56
Evaluation edtion
evaluation period 3
evaluation period 3
Event log
suppressing entries 89
executables, signed (Windows) 9
extract directory 56
9
F
Fast Projection indexes 60
file changes
migration 48
file data sources 95
file ID 46
files
after upgrade 46
fin_code
name change 32
fin_data
name change 32
firewalls 98
first time installations
planning installations 3
fixed-length devices 90
FLEXNET
download page 16
utilities 15
FLEXnet Licensing FLEXnet Licensing End User Guide
15
function
migration 61
G
generating
17, 18
Sybase IQ
Index
generating licenses 17
grace mode 29
grace mode, SySAM 114
H
hardware platform
changing 5, 42
host host name (licensing) 16
host ID (licensing) 15
host IDs and network adapters 16
I
iAnywhere JDBC driver 91
indexes
migration 60
one-byte FP 60
initialization file
creating 96
INOUT parameters 61
Installation
first time installations 3
planning 3
upprading from a previous version 4
installation
installating a license serverr 19
media 3
options 10
running the installer 19, 27
installation directory
IQ installation directory variable 27
parent installation directory variable 26
server 24
installer
license server installation 19
running 19, 27
running client install 39
interfaces file
adding entries 96
IQ Agent 102
IQ Local Stores
migrating 70
IQ Main Store
Installation and Configuration Guide
filename 51
iq_main dbspace 47
IQ_SYSTEM_MAIN
on raw device 51
IQ_SYSTEM_MAIN dbspace 46
IQ_SYSTEM_MAIN store
size 51
IQ_SYSTEM_TEMP dbspace 46
iqdemo database
table names 32
iqlsunload
about 56
migration utilities 56
parameters 56
permissions 59
running 56
syntax 56
usage 57
utilities
unload 56
iqlsunload utility
about 56
iqunload 45
database migration mode 45
logging errors 54
migration 45
parameters 49
schema unload mode 45
syntax 49
troubleshooting connection 54
understanding 49
usage 51
very large schemas 56
working with large schemas 55
utilities
unload 45
iqunload logging 54
iqunload utility
about 45
ISQL
connections 96
J
jConnect
127
Index
client component 38
server component 24
jConnect driver 91
JDBC
configuring connections
connecting with 91
join indexes
migration 60
joins
migration 61
96
L
large schemas
iqunload 55
license key
server installation 23
license models 15
unserved 15
license server
installing 18, 19
reread command 20, 21
starting 19, 20
status command 20, 21
license server requirements 7
License Utilities 24
Licensed edition 3
licensing 17, 18
available licenses 12
FLEXNET commands 16
FLEXNET utilities 15
host ID (obtaining) 15
host IDs and network adapters 16
host name 16
license key 23
license models 15
License Utilities 24
Network License Server 24
port number 16
steps before you generate a license 14
Sybase Product Download Center 11
Sybase Software Asset Management 24
SySAM documentation 15
SySAM server components 24
licensing requirements
128
evaluation edition 3
general requirements 3
licensed edition 3
SySAM 3
local stores
moving 70
locating SySAM errors 113
logging
extra 54
M
main cache 53
main store
filename 51
reserve size 51
size 51
migrating data
from 32-bit to 64-bit 42
from one platform to another 42
from prior Sybase IQ version 42
migrating databases
multiplex 67
option changes 46
procedure 46
simplex 63
migrating simplex databases 63
task summary 63
migration
BLANK PADDING 60
changing hardware platforms 42
constraints 60
data storage changes 46
errors, avioding 59
extract directory 56
file changes 48
FP indexes 60
functions 61
indexes 60
invalid SQL syntax 60
join indexes 60
local stores 70
logging 54
migration utilities 45
overview 41
Sybase IQ
Index
schema reload 46
setting page size 49
simplex databases 63
triggers 61
unenforced constraints 60
unsupported objects 60
upprading from a previous version 41
using raw device for IQ_SYSTEM_MAIN
views 61
migration utilities
iqlsunload 56
iqunload 45
-ms_filename parameter 51
-ms_reserve parameter 51
-ms_size parameter 51
multiplex
local stores 70
multplex database migration
workflow 67
N
named pipes
Sybase IQ use of 97
names
invalid 61
network adapters and host IDs 16
network functionality, verifying 10
Network License Server 24
-new_startline parameter 50, 54
O
object names
invalid 61
ODBC
driver managers 93
ODBC data sources
creating 94
odbc.ini file 95
OLE DB provider 96
Open Client
connecting from 96
operating system patches
Installation and Configuration Guide
see preinstallation tasks
OUT parameters 61
outer joins
Transact-SQL 61
51
6
P
page size
migrated database 49
parameters
iqlsunload 56
iqunload 49
iqunload utility 49
passwords
protecting 88
permissions
iqlsunload 59
planning installations 3
platforms, supported 2
platforrms
changing 5, 42
port number (licensing) 16
post-installation tasks
server 29
preinstallation 6
preinstallation tasks 6, 7, 8
increasing the swap space 6
operating system patches 6
verify network functionality 10
privilege
Administrator 89
product edtion 23
protocols
supported 97
PWD parameter 95
R
raw device
specifying during migration
readme.txt file 102
reloading 56
reserve size
specifying during migration
51
51
129
Index
reserved words
61
S
sales_order
name change 32
sample code (Windows) 9
sample database
name changes 32
owner 32
samples
directory 38
schema 56
schema reload
migration 46
schema unload
iqunload 45
schema-only unload 52
schemas
iqunload 56
security, Windows 9
served 15
served licenses 15, 18
server
not found 54
server components
jConnect 24
License Utilities 24
Network License Server 24
ODBC 24
Sybase Central 24
Sybase IQ client 24
Sybase IQ server 24
SySAM 24
server configuration files 87
server installation
default installation directory 24
grace mode 29
installation directory 24
installing server components 27
IQ directory variable 27
parent directory variable 26
parent installation directory 26
plug-in compatibility 24
post-installation tasks 29
130
prerequisites 23
server components 24
Sybase IQ installation directory 27
server objects
adding 96
servers
stopping 35
services, Windows 10
setting server configurations 87
shared memory 97
signed executables, signed (Windows) 9
simplex database migration 63
task summary 63
workflow 63
simplex migration
database verification (sp_iqcheckdb) 64
Single Application Edition (SA)
license 14
limits set by license 14
Small Business Edition (SE)
license 13
limits set by license 14
sp_iq_process_login procedure 55
sp_iq_process_post_login procedure 55
sp_iqcheckdb 64
verifying databases 75
verifying upgraded databases 66, 80
sp_iqlmconfig
verifying your license 29
starting Sybase IQ 32
startup switches
migration 50
stopping
servers 35
stored procedures 61
support, technical ix
swap space 6
increasing 6
preinstallation tasks 6
Sybase Central
requirements 102
setup 102
Sybase IQ
and TCP/IP 97
elevated operations agent 9
product edition 23
Sybase IQ
Index
product editions 1
stopping 35
supported platforms 2
supported protocols 97
Sybase IQ Service
granting Administrator privilege 89
Sybase Product Download Center (SPDC) 11
syntax
invalid SQL syntax 60
iqlsunload 56
iqunload 49
SySAM
available licenses 12
calling technical support 115
diagnosing problems 117
generating licenses 17
grace mode 114
license key 23
locating errors 113
Network License Server 24
Network License Utilities 24
overview 11
served licenses 18
steps before you generate a license 14
Sybase SySAM server components 24
SySAM documentation 15
troubleshooting 113
unserved licenses 17
SySAM documentation
FLEXnet Licensing End User Guide 15
Quick Start Guide 15
Users Guide 15
SySAM licenses
Demo/Evaluation Edition 14
Enterprise Edition 12
FLEXNET commands 16
FLEXNET utilities 15
host ID (obtaining) 15
host IDs and network adapters 16
host name 16
license models 15
port number 16
Single Application Edition (SA) 14
Small Business Edition (SE) 13
SySAM server components 24
Installation and Configuration Guide
T
tables
invalid names 60
not found 61
sample database 32
tape devices
for backups 90
TCP/IP
and Sybase IQ 97
tuning Sybase IQ performance under
technical support ix
SySAM problems 115
To 29
Transact-SQL outer joins 61
triggers
migration errors 61
troubleshooting
SySAM 113
98
U
UID parameter 95
unenforced constraints 60
unload utility
about 45
unloading schema only 52
unserved licenses 15, 17, 18
updating
configuration files 84
upgrading databases 46
upgrading from a previous version
migration 41
planning 4
usage
iqlsunload 57
iqunload 51
user names
empty 58
users
blank 58
invalid names 60
utilities
migration 45
utility database 43
131
Index
V
variable
IQ installation directory 27
parent installation directory 26
variable-length devices 90
verifying databases
after upgrade 66, 80
before upgrade 75
procedure 66, 75, 80
verifying your license 29
views
invalid 53, 61
W
wide tables
migrating 53
Windows Service
adding IQ as 88
adding Sybase IQ servers 88
Windows support issues 8
AWE cache, using 9
code samples 9
deployment changes 9
elevated operations agent (Sybase IQ)
security 9
signed executables 9
Windows services 10
workflows
first time installations 3
installation and migration 3
multiplex database migration 67
simplex database migration 63
upgrading installations 4
132
9
Sybase IQ