7.2 Netezza Odbc JDBC Guide

IBM Netezza
Version 7.2
IBM Netezza ODBC, JDBC, and OLE DB

Installation and Configuration Guide

IBM Netezza
Version 7.2
IBM Netezza ODBC, JDBC, and OLE DB

Installation and Configuration Guide

Note
Before using this information and the product it supports, read the information in “Notices” on page C-1
Revised: March 11, 2015

This edition applies to IBM Netezza Release 7.2 and to all subsequent releases until otherwise indicated in new
editions.
© Copyright IBM Corporation 2007, 2015.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Electronic emission notices . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Regulatory and compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
About this publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Audience for this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
If you need help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
How to send your comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Chapter 1. General information about ODBC, JDBC, and OLE DB . . . . . . . . . . 1-1

Architecture of ODBC and JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Process steps for ODBC, JDBC, and OLE DB . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Chapter 2. Support and release compatibility . . . . . . . . . . . . . . . . . . . 2-1

Supported platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Release compatibility matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Driver version support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Standards conformance and API versions . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
JDBC driver data source support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Chapter 3. Installing and uninstalling client software . . . . . . . . . . . . . . . 3-1

Client software packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Windows client tools software installation . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Installation requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Installing the Netezza tools on Windows . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
UNIX client tools software installation . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Installing the UNIX clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Set the path for Netezza CLI client commands . . . . . . . . . . . . . . . . . . . . . . 3-7
Removing the Netezza tools on Windows . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Remove the CLI clients from UNIX systems . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Chapter 4. ODBC drivers and driver managers . . . . . . . . . . . . . . . . . . 4-1

ODBC drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
ODBC driver tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
ODBC driver properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
ODBC driver managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
ODBC driver manager tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Windows driver managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Linux/UNIX driver managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Chapter 5. Installing and configuring ODBC . . . . . . . . . . . . . . . . . . . 5-1

Installing and configuring ODBC for Windows . . . . . . . . . . . . . . . . . . . . . . . 5-1
ODBC driver command-line installation for Windows . . . . . . . . . . . . . . . . . . . . 5-1
Installing the ODBC driver for Windows with the GUI . . . . . . . . . . . . . . . . . . . 5-1
ODBC driver data source configuration for Windows . . . . . . . . . . . . . . . . . . . . 5-2
Configuring ODBC for UNIX/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
ODBC driver configuration for UNIX/Linux . . . . . . . . . . . . . . . . . . . . . . . 5-7
ODBC data source configuration for UNIX/Linux . . . . . . . . . . . . . . . . . . . . . 5-9
ODBC connectivity validation for UNIX/Linux . . . . . . . . . . . . . . . . . . . . . . 5-12
Kerberos authentication details for ODBC clients . . . . . . . . . . . . . . . . . . . . . . 5-14
© Copyright IBM Corp. 2007, 2015 iii

Chapter 6. Installing and configuring JDBC. . . . . . . . . . . . . . . . . . . . 6-1
Installing the JDBC driver for Windows with the GUI . . . . . . . . . . . . . . . . . . . . . 6-1
Installing JDBC for UNIX/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
JDBC driver installation for UNIX/Linux on a supported platform . . . . . . . . . . . . . . . 6-1
Installing JDBC driver for UNIX/Linux on an unsupported platform . . . . . . . . . . . . . . . 6-2
Configuring the JDBC data source on Windows . . . . . . . . . . . . . . . . . . . . . . . 6-2
Configuring JDBC for UNIX/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Kerberos authentication details for JDBC clients . . . . . . . . . . . . . . . . . . . . . . . 6-4
JDBC setup considerations for IBM Cognos SSO environments . . . . . . . . . . . . . . . . . . 6-6
Chapter 7. Installing and configuring the OLE DB provider . . . . . . . . . . . . . 7-1

OLE DB provider silent installation options . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Installing the OLE DB provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Validating the OLE DB data source configuration . . . . . . . . . . . . . . . . . . . . . . 7-2
Kerberos authentication details for OLE DB clients . . . . . . . . . . . . . . . . . . . . . . 7-2
Appendix A. ODBC configuration files . . . . . . . . . . . . . . . . . . . . . . A-1

Netezza ODBC configuration file names and locations . . . . . . . . . . . . . . . . . . . . A-1
ODBC driver search behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
ODBC driver considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
The unixODBC driver manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
The unixODBC driver manager search behavior. . . . . . . . . . . . . . . . . . . . . . A-2
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
DataDirect driver manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
DataDirect driver manager search behavior . . . . . . . . . . . . . . . . . . . . . . . A-3
Incompatibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Investigate the client system configuration . . . . . . . . . . . . . . . . . . . . . . . . A-4
Appendix B. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . B-1

ODBC debug logging and driver manager tracing . . . . . . . . . . . . . . . . . . . . . . B-1
ODBC debug logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
ODBC driver manager tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
The nzodbcsql command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
JDBC debug logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Connection string examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
OLE DB debug logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1
iv IBM Netezza ODBC, JDBC, and OLE DB Installation and Configuration Guide
Electronic emission notices
When you attach a monitor to the equipment, you must use the designated
monitor cable and any interference suppression devices that are supplied with the
monitor.
Federal Communications Commission (FCC) Statement
This equipment was tested and found to comply with the limits for a Class A
digital device, according to Part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses, and can
radiate radio frequency energy and, if not installed and used in accordance with
the instruction manual, might cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful
interference, in which case the user is required to correct the interference at their
own expense.
Properly shielded and grounded cables and connectors must be used to meet FCC
emission limits. IBM® is not responsible for any radio or television interference
caused by using other than recommended cables and connectors or by
unauthorized changes or modifications to this equipment. Unauthorized changes
or modifications might void the authority of the user to operate the equipment.
This device complies with Part 15 of the FCC Rules. Operation is subject to the
following two conditions: (1) this device might not cause harmful interference, and
(2) this device must accept any interference received, including interference that
might cause undesired operation.
Industry Canada Class A Emission Compliance Statement
This Class A digital apparatus complies with Canadian ICES-003.
Avis de conformité à la réglementation d'Industrie Canada
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du

Canada.
Australia and New Zealand Class A Statement
This product is a Class A product. In a domestic environment, this product might

cause radio interference in which case the user might be required to take adequate
measures.
European Union EMC Directive Conformance Statement
This product is in conformity with the protection requirements of EU Council

Directive 2004/108/EC on the approximation of the laws of the Member States
relating to electromagnetic compatibility. IBM cannot accept responsibility for any
failure to satisfy the protection requirements resulting from a nonrecommended
modification of the product, including the fitting of non-IBM option cards.
© Copyright IBM Corp. 2007, 2015 v

This product is an EN 55022 Class A product. In a domestic environment, this
product might cause radio interference in which case the user might be required to
take adequate measures.
Responsible manufacturer:
International Business Machines Corp.

New Orchard Road
Armonk, New York 10504
914-499-1900
European Community contact:
IBM Technical Regulations, Department M456

IBM-Allee 1, 71137 Ehningen, Germany
Telephone: +49 7032 15-2937
Email: tjahn@de.ibm.com
Germany Class A Statement
Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie

zur Elektromagnetischen Verträglichkeit
Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie

2004/108/EG zur Angleichung der Rechtsvorschriften über die elektromagnetische
Verträglichkeit in den EUMitgliedsstaaten und hält die Grenzwerte der EN 55022
Klasse A ein.
Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu

installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM
empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für
die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der
IBM verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne
Empfehlung der IBM gesteckt/eingebaut werden.
EN 55022 Klasse A Geräte müssen mit folgendem Warnhinweis versehen werden:

“Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im
Wohnbereich Funk-Störungen verursachen; in diesem Fall kann vom Betreiber
verlangt werden, angemessene Maßnahmen zu ergreifen und dafür
aufzukommen.”
Deutschland: Einhaltung des Gesetzes über die

elektromagnetische Verträglichkeit von Geräten
Dieses Produkt entspricht dem “Gesetz über die elektromagnetische Verträglichkeit

von Geräten (EMVG)”. Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in
der Bundesrepublik Deutschland.
Zulassungsbescheinigung laut dem Deutschen Gesetz über die

elektromagnetische Verträglichkeit von Geräten (EMVG) (bzw. der
EMC EG Richtlinie 2004/108/EG) für Geräte der Klasse A
Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das
EG-Konformitätszeichen - CE - zu führen.
Verantwortlich für die Einhaltung der EMV Vorschriften ist der Hersteller:
vi IBM Netezza ODBC, JDBC, and OLE DB Installation and Configuration Guide
International Business Machines Corp.
New Orchard Road
Armonk, New York 10504
914-499-1900
Der verantwortliche Ansprechpartner des Herstellers in der EU ist:
IBM Deutschland
Technical Regulations, Department M456
IBM-Allee 1, 71137 Ehningen, Germany
Telephone: +49 7032 15-2937
Email: tjahn@de.ibm.com
Generelle Informationen: Das Gerät erfüllt die Schutzanforderungen nach EN 55024

und EN 55022 Klasse A.
Japan VCCI Class A Statement
This product is a Class A product based on the standard of the Voluntary Control
Council for Interference (VCCI). If this equipment is used in a domestic
environment, radio interference might occur, in which case the user might be
required to take corrective actions.
Japan Electronics and Information Technology Industries

Association (JEITA) Statement
Japan Electronics and Information Technology Industries Association (JEITA)

Confirmed Harmonics Guidelines (products less than or equal to 20 A per phase)
Japan Electronics and Information Technology Industries

Association (JEITA) Statement
Japan Electronics and Information Technology Industries Association (JEITA)

Confirmed Harmonics Guidelines (products greater than 20 A per phase)
Electronic emission notices vii

Korea Communications Commission (KCC) Statement
This is electromagnetic wave compatibility equipment for business (Type A). Sellers
and users need to pay attention to it. This is for any areas other than home.
Russia Electromagnetic Interference (EMI) Class A Statement
People's Republic of China Class A Electronic Emission

Statement
Taiwan Class A Compliance Statement
viii IBM Netezza ODBC, JDBC, and OLE DB Installation and Configuration Guide
Regulatory and compliance
Regulatory Notices
Install the NPS® system in a restricted-access location. Ensure that only those
people trained to operate or service the equipment have physical access to it.
Install each AC power outlet near the NPS rack that plugs into it, and keep it
freely accessible.
Provide approved circuit breakers on all power sources.
The IBM PureData® System for Analytics appliance requires a readily accessible
power cutoff. This can be a Unit Emergency Power Off Switch (UEPO), a circuit
breaker or completely remove power from the equipment by disconnecting the
Appliance Coupler (line cord) from all rack PDUs.
CAUTION:
Disconnecting power from the appliance without first stopping the NPS
software and high availability processes might result in data loss and increased
service time to restart the appliance. For all non-emergency situations, follow the
documented power-down procedures in the IBM Netezza System Administrator’s
Guide to ensure that the software and databases are stopped correctly, in order, to
avoid data loss or file corruption.
Product might be powered by redundant power sources. Disconnect ALL power

sources before servicing.
High leakage current. Earth connection essential before connecting supply. Courant
de fuite élevé. Raccordement à la terre indispensable avant le raccordement au
réseau.
Homologation Statement
This product may not be certified in your country for connection by any means
whatsoever to interfaces of public telecommunications networks. Further
certification may be required by law prior to making any such connection. Contact
an IBM representative or reseller for any questions.
© Copyright IBM Corp. 2007, 2015 ix

x IBM Netezza ODBC, JDBC, and OLE DB Installation and Configuration Guide
About this publication
This guide describes the IBM Netezza® appliance implementations of International
standards for a Structured Query Language Call Level Interface (SQL CLI).
Use this information to learn about the SQL CLI, ODBC, JDBC, and OLE DB
interfaces in the IBM Netezza database environment. The topics include procedures
for installing and configuring driver managers, IBM Netezza ODBC and JDBC
drivers, the OLE DB provider, and data sources on all IBM Netezza supported
platforms.
Audience for this guide

This information is intended for IBM Netezza appliance installers and
troubleshooting staff, database administrators, database programmers, and
production analysts.
You should be familiar with Netezza concepts and user interfaces, as described in
theIBM Netezza Getting Started Tips. You should be comfortable using
command-line interfaces, Linux operating system utilities, windows-based
administration interfaces, and installing software on client systems for access.
For more information about these implementations, refer to resources such as the
following sites:
v For the Microsoft ODBC implementation of the SQL CLI standards, see
http://msdn.microsoft.com/en-us/library.
v For the Oracle Sun Developer Network JDBC implementation of the SQL CLI,
see http://java.sun.com/reference/api/index.html .
v For the Microsoft OLE DB implementation, see http://msdn.microsoft.com/en-us/
library.
If you need help

