Article

Error numbers are returned in place of error messages with Connect drivers on UNIX / Linux

« Go Back

Information

 
Article Number000003050
EnvironmentProduct: Connect/Connect64 for ODBC, SequeLink ODBC client driver, OpenAccess ODBC client driver
Version: All supported versions
OS: All UNIX/Linux platforms
Database: All supported databases
Application: All supported applications
Question/Problem Description
When trying to connect to a database or running a query with the Connect/Connect64 for ODBC, SequeLink ODBC client driver, OpenAccess ODBC client driver, error numbers like 523 80 6105 6107 20101 are returned instead of an error message.
 
Steps to Reproduce
Clarifying Information
Error MessageSQLSTATE = 81
NATIVE ERROR = 0
MSG = 523 80

SQLSTATE = 60
NATIVE ERROR = 6105
MSG = [DataDirect][ODBC 20101 driver]6105

SQLSTATE = 60
NATIVE ERROR = 6107
MSG = [DataDirect][ODBC 20101 driver]6107

523 638
Defect/Enhancement Number
Cause
The ODBC driver manager and/or the ODBC driver library cannot load its message files.
InstallDir is not set correctly in the [ODBC] section of the odbc.ini file or the message files in locale/en_US/LC_MESSAGES are missing.
Resolution
Make sure the following are set correctly:
  • Set the environment variable LANG to en_US : 
    export LANG=en_US (ksh shell)
    setenv LANG en_US (csh shell)
  • Ensure that the environment variable ODBCINI (or ODBC_INI) is pointing to the proper odbc.ini file
  • Ensure that in the [ODBC] section of your odbc.ini file the correct installation path of the ODBC drivers is specified for InstallDir 
    e.g. InstallDir=/opt/odbc
  • Make sure the .mo / .po messages files exist (odbcinstaldir/locale/en_US/LC_MESSAGES) and can be loaded by your application


Act upon the error text which is returned.

For example: 523 80 will be translated to

523 "[DataDirect][ODBC lib]"
80 "Specified driver could not be loaded"

For this error message:
- Verify if the specified driver name location in your odbc datasource is correct
- Verify if the ODBCINI is pointing to the expected odbc.ini
- Verify if the Driver entry of the ODBC data source is pointing to a library specific for this platform (use the 'file driverlibname' command) 
- Verify if the library path environment variable contains the odbc/lib directory
- Verify that the security settings on the drivers and files have not been removed or changed so that the current user no longer has permissions to use the files.
- Ensure to use a 32-bit app with 32-bit ODBC drivers, versus 64-bit app with 64-bit ODBC drivers

Workaround
Notes
Attachment 
Last Modified Date11/5/2018 7:50 PM


Feedback
 
Did this article resolve your question/issue?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025