Troubleshooting

When using the Netezza connector, you might encounter errors that can be fixed by troubleshooting and adjusting values for properties or configuration.

Connection errors

You might encounter the following connection errors:

Table 1. Connection errors
Error type	Error details	Troubleshooting details
ODBC Driver Cannot Be Loaded	When running a Netezza connector DataStage job, or running a Metadata Import Wizard, or performing View data, you might encounter the following error: `Connection to database testdb with user testuser using DSN NZSQL failed. Reason: [SQLCODE=IM003][Native=0] [DataDirect][ODBC lib] Specified driver could not be loaded` Reason for the error might be as follows: On Windows 64-bit – A 64-bit version of the Netezza driver is installed. This does not work because Information Server is a 32-bit application on Windows. On Unix, the library search path is not set correctly.	For the error in a Windows 64-bit system: Make sure that both 32-bit and 64-bit drivers are installed. Make sure that you define your DSNs using the 32-bit version of Data source (ODBC). The 32-bit version of the Odbcad32.exe file is located in the %systemdrive%\Windows\SysWoW64 folder. See the following article for more details of DSN-related issues on Windows 64-bit: http://support.microsoft.com/kb/942976 For the error in a Unix system, include the Netezza ODBC driver directory (<nz-odbc-home>/lib64) in the path search environment variable. On an AIX system, if you get the error even after the library search path is set properly, you need to go to the Netezza ODBC driver directory (<nz-odbc-home>/lib64) and create the following symbolic link (depending on your setup you might need root privileges) : `cd <nz-odbc-home>/lib64 ln -s libnzodbc.a libnzodbc.so`
Incorrect Data Source Name (DSN)	When running a Netezza connector DataStage job, or running a Metadata Import Wizard, or performing View data, you might encounter the following error: `Connection to database testdb with user testuser using DSN NZSQL failed. Reason: [SQLCODE=IM002][Native=0] [DataDirect][ODBC lib] Data source name not found and no default driver specified` On a Unix system if `NZ_ODBC_INI_PATH`, is not set correctly you might encounter the following error: `Connection to database testdb with user testuser using DSN NZSQL failed. Reason: [SQLCODE=HY000][Native=33] Server and/or port attributes are empty`	For the error in a Windows system, start Data source (ODBC) and check the DSN name. For MDI and View data check the account under which the ASBAgent service is running. If the ASBAgent service is running under the system account, the DSN names must be defined as System DSNs. Otherwise, both the system and the user DSNs can be used. An InfoSphere DataStage job can access both system and user DSNs. For the error in a Unix system, you need to make sure that the case of the DSN matches. Also make sure that the environment variables: `ODBCINI` and `NZ_ODBC_INI_PATH` are set correctly. `ODBCINI` need to point to the correct odbc.ini file, and `NZ_ODBC_INI_PATH` needs to be set to the directory where the correct odbc.ini file is located.
User name/Password Issues	When running a Netezza connector DataStage job, or running a Metadata Import Wizard, or performing View data, you might encounter the following error: `Connection to database testdb with user testuser using DSN NZSQL failed. Reason: [SQLCODE=28000][Native=24] Password authentication failed for user 'testuser1'`	Verify that the user name/password combination is entered correctly in the job/MDI wizard. Also make sure that the specified user has the right privileges to connect to the selected database.
Firewall Issues	If the Netezza server is behind a firewall and you have not authenticated prior to running a Netezza connector job, or running a Metadata Import Wizard, or performing View data, you might encounter the following error: `Connection to database testdb with user testuser using DSN NZSQL failed. Reason: [SQLCODE=HY000][Native=0] [DataDirect][ODBC lib] Unicode converter truncated character`	Authenticate with the firewall prior to running a Netezza connector job, or running a Metadata Import Wizard, or performing View data.

Runtime errors

After the Netezza connector successfully connects to the Netezza server you might encounter the following errors:

Table 2. Run-time errors
Error type	Error details	Troubleshooting details
Schema Reconciliation Issues	Extra Link Columns When running a Netezza connector job, you might encounter the following error: `The following input link column(s): col2 were not found in the table test_table` Extra Table Columns When running a Netezza connector job, you might encounter the following error: `The following column(s): COL2 from the table test_table were not found in the input link schema`	The Extra Link Columns error occurs when the job is referring to a column that does not exist in the target table or the temporary work table. You need to either make sure that your job and your tables) have the same columns, or configure the connector to drop the extra columns by setting the connector property: Schema reconciliation → Unmatched link column action to Drop. The Extra Table Columns error occurs when the target table or the temporary work table has one or more columns not found in the link schema. You need to either make sure that your job and your tables have the same columns, or instruct the connector to ignore the extra columns by setting the connector property: Schema reconciliation → Unmatched table column action to Ignore nullable or Ignore all. The job might still fail if the extra columns are not nullable or if they do not have a default value.
Temporary Work Table (TWT) is in a Separate Database	When using an existing temporary work table in a separate database, the Netezza connector job might fail with the following error: `Table twttable not found`	You need to make sure that the correct TWT name is specified, if a fully qualified name is given, and if all the name parts are correct. Also, make sure that the connector property Use separate connection for TWT is set to Yes and that the child properties are set to the correct values.