If you are having trouble using the IBM Netezza appliance, follow these steps:
1. Try the action again, carefully following the instructions for that task in the
documentation.
2. Go to the IBM Support Portal at: http://www.ibm.com/support. Log in using
your IBM ID and password. You can search the Support Portal for solutions. To
submit a support request, click the Service Requests & PMRs tab.
3. If you have an active service contract maintenance agreement with IBM, you
can contact customer support teams by telephone. For individual countries,
visit the Technical Support section of the IBM Directory of worldwide contacts
(http://www.ibm.com/support/customercare/sas/f/handbook/contacts.html).
How to send your comments

You are encouraged to send any questions, comments, or suggestions about the
IBM Netezza documentation. Send an email to netezza-doc@wwpdl.vnet.ibm.com
and include the following information:
v The name and version of the manual that you are using
v Any comments that you have about the manual
© Copyright IBM Corp. 2007, 2015 xi
v Your name, address, and phone number
We appreciate your suggestions.
xii IBM Netezza ODBC, JDBC, and OLE DB Installation and Configuration Guide
Chapter 1. General information about ODBC, JDBC, and OLE
DB
The International standard for SQL defines a standard high-level language for
accessing and manipulating the data which is stored in a relational database. The
International standard for the SQL CLI defines an application programming
interface (API) that programs use to issue SQL statements in a standardized
manner through a series of well-defined API functions.
The term Open Database Connectivity (ODBC) is a more commonly used term than
SQL CLI, and in many contexts, the two terms are used synonymously. ODBC is a
Microsoft specification for an API that constitutes an implementation of the
International standards for the SQL CLI. ODBC is a superset of the SQL API, since
it defines many functions that the International standards for the SQL API do not
define. However, the SQL CLI and the Microsoft ODBC specification are closely
aligned, and the two terms are used interchangeably especially in the C and C++
programming environments. Unless otherwise noted, the terms SQL CLI and
ODBC mean the same thing in this document.
Sun Microsystems developed a specification, called JDBC, that defines an API for
the Java™ programming environment that Java programmers use to access
relational databases and issue SQL statements. The JDBC specification defines
many of the same types of functions for Java programmers that ODBC and the
SQL CLI define for C and C++ programmers. It is possible for Java programs to
directly invoke the API functions defined by ODBC and the SQL API. However,
the nature of the Java programming environment makes this process cumbersome.
JDBC often provides a better solution than ODBC for the object-oriented Java
programming environment.
Like ODBC, JDBC is an implementation of the International standards for the SQL
CLI. The JDBC implementation consists of a set of Java interfaces, classes, and
methods that a Java programmer can use to do the same types of functions that a
C or C++ programmer uses when invoking ODBC function calls. Similarly, JDBC
constitutes a superset of the SQL CLI, since it defines many functions that the
International standards for the SQL CLI do not define.
OLE DB was designed as a higher-level replacement for ODBC to support a wider

variety of non-relational databases that do not necessarily implement SQL (for
example, object databases and spreadsheets). OLE has a client-provider model,
where clients request access to data, and providers are the software component
interfaces that allow access to the data.
Architecture of ODBC and JDBC

This section describes the architectural components of the various implementations.
ODBC architecture
The ODBC implementation is a client-server architecture, with the following major

components:
Application
The application is responsible for interacting with the user and for
© Copyright IBM Corp. 2007, 2015 1-1

invoking ODBC API functions that submit SQL statements for processing
by a file system or a database management system.
Driver Manager
The Driver Manager accepts ODBC API functions from the application and
passes them to an ODBC driver for processing. It also accepts results from
the ODBC driver and passes them to the Application.
ODBC driver
The ODBC driver processes the ODBC API functions it receives from the
Driver Manager, interacts with the file system or database management
system to access the required data, and returns results to the ODBC Driver
Manager.
Data source
A data source contains the sets of data the ODBC driver accesses, along
with all the environments associated with the data. These environments
might include file access or database access software, an operating system,
and a networking platform.
To use ODBC to access an IBM Netezza appliance, you need at least a two-tier
client-server configuration. In a two-tier client-server system, the data source is
stored on the Netezza appliance, which handles all database access processing. The
ODBC driver, driver manager, and application reside on the client system and use
a network connection to a Postgres process on the Netezza appliance host, which
coordinates SQL statement processing functions.
JDBC architecture
The JDBC architecture consists of four major components:

Java Application
The application, written in the Java programming language, is responsible
for interacting with the user and for invoking JDBC API functions. These
API functions submit SQL statements for processing by a file system or a
database management system. The Java application uses interfaces, classes,
and methods defined by the Java API to connect to and access a data
source.
Java virtual machine
When a Java application is compiled, the Java object program consists of
byte codes. The Java virtual machine is responsible for converting the Java
byte codes into instructions that can run on the machine on which the
application is running. The Java virtual machine functions as an
intermediary between the Java object program and the machine on which
the application is running. There is a different Java virtual machine
implementation for each platform. The Java virtual machine makes it
possible for the same Java program to be run, without changing or
recompiling, on any machine for which a Java virtual machine is
implemented.
JDBC driver
The JDBC driver processes the JDBC API interfaces, classes, and methods
in the Java application. The Java application uses the JDBC driver to
interact with the file system or database management system to access the
required data. It also returns results to the Java virtual machine, which, in
turn, returns those results to the Java Application. There is a different JDBC
driver for each type of DBMS or data source type. Netezza provides a
JDBC driver for Version 3.0 of the Oracle JDBC API specification. The
1-2 IBM Netezza ODBC, JDBC, and OLE DB Installation and Configuration Guide
driver is a Type 4, pure Java driver that Netezza tested for conformance
with the Oracle JDBC specifications on Windows, Linux, and UNIX
platforms. The Netezza JDBC driver supports all NZSQL data types,
includes password encryption, and provides for connection options for
host, port, and database. Starting with Netezza appliance Release 4.6, the
JDBC driver requires Java Runtime Environment (JRE) release 1.5 or later.
If your Netezza host runs release 7.1.0.0 or later and is configured to use
SP 800-131a cryptography support, your JDBC clients require Java Runtime
Environment (JRE) release 1.7 or later. If your Netezza host runs release
7.2.0.0 or later and is configured to use Kerberos authentication, your JDBC
clients require Java Runtime Environment (JRE) release 1.6 or later.
Data source
A data source contains the sets of data the JDBC driver accesses, along
with all the environments associated with the data. These environments
might include file access or database access software, an operating system,
and a networking platform.
To use JDBC to access an IBM Netezza appliance, you need at least a two-tier
client-server configuration. In a two-tier client-server system, the data source is
stored on the Netezza appliance, which handles all database access processing. The
JDBC driver, virtual machine, and JDBC application reside on the client system and
use a network connection to a Postgres process on the Netezza appliance host,
which coordinates SQL statement processing functions.
Process steps for ODBC, JDBC, and OLE DB

This section summarizes the procedures to set up ODBC, JDBC, and OLE DB, and
provides links to the complete steps.
ODBC Setup Summary
To set up an ODBC environment:

1. Install the appropriate IBM Netezza appliance client tools. See Chapter 3,
“Installing and uninstalling client software,” on page 3-1.
2. (UNIX only) Download an ODBC driver manager. See “ODBC driver
managers” on page 4-2.
3. Select the ODBC driver to install. See “ODBC driver managers” on page 4-2.
4. Configure the data source. See Chapter 5, “Installing and configuring ODBC,”
on page 5-1
5. Test connectivity. See Chapter 5, “Installing and configuring ODBC,” on page
5-1.
JDBC Setup Summary
To set up a JDBC environment:

1. Install the appropriate Netezza appliance client tools. See Chapter 3, “Installing
and uninstalling client software,” on page 3-1.
2. Install the JDBC driver. See Chapter 6, “Installing and configuring JDBC,” on
page 6-1.
3. Configure the data source. See Chapter 6, “Installing and configuring JDBC,” on
page 6-1.
Chapter 1. General information about ODBC, JDBC, and OLE DB 1-3

OLE DB Setup Summary
To set up an OLE DB environment:

1. Install the appropriate Netezza appliance client tools. See Chapter 3, “Installing
and uninstalling client software,” on page 3-1.
2. Select the OLE DB provider to install. See Chapter 7, “Installing and
configuring the OLE DB provider,” on page 7-1
3. Configure the data source. See Chapter 7, “Installing and configuring the OLE
DB provider,” on page 7-1
Chapter 2. Support and release compatibility
This section describes the supported platforms and compatibility.
Related concepts:
“Client software packages” on page 3-1
Supported platforms
IBM Netezza supplies clients that support the following platforms for ODBC and
JDBC:
Table 2-1. Netezza supported platforms
Operating system 32-bit 64-bit
Windows
Windows 2008, Vista, 7 Intel / AMD Intel / AMD
Windows Server 2012 N/A Intel / AMD
Linux
Red Hat Enterprise Linux 5.2, 5.3, 5.5, 5.9; and 6 Intel / AMD Intel / AMD
through 6.5
Red Hat Linux 6.2+ N/A PowerPC®
SUSE Linux Enterprise Server 11 Intel / AMD Intel / AMD
®
SUSE Linux Enterprise Server 10 and 11, and IBM System z IBM System z
Red Hat Enterprise Linux 5.x
UNIX
IBM AIX® 6.1 with 5.0.2.1 C++ runtime libraries, N/A PowerPC
7.1
HP-UX 11i versions 1.6, 2 (B.11.22 and B.11.23), Itanium Itanium
and 3
Oracle Solaris 10, 11 SPARC SPARC
Oracle Solaris 10 x86 x86
Note: Typically, the Netezza clients also support the update releases for each of the
OS versions listed in the table, unless the OS vendor introduced architecture
changes in the update.
The OLE DB provider is supported on the Windows clients that are shown in the
following table:
Table 2-2. OLE DB Windows support
Operating system 32-bit 64-bit
Windows 2008, Vista, 7 Intel / AMD Intel / AMD
Windows Server 2012 N/A Intel / AMD

Release compatibility matrix
The following table shows the previous version compatibility between the
implementation, the IBM Netezza driver/provider versions, and Netezza appliance
software versions.
The software and driver/provider versions shown are baseline versions. Always
check the Netezza site for the latest version to ensure up-to-date capability.
Table 2-3. Implementation, Netezza driver/provider, and software compatibility
Netezza
Implementation driver/provider Netezza appliance software
ODBC 7.0.x 5.0.x, 6.0.x, 7.0.x, 7.1.x, 7.2.x
7.1.x 6.0.x, 7.0.x, 7.1.x, 7.2.x
7.2.x 7.0.x, 7.1.x, 7.2.x
JDBC 7.0.x 5.0.x, 6.0.x, 7.0.x, 7.1.x, 7.2.x
7.1.x 6.0.x, 7.0.x, 7.1.x, 7.2.x
7.2.x 7.0.x, 7.1.x, 7.2.x
OLE DB 7.0.x 5.0.x, 6.0.x, 7.0.x, 7.1.x, 7.2.x
7.1.x 6.0.x, 7.0.x, 7.1.x, 7.2.x
7.2.x 7.0.x, 7.1.x, 7.2.x
Different driver/provider and Netezza software versions might have different

available functions, so you might need to change your driver/provider or software
version for more features.
If you have a more recent driver and you must connect to a system that runs an
older Netezza release, a set query returns an error if the Netezza system does not
support the field that is being set.
Driver version support

The following table shows the IBM Netezza support for the driver versions.
Table 2-4. Netezza driver version support
Version Windows platforms Linux/UNIX platforms
Microsoft ODBC Version 3.0 Supported Supported
Microsoft ODBC Version 3.5 Supported Supported
Oracle JDBC Specification Supported Supported
Microsoft OLE DB Version 2.7 Supported Not Supported
A distinguishing feature of the Microsoft ODBC Release 3.x specifications is that

they are closely aligned with the X/Open and ANSI/ISO/IEC International
standards for the SQL CLI.
When you install a Netezza ODBC driver in a client computer system, you must
choose one of the available drivers. You cannot install multiple Netezza ODBC
drivers in the same client system.
Standards conformance and API versions
The IBM Netezza ODBC drivers conform to the Microsoft specification for the
Open Database Connectivity (ODBC) API and the following International
standards for the SQL Call Level Interface (SQL CLI):
v The X/Open CAE Specification “Data Management: SQL Call-Level Interface
(CLI)”
v ISO/IEC 9075-3:1995 (E) Call Level Interface (SQL CLI)
The X/Open and ISO/IEC standards for the SQL CLI are published in separate
documents, but the two standards are closely aligned.
For more information about JDBC conformance and API versions, see the Oracle
documentation.
For more information about OLE DB conformance and API versions, see the
Microsoft documentation at http://msdn.microsoft.com/en-us/library.
JDBC driver data source support

Up to 4.5.x, JDBC driver implementations for data sources had some limitations,
such as not allowing users to set different connection properties, such as:
securityLevel, caCertFile, loggerType. In 4.6, these data sources were removed and
improved data sources are added, as shown in the following table:
Table 2-5. Data source support changes
JDBC interface Former implementation New implementation Remarks
javax.sql.DataSource org.netezza.jdbc2.optional. org.netezza.datasource. Basic DataSource
SimpleDataSource NzDatasource implementation.
javax.sql.DataSource org.netezza.jdbc2.optional. org.netezza.datasource. Basic DataSource
PoolingDataSource NzConnectionPool implementation with
connection pooling
implemented inside it. Use
the connections provided
by this data source directly
as normal connections. The
Data Source internally
handles the pooling. Do
not use this data source if
your server/middleware
vendor provides a
connection pooling
implementation. This data
source is provided as a
convenience only.
javax.sql.ConnectionPool org.netezza.jdbc2.optional. org.netezza.datasource. Basic
DataSource ConnectionPool NzConnectionPoolDatasource ConnectionPoolDataSource
implementation.
IBM Netezza release 7.1 added support for IBM DB2 24:00:00 time support as an
optional configuration for the database. However, JDBC has limited support for the
24:00:00 time format. If you use the 24:00:00 time support in your Netezza
database, note that JDBC uses the value 23:59:59:999999 to represent the 00:00:00
time value of the next day.
Chapter 2. Support and release compatibility 2-3

Chapter 3. Installing and uninstalling client software
The IBM Netezza appliance client tools contain the ODBC drivers, JDBC drivers,
and the OLE DB provider that connect to a Netezza appliance from a client
system.
The first step in preparing a system for ODBC, JDBC, or OLE DB is to install the
Netezza appliance client tools software on your system. If these client tools are
installed, skip this section. After you install the client tools, you can install the
ODBC drivers, JDBC drivers, or the OLE DB provider.
The minimum disk space required to install each client is as follows:

v ODBC: 100 MB
v JDBC: 10 MB
v OLE DB: 100 MB
Related concepts:
Chapter 4, “ODBC drivers and driver managers,” on page 4-1
Chapter 5, “Installing and configuring ODBC,” on page 5-1
“Configuring ODBC for UNIX/Linux” on page 5-7
Chapter 6, “Installing and configuring JDBC,” on page 6-1
“Installing JDBC for UNIX/Linux” on page 6-1
Client software packages

Users who have access to IBM Passport Advantage® or Fix Central can download
the Netezza client kits in electronic format. Software media for the clients is also
available from Passport Advantage. Users must have accounts and the appropriate
support permissions to download the software from these locations. For more
information about Passport Advantage, see http://www.ibm.com/software/
howtobuy/passportadvantage/pao_customers.htm.
The client package names have format nz-platformclient-version.archive, where

platform is a client operating system type, version is a Netezza software release
version, and archive is the file compression format for the client.
Related concepts:
Chapter 2, “Support and release compatibility,” on page 2-1
Windows client tools software installation

The IBM Netezza Client Components–Windows DVD contains the Windows
nzsetup.exe command which installs the IBM Netezza Windows client tools. The
installation program installs the NzAdmin tool, several command-line executable
files and libraries, online help files, and Netezza guides in PDF format.
Installation requirements
The installation package requires a computer system that runs a supported
Windows operating system such as Windows Vista (32-bit and 64-bit), Windows

2008 (32-bit and 64-bit), Windows 7 (32-bit and 64-bit), and Windows Server 2012
(64-bit). The client system must also have either a CD/DVD drive or a network
connection.
If you use or view object names that use UTF-8 encoded characters, your Windows
client systems require the Microsoft universal font to display the characters within
the NzAdmin tool. The Arial Unicode MS font is installed by default on some
Windows systems, but you might need to run a manual installation for other
Windows platforms such as 2003 or others. For more information, see the Microsoft
support topics available on the Microsoft website.
Installing the Netezza tools on Windows

To install the IBM Netezza tools on Windows:
1. Insert the IBM Netezza Client Components–Windows into the DVD drive of your
client system.
Make sure that you use the client release that matches the Netezza software
release of your Netezza system. Do not use Netezza clients to manage Netezza
systems that have a different Netezza release.
If you downloaded the client package (nz-winclient-version.zip) to a
directory on your client system, change to that directory and extract the
package.
2. Double-click or run nzsetup.exe.
This is a standard installation program that consists of a series of steps in
which you select and enter information that is used to configure the
installation. You can cancel the installation at any time.
The installation program displays a license agreement, which you must accept to
install the client tools. You can also specify the following information:
Destination folder
You can use the default installation folder or specify an alternative
location. The default folder is C:\Program Files\IBM Netezza Tools. If you
choose a different folder, the installation program creates the folder if one
does not exist.
Setup type
Select the type of installation: typical, minimal, or custom.
Typical
Install the NzAdmin program, the help file, the documentation,
and the console utilities.
Minimal
Install the NzAdmin program and help files.
Custom
Install any combination of the administration application, console
applications, or documentation.
After you complete the selections and review the installation options, the client
installer creates the Netezza Tools folder, which has several subfolders. You cannot
change the subfolder names or locations.
Bin Executable files and support files
Doc Copies of the Netezza user guides and an Acrobat Index to search the doc
set
Help Application help files
jre Java runtime environment files for the installer and uninstaller programs of
the Netezza tools
sys Application string files
Uninstall Netezza Tools
Files to remove Netezza tools from the client system
The installation program displays a dialog when it completes. On some systems, it

might prompt you to reboot the system before you use the application.
The installation program adds the Netezza commands to the Start > Programs
menu. The program group is IBM Netezza and it has the suboptions IBM Netezza
Administrator and Documentation. The IBM Netezza Administrator option starts
the NzAdmin tool. The Documentation command lists the installed user guide
PDFs.
To use the commands in the bin directory, you must open a Windows
command-line prompt (a DOS prompt).
Environment variables
The following table lists the operating system environment variables that the
installation tool adds for the IBM Netezza console applications.
Table 3-1. Environment variables
Variable Operation Setting
NZ_DIR set Installation directory (for example C:\Program Files\IBM
Netezza Tools)
PATH append installation directory\bin
UNIX client tools software installation

The IBM Netezza UNIX clients DVDs and packages contain a tar file of the client
software for a platform and an unpack script. You use the unpack script to install
the client Netezza commands and their necessary files to the UNIX client system.
Installing the UNIX clients

The topic describes how to install the IBM Netezza UNIX client packages on 32-bit
and 64-bit operating system workstations.
If you are installing the clients on 64-bit operating systems, there are some
additional steps to install a second, 64-bit client package. The IBM Netezza clients
are 32-bit operating system executables and they require 32-bit libraries that are not
provided with the clients. If the libraries are not already installed on your system,
you must obtain and install the libraries using your operating system update
process.
1. Obtain the nz-platformclient-version.archive) client package from the IBM
Fix Central site and download it to the client system. Use or create a new,
empty directory to reduce any confusion with other files or directories. There
are several client packages available for different common operating system
types, as described in “Supported platforms” on page 2-1. Make sure that you
obtain the correct client package. These instructions use the Linux client
package as an example of the procedure.
Chapter 3. Installing and uninstalling client software 3-3

