unixodbc and netezza ODBC driver issue (Undefined symbol: SSL_connect) -


I'm trying to set up unixODBC to connect to the Netezza database, although I'm getting the "Undefined Icon: SSL_connect"

"When I try to connect using isql.

Currently using: CentOS 5.5, unixODBC 2.3.0 (the same problem with 2.2.11).

I have done the following:

  • According to README.txt coming with ODBC drivers, configure LD_LIBRARY_PATH, ODBCINI, and NZ_INI_FILE_PATH It has been made.
  • It has been ensured that all libraries are loaded using the ldd command symbolic link for Libssl and libcrypto.
  • Netezza drivers loaded the path The /etc/ld.so.conf file has been updated to ensure that this is done.
  • Used to confirm the nm SSL_connect symbol in the driver.

    The dltest file against this symbol is running a "file not found" error reporting Which I took Usually when I isql -v run tries to do additional debugging LD_DEBUG to obtain information environment variable, which SSL_co me Nnect.

    (FYI, Export LD_Debugs = File SQL SOS OSSS which I have used.)

    Any ideas? This is driving my madness because it appears that everything is there, but it still does not work. The worst part is that I had established the same thing on Ubuntu 10-10 months ago and it worked without any issues.

    Update:

    First of all, the LDD on libnzodbc.so file looks good all dependencies are satisfied.

    Secondly, the only file in which I was missing was the libc.mo file for en_US locale, so I set a symbolic link for en_GB. Unfortunately, it is still throwing the same error, even if it seems that it is looking for every other lib that is looking for it. Should I see something else in the stress output?

    UPDATE 2:

    One issue I see is looking for ISKL gccv_end in ISO 8859-1, therefore, although this symbol does not exist interestingly enough, The symbol does not exist on my Ubuntu server VM and Isql works fine. The above versions of the unixODBC mentioned above are the same issue.

    Update 3:

    OK. With LD and R options, LDD went back and yes, there are still problems, each SSL * symbol is unavailable. I'm guessing I have created a symbolic link for the wrong file. Anyone know what SSL_connect is in the SSL library file?

    o.k. Detected. It has come to know that the symbolic link I created was indicating the wrong library file. Basically I did this:

      (/ usr / lib /) ln -s libssl3.so libssl.so.4   

    I should do this Was:

      (/ usr / lib) ln -s ../../lib/libssl.so.0.9.8e libssl.so.4   < / Div> 

Comments

Popular posts from this blog

mysql - BLOB/TEXT column 'value' used in key specification without a key length -

c# - Using Vici cool Storage with monodroid -

python - referencing a variable in another function? -