public inbox for rhdb@sourceware.org
 help / color / mirror / Atom feed
From: "Derrick Snowden" <Derrick.Snowden@noaa.gov>
To: rhdb@sources.redhat.com
Cc: Derrick Snowden <Derrick.Snowden@noaa.gov>
Subject: Revisiting java problems
Date: Thu, 05 Feb 2004 00:09:00 -0000	[thread overview]
Message-ID: <1075939733.2320.10.camel@doris.aoml.noaa.gov> (raw)

Hi

I have read the thread from Jan 19 re java problems and I'm still
stumbling. I'm using FC1 and I have followed all the instructions in
that thread yet I still get the same error about rhdb-admin and the
classpath.  It is unable to find org.postgresql.jdbc3.*

I've installed postgresql-jdbc-7.3.4-11.i386.rpm and have verified that
postgresql.jar is in /usr/share/java yet if I try

% grepjar jdbc postgresql.jar

There is no mention to anything with the string jdbc3.  There are
however, jdbc1 matches.  I then downloaded the source tar.gz files for
postgres-base-7.3.4-11 and in the src/interfaces directory there are
*.java files to build classes with jdbc3 in the title.  

Is there anything else I have to do?  I should mention that rhdb-cc
fails with an error 
"Unable to find the java executable" which is in my PATH env variable. 
And, rhdb-visual explain fails to connect to a database with 

"Reason: JDBC Driver (org.postgresql.Driver) could not be found"
grepjar for Driver reveals

$ grepjar Driver postgresql.jar
org/postgresql/largeobject/LargeObjectManager.class:org/postgresql/Driver
org/postgresql/fastpath/Fastpath.class:org/postgresql/Driver
Z_BUF_ERROR

Any ideas?

thanks much!
Derrick



-- 
Derrick Snowden			
PhOD/AOML/NOAA			
4301 Rickenbacker Causeway
Miami, FL 33149			
Office:  305.361.4322  Fax: 305.361.4392

             reply	other threads:[~2004-02-05  0:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05  0:09 Derrick Snowden [this message]
2004-02-09 21:11 ` Fernando Nasser
2004-02-09 21:28 ` David Jee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1075939733.2320.10.camel@doris.aoml.noaa.gov \
    --to=derrick.snowden@noaa.gov \
    --cc=rhdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).