2. Log in to the workstation as the root user or a superuser account.
3. Change to the directory where you saved the client package, then uncompress
and extract the contents.
For the Linux client, use the gunzip command to uncompress the client
package, then you use a command such as tar xzf nz-linuxclient-
version.tar.gz to extract the package. To extract the other UNIX packages,
such as AIX, you might need to run other commands, such as uncompress to
uncompress the archive.The unpack process for the Linux package creates a
linux directory, a linux64 directory, a webadmin directory, and a
datadirect.package.tar.z file. Ignore the webadmin directory, which contains
the Web Admin interface client.
4. Change to the linux directory and run the unpack command to install the 32-bit
CLI files: ./unpack.
Note: On an HP-UX 11i client, /bin/sh might not be available. You can use the
command form sh ./unpack to unpack the client.
The unpack command checks the client system to ensure that it supports the
CLI package and prompts you for an installation location. The default is
/usr/local/nz for Linux, but you can install the CLI tools to any location on
the client. The program prompts you to create the directory if it does not
already exist. Sample command output follows:
------------------------------------------------------------------
IBM Netezza -- NPS Linux Client 7.1.0.0
(C) Copyright IBM Corp. 2002, 2014 All Rights Reserved.
------------------------------------------------------------------
Validating package checksum ... ok
Where should the NPS Linux Client be unpacked? [/usr/local/nz]
Directory ’/usr/local/nz’ does not exist; create it (y/n)? [y] Enter
0% 25% 50% 75% 100%
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Unpacking complete.
5. If your client has a 64-bt operating system, change to the linux64 directory and
run the unpack command to install the 64-bit CLI files:./unpack.
The unpack command prompts you for an installation location. The default is
/usr/local/nz for Linux, but you should use the same location that you used
for the 32-bit CLI files in the previous step. Sample command output follows:
------------------------------------------------------------------
IBM Netezza -- NPS Linux Client 7.1.0.0
(C) Copyright IBM Corp. 2002, 2014 All Rights Reserved.
------------------------------------------------------------------
Validating package checksum ... ok
Where should the NPS Linux Client be unpacked? [/usr/local/nz]
Installing in an existing directory. Changing permissions to
overwrite existing files...
0% 25% 50% 75% 100%
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Unpacking complete.
The client installation steps are complete, and the Netezza CLI commands are
installed to your specified destination directory. The NPS commands are located in
the bin directory where you unpacked the NPS clients. If you are using a 64-bit
operating system on your workstation, note that there is a 64-bit nzodbcsql
command in the bin64 directory for testing the SQL command connections.
Test to make sure that you can run the client commands. Change to the bin
subdirectory of the client installation directory (for example, /usr/local/nz/bin).
Run a sample command such as the nzds command to verify that the command
succeeds or to identify any errors.
./nzds -host nzhost -u user -pw password
The command displays a list of the data slices on the target NPS system. If the
command runs without error, your client system has the required libraries and
packages to support the Netezza clients. If the command fails with a library or
other error, the client may require some additional libraries or shared objects.
For example, on a Red Hat Enterprise Linux 64-bit client system, you could see an
error similar to the following:
[root@myrhsystem bin]# ./nzds
-bash: ./nzds: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
For example, on a SUSE 10/11 64-bit client system, you could see an error similar
to the following:
mylinux:/usr/local/nz/bin # ./nzds
./nzds: error while loading shared libraries: libssl.so.4: cannot open shared
object file: No such file or directory
mylinux:/usr/local/nz/bin # ldd nzds

linux-gate.so.1 => (0xffffe000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0xf76f1000)
libdl.so.2 => /lib/libdl.so.2 (0xf76ec000)
libssl.so.4 => not found
libcrypto.so.4 => not foundlibm.so.6 => /lib/libm.so.6 (0xf76c4000)
libc.so.6 => /lib/libc.so.6 (0xf7582000)
/lib/ld-linux.so.2 (0xf773f000)
These errors indicate that the client is missing 32-bit library files that are required
to run the NPS clients. Identify the packages that provide the library and obtain
those packages. You may need assistance from your local workstation IT
administrators to obtain the operating system packages for your workstation.
To identify and obtain the required Red Hat packages, you could use a process
similar to the following.
v Use the yum provides command and specify the file name to see which package
provides the file that could not be found (ld-linux.so.2 in this example).
yum provides ld-linux.so.2
Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use
subscription-manager to register.
RHEL64 | 3.9 kB 00:00 ...
glibc-2.12-1.107.el6.i686 : The GNU libc libraries
Repo : RHEL64
Matched from:
Other : ld-linux.so.2
In this example, the missing package is glibc-2.12-1.107.el6.i686.
v In some cases, the NPS command could report an error for a missing libssl file.
You can use the yum provides command to obtain more information about the
packages that contain the library, and if any of the files already exist on your
workstation.
yum provides */libssl*
Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use
subscription-manager to register.

nss-3.14.0.0-12.el6.x86_64 : Network Security Services
Repo : RHEL64
Matched from:
Filename : /usr/lib64/libssl3.soopenssl-devel-1.0.0-27.el6.x86_64 : Files for
: development of applications which will use OpenSSL
Repo : RHEL64
Matched from:
Filename : /usr/lib64/pkgconfig/libssl.pc
Filename : /usr/lib64/libssl.so
To resolve the problem, you may need to obtain and install the package
nss-3.14.0.0-12.el6.x86_64 or you might be able to create a symbolic link if
the library already exists on your system. Use caution when creating symbolic
links or changing the library files. You should consult with your IT department
to ensure that you can obtain the needed packages, or that changes to the
symbolic links will not impact the operation of other applications on your
workstation.
Based on the missing libraries and packages, use the following steps to obtain the
Red Hat packages.
v Mount the Red Hat distribution DVD or ISO file to the client system. Insert the
DVD into the DVD drive.
v Open a terminal window and log in as root.
v Run the following commands:
[root@myrhsystem]# mkdir /mnt/cdrom
[root@myrhsystem]# mount -o ro /dev/cdrom /mnt/cdrom
v Create the text file server.repo in the /etc/yum.repos.d directory.
Note: To use gedit, run the command: gedit /etc/yum.repos.d/server.repo

