Omnis Technical Note TNSQ0014 Updated January 2009

Configuring Oracle DAM(s) on Linux

For Omnis Studio
By Gary Ashford, Omnis Engineering


"The Oracle DAM shipped with Omnis Studio for Linux appears to have a version of Oracle clientware hard-coded into it. When starting Omnis, the DAM does not load because the version of Oracle clientware I am using is different."


When we build the Oracle DAM using the Linux compiler and linker tools (gcc and ld), the linker resolves the name of the client library we are linking against to the particular library on the build machine, e.g.
When Oracle 11g client is installed, this will be
This happens even if we rename to or when the DAM is linked via a symbolic link which in turn points to the target library. The former seems to occur because the linker picks up the verbose library name embedded into the Oracle client library.

Thus, it is not currently possible for us to produce an Oracle DAM which simply links against a generic "" library; the ideal scenario, because Oracle clientware otherwise follows the Linux convention whereby a symbolic link is shipped along with the target library, e.g.

ls -al              
lrwxrwxrwx 1 user users
14.08 ->
-rwxr-xr-x 1 user users

You can display the version of Oracle client which the Oracle DAM requires by navigating to the Omnis/xcomp folder and executing:

ldd => (0xffffe000) => not found => /usr/lib/ (0x40a7b000) => /lib/tls/ (0x40b00000) => /lib/tls/ (0x40b23000) => /home/oracle/OraHome92/lib/ (0x40c39000) => /lib/ (0x40c3c000) => /lib/tls/ (0x40c41000) => /lib/ (0x40c53000) => /usr/X11R6/lib/ (0x40c69000) => /usr/lib/ (0x40c7c000) => /usr/X11R6/lib/ (0x40c99000)
/lib/ => /lib/ (0x80000000) => /usr/X11R6/lib/ (0x40d96000) => /usr/X11R6/lib/ (0x40d9e000) => /usr/lib/ (0x40dac000) => /usr/lib/ (0x40dd6000) => /usr/lib/ (0x40df5000) => /usr/lib/ (0x40e64000) => /usr/lib/ (0x40e95000)


To resolve the missing library dependency, you need to create a symbolic link to the Oracle client library on your system and ensure that the filename matches that required by the DAM (see above).
You further need to ensure that the symbolic link you create is in a location where the Linux dynamic linker will find it, e.g. in a location specified by the LD_LIBRARY_PATH environment variable or on the standard library search path (/usr/lib & /usr/local/lib).

su  root
cd  /usr/lib
ln  -s  /home/oracle/OraHome92/lib/


su  root
cd  /home/oracle/Ora_Home1
ln  -s  /home/oracle/OraHome92/lib/

The above example assumes that the Oracle DAM requires and that the library installed on your system is and is located as shown. After creating the symbolic link, check that it points to the correct library (using ls -al). You can also verify that the linker will find the library by navigating to the Omnis/xcomp folder and executing ldd again.

The dependency should now be resolved and the Oracle DAM should load when Omnis Studio starts.