DlLoadLib: dlopen()= Could not load module

Question

When are the db6 libraries and binaries loaded? It would appear as if the db6 binaries are not loaded on this machine. Are they loaded as part of the Central Instance install - or perhaps the database instance installation.....
The file listed below does not exist - nor do the db6 executables that would normally be found under /sapmnt/<SID>exe
disp+work information from my server
kernel release                700
kernel make variant           700_REL
compiled on                   AIX 2 5 005DD9CD4C00
compiled for                  64 BIT
compilation mode              UNICODE
compile time                  May 21 2007 20:41:26
Thu Dec 27 14:48:17 2007
ERROR => DlLoadLib: dlopen()= Could not load module /usr/sap/UV3/SYS/exe/run/dbdb6slib.o.
System error: No such file or directory -> DLENOACCESS (2,No such file or directory) [dlux.c       314]
update level                  0
patch number                  111
source id                     0.111
supported environment
database (SAP, table SVERS)   700
operating system
AIX 1 5
AIX 2 5
AIX 3 5

Answer 1

Hi Timothy,
SAP Executables like disp+work, R3trans, R3load, tp, etc. that connect to the database load the SAP database interface library ( dbdb6slib.* ).
The are looking for this library in the current path or in the directory indicated by DIR_LIBRARY. In your case the SAP executable tries to load /usr/sap/UV3/SYS/exe/run/dbdb6slib.o .
The SAP database interface library itself dynamically loads the DB2 CLI libraries. If you are using a DB2 runtime client the DB2 CLI libraries ( libdb2.a and dependent libraries ) are expected to be located in ~($DB2INSTANCE)/sqllib/lib . This is typically /db2/db2<dbname>/sqllib/lib.
Only if libdb2.a is not found in this path LD_LIBRARY_PATCH or LIBPATH will be searched.
The library search path is automatically assembled by the SAP executables from DB2INSTANCE which is set by SAPINST. You do not need to include the path to the DB2 libraries in LD_LIBRARY_PATCH or LIBPATH explicitly.  On the other hand if you accidently include the wrong path in  LD_LIBRARY_PATCH or LIBPATH , the SAP executable will still try to load ~($DB2INSTANCE)/sqllib/lib/libdb2.a but the dependent libraries of libdb2.a may be taken from the wrong path.
Regards
              Frank