Progress 9.1E: No suitable driver

Ask our resident Progress expert about optimizing Yellowfin on your database

Progress 9.1E: No suitable driver

Postby Steve Joynt on Tue Oct 28, 2008 2:22 am

When attempting to connect to a Progress 9.1E database from Linux, a number of problems may cause the "No suitable driver" error. The most common is that the environment is not set up correctly to find the Progress libraries. Progress provides the java_env and slib_env scripts to set up the environment, and these should be run before starting Yellowfin. These can be put into the login scripts of the user that will start Yellowfin. For example, assuming the user is using the Bash shell, add these lines to .bashrc in the user's home directory:
Code: Select all
export DLC=/usr/dlc91e
export PATH="$PATH:$DLC/bin"
. $DLC/bin/java_env
. $DLC/bin/slib_env


Alternatively, the lines above can be added to the Yellowfin startup script. This may be easier if Yellowfin is being started from the system startup scripts automatically. In this case, add the lines to yellowfin/appserver/bin/catalina.sh in the "Yellowfin Options" section.

Another cause of the "No suitable driver" error is that Progress cannot find the necessary libraries. Check the output of "ldd $DLC/bin/_sqlsrv2". You will need to fix any libraries that say "not found":

Code: Select all
$ ldd $DLC/bin/_sqlsrv2
   linux-gate.so.1 =>  (0xffffe000)
   libprosqlsnd.so => /usr/dlc91e/lib/libprosqlsnd.so (0xb7eed000)
   libprosqlrds.so => /usr/dlc91e/lib/libprosqlrds.so (0xb7c68000)
   libprosqlsnw.so => /usr/dlc91e/lib/libprosqlsnw.so (0xb7c4a000)
   libprosqlgeneric.so => /usr/dlc91e/lib/libprosqlgeneric.so (0xb7b90000)
   libprosqldb.so => /usr/dlc91e/lib/libprosqldb.so (0xb7b34000)
   libprosqlmm.so => /usr/dlc91e/lib/libprosqlmm.so (0xb7b05000)
   libpronls.so => /usr/dlc91e/lib/libpronls.so (0xb7af7000)
   libprosqlss.so => /usr/dlc91e/lib/libprosqlss.so (0xb7af0000)
   libprosqljava.so => /usr/dlc91e/lib/libprosqljava.so (0xb7aec000)
   libprosqlos.so => /usr/dlc91e/lib/libprosqlos.so (0xb7ae5000)
   librocket_r.so => /usr/dlc91e/lib/librocket_r.so (0xb7a35000)
   libusort.so => /usr/dlc91e/lib/libusort.so (0xb7a33000)
   libjvm.so => not found
   libhpi.so => not found
   libnsl.so.1 => /lib/libnsl.so.1 (0xb7a1a000)
   libpthread.so.0 => /lib/libpthread.so.0 (0xb79c9000)
   libcrypt.so.1 => /lib/libcrypt.so.1 (0xb799d000)
   libdl.so.2 => /lib/libdl.so.2 (0xb799a000)
   libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0xb7952000)
   libm.so.6 => /lib/libm.so.6 (0xb7930000)
   libc.so.6 => /lib/libc.so.6 (0xb7818000)
   /lib/ld-linux.so.2 (0xb7ef5000)


If the various libpro* libraries are not found, check that the LD_LIBRARY_PATH environment variable includes the $DLC/lib directory. This should be set up by the slib_env script. If the libjvm/libhpi libraries are not found (as above), check that the LD_LIBRARY_PATH environment variable includes references to the java directories. This should be set up by the java_env script. Also see this knowledge base document. If other libraries are not found, you will need to install them. The process for installing libraries varies depending on the Linux distribution.

On recent versions of Linux you will often need to set the LD_ASSUME_KERNEL environment variable to 2.4.1 as decribed here. However, if you find you are getting timeouts after adding this, follow these instructions.

One more issue that can cause this error is using a 64-bit jvm. When running on a 64-bit architecture machine, you will need to run Yellowfin with a 32-bit jvm to be able to connect to Progress 9.1E. You can have multiple jvms installed, so it should not affect any other applications on your server. After installing a 32-bit jvm, you can change the jvm that Yellowfin uses by editing yellowfin/appserver/bin/catalina.sh:

Code: Select all
# set JAVA_HOME to value chosen in installer
JAVA_HOME="/usr/java-1.6"


Change this path to point to the 32-bit jvm directory.
Steve Joynt
 
Posts: 23
Joined: Mon Oct 30, 2006 4:48 am
Location: Melbourne, Australia

golfwholesaleseller

Postby bangde92 on Sun Jun 13, 2010 8:45 am

golfwholesaleseller

The Callaway FT-i driver

The Callaway FT-i driver has a square head with full carbon body technology meaning extra weight savings over a titanium head. By using a lightweight carbon body that weighs only 42g, the wholesale golf Callaway FT-i has been able to push as much weight as possible into the far corners of the head ishiner, dramatically increasing the club’s ability to resist twisting on off-centre hits and thus increase the Moment of Inertia (MOI) for straighter drives.
bangde92
 
Posts: 3
Joined: Thu Jun 10, 2010 5:58 am


Return to Yellowfin on Progress Database Engine

Who is online

Users browsing this forum: No registered users and 1 guest

cron