Creating a Data Source Name

Typically, after installing the Simba Netezza ODBC Driver, you need to create a Data Source Name (DSN). A DSN is a data structure that stores connection information so that it can be used by the connector to connect to Netezza.

You can specify connection settings in a DSN (in the odbc.ini file), in a connection string, or as connector-wide settings (in the simba.netezzaodbc.ini file). Settings in the connection string take precedence over settings in the DSN, and settings in the DSN take precedence over connector-wide settings.

The following instructions describe how to create a DSN by specifying connection settings in the odbc.ini file. If your machine is already configured to use an existing odbc.ini file, then update that file by adding the settings described below. Otherwise, copy the odbc.ini file from the Setup subfolder in the connector installation directory to the home directory, and then update the file as described below.

For information about specifying settings in a connection string, see Configuring a DSN-less Connection and Using a Connection String. For information about connector-wide settings, see Setting Connector-Wide Configuration Options.

To create a Data Source Name:

1. In a text editor, open the odbc.ini configuration file.

Note:

If you are using a hidden copy of the odbc.ini file, then you need to remove the period (.) from the start of the file name before the file becomes editable.

2. In the [ODBC Data Sources] section, add a new entry by typing a name for the DSN, an equal sign (=), and then the name of the connector.

For example, on a macOS machine:

[ODBC Data Sources]

Sample DSN=Simba Netezza ODBC Driver

For example, for a 32-bit connector on a Linux machine:

[ODBC Data Sources]

Sample DSN=Simba Netezza ODBC Driver 32-bit

3. Create a section that has the same name as your DSN, and then specify configuration options as key-value pairs in the section:
   1. Set the Driver property to the full path of the connector library file that matches the bitness of the application.

   For example, on a macOS machine:

   Driver=/Library/simba/netezzaodbc/lib/libnetezzaodbc_sbu.dylib

   For example, for a 32-bit connector on a Linux machine:

   Driver=/opt/simba/netezzaodbc/lib/32/libnetezzaodbc_sb32.so

   2. Set the Server property to the IP address or host name of the server, and then set the Port property to the number of the TCP port that the server uses to listen for client connections.

      For example:

      Server=192.168.222.160

      Port=5480

   3. Set the Database property to the name of the database that you want to access.

   For example:

   Database=Local

   4. Configure authentication by doing one of the following:
      • If your Netezza server is configured to authenticate the connection using MIT Kerberos or AD Kerberos, then set the UID property to your user name for accessing the database.

      For example:

      UID=skroob

      • Or, if your Netezza server is configured to authenticate the connection using another authentication method, then set the UID and PWD properties to your user name and password for accessing the database.

      For example:

      UID=skroob

      PWD=simba123456

      Note:

      Kerberos authentication on Netezza must be configured on the server.

   5. If you want to connect to the server through SSL, set the SecurityLevel connection property to the desired level of security, and set the CACertFile property to point to your security certificate. For more information, see Configuring SSL Verification.
   6. Optionally, set additional key-value pairs as needed to specify other optional connection settings. For detailed information about all the configuration options supported by the Simba Netezza ODBC Driver, see Driver Configuration Options on page 1.
4. Save the odbc.ini configuration file.

Note:

If you are storing this file in its default location in the home directory, then prefix the file name with a period (.) so that the file becomes hidden. If you are storing this file in another location, then save it as a non-hidden file (without the prefix), and make sure that the ODBCINI environment variable specifies the location. For more information, see Specifying the Locations of the Connector Configuration Files.

For example, the following is an odbc.ini configuration file for macOS containing a DSN that connects to Netezza over Kerberos:

You can now use the DSN in an application to connect to the data store.

Related topics

• Configuring a DSN-less Connection
• Configuring SSL Verification
• Configuring Logging Options
• Testing the Connection on a Non-Windows Machine on Linux on page 1
• Configuring the Driver on page 1
• Driver Configuration Options on page 1
• Specifying the Locations of the Driver Configuration Files on page 1