Setting up a connection to Netezza

You must install and configure the Netezza ODBC driver on the client machine from which you connect to the Netezza database.

Steps:

1. Install the Netezza ODBC driver on the client machine.

   Install a 32-bit ODBC driver if connecting from a 32-bit application such as ArcGIS for Desktop; install a 64-bit ODBC driver if connecting from a 64-bit application such as ArcGIS for Server. See the Netezza DBMS system requirements for supported versions of the driver.

2. Configure the driver to use a specific character set:
   • For Windows operating systems, set the driver to Optimize for ASCII character set during ODBC driver installation.
   • For Linux operating systems, set the following parameters in the odbcinst.ini file after ODBC driver installation:
     • UnicodeTranslationOption = utf16
     • CharacterTranslationOption = latin9
3. If connecting from ArcGIS Server on Linux, do the following:
   1. Open the init_user_param.sh script found in the /arcgis/server/usr directory of the ArcGIS Server installation directory.
   2. Uncomment and set the LIB_ODBC_DRIVER_MANAGER variable to the location of the libodbc.so.2.0.0 file.

      For example, export LIB_ODBC_DRIVER_MANAGER=$HOME/bin/libodbc.so.2.0.0

   3. Place the Netezza ODBC connection files in the ArcGIS user's $HOME directory. The files must be named .odbc.ini and .odbcinst.ini.
   4. If ArcGIS Server was already running before you set up the Netezza connection, restart ArcGIS Server.
4. After the ODBC driver is installed, you can set up an ODBC data source name. This name can then be used when you connect to the database.

   If you set an ODBC data source name for the database, use the same name when configuring all Netezza ODBC clients to that same database. For example, if you configure a data source name for the Netezza ODBC driver on your ArcGIS for Desktop machine, set the same data source name for the Netezza ODBC driver on your ArcGIS Server machine. If you do not do this, registration of the database with ArcGIS Server will not work properly, as it compares the connection strings of the data being published and the database that is registered.