The 64 bit ODBC driver of DB2-Client 10.1.2 (the shared library "libdb2o.so") contains an unresolved symbol named "db2Ingest".
An attempt of loading the library using immediate symbol resolution fails: dlopen("libdb2o.so", RTLD_NOW) returns NULL.
After that, a call of dlerror() returns a pointer to this message:
"/home/db2inst1/sqllib/lib64/libdb2o.so: undefined symbol: db2Ingest"
The library can only be loaded using lazy resolution: dlopen("libdb2o.so", RTLD_LAZY).
---> This seems to be an error - or can the symbol be left unresolved by purpose? Does anybody know?
Another problem with the "libdb2o.so" is its versioning:
The library seems to have a version number 1, because when linking a program with argument "-ldb2o", a call of "ldd" shows a reference to "libdb2o.so.1".
But in the directory "lib64" of DB2-Client 10.1.2, there is no such entry, but only a file "libdb2o.so".
I expected two entries in the directory: a symbolic link named "libdb2o.so", pointing to a file "libdb2o.so.1".
---> Perhaps the installation procedure forgets to store the versioned file and create a symbolic link?
This topic has been locked.
Pinned topic Problems with the 64 bit ODBC driver of DB2-Client 10.1.2 (libdb2o.so)
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Re: Problems with the 64 bit ODBC driver of DB2-Client 10.1.2 (libdb2o.so)2012-12-21T21:33:11ZThis is the accepted answer. This is the accepted answer.Hello,
db2Ingest is a new API interface matching the CLP command INGEST, newly introduced in Fix Pack 2 :
You should open a PMR with IBM support.