Progress Ver 9.1d JDBC/ODBC Problem

[osky50]

I haven’t been able to connect to Progress 9.1d database running on Linux Red Hat 8 Server via ODBC/JDBC using its Merant SQL-92 drivers.



[font=r_ansi]I start the db using the appropriated start up parameters to allow remote connections:[/font]

[font=r_ansi] [/font]

[font=r_ansi]proserve cap61 -L 40000 -B 500 -c 60 -n 20 -H LocalHost -S 2501[/font]

[font=r_ansi] [/font]

[font=r_ansi]Broker starts up no problem and when you test it , it does listen on port 2501.[/font]

[font=r_ansi] [/font]

[font=r_ansi]However, when you try to use expsql tool or any window odbc/jdbc client it always gives Database not started error:[/font]



[font=r_ansi]sqlexp -url jdbc:jdbcprogress:T:172.16.1.154:2501:cap61[/font]

[font=r_ansi]PROGRESS Version 9.1D as of Wed May 8 16:47:54 EDT 2002[/font]

[font=r_ansi]Connecting user "progress" to URL "jdbc:jdbcprogress:T:172.16.1.154:2501:cap61".[/font]

[font=r_ansi].. (8920)[/font]

[font=r_ansi]Error: [JDBC Progress Driver]atabase not started. (8933)[/font]

[font=r_ansi]See "/usr/prodb/sqlexp.log" and "/usr/prodb/SQLExplorer.exceptions" files for mo[/font]

[font=r_ansi]re information. (8950)[/font]

[font=r_ansi] [/font]

[font=r_ansi]If I use the progress client , it does connect to the database using por 2501.[/font]

[font=r_ansi] [/font]

Can any one help ?



TIA

Oscar

 

[miura]

HI It's Miura.
I don't have Linux Progress.
I think you should describe -N parameter (-N TCP)

Regards, Miura

 

[Fabrice]

Hi,

There could be many causes (permission on _sqlsrv2, wrong JDK version, permission on the db files, ...).

Check the Progress web site. P5893 may also be useful.

hth.

--Fabrice.

 

[Foothold]

I just fixed that very error by following P5893 (Edit LD_LIBRARY_PATH in $DLC/bin/java_env), up to a point. Option 1 does not work with the Linux j2sdk1.4.2_03/ directory structure. Option 2 may work, though I just worked it out myself.

 

[osky50]

Hi guys,



First off all thank you all for the quick reply you gave me, although I haven’t been able to solve the problem. I have looked and worked with the proposed solutions in P5893 that seems to have worked for all of you, but not for me L :



I have echoed the value of my [font=r_ansi]LD_LIBRARY_PATH variable in $DLC/bin/java_en[/font]v and all the paths that are there do exist and have the correct permissions except this: …./i386/classic.



Is that what is causing the problem ? , I don’t believe so as I installed full JDK1.4.0_03.

Do I need to use a different JDK version ?

Does any one have another suggestion ?



Thanks in advance

Here is a sample of the output when I run sqlexp (notice the echoing of LD_LIBRARY_PATH)



[font=r_ansi]PROGRESS Version 9.1D as of Wed May 8 16:47:54 EDT 2002[/font]

[font=r_ansi] [/font]

[font=r_ansi]/usr/java/j2sdk1.4.0_03/lib/i386:/usr/java/j2sdk1.4.0_03/jre/lib/i386:/usr/java/j2sdk1.4.0_03/jre/lib/i386/native_threads:/usr/java/j2sdk1.4.0_03/jre/bin:/usr/java/j2sdk1.4.0_03/jre/lib/i386/classic:[/font]

[font=r_ansi] [/font]

[font=r_ansi]Connecting user "progress" to URL "jdbc:jdbcprogress:T:172.16.1.154:2501:cap61".[/font]

[font=r_ansi].. (8920)[/font]

[font=r_ansi]Error: [JDBC Progress Driver]atabase not started. (8933)[/font]

[font=r_ansi]See "/home/progress/sqlexp.log" and "/home/progress/SQLExplorer.exceptions" file[/font]

[font=r_ansi]s for more information. (8950)[/font]

 

[Foothold]

> /usr/java/j2sdk1.4.0_03/jre/lib/i386/classic

That's your problem.

in the /usr/dlc/bin/java_env, right above the LD_LIBRARY_PATH section, replace "classic" with "server".

VMTYPE=server

Or use
find /usr/java/ -name "*.so"
to list all the Java .so, and match up those paths with the libraries required. View the required libraries with
ldd $DLC/bin/_sqlsrv2

 

[osky50]

Hi Patrick ,



I followed your instructions still no luck L . I have checked library dependencies and now everything it is in the path define in [font=r_ansi]LD_LIBRARY_PATH[/font]. Checking the output of the following command, it shows that files are there no problem and below I also show the current value of the variable [font=r_ansi]LD_LIBRARY_PATH after the latest changes, so you can see. [/font]