and add the following text to the file where baseurl is the mount point and the
RHEL distribution. In the example, the mounting point is cdrom and the RHEL
distribution is Workstation but it could be a server or the ISO file.
name=server
baseurl=file:///mnt/cdrom/Workstation
enabled=1
v Run the command: yum clean all
v Run the command to import related public keys: rpm --import
/mnt/cdrom/*GPG*
v Run the following command to install the required libraries: yum install
<package-name> where <package-name> is the file that contains the libraries that
you require for the NPS command operations.
To identify and obtain the required SUSE packages, you could use a process
similar to the following.
v Log in to the SUSE system as root or a superuser.
v If the test NPS command failed with the error that libssl.so.4 or
libcrypto.so.4 or both could not be found, you could be able to resolve the
issue by adding a symbolic link to the missing file from the NPS client
installation directory (for example, /usr/local/nz/lib). Use the ls /lib/libssl*
command to list the available libraries in the standard OS directories. You could
then create symbolic links to one of your existing libssl.so and libcrypto.so
files by using commands similar to the following:
mylinux:/usr/local/nz/lib # ln -s /usr/lib/libssl.so.0.9.8 /lib/libssl.so.4
mylinux:/usr/local/nz/lib # ln -s /usr/lib/libcrypto.so.0.9.8 /lib/libcrypto.so.4
v If you are missing other types of files or libraries, use the zypper wp command
and specify the file name to see which package provides it. An example follows.
zypper wp ld-linux.so.2
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
--+-------------+---------+----------+--------+---------------------------------
i | glibc-32bit | package | 2.9-13.2 | x86_64 | SUSE-Linux-Enterprise-Desktop-11
In this example, the missing package is glibc-32bit.
If the error indicates that you are missing other libraries or packages, use the
following steps to obtain the SUSE packages.
v Open a terminal window and log in as root.
v Run the yast command to open the YaST interface.
v One the YaST Control Center, select Software and go to the software repositories
to configure and enable a DVD, a server, or an ISO file as a repository source.
Select the appropriate source for your SUSE environment. Consult with your IT
department about the policies for package updates in your environment.
v On the Software tab, go to Software Management and search for the required
package or library such as glibc-32bit in this example.
v Click Accept to install the required package.
v Exit YaST by clicking Quit.
Set the path for Netezza CLI client commands

You can run most of the CLI commands from the IBM Netezza client systems,
except for nzstart and nzstop which run only on the host Netezza system.
To run the CLI commands on Solaris, you must include /usr/local/lib in your
environment variable LD_LIBRARY_PATH. Additionally, to use the ODBC driver on
Linux, Solaris, or HP-UX, you must also include in the LD_LIBRARY_PATH the
pathname /usr/local/nz/lib, or the directory path to nz/lib where you installed
the Netezza CLI tools.
Removing the Netezza tools on Windows

You can remove or uninstall the Windows tools by using the Control Panel. The
uninstallation program removes all folders, files, menu commands, and
environment variables. The registry entries created by other IBM Netezza
applications are not removed.
1. Click Start > Control Panel > Uninstall a program. The menu options can vary
with each Windows operating system type.
2. In the Programs and Features window, select IBM Netezza Tools, then click
Uninstall/Change. The Uninstall IBM Netezza Tools window opens.
3. Click Uninstall. The removal usually completes in a few minutes. Wait for the
removal to complete.
4. Using the File Explorer, check the installation location, which is usually
C:\Program Files\IBM Netezza Tools. If the Windows client was the only
installed Netezza software, you can delete the IBM Netezza Tools folder to
completely remove the application.
Remove the CLI clients from UNIX systems

To remove the client CLI kits from a UNIX system, change to the directory where
you installed the clients (for example, /usr/local/nz) and manually delete the
Netezza commands.

Chapter 4. ODBC drivers and driver managers
You can have only one ODBC driver installed on your system at a time. If you
need a different driver, remove the installed driver and install the different one.
Related concepts:
Chapter 3, “Installing and uninstalling client software,” on page 3-1
Chapter 5, “Installing and configuring ODBC,” on page 5-1
ODBC drivers
An ODBC driver uses a layer of code that translates the ODBC standard API calls
the application issues into vendor-specific functions. IBM Netezza supplies an
ODBC driver for many supported platforms (32-bit and 64-bit), and for many
different versions of the Netezza database.
ODBC drivers show the capabilities of the underlying data source, and each ODBC
driver is designed for a particular database management system. For example, an
ODBC driver designed to access a different vendor database cannot be used to
access a Netezza database.
ODBC driver tasks

ODBC drivers do various tasks, including:
v Connecting to and disconnecting from data sources.
v Checking for errors.
v Submitting SQL statements to the database management system software for
execution against a particular data source.
v Converting ODBC-standard SQL statements, if necessary, to DBMS-specific SQL
statements.
v Sending data to and retrieving data from a data source.
v Performing data conversion functions, as specified by the application.
v Returning information about the success or failure of an ODBC function.
ODBC driver properties

This section describes the meaning and purpose of each ODBC driver property.
Parameters define the properties of IBM Netezza ODBC drivers, configured either
through Windows or a UNIX/Linux configuration file. Use this information to
select appropriate values for each driver property during the driver configuration
process.
Table 4-1. ODBC driver properties
Property Setting
DebugLogging Select this option to activate debug logs. By default, logging is
disabled. To enable logging, select the property on the Windows
dialog, or for UNIX, specify a Boolean such as 1 or true.
Log File Path The location of the debug log files. The default is /tmp on
UNIX/Linux systems or C:\ on Windows systems.

Table 4-1. ODBC driver properties (continued)
Property Setting
Prefetch Count A numeric value that sets the number of rows the driver retrieves at a
time from a Netezza database. The default is 256 rows. To tune your
application, set a value that optimizes network use versus memory
use. The higher this value, the more memory is required to hold these
rows.
Socket Buffer Size A numeric value that specifies the size of the communications buffer
in bytes. The range is 1 K to 32 K. The default is 8192.
Character The Netezza appliance uses the Latin9 character encoding for char
Translation Option and varchar types. The character encoding for many Windows
systems is similar, but not identical. If your database includes
characters that use only the basic subset of letters (a-z or A-Z),
numbers (0-9), or punctuation characters, select the Optimize for
ASCII character set option for the driver on Windows, which
improves query performance. If your data includes special characters
such as the Euro symbol or others, clear the option so that the
characters convert correctly.
Unicode For UNIX/Linux drivers, specifies the unicode encoding value. Valid
Translation Option values are utf8, utf16, and utf32. The default is utf8.
Related concepts:
Appendix B, “Troubleshooting,” on page B-1
ODBC driver managers

The ODBC driver manager serves as an intermediary between an application and
an ODBC driver. It provides a single place for an application to invoke most
ODBC API functions. In most DBMS application environments, including the IBM
Netezza appliance environment, the application is linked to the driver manager
and is not linked directly to a specific ODBC driver.
The driver manager is the ODBC component that manages communication

between applications and ODBC drivers. In most cases, ODBC applications issue
ODBC API calls to the driver manager, and the driver manager, in turn, passes
those ODBC API function calls to the appropriate ODBC driver. The ODBC driver
then accesses the underlying database management system software.
For performance reasons, depending on the database management system software

used, some API functions might bypass the driver manager and access the ODBC
driver directly.
ODBC driver manager tasks

The driver manager handles a number of tasks that all ODBC applications need,
regardless of the particular ODBC driver they use or the data source they access.
These tasks include the following:
v Loading into memory the ODBC driver required by the application and the data
source it is accessing.
v Unloading from memory ODBC drivers when they are no longer needed.
v Passing ODBC API function calls from the application to an appropriate ODBC
driver.
v Performing any required ODBC API function call conversions. For example, if an
ODBC application issues ODBC 2.5 function calls and is using an ODBC 3.0
driver, the driver manager converts ODBC 2.5 function calls to their ODBC 3.0
equivalents when necessary.
v Performing error checking and validation functions on ODBC API function calls
before passing them to the ODBC driver.
v Performing some character set conversions. For example, if the application uses
an 8-bit ASCII character set, and the ODBC driver and DBMS work with
character data in 16-bit Unicode format, the driver manager does the necessary
character conversions.
The driver manager component is used only with ODBC. There is no separate
driver manager component in the JDBC architecture. With JDBC, all driver
manager functions run in the Java application environment.
Windows driver managers

Microsoft provides a driver manager for the Windows environment. The ODBC
driver manager is part of the Microsoft Data Access Component (MDAC) and, as
such, is part of the Windows operating system. Therefore, you do not have to
install a driver manager in the Windows environment to use the IBM Netezza
ODBC drivers.
Linux/UNIX driver managers

To use the IBM Netezza ODBC drivers in a Linux/UNIX environment, you must
install an appropriate driver manager. You can get driver manager components
from a number of sources.
v Open source
There are a number of driver managers available on the web from open source
software projects. Netezza supports the unixODBC driver manager component
for Linux/UNIX platforms. You can find information about unixODBC and
download kits at http://www.unixodbc.org.
v Commercial
A number of commercial software vendors develop and market ODBC
components, including driver managers. Netezza has licensed and provides
support for the DataDirect driver manager from DataDirect Technologies,
included with your system. It is not necessary to install the Netezza-licensed
version of the DataDirect driver manager to access the Netezza ODBC drivers.
You can find more information at http://www.datadirect.com.
Installing the unixODBC driver manager

This procedure is an example of how to install the unixODBC driver manager on a
UNIX/Linux system. If your installation uses a different driver manager, skip this
section. The steps are based on version 2.2.12, and assumes that the name of the
downloaded file is unixODBC-2.2.12.tar.gz. The file name might be different if
you download a later release. Match the file and directory names in the procedure
to the name of the file you download. Consult the README and INSTALL files
contained in the downloaded package to identify the specific steps for your driver.
1. Since the unixODBC installation procedure requires write access to the root of
the file system to create installation directories, log in as the superuser to
access the system during the installation process to use the default installation
directories.
2. Download the driver manager file from the www.unixodbc.org website.
Chapter 4. ODBC drivers and driver managers 4-3

3. Extract the downloaded file by issuing the following command: gzip -d
unixODBC-2.2.12.tar.gz
4. Run the following command to extract the contents of the
unixODBC-2.2.12.tar file: tar -xvf unixODBC-2.2.12.tar
5. Run the following command to change to the subdirectory created when the
unixODBC-2.2.12.tar file was extracted: cd undixODBC-2.2.12.
6. Run the following command to configure the software and set the installation
directory to /usr/local/unixODBC: ./configure --prefix=/usr/local/unixODBC
7. To configure without the GUI, run the following command: ./configure
--prefix=/usr/local/unixODBC --enable-gui=no
8. Run the following command to compile the package (this step might take a
few minutes to complete): make
9. Run the following command to install the programs, data files, and
documentation: make install
This step places the bin, etc, lib, and include subdirectories in the
/usr/local/unixODBC directory. These subdirectories contain the programs,
data files, and documentation for the unixODBC driver manager package.
10. Run the appropriate commands to add bin and lib subdirectories to the
environment:
For AIX:
export PATH=$PATH:/usr/local/unixODBC/bin
export LIBPATH=$LIBPATH:/usr/local/unixODBC/lib
For HP-UX:
export SHLIB_PATH=$SHLIB_PATH:/usr/local/unixODBC/lib
For Linux, Solaris:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/unixODBC/lib
The previous commands change the environment for the current session only.
After you verify that your environment modifications work correctly, edit
your login script to set the environment variables when users log in.
11. To free disk space, you can delete the installation tar file from the file system:
rm unixODBC-2.2.12.tar
If preferred, you can move the installation tar file to somewhere else in the
file system for safekeeping.
DataDirect driver manager installation

The driver manager from DataDirect Technologies is now included within each
UNIX client tar package. Consult the README and INSTALL files contained in the
platform-specific directories to determine whether the procedure needs to be
modified.
Chapter 5. Installing and configuring ODBC
This section describes the procedures used for installing and configuring ODBC
drivers and data sources for Windows or UNIX/Linux systems.
Related concepts:
Chapter 4, “ODBC drivers and driver managers,” on page 4-1
Installing and configuring ODBC for Windows

This section describes procedure for installing an IBM Netezza ODBC driver on a
Windows client system, configuring the driver and data sources, and testing for
connectivity to Netezza appliance data sources.
If you have already installed a Netezza ODBC driver on your computer system, go
to “ODBC driver data source configuration for Windows” on page 5-2.
The nzodbcsetup.exe executable file is the ODBC driver installation program. The
installation program installs the Netezza ODBC libraries on your system, creates a
Netezza SQL system data source entry (NZSQL) with appropriate default values,
and adds the appropriate entries to the Windows registry.
You can install the ODBC driver from the command line, or by double-clicking the
ODBC installation program, which runs the interactive GUI. The command-line
option can run the installation from the GUI or in silent mode, which is useful if
you use a software management program to install the ODBC driver on your client
systems.
Note: You can have only one ODBC driver installed on a Windows client system
at a time. If you need a different driver, install the new driver over the existing
driver.
ODBC driver command-line installation for Windows

To install the ODBC driver from the Windows command line, run the nzodbcsetup
executable file in the appropriate directory on your system. This file installs the
32-bit ODBC driver and libraries on 32-bit Windows platforms, and both 32-bit and
64-bit drivers and libraries on 64-bit platforms. The following example uses the C:
drive, however you can install wherever appropriate.
C:\>nzodbcsetup.exe
For a silent installation, run the setup with the silent option:
C:\>nzodbcsetup.exe -i silent
Installing the ODBC driver for Windows with the GUI

Follow these steps to install an IBM Netezza ODBC driver for Windows by using
the GUI. The examples are for a Windows 7 system, but the procedure is similar
for other Windows systems.
1. Start the installation program by double-clicking the nzodbcsetup.exe
executable file. It is in the /drivers directory of the Windows installation
package.

2. When a language option window opens, accept the default of English and click
OK. The language option window controls the language for the installation
program.
3. Review the information and click Next when the Introduction window opens.
4. If you are given the option to select the bit size of your driver, select 32-bit,
64-bit, or both, and click Next. On 64-bit systems, you are given the option of
selecting the bit size of the driver to install. On 32-bit systems, this window is
not displayed.
5. When the Character Translation Option window opens, specify whether you
will use only the basic subset of characters, such as letters (a-z or A-Z),
numbers (0-9), or punctuation marks in the CHAR and VARCHAR data types.
If you use only these characters, select the Optimize for ASCII character set
option to improve data transfer performance. However, if you use characters
such as the Euro symbol or other characters that are outside the basic set, do
not select the optimize option. Setting this option causes the characters that you
enter to be converted to the correct encodings so that they display correctly in
your query results. Click Next.
6. Install the Visual Studio C++ 2010 (VS2010) Libraries on the client system.
7. When the Pre-Installation Summary window opens, review your installation
choices. You can click Previous to page back through and select different
choices. When finished, click Install.
After you click Install, the installation program does the following processing:
v Installs the Netezza ODBC driver. A 32-bit driver on a 32-bit system and a
64-bit driver on a 64-bit system are installed in the \WINDOWS\system32 folder.
If installing both 32-bit and 64-bit drivers on a 64-bit system, the 32-bit driver
is installed in the \WINDOWS\SysWOW64 folder.
v Places entries in the Windows registry to add your selected ODBC driver to
the driver list.
v Places entries in the Windows registry to add the NZSQL data source to the
data source list.
8. When the Installation Complete window opens, click Done to close the
program. This window indicates that the installation process completed
successfully.
Before trying to access an ODBC data source, you must configure it. The next
section describes the configuration procedure.
ODBC driver data source configuration for Windows

After you install an IBM Netezza ODBC driver, the installation program creates an
entry for a system data source called NZSQL. You then configure that data source
to connect to a Netezza appliance data source. You can also configure a user data
source.
v A System DSN defines a data source available to all users of the client system.
v A User DSN defines a data source available only to the user who defined it.
Get the following configuration information from your Netezza system

administrator:
v The name of the database (and schema, if the databases support multiple
schemas) on the Netezza appliance.
v The server host name or IP address of your Netezza appliance.
v A valid user ID for accessing the system or user data source.
v A valid password for accessing the system or user data source.
Configuring the data source
The following steps outline the procedure to configure an IBM Netezza appliance
data source.
This procedure is for configuring a 32-bit DSN on a 32-bit system or a 64-bit DSN
on a 64-bit system. The 32-bit DSNs do not display in the 64-bit administrator. On
a 64-bit system, start the administrator by using the following file:
C:\windows\syswow64\odbcad32.exe
1. Open the ODBC Data Source Administrator window and select either the
System DSN tab or the User DSN tab for the appropriate configuration. Then
select either of the following options:
v To configure an existing DSN, select Configure.
v To configure a new DSN, select Add.
2. Configure the DSN and Driver Options from the Driver Setup window.
3. Test and verify the ODBC Connection.
4. Close any open configuration windows to finish the Data Source Configuration.
ODBC Data Source Administrator window:
You can make configuration selections in the ODBC Data Source Administrator
window.
To open the window, select Start > Administrative Tools > Data Sources (ODBC).
In the ODBC Data Source Administrator window, select either the System DSN tab
or the User DSN tab and select either Configure or Add:
v Selecting Add displays the Create New Data Source window. Select NetezzaSQL
as the driver and click Finish. The ODBC Driver Setup window opens.
v Selecting the System DSN tab displays a list of System Data Sources. Selecting
Configure displays the ODBC Driver Setup window.
ODBC Driver Setup window:
You can configure the DSN and Driver Options in the ODBC Driver Setup
window.
Select the DSN Options tab and enter appropriate values for the DSN Options. If
your application supplies a user name and password, these fields can be left blank,
since the user name and password of your application takes precedence over the
ones specified here. If the application does not supply a user name and password,
supply the values. For other options, you can accept the default values or change
the options.
Data source
A name that identifies the database connection properties.
Server The host name or IP address of the IBM Netezza system to which the
ODBC driver connects.
Database
The name of the database on the Netezza system.
Schema
The name of the schema within the specified database on the Netezza
system. This field is used for Netezza systems that support multiple
schemas within a database. If you do not specify a schema, you will
connect to the default schema of the database.
Chapter 5. Installing and configuring ODBC 5-3

User name
The user ID of the account on the Netezza system used to access the data
source.
Description
A description or comment about the data in the data source.
Port The port number for the data source. The default is 5480.
Password
The assigned password for the user specified.
The Advanced DSN Options tab displays more options. You can change these
options or accept the default options.
Read Only
If selected, this option restricts queries to read-only access of the database
(only SQL Select statements are allowed). The option is not selected by
default to support full access to the databae. To allow queries that modify
data, do not select the option.
Show System Tables
When retrieving a list of tables, select this option to include system tables
in the list. The option is not selected by default to hide the system tables.
Legacy SQL Tables Behavior
Select this option to cause SQLTables to return a list of all of the users that
own a database. The option is not selected by default to omit the list of
users.
Treat Numeric as Char
If selected, this option causes the driver to treat SQL_C_NUMERIC buffers
as SQL_C_CHAR buffers. The option is not selected by default and
SQL_C_NUMERIC buffers are treated as Numeric Structures.
Return SQL_BIT as 1/0
This option controls the Boolean value return form when a return type is
char or wchar. Select the option to configure SQL_BIT to return numeric
Boolean values (1 and 0). The option is not selected by default to return
character values (true or false).
Strip CR/LF
If selected, this option removes the carriage return and line feed characters
from the SQL statements. The option is not selected by default to retain
these control characters in your data.
Load Round Fraction
Select this value to round the actual data for numeric columns whose
precision exceeds the precision defined in the target table. The option is
not selected by default, which means that the data is not rounded.
Ignore Floating Point Truncation
Select this option to configure ODBC clients on the AIX platform to return
a warning when a floating point value is truncated during bigint to double
conversions and to return the value. The option is not selected by default,
so the query returns an "out of range" error for the floating point
exception.
Enable Fast Select
Select this option if you want to ODBC driver to skip the data type
conversions that occur when ODBC applications run SELECT queries.
Skipping the data conversion can improve SELECT query performance, but
if the application requests a cast conversion of some kind, the query will
fail. The option is not selected by default and the driver performs the data
type conversion.
Date Format
Specifies the date format you want as one of the following values:
v 1 = YMD. This value is the default.
v 2 = MDY
v 3 = DMY
On Windows platforms, you specify the text value (such as YMD); on
non-Windows platforms, specify the numeric value (such as 1).
Client User ID
Specifies a sample client user ID for the connection. This field supports
application monitoring by various tools such as IBM InfoSphere® Optim™
Performance Manager. The maximum length of the field can vary from 128
characters on Windows clients to 1024 characters on Linux clients,
including a null byte length.
Client Workstation Name
Specifies a sample client workstation name for the connection. This
optional field supports application monitoring by various tools such as
IBM InfoSphere Optim Performance Manager. The maximum length of the
field can vary from 128 characters on Windows clients to 1024 characters
on Linux clients, including a null byte length.
Client Application Name
Specifies a sample client application name for the connection. This optional
field supports application monitoring by various tools such as IBM
InfoSphere Optim Performance Manager. The maximum length of the field
can vary from 128 characters on Windows clients to 1024 characters on
Linux clients, including a null byte length.
Client Acct String
Specifies a sample client account string for the connection. This optional
field supports application monitoring by various tools such as IBM
InfoSphere Optim Performance Manager. The maximum length of the field
can vary from 128 characters on Windows clients to 1024 characters on
Linux clients, including a null byte length.
Client Program Info
Specifies a sample client program information string for the connection.
This optional field supports application monitoring by various tools such
as IBM InfoSphere Optim Performance Manager. The maximum length of
the field can vary from 128 characters on Windows clients to 1024
characters on Linux clients, including a null byte length.
Login timeout
The number of seconds after which to end the login process. Valid values
are 0 (no timeout) or any positive number.
Query timeout
The number of seconds after which to end the query request. Valid values
are 0 (no timeout) or any positive number.
Load Max Errors
Stops the load after N bad input rows. Default is 1, and 0 means no limit,
with a maximum of 2,147,483,647 (the largest signed 32-bit integer).

The SSL DSN Options tab shows Secure Socket Layer options. Select one of the
following options for the Security Level, and enter a certificate authority (CA) file
name.
Security Level
The level of security for the connection.
Only Unsecured
Only connections that do not use SSL to encrypt data are accepted.
This security level provides increased performance but carries the
risks that come with an unencrypted connection.
Preferred Unsecured
Connections that do not use SSL are preferred, but a connection is
not refused solely because it uses SSL encryption.
Preferred Secured
(Default) Connections that use SSL are preferred, but a connection
is not refused solely because it does not use SSL encryption.
Only Secured
Only connections that use SSL to encrypt data are accepted. This
security level provides increased security but reduces performance
somewhat, due to the necessity of encrypting the data stream.
CA Certificate File
Enter the name of the CA file (including the path) that will be used to
authenticate connections. If a CA is used for authentication, the name of
the CA file must match the name defined by the system administrator for
the database to which you are attempting to connect. For more information
about security and authentication, see IBM Netezza System Administrator’s
Guide.
Use the Driver Options tab to configure global driver options.

Enable Debug Logging
Select this option if you want the system to log information about each
ODBC connection. This information can be helpful in debugging
connection problems.
Log File Path
The location of the debug log files. The default is C:\ on Windows
systems.
Optimize for ASCII character set
The Netezza appliance uses the Latin9 character encoding for char and
varchar types. The character encoding for many Windows systems is
similar, but not identical. If your database includes characters that use only
the basic subset of letters (a-z or A-Z), numbers (0-9), or punctuation
characters, select the Optimize for ASCII character set option for the driver
on Windows, which improves query performance. If your data includes
special characters such as the Euro symbol or others, clear the option to
ensure that the characters convert correctly.
Prefetch Count
A numeric value that sets the number of rows the driver fetches at a time
from a Netezza database. The default is 256 rows. To tune your
application, set a value that optimizes network use versus memory use.
The higher this value, the more memory is required to hold these rows.
Socket Buffer Size
A numeric value that specifies the size of the communications buffer in
bytes. The range is 1 K to 32 K. The default is 8192.
Related concepts:
Appendix B, “Troubleshooting,” on page B-1
Test the connection:

When finished selecting DSN and Driver options, select the DSN Options tab and
click Test Connection to establish a connection to this data source on your IBM
Netezza appliance server. A message box displays, indicating that the connection
attempt was either successful or failed. If the connection attempt fails, check for
erroneous configuration information, correct it, and test the connection again. If
you cannot establish a connection after checking for errors, contact your Netezza
system administrator.
A successful connection message indicates that you successfully configured an

entry for the system data source. To end the configuration process, close all the
open dialog boxes.
Configuring ODBC for UNIX/Linux

This section describes the process for configuring ODBC and your IBM Netezza
appliance data source for UNIX/Linux.
You can access the files you need for the Netezza ODBC drivers and the ODBC
driver installation from the Netezza FTP support site, or from the IBM Netezza
Client CD. The installation program installs the Netezza tools and ODBC libraries
on your system, and creates a NetezzaSQL system data source entry (NZSQL) with
appropriate default values.
After the ODBC driver is installed, the next step is to configure the environment
variables to enable the ODBC driver to locate the correct configuration files. Then,
you configure the data sources.
Related concepts:
ODBC driver configuration for UNIX/Linux

The driver manager and the IBM Netezza ODBC drivers use a configuration file
named .odbcinst.ini to get information about ODBC drivers. During the Netezza
ODBC driver configuration process, you supply configuration information for the
Netezza ODBC driver by modifying entries in the .odbcinst.ini file.
The period precedes the file name only when the file is in the home directory of
the user as a hidden file.
The following example shows the contents of a 32-bit driver configuration file
named odbcinst.ini.sample. This file is in the nz/lib directory (ordinarily
/usr/local/nz/lib) after you installed the Netezza driver. Use the contents of the
sample file to configure your own .odbcinst.ini file.
[ODBC Drivers]
NetezzaSQL = Installed
[NetezzaSQL]
Driver = /usr/local/nz/lib/libnzsqlodbc3.so
Setup = /usr/local/nz/lib/libnzsqlodbc3.so

APILevel = 1
ConnectFunctions = YYN
Description = Netezza ODBC driver
DriverODBCVer = 03.51
DebugLogging = false
LogPath = /tmp
UnicodeTranslationOption = utf8
CharacterTranslationOption = all
PreFetch = 256
Socket = 16384
The Netezza ODBC driver properties are explained in Table 4-1 on page 4-1. Use
this table to select appropriate values for the configuration entries in your
.odbcinst.ini file. The Character Translation Option can be set to “all’ or “latin9.”
Related concepts:
Appendix A, “ODBC configuration files,” on page A-1
ODBC driver configuration steps for UNIX/Linux

The following steps are the steps to configure an IBM Netezza ODBC driver on a
UNIX/Linux client system:
1. Log in using your own user ID and password.
2. Modify environment variables.
3. Create the ODBC driver configuration file.
4. Optional: Modify the ODBC driver configuration file.
Configuring the ODBC driver for UNIX/Linux

If you previously installed the IBM Netezza client software while logged in as the
superuser, you can now log out and log back in using your own user ID and
password. You can use your own user ID and password when you configure your
ODBC driver and Netezza appliance data sources. Configuring the ODBC driver
and Netezza appliance data sources while logged in as an ordinary user allows
each user of the system to supply different configuration information to access
different Netezza appliance data sources.
1. Modify the environment variables to include the appropriate installation
directories. The following commands are examples:
For AIX:
export PATH=$PATH:/usr/local/nz/bin
export LIBPATH=$LIBPATH:/usr/local/nz/lib
For HP-UX:
export SHLIB_PATH=$SHLIB_PATH:/opt/datanz/nz/bin
For Linux, Solaris:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/nz/lib
The previous commands change the environment for the current session only.
After you verify that your environment modifications work correctly, edit your
login script to set the environment variables when users log in.
2. Configure Netezza ODBC drivers by using a text editor to modify the contents
of the .odbcinst.ini configuration file. You normally place the .odbcinst.ini
file in your home directory while logged in as an ordinary user.
You might want to place the .odbcinst.ini file in a different location, and you
might want to do the configuration as the superuser, rather than as an ordinary
user.
This step assumes that you are logged in as an ordinary user and are placing
the .odbcinst.ini file in your home directory. What you do in this step
depends on whether the .odbcinst.ini file exists in your home directory.
v The configuration file exists.
Use a text editor, such as vi, to examine the .odbcinst.ini configuration file
if it exists in your home directory, which can occur for different reasons,
including the following reasons:
– Your client system was previously configured for one or more ODBC
drivers other than the Netezza ODBC driver. If you still want to use those
ODBC drivers, do not modify existing entries in the .odbcinst.ini file. In
this case, add the entry in the odbcinst.ini.sample file to the end of the
existing contents of the .odbcinst.ini file.
– The Netezza client software and a Netezza ODBC driver were previously
installed on your client system, and the Netezza ODBC driver is
configured. In this case, you might not need to add any entries to the
.odbcinst.ini file. If your .odbcinst.ini file already contains an entry
similar to that found in the odbcinst.ini.sample file, no changes are
required. If it does not, then add the entry in the odbcinst.ini.sample file
to the end of the existing contents of the .odbcinst.ini file.
v The configuration file does not exist.
If the .odbcinst.ini configuration file does not yet exist in your home
directory, copy the entire odbcinst.ini.sample file into your home directory
and rename it .odbcinst.ini.
The entry from the odbcinst.ini.sample file can usually be used without
modifying your .odbcinst.ini file. Consult your Netezza system administrator to
see whether any configuration entries must be changed for your installation.
Related concepts:
ODBC data source configuration for UNIX/Linux

The driver manager and the IBM Netezza ODBC drivers use the .odbc.ini
configuration file to get information about data sources. To configure data sources
on a UNIX/Linux system, use a text editor to modify the .odbc.ini file.
Data source configuration file

This section describes the .odbc.ini file and shows samples of its contents. You
normally place the .odbc.ini file in your own home directory. It specifies details
about the IBM Netezza appliance data sources you want to access.
The period precedes the file name only when the file is in the home directory of
the user.
To configure the .odbc.ini file entries to access the system data source on your
own Netezza appliance, get the following configuration information from your
Netezza system administrator, and substitute it for the information in .odbc.ini:
Database
The name of the system database on the Netezza appliance.
SchemaName
User name
A valid user ID for accessing the system data source.
Server name
The server host name or IP address of your Netezza appliance.
Password
A valid password for accessing the system data source.
The following example shows the contents of a file named odbc.ini.sample, which
is in the nz/lib directory after you install your ODBC drivers. The sample file
describes a system data source found on every Netezza appliance, and includes
comments that explain each parameter. Use the contents of this sample file, along
with the administrator information you substituted, to configure your own
.odbc.ini file.
Because there can be differences between some source and target data types, add
the following code to your .odbc.ini file to prevent issues:
UnicodeTranslationOption=utf8
;
; odbc.ini
;
[ODBC Data Sources]
NZSQL = NetezzaSQL
[NZSQL]
;Path of a driver used for database connection
Driver = /usr/local/nz/lib/libnzodbc.so
;A decription used to identify the database connection properties.

Description = NetezzaSQL ODBC
;The name of a machine or IP address where the database is located.

Servername = 127.0.0.1
;The port number to connect.

Port = 5480
;The name of a database.

Database = dev
;The schema in the database. If unspecified, driver connects to

:default schema for the database.
SchemaName = sample_schema
;The name of a valid user.

Username = guest
;The password for the user.

Password = password
;Only Select SQL statements will be allowed if this field is checked.

ReadOnly = false
;When this option is enabled and the application bindtype is same as

;backend datatype the query performance will be faster. Query
;performance gain will be achieved only for single select statements
;(not for batch queries).It also works in case when application bind
;type is different than backend datatype but there are some
;restrictions on it.
FastSelect = false
;When set to true, system tables will be included in the available
table list.
ShowSystemTables = false
;When set to true, use old (2.5) functionality for returning schemas in
SQLTables.
LegacySQLTables = false
;Specifies login timeout in seconds.

LoginTimeout = 0
;Specifies query timeout in seconds.

QueryTimeout = 0
;Specifies date format as follows -

; 1: YMD
; 2: MDY
; 3: DMY
DateFormat = 1
;When selected, driver treats SQL_C_NUMERIC buffers as SQL_C_CHAR

buffers.
NumericAsChar = false
;Return SQL_BIT as "1"/"0" when char.

SQLBitOneZero = false
;When enabled, replaces all occurences of CRLF, CR and LF with a single

space.
StripCRLF = false
;Specifies level of security on the system

securityLevel = preferredUnSecured
;Name of the Root CA certificate.

caCertFile =
;Specifies maximum errors allowed. 0 value means no limit on

loadMaxErrors value.
;loadMaxErrors = 1
;If value is true, it rounds the data of numeric columns whose

precision exceeds the precision defined.
;loadRoundFraction = 0
[ODBC]
IANAAppCodePage=4
InstallDir=/opt/odbc32v51
Trace=0
TraceDll=/opt/odbc32v51/lib/odbctrac.so
TraceFile=odbctrace.out
UseCursorLib=0
The data source properties are explained in “ODBC Driver Setup window” on
page 5-3. Use this information to select appropriate values for the entries in your
.odbc.ini file.
Data source configuration steps for UNIX/Linux

Follow these steps to configure IBM Netezza appliance data sources on a
UNIX/Linux client system:
1. Create the data source configuration file.
2. Configure the data source.

Configuring the data source for UNIX/Linux
1. Configure IBM Netezza appliance data sources by modifying the .odbc.ini
configuration file. As with the .obdcinst.ini file, you normally place the
.odbc.ini configuration file in your home directory while logged in as an
ordinary user.
In some cases, you might want to place the .odbc.ini file in another location,
and you might want to do the configuration as the superuser rather than as an
ordinary user.
This step assumes that you are logged in as an ordinary user and are placing
the .odbc.ini file in your home directory. What you do in this step depends on
whether the .odbc.ini file exists in your home directory.
v The configuration file exists.
If the .odbc.ini configuration file exists in your home directory, use a text
editor to examine the contents of the .odbc.ini file to see whether it already
contains entries for the Netezza appliance data sources to access. If it does
not, copy the contents of the odbc.ini.sample file to the end of your existing
.odbc.ini file. Do not modify any existing entries in the file.
v The configuration file does not exist.
If the .odbc.ini configuration file does not yet exist in your home directory,
copy the entire odbc.ini.sample file into your home directory and rename it
.odbc.ini.
2. After you initially set up the .odbc.ini configuration file, use a text editor to
modify entries in the file to describe the Netezza appliance data sources to
access, as described in “Data source configuration file” on page 5-9. To access
additional Netezza appliance data sources, supply a set of configuration entries,
similar to that found in the odbc.ini.sample file, for each data source to access.
Related concepts:
ODBC connectivity validation for UNIX/Linux

To validate that you can use ODBC to connect to an IBM Netezza appliance data
source, use the interactive SQL query program called isql. The isql program is
installed on your system when you install the unixODBC driver manager. You can
use isql to run SQL queries against both the system data source and any user data
sources you configure.
If you are using a driver manager other than the unixODBC driver manager,
consult your Netezza system administrator to see if there is an SQL query program
installed on your client system that you can use instead of isql to validate ODBC
connectivity and query Netezza appliance data sources.
The following example uses the DataDirect driver manager, where you run the
example program in the example directory, specifying the NZSQL DSN, login, and
password, displaying output as in the following:
./example
DataDirect Technologies, Inc. ODBC Example Application.
Enter the data source name : NZSQL
Enter the user name : admin
Enter the password : password
Enter SQL statements (Press ENTER to QUIT)
SQL>
When you are connected, you can run the same queries as used in the following
examples. The system returns the same results.
ODBC connectivity validation steps for UNIX/Linux
Follow these steps to validate ODBC connectivity to the IBM Netezza appliance
data sources configured in the previous section.
1. Change directories.
2. Connect to NZSQL system data source.
3. Query system database.
4. Display query results.
5. Connect to Test User data source.
6. Query user database.
7. Display query results.
Validating the ODBC connectivity for UNIX/Linux

1. Change to the directory that contains the isql interactive SQL application by
entering the following command: cd /usr/local/unixODBC/bin
2. Start the isql interactive SQL application, and connect to the NZSQL system
data source by entering the following command: isql -v NZSQL
If your connection is successful, you see a response similar to the following:
+---------------------------------------+
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
+---------------------------------------+
3. Enter the following command to query the _t_dslice table: select * from
_t_dslice The system database in the NZSQL data source contains a table
named _t_dslice.
If your ODBC driver is correctly installed, and your system data source is
correctly configured, the isql program displays the contents of the _t_dslice
table from the system database in the NZSQL data source. You see a response
similar to the following:
+------------+------------+------------+------------+
| ds_id | ds_pridskid| ds_priptid | ds_mirdskid|
+------------+------------+------------+------------+
| 1 | 1002 | 0 | |
+------------+------------+------------+------------+
4. Enter the quit command to end the connection to the NZSQL system data
source and exit the isql program. Then restart isql and connect to the
Test_User user data source by entering the following command: isql -v
Test_User
If your connection is successful, you will again see a response similar to the
following:
+---------------------------------------+
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
+---------------------------------------+
5. Enter the following command to query the a_inventory table: select * from
a_inventory The example assumes the system database in the Test_User data
source contains a table named a_inventory.

If the ODBC driver is correctly installed, and the user data source is correctly
configured, the isql program displays the contents of the a_inventory table
from the system database in the Test_User data source:
+------------+----------+------------+
| part_no | part_name| on_hand |
+------------+----------+------------+
| 181 | Wheel | 449 |
| 124 | Bolt | 900 |
| 105 | Gear | 0 |
| 134 | Nut | 743 |
+------------+----------+------------+
Kerberos authentication details for ODBC clients

If your environment uses Kerberos to authenticate user access to the IBM Netezza
databases, the ODBC client application is responsible for obtaining authorization
tickets.
The ODBC client application must obtain the Kerberos authorization ticket from
the Kerberos Authentication Server using the kinit facility before connecting to the
Netezza databases. The Netezza ODBC driver detects that the Netezza appliance
uses Kerberos authentication and can transparently pass the authenticated user
credentials to the database.
When configuring the ODBC connection to the Netezza data sources, you can
leave the password and authentication arguments null/empty. These passwords
are ignored if specified in the SQLConnect or SQLDriverConnect API calls.
For more information about configuring the Netezza appliance to use Kerberos
authentication, refer to the security section in the IBM Netezza System
Administrator’s Guide.
Chapter 6. Installing and configuring JDBC
This section describes the procedures to install and configure JDBC. You can have
only one JDBC driver installed on your system at a time. If you need a different
driver, you must remove the installed driver before you install the correct one.
After installation, when you run an application that tries to use JDBC, you are
prompted for a value called Class Name. For the IBM Netezza Driver, enter
org.netezza.Driver.
Related concepts:
Installing the JDBC driver for Windows with the GUI

This section describes the procedure for installing IBM Netezza JDBC components
on a Windows system. Complete the following steps to install the JDBC driver.
1. Start the installation program by double-clicking the nzjdbcsetup.exe file in the
/drivers directory of the Windows installation kit.
2. When the language option window opens, accept the default of English and
click OK. The language option window controls the language for the
installation program.
3. Review the information in the Introduction window and click Next.
4. If you want to change the installation folder from the IBM Netezza default,
change the folder in the Choose Install Folder window and click Next when
you are done.
5. When the Pre-Installation Summary window opens, page through the previous
selections to review selections by using Previous. When you are finished, click
Install. The Pre-Installation Summary window summarizes your installation
choices.
6. When the Installation Completed window opens, click Done to exit. The
Installation Completed window indicates that the Netezza JDBC driver
installation process completed successfully.
Installing JDBC for UNIX/Linux

Before you can configure an IBM Netezza JDBC driver on your system, you must
first install the Netezza client tools software, which includes the JDBC driver.
Related concepts:
JDBC driver installation for UNIX/Linux on a supported

platform
The IBM Netezza appliance client tools installation procedure copies the Java jar
file that contains the JDBC driver into the nz/lib directory (usually
/usr/local/nz/lib). This file is named nzjdbc3.jar. To configure JDBC on a Linux
client system, run an export command to include an appropriate entry in your
CLASSPATH environment variable.
For help on options, run the following command: -java -jar nzjdbc3.jar -help

Before you use JDBC, verify that your system has Java installed (JRE Release 1.5 or
later, or JRE 1.7 or later if your Netezza host runs release 7.1.0.0 or later and uses
SP 800-131a cryptography). For more information, go to http://www.java.com
where you can test your system for Java software support and download the latest
version for your system.
Run the following command to modify your CLASSPATH environment variable to

include the location of the Netezza JDBC Version 3.0 driver:
export CLASSPATH=.:/usr/local/nz/lib/nzjdbc3.jar
The previous export commands changes the environment for the current session
only. After you verify that your environment modification works correctly, you can
edit your login script to set the environment variable when users log in.
Installing JDBC driver for UNIX/Linux on an unsupported

platform
This section describes how to install an IBM Netezza JDBC driver on Linux/UNIX
systems that is not one of the supported Linux/UNIX platforms as documented in
Chapter 2, “Support and release compatibility,” on page 2-1
1. Change to the appropriate directory on your IBM Netezza appliance host: cd
/nz/kit/sbin
2. Use the rcp or ftp command (by using binary transfer mode) to copy the JDBC
driver to your client machine. The following is a command example:
rcp nzjdbc3.jar client machine
3. Modify the CLASSPATH environment variable on the client machine to include
the path of the directory in which you placed the JDBC driver.
Configuring the JDBC data source on Windows

This section describes the procedure for configuring a JDBC data source on a
Windows system. You can save a data source name (DSN) on the local server
through the use of the nzjdbc.ini file, which is in the same directory as the driver
itself, and which controls the JDBC graphical user interface (GUI).
1. Start the GUI by running the following command: java -jar <driver JAR>
2. When the list of data sources is displayed, select Add to add a data source.
3. When the Datasource Configuration window opens, select the Connection
Options tab and enter the information in the appropriate fields:
Data source1
Name of the data source.
Host1 Name of the host to connect to.
Port1 Port number
Database1
Database (catalog) name
Description
Description for the data source.
User User name to connect to the database.
Password
Password for authentication.
Schema
Test Connection
Tests the connection with the set parameters.
1
These fields are required.
4. Select the Advanced Options tab and enter the information in the appropriate
fields:
Batch Size
Number of rows to be fetched in a cycle. The default is 256.
Login timeout
Maximum wait time to make a connection. The default is infinite.
Read Only
Read Only property for the connection. The default is false.
Auto Commit
Auto Commit property for the connection. The default is true.
Ignore UpdateCount
Allows the JDBC driver to export more than two billion rows (the
maximum int value). The default is OFF.
Log Level
Log Level for the connection. The default is OFF.
Logger Type
The type to be used for logging. The default is TEXT.
Logger Directory
Log directory where the log files are dumped.
Database Metadata
When selected, you can get metadata information that is not restricted
to the current catalog/schema. Not selecting this option means that
your information is restricted to the current catalog/schema. The
default is not selected.
Defaults
Selects the defaults for these options.
5. Select the SSL Options tab and enter the security level information as
appropriate:
Preferred Unsecured
Connections that do not use SSL are preferred, but a connection is not
refused solely because it uses SSL encryption.
Only Unsecured
Only connections that do not use SSL to encrypt data are accepted. This
security level provides increased performance but carries the risks that
come with an unencrypted connection.
Preferred Secured
Connections that use SSL are preferred, but a connection is not refused
solely because it does not use SSL encryption.
Only Secured
Only connections that use SSL to encrypt data are accepted. This
Chapter 6. Installing and configuring JDBC 6-3

security level provides increased security but reduces performance
somewhat, due to the necessity of encrypting the DataStream.
Certificate File
Enter the name of the certificate authority (CA) file used to authenticate
connections. If a CA is being used for authentication, the name of the
CA file must match the name defined by the system administrator for
the database to which you are attempting to connect. For more
information about security and authentication, see the IBM Netezza
System Administrator’s Guide.
6. When finished entering Data Source Configuration options, test the connection
by selecting Test Connection on the Connection Options tab.
7. When the connection is established, select OK on the confirmation screen.
8. When all your options are entered and your connection is tested, select OK on
the Datasource Configuration window.
9. Select Exit when finished.
Configuring JDBC for UNIX/Linux

This section describes the procedure for configuring JDBC on a UNIX/Linux
system.
1. Run the following command: java -jar nzjdbc3.jar
2. Enter data source information and parameter values for configuration, as
described in “Configuring the JDBC data source on Windows” on page 6-2.
Alternatively, you can use the console option -c to be prompted for each
parameter.
After all parameters are entered and saved, the nzjdbc.ini file is created. Make
sure that this file is in the CLASSPATH. For a test application, you can use the
DSN defined in the INI file.
3. To test the connection, run the following jar file with the -t option: java -jar
nzjdbc3.jar -t. This connection is tested without WebSphere®.
You can enter additional values in the test, such as the following values. Include
the -schema value if you are testing a connection to a database that has multiple
schemas.
java -jar nzjdbc3.jar -t -host yourhostname -u username
-pw password -db database -schema schemaname
Kerberos authentication details for JDBC clients

databases, review this information to configure the JDBC client to manage
authorization tickets.
The JDBC driver is responsible for obtaining the Kerberos tickets to authenticate
user access to the Netezza database. This is different from ODBC and OLE DB
environments where the client application is responsible for obtaining the tickets.
In a JDBC environment, your JDBC client must meet the following minimum
requirements:
v Your client system must have Java 1.6 or later installed.
v The login module class name in the login.conf file must be changed based to
the Java provider that you use.
– For IBM Java: com.ibm.security.auth.module.Krb5LoginModule
– For Oracle Java: com.sun.security.auth.module.Krb5LoginModule
v Set the system property java.security.auth.login.config to the login.conf file
path through the application or edit the <JAVA_HOME>/jre/lib/security/
java.security file to add the following line:
login.config.url.1=file:<LOGIN_CONF_FILE_PATH>
v Specify the value for the krbLoginModule name in the datasource connection
parameter as the name of the loginModule from the login.conf file. You must
provide this value because the login method of loginContext reads this
loginModule information out of the login.conf file, and uses the class mentioned
in it to authenticate further.
A sample login.conf file follows. In this example, the krbLoginModule name
would be loginModuleName.
loginModuleName {
com.sun.security.auth.module.Krb5LoginModule required
debug = true storeKey = false;
};
The default login module name is EntryModuleName.

v Set the system property java.security.krb5.conf to the Kerberos configuration
file name, or copy the configuration file to the following default location on the
client system. See the following link for more information: http://
pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=
%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fae
%2Frsec_SPNEGO_config_krb5.html.
Note: On UNIX systems, the configuration file name is krb5.conf and on

Windows, the file name is krb5.ini. The following list shows the default
locations for the Kerberos configuration file on various platforms.
– For IBM AIX: /etc/krb/krb5.conf
– For HP Itanium: /etc/krb5.conf
– For Linux: /etc/krb5.conf
– For Linux on IBM System z: /etc/krb5.conf
– For Linux on PowerPC: /etc/krb5.conf
– For Oracle Solaris: /etc/krb/krb5.conf
– For Windows: C:\winnt\krb5.ini or C:\windows\krb5.ini
v If you use the IBM Java runtime environment and you have several Netezza
appliances that reside in different domains, your JDBC client connection to some
of the systems could fail with the following error:
major string: General failure, unspecified at GSSAPI level
minor string: Error: java.lang.Exception: Error: java.lang.Exception: No credential
If this occurs, update your client Kerberos configuration file to include a
[domain_realm] definition that identifies all the domains that you need to access
and the Kerberos realm that controls the authentication requests. For example, if
you have Netezza systems configured within the domains east.company.com and
west.company.com, and the Kerberos realm is MYKRB5.COMPANY.COM, add
the following [domain_realm] to the Kerberos configuration file:
[domain_realm]
.company.com = MYKRB5.COMPANY.COM
company.com = MYKRB5.COMPANY.COM
Note: You can specify an entry for both east.company.com and

west.company.com, but because there is a common part of the domain name
Chapter 6. Installing and configuring JDBC 6-5

(company.com), you can specify the common domain. If the domain names are
more unique such as east.com and west.com, specify each unique domain for the
locations where your Netezza systems are present.
JDBC setup considerations for IBM Cognos SSO environments

If you use your IBM Netezza JDBC driver to support connections to an IBM
Cognos® environment that uses Kerberos single-sign-on (SSO) support, review this
topic for important configuration steps.
When an IBM Cognos Business Intelligence application is configured in Kerberos

SSO mode, Cognos performs the user authentication steps that the JDBC driver
would normally perform. It then passes an authentication ticket to the JDBC driver
in the connection request. In this environment, you must configure the JDBC driver
to bypass its normal authentication and use the authentication ticket.
You use the JDBC krbSSODelegation connection parameter and set it to true to
configure the JDBC driver to accept the authentication ticket. The default value is
false, which configures the driver to use the standard username and password
authentication (non-SSO) support.
The krbSSODelegation parameter is valid only for the following environments:

v The Cognos application is configured to use SSO support as described in the
Cognos documentation, and the Netezza system is configured to use Kerberos
authentication as described in the IBM Netezza System Administrator’s Guide.
v The Cognos application contacts the JDBC driver using the
Subject.doAs(subject, connectTask) method call.
Note: The REALM_NAME in krb5.conf file defined at the Cognos application

environment cannot have an at sign (@) character in the name.
If the krbSSODelegation parameter is true, but the JDBC driver did not obtain the
user credentials from the Cognos application, the JDBC driver returns an error
because it cannot validate the username for the connection.
Chapter 7. Installing and configuring the OLE DB provider
This section describes the procedure for installing the IBM Netezza OLE DB
provider on a Windows client system, configuring the provider and data sources,
and testing for connectivity to Netezza appliance data sources.
OLE DB provider silent installation options

The OLE DB provider offers silent installation options for both 32-bit and 64-bit
installation executable files. The installation options you have are:
v For 32-bit installations:
– C:\nzoledbsetup.exe (full GUI installation)
– C:\nzoledbsetup.exe -i silent (silent installation, VS2010 Libraries not
installed)
– C:\nzoledbsetup.exe -i silent -DVC8_LIB_INSTALL=1 (silent installation,
VS2010 Libraries installed)
v For 64-bit installations:
– C:\nzoledbsetup64.exe (full GUI installation)
– C:\nzoledbsetup64.exe -i silent (silent installation, VS2010 Libraries not
installed)
– C:\nzoledbsetup64.exe -i silent -DVC8_LIBS_INSTALL=1 (silent installation,
VS2010 Libraries installed)
Installing the OLE DB provider

Follow these steps to install the OLE DB provider. This example is for a Windows
7 system, but the procedure is similar for other Windows systems.
1. Start the installation program by double-clicking the nzoledbsetup.exe file. The
file is in the /drivers directory of the Windows installation package.
2. When the language options window opens, accept the default of English and
click OK. The language options window controls the language for the
installation program.
3. When the Introduction window opens, review the information and click Next.
4. Install the Visual Studio C++ 2010 (VS2010) Libraries on the client system.
5. When the Pre-Installation Summary window opens, review the installation
summary. You can use Previous to page through the previous windows to
review and change selections. Click Install to complete the installation process.
The Pre-Installation Summary window summarizes your installation choices.
After you click Install, the installation program does the following tasks:
v Installs the IBM Netezza OLE DB provider. A 32-bit provider on a 32-bit
system and a 64-bit provider on a 64-bit system are installed in the
\WINDOWS\system32 folder. On a 64-bit system, both providers are installed,
and the 32-bit provider is installed in the \WINDOWS\SysWOW64 folder.
v Places entries in the Windows registry to add the Netezza OLE DB provider
to the provider list.
6. When the Install Complete window opens, click Done to close the installation
program. The Install Complete window indicates that the installation process
completed successfully.

Before you try to access an OLE DB data source, you must configure it. The next
section describes the configuration procedure.
Validating the OLE DB data source configuration

1. Using a text editor, create an empty text file and save it to the desktop as
test.udl.
2. Double-click the desktop icon for the test.udl file that you created.
3. In the list of OLE DB providers, select IBM Netezza OLE DB Data Provider
(created during the OLE DB provider installation procedure) and click Next.
4. On the Connection tab, in the Data Source field, specify the name of the
system where the database is located.
5. Specify appropriate values for the database user name and password.
6. From the list, choose the name of the database (catalog) to which you want to
connect.
7. Optionally, if your database has multiple schemas, click the Advanced tab and
type the name of the schema within the database to which you want to
connect.
8. Click Test Connection in the lower right corner of the Connection tab.
9. Click OK to authenticate the user and establish the connection. If the
connection is successful, a confirmation window opens.
If the connection fails, verify that the SSL security parameters agree with those
parameters defined by the system administrator for the system to which you
are attempting to connect.
Kerberos authentication details for OLE DB clients

databases, the OLE-DB client application is responsible for obtaining authorization
tickets.
The OLE DB client application must obtain the Kerberos authorization ticket from
the Kerberos Authentication Server using the kinit facility before connecting to the
Netezza databases. The Netezza OLE DB provider detects that the Netezza
appliance uses Kerberos authentication and can transparently pass the
authenticated user credentials to the database.
When establishing the OLE DB connection to the Netezza data sources, you can
specify a password in the UDL file or in the Vbscript, but it will be ignored. If you
do not specify a password, the connections could return an error because of the
null password.
v For a UDL file, select the Blank Password option on the Connection tab of the
UDL file. If you do not select this option, the connection request fails with the
error Test connection failed because of an error in initializing provider.
Required properties not set (Server, user, password, ....etc.).
v For a Vbscript, set PASSWORD=NULL to avoid connection errors when the
password in the connection string is null. If you do not specify this setting, the
connection request fails with the error Required value is not set (Server,
user, password, ...etc.)
Appendix A. ODBC configuration files
This section introduces advanced considerations for configuring ODBC drivers and
data sources on Linux/UNIX client systems using the .odbcinst.ini and
.odbc.ini configuration files.
Related concepts:
“ODBC driver configuration for UNIX/Linux” on page 5-7
Related tasks:
“Configuring the ODBC driver for UNIX/Linux” on page 5-8
“Configuring the data source for UNIX/Linux” on page 5-12
Netezza ODBC configuration file names and locations

You can configure the .odbcinst.ini and .odbc.ini ODBC configuration files as
hidden files or as non-hidden files.
The ODBC configuration examples for Linux/UNIX systems in Chapter 5,

“Installing and configuring ODBC,” on page 5-1 configure the two ODBC
configuration files as hidden files by preceding their names with an initial period.
You can alternatively configure them as non-hidden files by omitting the initial
period.
Hidden files
When you place the two ODBC configuration files in the home directory of
the user, the IBM Netezza ODBC driver expects the files to have the
hidden file names .odbcinst.ini and .odbc.ini.
Non-hidden files
When you place the two ODBC configuration files in a directory other than
the home directory of the user, the Netezza ODBC driver expects the files
to have the non-hidden file names odbcinst.ini and odbc.ini.
ODBC driver search behavior

The default behavior of the IBM Netezza ODBC driver is to search the following
places, in sequence, to locate the two ODBC configuration files:
1. If there is an NZ_ODBC_INI_PATH entry in the environment that describes a
directory path, the driver looks first in that directory for two non-hidden
configuration files.
2. The driver then looks in the current home directory of the user for the two
hidden files .odbcinst.ini and .odbc.ini. If the two configuration files exist as
non-hidden files in the home directory of the user, the driver ignores them.
3. If the driver does not find hidden configuration files in the current home
directory of the user, it next looks in the /usr/local/etc directory for the two
non-hidden files odbcinst.ini and odbc.ini. If the two configuration files exist
as hidden files in the /usr/local/etc directory, the driver ignores them.
ODBC driver considerations

Placing hidden configuration files in the home directory of the user is useful if
each user of the Linux/UNIX system has a separate set of configuration files,
possibly describing different IBM Netezza appliance data sources. Each home
© Copyright IBM Corp. 2007, 2015 A-1

directory of a user has a pair of hidden configuration files that describe the
Netezza appliance data sources that user can access.
Placing non-hidden configuration files in either the first or third location is useful
if you want all users of the client system to have access to the same set of Netezza
appliance data sources, without requiring a separate set of configuration files in
each home directory of a user. The /usr/local/etc directory or the
NZ_ODBC_INI_PATH directory contains a single set of non-hidden configuration files
that describes the Netezza appliance data sources that all users of the client system
can access.
You can decide where to place the ODBC configuration files based on how you are
using the client system.
The way a Netezza ODBC driver looks for ODBC configuration files is
straightforward and unambiguous. However, the driver manager installed on the
client system also uses the two ODBC configuration files. The way a Netezza
ODBC driver looks for ODBC configuration files can sometime conflict with the
way the driver manager looks for them. This can sometimes cause configuration
problems.
The unixODBC driver manager

This section describes how the unixODBC driver manager searches for the ODBC
configuration files and how the unixODBC driver manager interacts with the IBM
Netezza ODBC drivers.
The unixODBC driver manager search behavior

The default behavior of the unixODBC driver manager is to search the following
places, in sequence, to locate the two ODBC configuration files:
1. The driver manager looks first in the home directory of the current user for the
two hidden files .odbcinst.ini and .odbc.ini. If the two configuration files
exist as non-hidden files in the home directory of the user, the driver manager
ignores them.
2. If the driver manager does not find hidden configuration files in the home
directory of the user, it looks next in the /usr/local/etc directory for the two
non-hidden files odbcinst.ini and odbc.ini. If the two configuration files exist
as hidden files in the /usr/local/etc directory, the driver manager ignores
them.
Compatibility
The methods the IBM Netezza ODBC driver and the unixODBC driver manager
use to locate the configuration files are compatible. It is relatively easy to ensure
that the Netezza ODBC driver and the unixODBC driver manager find the two
ODBC configuration files in the same place. Their uses of hidden and non-hidden
files are also compatible.
Place hidden configuration files in the home directory of each user if each user
needs to access different Netezza appliance data sources. Place non-hidden
configuration files in the /usr/local/etc directory if all users access the same
Netezza appliance data sources.
With the unixODBC driver manager, you do not need to use the NZ_ODBC_INI_PATH
environment variable.
A-2 IBM Netezza ODBC, JDBC, and OLE DB Installation and Configuration Guide
DataDirect driver manager
This section describes how the DataDirect driver manager searches for the ODBC
configuration files and how the DataDirect driver manager interacts with the IBM
Netezza ODBC drivers.
DataDirect driver manager search behavior

The default behavior of the DataDirect driver manager is to search the following
two places, in sequence, to locate the two ODBC configuration files:
1. The driver manager looks first in the home directory of current use for the two
non-hidden files odbcinst.ini and odbc.ini. If the two files exist as hidden
files in the home directory of the user, the driver manager ignores them.
2. If the driver manager does not find non-hidden configuration files in the home
directory of the user, it looks next in the /etc directory for the two non-hidden
files odbcinst.ini and odbc.ini. If the two configuration files exist as hidden
files in the /etc directory, the driver manager ignores them.
Incompatibilities
The following are incompatibilities between the IBM Netezza ODBC drivers and
the DataDirect driver manager:
1. The DataDirect driver manager looks first in the home directory of the current
user for non-hidden configuration files instead of hidden ones.
2. The DataDirect driver manager looks next in the /etc directory instead of in
the /usr/local/etc directory.
3. The DataDirect driver manager also looks at the value of the environment
variable ODBCINI to determine the location of the odbc.ini file to use.
To work around the ODBC configuration file search incompatibilities of the
DataDirect driver manager, use one of the following methods:
v Separate configuration files in each home directory
Use this method if you would like each user of the Linux/UNIX client
system to use a separate set of ODBC configuration files. Netezza ODBC
drivers look for hidden configuration files, and the DataDirect driver
manager looks for non-hidden files. To overcome this incompatibility, create
two soft links in the home directory of each user so that the DataDirect
driver manager finds non-hidden files in the home directory and the Netezza
ODBC driver finds hidden files:
– A soft link so odbcinst.ini points to .odbcinst.ini
– A soft link so odbc.ini points to .odbc.ini
v Shared configuration files
Use this method if you would like all users of the Linux/UNIX client system
to use the same set of ODBC configuration files. Configure the
NZ_ODBC_INI_PATH environment variable so it specifies the /etc directory, and
place the two non-hidden configuration files odbcinst.ini and odbc.ini in
the /etc directory. The DataDirect driver manager and the Netezza ODBC
driver then both find the configuration files in the /etc directory.
v Two environment variables
Use this method if you would like both the Netezza ODBC driver and
DataDirect driver manager to find the configuration files no matter where
they are in the file system. Use both NZ_ODBC_INI_PATH and ODBCINI together
to point to the odbc.ini and odbcinst.ini files anywhere on the file system.
Appendix A. ODBC configuration files A-3

Investigate the client system configuration
You might need to change the configuration of a UNIX/Linux client system to
access new IBM Netezza appliance data sources after the system is configured to
access other types of ODBC data sources. Such a system might already have a
driver manager installed and ODBC configuration files in some directory in the file
system. In such a situation, it is helpful to discover as much about the present
configuration as you can before deciding how to configure the Netezza ODBC
drivers and Netezza appliance data sources.
One technique is to use the env and grep commands to determine whether one or
more environment variables exist which point to ODBC configuration directories.
You might find the following command useful: env | grep -i ODBC.
The command shows you if there are any entries in the environment that contain
the characters ODBC. For example:
ODBC_HOME=/opt/odbc
or
ODBCINI=/opt/odbc/odbc.ini
These results can help you to determine how the client system is configured. You
can then look in the referenced directories for ODBC configuration files, and then
configure the Netezza ODBC driver to look in those same directories for the ODBC
configuration files.
A-4 IBM Netezza ODBC, JDBC, and OLE DB Installation and Configuration Guide
Appendix B. Troubleshooting
This section introduces methods for tracking system activity, which can help in
detecting problems and troubleshooting issues. A debug log provides you with a
record of system activity, so you can take steps to correct problems.
Related concepts:
“ODBC driver properties” on page 4-1
Related reference:
“ODBC Driver Setup window” on page 5-3
ODBC debug logging and driver manager tracing

This section contains information about the procedures for enabling debug logging
and driver manager tracing, two methods of tracking system activity. Use debug
logging, which provides the necessary information and is a supported driver
logging function. Tracing is an external, non-IBM Netezza driver manager option
that keeps a log of function calls between the driver manager and the driver, and
between the driver manager and the application. Both debugging and tracing are
disabled by default. Enable debugging and tracing only for troubleshooting
because they can degrade the client application performance.
ODBC debug logging

By default, debug logging is disabled because enabling debug logging can affect
performance.
Enabling ODBC logging in Windows

Use the following steps to enable ODBC logging in Windows.
1. Open the ODBC Data Source Administrator window by selecting Start >
Settings > Administrative Tools > Data Sources (ODBC).
2. In the ODBC Data Source Administrator window, select the System DSN tab.
3. Select the NZSQL system data source and click Configure.
4. Select the Driver Options tab.
5. Select Enable Debug Logging.
6. Specify the log file path, where the ODBC is saved. The log file name is
nzodbc_userpid.log.
7. Click OK to save your settings.
Enabling ODBC logging in UNIX/Linux

Use the following steps to enable ODBC logging in UNIX/Linux:
1. Open the .odbcinst.ini file.
2. In the NetezzaSQL section, set DebugLogging = true.
3. Save and close the file. The ODBC log is saved in the LogPath value, and the
log file name is nzodbc_userpid.log.
ODBC driver manager tracing

By default, driver manager tracing is disabled. Remember to disable tracing after
troubleshooting because tracing can degrade performance.
© Copyright IBM Corp. 2007, 2015 B-1

Enabling ODBC driver manager tracing in Windows
Use the following steps to enable ODBC driver manager tracing in Windows.
1. Open the ODBC Data Source Administrator window by selecting Start >
Settings > Administrative Tools > Data Sources (ODBC)
2. In the ODBC Data Source Administrator window, select the Tracing tab.
3. Specify the log file path and file name where the tracing log is saved.
4. Click Start Tracing Now and click OK.
Enabling ODBC driver manager tracing for UNIX/Linux

Use the following steps to enable ODBC driver manager tracing in UNIX/Linux.
1. Open the .odbc.ini file.
2. Make the following changes in the [ODBC] section:
Trace = 1
TraceAutoStop = 0
TraceFile = /tmp/odbctrace.out
3. Save and close the file. The log file is /tmp/odbctrace.out.
The nzodbcsql command

The nzodbcsql command allows users to test the settings and configuration of the
Netezza ODBC driver to identify any problem settings in the odbcinst.ini and
odbc.ini files.
The nzodbcsql command is a troubleshooting tool for testing the ODBC UNIX
clients. The command is included in the bin directory of the IBM Netezza CLI
client kits for Linux, Solaris, HP, and AIX.
When you run the command, the command displays some basic help and a
summary of the driver and IBM Netezza versions. You must specify the name of
the IBM Netezza DSN, and you can include options to limit the number of result
rows for testing purposes. For example:
[nz@nzhost ~]$ /usr/local/nz/bin64/nzodbcsql NZSQL
NZODBCSQL - program to test Netezza ODBC driver
Usage : <exe> <DSN> [Max-rows]

1 - Data Source Name - mandatory
2 - Maximum rows to display - optional; default 100
Type ’quit’ or ’\q’ or CTRL-D or ENTER at the prompt to quit
NOTE: Max 100 rows are displayed (for selects)
Driver version : ’Release 6.0 [Build 14432]’

NPS version : ’06.00.0000 Release 6.0 [Build 14432]’
Database : ’system’
nzodbc >
At the nzodbc> prompt, users can enter any SQL query to test the database
connection. For example:
nzodbc > select R_Name from region;
R_NAME
---------------------------
AMERICA
AFRICA
EUROPE
ASIA
MIDDLE EAST
Rows Returned : 5
B-2 IBM Netezza ODBC, JDBC, and OLE DB Installation and Configuration Guide
If your user data contains special characters or language forms, make sure that the
LANG environment variable is set correctly. If the LANG value is incorrect, the
nzodbcsql output shows a question mark character (?) for characters that it cannot
interpret. For example:
nzodbc > select * from city_test;
CITY
----------------------
Montr?al
Montr?al
Montr?al
Rows Returned : 3
If LANG is set correctly, the accented character prints correctly. For example:
[nz@nzhost ~]$ export LANG=en_US
[nz@nzhost ~]$ ./nzodbcsql NZSQL
NZODBCSQL - program to test Netezza ODBC driver

...
nzodbc > select * from city_test;
CITY
----------------------
Montréal
Montréal
Montréal
Rows Returned : 3
The nzodbcsql command is intended for testing connectivity and settings for the
odbc.ini and network settings. Do not use the tool as a database interface to
retrieve or insert large amounts of data.
JDBC debug logging

This section describes the debug logging mechanism for JDBC, available with the
GUI, or with the following options for the connection URL.
loglevel
You can set the following log levels, which are not case-sensitive:
Table B-1. Log levels
Level Number Result
off 0 No messages are logged (default).
debug 2 Logging is done at debug level. Every message is logged.
info 3 Only information messages, entry exit statements, and
unrecoverable messages are logged.
entry_exit 4 Only entry exit statements and unrecoverable messages are
logged.
fatal 5 Only unrecoverable messages are logged.
Enter the log level either by type or by number, as in the following examples:
loglevel=entry_exit
loglevel=4
Appendix B. Troubleshooting B-3

loggertype
You can set the following log format types, which are not case-sensitive:
v loggertype=text (Default)
v loggertype=html
logdirpath
You can set the directory path for the log files, as in the following example:
logdirpath=path on the local file system
The default values for logdirpath are as follows:

v Windows: C:\
v UNIX/Linux: /tmp/
The log file name for JDBC is: nzjdbc_Time_stamp.LOGEXTENSION
Where Time_stamp is in the format YYYY-MM-DD_HH-MI-SS, and the

LOGEXTENSION is either log or HTML, depending on whether the loggertype is
text or HTML.
Connection string examples

Separate connection string components with a semicolon, as in the following
examples:
jdbc:netezza://<host>/<database>;user=<username>;password=<password>;
loglevel=<log level>;logdirpath=<log directory>
UNIX logdirpath:
jdbc:netezza://tom/will;user=admin;password=password;loglevel=2;
logdirpath=/jdbc_log_file
Windows logdirpath:
jdbc:netezza://tom/will;user=admin;password=password;loglevel=2;
logdirpath=C:\
OLE DB debug logging

OLE DB debug logging is set up through the connection URL with the following
components:
Provider
Enter NZOLEDB
User ID
Enter your user ID
Password
Enter your password
Data source
Enter the IBM Netezza appliance host name
Initial catalog
Enter the database name
Port Enter the port number. The default is 5480.
Logging Level
Enter 1 to enable logging or 0 for no logging
Log Path
Enter the path for the log file. For example, c:\logs.
Separate components with a semicolon, as in the following example:

Provider=NZOLEDB;User ID=<UserID>;Password=<Password>;Data
Source=<npshostname>;Initial Catalog=<database name>;Port=5480;Logging
Level=1;Log Path=c:\logs
Appendix B. Troubleshooting B-5

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to: This
information was developed for products and services offered in the U.S.A.
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation

Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
© Copyright IBM Corp. 2007, 2015 C-1

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Software Interoperability Coordinator, Department 49XA
3605 Highway 52 N
Rochester, MN 55901
U.S.A.
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs.
C-2 IBM Netezza ODBC, JDBC, and OLE DB Installation and Configuration Guide
Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
© your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs.
© Copyright IBM Corp. _enter the year or years_.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo, ibm.com® and Netezza are trademarks or registered trademarks
of International Business Machines Corporation in the United States, other
countries, or both. If these and other IBM trademarked terms are marked on their
first occurrence in this information with a trademark symbol (® or ™), these
symbols indicate U.S. registered or common law trademarks owned by IBM at the
time this information was published. Such trademarks may also be registered or
common law trademarks in other countries. A current list of IBM trademarks is
available on the web at "Copyright and trademark information" at
http://www.ibm.com/legal/copytrade.shtml.
Adobe is a registered trademark of Adobe Systems Incorporated in the United

States, and/ or other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other
names may be trademarks of their respective owners.
Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United
States and/or other countries.
D-CC, D-C++, Diab+, FastJ, pSOS+, SingleStep, Tornado, VxWorks, Wind River,
and the Wind River logo are trademarks, registered trademarks, or service marks
of Wind River Systems, Inc. Tornado patent pending.
APC and the APC logo are trademarks or registered trademarks of American
Power Conversion Corporation.
Other company, product or service names may be trademarks or service marks of

others.
Notices C-3
C-4 IBM Netezza ODBC, JDBC, and OLE DB Installation and Configuration Guide
Index
C JDBC (continued)
installation
ODBC (continued)
troubleshooting B-2
Character Translation Option Linux 6-1 validating connectivity
window 5-1 unsupported platforms 6-2 Linux 5-12
configuration files. See ODBC driver or Windows 6-1 validating connectivity procedure
data source configuration files. 5-1 Linux 5-13
configuration. See ODBC or JDBC driver validating connectivity steps
or data source configuration. 5-1
K Linux 5-13
ODBC configuration files A-1
Kerberos
OLE DB
D authentication tickets for JDBC 6-4
authentication tickets for ODBC 5-14
debug logging B-4
data source configuration. See ODBC or provider installation for
authentication tickets for OLE
JDBC data source configuration. 5-1 Windows 7-1
DB 7-2
data sources. See ODBC or JDBC data validating connectivity 7-2
krbSSODelegation parameter 6-6
sources. 5-1 Optimize for ASCII character set
DataDirect driver manager A-3 option 5-1
driver configuration. See ODBC or JDBC
driver configuration. 5-1 M
driver installation. See ODBC or JDBC MDAC 4-3
Microsoft Data Access Component
R
driver installation. 5-1 release compatibility 2-2
driver manager (MDAC) 4-3
absence in JDBC architecture 4-2
DataDirect
configuration file search N S
behavior A-3 schemas, specifying in connections 5-3
nzodbcsql command B-2
IBM Netezza ODBC driver SSO setup
incompatibilities A-3 Cognos 6-6
functions 4-2 supported platforms 2-1
in Linux/UNIX systems 4-3 O
in Windows systems 4-3 ODBC
introduction 4-2 data source configuration
Linux 5-9
U
Recommendation for Linux/UNIX unixODBC
systems 4-3 Windows 5-2
driver manager A-2
unixODBC data source configuration file,
installation procedure 4-3
compatibility with IBM Netezza Linux 5-9
ODBC drivers A-2 data source configuration procedure
configuration file search Linux 5-12
behavior A-2 Windows 5-3 V
installation procedure 4-3 data source configuration steps Visual Studio 8 (VC8) Libraries 5-1
Linux 5-11
debug logging B-1
I driver configuration
Linux 5-7
installation. See client tools, ODBC or driver configuration file, Linux 5-7
JDBC installation. 5-1 driver configuration procedure,
Linux 5-8
driver configuration steps, Linux 5-8
J driver functions 4-1
JDBC driver installation
configuration procedure for Windows 5-1
Linux 6-1 Windows 5-1, 5-7
UNIX/Linux 6-4 driver manager tracing B-2
Windows 6-2 driver manager. See driver
data source configuration manager 4-2
UNIX/Linux 6-4 driver properties 4-1
Windows 6-2 IBM Netezza driver version
debug logging B-3 support 2-2
driver configuration, IBM Netezza-supported
UNIX/Linux 6-4 platforms 2-1
driver configuration, Windows 6-2 installation
driver data source 2-3 Windows 5-1, 5-7
© Copyright IBM Corp. 2007, 2015 X-1

X-2 IBM Netezza ODBC, JDBC, and OLE DB Installation and Configuration Guide

Part Number: 20751-15 Rev. 3
Printed in USA

7.2 Netezza Odbc JDBC Guide

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

7.2 Netezza Odbc JDBC Guide

Uploaded by

Copyright:

Available Formats

IBM Netezza

IBM Netezza ODBC, JDBC, and OLE DB

IBM Netezza ODBC, JDBC, and OLE DB

Revised: March 11, 2015

Regulatory and compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

About this publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1. General information about ODBC, JDBC, and OLE DB . . . . . . . . . . 1-1

Chapter 2. Support and release compatibility . . . . . . . . . . . . . . . . . . . 2-1

Chapter 3. Installing and uninstalling client software . . . . . . . . . . . . . . . 3-1

Chapter 4. ODBC drivers and driver managers . . . . . . . . . . . . . . . . . . 4-1

Chapter 5. Installing and configuring ODBC . . . . . . . . . . . . . . . . . . . 5-1

© Copyright IBM Corp. 2007, 2015 iii

Chapter 7. Installing and configuring the OLE DB provider . . . . . . . . . . . . . 7-1

Appendix A. ODBC configuration files . . . . . . . . . . . . . . . . . . . . . . A-1

Appendix B. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Federal Communications Commission (FCC) Statement

Industry Canada Class A Emission Compliance Statement

This Class A digital apparatus complies with Canadian ICES-003.

Avis de conformité à la réglementation d'Industrie Canada

Cet appareil numérique de la classe A est conforme à la norme NMB-003 du

Australia and New Zealand Class A Statement

This product is a Class A product. In a domestic environment, this product might

European Union EMC Directive Conformance Statement

This product is in conformity with the protection requirements of EU Council

© Copyright IBM Corp. 2007, 2015 v

International Business Machines Corp.

European Community contact:

IBM Technical Regulations, Department M456

Germany Class A Statement

Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie

Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie

Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu

EN 55022 Klasse A Geräte müssen mit folgendem Warnhinweis versehen werden:

Deutschland: Einhaltung des Gesetzes über die

Dieses Produkt entspricht dem “Gesetz über die elektromagnetische Verträglichkeit

Zulassungsbescheinigung laut dem Deutschen Gesetz über die

Der verantwortliche Ansprechpartner des Herstellers in der EU ist:

Generelle Informationen: Das Gerät erfüllt die Schutzanforderungen nach EN 55024

Japan VCCI Class A Statement

Japan Electronics and Information Technology Industries

Japan Electronics and Information Technology Industries Association (JEITA)

Japan Electronics and Information Technology Industries

Japan Electronics and Information Technology Industries Association (JEITA)

Electronic emission notices vii

Russia Electromagnetic Interference (EMI) Class A Statement

People's Republic of China Class A Electronic Emission

Taiwan Class A Compliance Statement

Provide approved circuit breakers on all power sources.

Product might be powered by redundant power sources. Disconnect ALL power

© Copyright IBM Corp. 2007, 2015 ix

Audience for this guide

If you need help

How to send your comments

We appreciate your suggestions.

OLE DB was designed as a higher-level replacement for ODBC to support a wider

Architecture of ODBC and JDBC

The ODBC implementation is a client-server architecture, with the following major

© Copyright IBM Corp. 2007, 2015 1-1

The JDBC architecture consists of four major components:

Process steps for ODBC, JDBC, and OLE DB

ODBC Setup Summary

To set up an ODBC environment: