Datadirect odbc lib specified driver could not be loaded datastage

SQLConnect error: Status = -1 SQLState = IM Natcode = 0 [ODBC] [DataDirect][ODBC lib] Specified driver could not be loaded Invalid parameter(s) found in configuration file then you may have to create a link to a shared library. Use the "ldd" utility to check why the driver will not load: $ ldd www.doorway.ru www.doorway.ru1 = (0xffffe). Error for thread 0 {error} STATE=IM, CODE=, MSG=[DataDirect][ODBC lib] Specified driver could not be loaded This issue can occur in one or more of the following cases: The Netezza ODBC library path is not included in the library path environment variable.  · SQLConnect error: Status = -1 SQLState = IM Natcode = 0 [ODBC] [DataDirect][ODBC lib] Specified driver could not be loaded Invalid parameter(s) found in configuration file Diagnosing The Problem Refer to How to troubleshoot ODBC connectivity errors in DataStage to check the configuration.

SQLConnect error: Status = -1 SQLState = IM Natcode = 0 [ODBC] [DataDirect][ODBC lib] Specified driver could not be loaded Invalid parameter(s) found in configuration file then you may have to create a link to a shared library. Use the "ldd" utility to check why the driver will not load: $ ldd www.doorway.ru www.doorway.ru1 = (0xffffe). 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=IM][Native=0] [DataDirect][ODBC lib] Specified driver could not be loaded. "[DataDirect][ODBC lib] Specified driver could not be loaded" while starting Repository Service in version ERROR: "Specified driver could not be loaded" when connecting to Data Service through PowerCenter or testing connectivity through SSGODBC.

13 sept Setting up odbc driver on UNIX Error when attempting to connect to database. Specified driver could not be loaded SQLConnect: Failed. [ISQL]ERROR: Could not SQLConnect. Explanation: You might see this error in a Linux environment when you configure the ODBC driver. It is related to www.doorway.ru Amazon Redshift provides bit ODBC drivers for Linux, Windows, These applications might not be able to detect user DSNs that are created under another.