What else could it be ??? L
Thanks for your help


[font=r_ansi]$> ldd _sqlsrv2 | grep "not found" | cut -f1 -d"=" | xargs Locate[/font]

[font=r_ansi]/usr/dlc/lib/libprosqlsnd.so[/font]

[font=r_ansi]/usr/dlc/lib/libprosqlrds.so[/font]

[font=r_ansi]/usr/dlc/lib/libprosqlsnw.so[/font]

[font=r_ansi]/usr/dlc/lib/libprosqlgeneric.so[/font]

[font=r_ansi]/usr/dlc/lib/libprosqldb.so[/font]

[font=r_ansi]/usr/dlc/lib/libprosqlmm.so[/font]

[font=r_ansi]/usr/dlc/lib/libpronls.so[/font]

[font=r_ansi]/usr/dlc/lib/libprosqlss.so[/font]

[font=r_ansi]/usr/dlc/lib/libprosqljava.so[/font]

[font=r_ansi]/usr/dlc/lib/libprosqlos.so[/font]

[font=r_ansi]/usr/dlc/lib/librocket_r.so[/font]

[font=r_ansi]/usr/dlc/lib/libusort.so[/font]

[font=r_ansi]/usr/java/j2sdk1.4.0_03/jre/lib/i386/client/libjvm.so[/font]

[font=r_ansi]/usr/java/j2sdk1.4.0_03/jre/lib/i386/server/libjvm.so[/font]

[font=r_ansi]/usr/java/j2sdk1.4.0_03/jre/lib/i386/native_threads/libhpi.so[/font]



[font=r_ansi]$> sqlexp -url jdbc:jdbcprogress:T:localhost:2501:cap61[/font]

[font=r_ansi]PROGRESS Version 9.1D as of Wed May 8 16:47:54 EDT 2002[/font]

[font=r_ansi]/usr/java/j2sdk1.4.0_03/lib/i386:/usr/java/j2sdk1.4.0_03/jre/lib/i386:/usr/java/[/font]

[font=r_ansi]j2sdk1.4.0_03/jre/lib/i386/native_threads:/usr/java/j2sdk1.4.0_03/jre/bin:/usr/j[/font]

[font=r_ansi]ava/j2sdk1.4.0_03/jre/lib/i386/client:/usr/java/j2sdk1.4.0_03/jre/lib/i386/serve[/font]

[font=r_ansi]r:[/font]

[font=r_ansi]Write access denied for file /usr/dlc/bin/sqlexp.log. (9229)[/font]

[font=r_ansi]SYSTEM ERROR: SQL Explorer terminating. (9232)[/font]

 

[dopena]

Don't use localhost in your -H parameter use the hostname instead.

 

[osky50]

It is actually running with -H Xart which is the real host name, it was a mistake of the posting sample. Still not being able to make it work :-(

 

[dopena]

Hmm! I have exactly the same problem before in HPUX and I called Progress they said that 91d doesn't work by using the word localhost rather than its actual host. I changed it at ait works. So it must be somthing else then. If I find my notes I will post it. Chaio.

 

[dopena]

Here is a KB maybe related to your error. BTW do you know where can I download Progress 91d for Linux Redhat/Fedora Core?

----------------------------------------------------------------------
Specifying -H localhost at Database Startup in V9 -- (1432)
----------------------------------------------------------------------
SUMMARY:

This Solution applies to Progress Version 9. It describes the
consequences of using '-H localhost' when starting a Database on
Version 9.

EXPLANATION:

In version 8, there is no difference when you specify '-H localhost',
'-H <machine name>', or no -H is used when starting a Database Server
( with _mprosrv or proserve). When the second form is used, Progress
performs a check on <machine name> to make sure that it matches the
machine name as returned by OS command 'hostname', but other than that
there is no functional difference between the three methods.

In Version 9, if you specify '-H localhost', the Database Server
process will be bound to the loopback interface and this will not
allow network connections from Clients on other machines.

If you try to connect a 4GL Client from a remote machine, you will get
the following error:

** Could not connect to server for database <DATABASE>, errno
<ERRNO>. (1432)

If you try to connect an ODBC Client via the Test button in the ODBC
Administration Tool the error is:

[MERANT] [ODBC PROGRESS DRIVER] [PROGRESS] Error in network daemon.

From a JDBC client, the following error message should appear:

Error : [JDBC Progress Driver]:Error in Network Daemon. (8933)

You might want to do that when running different Client and Server
versions (for example: 9.1C Clients connecting to a 9.0B Server, via
-H localhost -S ... -N TCP) and at the same time you want to prevent
remote Clients from connecting to the Database.

This is only relevant to the Database Server process (_mprosrv).
Other Client products (4GL Client, WebSpeed, AppServer) are not
affected.


References to Written Documentation:

Progress Knowledge Base Solution 19550, "1432 Error When Trying To
Connect Remote Client w/ Provision"